I already did some changes by hand and locally everthing looks fine but now I got a mail telling me of some problem:
globusrun-ws -submit -F https://<new_hostname>:8443/wsrf/services/ManagedJobFactoryService -s -c /bin/echo ok Delegating user credentials...Done. Submitting job...Done. Job ID: uuid:6dd1aa8c-bde3-11dc-ad3d-0018fe799cae Termination time: 01/09/2008 12:15 GMT Current job state: Active globusrun-ws: ignoring error while streaming gsiftp://<old_hostname>:2811/home/user/6dd1aa8c-bde3-11dc-ad3d-0018fe799cae.0.stdout globus_xio: Unable to connect to <old_hostname>:2811 globus_xio: globus_libc_getaddrinfo failed. globus_common: Name or service not known globusrun-ws: ignoring error while streaming gsiftp://<old_hostname>:2811/home/user/6dd1aa8c-bde3-11dc-ad3d-0018fe799cae.0.stderr globus_xio: Unable to connect to <old_hostname>:2811 globus_xio: globus_libc_getaddrinfo failed. globus_common: Name or service not known Current job state: CleanUp-Hold What could I have missed? Would that forced postinstall give me any trouble besides the RFT database? Matthias > /etc/grid-security/hostcert.pem and /etc/grid-security/hostkey.pem. > > Running $GLOBUS_LOCATION/sbin/gpt-postinstall -force should re- > generate any files that have the hostname configured into them, > though you may then have to setup the RFT database/password again. > > > Charles > > On Jan 8, 2008, at 8:28 AM, [EMAIL PROTECTED] wrote: > >> What files do I have to change if the hostname of the machine >> running the >> globus container changes? >> >> Matthias >> > >
