> On Apr 20, 2017, at 9:18 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
> Could you please share the output of
> sudo -u vdsm sudo service sanlock status
That command line prompts for vdsm’s password, which it doesn’t have. But
output returned as root is below. Is that ‘operation not permitted’ related?
Thanks,
-j
[root@sc5-ovirt-2 jlawrence]# service sanlock status
Redirecting to /bin/systemctl status sanlock.service
● sanlock.service - Shared Storage Lease Manager
Loaded: loaded (/usr/lib/systemd/system/sanlock.service; disabled; vendor
preset: disabled)
Active: active (running) since Wed 2017-04-19 16:56:40 PDT; 17h ago
Process: 16764 ExecStart=/usr/sbin/sanlock daemon (code=exited,
status=0/SUCCESS)
Main PID: 16765 (sanlock)
CGroup: /system.slice/sanlock.service
├─16765 /usr/sbin/sanlock daemon
└─16766 /usr/sbin/sanlock daemon
Apr 19 16:56:40 sc5-ovirt-2.squaretrade.com systemd[1]: Starting Shared Storage
Lease Manager...
Apr 19 16:56:40 sc5-ovirt-2.squaretrade.com systemd[1]: Started Shared Storage
Lease Manager.
Apr 19 16:56:40 sc5-ovirt-2.squaretrade.com sanlock[16765]: 2017-04-19
16:56:40-0700 482 [16765]: set scheduler RR|RESET_ON_FORK priority 99 failed:
Operation not permitted
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
