New Question

Openstack nova compute is terminating unexpectadly. [closed]

asked 2014-12-23 15:24:32 +0300

Niladri gravatar image

updated 2015-01-12 12:15:15 +0300

I have installed openstack Hyper-V nova compute with HyperVNovaComputeJuno201421.msi in my windows server 2012 R2 Hyper-V enabled machine. The installer worked fine and finished successfully. But whenever I am trying to start the nova service with 'net start nova-compute' command. It is giving the following error :

The OpenStack Nova Compute Service service is starting.. The OpenStack Nova Compute Service service could not be started.

A system error has occured.

System error 1067 has occured.

The process terminated unexpectadly.

What am I doing wrong?

Any Help is appreciated. Thanks in Advance.


I don't know if this was the actual reason, but in my first installation, my parameters were wrong. But on subsequent installation the error persisted even for correct parameters. So I uninstalled my OS itself, installed a fresh one and installed the Nova carefully with all the correct parameters, and voila!!!! it started alright.

I know it is not so neat, but anyway.


edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Claudiu Belu
close date 2016-11-09 19:49:11.306292

2 answers

Sort by » oldest newest most voted

answered 2015-01-22 11:20:05 +0300

The current beta image has a broken oslo.messaging - python.exe -c 'import olsomessaging' errors, and stdlib/oslomessaging is missing all the sub packages.

edit flag offensive delete link more


Yes thanks, we are aware of this issue and currently updating the build scripts. Unlike the stable releases, which are heavily tempest tested, the beta/master MSI is a continuous build from the upstream master bits, so it can suffer from temporary issues like this one. We plan to add a CI to run at least a minimum scenario test before publishing the binaries to catch this type of issues in a timely manner.

alexpilotti gravatar imagealexpilotti ( 2015-01-22 11:55:38 +0300 )edit

Fixed. There was more than that, as the greenlet version required by the latest oslo.messaging was not supported on the Windows Python 2.7.3 previously included, so we upgraded the entire Python environment bundled with the installer to 2.7.9.

alexpilotti gravatar imagealexpilotti ( 2015-01-23 04:41:46 +0300 )edit

answered 2014-12-23 15:40:35 +0300

alexpilotti gravatar image

updated 2014-12-26 10:04:07 +0300

Hi, as a first step, can you please post the content of the nova-compute.log? It's available in the log directory set during setup, by default "C:\OpenStack\Logs". The file might not exist if the service fails before being able to start the logging module.

Next step if the log file is not present, please start the Nova compute process manually with the following command line (please adjust the path based on your environment) and post the output here:

"C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\Scripts\nova-compute.exe" --config-file "C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\etc\nova.conf"



edit flag offensive delete link more


The folder C:\OpenStack\Logs is empty :(

Niladri gravatar imageNiladri ( 2014-12-23 16:31:31 +0300 )edit

The next step consists in running the Nova compute process manually and look for the error that prevents the service from starting. I updated the previous answer with the details on how to do this.

alexpilotti gravatar imagealexpilotti ( 2014-12-26 10:02:05 +0300 )edit

Hi I have the same path as you have posted and I executed the command , but it is returning this one line only. 'Failed to create process.'

Niladri gravatar imageNiladri ( 2014-12-26 16:16:18 +0300 )edit

You can try adding a & when running: & "C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\Scripts\nova-compute.exe" --config-file "C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\etc\nova.conf". The log folder is "C:\OpenStack\Log".

ader1990 gravatar imageader1990 ( 2015-01-05 14:35:58 +0300 )edit

If this does not work, you can examine the windows error log (start eventvwr.msc). Moreover, you can give some details about the information you have inserted when you have installed the msi and the features you have enabled. Thanks.

ader1990 gravatar imageader1990 ( 2015-01-05 14:40:15 +0300 )edit

Question Tools


Asked: 2014-12-23 15:24:32 +0300

Seen: 1,166 times

Last updated: Jan 22 '15