Re: Ganymede client hangs

[Lewis Muhlenkamp <lewism@tt.comm.mot.com>]

Jonathan,

I did everything you said below.  Everything now appears to work just
fine.  I think the problem with the "Edit Schema" pull down was the
fact they were originally done under Java 1.2.  Once I did a "make clean"
followed by the rest, I could now go to the exact same schema item and
do a pull down.  There were no errors this time.

There were two things I did have to do in order to rebuild everything.
The first was add "." to my PATH.  I have been working with the
Ganymede stuff as root.  For security reasons, I do not have "." in my
PATH.  The make complained about a lot of things when "." was not there.
You might want to do "./build" and ". ./config.sh" instead of just the
"build" and "config.sh" in the Makefile and build scripts.  You could
also put in the README that "." needs to be in the PATH if the user
wishes to rebuild everything.

The other item was I had to set CLASSPATH in order to pick up the swing
classes.  Again, you might want to mention that in the README, or have
it be part of the Makefile.  I did the following to define CLASSPATH:

  # export CLASSPATH=/opt/swing/swingall.jar:.


Once I did that, everything got made.

Thank you for all of your help.  I am now ready to begin playing with
Ganymede.  I'll let you know of anything else I find.

Again, thanks.


Jonathan Abbey wrote:
> 
> | Hello,
> |
> | I downloaded ganymede 0.98 a few hours back and started playing with it.
> | First, I am doing this on a HP-UX 10.20 machine (model 9000/777).  I am
> | doing it on a HP-UX machine because that is where our NIS master is
> | currently located.
> |
> | I downloaded the swing 1.1 software from Sun.  I already had JDK 1.1.7
> | from HP installed.  PERL 5.005_02 is also installed.
> |
> | The installServer and installClient both ran just fine.  I used the
> | gash option as the default schema, even though I have not used GASH
> | before.  I did not load in anything from my NIS maps.  I wanted to play
> | around with an empty system first.
> |
> | Also, I did not recompile anything.  I just ran the configure script
> | and the two install scripts.  I did not go into any directory and do
> | a make.
> |
> | Running "/opt/ganymede/bin/runServer" brings up the server just fine.
> | It spews a lot of messages to the screen, but the server comes up.
> | No errors are reported.
> 
> Everything sounds good so far.  You are correct that you don't need to load
> any data into Ganymede in order to play with it.  In fact, playing with the
> gash(arl) schema on an empty database is probably the best way to get an idea
> of the possibilities of the system, although you may need to do a bit of work
> to bootstrap things properly.  For instance, the user object may require
> that you specify a home group for the user, forcing you to create a group
> before you can create a user, etc.
> 
> | Running "/opt/ganyclient/bin/ganymedeAdmin" works just fine too.  It
> | brings up the login screen.  I can successfully log in as supergash.
> | It brings up the admin window and I can do everything I think I am
> | suppose to be able to do.
> |
> | I did notice that on some of the "Edit Schema" items, I get a lot of
> | messages in xterm in which I invoked ganymedeAdmin.  It seems to happen
> | when the pull-down menu only contains zero or one element.  For example,
> | the error I get when I try to pull down the "Field Type" in the
> | "Categories->Admin-Level Objects->Permissions->Admin Persona->Email Address"
> | schema window is as follows:
> |
> |  Exception occurred during event dispatching:
> |  java.lang.NullPointerException
> |      at arlut.csd.ganymede.BaseFieldEditor.setValuePerformed(Compiled Code)
> |      at arlut.csd.JDataComponent.JnumberField.sendCallback\
> |       (JnumberField.java:436)
> | [...]
> 
> Hm, I'll have to try to look at this.  Changing field type is something
> that has always worked, though.. it's kind of a critical error to have gone
> undetected.
> 
> It might be helpful if you could try doing this sequence while running the
> adminConsole in non-JIT mode.
> 
> Also, it can be helpful sometimes to run the server with
> 
> debug=debug.log
> 
> added to the end of the
> 
> $JAVA -ms32m -mx128m arlut.csd.ganymede.Ganymede properties=ganymede.properties
> 
> line.  This will force the server to log all RMI calls made to it by
> the client and console, as well as any server-side exceptions that are thrown
> in response to a client-initiated RMI call.
> 
> | The real problem though is when I try to bring up ganymede itself.  I get
> | the login screen.  I can enter supergash and the password.  The server
> | log shows supergash logging in.  The xterm in which I invoked ganymede
> | though, shows the following:
> |
> |   # bin/ganymede
> |   Running Ganymede Client
> |   Exception occurred during event dispatching:
> |   java.lang.RuntimeException: caught nullptr trying to load image \
> |    inactivate.gif, url = null
> |       at arlut.csd.Util.PackageResources.getImageResource(Compiled Code)
> |       at arlut.csd.ganymede.client.gclient.<init>(gclient.java:614)
> 
> Right, you've found a bug.  That image is not actually used in the
> client, and the inactivate.gif file is not actually present in the jar file,
> so HP's JVM is reasonable in complaining about this.  Interestingly enough,
> neither Sun's Solaris nor Win32 JDK's (1.1.7 or 1.2) do complain about this,
> though they arguably should.  Perhaps they would throw the exception if we
> ever actually attempted to render the image.
> 
> I've commented out the line that causes the problem for Ganymede 0.99.  You
> should be able to fix this yourself by editing src/client/gclient.java
> and looking for a line
> 
>   inactivateIcon = PackageResources.getImageResource(this, "inactivate.gif", \\
>                                                      getClass());
> 
> and deleting or commenting it out, then
> 
> cd src
> make
> make jars
> 
> and re-do your installServer and installClient to put the new versions of
> the jars in place.
> 
> Note that I compiled the jars using a 1.2 compiler.. the RMI interface
> classes seem to slightly differ between 1.1 and 1.2, so you will probably
> need to restart the server before being able to successfully connect with
> the new client jar.
> 
> | I cannot do anything after that.  I have to explicitly abort my session
> | by doing a ctl-c.  Even then, though, that session is still considered
> | logged in to the system.  I have to use the ganymedeAdmin function of
> | "Kill user" to remove that session.
> 
> Actually, the server should detect the client's death after a ten minute
> period and kill it off by itself, if you have the patience to wait for it.
> Killing it off manually amounts to the same thing, however, and causes no
> harm.
> 
> | When I noticed the message was regarding a GIF file, I took a dummy GIF
> | from apache (unknown.gif) and copied it into the /opt/ganymede/docs/gif
> | directory and called it inactivate.gif.  I also copied this file to the
> | doc/customization and doc/permissions directories.  None of them made
> | any difference.
> 
> Good idea, but this image needs to be in the jar file where the Ganymede
> client reads its resources from, rather than in the doc directory.
> 
> You could add the image to src/classes/arlut/csd/ganymede/client and then
> do a 'make jars' to fix the problem as well, if you didn't want to try
> rebuilding the source tree.

-- 
----------------------------------------------------------------------------
| Lewis Muhlenkamp                   | Network Administrator               |
| Motorola, Inc.                     | phone: 847-538-4670                 |
| Mailstop: IL02/1055C               | fax: 847-538-4315                   |
| 1301 E. Algonquin Rd.              | email: lewism@tt.comm.mot.com       |
| Schaumburg, IL 60196               |                                     |
----------------------------------------------------------------------------

----------------------------------------------------------------------------
To make changes to your subscription to the ganymede mailing list, send
mail to majordomo@arlut.utexas.edu.

To unsubcribe, include the line

unsubscribe ganymede

in the body of your mail message

Visit the Ganymede web page at http://www.arlut.utexas.edu/gash2

----------------------------------------------------------------------------