Oct 14 08:14:23 np0005486730 haproxy[7]: Server aodh/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:23 np0005486730 haproxy[7]: Server aodh/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:23 np0005486730 haproxy[7]: Server aodh/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:23 np0005486730 haproxy[7]: proxy aodh has no server available!
Oct 14 08:14:23 np0005486730 haproxy[7]: Server cinder/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:23 np0005486730 haproxy[7]: Server cinder/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:23 np0005486730 haproxy[7]: Server cinder/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:23 np0005486730 haproxy[7]: proxy cinder has no server available!
Oct 14 08:14:23 np0005486730 haproxy[7]: Server glance_api/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server glance_api/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server glance_api/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: proxy glance_api has no server available!
Oct 14 08:14:24 np0005486730 haproxy[7]: Server glance_api_internal/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server glance_api_internal/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server glance_api_internal/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: proxy glance_api_internal has no server available!
Oct 14 08:14:24 np0005486730 haproxy[7]: Server gnocchi/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server gnocchi/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server gnocchi/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: proxy gnocchi has no server available!
Oct 14 08:14:24 np0005486730 haproxy[7]: Server heat_api/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server heat_api/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Backup Server mysql/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server heat_api/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: proxy heat_api has no server available!
Oct 14 08:14:24 np0005486730 haproxy[7]: Backup Server mysql/np0005486729.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 17ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server heat_cfn/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Backup Server mysql/np0005486730.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 28ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: proxy mysql has no server available!
Oct 14 08:14:24 np0005486730 haproxy[7]: Server heat_cfn/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server heat_cfn/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: proxy heat_cfn has no server available!
Oct 14 08:14:24 np0005486730 haproxy[7]: Server horizon/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server horizon/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server horizon/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: proxy horizon has no server available!
Oct 14 08:14:24 np0005486730 haproxy[7]: Server keystone_admin/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server keystone_admin/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server keystone_admin/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: proxy keystone_admin has no server available!
Oct 14 08:14:24 np0005486730 haproxy[7]: Server keystone_public/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server keystone_public/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server keystone_public/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: proxy keystone_public has no server available!
Oct 14 08:14:24 np0005486730 haproxy[7]: Server manila/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server manila/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: Server manila/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:24 np0005486730 haproxy[7]: proxy manila has no server available!
Oct 14 08:14:25 np0005486730 haproxy[7]: Server neutron/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server neutron/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server neutron/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: proxy neutron has no server available!
Oct 14 08:14:25 np0005486730 haproxy[7]: Server nova_metadata/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server nova_metadata/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server nova_metadata/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: proxy nova_metadata has no server available!
Oct 14 08:14:25 np0005486730 haproxy[7]: Server nova_novncproxy/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server nova_novncproxy/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server nova_novncproxy/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: proxy nova_novncproxy has no server available!
Oct 14 08:14:25 np0005486730 haproxy[7]: Server nova_osapi/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server nova_osapi/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server nova_osapi/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: proxy nova_osapi has no server available!
Oct 14 08:14:25 np0005486730 haproxy[7]: Server placement/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server placement/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server placement/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: proxy placement has no server available!
Oct 14 08:14:25 np0005486730 haproxy[7]: Server redis/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused at step 1 of tcp-check (connect port 6379)", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server redis/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused at step 1 of tcp-check (connect port 6379)", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server redis/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused at step 1 of tcp-check (connect port 6379)", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: proxy redis has no server available!
Oct 14 08:14:25 np0005486730 haproxy[7]: Server swift_proxy_server/np0005486728.storage.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server swift_proxy_server/np0005486729.storage.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 3ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: Server swift_proxy_server/np0005486730.storage.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:14:25 np0005486730 haproxy[7]: proxy swift_proxy_server has no server available!
Oct 14 08:16:07 np0005486730 haproxy[7]: Backup Server mysql/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 21ms. 0 active and 1 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Oct 14 08:16:32 np0005486730 haproxy[7]: Backup Server mysql/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 27ms. 0 active and 2 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Oct 14 08:17:38 np0005486730 haproxy[7]: Server redis/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 0, info: "(tcp-check)", check duration: 2ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:17:46 np0005486730 haproxy[7]: Backup Server mysql/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 18ms. 0 active and 3 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Oct 14 08:18:32 np0005486730 haproxy[7]: Server keystone_admin/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 4ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:18:32 np0005486730 haproxy[7]: Server keystone_admin/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 6ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:18:32 np0005486730 haproxy[7]: Server keystone_public/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 4ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:18:32 np0005486730 haproxy[7]: Server keystone_public/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 8ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:18:34 np0005486730 haproxy[7]: Server horizon/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 301, check duration: 1ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:18:34 np0005486730 haproxy[7]: Server horizon/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 301, check duration: 1ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:19:10 np0005486730 haproxy[7]: Server horizon/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 301, check duration: 1ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:19:36 np0005486730 haproxy[7]: Server keystone_admin/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 8ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:19:36 np0005486730 haproxy[7]: Server keystone_public/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 11ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:49 np0005486730 haproxy[7]: Server cinder/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 2ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:49 np0005486730 haproxy[7]: Server heat_api/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 13ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:50 np0005486730 haproxy[7]: Server heat_cfn/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 1ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:51 np0005486730 haproxy[7]: Server aodh/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 4ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:52 np0005486730 haproxy[7]: Server manila/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 3ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:53 np0005486730 haproxy[7]: Server nova_novncproxy/np0005486728.internalapi.localdomain is UP, reason: Layer4 check passed, check duration: 0ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:55 np0005486730 haproxy[7]: Server placement/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 4ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:57 np0005486730 haproxy[7]: Server neutron/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 5ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:57 np0005486730 haproxy[7]: Server nova_metadata/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 2ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:58 np0005486730 haproxy[7]: Server swift_proxy_server/np0005486728.storage.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 1ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:58 np0005486730 haproxy[7]: Server nova_osapi/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 3ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:58 np0005486730 haproxy[7]: Server glance_api/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 5ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:23:58 np0005486730 haproxy[7]: Server glance_api_internal/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 5ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:02 np0005486730 haproxy[7]: Server heat_api/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 2ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:02 np0005486730 haproxy[7]: Server cinder/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 2ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:02 np0005486730 haproxy[7]: Server heat_cfn/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 6ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:02 np0005486730 haproxy[7]: Server aodh/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 5ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:05 np0005486730 haproxy[7]: Server cinder/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 4ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:06 np0005486730 haproxy[7]: Server heat_cfn/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 2ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:06 np0005486730 haproxy[7]: Server aodh/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 13ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:06 np0005486730 haproxy[7]: Server heat_api/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 1ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:06 np0005486730 haproxy[7]: Server manila/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 1045ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:07 np0005486730 haproxy[7]: Server nova_novncproxy/np0005486730.internalapi.localdomain is UP, reason: Layer4 check passed, check duration: 0ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:07 np0005486730 haproxy[7]: Server placement/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 1ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:09 np0005486730 haproxy[7]: Server nova_novncproxy/np0005486729.internalapi.localdomain is UP, reason: Layer4 check passed, check duration: 0ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:10 np0005486730 haproxy[7]: Server manila/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 957ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:11 np0005486730 haproxy[7]: Server nova_metadata/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 3ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:11 np0005486730 haproxy[7]: Server nova_osapi/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 4ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:11 np0005486730 haproxy[7]: Server neutron/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 4ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:11 np0005486730 haproxy[7]: Server placement/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 1ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:12 np0005486730 haproxy[7]: Server swift_proxy_server/np0005486730.storage.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 0ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:12 np0005486730 haproxy[7]: Server glance_api/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 5ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:12 np0005486730 haproxy[7]: Server glance_api_internal/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 6ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:13 np0005486730 haproxy[7]: Server neutron/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 5ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:14 np0005486730 haproxy[7]: Server glance_api_internal/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 4ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:14 np0005486730 haproxy[7]: Server nova_metadata/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 4ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:15 np0005486730 haproxy[7]: Server nova_osapi/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 9ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:16 np0005486730 haproxy[7]: Server swift_proxy_server/np0005486729.storage.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 2ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:24:16 np0005486730 haproxy[7]: Server glance_api/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 4ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:28:00 np0005486730 haproxy[7]: 192.168.122.110:34078 [14/Oct/2025:08:28:00.412] redis redis/np0005486728.internalapi.localdomain 1/0/13 10 -- 39/39/38/38/0 0/0
Oct 14 08:28:00 np0005486730 haproxy[7]: 192.168.122.110:34042 [14/Oct/2025:08:28:00.189] redis redis/np0005486728.internalapi.localdomain 1/0/236 4427 -- 38/38/37/37/0 0/0
Oct 14 08:28:00 np0005486730 haproxy[7]: 192.168.122.104:60066 [14/Oct/2025:08:28:00.523] redis redis/np0005486728.internalapi.localdomain 1/0/18 10 -- 39/39/38/38/0 0/0
Oct 14 08:28:00 np0005486730 haproxy[7]: 192.168.122.104:60046 [14/Oct/2025:08:28:00.287] redis redis/np0005486728.internalapi.localdomain 1/0/254 4427 -- 38/38/37/37/0 0/0
Oct 14 08:28:00 np0005486730 haproxy[7]: 192.168.122.110:34100 [14/Oct/2025:08:28:00.706] redis redis/np0005486728.internalapi.localdomain 1/0/9 10 -- 39/39/38/38/0 0/0
Oct 14 08:28:00 np0005486730 haproxy[7]: 192.168.122.110:34086 [14/Oct/2025:08:28:00.454] redis redis/np0005486728.internalapi.localdomain 1/0/262 4428 -- 39/39/37/37/0 0/0
Oct 14 08:28:00 np0005486730 haproxy[7]: 192.168.122.104:60084 [14/Oct/2025:08:28:00.844] redis redis/np0005486728.internalapi.localdomain 1/0/15 10 -- 38/38/37/37/0 0/0
Oct 14 08:28:00 np0005486730 haproxy[7]: 192.168.122.104:60082 [14/Oct/2025:08:28:00.569] redis redis/np0005486728.internalapi.localdomain 1/0/290 4428 -- 38/38/36/36/0 0/0
Oct 14 08:28:03 np0005486730 haproxy[7]: Server gnocchi/np0005486730.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 3ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:28:04 np0005486730 haproxy[7]: Server gnocchi/np0005486729.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 3ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.110:36422 [14/Oct/2025:08:28:06.001] redis redis/np0005486728.internalapi.localdomain 1/0/26 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.110:36406 [14/Oct/2025:08:28:05.744] redis redis/np0005486728.internalapi.localdomain 1/0/285 4427 -- 44/44/43/43/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.104:51668 [14/Oct/2025:08:28:06.199] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.104:51658 [14/Oct/2025:08:28:05.893] redis redis/np0005486728.internalapi.localdomain 1/0/317 4427 -- 45/45/43/43/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.110:36440 [14/Oct/2025:08:28:06.258] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.110:36426 [14/Oct/2025:08:28:06.038] redis redis/np0005486728.internalapi.localdomain 1/0/231 4427 -- 45/45/43/43/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.110:36456 [14/Oct/2025:08:28:06.553] redis redis/np0005486728.internalapi.localdomain 1/0/8 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.110:36448 [14/Oct/2025:08:28:06.302] redis redis/np0005486728.internalapi.localdomain 1/0/259 4427 -- 45/45/43/43/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.104:51684 [14/Oct/2025:08:28:06.566] redis redis/np0005486728.internalapi.localdomain 1/0/8 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.104:51678 [14/Oct/2025:08:28:06.249] redis redis/np0005486728.internalapi.localdomain 1/0/324 4427 -- 43/43/42/42/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.110:36468 [14/Oct/2025:08:28:06.585] redis redis/np0005486728.internalapi.localdomain 1/0/234 4428 -- 45/45/44/44/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.110:36480 [14/Oct/2025:08:28:06.810] redis redis/np0005486728.internalapi.localdomain 1/0/9 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.104:51696 [14/Oct/2025:08:28:06.600] redis redis/np0005486728.internalapi.localdomain 1/0/260 4428 -- 44/44/43/43/0 0/0
Oct 14 08:28:06 np0005486730 haproxy[7]: 192.168.122.104:51698 [14/Oct/2025:08:28:06.849] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0
Oct 14 08:28:07 np0005486730 haproxy[7]: 192.168.122.104:51708 [14/Oct/2025:08:28:07.136] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:07 np0005486730 haproxy[7]: 192.168.122.104:51702 [14/Oct/2025:08:28:06.887] redis redis/np0005486728.internalapi.localdomain 1/0/261 4428 -- 43/43/42/42/0 0/0
Oct 14 08:28:12 np0005486730 haproxy[7]: 192.168.122.110:36496 [14/Oct/2025:08:28:12.096] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:12 np0005486730 haproxy[7]: 192.168.122.110:36488 [14/Oct/2025:08:28:11.849] redis redis/np0005486728.internalapi.localdomain 1/0/260 4427 -- 43/43/42/42/0 0/0
Oct 14 08:28:12 np0005486730 haproxy[7]: 192.168.122.110:36520 [14/Oct/2025:08:28:12.334] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:12 np0005486730 haproxy[7]: 192.168.122.110:36504 [14/Oct/2025:08:28:12.126] redis redis/np0005486728.internalapi.localdomain 1/0/221 4427 -- 44/44/43/43/0 0/0
Oct 14 08:28:12 np0005486730 haproxy[7]: 192.168.122.104:48516 [14/Oct/2025:08:28:12.410] redis redis/np0005486728.internalapi.localdomain 1/0/13 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:12 np0005486730 haproxy[7]: 192.168.122.104:48510 [14/Oct/2025:08:28:12.181] redis redis/np0005486728.internalapi.localdomain 1/0/242 4427 -- 45/45/43/43/0 0/0
Oct 14 08:28:12 np0005486730 haproxy[7]: 192.168.122.110:46088 [14/Oct/2025:08:28:12.700] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:12 np0005486730 haproxy[7]: 192.168.122.110:36534 [14/Oct/2025:08:28:12.375] redis redis/np0005486728.internalapi.localdomain 1/0/338 4428 -- 44/44/43/43/0 0/0
Oct 14 08:28:12 np0005486730 haproxy[7]: 192.168.122.104:48526 [14/Oct/2025:08:28:12.449] redis redis/np0005486728.internalapi.localdomain 1/0/336 4428 -- 45/45/44/44/0 0/0
Oct 14 08:28:12 np0005486730 haproxy[7]: 192.168.122.104:48542 [14/Oct/2025:08:28:12.765] redis redis/np0005486728.internalapi.localdomain 1/1/21 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:12 np0005486730 haproxy[7]: 192.168.122.110:46116 [14/Oct/2025:08:28:12.988] redis redis/np0005486728.internalapi.localdomain 1/0/9 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:13 np0005486730 haproxy[7]: 192.168.122.110:46102 [14/Oct/2025:08:28:12.765] redis redis/np0005486728.internalapi.localdomain 1/1/233 4428 -- 44/44/43/43/0 0/0
Oct 14 08:28:13 np0005486730 haproxy[7]: 192.168.122.104:48556 [14/Oct/2025:08:28:13.073] redis redis/np0005486728.internalapi.localdomain 1/0/9 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:13 np0005486730 haproxy[7]: 192.168.122.104:48552 [14/Oct/2025:08:28:12.822] redis redis/np0005486728.internalapi.localdomain 1/0/261 4428 -- 44/44/42/42/0 0/0
Oct 14 08:28:13 np0005486730 haproxy[7]: 192.168.122.104:48582 [14/Oct/2025:08:28:13.397] redis redis/np0005486728.internalapi.localdomain 1/0/15 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:13 np0005486730 haproxy[7]: 192.168.122.104:48568 [14/Oct/2025:08:28:13.117] redis redis/np0005486728.internalapi.localdomain 1/0/296 4428 -- 43/43/42/42/0 0/0
Oct 14 08:28:18 np0005486730 haproxy[7]: 192.168.122.110:46146 [14/Oct/2025:08:28:18.308] redis redis/np0005486728.internalapi.localdomain 1/0/8 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:18 np0005486730 haproxy[7]: 192.168.122.110:46130 [14/Oct/2025:08:28:18.029] redis redis/np0005486728.internalapi.localdomain 1/0/287 4427 -- 43/43/42/42/0 0/0
Oct 14 08:28:18 np0005486730 haproxy[7]: 192.168.122.110:46164 [14/Oct/2025:08:28:18.580] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:18 np0005486730 haproxy[7]: 192.168.122.110:46158 [14/Oct/2025:08:28:18.333] redis redis/np0005486728.internalapi.localdomain 1/0/258 4427 -- 44/44/43/43/0 0/0
Oct 14 08:28:18 np0005486730 haproxy[7]: 192.168.122.104:48606 [14/Oct/2025:08:28:18.738] redis redis/np0005486728.internalapi.localdomain 1/0/15 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:18 np0005486730 haproxy[7]: 192.168.122.104:48596 [14/Oct/2025:08:28:18.450] redis redis/np0005486728.internalapi.localdomain 1/0/303 4427 -- 44/44/43/43/0 0/0
Oct 14 08:28:18 np0005486730 haproxy[7]: 192.168.122.110:46170 [14/Oct/2025:08:28:18.851] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:18 np0005486730 haproxy[7]: 192.168.122.110:46166 [14/Oct/2025:08:28:18.621] redis redis/np0005486728.internalapi.localdomain 1/0/244 4429 -- 44/44/43/43/0 0/0
Oct 14 08:28:19 np0005486730 haproxy[7]: 192.168.122.104:48620 [14/Oct/2025:08:28:19.033] redis redis/np0005486728.internalapi.localdomain 1/0/13 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:19 np0005486730 haproxy[7]: 192.168.122.104:48612 [14/Oct/2025:08:28:18.783] redis redis/np0005486728.internalapi.localdomain 1/0/264 4428 -- 44/44/43/43/0 0/0
Oct 14 08:28:19 np0005486730 haproxy[7]: 192.168.122.110:46182 [14/Oct/2025:08:28:19.173] redis redis/np0005486728.internalapi.localdomain 1/1/10 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:19 np0005486730 haproxy[7]: 192.168.122.110:46174 [14/Oct/2025:08:28:18.895] redis redis/np0005486728.internalapi.localdomain 1/0/289 4428 -- 44/44/43/43/0 0/0
Oct 14 08:28:19 np0005486730 haproxy[7]: 192.168.122.104:48632 [14/Oct/2025:08:28:19.317] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:19 np0005486730 haproxy[7]: 192.168.122.104:48626 [14/Oct/2025:08:28:19.073] redis redis/np0005486728.internalapi.localdomain 1/0/254 4428 -- 43/43/42/42/0 0/0
Oct 14 08:28:19 np0005486730 haproxy[7]: 192.168.122.104:48658 [14/Oct/2025:08:28:19.602] redis redis/np0005486728.internalapi.localdomain 1/1/11 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:19 np0005486730 haproxy[7]: 192.168.122.104:48644 [14/Oct/2025:08:28:19.359] redis redis/np0005486728.internalapi.localdomain 1/0/255 4428 -- 44/44/42/42/0 0/0
Oct 14 08:28:24 np0005486730 haproxy[7]: 192.168.122.110:46082 [14/Oct/2025:08:28:24.458] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:24 np0005486730 haproxy[7]: 192.168.122.110:46080 [14/Oct/2025:08:28:24.219] redis redis/np0005486728.internalapi.localdomain 1/0/251 4427 -- 43/43/42/42/0 0/0
Oct 14 08:28:24 np0005486730 haproxy[7]: 192.168.122.110:46084 [14/Oct/2025:08:28:24.486] redis redis/np0005486728.internalapi.localdomain 1/0/251 4428 -- 45/45/43/43/0 0/0
Oct 14 08:28:24 np0005486730 haproxy[7]: 192.168.122.110:46090 [14/Oct/2025:08:28:24.724] redis redis/np0005486728.internalapi.localdomain 1/0/13 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:24 np0005486730 haproxy[7]: 192.168.122.104:40662 [14/Oct/2025:08:28:24.908] redis redis/np0005486728.internalapi.localdomain 1/0/13 10 -- 45/45/44/43/0 0/0
Oct 14 08:28:24 np0005486730 haproxy[7]: 192.168.122.104:40656 [14/Oct/2025:08:28:24.649] redis redis/np0005486728.internalapi.localdomain 1/0/271 4428 -- 45/45/43/43/0 0/0
Oct 14 08:28:25 np0005486730 haproxy[7]: 192.168.122.110:46092 [14/Oct/2025:08:28:24.766] redis redis/np0005486728.internalapi.localdomain 1/0/267 4429 -- 45/45/44/44/0 0/0
Oct 14 08:28:25 np0005486730 haproxy[7]: 192.168.122.110:46094 [14/Oct/2025:08:28:25.014] redis redis/np0005486728.internalapi.localdomain 1/1/18 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:25 np0005486730 haproxy[7]: 192.168.122.104:40682 [14/Oct/2025:08:28:25.251] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:25 np0005486730 haproxy[7]: 192.168.122.104:40668 [14/Oct/2025:08:28:24.944] redis redis/np0005486728.internalapi.localdomain 1/0/318 4429 -- 45/45/43/43/0 0/0
Oct 14 08:28:25 np0005486730 haproxy[7]: 192.168.122.110:46114 [14/Oct/2025:08:28:25.332] redis redis/np0005486728.internalapi.localdomain 1/0/9 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:25 np0005486730 haproxy[7]: 192.168.122.110:46108 [14/Oct/2025:08:28:25.060] redis redis/np0005486728.internalapi.localdomain 1/0/280 4429 -- 44/44/43/43/0 0/0
Oct 14 08:28:25 np0005486730 haproxy[7]: 192.168.122.104:40696 [14/Oct/2025:08:28:25.544] redis redis/np0005486728.internalapi.localdomain 1/0/18 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:25 np0005486730 haproxy[7]: 192.168.122.104:40692 [14/Oct/2025:08:28:25.295] redis redis/np0005486728.internalapi.localdomain 1/0/267 4429 -- 44/44/42/42/0 0/0
Oct 14 08:28:25 np0005486730 haproxy[7]: 192.168.122.104:40712 [14/Oct/2025:08:28:25.820] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:25 np0005486730 haproxy[7]: 192.168.122.104:40708 [14/Oct/2025:08:28:25.593] redis redis/np0005486728.internalapi.localdomain 1/0/239 4429 -- 44/44/42/42/0 0/0
Oct 14 08:28:30 np0005486730 haproxy[7]: 192.168.122.110:46120 [14/Oct/2025:08:28:30.605] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:30 np0005486730 haproxy[7]: 192.168.122.110:46118 [14/Oct/2025:08:28:30.372] redis redis/np0005486728.internalapi.localdomain 1/0/248 4428 -- 43/43/42/42/0 0/0
Oct 14 08:28:30 np0005486730 haproxy[7]: 192.168.122.110:46138 [14/Oct/2025:08:28:30.875] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:30 np0005486730 haproxy[7]: 192.168.122.110:46124 [14/Oct/2025:08:28:30.641] redis redis/np0005486728.internalapi.localdomain 1/0/247 4428 -- 44/44/43/43/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.104:40726 [14/Oct/2025:08:28:31.117] redis redis/np0005486728.internalapi.localdomain 1/1/15 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.104:40720 [14/Oct/2025:08:28:30.862] redis redis/np0005486728.internalapi.localdomain 1/0/272 4429 -- 45/45/43/43/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.110:46152 [14/Oct/2025:08:28:30.913] redis redis/np0005486728.internalapi.localdomain 1/0/292 4429 -- 45/45/44/44/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.110:46160 [14/Oct/2025:08:28:31.194] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.104:40742 [14/Oct/2025:08:28:31.151] redis redis/np0005486728.internalapi.localdomain 1/0/259 4429 -- 45/45/44/44/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.104:40750 [14/Oct/2025:08:28:31.399] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/43/43/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.110:46168 [14/Oct/2025:08:28:31.233] redis redis/np0005486728.internalapi.localdomain 1/0/290 4429 -- 45/45/44/44/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.110:46172 [14/Oct/2025:08:28:31.498] redis redis/np0005486728.internalapi.localdomain 1/0/26 10 -- 45/45/43/43/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.104:38368 [14/Oct/2025:08:28:31.658] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.104:40760 [14/Oct/2025:08:28:31.427] redis redis/np0005486728.internalapi.localdomain 1/1/243 4429 -- 43/43/42/42/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.104:38376 [14/Oct/2025:08:28:31.690] redis redis/np0005486728.internalapi.localdomain 1/0/221 4429 -- 44/44/43/43/0 0/0
Oct 14 08:28:31 np0005486730 haproxy[7]: 192.168.122.104:38378 [14/Oct/2025:08:28:31.896] redis redis/np0005486728.internalapi.localdomain 1/0/15 10 -- 44/44/42/42/0 0/0
Oct 14 08:28:36 np0005486730 haproxy[7]: 192.168.122.110:50626 [14/Oct/2025:08:28:36.815] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:36 np0005486730 haproxy[7]: 192.168.122.110:50612 [14/Oct/2025:08:28:36.547] redis redis/np0005486728.internalapi.localdomain 1/0/277 4429 -- 43/43/42/42/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.110:50642 [14/Oct/2025:08:28:37.091] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.110:50638 [14/Oct/2025:08:28:36.850] redis redis/np0005486728.internalapi.localdomain 1/0/252 4430 -- 45/45/43/43/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.104:38380 [14/Oct/2025:08:28:36.937] redis redis/np0005486728.internalapi.localdomain 1/0/236 4430 -- 45/45/44/44/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.104:38386 [14/Oct/2025:08:28:37.161] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/43/43/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.110:50656 [14/Oct/2025:08:28:37.374] redis redis/np0005486728.internalapi.localdomain 1/0/8 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.110:50652 [14/Oct/2025:08:28:37.128] redis redis/np0005486728.internalapi.localdomain 1/0/254 4431 -- 44/44/43/43/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.104:38390 [14/Oct/2025:08:28:37.448] redis redis/np0005486728.internalapi.localdomain 1/0/17 10 -- 45/45/43/43/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.104:38388 [14/Oct/2025:08:28:37.201] redis redis/np0005486728.internalapi.localdomain 1/0/265 4431 -- 45/45/43/43/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.110:50678 [14/Oct/2025:08:28:37.709] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.110:50664 [14/Oct/2025:08:28:37.408] redis redis/np0005486728.internalapi.localdomain 1/0/311 4431 -- 45/45/43/43/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.104:38400 [14/Oct/2025:08:28:37.753] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:37 np0005486730 haproxy[7]: 192.168.122.104:38398 [14/Oct/2025:08:28:37.495] redis redis/np0005486728.internalapi.localdomain 1/0/270 4431 -- 44/44/42/42/0 0/0
Oct 14 08:28:38 np0005486730 haproxy[7]: 192.168.122.104:38412 [14/Oct/2025:08:28:38.080] redis redis/np0005486728.internalapi.localdomain 1/0/16 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:38 np0005486730 haproxy[7]: 192.168.122.104:38408 [14/Oct/2025:08:28:37.801] redis redis/np0005486728.internalapi.localdomain 1/0/296 4431 -- 44/44/42/42/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.110:47054 [14/Oct/2025:08:28:43.041] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.110:47042 [14/Oct/2025:08:28:42.760] redis redis/np0005486728.internalapi.localdomain 1/0/291 4428 -- 43/43/42/42/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.110:47076 [14/Oct/2025:08:28:43.326] redis redis/np0005486728.internalapi.localdomain 1/0/9 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.110:47066 [14/Oct/2025:08:28:43.070] redis redis/np0005486728.internalapi.localdomain 1/0/266 4428 -- 45/45/43/43/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.104:50134 [14/Oct/2025:08:28:43.378] redis redis/np0005486728.internalapi.localdomain 1/0/17 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.104:50130 [14/Oct/2025:08:28:43.129] redis redis/np0005486728.internalapi.localdomain 1/0/266 4429 -- 45/45/43/43/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.110:47090 [14/Oct/2025:08:28:43.597] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.110:47086 [14/Oct/2025:08:28:43.356] redis redis/np0005486728.internalapi.localdomain 1/0/254 4429 -- 44/44/43/43/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.104:50156 [14/Oct/2025:08:28:43.681] redis redis/np0005486728.internalapi.localdomain 1/0/13 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.104:50142 [14/Oct/2025:08:28:43.416] redis redis/np0005486728.internalapi.localdomain 1/0/278 4429 -- 44/44/43/43/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.110:47092 [14/Oct/2025:08:28:43.633] redis redis/np0005486728.internalapi.localdomain 1/0/228 4429 -- 45/45/43/43/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.110:47104 [14/Oct/2025:08:28:43.843] redis redis/np0005486728.internalapi.localdomain 1/0/18 10 -- 45/45/43/43/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.104:50170 [14/Oct/2025:08:28:43.958] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:43 np0005486730 haproxy[7]: 192.168.122.104:50166 [14/Oct/2025:08:28:43.713] redis redis/np0005486728.internalapi.localdomain 1/0/257 4429 -- 43/43/42/42/0 0/0
Oct 14 08:28:44 np0005486730 haproxy[7]: 192.168.122.104:50194 [14/Oct/2025:08:28:44.236] redis redis/np0005486728.internalapi.localdomain 1/0/16 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:44 np0005486730 haproxy[7]: 192.168.122.104:50178 [14/Oct/2025:08:28:43.997] redis redis/np0005486728.internalapi.localdomain 1/0/255 4429 -- 44/44/42/42/0 0/0
Oct 14 08:28:49 np0005486730 haproxy[7]: 192.168.122.110:47118 [14/Oct/2025:08:28:49.151] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:49 np0005486730 haproxy[7]: 192.168.122.110:47112 [14/Oct/2025:08:28:48.903] redis redis/np0005486728.internalapi.localdomain 1/0/263 4429 -- 43/43/42/42/0 0/0
Oct 14 08:28:49 np0005486730 haproxy[7]: 192.168.122.110:47150 [14/Oct/2025:08:28:49.439] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:49 np0005486730 haproxy[7]: 192.168.122.110:47134 [14/Oct/2025:08:28:49.198] redis redis/np0005486728.internalapi.localdomain 1/0/251 4429 -- 44/44/43/43/0 0/0
Oct 14 08:28:49 np0005486730 haproxy[7]: 192.168.122.104:50210 [14/Oct/2025:08:28:49.549] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:49 np0005486730 haproxy[7]: 192.168.122.104:50204 [14/Oct/2025:08:28:49.292] redis redis/np0005486728.internalapi.localdomain 1/0/270 4429 -- 45/45/43/43/0 0/0
Oct 14 08:28:49 np0005486730 haproxy[7]: 192.168.122.110:47174 [14/Oct/2025:08:28:49.683] redis redis/np0005486728.internalapi.localdomain 1/0/67 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:49 np0005486730 haproxy[7]: 192.168.122.110:47164 [14/Oct/2025:08:28:49.477] redis redis/np0005486728.internalapi.localdomain 1/0/273 4430 -- 44/44/43/43/0 0/0
Oct 14 08:28:49 np0005486730 haproxy[7]: 192.168.122.104:50236 [14/Oct/2025:08:28:49.799] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:49 np0005486730 haproxy[7]: 192.168.122.104:50226 [14/Oct/2025:08:28:49.582] redis redis/np0005486728.internalapi.localdomain 1/0/228 4430 -- 44/44/43/43/0 0/0
Oct 14 08:28:50 np0005486730 haproxy[7]: 192.168.122.110:47176 [14/Oct/2025:08:28:49.777] redis redis/np0005486728.internalapi.localdomain 1/0/279 4430 -- 45/45/43/43/0 0/0
Oct 14 08:28:50 np0005486730 haproxy[7]: 192.168.122.110:47192 [14/Oct/2025:08:28:50.044] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/43/43/0 0/0
Oct 14 08:28:50 np0005486730 haproxy[7]: 192.168.122.104:50240 [14/Oct/2025:08:28:49.842] redis redis/np0005486728.internalapi.localdomain 1/0/267 4430 -- 44/44/43/43/0 0/0
Oct 14 08:28:50 np0005486730 haproxy[7]: 192.168.122.104:50248 [14/Oct/2025:08:28:50.098] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 43/43/42/42/0 0/0
Oct 14 08:28:50 np0005486730 haproxy[7]: 192.168.122.104:50266 [14/Oct/2025:08:28:50.378] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:50 np0005486730 haproxy[7]: 192.168.122.104:50262 [14/Oct/2025:08:28:50.140] redis redis/np0005486728.internalapi.localdomain 1/0/249 4430 -- 43/43/42/42/0 0/0
Oct 14 08:28:55 np0005486730 haproxy[7]: 192.168.122.110:46494 [14/Oct/2025:08:28:55.316] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:55 np0005486730 haproxy[7]: 192.168.122.110:46480 [14/Oct/2025:08:28:55.084] redis redis/np0005486728.internalapi.localdomain 1/0/245 4429 -- 43/43/42/42/0 0/0
Oct 14 08:28:55 np0005486730 haproxy[7]: 192.168.122.110:46506 [14/Oct/2025:08:28:55.560] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:55 np0005486730 haproxy[7]: 192.168.122.110:46502 [14/Oct/2025:08:28:55.347] redis redis/np0005486728.internalapi.localdomain 1/0/223 4429 -- 45/45/43/43/0 0/0
Oct 14 08:28:55 np0005486730 haproxy[7]: 192.168.122.104:60088 [14/Oct/2025:08:28:55.662] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:55 np0005486730 haproxy[7]: 192.168.122.104:60072 [14/Oct/2025:08:28:55.425] redis redis/np0005486728.internalapi.localdomain 1/0/248 4430 -- 44/44/43/43/0 0/0
Oct 14 08:28:55 np0005486730 haproxy[7]: 192.168.122.110:46526 [14/Oct/2025:08:28:55.843] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:55 np0005486730 haproxy[7]: 192.168.122.110:46520 [14/Oct/2025:08:28:55.597] redis redis/np0005486728.internalapi.localdomain 1/0/256 4430 -- 44/44/43/43/0 0/0
Oct 14 08:28:55 np0005486730 haproxy[7]: 192.168.122.104:60106 [14/Oct/2025:08:28:55.980] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:55 np0005486730 haproxy[7]: 192.168.122.104:60094 [14/Oct/2025:08:28:55.708] redis redis/np0005486728.internalapi.localdomain 1/0/283 4430 -- 44/44/43/43/0 0/0
Oct 14 08:28:56 np0005486730 haproxy[7]: 192.168.122.110:46536 [14/Oct/2025:08:28:56.079] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 45/45/44/44/0 0/0
Oct 14 08:28:56 np0005486730 haproxy[7]: 192.168.122.110:46532 [14/Oct/2025:08:28:55.872] redis redis/np0005486728.internalapi.localdomain 1/0/218 4430 -- 44/44/43/43/0 0/0
Oct 14 08:28:56 np0005486730 haproxy[7]: 192.168.122.104:60136 [14/Oct/2025:08:28:56.258] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:56 np0005486730 haproxy[7]: 192.168.122.104:60120 [14/Oct/2025:08:28:56.018] redis redis/np0005486728.internalapi.localdomain 1/0/254 4430 -- 44/44/42/42/0 0/0
Oct 14 08:28:56 np0005486730 haproxy[7]: 192.168.122.104:60156 [14/Oct/2025:08:28:56.539] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 44/44/43/43/0 0/0
Oct 14 08:28:56 np0005486730 haproxy[7]: 192.168.122.104:60152 [14/Oct/2025:08:28:56.301] redis redis/np0005486728.internalapi.localdomain 1/0/249 4430 -- 44/44/42/42/0 0/0
Oct 14 08:29:01 np0005486730 haproxy[7]: 192.168.122.110:46556 [14/Oct/2025:08:29:01.365] redis redis/np0005486728.internalapi.localdomain 1/0/16 10 -- 44/44/43/43/0 0/0
Oct 14 08:29:01 np0005486730 haproxy[7]: 192.168.122.110:46544 [14/Oct/2025:08:29:01.128] redis redis/np0005486728.internalapi.localdomain 1/1/253 4429 -- 43/43/42/42/0 0/0
Oct 14 08:29:01 np0005486730 haproxy[7]: 192.168.122.110:46574 [14/Oct/2025:08:29:01.648] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/43/43/0 0/0
Oct 14 08:29:01 np0005486730 haproxy[7]: 192.168.122.110:46562 [14/Oct/2025:08:29:01.399] redis redis/np0005486728.internalapi.localdomain 1/0/260 4429 -- 45/45/43/43/0 0/0
Oct 14 08:29:01 np0005486730 haproxy[7]: 192.168.122.104:43764 [14/Oct/2025:08:29:01.844] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:01 np0005486730 haproxy[7]: 192.168.122.104:43754 [14/Oct/2025:08:29:01.576] redis redis/np0005486728.internalapi.localdomain 1/0/282 4430 -- 45/45/43/43/0 0/0
Oct 14 08:29:01 np0005486730 haproxy[7]: 192.168.122.110:46592 [14/Oct/2025:08:29:01.930] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:01 np0005486730 haproxy[7]: 192.168.122.110:46584 [14/Oct/2025:08:29:01.693] redis redis/np0005486728.internalapi.localdomain 1/1/248 4430 -- 44/44/43/43/0 0/0
Oct 14 08:29:02 np0005486730 haproxy[7]: 192.168.122.104:43778 [14/Oct/2025:08:29:02.103] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:02 np0005486730 haproxy[7]: 192.168.122.104:43772 [14/Oct/2025:08:29:01.880] redis redis/np0005486728.internalapi.localdomain 1/0/236 4430 -- 45/45/43/43/0 0/0
Oct 14 08:29:02 np0005486730 haproxy[7]: 192.168.122.110:46598 [14/Oct/2025:08:29:01.969] redis redis/np0005486728.internalapi.localdomain 1/0/249 4431 -- 45/45/43/43/0 0/0
Oct 14 08:29:02 np0005486730 haproxy[7]: 192.168.122.110:46604 [14/Oct/2025:08:29:02.206] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/43/43/0 0/0
Oct 14 08:29:02 np0005486730 haproxy[7]: 192.168.122.104:43804 [14/Oct/2025:08:29:02.374] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 44/44/43/43/0 0/0
Oct 14 08:29:02 np0005486730 haproxy[7]: 192.168.122.104:43788 [14/Oct/2025:08:29:02.138] redis redis/np0005486728.internalapi.localdomain 1/0/250 4431 -- 44/44/42/42/0 0/0
Oct 14 08:29:02 np0005486730 haproxy[7]: 192.168.122.104:43826 [14/Oct/2025:08:29:02.649] redis redis/np0005486728.internalapi.localdomain 1/0/8 10 -- 44/44/42/42/0 0/0
Oct 14 08:29:02 np0005486730 haproxy[7]: 192.168.122.104:43818 [14/Oct/2025:08:29:02.418] redis redis/np0005486728.internalapi.localdomain 1/0/239 4431 -- 44/44/42/42/0 0/0
Oct 14 08:29:07 np0005486730 haproxy[7]: 192.168.122.110:44570 [14/Oct/2025:08:29:07.495] redis redis/np0005486728.internalapi.localdomain 1/0/15 10 -- 44/44/43/43/0 0/0
Oct 14 08:29:07 np0005486730 haproxy[7]: 192.168.122.110:44556 [14/Oct/2025:08:29:07.245] redis redis/np0005486728.internalapi.localdomain 1/0/265 4430 -- 43/43/42/42/0 0/0
Oct 14 08:29:07 np0005486730 haproxy[7]: 192.168.122.110:44576 [14/Oct/2025:08:29:07.812] redis redis/np0005486728.internalapi.localdomain 1/0/13 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:07 np0005486730 haproxy[7]: 192.168.122.110:44572 [14/Oct/2025:08:29:07.545] redis redis/np0005486728.internalapi.localdomain 1/0/280 4431 -- 45/45/43/43/0 0/0
Oct 14 08:29:07 np0005486730 haproxy[7]: 192.168.122.104:43844 [14/Oct/2025:08:29:07.924] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:07 np0005486730 haproxy[7]: 192.168.122.104:43828 [14/Oct/2025:08:29:07.691] redis redis/np0005486728.internalapi.localdomain 1/0/244 4431 -- 45/45/43/43/0 0/0
Oct 14 08:29:08 np0005486730 haproxy[7]: 192.168.122.110:44590 [14/Oct/2025:08:29:08.104] redis redis/np0005486728.internalapi.localdomain 1/0/13 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:08 np0005486730 haproxy[7]: 192.168.122.110:44578 [14/Oct/2025:08:29:07.856] redis redis/np0005486728.internalapi.localdomain 1/0/262 4433 -- 44/44/43/43/0 0/0
Oct 14 08:29:08 np0005486730 haproxy[7]: 192.168.122.104:43858 [14/Oct/2025:08:29:08.157] redis redis/np0005486728.internalapi.localdomain 1/0/8 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:08 np0005486730 haproxy[7]: 192.168.122.104:43856 [14/Oct/2025:08:29:07.951] redis redis/np0005486728.internalapi.localdomain 1/0/216 4433 -- 45/45/43/43/0 0/0
Oct 14 08:29:08 np0005486730 haproxy[7]: 192.168.122.110:44606 [14/Oct/2025:08:29:08.382] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:08 np0005486730 haproxy[7]: 192.168.122.110:44598 [14/Oct/2025:08:29:08.138] redis redis/np0005486728.internalapi.localdomain 1/0/255 4433 -- 45/45/43/43/0 0/0
Oct 14 08:29:08 np0005486730 haproxy[7]: 192.168.122.104:43874 [14/Oct/2025:08:29:08.449] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0
Oct 14 08:29:08 np0005486730 haproxy[7]: 192.168.122.104:43860 [14/Oct/2025:08:29:08.194] redis redis/np0005486728.internalapi.localdomain 1/0/268 4433 -- 44/44/42/42/0 0/0
Oct 14 08:29:08 np0005486730 haproxy[7]: 192.168.122.104:43878 [14/Oct/2025:08:29:08.492] redis redis/np0005486728.internalapi.localdomain 1/0/284 4433 -- 44/44/43/43/0 0/0
Oct 14 08:29:08 np0005486730 haproxy[7]: 192.168.122.104:43888 [14/Oct/2025:08:29:08.759] redis redis/np0005486728.internalapi.localdomain 1/0/17 10 -- 43/43/42/42/0 0/0
Oct 14 08:29:13 np0005486730 haproxy[7]: 192.168.122.110:34762 [14/Oct/2025:08:29:13.678] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 44/44/43/43/0 0/0
Oct 14 08:29:13 np0005486730 haproxy[7]: 192.168.122.110:34748 [14/Oct/2025:08:29:13.420] redis redis/np0005486728.internalapi.localdomain 1/0/272 4432 -- 43/43/42/42/0 0/0
Oct 14 08:29:13 np0005486730 haproxy[7]: 192.168.122.110:34776 [14/Oct/2025:08:29:13.708] redis redis/np0005486728.internalapi.localdomain 1/0/224 4432 -- 45/45/44/44/0 0/0
Oct 14 08:29:13 np0005486730 haproxy[7]: 192.168.122.110:34784 [14/Oct/2025:08:29:13.916] redis redis/np0005486728.internalapi.localdomain 1/0/16 10 -- 45/45/43/43/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.104:47650 [14/Oct/2025:08:29:14.112] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.104:47640 [14/Oct/2025:08:29:13.811] redis redis/np0005486728.internalapi.localdomain 1/0/314 4432 -- 45/45/43/43/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.110:34796 [14/Oct/2025:08:29:14.215] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.110:34786 [14/Oct/2025:08:29:13.960] redis redis/np0005486728.internalapi.localdomain 1/1/270 4433 -- 44/44/43/43/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.104:47654 [14/Oct/2025:08:29:14.141] redis redis/np0005486728.internalapi.localdomain 1/0/224 4433 -- 45/45/43/43/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.104:47664 [14/Oct/2025:08:29:14.353] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 45/45/43/43/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.110:34814 [14/Oct/2025:08:29:14.500] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.110:34806 [14/Oct/2025:08:29:14.258] redis redis/np0005486728.internalapi.localdomain 1/0/256 4433 -- 44/44/43/43/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.104:47678 [14/Oct/2025:08:29:14.403] redis redis/np0005486728.internalapi.localdomain 1/0/258 4433 -- 44/44/43/43/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.104:47684 [14/Oct/2025:08:29:14.649] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 44/44/42/42/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.104:47692 [14/Oct/2025:08:29:14.689] redis redis/np0005486728.internalapi.localdomain 1/0/251 4433 -- 44/44/42/42/0 0/0
Oct 14 08:29:14 np0005486730 haproxy[7]: 192.168.122.104:47708 [14/Oct/2025:08:29:14.927] redis redis/np0005486728.internalapi.localdomain 1/0/13 10 -- 44/44/42/42/0 0/0
Oct 14 08:29:19 np0005486730 haproxy[7]: 192.168.122.110:34830 [14/Oct/2025:08:29:19.813] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 44/44/43/43/0 0/0
Oct 14 08:29:19 np0005486730 haproxy[7]: 192.168.122.110:34826 [14/Oct/2025:08:29:19.554] redis redis/np0005486728.internalapi.localdomain 1/0/270 4432 -- 43/43/42/42/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.110:34848 [14/Oct/2025:08:29:20.116] redis redis/np0005486728.internalapi.localdomain 1/0/11 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.110:34846 [14/Oct/2025:08:29:19.867] redis redis/np0005486728.internalapi.localdomain 1/0/261 4432 -- 45/45/43/43/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.104:47724 [14/Oct/2025:08:29:20.230] redis redis/np0005486728.internalapi.localdomain 1/0/13 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.104:47712 [14/Oct/2025:08:29:19.972] redis redis/np0005486728.internalapi.localdomain 1/0/272 4432 -- 45/45/43/43/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.110:34876 [14/Oct/2025:08:29:20.388] redis redis/np0005486728.internalapi.localdomain 1/0/10 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.110:34864 [14/Oct/2025:08:29:20.150] redis redis/np0005486728.internalapi.localdomain 1/0/249 4433 -- 44/44/43/43/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.104:47742 [14/Oct/2025:08:29:20.472] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 45/45/44/44/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.104:47730 [14/Oct/2025:08:29:20.263] redis redis/np0005486728.internalapi.localdomain 1/0/224 4433 -- 45/45/43/43/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.110:34896 [14/Oct/2025:08:29:20.640] redis redis/np0005486728.internalapi.localdomain 1/0/14 10 -- 45/45/43/43/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.110:34890 [14/Oct/2025:08:29:20.419] redis redis/np0005486728.internalapi.localdomain 1/0/235 4433 -- 45/45/43/43/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.104:47760 [14/Oct/2025:08:29:20.771] redis redis/np0005486728.internalapi.localdomain 1/0/13 10 -- 44/44/43/43/0 0/0
Oct 14 08:29:20 np0005486730 haproxy[7]: 192.168.122.104:47758 [14/Oct/2025:08:29:20.523] redis redis/np0005486728.internalapi.localdomain 1/0/262 4433 -- 43/43/42/42/0 0/0
Oct 14 08:29:21 np0005486730 haproxy[7]: 192.168.122.104:47788 [14/Oct/2025:08:29:21.093] redis redis/np0005486728.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0
Oct 14 08:29:21 np0005486730 haproxy[7]: 192.168.122.104:47774 [14/Oct/2025:08:29:20.815] redis redis/np0005486728.internalapi.localdomain 1/0/291 4433 -- 43/43/42/42/0 0/0
Oct 14 08:29:25 np0005486730 haproxy[7]: 192.168.122.103:56036 [14/Oct/2025:08:29:25.894] redis redis/np0005486728.internalapi.localdomain 1/0/39 14 -- 44/44/43/43/0 0/0
Oct 14 08:29:31 np0005486730 haproxy[7]: Server gnocchi/np0005486728.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 3ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Oct 14 08:41:05 np0005486730 haproxy[7]: Server aodh/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:41:09 np0005486730 haproxy[7]: Server aodh/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:41:09 np0005486730 haproxy[7]: 192.168.122.103:46728 [14/Oct/2025:08:23:45.098] redis redis/np0005486728.internalapi.localdomain 1/0/1044878 22368 -- 83/83/82/82/0 0/0
Oct 14 08:41:09 np0005486730 haproxy[7]: 192.168.122.103:53536 [14/Oct/2025:08:24:45.407] redis redis/np0005486728.internalapi.localdomain 1/0/984573 16919 -- 82/82/81/81/0 0/0
Oct 14 08:41:09 np0005486730 haproxy[7]: 192.168.122.103:46750 [14/Oct/2025:08:23:45.354] redis redis/np0005486728.internalapi.localdomain 1/0/1044626 5479 -- 81/81/80/80/0 0/0
Oct 14 08:41:09 np0005486730 haproxy[7]: 192.168.122.103:46724 [14/Oct/2025:08:23:44.801] redis redis/np0005486728.internalapi.localdomain 1/0/1045179 22406 -- 80/80/79/79/0 0/0
Oct 14 08:41:09 np0005486730 haproxy[7]: 192.168.122.103:46744 [14/Oct/2025:08:23:45.141] redis redis/np0005486728.internalapi.localdomain 1/0/1044851 22426 -- 79/79/78/78/0 0/0
Oct 14 08:41:11 np0005486730 haproxy[7]: 192.168.122.104:60750 [14/Oct/2025:08:24:01.551] redis redis/np0005486728.internalapi.localdomain 1/0/1029664 22302 -- 78/78/77/77/0 0/0
Oct 14 08:41:11 np0005486730 haproxy[7]: 192.168.122.104:56750 [14/Oct/2025:08:24:01.883] redis redis/np0005486728.internalapi.localdomain 1/0/1029332 22296 -- 78/78/76/76/0 0/0
Oct 14 08:41:11 np0005486730 haproxy[7]: 192.168.122.104:56760 [14/Oct/2025:08:24:01.941] redis redis/np0005486728.internalapi.localdomain 1/0/1029280 22352 -- 76/76/75/75/0 0/0
Oct 14 08:41:11 np0005486730 haproxy[7]: 192.168.122.104:56736 [14/Oct/2025:08:24:01.657] redis redis/np0005486728.internalapi.localdomain 1/2/1029566 22352 -- 75/75/74/74/0 0/0
Oct 14 08:41:12 np0005486730 haproxy[7]: 192.168.122.110:37278 [14/Oct/2025:08:23:58.249] redis redis/np0005486728.internalapi.localdomain 1/0/1034110 22347 -- 74/74/73/73/0 0/0
Oct 14 08:41:12 np0005486730 haproxy[7]: 192.168.122.110:37300 [14/Oct/2025:08:23:58.494] redis redis/np0005486728.internalapi.localdomain 1/0/1033869 22379 -- 73/73/72/72/0 0/0
Oct 14 08:41:12 np0005486730 haproxy[7]: 192.168.122.110:56806 [14/Oct/2025:08:24:58.514] redis redis/np0005486728.internalapi.localdomain 1/0/973848 16897 -- 72/72/71/71/0 0/0
Oct 14 08:41:12 np0005486730 haproxy[7]: 192.168.122.110:37292 [14/Oct/2025:08:23:58.438] redis redis/np0005486728.internalapi.localdomain 1/0/1033925 5487 -- 71/71/70/70/0 0/0
Oct 14 08:41:12 np0005486730 haproxy[7]: 192.168.122.110:37288 [14/Oct/2025:08:23:58.404] redis redis/np0005486728.internalapi.localdomain 1/0/1033961 5486 -- 70/70/69/69/0 0/0
Oct 14 08:41:12 np0005486730 haproxy[7]: 192.168.122.110:56802 [14/Oct/2025:08:24:58.481] redis redis/np0005486728.internalapi.localdomain 1/0/973886 16897 -- 69/69/68/68/0 0/0
Oct 14 08:41:13 np0005486730 haproxy[7]: Server aodh/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:41:13 np0005486730 haproxy[7]: proxy aodh has no server available!
Oct 14 08:43:14 np0005486730 haproxy[7]: 192.168.122.103:46732 [14/Oct/2025:08:23:45.121] redis redis/np0005486728.internalapi.localdomain 1/0/1169523 1533 -- 68/68/67/67/0 0/0
Oct 14 08:43:14 np0005486730 haproxy[7]: 192.168.122.103:46730 [14/Oct/2025:08:23:45.102] redis redis/np0005486728.internalapi.localdomain 1/0/1169542 4409 -- 67/67/66/66/0 0/0
Oct 14 08:43:16 np0005486730 haproxy[7]: 192.168.122.104:56762 [14/Oct/2025:08:24:02.094] redis redis/np0005486728.internalapi.localdomain 1/10/1154022 6270 -- 66/66/65/65/0 0/0
Oct 14 08:43:17 np0005486730 haproxy[7]: 192.168.122.110:37268 [14/Oct/2025:08:23:58.212] redis redis/np0005486728.internalapi.localdomain 1/0/1159035 6100 -- 65/65/64/64/0 0/0
Oct 14 08:44:03 np0005486730 haproxy[7]: Server horizon/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:07 np0005486730 haproxy[7]: Server horizon/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:11 np0005486730 haproxy[7]: Server horizon/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:11 np0005486730 haproxy[7]: proxy horizon has no server available!
Oct 14 08:44:15 np0005486730 haproxy[7]: Server keystone_public/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:15 np0005486730 haproxy[7]: Server keystone_admin/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 2ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:19 np0005486730 haproxy[7]: Server keystone_public/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:19 np0005486730 haproxy[7]: Server keystone_admin/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 2ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:23 np0005486730 haproxy[7]: Server keystone_public/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:23 np0005486730 haproxy[7]: proxy keystone_public has no server available!
Oct 14 08:44:23 np0005486730 haproxy[7]: Server keystone_admin/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:23 np0005486730 haproxy[7]: proxy keystone_admin has no server available!
Oct 14 08:44:30 np0005486730 haproxy[7]: Server cinder/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:34 np0005486730 haproxy[7]: Server cinder/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:38 np0005486730 haproxy[7]: Server cinder/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:44:38 np0005486730 haproxy[7]: proxy cinder has no server available!
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:52690 [14/Oct/2025:08:36:15.437] redis redis/np0005486728.internalapi.localdomain 1/0/563514 78 -- 65/65/64/64/0 0/0
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:51692 [14/Oct/2025:08:29:29.771] redis redis/np0005486728.internalapi.localdomain 1/0/969181 4758 -- 65/65/63/63/0 0/0
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:51746 [14/Oct/2025:08:29:32.920] redis redis/np0005486728.internalapi.localdomain 1/0/966031 4759 -- 65/65/62/62/0 0/0
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:52530 [14/Oct/2025:08:38:41.625] redis redis/np0005486728.internalapi.localdomain 1/0/417325 38 -- 62/62/60/60/0 0/0
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:51644 [14/Oct/2025:08:29:29.443] redis redis/np0005486728.internalapi.localdomain 1/0/969509 4756 -- 62/62/60/60/0 0/0
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:51770 [14/Oct/2025:08:29:33.610] redis redis/np0005486728.internalapi.localdomain 1/0/965342 4758 -- 60/60/59/59/0 0/0
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:47178 [14/Oct/2025:08:37:16.356] redis redis/np0005486728.internalapi.localdomain 1/0/502600 38 -- 59/59/58/58/0 0/0
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:51724 [14/Oct/2025:08:29:29.829] redis redis/np0005486728.internalapi.localdomain 1/0/969127 4758 -- 58/58/56/56/0 0/0
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:51732 [14/Oct/2025:08:29:32.373] redis redis/np0005486728.internalapi.localdomain 1/0/966583 4760 -- 59/59/57/57/0 0/0
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:52540 [14/Oct/2025:08:38:41.701] redis redis/np0005486728.internalapi.localdomain 1/0/417254 46 -- 58/58/55/55/0 0/0
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:51682 [14/Oct/2025:08:29:29.721] redis redis/np0005486728.internalapi.localdomain 1/0/969237 4758 -- 55/55/54/54/0 0/0
Oct 14 08:45:38 np0005486730 haproxy[7]: 192.168.122.103:51762 [14/Oct/2025:08:29:33.169] redis redis/np0005486728.internalapi.localdomain 1/0/965788 4758 -- 55/55/53/53/0 0/0
Oct 14 08:45:41 np0005486730 haproxy[7]: Server glance_api/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:45:42 np0005486730 haproxy[7]: Server glance_api/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:43902 [14/Oct/2025:08:38:41.560] redis redis/np0005486728.internalapi.localdomain 1/0/421632 46 -- 53/53/52/52/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:60062 [14/Oct/2025:08:28:00.375] redis redis/np0005486728.internalapi.localdomain 1/0/1062819 4778 -- 53/53/51/51/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:59420 [14/Oct/2025:08:29:32.014] redis redis/np0005486728.internalapi.localdomain 1/0/971179 4758 -- 51/51/50/50/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:41920 [14/Oct/2025:08:29:31.294] redis redis/np0005486728.internalapi.localdomain 1/0/971902 4760 -- 50/50/49/49/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:51626 [14/Oct/2025:08:28:01.807] redis redis/np0005486728.internalapi.localdomain 1/0/1061389 4778 -- 50/50/48/48/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:34880 [14/Oct/2025:08:38:41.550] redis redis/np0005486728.internalapi.localdomain 1/0/421646 30 -- 48/48/47/47/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:59408 [14/Oct/2025:08:29:31.687] redis redis/np0005486728.internalapi.localdomain 1/0/971516 4760 -- 47/47/46/46/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:45724 [14/Oct/2025:08:36:15.429] redis redis/np0005486728.internalapi.localdomain 1/0/567774 30 -- 46/46/44/44/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:51642 [14/Oct/2025:08:28:01.885] redis redis/np0005486728.internalapi.localdomain 1/0/1061319 4778 -- 46/46/44/44/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:51610 [14/Oct/2025:08:28:01.717] redis redis/np0005486728.internalapi.localdomain 1/0/1061491 4778 -- 44/44/43/43/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:34874 [14/Oct/2025:08:38:41.529] redis redis/np0005486728.internalapi.localdomain 1/0/421678 30 -- 44/44/42/42/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: 192.168.122.104:59432 [14/Oct/2025:08:29:32.630] redis redis/np0005486728.internalapi.localdomain 1/0/970579 4759 -- 42/42/41/41/0 0/0
Oct 14 08:45:43 np0005486730 haproxy[7]: Server glance_api/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:45:43 np0005486730 haproxy[7]: proxy glance_api has no server available!
Oct 14 08:45:46 np0005486730 haproxy[7]: Server gnocchi/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:52962 [14/Oct/2025:08:38:41.560] redis redis/np0005486728.internalapi.localdomain 1/0/425764 54 -- 41/41/40/40/0 0/0
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:34118 [14/Oct/2025:08:28:01.819] redis redis/np0005486728.internalapi.localdomain 1/0/1065506 4783 -- 40/40/39/39/0 0/0
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:59532 [14/Oct/2025:08:29:31.163] redis redis/np0005486728.internalapi.localdomain 1/0/976162 4765 -- 39/39/38/38/0 0/0
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:52976 [14/Oct/2025:08:38:41.666] redis redis/np0005486728.internalapi.localdomain 1/0/425662 30 -- 38/38/37/37/0 0/0
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:59562 [14/Oct/2025:08:29:31.940] redis redis/np0005486728.internalapi.localdomain 1/0/975390 4765 -- 37/37/36/36/0 0/0
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:34066 [14/Oct/2025:08:28:00.388] redis redis/np0005486728.internalapi.localdomain 1/0/1066943 4784 -- 36/36/35/35/0 0/0
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:59564 [14/Oct/2025:08:29:32.236] redis redis/np0005486728.internalapi.localdomain 1/0/975095 4764 -- 35/35/34/34/0 0/0
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:34112 [14/Oct/2025:08:28:01.670] redis redis/np0005486728.internalapi.localdomain 1/0/1065661 4783 -- 34/34/33/33/0 0/0
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:52956 [14/Oct/2025:08:38:41.547] redis redis/np0005486728.internalapi.localdomain 1/0/425783 38 -- 33/33/32/32/0 0/0
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:59546 [14/Oct/2025:08:29:31.557] redis redis/np0005486728.internalapi.localdomain 1/0/975779 4765 -- 32/32/31/31/0 0/0
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:42304 [14/Oct/2025:08:43:42.496] redis redis/np0005486728.internalapi.localdomain 1/0/124838 22 -- 31/31/30/30/0 0/0
Oct 14 08:45:47 np0005486730 haproxy[7]: 192.168.122.110:34130 [14/Oct/2025:08:28:01.897] redis redis/np0005486728.internalapi.localdomain 1/0/1065439 4783 -- 30/30/29/29/0 0/0
Oct 14 08:45:48 np0005486730 haproxy[7]: 192.168.122.103:51668 [14/Oct/2025:08:29:29.618] redis redis/np0005486728.internalapi.localdomain 1/0/978807 4766 -- 29/29/28/28/0 0/0
Oct 14 08:45:48 np0005486730 haproxy[7]: 192.168.122.103:51652 [14/Oct/2025:08:29:29.598] redis redis/np0005486728.internalapi.localdomain 1/0/978831 149 -- 28/28/27/27/0 0/0
Oct 14 08:45:48 np0005486730 haproxy[7]: 192.168.122.103:51650 [14/Oct/2025:08:29:29.552] redis redis/np0005486728.internalapi.localdomain 1/0/978887 33968 -- 27/27/26/26/0 0/0
Oct 14 08:45:48 np0005486730 haproxy[7]: 192.168.122.103:39908 [14/Oct/2025:08:37:24.788] redis redis/np0005486728.internalapi.localdomain 1/0/503651 17146 -- 26/26/25/25/0 0/0
Oct 14 08:45:48 np0005486730 haproxy[7]: 192.168.122.103:51710 [14/Oct/2025:08:29:29.813] redis redis/np0005486728.internalapi.localdomain 1/0/978627 34018 -- 26/26/24/24/0 0/0
Oct 14 08:45:48 np0005486730 haproxy[7]: 192.168.122.103:51700 [14/Oct/2025:08:29:29.773] redis redis/np0005486728.internalapi.localdomain 1/0/978667 3417 -- 24/24/23/23/0 0/0
Oct 14 08:45:49 np0005486730 haproxy[7]: 192.168.122.104:60048 [14/Oct/2025:08:28:00.312] redis redis/np0005486728.internalapi.localdomain 1/1/1069263 4787 -- 23/23/22/22/0 0/0
Oct 14 08:45:49 np0005486730 haproxy[7]: 192.168.122.104:60030 [14/Oct/2025:08:28:00.266] redis redis/np0005486728.internalapi.localdomain 1/0/1069311 139 -- 22/22/21/21/0 0/0
Oct 14 08:45:49 np0005486730 haproxy[7]: 192.168.122.104:43904 [14/Oct/2025:08:38:41.762] redis redis/np0005486728.internalapi.localdomain 1/0/427826 1180 -- 21/21/20/20/0 0/0
Oct 14 08:45:49 np0005486730 haproxy[7]: 192.168.122.104:41908 [14/Oct/2025:08:29:26.133] redis redis/np0005486728.internalapi.localdomain 1/0/983456 49683 -- 20/20/19/19/0 0/0
Oct 14 08:45:49 np0005486730 haproxy[7]: 192.168.122.104:41910 [14/Oct/2025:08:29:26.362] redis redis/np0005486728.internalapi.localdomain 1/0/983227 3417 -- 19/19/18/18/0 0/0
Oct 14 08:45:49 np0005486730 haproxy[7]: 192.168.122.104:41912 [14/Oct/2025:08:29:26.396] redis redis/np0005486728.internalapi.localdomain 1/0/983194 33877 -- 18/18/17/17/0 0/0
Oct 14 08:45:50 np0005486730 haproxy[7]: 192.168.122.110:34048 [14/Oct/2025:08:28:00.197] redis redis/np0005486728.internalapi.localdomain 1/0/1070542 4786 -- 17/17/16/16/0 0/0
Oct 14 08:45:50 np0005486730 haproxy[7]: 192.168.122.110:34054 [14/Oct/2025:08:28:00.211] redis redis/np0005486728.internalapi.localdomain 1/0/1070531 139 -- 16/16/15/15/0 0/0
Oct 14 08:45:50 np0005486730 haproxy[7]: 192.168.122.110:54594 [14/Oct/2025:08:37:24.413] redis redis/np0005486728.internalapi.localdomain 1/0/506337 8613 -- 15/15/14/14/0 0/0
Oct 14 08:45:50 np0005486730 haproxy[7]: 192.168.122.110:59518 [14/Oct/2025:08:29:26.972] redis redis/np0005486728.internalapi.localdomain 1/0/983779 33348 -- 14/14/13/13/0 0/0
Oct 14 08:45:50 np0005486730 haproxy[7]: 192.168.122.110:59508 [14/Oct/2025:08:29:25.936] redis redis/np0005486728.internalapi.localdomain 1/0/984815 3417 -- 13/13/12/12/0 0/0
Oct 14 08:45:50 np0005486730 haproxy[7]: 192.168.122.110:59492 [14/Oct/2025:08:29:25.687] redis redis/np0005486728.internalapi.localdomain 1/0/985063 40214 -- 12/12/11/11/0 0/0
Oct 14 08:45:51 np0005486730 haproxy[7]: Server gnocchi/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:45:55 np0005486730 haproxy[7]: Server gnocchi/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:45:55 np0005486730 haproxy[7]: proxy gnocchi has no server available!
Oct 14 08:46:04 np0005486730 haproxy[7]: Server manila/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:46:08 np0005486730 haproxy[7]: Server manila/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:46:12 np0005486730 haproxy[7]: Server manila/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:46:12 np0005486730 haproxy[7]: proxy manila has no server available!
Oct 14 08:47:16 np0005486730 haproxy[7]: Server neutron/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:47:32 np0005486730 haproxy[7]: Server neutron/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:47:57 np0005486730 haproxy[7]: Server neutron/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:47:57 np0005486730 haproxy[7]: proxy neutron has no server available!
Oct 14 08:48:05 np0005486730 haproxy[7]: Server placement/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:48:10 np0005486730 haproxy[7]: Server placement/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:48:14 np0005486730 haproxy[7]: Server placement/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:48:14 np0005486730 haproxy[7]: proxy placement has no server available!
Oct 14 08:48:21 np0005486730 haproxy[7]: Server nova_osapi/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:48:25 np0005486730 haproxy[7]: Server nova_osapi/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:48:29 np0005486730 haproxy[7]: Server nova_osapi/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:48:29 np0005486730 haproxy[7]: proxy nova_osapi has no server available!
Oct 14 08:48:41 np0005486730 haproxy[7]: Server nova_metadata/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:48:45 np0005486730 haproxy[7]: Server nova_metadata/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:48:49 np0005486730 haproxy[7]: Server nova_metadata/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:48:49 np0005486730 haproxy[7]: proxy nova_metadata has no server available!
Oct 14 08:49:30 np0005486730 haproxy[7]: Server nova_novncproxy/np0005486728.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 26ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:49:32 np0005486730 haproxy[7]: Server nova_novncproxy/np0005486730.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:49:32 np0005486730 haproxy[7]: Server nova_novncproxy/np0005486729.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Oct 14 08:49:32 np0005486730 haproxy[7]: proxy nova_novncproxy has no server available!
Oct 14 09:09:49 np0005486730 haproxy[7]: Backup Server mysql/np0005486730.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 63ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.