Comment 2 for bug 1845244

I'm seeing the same behavior with Stein from source on Kolla 8.0.2

Nothing that seems of value in the container logs

2019-10-12 15:21:20.311 6 INFO oslo_service.service [req-4993422c-8481-49bf-ac05-f3b51f89d734 - - - - -] Child 33 exited with status 0
2019-10-12 15:21:20.313 6 INFO oslo_service.service [req-4993422c-8481-49bf-ac05-f3b51f89d734 - - - - -] Child 36 exited with status 0
2019-10-12 15:21:20.382 6 INFO oslo_service.service [req-4993422c-8481-49bf-ac05-f3b51f89d734 - - - - -] Child 32 exited with status 0
2019-10-12 15:21:20.456 6 INFO oslo_service.service [req-4993422c-8481-49bf-ac05-f3b51f89d734 - - - - -] Child 37 exited with status 0
2019-10-12 15:21:21.869 6 INFO oslo_service.service [req-4993422c-8481-49bf-ac05-f3b51f89d734 - - - - -] Child 31 exited with status 0
2019-10-12 15:21:21.892 6 INFO oslo_service.service [req-4993422c-8481-49bf-ac05-f3b51f89d734 - - - - -] Child 34 exited with status 0
2019-10-12 15:21:21.921 6 INFO oslo_service.service [req-4993422c-8481-49bf-ac05-f3b51f89d734 - - - - -] Child 38 exited with status 0
2019-10-12 15:21:21.958 6 INFO oslo_service.service [req-4993422c-8481-49bf-ac05-f3b51f89d734 - - - - -] Child 35 exited with status 0

## When I manually restarted the container - docker start xxxx

2019-10-12 15:32:04.835 6 INFO oslo_service.periodic_task [-] Skipping periodic task _discover_hosts_in_cells because its interval is negative
2019-10-12 15:32:05.371 6 INFO oslo_service.service [req-28f96a67-8ba8-4213-8963-73b52c4559c1 - - - - -] Starting 8 workers
2019-10-12 15:32:05.379 23 INFO nova.service [-] Starting scheduler node (version 19.0.2)
2019-10-12 15:32:05.381 24 INFO nova.service [-] Starting scheduler node (version 19.0.2)
2019-10-12 15:32:05.382 25 INFO nova.service [-] Starting scheduler node (version 19.0.2)
2019-10-12 15:32:05.386 26 INFO nova.service [-] Starting scheduler node (version 19.0.2)
2019-10-12 15:32:05.389 28 INFO nova.service [-] Starting scheduler node (version 19.0.2)
2019-10-12 15:32:05.388 27 INFO nova.service [-] Starting scheduler node (version 19.0.2)
2019-10-12 15:32:05.392 29 INFO nova.service [-] Starting scheduler node (version 19.0.2)
2019-10-12 15:32:05.401 30 INFO nova.service [-] Starting scheduler node (version 19.0.2)

There is this for the container stdout. It's not repeated when restarting and it might be shown during the shutdown.

Exception TypeError: "'NoneType' object is not callable" in <bound method _SocketDuckForFd.__del__ of _SocketDuckForFd:6> ignored