Shireesh, I have attached a gluster volume set help-xml from one of the backend servers. I replicated this error a few times so this particular test only has one backend server (running 3.3beta2) and the front-end server. Also attached is the Gluster Management Gateway log file. The screenshot is redundant as it contains the exact same error message that is in glustermg.log. Just search for "Error during unmarshalling string". Note: There are some unrelated error messages at the top of the glustermg.log file. I had forgotten to set $JAVA_HOME. Thanks again for your assistance. Peter -----Original Message----- From: Shireesh Anjal [mailto:sanjal at redhat.com] Sent: Friday, March 02, 2012 12:44 AM To: Scudamore, Peter Cc: gluster-users at gluster.org Subject: Re: Gluster Management Console Hi Peter, Can you please send the following details? - Output of "gluster volume set help-xml" from one of the backend servers. I'm assuming that all backend servers are running exactly same version of GlusterFS (3.3beta2) - The Gluster Management Gateway log file (/var/log/glustermg/glustermg.log) - Screenshot of the error dialog you see on the UI -- Regards, Shireesh On Thursday 01 March 2012 11:20 PM, Scudamore, Peter wrote: > > Hi, > > I am trying to set up the Gluster Management Console (backend servers > - centos 6, glusterfs 3.3beta2, management gateway ? centos 6). I can > launch the java app and make it through the password changing screen. > Then I choose ?register? and input the cluster name and the IP of one > of the backend servers. > > I made it through the part where I had to set the root password on the > backend server to syst3m in order for the management gateway to set up > password-less authentication. > > Then a pop-up windows shows ?sync-ing servers?. This goes away and I > am left with a huge error message. The first part says [500][Fetching > volume options info failed! [Error during unmashalling string? > > The rest of the error window looks to contain a ?gluster volume set > help-xml? from the backend server. I performed this command on the > backend server to verify that the XML is returning properly and I am > not getting the ?chopped-off-xml-issue? reported by other users. > > Please advise. > > Thanks, > > Peter > > *Peter Scudamore* > > *CCNP, CCDP, MCSE, SCSA* > > *PGi, Senior Systems Engineer* > > Office: 719.457.2791 > > Fax: 877.573.6350 > > Globalmeet? room: https://premiere.globalmeet.com/Scudamore > > iMeet? room: https://www.imeet.com/PeterScudamore > <https://imeet.com/PeterScudamore> 17198670487x973275# > > Description: cid:image001.jpg at 01CBC38E.78122AE0 <http://www.pgi.com/> > > Follow us cid:image002.jpg at 01CBC3A1.6343A680 > <http://www.facebook.com/#%21/PgiFans>cid:image003.jpg at 01CBC3A1.6343A680 > <http://twitter.com/PGiMeetTweet>cid:image004.jpg at 01CBC3A1.6343A680 > <http://www.youtube.com/user/PGiPremiereGlobal>cid:image005.jpg at 01CBC3A1.6343A680 > <http://blog.pgi.com/> > > > > This body part will be downloaded on demand. -------------- next part -------------- A non-text attachment was scrubbed... Name: glustermg.log Type: application/octet-stream Size: 1368574 bytes Desc: glustermg.log URL: <http://gluster.org/pipermail/gluster-users/attachments/20120302/7bf2aaf7/attachment-0001.obj> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: gluster-volume-set-help-xml.txt URL: <http://gluster.org/pipermail/gluster-users/attachments/20120302/7bf2aaf7/attachment-0001.txt>
