Ok,

We'll need to add that to the instructions or to the Troubleshooting Guide.

Stefan

________________________________________
From: Moonshot community list [[log in to unmask]] on behalf of Mark Cairney [[log in to unmask]]
Sent: Wednesday, July 17, 2013 6:58 PM
To: [log in to unmask]
Subject: Re: failure at step 5.2 of CentOS setup

Hi,

I think I encountered this too- running the following command appeared
to fix it:

  dbus-uuidgen > /var/lib/dbus/machine-id


On 17/07/2013 16:30, Rhys Smith wrote:
> Worked fine for me - and I used the minimal install.
>
> Referring to your previous email - did you reboot after changing the selinux mode? Not sure if it's still the case, but you definitely used to have to reboot for it to take effect.
>
> Rhys.
> --
> Dr Rhys Smith
> Identity, Access, and Middleware Specialist
> Cardiff University & Janet - the UK's research and education network
>
> email: [log in to unmask] / [log in to unmask]
> GPG: 0xDE2F024C
>
> On 17 Jul 2013, at 16:25, Alan Buxey <[log in to unmask]>
>   wrote:
>
>> Yes all done as root at this time.  Have a test user which also fails (Both accounts have the .gss_eap_id etc). Wonder if there's a few components that a minimum install misses..
>>
>> alan
>>
>>
>>
>> -------- Original message --------
>> From: Stefan Paetow <[log in to unmask]>
>> Date: 17/07/2013 15:33 (GMT+00:00)
>> To: [log in to unmask]
>> Subject: Re: failure at step 5.2 of CentOS setup
>>
>>
>> Hi Alan,
>>
>> Are you running gss-server as root? If not, please try that...
>>
>> Stefan
>>
>>> -----Original Message-----
>>> From: Moonshot community list [mailto:MOONSHOT-
>>> [log in to unmask]] On Behalf Of Alan Buxey
>>> Sent: 17 July 2013 15:11
>>> To: [log in to unmask]
>>> Subject: failure at step 5.2 of CentOS setup
>>>
>>> Hi,
>>>
>>> in parallel to more technical approach I am installing based on current
>>> instructions (to provide feedback, ensure accuracy etc)
>>>
>>> following this guide:
>>>
>>> at step 5.2, after running gss-server I try testing with gss-client and
>>> get
>>>
>>> # gss-client -mech "{1.3.6.1.5.5.15.1.1.18 }" 127.0.0.1 host@localhost
>>> bar process 14789: D-Bus library appears to be incorrectly set up;
>>> failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id":
>>> No such file or directory See the manual page for dbus-uuidgen to
>>> correct this issue.
>>>    D-Bus not built with -rdynamic so unable to print a backtrace reading
>>> token flags: 0 bytes read Aborted
>>>
>>>
>>> (get the same error with the spegno approach too)
>>>
>>> all of this is from RPM (EPEL and moonshot repo etc).
>>>
>>> where did it all go wrong?  ;-)
>>>
>>> alan
>> --
>> This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
>> Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
>> Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
>> Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom


--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

-- 
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom