Il 23/01/2014 15:30, Brad House ha scritto: > > > On 01/23/2014 09:24 AM, Sandro Bonazzola wrote: >>> # service vdsmd status >>> >Redirecting to /bin/systemctl status vdsmd.service >>> >vdsmd.service - Virtual Desktop Server Manager >>> > Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) >>> > Active: failed (Result: start-limit) since Thu 2014-01-23 09:16:38 >>> > EST; 1min 26s ago >>> > Process: 2387 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh >>> > --post-stop (code=exited, status=0/SUCCESS) >>> > Process: 2380 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1 >>> > /dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, >>> > status=1/FAILURE) >>> > Process: 2328 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh >>> > --pre-start (code=exited, status=0/SUCCESS) >>> > >>> >Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Unit >>> >vdsmd.service entered failed state. >>> >Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: vdsmd.service >>> >holdoff time over, scheduling restart. >>> >Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Stopping >>> >Virtual Desktop Server Manager... >>> >Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Starting >>> >Virtual Desktop Server Manager... >>> >Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: vdsmd.service >>> >start request repeated too quickly, refusing to start. > >> what's this ^^^^. It's the first start of vdsmd! > > > I'm not sure I understand the meaning of this reply :/
Sorry it was for vdsm people. It sorted out that changing owner to vdsm:kvm on /var/log/vdsm/vdsm.log solve the issue. Investigating how owner have been set to root:root on that file. > > Thanks. > -Brad -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
