Hi,
Thank You for the response. This looks like the problem is not in logs
(they get filled by daemon regardless of the error). I get this not very
meaningful message when I try to start RGMA-server:
/etc/init.d/edg-rgma-servicetool start --verbose
Using following settings
LOG4J_JAR: /usr/share/java/log4j.jar
RGMA_HOME: /opt/edg
RGMA_USER: rgma
Debug logging file: /opt/edg/var/log/rgma-servicetool.log
Process lock file: /var/lock/subsys/edg-rgma-servicetool
Starting edg-rgma-servicetool: log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: /opt/edg/var/log/rgma-servicetool.log
(Permission denied)
at java.io.FileOutputStream.openAppend(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:272)
at
org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:156)
at
org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151)
at
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:247)
at
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:123)
at
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:87)
at
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:645)
at
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:603)
at
org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:500)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:406)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:432)
at
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:460)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:145)
at org.apache.log4j.Logger.getLogger(Logger.java:85)
at org.glite.rgma.servicetool.daemon.StatusDaemon.<clinit>(Unknown
Source)
Couldn't connect to R-GMA server
[FAILED]
For more details check /opt/edg/var/log/rgma-servicetool.log
cron will attempt a restart within the next hour
to disable restart run edg-rgma-servicetool stop
Any ideas,
Piotr
--
Piotr Siwczak <[log in to unmask]>
System Administrator
Poznan Supercomputing and Networking Center
Supercomputing Department
(www.eu-egee.org <[log in to unmask]>)
--
On Fri, 3 Jun 2005, Steve Fisher wrote:
> On Fri, Jun 03, 2005 at 11:06:10AM +0100, Rob Byrom wrote:
>> Hi Piotr,
>>
>> The error you see is fairly harmless, it just means log4j is unable to
>> append any logging statements to the rgma-server.log file when rgma is
>> running (so the worst that will happen is logging will be disabled).
>>
>> Normally the log file is created by the log4j system (via the tomcat
>> user), check the directory exists and file permissions are set to allow
>> r/w for tomcat.
>>
>> Rob
>
> You may not have received Rob's reply
>
> Steve
>
>>
>> On Fri, 2005-06-03 at 11:01, Burke, S (Stephen) wrote:
>>> FYI
>>>
>>> -----Original Message-----
>>> From: LHC Computer Grid - Rollout
>>> [mailto:[log in to unmask]] On Behalf Of Piotr Siwczak
>>> Sent: 03 June 2005 10:57
>>> To: [log in to unmask]
>>> Subject: [LCG-ROLLOUT] RGMA log4j problem - LCG240(itanium release)
>>>
>>>
>>> Hi,
>>>
>>> I am clueless about RGMA setup at my site. I keep getting the following
>>> error while initializing RGMA with YAIM or by hand:
>>>
>>
>>
>> _______________________________________________
>> JRA1-UK mailing list
>> [log in to unmask]
>> http://www.physics.gla.ac.uk/mailman/listinfo/jra1-uk
>
|