[Users] host deploy and after reboot not responsive

[Dan Kenigsberg]

On Tue, Jan 22, 2013 at 12:52:43PM +0100, Gianluca Cecchi wrote:
> On Sat, Jan 19, 2013 at 8:26 PM, Dan Kenigsberg  wrote:
> > It might be it - but there must be more clues in the logs. I'd like to
> > see both vdsm.log and /var/log/message of boottime. journalctl may have
> > stories to tell, too.
> 
> In the mean time here
> messages
> https://docs.google.com/file/d/0BwoPbcrMv8mvNHpPREZGMnhYSzg/edit

Sorry, this gives no trace of a vdsmd failure. It would be great to know
if removal of the ntpd requirement helps vdsm on boot.


Jan 16 01:09:40 f18ovn03 ntpd[2489]: 0.0.0.0 c011 01 freq_not_set
Jan 16 01:09:40 f18ovn03 systemd-vdsmd[2483]: Note: Forwarding request to 'systemctl disable libvirt-guests.service'.
Jan 16 01:09:40 f18ovn03 systemd[1]: Reloading.
Jan 16 01:09:40 f18ovn03 systemd[1]: tuned.service has a D-Bus service name specified, but is not of type dbus. Ignoring.
Jan 16 01:09:40 f18ovn03 systemd-vdsmd[2483]: vdsm: libvirt already configured for vdsm [  OK  ]
Jan 16 01:09:41 f18ovn03 systemd-vdsmd[2483]: Starting wdmd...
Jan 16 01:09:41 f18ovn03 systemd-vdsmd[2483]: Redirecting to /bin/systemctl start  wdmd.service
Jan 16 01:09:41 f18ovn03 systemd[1]: Starting Watchdog Multiplexing Daemon...
Jan 16 01:09:41 f18ovn03 wdmd[2602]: wdmd started S0 H1 G179
Jan 16 01:09:41 f18ovn03 systemd-wdmd[2594]: Starting wdmd: [  OK  ]
Jan 16 01:09:41 f18ovn03 wdmd[2602]: /dev/watchdog armed with fire_timeout 60
Jan 16 01:09:41 f18ovn03 systemd[1]: Started Watchdog Multiplexing Daemon.
Jan 16 01:09:41 f18ovn03 systemd-vdsmd[2483]: Starting sanlock...
Jan 16 01:09:41 f18ovn03 systemd-vdsmd[2483]: Redirecting to /bin/systemctl start  sanlock.service
Jan 16 01:09:41 f18ovn03 systemd[1]: Starting Shared Storage Lease Manager...
Jan 16 01:09:41 f18ovn03 systemd-sanlock[2618]: Starting sanlock: [  OK  ]
Jan 16 01:09:41 f18ovn03 systemd[1]: Started Shared Storage Lease Manager.
Jan 16 01:09:41 f18ovn03 systemd-vdsmd[2483]: Starting iscsid:
Jan 16 01:09:41 f18ovn03 systemd-vdsmd[2483]: Redirecting to /bin/systemctl start  libvirtd.service
Jan 16 01:09:41 f18ovn03 systemd[1]: Started Virtualization daemon.
Jan 16 01:09:44 f18ovn03 kernel: [  361.499864] bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Jan 16 01:09:44 f18ovn03 kernel: [  361.528772] 8021q: 802.1Q VLAN Support v1.8
Jan 16 01:09:44 f18ovn03 kernel: [  361.530500] bonding: bond4 is being created...
Jan 16 01:09:44 f18ovn03 systemd-vdsmd[2483]: Starting up vdsm daemon:
Jan 16 01:09:44 f18ovn03 systemd-vdsmd[2483]: [  OK  ]#015vdsm start[  OK  ]
Jan 16 01:09:44 f18ovn03 systemd[1]: Started Virtual Desktop Server Manager.
Jan 16 01:09:45 f18ovn03 vdsm fileUtils WARNING Dir /rhev/data-center/mnt already exists
Jan 16 01:09:48 f18ovn03 vdsm Storage.LVM WARNING lvm pvs failed: 5 ['  NQRb0Q-3C0k-3RRo-1LZZ-NNy2-42A1-c7zO8e|/dev/mapper/3600507630efe05800000000000001601|106971529216|c6bb44ee-b824-44a0-a62c-f537a23d2e2b|x3XSZx-avUC-0NNI-w5K4-nCOp-uxp5-TD9GvH|135266304|797|0|2|107374182400'] ['  Skipping clustered volume group VG_VIRT04', '  Skipping volume group VG_VIRT04', '  Skipping clustered volume group VG_VIRT02', '  Skipping volume group VG_VIRT02', '  Skipping clustered volume group VG_VIRT03', '  Skipping volume group VG_VIRT03', '  Skipping clustered volume group VG_VIRT03', '  Skipping volume group VG_VIRT03', '  Skipping clustered volume group VG_VIRT01', '  Skipping volume group VG_VIRT01', '  Skipping clustered volume group VG_VIRT01', '  Skipping volume group VG_VIRT01']
Jan 16 01:09:48 f18ovn03 vdsm Storage.LVM WARNING lvm vgs failed: 5 ['  x3XSZx-avUC-0NNI-w5K4-nCOp-uxp5-TD9GvH|c6bb44ee-b824-44a0-a62c-f537a23d2e2b|wz--n-|106971529216|106971529216|134217728|797|797|RHAT_storage_domain_UNREADY|134217728|67107328'] ['  Skipping clustered volume group VG_VIRT04', '  Skipping clustered volume group VG_VIRT02', '  Skipping clustered volume group VG_VIRT03', '  Skipping clustered volume group VG_VIRT01']
Jan 16 01:09:48 f18ovn03 vdsm vds WARNING Unable to load the json rpc server module. Please make sure it is installed.


> 
> vdsm.log
> https://docs.google.com/file/d/0BwoPbcrMv8mvQ0k0aEJ5cWtXeTA/edit
> 
> The are related at boot on 16/01 at 01:04 am
> 
> In the afternoon I should be able to make the nt changes you requested.
> 
> journalctl was rotated. any command to let journalctl take another log
> file if present?
> 
> it says now:
> -- Logs begin at Wed, 2013-01-16 14:39:23 CET, end at Tue, 2013-01-22
> 12:52:05 CET. --
> 
> Gianluca