It would seem that the ZFS Web UI lacks a few requisite classes to support the
updates ZFS features in snv_b89+.
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/lis
Just a note:
Setting compression to gzip on a zpool breaks the GUI with a similar type of
error -
Application Error
com.iplanet.jato.NavigationException: Exception encountered during forward
Root cause = [java.lang.IllegalArgumentException: No enum const class
com.sun.zfs.common.model.Compressi
Hi Dan,
I filed a bug 6715550 to fix this issue.
Thanks for reporting it--
Cindy
Dan Reiland wrote:
>>Yeah. The command line works fine. Thought it to be a
>>bit curious that there was an issue with the HTTP
>>interface. It's low priority I guess because it
>>doesn't impact the functionality re
That fixed it on my SunBlade 2500 with NV90. Thank you very much. This has been
happening on and off for many builds. The fix gores in my "How To" document.
--ron
Message was edited by:
halstead
This message posted from opensolaris.org
___
Interesting, we'll try that.
Our server with the problem has been boxed now, so I'll check the solution when
it gets on site.
Thanks ahead, anyway ;)
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
> Yeah. The command line works fine. Thought it to be a
> bit curious that there was an issue with the HTTP
> interface. It's low priority I guess because it
> doesn't impact the functionality really.
>
> Thanks for the responses.
I was receiving the same stacktrace:
[b]No enum const class
com.s
Yeah. The command line works fine. Thought it to be a bit curious that there
was an issue with the HTTP interface. It's low priority I guess because it
doesn't impact the functionality really.
Thanks for the responses.
This message posted from opensolaris.org
Likewise. Just plain doesn't work.
Not required though, since the command-line is okay and way powerful ;)
And there are some more interesting challenges to work on, so I didn't push
this problem any more yet.
This message posted from opensolaris.org
_
> snv_89 is the same. The ZFS Administration console
> worked fine to create my first 2 pools. I've been
> unable to use it since then. I have the same stack
> trace errors.
>
> Did you find a workaround for this issue?
>
> -Rick
Nothing yetdropping to the command line for the moment. Lookin
snv_89 is the same. The ZFS Administration console worked fine to create my
first 2 pools. I've been unable to use it since then. I have the same stack
trace errors.
Did you find a workaround for this issue?
-Rick
This message posted from opensolaris.org
> I checked - this system has a UFS root. When
> installed as snv_84 and then LU'd to snv_89, and when
> I fiddled with these packages from various other
> releases, it had the stacktrace instead of the ZFS
> admin GUI (or the well-known "smcwebserver restart"
> effect for the older packages).
>
>
A further update. With B90 and UFS as root partition, the ZFS administration
GUI worked fine. So I presented two additional disks and proceeded to create a
zpool. The creation of the pool worked fine however the ZFS administration
interface is now broken with the same error as in the original po
I checked - this system has a UFS root. When installed as snv_84 and then LU'd
to snv_89, and when I fiddled with these packages from various other releases,
it had the stacktrace instead of the ZFS admin GUI (or the well-known
"smcwebserver restart" effect for the older packages).
This system
Just tried SXCE B90 with UFS as root partition in VBOX 1.6 and it works fine,
so ZFS as the root partition might be the cause...
Cheers, JP
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail
I have the same problem here with https://localhost:6789 ZFS Administration
bombing out with the same error.
I am using SXCE B90 with ZFS as the root partition running in VBOX 1.6.
Any suggestions on next steps?
Cheers, JP
This message posted from opensolaris.org
___
No, I did not set that property; not now, not in previous releases.
Nice to see "secure by default" coming to the admin tools as well.
Waiting for SSH to become 127.0.0.1:22 sometime... just kidding ;)
Thanks for the tip!
Any ideas about the stacktrace? - it's still there instead of the web-GUI
On May 29, 2008, at 9:52 AM, Jim Klimov wrote:
I've installed SXDE (snv_89) and found that the web console only
listens on https://localhost:6789/ now, and the module for ZFS admin
doesn't work.
It works for out of the box without any special mojo. In order to get
the webconsole to list
I've installed SXDE (snv_89) and found that the web console only listens on
https://localhost:6789/ now, and the module for ZFS admin doesn't work.
When I open the link, the left frame lists a stacktrace (below) and the right
frame is plain empty. Any suggestions?
I tried substituting different
18 matches
Mail list logo
