i thought i'd let you know that we were finally able to fix all of our
problems. We got rid of it by using vdt. Now we're using gt-4.0.3 but i
have to say that we were able to make everything work again in more or
less 3 days. it took me at least 3 days to convince gt-4.0.4 to compile
completely ;) if you are really having a hard time making things work
you might be better off to use vdt as it comes preconfigured and working
almost out of the box!
Thanks for trying to figure out what was wrong in my case Martin!
Regards,
Christoph
Martin Feller wrote:
> It's hard to analyze what happened. I personally would cleanup
> $GLOBUS_LOCATION, reinstall it and check if things work then.
> Also: do you run the container as root? I saw that
> container-log4j.properties belongs to root.
> If so: it's better to install and run it as a non-privileged user.
> Martin
>
>
>> Hi Martin!
>>
>> Thanks for your patience!
>>
>> *Well this is a Athlon MP 2000+ with Gentoo Linux SMP-Kernel.
>> *The JVM we are using at the moment is: java version "1.5.0_11"
>> *Yeah we upgraded from 4.0.1 to 4.0.4 (this was my first
>> globus-installation so i think something might've gone wrong) but as
>> i mentioned in my first mail we are quite sure that it DID work (even
>> globusrun-ws) before. The only thing we did after we finished off the
>> installation was a gpt-postinstall again (later on because we
>> remarked that we ran gpt-postinstall as root during the installation)
>> *Contents of $GLOBUS_LOCATION/container-log4j.properties:
>>
>> # Set root category priority to WARN and its only appender to A1.
>>
>> log4j.rootCategory=INFO, A1
>>
>> # A1 is set to be a ConsoleAppender.
>>
>> log4j.appender.A1=org.apache.log4j.ConsoleAppender
>>
>> # A1 uses PatternLayout.
>> log4j.appender.A1.layout=org.apache.log4j.PatternLayout
>> log4j.appender.A1.layout.ConversionPattern=%d{ISO8601} %-5p %c{2}
>> [%t,%M:%L] %m%n
>>
>> # Display any warnings generated by our code
>> #log4j.category.org.globus=DEBUG
>> log4j.category.org.globus=INFO
>> # Comment out the line below if you want to log every authorization
>> # decision the container makes.
>> log4j.category.org.globus.wsrf.impl.security.authorization.ServiceAuthorizationChain=WARN
>>
>>
>> # Enable SOAP Message Logging
>> # log4j.category.org.globus.wsrf.handlers.MessageLoggingHandler=DEBUG
>>
>> # Uncomment the following line to enable MDS debugging
>> # log4j.category.org.globus.mds=DEBUG
>>
>> # Uncomment the following line to enable GRAM debugging
>> log4j.category.org.globus.exec=DEBUG
>>
>> # Uncomment the following line to enable RFT debugging
>> log4j.category.org.globus.transfer=DEBUG
>> # Uncomment the following line to enable GridFTP debugging
>> log4j.category.org.globus.ftp=DEBUG
>>
>> i commented out the line log4j.category.org.globus=DEBUG again after
>> i got the log-file i sent you because it created a really BIG log
>> after just about 5 mins of running.
>>
>> *ls -lah /opt/globus/container-log4j.properties
>> -rw-r--r-- 1 root root 1.2K Jun 13 16:35
>> /opt/globus/container-log4j.properties
>>
>> *i followed the Globus administration guide. I forgot to edit some
>> configuration-files but in the end everything was working again.
>>
>> Christoph
>>
>>
>> [EMAIL PROTECTED] wrote:
>>> Ups, something must have gone wrong with my email:
>>> The first entry in the log you sent indicates that something
>>> goes wrong with log4j. The whole logfile is strange with
>>> all these hex loggings. That's why i can't say what happened.
>>>
>>> What i wanted do know is:
>>>
>>> * What machine is that?
>>> * What JVM are you using?
>>> * GT is 4.0.4, right?
>>> * What does $GLOBUS_LOCATION/container-log4j.properties look like?
>>> * How are the permissions on that file and who is the owner
>>> * Did you follow any installation guide
>>>
>>> Martin
>>>
>>>
>>>> Hi Christoph,
>>>>
>>>> something goes really wrong with your installation.
>>>> The logfile doesn't look like it should at all. I never
>>>> saw such a logfile!
>>>> Since all jobs hang, it's not an RFT issue.
>>>>
>>>> The first entry in the logfile:
>>>> container.log
>>>>
>>>>
>>>
>>>
>>
