[ovirt-devel] engine-setup fails on first attempt due to "Command '/bin/systemctl' failed to execute" then succeeds.

[Sandro Bonazzola]

Il 27/11/2014 00:12, Dan Kenigsberg ha scritto:
> (Poor mailing list, needs to duplicate so much logs to so many
> subscribers. Pastebin is so more efficient)

+1

> 
> On Wed, Nov 26, 2014 at 06:57:27AM -0500, Mooli Tayer wrote:
> 
>> 2014-11-26 12:17:45 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:936 execute-output: ('/bin/systemctl', 'stop', 'nfs-server.service') stderr:
>>
>>
>> 2014-11-26 12:17:45 DEBUG otopi.plugins.otopi.services.systemd systemd.state:134 starting service nfs-server
>> 2014-11-26 12:17:45 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:823 execute: ('/bin/systemctl', 'start', 'nfs-server.service'), executable='None', cwd='None', env=None
>> 2014-11-26 12:17:45 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:873 execute-result: ('/bin/systemctl', 'start', 'nfs-server.service'), rc=1
>> 2014-11-26 12:17:45 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:931 execute-output: ('/bin/systemctl', 'start', 'nfs-server.service') stdout:
>>
>>
>> 2014-11-26 12:17:45 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:936 execute-output: ('/bin/systemctl', 'start', 'nfs-server.service') stderr:
>> Job for nfs-server.service failed. See 'systemctl status nfs-server.service' and 'journalctl -xn' for details.
> 
> 
> could you look for details of the nfs-server.service startup failure?

+1
looks like a nfs service issue

> 
> Dan.
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
> 


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com