[Users] hosted-engine setup fails on RHEL6

[Sandro Bonazzola]

Il 23/01/2014 14:39, Frank Wall ha scritto:
> Hi Sandro,
> 
> On Thu, Jan 23, 2014 at 02:28:29PM +0100, Sandro Bonazzola wrote:
>> Do you have the same issue you've with nightly?
> 
> on BETA the hosted-engine setup fails (earlier) with another issue that seems to be
> fixed in NIGHTLY:
> 
> 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel rhel.status:138 check service vdsmd status
> 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:366 execute: ('/sbin/initctl', 'status', 'vdsmd'), executable='None', cwd='None', env=None
> 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:383 execute-result: ('/sbin/initctl', 'status', 'vdsmd'), rc=1
> 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:441 execute-output: ('/sbin/initctl', 'status', 'vdsmd') stdout:
> 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:446 execute-output: ('/sbin/initctl', 'status', 'vdsmd') stderr:
> initctl: Unknown job: vdsmd
> 

can you attach full logs of this execution?


> Please don't mixup things... this was the first try on BETA. All other logs are from NIGHTLY :-)
> 
> 
>> can you attach vdsm logs?
> 
> Yes, but only a few lines are logged during hosted-engine setup:
> 
> MainThread::DEBUG::2014-01-23 14:17:37,132::supervdsmServer::424::SuperVdsm.Server::(main) Terminated normally
> MainThread::DEBUG::2014-01-23 14:17:37,885::netconfpersistence::134::root::(_getConfigs) Non-existing config set.
> MainThread::DEBUG::2014-01-23 14:17:37,885::netconfpersistence::134::root::(_getConfigs) Non-existing config set.
> MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::384::SuperVdsm.Server::(main) Making sure I'm root - SuperVdsm
> MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::393::SuperVdsm.Server::(main) Parsing cmd args
> MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::396::SuperVdsm.Server::(main) Cleaning old socket /var/run/vdsm/svdsm.sock
> MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::400::SuperVdsm.Server::(main) Setting up keep alive thread
> MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::406::SuperVdsm.Server::(main) Creating remote object manager
> MainThread::DEBUG::2014-01-23 14:17:37,901::supervdsmServer::417::SuperVdsm.Server::(main) Started serving super vdsm object
> sourceRoute::DEBUG::2014-01-23 14:17:37,901::sourceRouteThread::56::root::(_subscribeToInotifyLoop) sourceRouteThread.subscribeToInotifyLoop started
> 

so vdsmd never started at all?


> 
> 
> Thanks
> - Frank
> 


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com