Hi Torsten,
On 22-01-10 11:01, Torsten Harenberg wrote:
> Hi all,
>
> has anybody else tried that?
>
> At least for our CE it seems not to work:
>
> [root@grid-ce5 maui]# strings /usr/sbin/maui | grep '^[0-9][0-9][0-9][0-9][0-9][0-9]$'
> 333333
> [root@grid-ce5 maui]# cat /opt/glite/etc/maui-key.txt
> 333333
Do you run the Maui server on the CE? If so, then I would assume that
your client and server are from the same build and you would not need
this trick. But if they are on different hosts (and use different
builds), it may be needed. At least for us it was the only way so far to
make client commands work from another host with a different Maui build.
Executing the string command on our batch server produces 3 lines of
output (instead of the one you got):
[root@stro ~]# strings /usr/sbin/maui | grep
'^[0-9][0-9][0-9][0-9][0-9][0-9]$'
230774
333333
333333
I took the first line and put that in the maui key file.
Cheers,
Ronald
> [root@grid-ce5 maui]# diagnose -g --keyfile=/opt/glite/etc/maui-key.txt
> ERROR: lost connection to server
> ERROR: cannot request service (status)
> [root@grid-ce5 maui]# tail -2 /var/log/maui.log
> 01/22 11:00:23 ALERT: checksum does not match (af96c2c6796d75da:986304f2ab02b2eb) request 'TS=1264154423 AUTH=root DT=CMD=diagnose AUTH=root ARG=8 0 ALL [NONE]
>
>
> Cheers,
>
> Torsten
>
>
> Am 21.01.2010 um 13:32 schrieb Ronald Starink:
>
>> Hi Dug,
>>
>> Thanks a lot for this hack, it fixes our problem!
>>
>> Cheers,
>> Ronald
>>
>>
>> On 21-01-10 12:26, Douglas McNab wrote:
>>> Hi Ronald,
>>>
>>> I can't take credit for this one, that goes to Graeme Stewart.
>>>
>>> You can find out the key by running strings on the maui binary:
>>> strings /usr/sbin/maui | grep '^[0-9][0-9][0-9][0-9][0-9][0-9]$'
>>> 230774
>>>
>>> and use it like this:
>>>
>>> create a file with the contents of your key: /opt/glite/etc/maui-key.txt
>>> edit this: /opt/lcg/libexec/vomaxjobs-maui
>>> and add the following to the diagnose line:
>>> -keyfile=/opt/glite/etc/maui-key.txt
>>>
>>> i.e.
>>> ----
>>> else:
>>> cmd = 'diagnose -g --keyfile=/opt/glite/etc/maui-key.txt'
>>> ----
>>>
>>> Regards,
>>>
>>> Dug
>>>
>>>
>>> 2010/1/21 Ronald Starink <[log in to unmask]>
>>>
>>>> Hi Ramon,
>>>>
>>>> Thanks for your response. I tried that already, but unfortunately,
>>>> without success. The Maui server still logs an error about the failing
>>>> checksum. The link below also does not give much hope about getting Maui
>>>> security settings to work:
>>>> http://archive.netbsd.se/?ml=cluster-maui-users&a=2006-09&t=3467631
>>>>
>>>> Ronald
>>>>
>>>>
>>>> On 21-01-10 11:17, Ramon Bastiaans wrote:
>>>>> You could try experimenting with a peer specific key as described here:
>>>>> * http://www.clusterresources.com/products/maui/docs/a.esecurity.shtml
>>>>>
>>>>> Although I've never used or tested that myself (since we build our own
>>>>> maui), so I have no clue how (well) that works.
>>>>>
>>>>>
>>>>> Kind regards,
>>>>> - Ramon.
>>>>>
>>>>> On 01/20/2010 04:48 PM, Ronald Starink wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Since upgrading our batch system server to EL5 x86-64 and upgrading all
>>>>>> Maui packages to the latest versions from gLite, the Maui clients at the
>>>>>> lcg-CEs cannot connect to the Maui server anymore:
>>>>>>
>>>>>> [root@tbn14 ~]# diagnose -g
>>>>>> ERROR: lost connection to server
>>>>>> ERROR: cannot request service (status)
>>>>>>
>>>>>> The Maui log at the server then shows:
>>>>>> 01/20 16:47:08 ALERT: checksum does not match
>>>>>> (70b0309b6732b3ed:2c66242ebb0cd620) request 'TS=1264002428 AUTH=root
>>>>>> DT=CMD=diagnose AUTH=root ARG=8 0 ALL tbn04.nikhef.nl
>>>>>>
>>>>>> This results in publishing '444444' waiting jobs in the information
>>>>>> system :-(
>>>>>>
>>>>>> The lcg-CE uses the following package versions:
>>>>>> maui-client-3.2.6p21-snap.1224706197.2.slc4
>>>>>> maui-3.2.6p21-snap.1224706197.2.slc4
>>>>>>
>>>>>> The batch server uses these versions:
>>>>>> maui-client-3.2.6p21-snap.1234905291.5.el5
>>>>>> maui-3.2.6p21-snap.1234905291.5.el5
>>>>>> maui-server-3.2.6p21-snap.1234905291.5.el5
>>>>>>
>>>>>> I know that at a key can be provided when compiling Maui. That key has
>>>>>> to be used for building the client and server versions that need to work
>>>>>> together. This problem makes me wonder if the gLite 3.1 and 3.2 versions
>>>>>> were built with the same key. Does anyone else successfully use the
>>>>>> above combination of client and server versions of Maui?
>>>>>>
>>>>>> Thanks,
>>>>>> Ronald
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>
> --
> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
> <> <>
> <> Dr. Torsten Harenberg [log in to unmask] <>
> <> Bergische Universitaet <>
> <> FB C - Physik Tel.: +49 (0)202 439-3521 <>
> <> Gaussstr. 20 Fax : +49 (0)202 439-2811 <>
> <> 42097 Wuppertal <>
> <> <>
> <><><><><><><>< Of course it runs NetBSD http://www.netbsd.org ><>
>
|