I think this is going to require more time and information. Perhaps you could open a launchpad bug to track this?
I just brought up a new vagrant successfully yesterday, would you mind checking if you have the latest code and trying again? Also, if there is anything else relating to storm or monasca-thresh in that last log you provided, could you include that as well? Thanks, Ryan From: Pradeep Singh <ps4openst...@gmail.com<mailto:ps4openst...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, January 4, 2017 at 11:33 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Monasca] Monasca devstack installation is failing Hello, I am trying to install Monasca devstack using vagrant file given in monasca-ui repo. And its failing again and again with below error. Could you please help me, i will really appreciate your help. ==> default: 2017-01-05 06:28:06.125 | ++ functions-common:start_service:2306 : sudo /bin/systemctl start monasca-thresh ==> default: 2017-01-05 06:28:27.440 | Job for monasca-thresh.service failed because the control process exited with error code. See "systemctl status monasca-thresh.service" and "journalctl -xe" for details. ==> default: 2017-01-05 06:28:27.444 | ++ /opt/stack/monasca-api/devstack/plugin.sh:start_monasca_services:235 : restart_service monasca-thresh ==> default: 2017-01-05 06:28:27.447 | ++ functions-common:restart_service:2282 : '[' -x /bin/systemctl ']' ==> default: 2017-01-05 06:28:27.450 | ++ functions-common:restart_service:2283 : sudo /bin/systemctl restart monasca-thresh ==> default: 2017-01-05 06:28:47.368 | Job for monasca-thresh.service failed because the control process exited with error code. See "systemctl status monasca-thresh.service" and "journalctl -xe" for details. vagrant@devstack:~$ systemctl status monasca-thresh.service ● monasca-thresh.service - LSB: Monitoring threshold engine running under storm Loaded: loaded (/etc/init.d/monasca-thresh; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2017-01-05 06:28:47 UTC; 27s ago Docs: man:systemd-sysv-generator(8) Process: 28638 ExecStart=/etc/init.d/monasca-thresh start (code=exited, status=1/FAILURE) Jan 05 06:28:47 devstack monasca-thresh[28638]: main() Jan 05 06:28:47 devstack monasca-thresh[28638]: File "/opt/storm/current/bin/storm.py", line 766, in main Jan 05 06:28:47 devstack monasca-thresh[28638]: (COMMANDS.get(COMMAND, unknown_command))(*ARGS) Jan 05 06:28:47 devstack monasca-thresh[28638]: File "/opt/storm/current/bin/storm.py", line 248, in jar Jan 05 06:28:47 devstack monasca-thresh[28638]: os.remove(tmpjar) Jan 05 06:28:47 devstack monasca-thresh[28638]: OSError: [Errno 2] No such file or directory: '/tmp/30c1980ed31011e68cd3080027b55b5e.jar' Jan 05 06:28:47 devstack systemd[1]: monasca-thresh.service: Control process exited, code=exited status=1 Jan 05 06:28:47 devstack systemd[1]: Failed to start LSB: Monitoring threshold engine running under storm. Jan 05 06:28:47 devstack systemd[1]: monasca-thresh.service: Unit entered failed state. Jan 05 06:28:47 devstack systemd[1]: monasca-thresh.service: Failed with result 'exit-code'. Thanks, Pradeep
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
