Troubleshooting Octavia Q & A: Dropping Packets Problem

Q. Hi I have a question for the health-manager. Who adds the entry to amphora_health table? I’m trying to get the Octavia health manager running, but I don't see any entries in the amphora_health table. I did a tcpdump on o-hm0 and port 5555 and I can see packages from my amphora.
A. You're saying you have no entries in the amphora_health table, but you have a LB?
Q. Yes, my LB is active.
	
A. Are there logs for the health daemon on the amphora?
If you have the log level at debug you should see some messages. The VMs should be sending heartbeats to the o-hm process, and that should log when it receives them and also when it inserts that information into the DB.	Are you on master or on a stable branch?

Q. I’m on master running on a non-devstack environment
A. Okay, so the o-hm should be handling any heartbeats coming in, so is the amphora sending heartbeats?
	Q. Yes, I did a tcpdump on o-hm port 5555 and I see UDP packages from the amphora's IP address.
	A. o-hm should be handling those...you don't see any logs?
Set up the health manager to log at debug. You should see messages as it processes the health packets. Also, make sure your firewall on the health manager instance has the port open.
Q. In o-hm, all I see is  attempting to listen on 192.168.0.3 port 5555 followed by DEBUG octavia.controller.healthmanager.health_manager [-] Starting amphora health check health_check /opt/bbc/openstack-11.0-master/neutron/local/lib/python2.7/site-packages/octavia/controller/healthmanager/health_manager.py:47 (repeated constantly)
A. Yeah that’s the periodic process that starts up to check the amphora_health table for the stale heartbeats.
	It sounds like there is a kernel firewall dropping the packets