Debugging: Error messages and diagnosis

  • Error: during installation
    configure: error: Cannot locate qstat
    Error finding pbs tools
    loading cache ./config.cache
    checking for qstat... no
    ERROR: Command failed

    This is not a fatal error. You do not have PBS installed on your machine, so the PBS setup packages exited. Proceed with your configuration.

  • Error: during installation
    running /home/bacon/pkgs/gt3-beta/setup/globus/setup-mjs-fork...
    Can't open perl script "/home/bacon/pkgs/gt3-beta/etc/setup-mjs.pl": No such file or directory
    ERROR: Command failed
    Can't open perl script "/home/bacon/pkgs/gt3-beta/etc/setup-mmjfs.pl": No such file or directory

    The ManagedJobService failed to build. Check your install.log to see if core and mjs built.

  • Error: during installation
    /sandbox/gose/binary-build/side_tools/BUILD/globus_openssl-0.15/crypto/bio/b_print.c:234:
    undefined reference to `__ctype_b'
    /usr/local/globus/gt3-beta/lib/libcrypto_gcc32dbg.a(b_print.o)(.text+0x29a): /sandbox/gose/binary-build/side_tools/BUILD/globus_openssl-0.15/crypto/bio/b_print.c:252:
    more undefined references to `__ctype_b' follow
    collect2: ld returned 1 exit status
    make[1]: *** [globus-grim] Error 1
    make[1]: Leaving directory
    `/usr/local/globus/gt3-beta-installer/BUILD/globus_grim-0.1'
    make: *** [all-recursive] Error 1

    This is an incompatibility between the glibc used to create GT2 linux binary bundles and the glibc shipped with Redhat 9.0. It only affects building static binaries, like globus-grim. The workaround is to install from the all-source bundles on RH 9.0.

  • Error: during installation
    /usr//bin/ld: cannot find -ly collect2: ld returned 1 exit status make[1]: *** [soapcpp2] Error 1 make[1]: Leaving directory `/home/globus/gt3-beta-installer/BUILD/globus_gsoap_soapcpp2-0.2' make: *** [all-recursive] Error 1

    YACC or bison is reuquired to build cbindings from source. It appears that your system does not come with it installed. You may download a copy from the Bison Homepage.

  • Error: during startContainer
    [06/12/2003 11:56:15:178 ] org.globus.ogsa.handlers.container.ContainerHandlerHelper [runHandler:75] ERROR: java.lang.Exception: grim setuid program failed. Not running as a setuid program. The user must simply use their own proxy.

    bin/globus-grim is not setuid. Make sure it is owned by the same user who owns the hostcert, and that it is setuid. If your hostcert is owned by root, running bin/setperms.sh will do this for you.

  • Error: during startContainer
    [java] [06/06/2003 10:23:28:006 ] org.globus.ogsa.handlers.container.ContainerHandlerHelper [runHandler:75] ERROR: java.lang.Exception: grim setuid program failed.

    Either root did not run setperms.sh, or you do not have a hostcert.pem and hostkey.pem in /etc/grid-security. To debug, try running "bin/globus-grim -out /tmp/grim_test" and read the error messages.

  • Error: during startContainer
    [java] [06/06/2003 10:50:41:653 ] org.globus.ogsa.impl.base.providers.servicedata.impl.HostScriptProvider [run:721] ERROR: Execution error: Fatal Error: URI=null Line=1: Premature end of file. while processing libexec/grid-hostinfo-mem-linux

    You ran startContainer without setting GLOBUS_LOCATION. You can debug after setting GLOBUS_LOCATION by running libexec/grid-hostinfo-mem-linux by hand.

For support, please see the Support Page [UPDATE: Version 3.0 is no longer supported. Please upgrade to 3.2 or 4.0.]

bacon@mcs.anl.gov
Last modified: Thu Jun 12 11:59:19 CDT 2003