Red Hat Bugzilla – Bug 870139
3.2 - No proper log when vdsm service fails to initialize due to permission error on logger (vdsm.log)
Last modified: 2016-02-10 14:18:48 EST
Description of problem:
No proper log when vdsm service fails to initialize due to permission error on logger (vdsm.log)
Version-Release number of selected component (if applicable):
RHEVM 3.1 - SI22
QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.295.el6_3.2.x86_64
Steps to Reproduce:
No description or reason in logs found, when VDSM service failed to start.
In my case VDSM service failed to start from the fact that Logger has wrong permission.
When I manually start vdsm service, I get “OK”, although this wrong status
In vdsm.log shoud alwase be a reason of failure VDSM service.
My fix for that:
http://gerrit.ovirt.org/#/c/9118 - it adds verification for the log file permissions before starting vdsm service.
Some bugs with my solution: It doesn't verify the mode of the file and selinux permissions. Danken suggested another solution that raises another bug issue in coreutils (https://bugzilla.redhat.com/show_bug.cgi?id=879215).
We are still trying to find alternative or a fix for that coreutil bug.
Alternative like checking the permissions via vdsm process (and not by vdsmd script) won't help because the user can't receive reports about the failure without using log file (we can report to another log file though, but I don't know which), I prefer to stick with danken suggestion until the coreutil issue will be solved.
About the alternative in the last paragraph... Could we log it to the syslog using:
Still no news from https://bugzilla.redhat.com/show_bug.cgi?id=879215
So I posted http://gerrit.ovirt.org/#/c/9700/ (notice that by default assert message is being reported to syslog)
And after fixing the su bug we'll add - http://gerrit.ovirt.org/#/c/9118/
Mar 5 16:37:22 cheetah01 respawn: slave '/usr/share/vdsm/vdsm' died too quickly, respawning slave
Mar 5 16:37:22 cheetah01 python: error in accessing vdsm log file
3.2 has been released