oVirt/vdsm

Log output is incomplete or unavailable

xiaofanshifu opened this issue · 2 comments

xiaofanshifu commented

Ask for help!

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

[root@node-3 ~]# systemctl status vdsmd
● vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2022-08-16 16:45:04 CST; 10 months 27 days ago
 Main PID: 6849 (vdsmd)
    Tasks: 38
   Memory: 148.7M
   CGroup: /system.slice/vdsmd.service
           └─6849 /usr/bin/python2 /usr/share/vdsm/vdsmd

Jul 11 23:18:07 node-3 vdsm[6849]: WARN MOM not available.
Jul 11 23:18:07 node-3 vdsm[6849]: WARN MOM not available, KSM stats will be missing.
Jul 11 23:18:24 node-3 vdsm[6849]: WARN unhandled close event
Jul 11 23:22:12 node-3 vdsm[6849]: WARN unhandled write event
Jul 11 23:22:12 node-3 vdsm[6849]: WARN unhandled close event
Jul 11 23:25:06 node-3 vdsm[6849]: WARN unhandled close event
Jul 11 23:33:02 node-3 vdsm[6849]: WARN unhandled close event
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
[root@node-3 ~]#
[root@node-3 ~]# systemctl status supervdsmd
● supervdsmd.service - Auxiliary vdsm service for running helper functions as root
   Loaded: loaded (/usr/lib/systemd/system/supervdsmd.service; static; vendor preset: enabled)
   Active: active (running) since Tue 2022-08-16 16:45:01 CST; 10 months 27 days ago
 Main PID: 6699 (supervdsmd)
    Tasks: 18
   Memory: 156.5M
   CGroup: /system.slice/supervdsmd.service
           └─6699 /usr/bin/python2 /usr/share/vdsm/supervdsmd --sockfile /var/run/vdsm/svdsm.sock

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
[root@node-3 ~]#

Is the logratate log not sending a signal?

michalskrivanek commented

we write logs the good old fashioned way to /var/log/vdsm/vdsm.log. That is the primary place to look at for vdsm.

nirs commented

Looks like systemd problem, not vdsm. Also this is very old and inactive issue, maybe close?