Comment 1 for bug 1698355

Looks like a child is killed and spawned again at the time of the error.

time: 0.3141711
Jun 16 11:18:39.592744 ubuntu-xenial-osic-cloud1-s3500-9357622 neutron-server[25622]: INFO oslo_service.service [-] Child 25715 killed by signal 9
Jun 16 11:18:39.606119 ubuntu-xenial-osic-cloud1-s3500-9357622 neutron-server[25622]: DEBUG oslo_service.service [-] Started child 542 {{(pid=25622) _start_child /usr/local/lib/python3.5/dist-packages/oslo_service/service.py:513}}
Jun 16 11:18:39.673921 ubuntu-xenial-osic-cloud1-s3500-9357622 neutron-server[25622]: DEBUG neutron_lib.callbacks.manager [-] Notify callbacks [] for process, after_init {{(pid=542) _notify_loop /usr/local/lib/python3.5/dist-packages/neutron_lib/callbacks/manager.py:167}}
Jun 16 11:18:39.688446 ubuntu-xenial-osic-cloud1-s3500-9357622 neutron-server[25622]: INFO neutron.wsgi [-] (542) wsgi starting up on http://0.0.0.0:9696
Jun 16

http://logs.openstack.org/04/461904/5/gate/gate-heat-dsvm-functional-convg-mysql-lbaasv2-py35-ubuntu-xenial/beeca10/logs/screen-q-svc.txt.gz#_Jun_16_11_18_39_592744

Probably OOM issue?