Univention Bugzilla – Bug 35069
Add timestamp to libvirt-check.sh
Last modified: 2015-01-29 11:41:10 CET
+++ This bug was initially created as a clone of Bug #33966 +++ ibvirt-check.sh (and other similar scripts) should add a time-stamp to their log output to help correlate events. The current output is not very helpful: > libvirt-check.sh: libvirt does not response like expected. Restarting libvirt now. > Restarting UCS libvirt daemon: libvirtdok: run: univention-libvirt: (pid 14108) 0s, normally down > .
Please please please! In a customer environment the check script started killing libvirtd regularly (Bug #36605). Without a time stamp is hard to correlate the execution of the script to the error message of UVMMd loosing its connection to the affected host.
r57189 | Bug #35069 libvirt: Improve check script Package: univention-virtual-machine-manager-node Version: 3.0.4-1.87.201501081418 Branch: ucs_4.0-0 Scope: errata4.0-0 2014-12-08-univention-virtual-machine-manager-node.yaml Add time stamp to libvirtd check script output. # pkill -STOP libvirtd # bash -x /usr/lib/univention-virtual-machine-manager-node/libvirt-check.sh # cat /var/log/univention/virtual-machine-manager-node-errors.log Jan 8 14:14:34 test35 libvirtd: does not response, restarting Restarting UCS libvirt daemon: libvirtdok: run: univention-libvirt: (pid 6458) 0s, normally down .
OK: Timestamp added OK: Now logs output of restart command OK: YAML -> Verified
<http://errata.univention.de/ucs/4.0/54.html>