Jun 13 08:10:10 np0000072643 haproxy[7]: Server aodh/np0000072641.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Server aodh/np0000072642.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Server aodh/np0000072643.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: proxy aodh has no server available!
Jun 13 08:10:10 np0000072643 haproxy[7]: Server cinder/np0000072641.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Server cinder/np0000072642.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Server cinder/np0000072643.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: proxy cinder has no server available!
Jun 13 08:10:10 np0000072643 haproxy[7]: Server glance_api/np0000072641.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Server glance_api/np0000072642.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Server glance_api/np0000072643.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: proxy glance_api has no server available!
Jun 13 08:10:10 np0000072643 haproxy[7]: Server glance_api_internal/np0000072641.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Server glance_api_internal/np0000072642.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Server glance_api_internal/np0000072643.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: proxy glance_api_internal has no server available!
Jun 13 08:10:10 np0000072643 haproxy[7]: Server gnocchi/np0000072641.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Server gnocchi/np0000072642.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Server gnocchi/np0000072643.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: proxy gnocchi has no server available!
Jun 13 08:10:10 np0000072643 haproxy[7]: Server heat_api/np0000072641.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Server heat_api/np0000072642.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.
Jun 13 08:10:10 np0000072643 haproxy[7]: Backup Server mysql/np0000072641.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server heat_api/np0000072643.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: proxy heat_api has no server available!
Jun 13 08:10:11 np0000072643 haproxy[7]: Backup Server mysql/np0000072642.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 22ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server heat_cfn/np0000072641.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Backup Server mysql/np0000072643.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 18ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Jun 13 08:10:11 np0000072643 haproxy[7]: proxy mysql has no server available!
Jun 13 08:10:11 np0000072643 haproxy[7]: Server heat_cfn/np0000072642.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server heat_cfn/np0000072643.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: proxy heat_cfn has no server available!
Jun 13 08:10:11 np0000072643 haproxy[7]: Server horizon/np0000072641.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server horizon/np0000072642.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server horizon/np0000072643.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: proxy horizon has no server available!
Jun 13 08:10:11 np0000072643 haproxy[7]: Server keystone_admin/np0000072641.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server keystone_admin/np0000072642.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server keystone_admin/np0000072643.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: proxy keystone_admin has no server available!
Jun 13 08:10:11 np0000072643 haproxy[7]: Server keystone_public/np0000072641.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server keystone_public/np0000072642.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server keystone_public/np0000072643.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: proxy keystone_public has no server available!
Jun 13 08:10:11 np0000072643 haproxy[7]: Server manila/np0000072641.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server manila/np0000072642.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server manila/np0000072643.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: proxy manila has no server available!
Jun 13 08:10:11 np0000072643 haproxy[7]: Server neutron/np0000072641.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server neutron/np0000072642.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server neutron/np0000072643.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: proxy neutron has no server available!
Jun 13 08:10:11 np0000072643 haproxy[7]: Server nova_metadata/np0000072641.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server nova_metadata/np0000072642.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server nova_metadata/np0000072643.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: proxy nova_metadata has no server available!
Jun 13 08:10:11 np0000072643 haproxy[7]: Server nova_novncproxy/np0000072641.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server nova_novncproxy/np0000072642.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: Server nova_novncproxy/np0000072643.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.
Jun 13 08:10:11 np0000072643 haproxy[7]: proxy nova_novncproxy has no server available!
Jun 13 08:10:11 np0000072643 haproxy[7]: Server nova_osapi/np0000072641.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: Server nova_osapi/np0000072642.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: Server nova_osapi/np0000072643.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: proxy nova_osapi has no server available!
Jun 13 08:10:12 np0000072643 haproxy[7]: Server placement/np0000072641.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: Server placement/np0000072642.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: Server placement/np0000072643.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: proxy placement has no server available!
Jun 13 08:10:12 np0000072643 haproxy[7]: Server redis/np0000072641.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: Server redis/np0000072642.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: Server redis/np0000072643.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: proxy redis has no server available!
Jun 13 08:10:12 np0000072643 haproxy[7]: Server swift_proxy_server/np0000072641.storage.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: Server swift_proxy_server/np0000072642.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: Server swift_proxy_server/np0000072643.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.
Jun 13 08:10:12 np0000072643 haproxy[7]: proxy swift_proxy_server has no server available!
Jun 13 08:11:53 np0000072643 haproxy[7]: Backup Server mysql/np0000072643.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 27ms. 0 active and 1 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Jun 13 08:12:17 np0000072643 haproxy[7]: Backup Server mysql/np0000072642.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 24ms. 0 active and 2 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Jun 13 08:13:24 np0000072643 haproxy[7]: Server redis/np0000072641.internalapi.localdomain is UP, reason: Layer7 check passed, code: 0, info: "(tcp-check)", check duration: 5ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:13:31 np0000072643 haproxy[7]: Backup Server mysql/np0000072641.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 59ms. 0 active and 3 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Jun 13 08:14:16 np0000072643 haproxy[7]: Server keystone_admin/np0000072642.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 11ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:14:16 np0000072643 haproxy[7]: Server keystone_public/np0000072642.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 14ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:14:17 np0000072643 haproxy[7]: Server keystone_admin/np0000072643.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.
Jun 13 08:14:17 np0000072643 haproxy[7]: Server keystone_public/np0000072643.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.
Jun 13 08:14:19 np0000072643 haproxy[7]: Server horizon/np0000072642.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.
Jun 13 08:14:21 np0000072643 haproxy[7]: Server horizon/np0000072643.internalapi.localdomain is UP, reason: Layer7 check passed, code: 301, check duration: 0ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:14:53 np0000072643 haproxy[7]: Server horizon/np0000072641.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.
Jun 13 08:15:19 np0000072643 haproxy[7]: Server keystone_admin/np0000072641.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 10ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:15:19 np0000072643 haproxy[7]: Server keystone_public/np0000072641.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 14ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:19:25 np0000072643 haproxy[7]: Server cinder/np0000072641.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.
Jun 13 08:19:25 np0000072643 haproxy[7]: Server heat_cfn/np0000072641.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.
Jun 13 08:19:25 np0000072643 haproxy[7]: Server heat_api/np0000072641.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.
Jun 13 08:19:26 np0000072643 haproxy[7]: Server aodh/np0000072641.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 11ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:19:28 np0000072643 haproxy[7]: Server manila/np0000072641.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 920ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:19:30 np0000072643 haproxy[7]: Server nova_novncproxy/np0000072641.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.
Jun 13 08:19:32 np0000072643 haproxy[7]: Server placement/np0000072641.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.
Jun 13 08:19:33 np0000072643 haproxy[7]: Server nova_metadata/np0000072641.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.
Jun 13 08:19:34 np0000072643 haproxy[7]: Server neutron/np0000072641.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.
Jun 13 08:19:34 np0000072643 haproxy[7]: Server nova_osapi/np0000072641.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 9ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:19:34 np0000072643 haproxy[7]: Server swift_proxy_server/np0000072641.storage.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.
Jun 13 08:19:34 np0000072643 haproxy[7]: Server glance_api/np0000072641.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.
Jun 13 08:19:35 np0000072643 haproxy[7]: Server glance_api_internal/np0000072641.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.
Jun 13 08:19:41 np0000072643 haproxy[7]: Server aodh/np0000072642.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 7ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:19:42 np0000072643 haproxy[7]: Server heat_api/np0000072643.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.
Jun 13 08:19:42 np0000072643 haproxy[7]: Server heat_cfn/np0000072642.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.
Jun 13 08:19:42 np0000072643 haproxy[7]: Server cinder/np0000072643.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 7ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:19:42 np0000072643 haproxy[7]: Server aodh/np0000072643.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.
Jun 13 08:19:42 np0000072643 haproxy[7]: Server heat_api/np0000072642.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 18ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:19:43 np0000072643 haproxy[7]: Server cinder/np0000072642.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.
Jun 13 08:19:43 np0000072643 haproxy[7]: Server heat_cfn/np0000072643.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.
Jun 13 08:19:43 np0000072643 haproxy[7]: Server manila/np0000072642.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.
Jun 13 08:19:46 np0000072643 haproxy[7]: Server manila/np0000072643.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.
Jun 13 08:19:46 np0000072643 haproxy[7]: Server nova_novncproxy/np0000072643.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.
Jun 13 08:19:46 np0000072643 haproxy[7]: Server nova_novncproxy/np0000072642.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.
Jun 13 08:19:48 np0000072643 haproxy[7]: Server placement/np0000072643.internalapi.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.
Jun 13 08:19:48 np0000072643 haproxy[7]: Server placement/np0000072642.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.
Jun 13 08:19:50 np0000072643 haproxy[7]: Server neutron/np0000072643.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.
Jun 13 08:19:50 np0000072643 haproxy[7]: Server swift_proxy_server/np0000072642.storage.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.
Jun 13 08:19:51 np0000072643 haproxy[7]: Server nova_metadata/np0000072642.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.
Jun 13 08:19:51 np0000072643 haproxy[7]: Server glance_api_internal/np0000072643.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.
Jun 13 08:19:51 np0000072643 haproxy[7]: Server glance_api/np0000072642.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 12ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Jun 13 08:19:51 np0000072643 haproxy[7]: Server glance_api_internal/np0000072642.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.
Jun 13 08:19:51 np0000072643 haproxy[7]: Server nova_osapi/np0000072642.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.
Jun 13 08:19:51 np0000072643 haproxy[7]: Server nova_metadata/np0000072643.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.
Jun 13 08:19:52 np0000072643 haproxy[7]: Server neutron/np0000072642.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.
Jun 13 08:19:52 np0000072643 haproxy[7]: Server swift_proxy_server/np0000072643.storage.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.
Jun 13 08:19:52 np0000072643 haproxy[7]: Server nova_osapi/np0000072643.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.
Jun 13 08:19:52 np0000072643 haproxy[7]: Server glance_api/np0000072643.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.
Jun 13 08:23:32 np0000072643 haproxy[7]: 192.168.122.104:46128 [13/Jun/2026:08:23:32.081] redis redis/np0000072641.internalapi.localdomain 1/0/7 10 -- 31/31/29/29/0 0/0
Jun 13 08:23:32 np0000072643 haproxy[7]: 192.168.122.104:46122 [13/Jun/2026:08:23:31.792] redis redis/np0000072641.internalapi.localdomain 1/0/297 4427 -- 31/31/29/29/0 0/0
Jun 13 08:23:32 np0000072643 haproxy[7]: 192.168.122.104:46142 [13/Jun/2026:08:23:32.119] redis redis/np0000072641.internalapi.localdomain 1/0/261 4427 -- 32/32/30/30/0 0/0
Jun 13 08:23:32 np0000072643 haproxy[7]: 192.168.122.104:46158 [13/Jun/2026:08:23:32.371] redis redis/np0000072641.internalapi.localdomain 1/0/9 10 -- 32/32/30/30/0 0/0
Jun 13 08:23:34 np0000072643 haproxy[7]: Server gnocchi/np0000072642.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.
Jun 13 08:23:36 np0000072643 haproxy[7]: 192.168.122.110:48152 [13/Jun/2026:08:23:36.877] redis redis/np0000072641.internalapi.localdomain 1/0/28 10 -- 38/38/37/37/0 0/0
Jun 13 08:23:36 np0000072643 haproxy[7]: 192.168.122.110:48108 [13/Jun/2026:08:23:36.602] redis redis/np0000072641.internalapi.localdomain 1/1/304 4428 -- 37/37/36/36/0 0/0
Jun 13 08:23:37 np0000072643 haproxy[7]: 192.168.122.110:48170 [13/Jun/2026:08:23:37.225] redis redis/np0000072641.internalapi.localdomain 1/0/16 10 -- 38/38/37/37/0 0/0
Jun 13 08:23:37 np0000072643 haproxy[7]: 192.168.122.110:48160 [13/Jun/2026:08:23:36.942] redis redis/np0000072641.internalapi.localdomain 1/0/301 4429 -- 38/38/36/36/0 0/0
Jun 13 08:23:37 np0000072643 haproxy[7]: 192.168.122.104:46220 [13/Jun/2026:08:23:37.682] redis redis/np0000072641.internalapi.localdomain 1/0/15 10 -- 38/38/37/37/0 0/0
Jun 13 08:23:37 np0000072643 haproxy[7]: 192.168.122.104:46204 [13/Jun/2026:08:23:37.417] redis redis/np0000072641.internalapi.localdomain 1/0/280 4429 -- 37/37/36/36/0 0/0
Jun 13 08:23:37 np0000072643 haproxy[7]: 192.168.122.104:46240 [13/Jun/2026:08:23:37.948] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 38/38/37/37/0 0/0
Jun 13 08:23:37 np0000072643 haproxy[7]: 192.168.122.104:46232 [13/Jun/2026:08:23:37.726] redis redis/np0000072641.internalapi.localdomain 1/0/232 4429 -- 37/37/36/36/0 0/0
Jun 13 08:23:38 np0000072643 haproxy[7]: 192.168.122.104:46258 [13/Jun/2026:08:23:38.244] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 38/38/37/37/0 0/0
Jun 13 08:23:38 np0000072643 haproxy[7]: 192.168.122.104:46252 [13/Jun/2026:08:23:37.987] redis redis/np0000072641.internalapi.localdomain 1/0/269 4429 -- 37/37/36/36/0 0/0
Jun 13 08:23:38 np0000072643 haproxy[7]: 192.168.122.104:46290 [13/Jun/2026:08:23:38.570] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Jun 13 08:23:38 np0000072643 haproxy[7]: 192.168.122.104:46274 [13/Jun/2026:08:23:38.286] redis redis/np0000072641.internalapi.localdomain 1/0/294 4430 -- 39/39/37/37/0 0/0
Jun 13 08:23:40 np0000072643 haproxy[7]: Server gnocchi/np0000072643.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.
Jun 13 08:23:42 np0000072643 haproxy[7]: 192.168.122.110:46720 [13/Jun/2026:08:23:42.270] redis redis/np0000072641.internalapi.localdomain 1/1/277 4428 -- 41/41/40/40/0 0/0
Jun 13 08:23:42 np0000072643 haproxy[7]: 192.168.122.110:46730 [13/Jun/2026:08:23:42.533] redis redis/np0000072641.internalapi.localdomain 1/0/14 10 -- 41/41/39/39/0 0/0
Jun 13 08:23:42 np0000072643 haproxy[7]: 192.168.122.110:46738 [13/Jun/2026:08:23:42.826] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:42 np0000072643 haproxy[7]: 192.168.122.110:46732 [13/Jun/2026:08:23:42.575] redis redis/np0000072641.internalapi.localdomain 1/0/265 4428 -- 40/40/39/39/0 0/0
Jun 13 08:23:43 np0000072643 haproxy[7]: 192.168.122.110:46748 [13/Jun/2026:08:23:42.865] redis redis/np0000072641.internalapi.localdomain 1/0/281 4428 -- 41/41/40/40/0 0/0
Jun 13 08:23:43 np0000072643 haproxy[7]: 192.168.122.110:46764 [13/Jun/2026:08:23:43.122] redis redis/np0000072641.internalapi.localdomain 1/0/24 10 -- 40/40/39/39/0 0/0
Jun 13 08:23:43 np0000072643 haproxy[7]: 192.168.122.110:46774 [13/Jun/2026:08:23:43.435] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:43 np0000072643 haproxy[7]: 192.168.122.110:46768 [13/Jun/2026:08:23:43.176] redis redis/np0000072641.internalapi.localdomain 1/0/270 4429 -- 40/40/39/39/0 0/0
Jun 13 08:23:43 np0000072643 haproxy[7]: 192.168.122.104:48422 [13/Jun/2026:08:23:43.902] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:43 np0000072643 haproxy[7]: 192.168.122.104:48408 [13/Jun/2026:08:23:43.617] redis redis/np0000072641.internalapi.localdomain 1/0/298 4429 -- 40/40/39/39/0 0/0
Jun 13 08:23:44 np0000072643 haproxy[7]: 192.168.122.104:48432 [13/Jun/2026:08:23:44.157] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:44 np0000072643 haproxy[7]: 192.168.122.104:48426 [13/Jun/2026:08:23:43.931] redis redis/np0000072641.internalapi.localdomain 1/0/238 4429 -- 41/41/39/39/0 0/0
Jun 13 08:23:44 np0000072643 haproxy[7]: 192.168.122.104:48448 [13/Jun/2026:08:23:44.415] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:44 np0000072643 haproxy[7]: 192.168.122.104:48440 [13/Jun/2026:08:23:44.195] redis redis/np0000072641.internalapi.localdomain 1/0/232 4429 -- 40/40/39/39/0 0/0
Jun 13 08:23:44 np0000072643 haproxy[7]: 192.168.122.104:48470 [13/Jun/2026:08:23:44.720] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:44 np0000072643 haproxy[7]: 192.168.122.104:48456 [13/Jun/2026:08:23:44.458] redis redis/np0000072641.internalapi.localdomain 1/0/275 4429 -- 40/40/39/39/0 0/0
Jun 13 08:23:48 np0000072643 haproxy[7]: 192.168.122.110:46780 [13/Jun/2026:08:23:48.484] redis redis/np0000072641.internalapi.localdomain 1/0/323 4428 -- 41/41/40/40/0 0/0
Jun 13 08:23:48 np0000072643 haproxy[7]: 192.168.122.110:59472 [13/Jun/2026:08:23:48.798] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 40/40/39/39/0 0/0
Jun 13 08:23:49 np0000072643 haproxy[7]: 192.168.122.110:59498 [13/Jun/2026:08:23:49.187] redis redis/np0000072641.internalapi.localdomain 1/1/26 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:49 np0000072643 haproxy[7]: 192.168.122.110:59486 [13/Jun/2026:08:23:48.833] redis redis/np0000072641.internalapi.localdomain 1/0/382 4428 -- 40/40/39/39/0 0/0
Jun 13 08:23:49 np0000072643 haproxy[7]: 192.168.122.110:59512 [13/Jun/2026:08:23:49.244] redis redis/np0000072641.internalapi.localdomain 1/0/339 4428 -- 41/41/39/39/0 0/0
Jun 13 08:23:49 np0000072643 haproxy[7]: 192.168.122.110:59516 [13/Jun/2026:08:23:49.569] redis redis/np0000072641.internalapi.localdomain 1/0/14 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:49 np0000072643 haproxy[7]: 192.168.122.110:59534 [13/Jun/2026:08:23:49.892] redis redis/np0000072641.internalapi.localdomain 1/0/16 10 -- 42/42/41/41/0 0/0
Jun 13 08:23:49 np0000072643 haproxy[7]: 192.168.122.110:59530 [13/Jun/2026:08:23:49.628] redis redis/np0000072641.internalapi.localdomain 1/0/281 4429 -- 41/41/40/40/0 0/0
Jun 13 08:23:50 np0000072643 haproxy[7]: 192.168.122.104:47648 [13/Jun/2026:08:23:50.018] redis redis/np0000072641.internalapi.localdomain 1/0/14 10 -- 41/41/39/39/0 0/0
Jun 13 08:23:50 np0000072643 haproxy[7]: 192.168.122.104:47646 [13/Jun/2026:08:23:49.764] redis redis/np0000072641.internalapi.localdomain 1/0/270 4429 -- 41/41/39/39/0 0/0
Jun 13 08:23:50 np0000072643 haproxy[7]: 192.168.122.104:47666 [13/Jun/2026:08:23:50.272] redis redis/np0000072641.internalapi.localdomain 1/0/14 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:50 np0000072643 haproxy[7]: 192.168.122.104:47654 [13/Jun/2026:08:23:50.047] redis redis/np0000072641.internalapi.localdomain 1/0/240 4429 -- 41/41/39/39/0 0/0
Jun 13 08:23:50 np0000072643 haproxy[7]: 192.168.122.104:47684 [13/Jun/2026:08:23:50.534] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:50 np0000072643 haproxy[7]: 192.168.122.104:47678 [13/Jun/2026:08:23:50.306] redis redis/np0000072641.internalapi.localdomain 1/0/240 4429 -- 41/41/39/39/0 0/0
Jun 13 08:23:50 np0000072643 haproxy[7]: 192.168.122.104:47696 [13/Jun/2026:08:23:50.576] redis redis/np0000072641.internalapi.localdomain 1/0/257 4429 -- 41/41/40/40/0 0/0
Jun 13 08:23:50 np0000072643 haproxy[7]: 192.168.122.104:47702 [13/Jun/2026:08:23:50.820] redis redis/np0000072641.internalapi.localdomain 1/2/21 10 -- 40/40/39/39/0 0/0
Jun 13 08:23:55 np0000072643 haproxy[7]: 192.168.122.110:59550 [13/Jun/2026:08:23:55.239] redis redis/np0000072641.internalapi.localdomain 1/0/9 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:55 np0000072643 haproxy[7]: 192.168.122.110:59544 [13/Jun/2026:08:23:54.944] redis redis/np0000072641.internalapi.localdomain 1/0/309 4428 -- 40/40/39/39/0 0/0
Jun 13 08:23:55 np0000072643 haproxy[7]: 192.168.122.110:59580 [13/Jun/2026:08:23:55.539] redis redis/np0000072641.internalapi.localdomain 1/1/20 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:55 np0000072643 haproxy[7]: 192.168.122.110:59566 [13/Jun/2026:08:23:55.267] redis redis/np0000072641.internalapi.localdomain 1/0/293 4428 -- 40/40/39/39/0 0/0
Jun 13 08:23:55 np0000072643 haproxy[7]: 192.168.122.110:59586 [13/Jun/2026:08:23:55.861] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 42/42/41/41/0 0/0
Jun 13 08:23:55 np0000072643 haproxy[7]: 192.168.122.110:59582 [13/Jun/2026:08:23:55.585] redis redis/np0000072641.internalapi.localdomain 1/0/288 4429 -- 42/42/40/40/0 0/0
Jun 13 08:23:56 np0000072643 haproxy[7]: 192.168.122.104:47714 [13/Jun/2026:08:23:56.101] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 42/42/41/41/0 0/0
Jun 13 08:23:56 np0000072643 haproxy[7]: 192.168.122.104:47708 [13/Jun/2026:08:23:55.868] redis redis/np0000072641.internalapi.localdomain 1/0/244 4429 -- 41/41/40/40/0 0/0
Jun 13 08:23:56 np0000072643 haproxy[7]: 192.168.122.110:59602 [13/Jun/2026:08:23:55.893] redis redis/np0000072641.internalapi.localdomain 1/0/292 4429 -- 42/42/41/41/0 0/0
Jun 13 08:23:56 np0000072643 haproxy[7]: 192.168.122.110:59610 [13/Jun/2026:08:23:56.171] redis redis/np0000072641.internalapi.localdomain 1/0/16 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:56 np0000072643 haproxy[7]: 192.168.122.104:47720 [13/Jun/2026:08:23:56.386] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 41/41/39/39/0 0/0
Jun 13 08:23:56 np0000072643 haproxy[7]: 192.168.122.104:47718 [13/Jun/2026:08:23:56.138] redis redis/np0000072641.internalapi.localdomain 1/0/260 4429 -- 41/41/39/39/0 0/0
Jun 13 08:23:56 np0000072643 haproxy[7]: 192.168.122.104:47742 [13/Jun/2026:08:23:56.717] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:56 np0000072643 haproxy[7]: 192.168.122.104:47732 [13/Jun/2026:08:23:56.416] redis redis/np0000072641.internalapi.localdomain 1/0/311 4429 -- 41/41/39/39/0 0/0
Jun 13 08:23:57 np0000072643 haproxy[7]: 192.168.122.104:47766 [13/Jun/2026:08:23:57.077] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0
Jun 13 08:23:57 np0000072643 haproxy[7]: 192.168.122.104:47758 [13/Jun/2026:08:23:56.758] redis redis/np0000072641.internalapi.localdomain 1/0/331 4429 -- 40/40/39/39/0 0/0
Jun 13 08:24:01 np0000072643 haproxy[7]: 192.168.122.110:40970 [13/Jun/2026:08:24:01.219] redis redis/np0000072641.internalapi.localdomain 1/0/260 4428 -- 41/41/39/39/0 0/0
Jun 13 08:24:01 np0000072643 haproxy[7]: 192.168.122.110:40976 [13/Jun/2026:08:24:01.467] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:01 np0000072643 haproxy[7]: 192.168.122.110:40994 [13/Jun/2026:08:24:01.745] redis redis/np0000072641.internalapi.localdomain 1/0/9 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:01 np0000072643 haproxy[7]: 192.168.122.110:40980 [13/Jun/2026:08:24:01.501] redis redis/np0000072641.internalapi.localdomain 1/0/253 4428 -- 40/40/39/39/0 0/0
Jun 13 08:24:02 np0000072643 haproxy[7]: 192.168.122.110:41014 [13/Jun/2026:08:24:02.041] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:02 np0000072643 haproxy[7]: 192.168.122.110:41004 [13/Jun/2026:08:24:01.776] redis redis/np0000072641.internalapi.localdomain 1/0/277 4428 -- 41/41/39/39/0 0/0
Jun 13 08:24:02 np0000072643 haproxy[7]: 192.168.122.110:41038 [13/Jun/2026:08:24:02.327] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:02 np0000072643 haproxy[7]: 192.168.122.110:41030 [13/Jun/2026:08:24:02.074] redis redis/np0000072641.internalapi.localdomain 1/0/262 4429 -- 41/41/40/40/0 0/0
Jun 13 08:24:02 np0000072643 haproxy[7]: 192.168.122.104:52384 [13/Jun/2026:08:24:02.120] redis redis/np0000072641.internalapi.localdomain 1/0/250 4429 -- 41/41/40/40/0 0/0
Jun 13 08:24:02 np0000072643 haproxy[7]: 192.168.122.104:52396 [13/Jun/2026:08:24:02.361] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/39/39/0 0/0
Jun 13 08:24:02 np0000072643 haproxy[7]: 192.168.122.104:52408 [13/Jun/2026:08:24:02.683] redis redis/np0000072641.internalapi.localdomain 1/0/13 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:02 np0000072643 haproxy[7]: 192.168.122.104:52398 [13/Jun/2026:08:24:02.391] redis redis/np0000072641.internalapi.localdomain 1/0/306 4429 -- 41/41/39/39/0 0/0
Jun 13 08:24:03 np0000072643 haproxy[7]: 192.168.122.104:52422 [13/Jun/2026:08:24:02.724] redis redis/np0000072641.internalapi.localdomain 1/0/276 4429 -- 41/41/40/40/0 0/0
Jun 13 08:24:03 np0000072643 haproxy[7]: 192.168.122.104:52432 [13/Jun/2026:08:24:02.988] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 41/41/39/39/0 0/0
Jun 13 08:24:03 np0000072643 haproxy[7]: 192.168.122.104:52446 [13/Jun/2026:08:24:03.291] redis redis/np0000072641.internalapi.localdomain 1/0/9 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:03 np0000072643 haproxy[7]: 192.168.122.104:52444 [13/Jun/2026:08:24:03.025] redis redis/np0000072641.internalapi.localdomain 1/0/274 4429 -- 41/41/39/39/0 0/0
Jun 13 08:24:07 np0000072643 haproxy[7]: 192.168.122.110:41060 [13/Jun/2026:08:24:07.682] redis redis/np0000072641.internalapi.localdomain 1/0/17 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:07 np0000072643 haproxy[7]: 192.168.122.110:41044 [13/Jun/2026:08:24:07.365] redis redis/np0000072641.internalapi.localdomain 1/0/334 4428 -- 41/41/39/39/0 0/0
Jun 13 08:24:08 np0000072643 haproxy[7]: 192.168.122.110:41068 [13/Jun/2026:08:24:07.731] redis redis/np0000072641.internalapi.localdomain 1/0/295 4428 -- 41/41/40/40/0 0/0
Jun 13 08:24:08 np0000072643 haproxy[7]: 192.168.122.110:41084 [13/Jun/2026:08:24:08.016] redis redis/np0000072641.internalapi.localdomain 1/0/13 10 -- 40/40/39/39/0 0/0
Jun 13 08:24:08 np0000072643 haproxy[7]: 192.168.122.110:41108 [13/Jun/2026:08:24:08.304] redis redis/np0000072641.internalapi.localdomain 1/0/9 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:08 np0000072643 haproxy[7]: 192.168.122.110:41096 [13/Jun/2026:08:24:08.056] redis redis/np0000072641.internalapi.localdomain 1/0/257 4428 -- 40/40/39/39/0 0/0
Jun 13 08:24:08 np0000072643 haproxy[7]: 192.168.122.110:35432 [13/Jun/2026:08:24:08.620] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:08 np0000072643 haproxy[7]: 192.168.122.110:41118 [13/Jun/2026:08:24:08.343] redis redis/np0000072641.internalapi.localdomain 1/0/288 4429 -- 42/42/40/40/0 0/0
Jun 13 08:24:08 np0000072643 haproxy[7]: 192.168.122.104:52466 [13/Jun/2026:08:24:08.653] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:08 np0000072643 haproxy[7]: 192.168.122.104:52454 [13/Jun/2026:08:24:08.335] redis redis/np0000072641.internalapi.localdomain 1/0/329 4429 -- 40/40/39/39/0 0/0
Jun 13 08:24:08 np0000072643 haproxy[7]: 192.168.122.104:52490 [13/Jun/2026:08:24:08.977] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:08 np0000072643 haproxy[7]: 192.168.122.104:52480 [13/Jun/2026:08:24:08.693] redis redis/np0000072641.internalapi.localdomain 1/0/294 4429 -- 41/41/39/39/0 0/0
Jun 13 08:24:09 np0000072643 haproxy[7]: 192.168.122.104:52518 [13/Jun/2026:08:24:09.253] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:09 np0000072643 haproxy[7]: 192.168.122.104:52502 [13/Jun/2026:08:24:09.014] redis redis/np0000072641.internalapi.localdomain 1/0/250 4429 -- 41/41/39/39/0 0/0
Jun 13 08:24:09 np0000072643 haproxy[7]: 192.168.122.104:52520 [13/Jun/2026:08:24:09.297] redis redis/np0000072641.internalapi.localdomain 1/0/264 4429 -- 41/41/39/39/0 0/0
Jun 13 08:24:09 np0000072643 haproxy[7]: 192.168.122.104:45576 [13/Jun/2026:08:24:09.550] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 41/41/39/39/0 0/0
Jun 13 08:24:13 np0000072643 haproxy[7]: 192.168.122.110:35440 [13/Jun/2026:08:24:13.667] redis redis/np0000072641.internalapi.localdomain 1/1/321 4429 -- 41/41/39/39/0 0/0
Jun 13 08:24:13 np0000072643 haproxy[7]: 192.168.122.110:35442 [13/Jun/2026:08:24:13.975] redis redis/np0000072641.internalapi.localdomain 1/0/14 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:14 np0000072643 haproxy[7]: 192.168.122.110:35448 [13/Jun/2026:08:24:14.023] redis redis/np0000072641.internalapi.localdomain 1/2/288 4429 -- 41/41/40/40/0 0/0
Jun 13 08:24:14 np0000072643 haproxy[7]: 192.168.122.110:35450 [13/Jun/2026:08:24:14.290] redis redis/np0000072641.internalapi.localdomain 1/5/23 10 -- 40/40/39/39/0 0/0
Jun 13 08:24:14 np0000072643 haproxy[7]: 192.168.122.110:35466 [13/Jun/2026:08:24:14.601] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 42/42/40/40/0 0/0
Jun 13 08:24:14 np0000072643 haproxy[7]: 192.168.122.110:35454 [13/Jun/2026:08:24:14.340] redis redis/np0000072641.internalapi.localdomain 1/0/273 4430 -- 42/42/40/40/0 0/0
Jun 13 08:24:14 np0000072643 haproxy[7]: 192.168.122.104:45592 [13/Jun/2026:08:24:14.867] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:14 np0000072643 haproxy[7]: 192.168.122.104:45590 [13/Jun/2026:08:24:14.592] redis redis/np0000072641.internalapi.localdomain 1/0/285 4430 -- 42/42/40/40/0 0/0
Jun 13 08:24:14 np0000072643 haproxy[7]: 192.168.122.110:35482 [13/Jun/2026:08:24:14.920] redis redis/np0000072641.internalapi.localdomain 1/0/14 10 -- 42/42/40/40/0 0/0
Jun 13 08:24:14 np0000072643 haproxy[7]: 192.168.122.110:35470 [13/Jun/2026:08:24:14.637] redis redis/np0000072641.internalapi.localdomain 1/0/298 4431 -- 42/42/40/40/0 0/0
Jun 13 08:24:15 np0000072643 haproxy[7]: 192.168.122.104:45612 [13/Jun/2026:08:24:15.149] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:15 np0000072643 haproxy[7]: 192.168.122.104:45604 [13/Jun/2026:08:24:14.904] redis redis/np0000072641.internalapi.localdomain 1/0/257 4431 -- 41/41/39/39/0 0/0
Jun 13 08:24:15 np0000072643 haproxy[7]: 192.168.122.104:45638 [13/Jun/2026:08:24:15.455] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:15 np0000072643 haproxy[7]: 192.168.122.104:45626 [13/Jun/2026:08:24:15.189] redis redis/np0000072641.internalapi.localdomain 1/0/277 4431 -- 41/41/39/39/0 0/0
Jun 13 08:24:15 np0000072643 haproxy[7]: 192.168.122.104:45656 [13/Jun/2026:08:24:15.716] redis redis/np0000072641.internalapi.localdomain 1/0/9 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:15 np0000072643 haproxy[7]: 192.168.122.104:45644 [13/Jun/2026:08:24:15.496] redis redis/np0000072641.internalapi.localdomain 1/0/229 4431 -- 40/40/39/39/0 0/0
Jun 13 08:24:20 np0000072643 haproxy[7]: 192.168.122.110:39954 [13/Jun/2026:08:24:19.964] redis redis/np0000072641.internalapi.localdomain 1/0/255 4430 -- 41/41/40/40/0 0/0
Jun 13 08:24:20 np0000072643 haproxy[7]: 192.168.122.110:39960 [13/Jun/2026:08:24:20.206] redis redis/np0000072641.internalapi.localdomain 1/0/16 10 -- 40/40/39/39/0 0/0
Jun 13 08:24:20 np0000072643 haproxy[7]: 192.168.122.110:39990 [13/Jun/2026:08:24:20.489] redis redis/np0000072641.internalapi.localdomain 1/0/21 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:20 np0000072643 haproxy[7]: 192.168.122.110:39974 [13/Jun/2026:08:24:20.247] redis redis/np0000072641.internalapi.localdomain 1/0/264 4430 -- 40/40/39/39/0 0/0
Jun 13 08:24:20 np0000072643 haproxy[7]: 192.168.122.110:40016 [13/Jun/2026:08:24:20.798] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:20 np0000072643 haproxy[7]: 192.168.122.110:40004 [13/Jun/2026:08:24:20.542] redis redis/np0000072641.internalapi.localdomain 1/0/269 4431 -- 41/41/40/40/0 0/0
Jun 13 08:24:21 np0000072643 haproxy[7]: 192.168.122.104:45996 [13/Jun/2026:08:24:20.769] redis redis/np0000072641.internalapi.localdomain 1/0/294 4431 -- 42/42/41/41/0 0/0
Jun 13 08:24:21 np0000072643 haproxy[7]: 192.168.122.104:46010 [13/Jun/2026:08:24:21.049] redis redis/np0000072641.internalapi.localdomain 1/0/13 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:21 np0000072643 haproxy[7]: 192.168.122.110:40018 [13/Jun/2026:08:24:20.855] redis redis/np0000072641.internalapi.localdomain 1/0/316 4431 -- 42/42/41/41/0 0/0
Jun 13 08:24:21 np0000072643 haproxy[7]: 192.168.122.110:40034 [13/Jun/2026:08:24:21.157] redis redis/np0000072641.internalapi.localdomain 1/1/12 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:21 np0000072643 haproxy[7]: 192.168.122.104:46022 [13/Jun/2026:08:24:21.371] redis redis/np0000072641.internalapi.localdomain 1/0/18 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:21 np0000072643 haproxy[7]: 192.168.122.104:46014 [13/Jun/2026:08:24:21.092] redis redis/np0000072641.internalapi.localdomain 1/0/298 4431 -- 40/40/39/39/0 0/0
Jun 13 08:24:21 np0000072643 haproxy[7]: 192.168.122.104:46052 [13/Jun/2026:08:24:21.676] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:21 np0000072643 haproxy[7]: 192.168.122.104:46036 [13/Jun/2026:08:24:21.420] redis redis/np0000072641.internalapi.localdomain 1/3/269 4431 -- 41/41/39/39/0 0/0
Jun 13 08:24:21 np0000072643 haproxy[7]: 192.168.122.104:46074 [13/Jun/2026:08:24:21.961] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:21 np0000072643 haproxy[7]: 192.168.122.104:46062 [13/Jun/2026:08:24:21.715] redis redis/np0000072641.internalapi.localdomain 1/0/258 4431 -- 40/40/39/39/0 0/0
Jun 13 08:24:26 np0000072643 haproxy[7]: 192.168.122.110:40046 [13/Jun/2026:08:24:26.209] redis redis/np0000072641.internalapi.localdomain 1/0/283 4428 -- 41/41/39/39/0 0/0
Jun 13 08:24:26 np0000072643 haproxy[7]: 192.168.122.110:40052 [13/Jun/2026:08:24:26.481] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/39/39/0 0/0
Jun 13 08:24:26 np0000072643 haproxy[7]: 192.168.122.110:40068 [13/Jun/2026:08:24:26.768] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:26 np0000072643 haproxy[7]: 192.168.122.110:40062 [13/Jun/2026:08:24:26.511] redis redis/np0000072641.internalapi.localdomain 1/0/267 4428 -- 40/40/39/39/0 0/0
Jun 13 08:24:27 np0000072643 haproxy[7]: 192.168.122.110:40088 [13/Jun/2026:08:24:27.059] redis redis/np0000072641.internalapi.localdomain 1/1/14 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:27 np0000072643 haproxy[7]: 192.168.122.110:40080 [13/Jun/2026:08:24:26.801] redis redis/np0000072641.internalapi.localdomain 1/0/273 4429 -- 41/41/40/40/0 0/0
Jun 13 08:24:27 np0000072643 haproxy[7]: 192.168.122.104:46092 [13/Jun/2026:08:24:27.269] redis redis/np0000072641.internalapi.localdomain 1/0/8 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:27 np0000072643 haproxy[7]: 192.168.122.104:46086 [13/Jun/2026:08:24:27.007] redis redis/np0000072641.internalapi.localdomain 1/0/270 4429 -- 42/42/40/40/0 0/0
Jun 13 08:24:27 np0000072643 haproxy[7]: 192.168.122.110:40110 [13/Jun/2026:08:24:27.359] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:27 np0000072643 haproxy[7]: 192.168.122.110:40102 [13/Jun/2026:08:24:27.105] redis redis/np0000072641.internalapi.localdomain 1/0/267 4429 -- 42/42/40/40/0 0/0
Jun 13 08:24:27 np0000072643 haproxy[7]: 192.168.122.104:46104 [13/Jun/2026:08:24:27.538] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:27 np0000072643 haproxy[7]: 192.168.122.104:46100 [13/Jun/2026:08:24:27.304] redis redis/np0000072641.internalapi.localdomain 1/0/245 4429 -- 40/40/39/39/0 0/0
Jun 13 08:24:27 np0000072643 haproxy[7]: 192.168.122.104:46130 [13/Jun/2026:08:24:27.839] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/39/39/0 0/0
Jun 13 08:24:27 np0000072643 haproxy[7]: 192.168.122.104:46116 [13/Jun/2026:08:24:27.581] redis redis/np0000072641.internalapi.localdomain 1/0/270 4429 -- 41/41/39/39/0 0/0
Jun 13 08:24:28 np0000072643 haproxy[7]: 192.168.122.104:46146 [13/Jun/2026:08:24:28.134] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:28 np0000072643 haproxy[7]: 192.168.122.104:46132 [13/Jun/2026:08:24:27.886] redis redis/np0000072641.internalapi.localdomain 1/0/260 4429 -- 40/40/39/39/0 0/0
Jun 13 08:24:32 np0000072643 haproxy[7]: 192.168.122.110:40342 [13/Jun/2026:08:24:32.713] redis redis/np0000072641.internalapi.localdomain 1/0/13 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:32 np0000072643 haproxy[7]: 192.168.122.110:40328 [13/Jun/2026:08:24:32.411] redis redis/np0000072641.internalapi.localdomain 1/0/322 4429 -- 40/40/39/39/0 0/0
Jun 13 08:24:33 np0000072643 haproxy[7]: 192.168.122.110:40354 [13/Jun/2026:08:24:33.005] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:33 np0000072643 haproxy[7]: 192.168.122.110:40352 [13/Jun/2026:08:24:32.746] redis redis/np0000072641.internalapi.localdomain 1/0/271 4429 -- 41/41/39/39/0 0/0
Jun 13 08:24:33 np0000072643 haproxy[7]: 192.168.122.110:40366 [13/Jun/2026:08:24:33.295] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:33 np0000072643 haproxy[7]: 192.168.122.110:40356 [13/Jun/2026:08:24:33.048] redis redis/np0000072641.internalapi.localdomain 1/0/259 4430 -- 42/42/40/40/0 0/0
Jun 13 08:24:33 np0000072643 haproxy[7]: 192.168.122.104:56472 [13/Jun/2026:08:24:33.460] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:33 np0000072643 haproxy[7]: 192.168.122.104:56462 [13/Jun/2026:08:24:33.180] redis redis/np0000072641.internalapi.localdomain 1/0/291 4430 -- 42/42/40/40/0 0/0
Jun 13 08:24:33 np0000072643 haproxy[7]: 192.168.122.110:40386 [13/Jun/2026:08:24:33.587] redis redis/np0000072641.internalapi.localdomain 1/0/14 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:33 np0000072643 haproxy[7]: 192.168.122.110:40372 [13/Jun/2026:08:24:33.335] redis redis/np0000072641.internalapi.localdomain 1/0/266 4430 -- 42/42/40/40/0 0/0
Jun 13 08:24:33 np0000072643 haproxy[7]: 192.168.122.104:56496 [13/Jun/2026:08:24:33.802] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:33 np0000072643 haproxy[7]: 192.168.122.104:56484 [13/Jun/2026:08:24:33.504] redis redis/np0000072641.internalapi.localdomain 1/0/310 4430 -- 40/40/39/39/0 0/0
Jun 13 08:24:34 np0000072643 haproxy[7]: 192.168.122.104:56508 [13/Jun/2026:08:24:34.076] redis redis/np0000072641.internalapi.localdomain 1/0/16 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:34 np0000072643 haproxy[7]: 192.168.122.104:56498 [13/Jun/2026:08:24:33.834] redis redis/np0000072641.internalapi.localdomain 1/0/258 4430 -- 41/41/39/39/0 0/0
Jun 13 08:24:34 np0000072643 haproxy[7]: 192.168.122.104:56528 [13/Jun/2026:08:24:34.362] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:34 np0000072643 haproxy[7]: 192.168.122.104:56514 [13/Jun/2026:08:24:34.119] redis redis/np0000072641.internalapi.localdomain 1/0/253 4430 -- 41/41/39/39/0 0/0
Jun 13 08:24:38 np0000072643 haproxy[7]: 192.168.122.110:38384 [13/Jun/2026:08:24:38.639] redis redis/np0000072641.internalapi.localdomain 1/0/279 4429 -- 41/41/40/40/0 0/0
Jun 13 08:24:38 np0000072643 haproxy[7]: 192.168.122.110:38392 [13/Jun/2026:08:24:38.909] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 40/40/39/39/0 0/0
Jun 13 08:24:39 np0000072643 haproxy[7]: 192.168.122.110:38398 [13/Jun/2026:08:24:39.168] redis redis/np0000072641.internalapi.localdomain 1/0/16 10 -- 41/41/39/39/0 0/0
Jun 13 08:24:39 np0000072643 haproxy[7]: 192.168.122.110:38394 [13/Jun/2026:08:24:38.939] redis redis/np0000072641.internalapi.localdomain 1/0/246 4430 -- 41/41/39/39/0 0/0
Jun 13 08:24:39 np0000072643 haproxy[7]: 192.168.122.110:38412 [13/Jun/2026:08:24:39.221] redis redis/np0000072641.internalapi.localdomain 1/0/281 4431 -- 42/42/40/40/0 0/0
Jun 13 08:24:39 np0000072643 haproxy[7]: 192.168.122.110:38416 [13/Jun/2026:08:24:39.490] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 42/42/40/40/0 0/0
Jun 13 08:24:39 np0000072643 haproxy[7]: 192.168.122.104:52814 [13/Jun/2026:08:24:39.664] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:39 np0000072643 haproxy[7]: 192.168.122.104:56538 [13/Jun/2026:08:24:39.408] redis redis/np0000072641.internalapi.localdomain 1/0/268 4431 -- 42/42/40/40/0 0/0
Jun 13 08:24:39 np0000072643 haproxy[7]: 192.168.122.110:38430 [13/Jun/2026:08:24:39.837] redis redis/np0000072641.internalapi.localdomain 1/0/23 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:39 np0000072643 haproxy[7]: 192.168.122.110:38426 [13/Jun/2026:08:24:39.535] redis redis/np0000072641.internalapi.localdomain 1/0/325 4431 -- 41/41/40/40/0 0/0
Jun 13 08:24:39 np0000072643 haproxy[7]: 192.168.122.104:52828 [13/Jun/2026:08:24:39.699] redis redis/np0000072641.internalapi.localdomain 1/0/244 4431 -- 41/41/40/40/0 0/0
Jun 13 08:24:39 np0000072643 haproxy[7]: 192.168.122.104:52842 [13/Jun/2026:08:24:39.933] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/39/39/0 0/0
Jun 13 08:24:40 np0000072643 haproxy[7]: 192.168.122.104:52862 [13/Jun/2026:08:24:40.230] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:40 np0000072643 haproxy[7]: 192.168.122.104:52854 [13/Jun/2026:08:24:39.974] redis redis/np0000072641.internalapi.localdomain 1/0/268 4432 -- 41/41/39/39/0 0/0
Jun 13 08:24:40 np0000072643 haproxy[7]: 192.168.122.104:52870 [13/Jun/2026:08:24:40.260] redis redis/np0000072641.internalapi.localdomain 1/0/235 4432 -- 41/41/40/40/0 0/0
Jun 13 08:24:40 np0000072643 haproxy[7]: 192.168.122.104:52882 [13/Jun/2026:08:24:40.485] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 40/40/39/39/0 0/0
Jun 13 08:24:45 np0000072643 haproxy[7]: 192.168.122.110:38446 [13/Jun/2026:08:24:45.158] redis redis/np0000072641.internalapi.localdomain 1/0/9 10 -- 41/41/40/39/0 0/0
Jun 13 08:24:45 np0000072643 haproxy[7]: 192.168.122.110:38444 [13/Jun/2026:08:24:44.899] redis redis/np0000072641.internalapi.localdomain 1/0/268 4431 -- 41/41/39/39/0 0/0
Jun 13 08:24:45 np0000072643 haproxy[7]: 192.168.122.110:38468 [13/Jun/2026:08:24:45.450] redis redis/np0000072641.internalapi.localdomain 1/0/13 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:45 np0000072643 haproxy[7]: 192.168.122.110:38454 [13/Jun/2026:08:24:45.195] redis redis/np0000072641.internalapi.localdomain 1/0/268 4431 -- 40/40/39/39/0 0/0
Jun 13 08:24:45 np0000072643 haproxy[7]: 192.168.122.110:38488 [13/Jun/2026:08:24:45.764] redis redis/np0000072641.internalapi.localdomain 1/0/18 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:45 np0000072643 haproxy[7]: 192.168.122.110:38482 [13/Jun/2026:08:24:45.494] redis redis/np0000072641.internalapi.localdomain 1/0/288 4432 -- 42/42/40/40/0 0/0
Jun 13 08:24:45 np0000072643 haproxy[7]: 192.168.122.104:52904 [13/Jun/2026:08:24:45.790] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/39/39/0 0/0
Jun 13 08:24:45 np0000072643 haproxy[7]: 192.168.122.104:52898 [13/Jun/2026:08:24:45.528] redis redis/np0000072641.internalapi.localdomain 1/0/272 4432 -- 41/41/39/39/0 0/0
Jun 13 08:24:46 np0000072643 haproxy[7]: 192.168.122.104:52930 [13/Jun/2026:08:24:46.055] redis redis/np0000072641.internalapi.localdomain 1/1/13 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:46 np0000072643 haproxy[7]: 192.168.122.104:52916 [13/Jun/2026:08:24:45.825] redis redis/np0000072641.internalapi.localdomain 1/0/244 4433 -- 41/41/40/40/0 0/0
Jun 13 08:24:46 np0000072643 haproxy[7]: 192.168.122.110:38492 [13/Jun/2026:08:24:45.812] redis redis/np0000072641.internalapi.localdomain 1/0/291 4433 -- 42/42/40/40/0 0/0
Jun 13 08:24:46 np0000072643 haproxy[7]: 192.168.122.110:38494 [13/Jun/2026:08:24:46.091] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 42/42/40/40/0 0/0
Jun 13 08:24:46 np0000072643 haproxy[7]: 192.168.122.104:52944 [13/Jun/2026:08:24:46.366] redis redis/np0000072641.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:46 np0000072643 haproxy[7]: 192.168.122.104:52940 [13/Jun/2026:08:24:46.099] redis redis/np0000072641.internalapi.localdomain 1/0/279 4433 -- 40/40/39/39/0 0/0
Jun 13 08:24:46 np0000072643 haproxy[7]: 192.168.122.104:52960 [13/Jun/2026:08:24:46.407] redis redis/np0000072641.internalapi.localdomain 1/0/264 4433 -- 41/41/40/40/0 0/0
Jun 13 08:24:46 np0000072643 haproxy[7]: 192.168.122.104:52972 [13/Jun/2026:08:24:46.660] redis redis/np0000072641.internalapi.localdomain 1/0/14 10 -- 40/40/39/39/0 0/0
Jun 13 08:24:51 np0000072643 haproxy[7]: 192.168.122.110:59770 [13/Jun/2026:08:24:51.408] redis redis/np0000072641.internalapi.localdomain 1/0/11 10 -- 41/41/40/39/0 0/0
Jun 13 08:24:51 np0000072643 haproxy[7]: 192.168.122.110:59768 [13/Jun/2026:08:24:51.142] redis redis/np0000072641.internalapi.localdomain 1/0/277 4432 -- 41/41/39/39/0 0/0
Jun 13 08:24:51 np0000072643 haproxy[7]: 192.168.122.110:59786 [13/Jun/2026:08:24:51.730] redis redis/np0000072641.internalapi.localdomain 1/0/14 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:51 np0000072643 haproxy[7]: 192.168.122.110:59782 [13/Jun/2026:08:24:51.450] redis redis/np0000072641.internalapi.localdomain 1/0/294 4432 -- 42/42/40/40/0 0/0
Jun 13 08:24:51 np0000072643 haproxy[7]: 192.168.122.104:55036 [13/Jun/2026:08:24:51.957] redis redis/np0000072641.internalapi.localdomain 1/0/15 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:51 np0000072643 haproxy[7]: 192.168.122.104:55020 [13/Jun/2026:08:24:51.701] redis redis/np0000072641.internalapi.localdomain 1/0/271 4432 -- 42/42/40/40/0 0/0
Jun 13 08:24:52 np0000072643 haproxy[7]: 192.168.122.110:59812 [13/Jun/2026:08:24:52.024] redis redis/np0000072641.internalapi.localdomain 1/0/15 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:52 np0000072643 haproxy[7]: 192.168.122.110:59802 [13/Jun/2026:08:24:51.766] redis redis/np0000072641.internalapi.localdomain 1/0/273 4433 -- 41/41/40/40/0 0/0
Jun 13 08:24:52 np0000072643 haproxy[7]: 192.168.122.104:55052 [13/Jun/2026:08:24:52.257] redis redis/np0000072641.internalapi.localdomain 1/0/8 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:52 np0000072643 haproxy[7]: 192.168.122.104:55048 [13/Jun/2026:08:24:51.992] redis redis/np0000072641.internalapi.localdomain 1/0/274 4433 -- 41/41/40/40/0 0/0
Jun 13 08:24:52 np0000072643 haproxy[7]: 192.168.122.110:59838 [13/Jun/2026:08:24:52.353] redis redis/np0000072641.internalapi.localdomain 1/0/13 10 -- 42/42/41/41/0 0/0
Jun 13 08:24:52 np0000072643 haproxy[7]: 192.168.122.110:59826 [13/Jun/2026:08:24:52.068] redis redis/np0000072641.internalapi.localdomain 1/0/298 4433 -- 41/41/40/40/0 0/0
Jun 13 08:24:52 np0000072643 haproxy[7]: 192.168.122.104:55066 [13/Jun/2026:08:24:52.538] redis redis/np0000072641.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0
Jun 13 08:24:52 np0000072643 haproxy[7]: 192.168.122.104:55058 [13/Jun/2026:08:24:52.293] redis redis/np0000072641.internalapi.localdomain 1/0/256 4433 -- 40/40/39/39/0 0/0
Jun 13 08:24:52 np0000072643 haproxy[7]: 192.168.122.104:55074 [13/Jun/2026:08:24:52.577] redis redis/np0000072641.internalapi.localdomain 1/0/301 4433 -- 41/41/40/40/0 0/0
Jun 13 08:24:52 np0000072643 haproxy[7]: 192.168.122.104:55084 [13/Jun/2026:08:24:52.867] redis redis/np0000072641.internalapi.localdomain 1/0/15 10 -- 40/40/39/39/0 0/0
Jun 13 08:24:54 np0000072643 haproxy[7]: 192.168.122.103:57508 [13/Jun/2026:08:24:54.191] redis redis/np0000072641.internalapi.localdomain 1/0/28 14 -- 40/40/39/39/0 0/0
Jun 13 08:25:00 np0000072643 haproxy[7]: Server gnocchi/np0000072641.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.
Jun 13 08:35:45 np0000072643 haproxy[7]: Server aodh/np0000072641.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.
Jun 13 08:35:49 np0000072643 haproxy[7]: Server aodh/np0000072642.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.
Jun 13 08:35:49 np0000072643 haproxy[7]: 192.168.122.103:60948 [13/Jun/2026:08:19:21.068] redis redis/np0000072641.internalapi.localdomain 1/0/988429 21310 -- 80/80/79/79/0 0/0
Jun 13 08:35:49 np0000072643 haproxy[7]: 192.168.122.103:60972 [13/Jun/2026:08:19:21.311] redis redis/np0000072641.internalapi.localdomain 1/0/988192 21336 -- 79/79/78/78/0 0/0
Jun 13 08:35:49 np0000072643 haproxy[7]: 192.168.122.103:43566 [13/Jun/2026:08:30:22.299] redis redis/np0000072641.internalapi.localdomain 1/3/327556 10 -- 78/78/77/77/0 0/0
Jun 13 08:35:49 np0000072643 haproxy[7]: 192.168.122.103:43578 [13/Jun/2026:08:30:22.299] redis redis/np0000072641.internalapi.localdomain 1/3/327561 6247 -- 77/77/76/76/0 0/0
Jun 13 08:35:49 np0000072643 haproxy[7]: 192.168.122.103:60934 [13/Jun/2026:08:19:20.991] redis redis/np0000072641.internalapi.localdomain 1/0/988519 15185 -- 76/76/75/75/0 0/0
Jun 13 08:35:49 np0000072643 haproxy[7]: 192.168.122.103:45768 [13/Jun/2026:08:20:21.212] redis redis/np0000072641.internalapi.localdomain 1/0/928298 15930 -- 75/75/74/74/0 0/0
Jun 13 08:35:49 np0000072643 haproxy[7]: 192.168.122.103:60952 [13/Jun/2026:08:19:21.135] redis redis/np0000072641.internalapi.localdomain 1/0/988376 5471 -- 74/74/73/73/0 0/0
Jun 13 08:35:51 np0000072643 haproxy[7]: 192.168.122.104:51396 [13/Jun/2026:08:19:38.523] redis redis/np0000072641.internalapi.localdomain 1/0/972190 21277 -- 73/73/72/72/0 0/0
Jun 13 08:35:51 np0000072643 haproxy[7]: 192.168.122.104:51374 [13/Jun/2026:08:19:38.193] redis redis/np0000072641.internalapi.localdomain 1/0/972525 21300 -- 72/72/71/71/0 0/0
Jun 13 08:35:51 np0000072643 haproxy[7]: 192.168.122.104:46572 [13/Jun/2026:08:20:38.467] redis redis/np0000072641.internalapi.localdomain 1/0/912251 15822 -- 71/71/70/70/0 0/0
Jun 13 08:35:51 np0000072643 haproxy[7]: 192.168.122.104:51392 [13/Jun/2026:08:19:38.400] redis redis/np0000072641.internalapi.localdomain 1/1/972319 5486 -- 70/70/69/69/0 0/0
Jun 13 08:35:51 np0000072643 haproxy[7]: 192.168.122.104:51404 [13/Jun/2026:08:19:38.802] redis redis/np0000072641.internalapi.localdomain 1/0/971926 21326 -- 69/69/68/68/0 0/0
Jun 13 08:35:52 np0000072643 haproxy[7]: 192.168.122.110:58488 [13/Jun/2026:08:19:38.740] redis redis/np0000072641.internalapi.localdomain 1/1/973173 21276 -- 68/68/67/67/0 0/0
Jun 13 08:35:52 np0000072643 haproxy[7]: 192.168.122.110:58494 [13/Jun/2026:08:19:38.968] redis redis/np0000072641.internalapi.localdomain 1/5/972948 21303 -- 67/67/66/66/0 0/0
Jun 13 08:35:52 np0000072643 haproxy[7]: 192.168.122.110:58476 [13/Jun/2026:08:19:38.739] redis redis/np0000072641.internalapi.localdomain 1/0/973179 21293 -- 66/66/65/65/0 0/0
Jun 13 08:35:52 np0000072643 haproxy[7]: 192.168.122.110:33064 [13/Jun/2026:08:20:38.794] redis redis/np0000072641.internalapi.localdomain 1/0/913124 15 -- 66/66/64/64/0 0/0
Jun 13 08:35:52 np0000072643 haproxy[7]: 192.168.122.110:58464 [13/Jun/2026:08:19:38.657] redis redis/np0000072641.internalapi.localdomain 1/0/973266 21330 -- 64/64/63/63/0 0/0
Jun 13 08:35:54 np0000072643 haproxy[7]: Server aodh/np0000072643.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.
Jun 13 08:35:54 np0000072643 haproxy[7]: proxy aodh has no server available!
Jun 13 08:37:54 np0000072643 haproxy[7]: 192.168.122.103:60960 [13/Jun/2026:08:19:21.215] redis redis/np0000072641.internalapi.localdomain 1/0/1112679 5916 -- 63/63/62/62/0 0/0
Jun 13 08:37:55 np0000072643 haproxy[7]: 192.168.122.104:51390 [13/Jun/2026:08:19:38.212] redis redis/np0000072641.internalapi.localdomain 1/0/1097273 6080 -- 62/62/61/61/0 0/0
Jun 13 08:37:57 np0000072643 haproxy[7]: 192.168.122.110:36454 [13/Jun/2026:08:19:38.468] redis redis/np0000072641.internalapi.localdomain 1/0/1098243 5055 -- 61/61/60/60/0 0/0
Jun 13 08:37:57 np0000072643 haproxy[7]: 192.168.122.110:36464 [13/Jun/2026:08:19:38.475] redis redis/np0000072641.internalapi.localdomain 1/0/1098237 1207 -- 61/61/59/59/0 0/0
Jun 13 08:39:10 np0000072643 haproxy[7]: Server horizon/np0000072641.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.
Jun 13 08:39:14 np0000072643 haproxy[7]: Server horizon/np0000072642.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.
Jun 13 08:39:18 np0000072643 haproxy[7]: Server horizon/np0000072643.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.
Jun 13 08:39:18 np0000072643 haproxy[7]: proxy horizon has no server available!
Jun 13 08:39:22 np0000072643 haproxy[7]: Server keystone_public/np0000072641.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.
Jun 13 08:39:22 np0000072643 haproxy[7]: Server keystone_admin/np0000072641.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.
Jun 13 08:39:27 np0000072643 haproxy[7]: Server keystone_public/np0000072642.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.
Jun 13 08:39:27 np0000072643 haproxy[7]: Server keystone_admin/np0000072642.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.
Jun 13 08:39:31 np0000072643 haproxy[7]: Server keystone_public/np0000072643.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.
Jun 13 08:39:31 np0000072643 haproxy[7]: proxy keystone_public has no server available!
Jun 13 08:39:31 np0000072643 haproxy[7]: Server keystone_admin/np0000072643.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.
Jun 13 08:39:31 np0000072643 haproxy[7]: proxy keystone_admin has no server available!
Jun 13 08:39:38 np0000072643 haproxy[7]: Server cinder/np0000072641.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.
Jun 13 08:39:42 np0000072643 haproxy[7]: Server cinder/np0000072642.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.
Jun 13 08:39:46 np0000072643 haproxy[7]: Server cinder/np0000072643.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.
Jun 13 08:39:46 np0000072643 haproxy[7]: proxy cinder has no server available!
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:57596 [13/Jun/2026:08:24:58.529] redis redis/np0000072641.internalapi.localdomain 1/0/1016546 4778 -- 60/60/57/56/0 0/0
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:57556 [13/Jun/2026:08:24:56.714] redis redis/np0000072641.internalapi.localdomain 1/0/1018362 4768 -- 60/60/55/55/0 0/0
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:58996 [13/Jun/2026:08:34:28.965] redis redis/np0000072641.internalapi.localdomain 1/0/446481 22 -- 60/60/55/55/0 0/0
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:57456 [13/Jun/2026:08:25:00.669] redis redis/np0000072641.internalapi.localdomain 1/0/1014407 4773 -- 60/60/57/57/0 0/0
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:58998 [13/Jun/2026:08:34:29.018] redis redis/np0000072641.internalapi.localdomain 1/0/446428 30 -- 60/60/55/55/0 0/0
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:57588 [13/Jun/2026:08:24:58.440] redis redis/np0000072641.internalapi.localdomain 1/0/1016635 4778 -- 57/57/54/54/0 0/0
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:57466 [13/Jun/2026:08:25:01.362] redis redis/np0000072641.internalapi.localdomain 1/0/1013715 4773 -- 55/55/53/53/0 0/0
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:58980 [13/Jun/2026:08:34:28.881] redis redis/np0000072641.internalapi.localdomain 1/0/446566 38 -- 53/53/52/52/0 0/0
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:57462 [13/Jun/2026:08:25:01.135] redis redis/np0000072641.internalapi.localdomain 1/0/1013941 4772 -- 52/52/51/51/0 0/0
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:59002 [13/Jun/2026:08:34:29.020] redis redis/np0000072641.internalapi.localdomain 1/0/446433 30 -- 51/51/50/50/0 0/0
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:57598 [13/Jun/2026:08:24:58.554] redis redis/np0000072641.internalapi.localdomain 1/0/1016529 4778 -- 51/51/49/49/0 0/0
Jun 13 08:41:55 np0000072643 haproxy[7]: 192.168.122.103:57480 [13/Jun/2026:08:25:01.702] redis redis/np0000072641.internalapi.localdomain 1/0/1013381 4773 -- 51/51/48/48/0 0/0
Jun 13 08:41:57 np0000072643 haproxy[7]: Server glance_api/np0000072641.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.
Jun 13 08:41:58 np0000072643 haproxy[7]: Server glance_api/np0000072642.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.
Jun 13 08:41:59 np0000072643 haproxy[7]: Server glance_api/np0000072643.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.
Jun 13 08:41:59 np0000072643 haproxy[7]: proxy glance_api has no server available!
Jun 13 08:41:59 np0000072643 haproxy[7]: 192.168.122.104:55132 [13/Jun/2026:08:24:58.802] redis redis/np0000072641.internalapi.localdomain 1/0/1020335 4783 -- 48/48/47/47/0 0/0
Jun 13 08:41:59 np0000072643 haproxy[7]: 192.168.122.104:46160 [13/Jun/2026:08:23:32.477] redis redis/np0000072641.internalapi.localdomain 1/1/1106660 4794 -- 48/48/46/46/0 0/0
Jun 13 08:41:59 np0000072643 haproxy[7]: 192.168.122.104:50820 [13/Jun/2026:08:33:00.720] redis redis/np0000072641.internalapi.localdomain 1/0/538767 70 -- 46/46/45/45/0 0/0
Jun 13 08:41:59 np0000072643 haproxy[7]: 192.168.122.104:46188 [13/Jun/2026:08:23:32.629] redis redis/np0000072641.internalapi.localdomain 1/0/1106510 4794 -- 45/45/44/44/0 0/0
Jun 13 08:41:59 np0000072643 haproxy[7]: 192.168.122.104:35848 [13/Jun/2026:08:24:59.436] redis redis/np0000072641.internalapi.localdomain 1/0/1019702 4777 -- 44/44/43/43/0 0/0
Jun 13 08:41:59 np0000072643 haproxy[7]: 192.168.122.104:57444 [13/Jun/2026:08:34:29.019] redis redis/np0000072641.internalapi.localdomain 1/0/450490 30 -- 44/44/42/42/0 0/0
Jun 13 08:41:59 np0000072643 haproxy[7]: 192.168.122.104:55134 [13/Jun/2026:08:24:59.037] redis redis/np0000072641.internalapi.localdomain 1/0/1020101 4778 -- 42/42/41/41/0 0/0
Jun 13 08:41:59 np0000072643 haproxy[7]: 192.168.122.104:39558 [13/Jun/2026:08:31:57.898] redis redis/np0000072641.internalapi.localdomain 1/0/601592 46 -- 41/41/40/40/0 0/0
Jun 13 08:41:59 np0000072643 haproxy[7]: 192.168.122.104:46144 [13/Jun/2026:08:23:32.143] redis redis/np0000072641.internalapi.localdomain 1/0/1106996 4794 -- 40/40/39/39/0 0/0
Jun 13 08:41:59 np0000072643 haproxy[7]: 192.168.122.104:55120 [13/Jun/2026:08:24:58.349] redis redis/np0000072641.internalapi.localdomain 1/0/1020791 4783 -- 39/39/38/38/0 0/0
Jun 13 08:41:59 np0000072643 haproxy[7]: 192.168.122.104:46174 [13/Jun/2026:08:23:32.485] redis redis/np0000072641.internalapi.localdomain 1/0/1106655 4794 -- 39/39/37/37/0 0/0
Jun 13 08:42:03 np0000072643 haproxy[7]: Server gnocchi/np0000072641.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.
Jun 13 08:42:03 np0000072643 haproxy[7]: 192.168.122.110:43136 [13/Jun/2026:08:34:28.899] redis redis/np0000072641.internalapi.localdomain 1/0/454691 22 -- 37/37/36/36/0 0/0
Jun 13 08:42:03 np0000072643 haproxy[7]: 192.168.122.110:59868 [13/Jun/2026:08:24:58.185] redis redis/np0000072641.internalapi.localdomain 1/0/1025033 4780 -- 37/37/35/35/0 0/0
Jun 13 08:42:03 np0000072643 haproxy[7]: 192.168.122.110:56412 [13/Jun/2026:08:24:59.254] redis redis/np0000072641.internalapi.localdomain 1/0/1023965 4783 -- 36/36/32/32/0 0/0
Jun 13 08:42:03 np0000072643 haproxy[7]: 192.168.122.110:51848 [13/Jun/2026:08:31:57.926] redis redis/np0000072641.internalapi.localdomain 1/0/605645 22 -- 37/37/33/33/0 0/0
Jun 13 08:42:03 np0000072643 haproxy[7]: 192.168.122.110:48144 [13/Jun/2026:08:23:36.836] redis redis/np0000072641.internalapi.localdomain 1/0/1106383 4793 -- 37/37/33/33/0 0/0
Jun 13 08:42:03 np0000072643 haproxy[7]: 192.168.122.110:46710 [13/Jun/2026:08:23:38.662] redis redis/np0000072641.internalapi.localdomain 1/0/1104558 4794 -- 35/35/31/31/0 0/0
Jun 13 08:42:03 np0000072643 haproxy[7]: 192.168.122.110:46708 [13/Jun/2026:08:23:38.600] redis redis/np0000072641.internalapi.localdomain 1/0/1104619 4794 -- 33/33/30/30/0 0/0
Jun 13 08:42:03 np0000072643 haproxy[7]: 192.168.122.110:56416 [13/Jun/2026:08:24:59.696] redis redis/np0000072641.internalapi.localdomain 1/0/1023524 4780 -- 31/31/29/29/0 0/0
Jun 13 08:42:03 np0000072643 haproxy[7]: 192.168.122.110:48178 [13/Jun/2026:08:23:38.392] redis redis/np0000072641.internalapi.localdomain 1/0/1104828 4794 -- 29/29/28/28/0 0/0
Jun 13 08:42:03 np0000072643 haproxy[7]: 192.168.122.110:56402 [13/Jun/2026:08:24:58.643] redis redis/np0000072641.internalapi.localdomain 1/0/1024577 4782 -- 28/28/27/27/0 0/0
Jun 13 08:42:05 np0000072643 haproxy[7]: 192.168.122.103:57538 [13/Jun/2026:08:24:56.346] redis redis/np0000072641.internalapi.localdomain 1/0/1027996 4776 -- 27/27/26/26/0 0/0
Jun 13 08:42:05 np0000072643 haproxy[7]: 192.168.122.103:57524 [13/Jun/2026:08:24:56.345] redis redis/np0000072641.internalapi.localdomain 1/0/1027999 149 -- 26/26/25/25/0 0/0
Jun 13 08:42:05 np0000072643 haproxy[7]: 192.168.122.103:57572 [13/Jun/2026:08:24:57.554] redis redis/np0000072641.internalapi.localdomain 1/0/1026807 35258 -- 25/25/24/24/0 0/0
Jun 13 08:42:05 np0000072643 haproxy[7]: 192.168.122.103:45262 [13/Jun/2026:08:31:57.903] redis redis/np0000072641.internalapi.localdomain 1/0/606810 3675 -- 25/25/23/23/0 0/0
Jun 13 08:42:05 np0000072643 haproxy[7]: 192.168.122.103:57550 [13/Jun/2026:08:24:56.524] redis redis/np0000072641.internalapi.localdomain 1/0/1027838 2238 -- 23/23/22/22/0 0/0
Jun 13 08:42:05 np0000072643 haproxy[7]: 192.168.122.103:57516 [13/Jun/2026:08:24:56.304] redis redis/np0000072641.internalapi.localdomain 1/0/1028056 48844 -- 22/22/21/21/0 0/0
Jun 13 08:42:06 np0000072643 haproxy[7]: 192.168.122.104:46112 [13/Jun/2026:08:23:31.785] redis redis/np0000072641.internalapi.localdomain 1/0/1113842 4800 -- 21/21/20/20/0 0/0
Jun 13 08:42:06 np0000072643 haproxy[7]: 192.168.122.104:46110 [13/Jun/2026:08:23:31.737] redis redis/np0000072641.internalapi.localdomain 1/0/1113892 154 -- 20/20/19/19/0 0/0
Jun 13 08:42:06 np0000072643 haproxy[7]: 192.168.122.104:55100 [13/Jun/2026:08:24:58.172] redis redis/np0000072641.internalapi.localdomain 1/0/1027466 2238 -- 19/19/18/18/0 0/0
Jun 13 08:42:06 np0000072643 haproxy[7]: 192.168.122.104:55096 [13/Jun/2026:08:24:57.915] redis redis/np0000072641.internalapi.localdomain 1/0/1027724 50144 -- 19/19/17/17/0 0/0
Jun 13 08:42:06 np0000072643 haproxy[7]: 192.168.122.104:47324 [13/Jun/2026:08:32:27.969] redis redis/np0000072641.internalapi.localdomain 1/0/578020 1444 -- 17/17/15/15/0 0/0
Jun 13 08:42:06 np0000072643 haproxy[7]: 192.168.122.104:55116 [13/Jun/2026:08:24:58.213] redis redis/np0000072641.internalapi.localdomain 1/0/1027425 34438 -- 17/17/15/15/0 0/0
Jun 13 08:42:07 np0000072643 haproxy[7]: 192.168.122.110:48122 [13/Jun/2026:08:23:36.633] redis redis/np0000072641.internalapi.localdomain 1/0/1110275 4802 -- 15/15/14/14/0 0/0
Jun 13 08:42:07 np0000072643 haproxy[7]: 192.168.122.110:48136 [13/Jun/2026:08:23:36.642] redis redis/np0000072641.internalapi.localdomain 1/0/1110270 154 -- 14/14/13/13/0 0/0
Jun 13 08:42:07 np0000072643 haproxy[7]: 192.168.122.110:51840 [13/Jun/2026:08:31:57.903] redis redis/np0000072641.internalapi.localdomain 1/0/609375 26752 -- 13/13/12/12/0 0/0
Jun 13 08:42:07 np0000072643 haproxy[7]: 192.168.122.110:59864 [13/Jun/2026:08:24:57.674] redis redis/np0000072641.internalapi.localdomain 1/0/1029253 35285 -- 13/13/11/11/0 0/0
Jun 13 08:42:07 np0000072643 haproxy[7]: 192.168.122.110:59844 [13/Jun/2026:08:24:57.401] redis redis/np0000072641.internalapi.localdomain 1/0/1029525 25710 -- 11/11/9/9/0 0/0
Jun 13 08:42:07 np0000072643 haproxy[7]: 192.168.122.110:59854 [13/Jun/2026:08:24:57.644] redis redis/np0000072641.internalapi.localdomain 1/0/1029282 2238 -- 11/11/9/9/0 0/0
Jun 13 08:42:07 np0000072643 haproxy[7]: Server gnocchi/np0000072642.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.
Jun 13 08:42:11 np0000072643 haproxy[7]: Server gnocchi/np0000072643.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.
Jun 13 08:42:11 np0000072643 haproxy[7]: proxy gnocchi has no server available!
Jun 13 08:42:23 np0000072643 haproxy[7]: Server manila/np0000072641.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.
Jun 13 08:42:27 np0000072643 haproxy[7]: Server manila/np0000072642.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.
Jun 13 08:42:32 np0000072643 haproxy[7]: Server manila/np0000072643.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.
Jun 13 08:42:32 np0000072643 haproxy[7]: proxy manila has no server available!
Jun 13 08:43:09 np0000072643 haproxy[7]: Backup Server mysql/np0000072643.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 407ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
Jun 13 08:43:24 np0000072643 haproxy[7]: Backup Server mysql/np0000072643.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 22ms. 0 active and 3 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Jun 13 08:43:50 np0000072643 haproxy[7]: Server neutron/np0000072641.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.
Jun 13 08:44:19 np0000072643 haproxy[7]: Backup Server mysql/np0000072641.internalapi.localdomain is DOWN, reason: Layer4 timeout, check duration: 1001ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
Jun 13 08:44:19 np0000072643 haproxy[7]: Backup Server mysql/np0000072642.internalapi.localdomain is DOWN, reason: Layer4 timeout, check duration: 1001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
Jun 13 08:44:21 np0000072643 haproxy[7]: Backup Server mysql/np0000072643.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 13ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Jun 13 08:44:21 np0000072643 haproxy[7]: proxy mysql has no server available!
Jun 13 08:44:22 np0000072643 haproxy[7]: Backup Server mysql/np0000072641.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 19ms. 0 active and 1 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Jun 13 08:44:25 np0000072643 haproxy[7]: Backup Server mysql/np0000072642.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 1419ms. 0 active and 2 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Jun 13 08:44:25 np0000072643 haproxy[7]: Server neutron/np0000072642.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 334ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Jun 13 08:44:28 np0000072643 haproxy[7]: Backup Server mysql/np0000072643.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 21ms. 0 active and 3 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Jun 13 08:45:05 np0000072643 haproxy[7]: Server neutron/np0000072643.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.
Jun 13 08:45:05 np0000072643 haproxy[7]: proxy neutron has no server available!
Jun 13 08:45:17 np0000072643 haproxy[7]: Server placement/np0000072641.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.
Jun 13 08:45:20 np0000072643 haproxy[7]: Server placement/np0000072642.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.
Jun 13 08:45:25 np0000072643 haproxy[7]: Server placement/np0000072643.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.
Jun 13 08:45:25 np0000072643 haproxy[7]: proxy placement has no server available!
Jun 13 08:45:32 np0000072643 haproxy[7]: Server nova_osapi/np0000072641.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.
Jun 13 08:45:36 np0000072643 haproxy[7]: Server nova_osapi/np0000072642.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.
Jun 13 08:45:40 np0000072643 haproxy[7]: Server nova_osapi/np0000072643.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.
Jun 13 08:45:40 np0000072643 haproxy[7]: proxy nova_osapi has no server available!
Jun 13 08:45:54 np0000072643 haproxy[7]: Server nova_metadata/np0000072641.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.
Jun 13 08:45:58 np0000072643 haproxy[7]: Server nova_metadata/np0000072642.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.
Jun 13 08:46:02 np0000072643 haproxy[7]: Server nova_metadata/np0000072643.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.
Jun 13 08:46:02 np0000072643 haproxy[7]: proxy nova_metadata has no server available!
Jun 13 08:46:45 np0000072643 haproxy[7]: Server nova_novncproxy/np0000072642.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.
Jun 13 08:46:45 np0000072643 haproxy[7]: Server nova_novncproxy/np0000072641.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.
Jun 13 08:46:46 np0000072643 haproxy[7]: Server nova_novncproxy/np0000072643.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.
Jun 13 08:46:46 np0000072643 haproxy[7]: proxy nova_novncproxy has no server available!
Jun 13 09:07:18 np0000072643 haproxy[7]: Backup Server mysql/np0000072643.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 18ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.