[Users] host deploy and after reboot not responsive

[Dan Kenigsberg]

On Tue, Jan 15, 2013 at 11:38:29AM +0100, Gianluca Cecchi wrote:
> On Tue, Jan 15, 2013 at 11:30 AM, Dan Kenigsberg wrote:
> 
> > Do you have systemd's logs (/var/log/messages may have traces of vdsm's
> > stop/start).
> >
> > What happens id you start vdsm now, does it crash again or happily running?
> >
> 
> I found this strange line in messages tat could indicate something:
> Jan 15 06:07:16 f18ovn03 vdsm vds WARNING Unable to load the json rpc
> server module. Please make sure it is installed.

That's plain log noise, since you do not have vdsm-json installed. oVirt
currently uses only xmlrpc, so this is not a real issue. I suppose that
the language of this line should be fined to something like "If you
really want jsonrpc, please make sure it is installed".

> 
> Anyway full node messages here:
> https://docs.google.com/file/d/0BwoPbcrMv8mvZnRZZnMtdU9hR28/edit

It seems that vdsm has stopped since the host was rebooted...

Jan 15 06:07:16 f18ovn03 vdsm vds WARNING Unable to load the json rpc server mod
Jan 15 06:07:18 f18ovn03 systemd[1]: Deactivating swap /dev/dm-0...
Jan 15 06:07:18 f18ovn03 systemd[1]: Deactivating swap /dev/dm-0...
Jan 15 06:07:18 f18ovn03 systemd[1]: Deactivating swap /dev/dm-0...
Jan 15 06:07:18 f18ovn03 systemd[1]: Deactivating swap /dev/dm-0...
Jan 15 06:07:18 f18ovn03 systemd[1]: Deactivating swap /dev/dm-0...
Jan 15 06:07:18 f18ovn03 systemd[1]: Stopping Stop Read-Ahead Data Collection 10
Jan 15 06:07:18 f18ovn03 systemd[1]: Stopped Stop Read-Ahead Data Collection 10s
Jan 15 06:07:18 f18ovn03 systemd[1]: Stopping Shared Storage Lease Manager...
Jan 15 06:07:18 f18ovn03 systemd[1]: Stopping Watchdog Multiplexing Daemon...
Jan 15 06:07:18 f18ovn03 systemd[1]: Stopping Network Time Service...
Jan 15 06:07:18 f18ovn03 systemd[1]: Stopping Multi-User.

the only remaining question is why vdsm did not start up after boot. Could it
be that it is missing `systemctl enable`?

> 
> I asked a guy that can access the server to run
> 
> systemctl status vdsmd.service
> (I forgot a final d in the service daemon name in the previous e-mail)
> 
> and a
> systemctl start vdsmd.service
> 
> At the same time if you have any hint for vdsClient command it is welcome...
> Gianluca

vdsClient -s 0 getVdsCaps

would access localhost vdsm (assuming you are using the default ssl). If it
barfs, we have a problem.

Dan.