Hi,
there is more to that:
On Thu, 4 Aug 2005, Cristina Aiftimiei wrote:
> Oliver KEEBLE wrote:
>> We have rebuilt the lcg-MON meta-package so it contains the gridice
>> server software. If you need to update a 2.6.0 MON;
>>
>> # apt-get update
>> # rpm -e --nodeps lcg-MON
>> # apt-get install lcg-MON
>>
> To configure the gridice-sensor/collector you still have to run:
> /opt/lcg/yaim/scripts/run_function <site-info.def> config_fmon_client.
>
> The function should be added in the node-info.def (MON_FUNCTIONS) in the next
> yaim release.
It also seemed to spawn globus-mds to publish the GridIce info, but did
not work:
Configuring config_fmon_client
...
Stopping Globus MDS for GridICE [ OK ]
Starting Globus MDS for GridICE (gcc32dbgpthr) [ OK ]
[root@grid154 examples]# /etc/init.d/globus-mds stop
Stopping Globus MDS [FAILED]
It was not running, of course. Trying to run globus-mds by hand first
revealed that mds was not configured at all in /etc/globus.conf. After
configuring it by hand, I now get this error message instead:
Starting Globus MDS
No schemalist script found for provider <edg>
(gcc32dbgpthr) [ OK ]
Of course, it does not start, but note [ OK ] again at the end. It is a
bit annoying that you get positive feedback for nothing...
After including both config_globus and config_gip for the MON type in
node-types.def, and reconfiguring again with yaim (and putting in the mds
part in /etc/globus.conf, as it had somehow been deleted again), I have a
runnig globus-mds! Too bad, the output is still a bit 'spartan':
version: 2
#
# filter: (objectclass=*)
# requesting: ALL
#
# local, grid
dn: Mds-Vo-name=local,o=grid
objectClass: GlobusStub
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
What should be installed/configured in order to make globus-mds publish
the GridIce
info?
Szabolcs
>
> Cristina
>
>> * bug #9856 overview: yaim 2.6 config_rgma_client configures for
>> insecure operation while config_rgma_server configures for secure
>>
>> This was a local issue and has been closed.
>>
>> * bug #9853 overview: R-GMA cron jobs not running in LCG-2.6
>>
>> Problem with a jar file actually being a .tar.gz - this is being addressed
>>
>> * bug #9817 overview: APEL_HOME missing
>>
>> We will fix this in the next yaim release. In the meantime, you can add
>> the following lines to /etc/cron.d/edg-rgma-apel;
>>
>> RGMA_HOME=/opt/glite
>> APEL_HOME=/opt/glite
>>
>> (replacing /opt/glite with your own path if necessary). You'll have to
>> untar that 'jar' file too to get things to work.
>>
>> Oliver.
>>
>> Oliver Keeble Information Technology Department
>> [log in to unmask] CERN
>> +41 22 76 72360 CH-1211 Geneva 23
>>
>>
>> Dimitris Zilaskos wrote:
>>
>>> Hello everyone ,
>>> I am encountering the following problems in installing LCG 2.6
>>>
>>> the RGMA cronjobs do not run. They need APEL_HOME but this is not
>>> defined anywhere. Even if it is manually defined to /opt/glite it does
>>> not run and returns the following :
>>> Tue Aug 2 20:05:24 UTC 2005: apel-publisher - Read-in configuration:
>>> [logenabled, j] [DBUsername=accounting,
>>> DBURL=jdbc:mysql://node008.grid.auth.gr:3306/accounting,
>>> DBPassword=****, site=GR-01-AUTH, republish=all]
>>> Tue Aug 2 20:05:24 UTC 2005: apel-publisher - ------ Starting the apel
>>> application ------
>>> Tue Aug 2 20:05:24 UTC 2005: apel-publisher - program aborted
>>> org.glite.apel.core.ApelException: Unable to setup a database
>>> connection: org.gjt.mm.mysql.Driver
>>> at org.glite.apel.core.db.MySQLImpl.<init>(MySQLImpl.java:93)
>>> at
>>> org.glite.apel.publisher.AccountManager.<init>(AccountManager.java:69)
>>> at
>>> org.glite.apel.publisher.ApelPublisher.runJoinProcessor(ApelPublisher.java:110)
>>> at org.glite.apel.publisher.ApelPublisher.run(ApelPublisher.java:68)
>>> at org.glite.apel.publisher.ApelPublisher.main(ApelPublisher.java:234)
>>>
>>> This is caused by mm-mysql.jar in /opt/glite/share/glite-apel-core/java
>>> which is a gziped tarball file and not a jar file , and contains
>>> mysql-connector-java-1.3.8-bin.jar , which is the new version for
>>> mm-mysql.jar If I copy mysql-connector-java-1.3.8-bin.jar over the yaim
>>> installed mm-mysql.jar the jobs run.
>>>
>>> Also it seems that yaim configures rgma clients for insecure operation
>>> but the server is configured for secure only
>>>
>>> About gridice , despite definined the monitor box as the gridice server
>>> , no gridice rpms are installed by yaim in it.
>>>
>>> Relevant bugs are
>>> https://savannah.cern.ch/bugs/?func=detailitem&item_id=9857
>>> https://savannah.cern.ch/bugs/?func=detailitem&item_id=9856
>>> https://savannah.cern.ch/bugs/?func=detailitem&item_id=9853
>>> https://savannah.cern.ch/bugs/?func=detailitem&item_id=9817
>>>
>>> Can anyone have a look at them ?
>>>
>>> Best regards ,
>>>
>>>
>>
>>
>
>
> --
> ---
> Cristina Aiftimiei - EGEE Project
> Ist. Naz. di Fisica Nucleare - Padova
> Address: via F. Marzolo, 8 - 35131 Padova - ITALY Email:
> [log in to unmask]
> Phone: +39-0498277005
> Mobile:+39-3460230488
>
|