<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi Tushar,<div>Thanks you for your quick response on this. As I have already included the masakari-monitors plugin in my compute host's local.conf file in devstack, I have the repo present in my VM. Following the steps to set up the conf files and start the necessary masakari monitoring processes from this link <a href="https://github.com/openstack/masakari-monitors/blob/master/README.rst">https://github.com/openstack/masakari-monitors/blob/master/README.rst</a> I get the same error when I start the 3 monitoring processes (masakari-processmonitor, masakari-hostmonitor, masakari-instancemonitor) -</div><div><br></div><div><div>stack@devstack-:/etc/masakarimonitors$ masakari-processmonitor</div><div>Traceback (most recent call last):</div><div> File "/usr/local/bin/masakari-processmonitor", line 10, in <module></div><div> sys.exit(main())</div><div> File "/usr/local/lib/python2.7/dist-packages/masakarimonitors/cmd/processmonitor.py", line 31, in main</div><div> config.parse_args(sys.argv)</div><div> File "/usr/local/lib/python2.7/dist-packages/masakarimonitors/config.py", line 32, in parse_args</div><div> default_config_files=default_config_files)</div><div> File "/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2127, in __call__</div><div> self._check_required_opts()</div><div> File "/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2865, in _check_required_opts</div><div> raise RequiredOptError(<a href="http://opt.name">opt.name</a>, group)</div><div>oslo_config.cfg.RequiredOptError: value required for option auth-url in group [api]</div></div><div><br></div><div>After masakari setup I can file all the required binaries in my /usr/local/bin directory -</div><div><br></div><div><div>$ ls -ltr /usr/local/bin/masakari*</div><div>-rwxr-xr-x 1 root root 222 Apr 17 01:55 /usr/local/bin/masakari</div><div>-rwxr-xr-x 1 root root 976 Apr 21 23:41 /usr/local/bin/masakari-processmonitor.sh</div><div>-rwxr-xr-x 1 root root 918 Apr 21 23:41 /usr/local/bin/masakari-hostmonitor.sh</div><div>-rwxr-xr-x 1 root root 1854 Apr 29 01:01 /usr/local/bin/masakari-wsgi</div><div>-rwxr-xr-x 1 root root 158 Apr 29 01:01 /usr/local/bin/masakari-status</div><div>-rwxr-xr-x 1 root root 158 Apr 29 01:01 /usr/local/bin/masakari-manage</div><div>-rwxr-xr-x 1 root root 158 Apr 29 01:01 /usr/local/bin/masakari-engine</div><div>-rwxr-xr-x 1 root root 155 Apr 29 01:01 /usr/local/bin/masakari-api</div><div>-rwxr-xr-x 1 root root 174 Apr 30 04:34 /usr/local/bin/masakari-processmonitor</div><div>-rwxr-xr-x 1 root root 188 Apr 30 04:34 /usr/local/bin/masakari-introspectiveinstancemonitor</div><div>-rwxr-xr-x 1 root root 175 Apr 30 04:34 /usr/local/bin/masakari-instancemonitor</div><div>-rwxr-xr-x 1 root root 171 Apr 30 04:34 /usr/local/bin/masakari-hostmonitor</div></div><div><br></div><div>Please let me know is there any issue with my masakari setup with devstack and where can I find latest documentation on Masakari for using in devstack.</div><div><br></div><div>thanks for your pointer,</div><div>best regards,</div><div>Sanjay</div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 30, 2019 at 3:24 AM Patil, Tushar <<a href="mailto:Tushar.Patil@nttdata.com">Tushar.Patil@nttdata.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Sanjay,<br>
<br>
In case of masakari-processmonitor, it only monitors processes as mentioned in the process_list.yaml which by default monitors libvirt-bin, nova-compute, instancemonitor, hostmonitor and sshd processes.<br>
<br>
To test process failure, you should terminate any of the above processes.<br>
<br>
In case of instancemonitor, you can shutdown the VM to test whether a notification is sent or not.<br>
<br>
>> I have asked the same question in openstack forum, but not got a single response.<br>
Sorry, I didn't notice your question on forum. I have replied above comment on forum as well.<br>
<br>
Regards,<br>
Tushar Patil<br>
<br>
________________________________________<br>
From: Sanjay K <<a href="mailto:isanjayk5@gmail.com" target="_blank">isanjayk5@gmail.com</a>><br>
Sent: Monday, April 29, 2019 6:18:20 PM<br>
To: <a href="mailto:openstack-discuss@lists.openstack.org" target="_blank">openstack-discuss@lists.openstack.org</a><br>
Subject: [devstack][stein][masakari]Using Masakari in multihost devstack stein setup<br>
<br>
Hi all,<br>
I have been trying to setup Masakari in a 3 node setup - 1 controller + 2 computes with minimal openstack services installed using devstack stable/stein version. All these 3 nodes are Ubuntu 16.04 VMs. I have included Masakari plugin in controller's local.conf file and included masakari-monitor in both compute node's local.conf file. I want to test out VM/process failure in my test environment. To do so, when I kill one of the qemu process created for one instance (cirros 256 flavor VMs) on one of the compute with root user login, I did not see any notification under my horizon/instance-ha section for this (I have already created Segments, Hosts under instance-ha in horizon). Also the killed process is not restarted by Masakari.<br>
<br>
I have asked the same question in openstack forum, but not got a single response.<br>
<br>
masakari-notification-on-process-failure<<a href="https://ask.openstack.org/en/question/121490/masakari-notification-on-process-failure/" rel="noreferrer" target="_blank">https://ask.openstack.org/en/question/121490/masakari-notification-on-process-failure/</a>><br>
<br>
Whether any additional services related to Masakari need to be configured on compute hosts to detect failures since I did not find exactly the documentation related inside devstack for this.<br>
<br>
Please let me know if I am missing anything my set up. Any helps and pointers are most appreciated.<br>
<br>
thank you for your reply.<br>
<br>
best regards<br>
Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.<br>
</blockquote></div>