Bugzilla – Bug 5624
LIGO: globus-rls-admin and globus-rls-cli tools do not exit properly on Debian 4.0 ONLY (Workaround)
Last modified: 2008-05-28 19:18:13
You need to log in before you can comment on or make changes to this bug.
The system has these details: datarobot@golf:~$ uname -a Linux golf 2.6.18-5-686 #1 SMP Wed Sep 26 17:54:59 UTC 2007 i686 GNU/Linux datarobot@golf:~$ cat /etc/issue Debian GNU/Linux 4.0 \n \l datarobot@golf:~$ gcc --version gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. The version of RLS used is that from the GT 4.0.5 source tarball. That is, RLS and the globus-rls-admin tool were built from source on the machine using the gcc shown above. When the globus-rls-admin command is run it hangs after printing out the expected output. For example: datarobot@golf:~$ globus-rls-admin -S rls://localhost Version: 4.3 Uptime: 168:38:10 LRC stats update method: lfnlist update method: bloomfilter lfnlist update interval: 86400 bloomfilter update interval: 900 numlfn: 0 numpfn: 0 nummap: 0 RLI stats updated via bloomfilters At this point the command hangs and control is not returned back to the shell. Neither Ctrl+c nor Ctrl+z interrupt the process and return command to the shell. This behavior is not specific to the '-S' flag. It also happens when using the '-p' flag to ping the server. It may happen with other options too but we have not tested all of them. I will run the command under strace and attach the output to the bug report.
The output of running the hanging command under strace is at http://www.lsc-group.phys.uwm.edu/lscdatagrid/downloads/ldr_software/strace.out
Can you point g-r-a at another server on another host and see what happens? Preferably, this would be a server on a host you're not having problems with. It may also be worth testing with an older server if you have one running.
On the Debian 4 system golf.astro.cf.ac.uk I ran globus-rls-admin -S rls://nemo-dataserver.phys.uwm.edu and saw the same behavior. The expected output is written to the terminal but then control is not returned to the shell. The RLS running on the system nemo-dataserver.phys.uwm.edu reports version 4.2.
The same problem occurred with a USC user using a Debbian 4 release: Linux version 2.6.18-4-686 (Debian 2.6.18.dfsg.1-12etch2) (dannf@debian.org) (gc c version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Wed May 9 23:03: 12 UTC 2007 I have tried out the g-r-a and g-r-c clients on some Debbian 3.1 boxes and it works fine. No probems on RH8, RH9, FC6, and Solaris (SunOS 5.9) that I can tell.
I ran globus-rls-admin under gdb and saw that the third (3rd) time after executing the command globus_module_deactivate(modules[i]); is when the client hangs. So it appears that it is hanging when deactivating the GLOBUS_RLS_CLIENT_MODULE.
I commented out the code in admin.c that loops over globus_module_deactivate and forced a rebuild and now the client does not hang. I also tried changing to using globus_module_deactivate_all() but that did not help and the client continued to hang.
I see that the deactivation loop counts down/backwards, so the client is actually hanging during the GLOBUS_COMMON_MODULE deactivation.
So this is bug 5481.
Since there is a Debian 4.0 workaround, I'm going to change severity to normal. Hopefully that seems reasonable, given the circumstances.
I'm going to close this since the "fix" is a workaround for a Debian 4.0 bug that is out of our control.
After reopening this bug I'm closing it with FIXED status because the core libs have fixed the bug (see bug 5481).