As far as I know, no : it's not a known issue *yet* ;)
Could you please give us more details ?
What's the output of /opt/edg/etc/cron/edg-rgma-servlet-monitor (if
any...) ?
Is there something wrong in /opt/edg/var/log/edg-rgma-tools.log ?
Could you "echo" the "CMD" run by
/opt/edg/etc/cron/edg-rgma-servlet-monitor (line 69 for me) to be sure
the servlet status publishing script is called with the right parameters
(why isn't there any (damn) debug option in all those Grid scripts ???) ?
Thanks
Frederic
P.S : I CC JRA1 so that someone could maybe help us find what's wrong...
P.S : I tried to rebuild some kind of mail history to ease the problem
followup
Jiri Kosina a écrit :
>
> This seems like exactly the same problem I am having on both my sites.
> edg-rgma -c "latest select URI from Service" works, but my site is not
> listed in R-GMA browser.
>
> Even the output of the rgma check command seems the same.
>
> Is this some known issue?
>
> --
> Jiri Kosina
> Institute of Physics, Academy of sciences of the Czech Republic
> On Mon, 14 Feb 2005, Frederic Schaer wrote:
>
>> Hi,
>>
>> it seems you RGMA is "partially" working : it can see producers of
>> LcgRecords accounting records, and I guess the following command will
>> work :
>> edg-rgma -c "latest select URI from Service"
>>
>> ... doesn't it ?
>>
>> However, I don't see you Mon Box (accip41.physik.rwth-aachen.de) in
>> the RGMA Browser (http://lcgic01.gridpp.rl.ac.uk:8080/R-GMA/index.html).
>>
>> It seems nothing is publishing your servlets status into RGMA...
>> could you check you have something like the two following lines in
>> your MON Crontab (taken from an lCG 2.2 MON node)?
>> */2 * * * * /opt/edg/etc/cron/edg-rgma-service-status-monitor >>
>> /opt/edg/var/log/edg-rgma-tools.log 2>&1
>> */2 * * * * /bin/rm -f /tmp/rgma-restart > /dev/null 2>&1 ;
>> /opt/edg/etc/cron/edg-rgma-servlet-monitor >>
>> /opt/edg/var/log/edg-rgma-tools.log 2>&1
>>
>> The servlet-monitor calls
>> $EDG_LOCATION/libexec/edg-rgma-servlet-status to publish servlets
>> information. Please note this last script used in the LCG 2.2 version
>> was using a "sitename" system call, which in some cases returned the
>> short name and which has been replaced (or should have been) with a
>> "sitename -f" call (line 699).
>>
>>---------------------------------------------------------------------------------------------------------
>>
>>>> PROBLEM DESCRIPTION <<
>>
>>---------------------------------------------------------------------------------------------------------
>>
>>Andreas Nowack a écrit :
>>
>>
>> Hello,
>>
>>it seems to me that we still have some problems with R-GMA. But I cannot
>>locate the source of the problem:
>>
>># ./edg-rgma-check
>>[...]
>>Checking for site RGMA in Service and Service Status Tables...
>>R-GMA.ConsumerService: Failed
>>R-GMA.StreamProducerService: Failed
>>R-GMA.ArchiverService: Failed
>>R-GMA.CanonicalProducerService: Failed
>>R-GMA.DBProducerService: Failed
>>R-GMA.LatestProducerService: Failed
>>[...]
>>
>>
>>Someone suggested some time ago to check the Flexible Archiver. This is what I
>>get:
>># edg-rgma
>>
>>Welcome to the R-GMA virtual database for Virtual Organisations.
>>You are connected via the
>>http://lcgic01.gridpp.rl.ac.uk:8080/R-GMA/RegistryServlet R-GMA registry
>>server.
>>Type "help" for a list of commands.
>>
>>rgma> show producers of LcgRecords;
>>Continuous:
>>http://goc01.grid-support.ac.uk:8080/R-GMA/StreamProducerServlet 623512467
>>No History:
>>Latest:
>>http://goc01.grid-support.ac.uk:8080/R-GMA/LatestProducerServlet 1459734926
>>rgma>
>>
>>Could anybody help us?
>>
>>
>>
|