Re: [Openstack] Masakari on queens

2018-06-29 Thread Torin Woltjer
The wrong address was specified in the corosync configuration. Corrected that 
and now it runs without error. The important part here was the -c 1 switch of 
tcpdump. Timeout was being reached before a single packet was captured on 
tcpdump ( because the configuration of corosync was incorrect ). Once timeout 
was reached it was producing an exit code 124, which triggered the exception in 
the host_handler.

Torin Woltjer

Grand Dial Communications - A ZK Tech Inc. Company

616.776.1066 ext. 2006
www.granddial.com


From: "Torin Woltjer" 
Sent: 6/22/18 2:17 PM
To: "tushar.pa...@nttdata.com" 
Subject: Re: Masakari on queens
Oddly enough, I never made changes to the original code to get that output. It 
is just masakari-monitor 4.0.0 as installed by pip.

Here are the changes and output to that code snippit you sent:
http://paste.openstack.org/show/723924/

I'd like to increase the logging, but I'm not familiar with the codebase and 
lack more than a rudimentary knowledge of python. I've found where it seems pip 
installed the files for masakari-hostmonitor, but I don't know which one 
contains the corosync bit.


From: "Patil, Tushar" 
Sent: 6/20/18 12:51 AM
To: "torin.wolt...@granddial.com" 
Subject: Re: Masakari on queens
Hi Torin,

Option -i is correct.

It seems that you have modified code to log error message: 
"ProcessExecutionError: Unexpected error while running command."

Could you please log 'stderr' and 'exit_code' as well in order to know the 
exact error you are getting?
I suspect you must be getting 124 exit code.

This is a small program which I have created to simulate the error you are 
getting.
http://paste.openstack.org/show/723882/

Please specify interface and port as per your configuration and run the program.

Regards,
Tushar Patil


From: Torin Woltjer
Sent: Tuesday, June 19, 2018 9:58:32 PM
To: Patil, Tushar
Subject: Re: Masakari on queens

Thank for the reply. Tushar Patil.

The command:
$timeout 5 tcpdump -n -c 1 -p -I vlan60 port 5405
returns:
"tcpdump: enp2s0f0: That device doesn't support monitor mode"

The command:
(lowercase i)
$timeout 5 tcpdump -n -c 1 -p -i vlan60 port 5405
Runs fine with no errors:
"tcpdump: listening on vlan60, link-type EN10MB (Ethernet), capture size 262144 
bytes"

The in use interfaces on all of my nodes are as follows:

enp2s0f0=192.168.114.x
enp3s0f0=bond0=vlan60,vlan101
enp3s0f1=bond0=vlan60,vlan101
vlan60=management
vlan101=provider

>From this part of handle_host.py I can't tell what is causing the command to 
>raise exception.


From: "Patil, Tushar"
Sent: 6/18/18 9:10 PM
To: "openstack@lists.openstack.org" , "torin.wolt...@granddial.com"
Subject: Re: Masakari on queens
Hi Torin,

Looking at the code, it seems it is trying to run below command as root user.

timeout tcpdump -n -c 1 -p -I port

where,
tcpdump_timeout -> CONF.host.tcpdump_timeout -> default value is 5 seconds
multicast_interface -> corosync_multicast_interface -> vlan60
multicast_ports-> corosync_multicast_ports -> 5405

Unfortunately, the error message is suppressed [1] hence it's difficult to know 
the exact reason.
Can you please run below command on the host where you are running 
masakari-hostmonitor service? The error you would get after running this 
command would give you some hint to troubleshoot this issue further.

$timeout 5 tcpdump -n -c 1 -p -I vlan60 port 5405

[1] : 
https://github.com/openstack/masakari-monitors/blob/cde057bc685b7bbc35f5c425f9690b01766654b2/masakarimonitors/hostmonitor/host_handler/handle_host.py#L121

Regards,
Tushar Patil


From: Torin Woltjer
Sent: Tuesday, June 19, 2018 4:01:29 AM
To: Patil, Tushar; openstack@lists.openstack.org
Subject: Masakari on queens

Hello Tushar Patil,

I have upgraded to Openstack Queens and am trying to run Masakari version 4.0.0 
. I'm curious what additional configuration is required to get this set up 
correctly.

/etc/masakarimonitors/masakarimonitors.conf
http://paste.openstack.org/show/723726/

masakari-hostmonitor is giving me errors like:
2018-06-18 12:44:44.812 18236 ERROR 
masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync 
communication is failed.: ProcessExecutionError: Unexpected error while running 
command.
2018-06-18 12:45:14.895 18236 INFO 
masakarimonitors.hostmonitor.host_handler.handle_host [-] 
'UBNTU-OSTACK-COMPUTE2' is 'online'.
2018-06-18 12:46:20.047 18236 WARNING 
masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync 
communication using 'vlan60' is failed.: ProcessExecutionError: Unexpected 
error while running command.

Do you have any knowledge on this?
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,

[Openstack] (no subject)

2018-06-29 Thread Torin Woltjer
Installed masakari 4.0.0 on queens. Hostmonitor, instancemonitor, and 
processmonitor all running on compute nodes. API and engine running on 
controller nodes. I've tried using the masakari client to list/add segments, 
any of those commands does nothing and returns:

("'NoneType' object has no attribute 'auth_url'", ', mode 
'w' at 0x7f26bb4b71e0>)

Torin Woltjer

Grand Dial Communications - A ZK Tech Inc. Company

616.776.1066 ext. 2006
www.granddial.com


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack