Jun 9 08:18:44 np0000068130 haproxy[7]: Server aodh/np0000068128.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 9 08:18:44 np0000068130 haproxy[7]: Server aodh/np0000068129.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 9 08:18:44 np0000068130 haproxy[7]: Server aodh/np0000068130.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 9 08:18:44 np0000068130 haproxy[7]: proxy aodh has no server available! Jun 9 08:18:44 np0000068130 haproxy[7]: Server cinder/np0000068128.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 9 08:18:44 np0000068130 haproxy[7]: Server cinder/np0000068129.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 9 08:18:44 np0000068130 haproxy[7]: Server cinder/np0000068130.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 9 08:18:44 np0000068130 haproxy[7]: proxy cinder has no server available! Jun 9 08:18:45 np0000068130 haproxy[7]: Server glance_api/np0000068128.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 9 08:18:45 np0000068130 haproxy[7]: Server glance_api/np0000068129.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 9 08:18:45 np0000068130 haproxy[7]: Server glance_api/np0000068130.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 9 08:18:45 np0000068130 haproxy[7]: proxy glance_api has no server available! Jun 9 08:18:45 np0000068130 haproxy[7]: Server glance_api_internal/np0000068128.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 9 08:18:45 np0000068130 haproxy[7]: Server glance_api_internal/np0000068129.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 9 08:18:45 np0000068130 haproxy[7]: Server glance_api_internal/np0000068130.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 9 08:18:45 np0000068130 haproxy[7]: proxy glance_api_internal has no server available! Jun 9 08:18:45 np0000068130 haproxy[7]: Server gnocchi/np0000068128.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 9 08:18:45 np0000068130 haproxy[7]: Server gnocchi/np0000068129.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 9 08:18:45 np0000068130 haproxy[7]: Server gnocchi/np0000068130.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 9 08:18:45 np0000068130 haproxy[7]: proxy gnocchi has no server available! Jun 9 08:18:45 np0000068130 haproxy[7]: Server heat_api/np0000068128.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 9 08:18:45 np0000068130 haproxy[7]: Server heat_api/np0000068129.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 9 08:18:45 np0000068130 haproxy[7]: Backup Server mysql/np0000068128.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue. Jun 9 08:18:45 np0000068130 haproxy[7]: Server heat_api/np0000068130.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 9 08:18:45 np0000068130 haproxy[7]: proxy heat_api has no server available! Jun 9 08:18:45 np0000068130 haproxy[7]: Backup Server mysql/np0000068129.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 24ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue. Jun 9 08:18:45 np0000068130 haproxy[7]: Server heat_cfn/np0000068128.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 9 08:18:45 np0000068130 haproxy[7]: Server heat_cfn/np0000068129.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 9 08:18:45 np0000068130 haproxy[7]: Backup Server mysql/np0000068130.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 64ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Jun 9 08:18:45 np0000068130 haproxy[7]: proxy mysql has no server available! Jun 9 08:18:45 np0000068130 haproxy[7]: Server heat_cfn/np0000068130.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 9 08:18:45 np0000068130 haproxy[7]: proxy heat_cfn has no server available! Jun 9 08:18:45 np0000068130 haproxy[7]: Server horizon/np0000068128.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 9 08:18:45 np0000068130 haproxy[7]: Server horizon/np0000068129.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 9 08:18:45 np0000068130 haproxy[7]: Server horizon/np0000068130.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 9 08:18:45 np0000068130 haproxy[7]: proxy horizon has no server available! Jun 9 08:18:45 np0000068130 haproxy[7]: Server keystone_admin/np0000068128.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 9 08:18:45 np0000068130 haproxy[7]: Server keystone_admin/np0000068129.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 9 08:18:45 np0000068130 haproxy[7]: Server keystone_admin/np0000068130.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 9 08:18:45 np0000068130 haproxy[7]: proxy keystone_admin has no server available! Jun 9 08:18:45 np0000068130 haproxy[7]: Server keystone_public/np0000068128.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 9 08:18:45 np0000068130 haproxy[7]: Server keystone_public/np0000068129.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 9 08:18:45 np0000068130 haproxy[7]: Server keystone_public/np0000068130.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 9 08:18:45 np0000068130 haproxy[7]: proxy keystone_public has no server available! Jun 9 08:18:45 np0000068130 haproxy[7]: Server manila/np0000068128.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 9 08:18:45 np0000068130 haproxy[7]: Server manila/np0000068129.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 9 08:18:45 np0000068130 haproxy[7]: Server manila/np0000068130.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 9 08:18:45 np0000068130 haproxy[7]: proxy manila has no server available! Jun 9 08:18:46 np0000068130 haproxy[7]: Server neutron/np0000068128.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 9 08:18:46 np0000068130 haproxy[7]: Server neutron/np0000068129.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 9 08:18:46 np0000068130 haproxy[7]: Server neutron/np0000068130.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 9 08:18:46 np0000068130 haproxy[7]: proxy neutron has no server available! Jun 9 08:18:46 np0000068130 haproxy[7]: Server nova_metadata/np0000068128.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 9 08:18:46 np0000068130 haproxy[7]: Server nova_metadata/np0000068129.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 9 08:18:46 np0000068130 haproxy[7]: Server nova_metadata/np0000068130.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 9 08:18:46 np0000068130 haproxy[7]: proxy nova_metadata has no server available! Jun 9 08:18:46 np0000068130 haproxy[7]: Server nova_novncproxy/np0000068128.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 9 08:18:46 np0000068130 haproxy[7]: Server nova_novncproxy/np0000068129.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 9 08:18:46 np0000068130 haproxy[7]: Server nova_novncproxy/np0000068130.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 9 08:18:46 np0000068130 haproxy[7]: proxy nova_novncproxy has no server available! Jun 9 08:18:46 np0000068130 haproxy[7]: Server nova_osapi/np0000068128.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 9 08:18:46 np0000068130 haproxy[7]: Server nova_osapi/np0000068129.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 9 08:18:46 np0000068130 haproxy[7]: Server nova_osapi/np0000068130.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 9 08:18:46 np0000068130 haproxy[7]: proxy nova_osapi has no server available! Jun 9 08:18:46 np0000068130 haproxy[7]: Server placement/np0000068128.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 9 08:18:46 np0000068130 haproxy[7]: Server placement/np0000068129.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 9 08:18:46 np0000068130 haproxy[7]: Server placement/np0000068130.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 9 08:18:46 np0000068130 haproxy[7]: proxy placement has no server available! Jun 9 08:18:46 np0000068130 haproxy[7]: Server redis/np0000068128.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 9 08:18:46 np0000068130 haproxy[7]: Server redis/np0000068129.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 9 08:18:46 np0000068130 haproxy[7]: Server redis/np0000068130.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 9 08:18:46 np0000068130 haproxy[7]: proxy redis has no server available! Jun 9 08:18:46 np0000068130 haproxy[7]: Server swift_proxy_server/np0000068128.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 9 08:18:46 np0000068130 haproxy[7]: Server swift_proxy_server/np0000068129.storage.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 2ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Jun 9 08:18:46 np0000068130 haproxy[7]: Server swift_proxy_server/np0000068130.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 9 08:18:46 np0000068130 haproxy[7]: proxy swift_proxy_server has no server available! Jun 9 08:20:29 np0000068130 haproxy[7]: Backup Server mysql/np0000068130.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 25ms. 0 active and 1 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue. Jun 9 08:20:53 np0000068130 haproxy[7]: Backup Server mysql/np0000068129.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 25ms. 0 active and 2 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue. Jun 9 08:22:00 np0000068130 haproxy[7]: Server redis/np0000068128.internalapi.localdomain is UP, reason: Layer7 check passed, code: 0, info: "(tcp-check)", check duration: 2ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:22:17 np0000068130 haproxy[7]: Backup Server mysql/np0000068128.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 20ms. 0 active and 3 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue. Jun 9 08:23:02 np0000068130 haproxy[7]: Server keystone_admin/np0000068129.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 8ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:23:02 np0000068130 haproxy[7]: Server keystone_public/np0000068129.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 9 08:23:03 np0000068130 haproxy[7]: Server keystone_admin/np0000068130.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 9 08:23:03 np0000068130 haproxy[7]: Server keystone_public/np0000068130.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 8ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:23:05 np0000068130 haproxy[7]: Server horizon/np0000068129.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 9 08:23:05 np0000068130 haproxy[7]: Server horizon/np0000068130.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 9 08:23:39 np0000068130 haproxy[7]: Server horizon/np0000068128.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 9 08:24:14 np0000068130 haproxy[7]: Server keystone_admin/np0000068128.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 6ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:24:14 np0000068130 haproxy[7]: Server keystone_public/np0000068128.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 9ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:28 np0000068130 haproxy[7]: Server heat_api/np0000068128.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 19ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:28 np0000068130 haproxy[7]: Server aodh/np0000068128.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 597ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:28 np0000068130 haproxy[7]: Server cinder/np0000068128.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 104ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:28 np0000068130 haproxy[7]: Server heat_cfn/np0000068128.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 9 08:28:34 np0000068130 haproxy[7]: Server nova_novncproxy/np0000068128.internalapi.localdomain is UP, reason: Layer4 check passed, check duration: 1481ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:34 np0000068130 haproxy[7]: Server manila/np0000068128.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 2857ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:38 np0000068130 haproxy[7]: Server placement/np0000068128.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 9 08:28:40 np0000068130 haproxy[7]: Server nova_metadata/np0000068128.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 9 08:28:40 np0000068130 haproxy[7]: Server swift_proxy_server/np0000068128.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 9 08:28:40 np0000068130 haproxy[7]: Server glance_api_internal/np0000068128.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 6ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:40 np0000068130 haproxy[7]: Server glance_api/np0000068128.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 9 08:28:40 np0000068130 haproxy[7]: Server neutron/np0000068128.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 19ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:40 np0000068130 haproxy[7]: Server nova_osapi/np0000068128.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 9 08:28:42 np0000068130 haproxy[7]: Server cinder/np0000068130.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 9 08:28:42 np0000068130 haproxy[7]: Server heat_api/np0000068130.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 9 08:28:42 np0000068130 haproxy[7]: Server heat_cfn/np0000068130.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 9 08:28:42 np0000068130 haproxy[7]: Server cinder/np0000068129.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 9 08:28:42 np0000068130 haproxy[7]: Server aodh/np0000068130.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 9 08:28:42 np0000068130 haproxy[7]: Server heat_cfn/np0000068129.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 1ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:43 np0000068130 haproxy[7]: Server heat_api/np0000068129.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 7ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:43 np0000068130 haproxy[7]: Server aodh/np0000068129.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 9 08:28:45 np0000068130 haproxy[7]: Server manila/np0000068129.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 9 08:28:45 np0000068130 haproxy[7]: Server manila/np0000068130.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 1087ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:46 np0000068130 haproxy[7]: Server nova_novncproxy/np0000068130.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 9 08:28:48 np0000068130 haproxy[7]: Server nova_novncproxy/np0000068129.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 9 08:28:48 np0000068130 haproxy[7]: Server placement/np0000068130.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 9 08:28:48 np0000068130 haproxy[7]: Server placement/np0000068129.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 0ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:50 np0000068130 haproxy[7]: Server neutron/np0000068130.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 9 08:28:51 np0000068130 haproxy[7]: Server swift_proxy_server/np0000068130.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 9 08:28:51 np0000068130 haproxy[7]: Server nova_metadata/np0000068130.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 9 08:28:51 np0000068130 haproxy[7]: Server swift_proxy_server/np0000068129.storage.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 2ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:51 np0000068130 haproxy[7]: Server glance_api/np0000068130.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 9 08:28:51 np0000068130 haproxy[7]: Server glance_api_internal/np0000068130.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 9 08:28:51 np0000068130 haproxy[7]: Server glance_api_internal/np0000068129.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 9 08:28:51 np0000068130 haproxy[7]: Server nova_osapi/np0000068130.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 9 08:28:51 np0000068130 haproxy[7]: Server nova_metadata/np0000068129.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 9 08:28:52 np0000068130 haproxy[7]: Server nova_osapi/np0000068129.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 6ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. Jun 9 08:28:52 np0000068130 haproxy[7]: Server neutron/np0000068129.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 9 08:28:53 np0000068130 haproxy[7]: Server glance_api/np0000068129.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 9 08:32:35 np0000068130 haproxy[7]: 192.168.122.110:56244 [09/Jun/2026:08:32:35.456] redis redis/np0000068128.internalapi.localdomain 1/0/15 10 -- 32/32/31/31/0 0/0 Jun 9 08:32:35 np0000068130 haproxy[7]: 192.168.122.110:56196 [09/Jun/2026:08:32:35.197] redis redis/np0000068128.internalapi.localdomain 1/0/275 4428 -- 32/32/30/30/0 0/0 Jun 9 08:32:35 np0000068130 haproxy[7]: 192.168.122.110:56264 [09/Jun/2026:08:32:35.736] redis redis/np0000068128.internalapi.localdomain 1/0/18 10 -- 32/32/31/31/0 0/0 Jun 9 08:32:35 np0000068130 haproxy[7]: 192.168.122.110:56258 [09/Jun/2026:08:32:35.501] redis redis/np0000068128.internalapi.localdomain 1/0/253 4428 -- 32/32/30/30/0 0/0 Jun 9 08:32:38 np0000068130 haproxy[7]: Server gnocchi/np0000068130.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 9 08:32:40 np0000068130 haproxy[7]: 192.168.122.104:47302 [09/Jun/2026:08:32:40.306] redis redis/np0000068128.internalapi.localdomain 1/1/18 10 -- 36/36/35/35/0 0/0 Jun 9 08:32:40 np0000068130 haproxy[7]: 192.168.122.104:47280 [09/Jun/2026:08:32:40.012] redis redis/np0000068128.internalapi.localdomain 1/0/313 4428 -- 35/35/34/34/0 0/0 Jun 9 08:32:40 np0000068130 haproxy[7]: 192.168.122.104:47328 [09/Jun/2026:08:32:40.652] redis redis/np0000068128.internalapi.localdomain 1/0/14 10 -- 37/37/36/36/0 0/0 Jun 9 08:32:40 np0000068130 haproxy[7]: 192.168.122.104:47318 [09/Jun/2026:08:32:40.372] redis redis/np0000068128.internalapi.localdomain 1/0/294 4429 -- 37/37/35/35/0 0/0 Jun 9 08:32:41 np0000068130 haproxy[7]: 192.168.122.110:38360 [09/Jun/2026:08:32:41.056] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 37/37/36/36/0 0/0 Jun 9 08:32:41 np0000068130 haproxy[7]: 192.168.122.110:38354 [09/Jun/2026:08:32:40.785] redis redis/np0000068128.internalapi.localdomain 1/0/283 4429 -- 36/36/35/35/0 0/0 Jun 9 08:32:41 np0000068130 haproxy[7]: 192.168.122.110:38382 [09/Jun/2026:08:32:41.351] redis redis/np0000068128.internalapi.localdomain 1/1/13 10 -- 37/37/35/35/0 0/0 Jun 9 08:32:41 np0000068130 haproxy[7]: 192.168.122.110:38374 [09/Jun/2026:08:32:41.084] redis redis/np0000068128.internalapi.localdomain 1/0/280 4429 -- 37/37/35/35/0 0/0 Jun 9 08:32:41 np0000068130 haproxy[7]: 192.168.122.110:38402 [09/Jun/2026:08:32:41.642] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0 Jun 9 08:32:41 np0000068130 haproxy[7]: 192.168.122.110:38396 [09/Jun/2026:08:32:41.395] redis redis/np0000068128.internalapi.localdomain 1/0/258 4429 -- 38/38/37/37/0 0/0 Jun 9 08:32:41 np0000068130 haproxy[7]: 192.168.122.110:38416 [09/Jun/2026:08:32:41.925] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:41 np0000068130 haproxy[7]: 192.168.122.110:38408 [09/Jun/2026:08:32:41.683] redis redis/np0000068128.internalapi.localdomain 1/0/253 4429 -- 40/40/38/38/0 0/0 Jun 9 08:32:43 np0000068130 haproxy[7]: Server gnocchi/np0000068129.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 9 08:32:45 np0000068130 haproxy[7]: 192.168.122.104:60640 [09/Jun/2026:08:32:45.984] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:45 np0000068130 haproxy[7]: 192.168.122.104:60630 [09/Jun/2026:08:32:45.711] redis redis/np0000068128.internalapi.localdomain 1/1/285 4428 -- 40/40/38/38/0 0/0 Jun 9 08:32:46 np0000068130 haproxy[7]: 192.168.122.104:60644 [09/Jun/2026:08:32:46.336] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:46 np0000068130 haproxy[7]: 192.168.122.104:60642 [09/Jun/2026:08:32:46.020] redis redis/np0000068128.internalapi.localdomain 1/0/330 4428 -- 39/39/38/38/0 0/0 Jun 9 08:32:46 np0000068130 haproxy[7]: 192.168.122.104:60656 [09/Jun/2026:08:32:46.652] redis redis/np0000068128.internalapi.localdomain 1/1/13 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:46 np0000068130 haproxy[7]: 192.168.122.104:60648 [09/Jun/2026:08:32:46.382] redis redis/np0000068128.internalapi.localdomain 1/0/283 4427 -- 39/39/38/38/0 0/0 Jun 9 08:32:47 np0000068130 haproxy[7]: 192.168.122.104:60668 [09/Jun/2026:08:32:47.013] redis redis/np0000068128.internalapi.localdomain 1/0/9 10 -- 41/41/40/40/0 0/0 Jun 9 08:32:47 np0000068130 haproxy[7]: 192.168.122.104:60660 [09/Jun/2026:08:32:46.698] redis redis/np0000068128.internalapi.localdomain 1/0/324 4429 -- 41/41/39/39/0 0/0 Jun 9 08:32:47 np0000068130 haproxy[7]: 192.168.122.110:38438 [09/Jun/2026:08:32:47.212] redis redis/np0000068128.internalapi.localdomain 1/0/8 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:47 np0000068130 haproxy[7]: 192.168.122.110:38426 [09/Jun/2026:08:32:46.968] redis redis/np0000068128.internalapi.localdomain 1/0/252 4429 -- 40/40/38/38/0 0/0 Jun 9 08:32:47 np0000068130 haproxy[7]: 192.168.122.110:38446 [09/Jun/2026:08:32:47.494] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:47 np0000068130 haproxy[7]: 192.168.122.110:38440 [09/Jun/2026:08:32:47.247] redis redis/np0000068128.internalapi.localdomain 1/0/258 4429 -- 40/40/38/38/0 0/0 Jun 9 08:32:47 np0000068130 haproxy[7]: 192.168.122.110:46322 [09/Jun/2026:08:32:47.810] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:47 np0000068130 haproxy[7]: 192.168.122.110:38452 [09/Jun/2026:08:32:47.535] redis redis/np0000068128.internalapi.localdomain 1/3/286 4429 -- 39/39/38/38/0 0/0 Jun 9 08:32:48 np0000068130 haproxy[7]: 192.168.122.110:46328 [09/Jun/2026:08:32:48.061] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:48 np0000068130 haproxy[7]: 192.168.122.110:46324 [09/Jun/2026:08:32:47.837] redis redis/np0000068128.internalapi.localdomain 1/0/239 4429 -- 39/39/38/38/0 0/0 Jun 9 08:32:52 np0000068130 haproxy[7]: 192.168.122.104:60684 [09/Jun/2026:08:32:52.314] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:52 np0000068130 haproxy[7]: 192.168.122.104:60670 [09/Jun/2026:08:32:52.063] redis redis/np0000068128.internalapi.localdomain 1/0/265 4428 -- 39/39/38/38/0 0/0 Jun 9 08:32:52 np0000068130 haproxy[7]: 192.168.122.104:60708 [09/Jun/2026:08:32:52.614] redis redis/np0000068128.internalapi.localdomain 1/0/17 10 -- 40/40/38/38/0 0/0 Jun 9 08:32:52 np0000068130 haproxy[7]: 192.168.122.104:60696 [09/Jun/2026:08:32:52.361] redis redis/np0000068128.internalapi.localdomain 1/0/271 4428 -- 40/40/38/38/0 0/0 Jun 9 08:32:52 np0000068130 haproxy[7]: 192.168.122.104:60714 [09/Jun/2026:08:32:52.662] redis redis/np0000068128.internalapi.localdomain 1/0/294 4429 -- 40/40/39/39/0 0/0 Jun 9 08:32:52 np0000068130 haproxy[7]: 192.168.122.104:60718 [09/Jun/2026:08:32:52.946] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0 Jun 9 08:32:53 np0000068130 haproxy[7]: 192.168.122.104:60746 [09/Jun/2026:08:32:53.260] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0 Jun 9 08:32:53 np0000068130 haproxy[7]: 192.168.122.104:60730 [09/Jun/2026:08:32:52.986] redis redis/np0000068128.internalapi.localdomain 1/0/287 4429 -- 40/40/39/39/0 0/0 Jun 9 08:32:53 np0000068130 haproxy[7]: 192.168.122.110:46340 [09/Jun/2026:08:32:53.362] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:53 np0000068130 haproxy[7]: 192.168.122.110:46338 [09/Jun/2026:08:32:53.112] redis redis/np0000068128.internalapi.localdomain 1/1/261 4429 -- 40/40/38/38/0 0/0 Jun 9 08:32:53 np0000068130 haproxy[7]: 192.168.122.110:46370 [09/Jun/2026:08:32:53.650] redis redis/np0000068128.internalapi.localdomain 1/0/8 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:53 np0000068130 haproxy[7]: 192.168.122.110:46356 [09/Jun/2026:08:32:53.395] redis redis/np0000068128.internalapi.localdomain 1/0/264 4429 -- 39/39/38/38/0 0/0 Jun 9 08:32:53 np0000068130 haproxy[7]: 192.168.122.110:46394 [09/Jun/2026:08:32:53.914] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:53 np0000068130 haproxy[7]: 192.168.122.110:46386 [09/Jun/2026:08:32:53.679] redis redis/np0000068128.internalapi.localdomain 1/0/245 4429 -- 40/40/38/38/0 0/0 Jun 9 08:32:54 np0000068130 haproxy[7]: 192.168.122.110:46412 [09/Jun/2026:08:32:54.187] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:54 np0000068130 haproxy[7]: 192.168.122.110:46404 [09/Jun/2026:08:32:53.950] redis redis/np0000068128.internalapi.localdomain 1/0/248 4429 -- 40/40/38/38/0 0/0 Jun 9 08:32:58 np0000068130 haproxy[7]: 192.168.122.104:39754 [09/Jun/2026:08:32:58.572] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:58 np0000068130 haproxy[7]: 192.168.122.104:39746 [09/Jun/2026:08:32:58.311] redis redis/np0000068128.internalapi.localdomain 1/0/274 4428 -- 39/39/38/38/0 0/0 Jun 9 08:32:58 np0000068130 haproxy[7]: 192.168.122.104:39778 [09/Jun/2026:08:32:58.902] redis redis/np0000068128.internalapi.localdomain 1/0/15 10 -- 40/40/39/39/0 0/0 Jun 9 08:32:58 np0000068130 haproxy[7]: 192.168.122.104:39768 [09/Jun/2026:08:32:58.617] redis redis/np0000068128.internalapi.localdomain 1/1/300 4428 -- 39/39/38/38/0 0/0 Jun 9 08:32:59 np0000068130 haproxy[7]: 192.168.122.104:39802 [09/Jun/2026:08:32:59.221] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0 Jun 9 08:32:59 np0000068130 haproxy[7]: 192.168.122.104:39788 [09/Jun/2026:08:32:58.950] redis redis/np0000068128.internalapi.localdomain 1/1/286 4429 -- 40/40/39/39/0 0/0 Jun 9 08:32:59 np0000068130 haproxy[7]: 192.168.122.110:56972 [09/Jun/2026:08:32:59.492] redis redis/np0000068128.internalapi.localdomain 1/0/14 10 -- 41/41/40/40/0 0/0 Jun 9 08:32:59 np0000068130 haproxy[7]: 192.168.122.110:56966 [09/Jun/2026:08:32:59.225] redis redis/np0000068128.internalapi.localdomain 1/0/281 4429 -- 41/41/39/39/0 0/0 Jun 9 08:32:59 np0000068130 haproxy[7]: 192.168.122.104:39822 [09/Jun/2026:08:32:59.548] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0 Jun 9 08:32:59 np0000068130 haproxy[7]: 192.168.122.104:39814 [09/Jun/2026:08:32:59.273] redis redis/np0000068128.internalapi.localdomain 1/0/286 4429 -- 40/40/39/39/0 0/0 Jun 9 08:32:59 np0000068130 haproxy[7]: 192.168.122.110:56986 [09/Jun/2026:08:32:59.533] redis redis/np0000068128.internalapi.localdomain 1/2/301 4429 -- 40/40/39/39/0 0/0 Jun 9 08:32:59 np0000068130 haproxy[7]: 192.168.122.110:56990 [09/Jun/2026:08:32:59.826] redis redis/np0000068128.internalapi.localdomain 1/0/8 10 -- 40/40/38/38/0 0/0 Jun 9 08:33:00 np0000068130 haproxy[7]: 192.168.122.110:57008 [09/Jun/2026:08:33:00.077] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:00 np0000068130 haproxy[7]: 192.168.122.110:56996 [09/Jun/2026:08:32:59.854] redis redis/np0000068128.internalapi.localdomain 1/0/236 4429 -- 39/39/38/38/0 0/0 Jun 9 08:33:00 np0000068130 haproxy[7]: 192.168.122.110:57026 [09/Jun/2026:08:33:00.374] redis redis/np0000068128.internalapi.localdomain 1/0/9 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:00 np0000068130 haproxy[7]: 192.168.122.110:57012 [09/Jun/2026:08:33:00.116] redis redis/np0000068128.internalapi.localdomain 1/0/268 4429 -- 39/39/38/38/0 0/0 Jun 9 08:33:04 np0000068130 haproxy[7]: 192.168.122.104:39126 [09/Jun/2026:08:33:04.598] redis redis/np0000068128.internalapi.localdomain 1/0/284 4428 -- 40/40/39/39/0 0/0 Jun 9 08:33:04 np0000068130 haproxy[7]: 192.168.122.104:39138 [09/Jun/2026:08:33:04.873] redis redis/np0000068128.internalapi.localdomain 1/0/9 10 -- 40/40/38/38/0 0/0 Jun 9 08:33:05 np0000068130 haproxy[7]: 192.168.122.104:39168 [09/Jun/2026:08:33:05.164] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:05 np0000068130 haproxy[7]: 192.168.122.104:39154 [09/Jun/2026:08:33:04.908] redis redis/np0000068128.internalapi.localdomain 1/0/271 4428 -- 39/39/38/38/0 0/0 Jun 9 08:33:05 np0000068130 haproxy[7]: 192.168.122.104:39176 [09/Jun/2026:08:33:05.472] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:05 np0000068130 haproxy[7]: 192.168.122.104:39172 [09/Jun/2026:08:33:05.210] redis redis/np0000068128.internalapi.localdomain 1/0/276 4428 -- 41/41/39/39/0 0/0 Jun 9 08:33:05 np0000068130 haproxy[7]: 192.168.122.110:57034 [09/Jun/2026:08:33:05.627] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:05 np0000068130 haproxy[7]: 192.168.122.110:57032 [09/Jun/2026:08:33:05.408] redis redis/np0000068128.internalapi.localdomain 1/0/229 4429 -- 41/41/39/39/0 0/0 Jun 9 08:33:05 np0000068130 haproxy[7]: 192.168.122.104:39196 [09/Jun/2026:08:33:05.782] redis redis/np0000068128.internalapi.localdomain 1/0/14 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:05 np0000068130 haproxy[7]: 192.168.122.104:39192 [09/Jun/2026:08:33:05.517] redis redis/np0000068128.internalapi.localdomain 1/0/279 4429 -- 41/41/39/39/0 0/0 Jun 9 08:33:05 np0000068130 haproxy[7]: 192.168.122.110:57040 [09/Jun/2026:08:33:05.667] redis redis/np0000068128.internalapi.localdomain 1/1/280 4429 -- 40/40/39/39/0 0/0 Jun 9 08:33:05 np0000068130 haproxy[7]: 192.168.122.110:57054 [09/Jun/2026:08:33:05.934] redis redis/np0000068128.internalapi.localdomain 1/0/16 10 -- 39/39/38/38/0 0/0 Jun 9 08:33:06 np0000068130 haproxy[7]: 192.168.122.110:57080 [09/Jun/2026:08:33:06.190] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:06 np0000068130 haproxy[7]: 192.168.122.110:57066 [09/Jun/2026:08:33:05.969] redis redis/np0000068128.internalapi.localdomain 1/0/236 4429 -- 39/39/38/38/0 0/0 Jun 9 08:33:06 np0000068130 haproxy[7]: 192.168.122.110:57108 [09/Jun/2026:08:33:06.516] redis redis/np0000068128.internalapi.localdomain 1/0/9 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:06 np0000068130 haproxy[7]: 192.168.122.110:57092 [09/Jun/2026:08:33:06.222] redis redis/np0000068128.internalapi.localdomain 1/0/303 4428 -- 39/39/38/38/0 0/0 Jun 9 08:33:11 np0000068130 haproxy[7]: 192.168.122.104:39210 [09/Jun/2026:08:33:11.110] redis redis/np0000068128.internalapi.localdomain 1/0/65 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:11 np0000068130 haproxy[7]: 192.168.122.104:39198 [09/Jun/2026:08:33:10.839] redis redis/np0000068128.internalapi.localdomain 1/0/338 4428 -- 40/40/38/38/0 0/0 Jun 9 08:33:11 np0000068130 haproxy[7]: 192.168.122.104:39212 [09/Jun/2026:08:33:11.206] redis redis/np0000068128.internalapi.localdomain 1/0/286 4428 -- 40/40/39/39/0 0/0 Jun 9 08:33:11 np0000068130 haproxy[7]: 192.168.122.104:39216 [09/Jun/2026:08:33:11.478] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 39/39/38/38/0 0/0 Jun 9 08:33:11 np0000068130 haproxy[7]: 192.168.122.104:39232 [09/Jun/2026:08:33:11.765] redis redis/np0000068128.internalapi.localdomain 1/0/16 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:11 np0000068130 haproxy[7]: 192.168.122.104:39226 [09/Jun/2026:08:33:11.514] redis redis/np0000068128.internalapi.localdomain 1/0/267 4428 -- 41/41/39/39/0 0/0 Jun 9 08:33:11 np0000068130 haproxy[7]: 192.168.122.110:50690 [09/Jun/2026:08:33:11.561] redis redis/np0000068128.internalapi.localdomain 1/0/247 4430 -- 41/41/39/39/0 0/0 Jun 9 08:33:11 np0000068130 haproxy[7]: 192.168.122.110:50702 [09/Jun/2026:08:33:11.795] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 41/41/39/39/0 0/0 Jun 9 08:33:12 np0000068130 haproxy[7]: 192.168.122.104:39246 [09/Jun/2026:08:33:12.036] redis redis/np0000068128.internalapi.localdomain 1/0/17 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:12 np0000068130 haproxy[7]: 192.168.122.104:39236 [09/Jun/2026:08:33:11.802] redis redis/np0000068128.internalapi.localdomain 1/0/252 4430 -- 41/41/39/39/0 0/0 Jun 9 08:33:12 np0000068130 haproxy[7]: 192.168.122.110:50726 [09/Jun/2026:08:33:12.092] redis redis/np0000068128.internalapi.localdomain 1/0/8 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:12 np0000068130 haproxy[7]: 192.168.122.110:50714 [09/Jun/2026:08:33:11.836] redis redis/np0000068128.internalapi.localdomain 1/0/265 4430 -- 39/39/38/38/0 0/0 Jun 9 08:33:12 np0000068130 haproxy[7]: 192.168.122.110:50738 [09/Jun/2026:08:33:12.357] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:12 np0000068130 haproxy[7]: 192.168.122.110:50736 [09/Jun/2026:08:33:12.118] redis redis/np0000068128.internalapi.localdomain 1/0/250 4430 -- 39/39/38/38/0 0/0 Jun 9 08:33:12 np0000068130 haproxy[7]: 192.168.122.110:50760 [09/Jun/2026:08:33:12.648] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:12 np0000068130 haproxy[7]: 192.168.122.110:50746 [09/Jun/2026:08:33:12.394] redis redis/np0000068128.internalapi.localdomain 1/0/264 4430 -- 39/39/38/38/0 0/0 Jun 9 08:33:17 np0000068130 haproxy[7]: 192.168.122.104:50198 [09/Jun/2026:08:33:17.324] redis redis/np0000068128.internalapi.localdomain 1/1/15 10 -- 40/40/38/38/0 0/0 Jun 9 08:33:17 np0000068130 haproxy[7]: 192.168.122.104:50188 [09/Jun/2026:08:33:17.083] redis redis/np0000068128.internalapi.localdomain 1/0/256 4430 -- 40/40/38/38/0 0/0 Jun 9 08:33:17 np0000068130 haproxy[7]: 192.168.122.104:50204 [09/Jun/2026:08:33:17.370] redis redis/np0000068128.internalapi.localdomain 1/0/258 4430 -- 40/40/39/39/0 0/0 Jun 9 08:33:17 np0000068130 haproxy[7]: 192.168.122.104:50216 [09/Jun/2026:08:33:17.617] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 40/40/38/38/0 0/0 Jun 9 08:33:17 np0000068130 haproxy[7]: 192.168.122.104:50220 [09/Jun/2026:08:33:17.934] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 42/42/41/41/0 0/0 Jun 9 08:33:17 np0000068130 haproxy[7]: 192.168.122.104:50218 [09/Jun/2026:08:33:17.661] redis redis/np0000068128.internalapi.localdomain 1/0/282 4430 -- 42/42/40/40/0 0/0 Jun 9 08:33:17 np0000068130 haproxy[7]: 192.168.122.110:56430 [09/Jun/2026:08:33:17.693] redis redis/np0000068128.internalapi.localdomain 1/0/259 4430 -- 40/40/39/39/0 0/0 Jun 9 08:33:17 np0000068130 haproxy[7]: 192.168.122.110:56440 [09/Jun/2026:08:33:17.941] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 40/40/38/38/0 0/0 Jun 9 08:33:18 np0000068130 haproxy[7]: 192.168.122.110:56452 [09/Jun/2026:08:33:17.973] redis redis/np0000068128.internalapi.localdomain 1/0/270 4431 -- 41/41/40/40/0 0/0 Jun 9 08:33:18 np0000068130 haproxy[7]: 192.168.122.110:56462 [09/Jun/2026:08:33:18.229] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:18 np0000068130 haproxy[7]: 192.168.122.104:50226 [09/Jun/2026:08:33:18.275] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:18 np0000068130 haproxy[7]: 192.168.122.104:50222 [09/Jun/2026:08:33:17.967] redis redis/np0000068128.internalapi.localdomain 1/0/323 4431 -- 41/41/39/39/0 0/0 Jun 9 08:33:18 np0000068130 haproxy[7]: 192.168.122.110:56488 [09/Jun/2026:08:33:18.512] redis redis/np0000068128.internalapi.localdomain 1/0/8 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:18 np0000068130 haproxy[7]: 192.168.122.110:56474 [09/Jun/2026:08:33:18.262] redis redis/np0000068128.internalapi.localdomain 1/0/259 4428 -- 39/39/38/38/0 0/0 Jun 9 08:33:18 np0000068130 haproxy[7]: 192.168.122.110:56504 [09/Jun/2026:08:33:18.538] redis redis/np0000068128.internalapi.localdomain 1/0/258 4428 -- 40/40/38/38/0 0/0 Jun 9 08:33:18 np0000068130 haproxy[7]: 192.168.122.110:56520 [09/Jun/2026:08:33:18.789] redis redis/np0000068128.internalapi.localdomain 1/0/7 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:23 np0000068130 haproxy[7]: 192.168.122.104:34120 [09/Jun/2026:08:33:23.583] redis redis/np0000068128.internalapi.localdomain 1/0/16 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:23 np0000068130 haproxy[7]: 192.168.122.104:50232 [09/Jun/2026:08:33:23.321] redis redis/np0000068128.internalapi.localdomain 1/0/278 4428 -- 40/40/38/38/0 0/0 Jun 9 08:33:23 np0000068130 haproxy[7]: 192.168.122.104:34134 [09/Jun/2026:08:33:23.860] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:23 np0000068130 haproxy[7]: 192.168.122.104:34124 [09/Jun/2026:08:33:23.624] redis redis/np0000068128.internalapi.localdomain 1/1/247 4428 -- 41/41/39/39/0 0/0 Jun 9 08:33:24 np0000068130 haproxy[7]: 192.168.122.110:56546 [09/Jun/2026:08:33:24.074] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:24 np0000068130 haproxy[7]: 192.168.122.110:56536 [09/Jun/2026:08:33:23.829] redis redis/np0000068128.internalapi.localdomain 1/0/258 4429 -- 41/41/39/39/0 0/0 Jun 9 08:33:24 np0000068130 haproxy[7]: 192.168.122.104:34152 [09/Jun/2026:08:33:24.117] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:24 np0000068130 haproxy[7]: 192.168.122.104:34138 [09/Jun/2026:08:33:23.895] redis redis/np0000068128.internalapi.localdomain 1/0/236 4429 -- 41/41/39/39/0 0/0 Jun 9 08:33:24 np0000068130 haproxy[7]: 192.168.122.110:56562 [09/Jun/2026:08:33:24.124] redis redis/np0000068128.internalapi.localdomain 1/0/276 4429 -- 41/41/40/40/0 0/0 Jun 9 08:33:24 np0000068130 haproxy[7]: 192.168.122.110:56578 [09/Jun/2026:08:33:24.389] redis redis/np0000068128.internalapi.localdomain 1/1/12 10 -- 41/41/39/39/0 0/0 Jun 9 08:33:24 np0000068130 haproxy[7]: 192.168.122.104:34156 [09/Jun/2026:08:33:24.159] redis redis/np0000068128.internalapi.localdomain 1/0/258 4429 -- 40/40/39/39/0 0/0 Jun 9 08:33:24 np0000068130 haproxy[7]: 192.168.122.104:34168 [09/Jun/2026:08:33:24.407] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0 Jun 9 08:33:24 np0000068130 haproxy[7]: 192.168.122.110:56582 [09/Jun/2026:08:33:24.688] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:24 np0000068130 haproxy[7]: 192.168.122.110:56580 [09/Jun/2026:08:33:24.429] redis redis/np0000068128.internalapi.localdomain 1/0/272 4430 -- 40/40/38/38/0 0/0 Jun 9 08:33:25 np0000068130 haproxy[7]: 192.168.122.110:56598 [09/Jun/2026:08:33:24.990] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:25 np0000068130 haproxy[7]: 192.168.122.110:56584 [09/Jun/2026:08:33:24.730] redis redis/np0000068128.internalapi.localdomain 1/0/270 4430 -- 39/39/38/38/0 0/0 Jun 9 08:33:29 np0000068130 haproxy[7]: 192.168.122.104:34170 [09/Jun/2026:08:33:29.456] redis redis/np0000068128.internalapi.localdomain 1/0/268 4427 -- 40/40/39/39/0 0/0 Jun 9 08:33:29 np0000068130 haproxy[7]: 192.168.122.104:34182 [09/Jun/2026:08:33:29.712] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 40/40/38/38/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.104:34206 [09/Jun/2026:08:33:30.020] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.104:34190 [09/Jun/2026:08:33:29.763] redis redis/np0000068128.internalapi.localdomain 1/0/270 4429 -- 40/40/39/39/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.110:34784 [09/Jun/2026:08:33:30.029] redis redis/np0000068128.internalapi.localdomain 1/0/261 4430 -- 41/41/39/39/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.110:34796 [09/Jun/2026:08:33:30.278] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.104:34216 [09/Jun/2026:08:33:30.318] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.104:34214 [09/Jun/2026:08:33:30.067] redis redis/np0000068128.internalapi.localdomain 1/0/263 4430 -- 41/41/39/39/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.110:34802 [09/Jun/2026:08:33:30.585] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.110:34798 [09/Jun/2026:08:33:30.315] redis redis/np0000068128.internalapi.localdomain 1/0/282 4430 -- 40/40/39/39/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.104:34224 [09/Jun/2026:08:33:30.364] redis redis/np0000068128.internalapi.localdomain 1/0/294 4430 -- 41/41/39/39/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.104:34234 [09/Jun/2026:08:33:30.646] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.110:34808 [09/Jun/2026:08:33:30.631] redis redis/np0000068128.internalapi.localdomain 1/0/281 4430 -- 40/40/39/39/0 0/0 Jun 9 08:33:30 np0000068130 haproxy[7]: 192.168.122.110:34818 [09/Jun/2026:08:33:30.901] redis redis/np0000068128.internalapi.localdomain 1/0/14 10 -- 39/39/38/38/0 0/0 Jun 9 08:33:31 np0000068130 haproxy[7]: 192.168.122.110:34838 [09/Jun/2026:08:33:31.177] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 40/40/39/39/0 0/0 Jun 9 08:33:31 np0000068130 haproxy[7]: 192.168.122.110:34826 [09/Jun/2026:08:33:30.946] redis redis/np0000068128.internalapi.localdomain 1/0/242 4430 -- 39/39/38/38/0 0/0 Jun 9 08:33:36 np0000068130 haproxy[7]: 192.168.122.104:52850 [09/Jun/2026:08:33:36.006] redis redis/np0000068128.internalapi.localdomain 1/517/536 10 -- 41/41/40/40/0 0/0 Jun 9 08:33:36 np0000068130 haproxy[7]: 192.168.122.104:52834 [09/Jun/2026:08:33:35.696] redis redis/np0000068128.internalapi.localdomain 1/1/847 4429 -- 40/40/39/39/0 0/0 Jun 9 08:33:38 np0000068130 haproxy[7]: 192.168.122.110:34854 [09/Jun/2026:08:33:36.210] redis redis/np0000068128.internalapi.localdomain 1/314/2490 4429 -- 44/44/42/42/0 0/0 Jun 9 08:33:38 np0000068130 haproxy[7]: 192.168.122.110:34864 [09/Jun/2026:08:33:36.825] redis redis/np0000068128.internalapi.localdomain 1/1841/1877 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:38 np0000068130 haproxy[7]: 192.168.122.104:52862 [09/Jun/2026:08:33:38.934] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:38 np0000068130 haproxy[7]: 192.168.122.104:52856 [09/Jun/2026:08:33:36.566] redis redis/np0000068128.internalapi.localdomain 1/541/2380 4429 -- 43/43/42/42/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.110:40526 [09/Jun/2026:08:33:39.014] redis redis/np0000068128.internalapi.localdomain 1/0/8 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.110:40510 [09/Jun/2026:08:33:38.738] redis redis/np0000068128.internalapi.localdomain 1/0/287 4429 -- 43/43/42/42/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.104:52878 [09/Jun/2026:08:33:39.226] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.104:52876 [09/Jun/2026:08:33:38.972] redis redis/np0000068128.internalapi.localdomain 1/7/265 4430 -- 44/44/42/42/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.110:40542 [09/Jun/2026:08:33:39.041] redis redis/np0000068128.internalapi.localdomain 1/0/242 4430 -- 44/44/42/42/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.110:40550 [09/Jun/2026:08:33:39.274] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 44/44/42/42/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.104:52900 [09/Jun/2026:08:33:39.509] redis redis/np0000068128.internalapi.localdomain 1/0/14 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.104:52894 [09/Jun/2026:08:33:39.261] redis redis/np0000068128.internalapi.localdomain 1/0/262 4431 -- 43/43/42/42/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.110:40572 [09/Jun/2026:08:33:39.573] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.110:40558 [09/Jun/2026:08:33:39.302] redis redis/np0000068128.internalapi.localdomain 1/0/284 4431 -- 43/43/42/42/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.104:52902 [09/Jun/2026:08:33:39.557] redis redis/np0000068128.internalapi.localdomain 1/2/289 4431 -- 44/44/43/43/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.104:52908 [09/Jun/2026:08:33:39.835] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 44/44/42/42/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.110:40594 [09/Jun/2026:08:33:39.888] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:39 np0000068130 haproxy[7]: 192.168.122.110:40588 [09/Jun/2026:08:33:39.627] redis redis/np0000068128.internalapi.localdomain 1/0/271 4431 -- 43/43/42/42/0 0/0 Jun 9 08:33:40 np0000068130 haproxy[7]: 192.168.122.104:52928 [09/Jun/2026:08:33:40.158] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 43/43/42/42/0 0/0 Jun 9 08:33:40 np0000068130 haproxy[7]: 192.168.122.104:52912 [09/Jun/2026:08:33:39.871] redis redis/np0000068128.internalapi.localdomain 1/0/301 4432 -- 43/43/41/41/0 0/0 Jun 9 08:33:45 np0000068130 haproxy[7]: 192.168.122.110:40606 [09/Jun/2026:08:33:44.934] redis redis/np0000068128.internalapi.localdomain 1/0/285 4431 -- 44/44/42/42/0 0/0 Jun 9 08:33:45 np0000068130 haproxy[7]: 192.168.122.110:40608 [09/Jun/2026:08:33:45.211] redis redis/np0000068128.internalapi.localdomain 1/0/7 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:45 np0000068130 haproxy[7]: 192.168.122.104:47688 [09/Jun/2026:08:33:45.210] redis redis/np0000068128.internalapi.localdomain 1/0/306 4431 -- 45/45/44/44/0 0/0 Jun 9 08:33:45 np0000068130 haproxy[7]: 192.168.122.104:47700 [09/Jun/2026:08:33:45.469] redis redis/np0000068128.internalapi.localdomain 1/0/47 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:45 np0000068130 haproxy[7]: 192.168.122.110:40616 [09/Jun/2026:08:33:45.247] redis redis/np0000068128.internalapi.localdomain 1/1/272 4431 -- 43/43/42/42/0 0/0 Jun 9 08:33:45 np0000068130 haproxy[7]: 192.168.122.110:40632 [09/Jun/2026:08:33:45.496] redis redis/np0000068128.internalapi.localdomain 1/0/23 10 -- 43/43/41/41/0 0/0 Jun 9 08:33:45 np0000068130 haproxy[7]: 192.168.122.110:40654 [09/Jun/2026:08:33:45.791] redis redis/np0000068128.internalapi.localdomain 1/0/7 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:45 np0000068130 haproxy[7]: 192.168.122.110:40638 [09/Jun/2026:08:33:45.538] redis redis/np0000068128.internalapi.localdomain 1/0/261 4432 -- 44/44/42/42/0 0/0 Jun 9 08:33:45 np0000068130 haproxy[7]: 192.168.122.104:47710 [09/Jun/2026:08:33:45.842] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:45 np0000068130 haproxy[7]: 192.168.122.104:47708 [09/Jun/2026:08:33:45.548] redis redis/np0000068128.internalapi.localdomain 1/1/306 4433 -- 44/44/42/42/0 0/0 Jun 9 08:33:46 np0000068130 haproxy[7]: 192.168.122.110:40656 [09/Jun/2026:08:33:45.826] redis redis/np0000068128.internalapi.localdomain 1/0/247 4433 -- 44/44/43/43/0 0/0 Jun 9 08:33:46 np0000068130 haproxy[7]: 192.168.122.110:40664 [09/Jun/2026:08:33:46.065] redis redis/np0000068128.internalapi.localdomain 1/0/7 10 -- 43/43/42/42/0 0/0 Jun 9 08:33:46 np0000068130 haproxy[7]: 192.168.122.104:47718 [09/Jun/2026:08:33:46.132] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0 Jun 9 08:33:46 np0000068130 haproxy[7]: 192.168.122.104:47712 [09/Jun/2026:08:33:45.878] redis redis/np0000068128.internalapi.localdomain 1/0/266 4433 -- 43/43/41/41/0 0/0 Jun 9 08:33:46 np0000068130 haproxy[7]: 192.168.122.104:47738 [09/Jun/2026:08:33:46.432] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0 Jun 9 08:33:46 np0000068130 haproxy[7]: 192.168.122.104:47724 [09/Jun/2026:08:33:46.170] redis redis/np0000068128.internalapi.localdomain 1/0/274 4433 -- 42/42/41/41/0 0/0 Jun 9 08:33:51 np0000068130 haproxy[7]: 192.168.122.110:60264 [09/Jun/2026:08:33:51.410] redis redis/np0000068128.internalapi.localdomain 1/0/16 10 -- 43/43/42/42/0 0/0 Jun 9 08:33:51 np0000068130 haproxy[7]: 192.168.122.110:60262 [09/Jun/2026:08:33:51.110] redis redis/np0000068128.internalapi.localdomain 1/0/315 4432 -- 43/43/41/41/0 0/0 Jun 9 08:33:51 np0000068130 haproxy[7]: 192.168.122.104:47752 [09/Jun/2026:08:33:51.726] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:51 np0000068130 haproxy[7]: 192.168.122.104:47746 [09/Jun/2026:08:33:51.471] redis redis/np0000068128.internalapi.localdomain 1/0/266 4432 -- 43/43/42/42/0 0/0 Jun 9 08:33:51 np0000068130 haproxy[7]: 192.168.122.110:60284 [09/Jun/2026:08:33:51.741] redis redis/np0000068128.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0 Jun 9 08:33:51 np0000068130 haproxy[7]: 192.168.122.110:60276 [09/Jun/2026:08:33:51.456] redis redis/np0000068128.internalapi.localdomain 1/0/295 4431 -- 42/42/41/41/0 0/0 Jun 9 08:33:52 np0000068130 haproxy[7]: 192.168.122.104:47778 [09/Jun/2026:08:33:52.027] redis redis/np0000068128.internalapi.localdomain 1/1/11 10 -- 45/45/44/44/0 0/0 Jun 9 08:33:52 np0000068130 haproxy[7]: 192.168.122.104:47768 [09/Jun/2026:08:33:51.760] redis redis/np0000068128.internalapi.localdomain 1/0/277 4433 -- 45/45/43/43/0 0/0 Jun 9 08:33:52 np0000068130 haproxy[7]: 192.168.122.110:60294 [09/Jun/2026:08:33:52.037] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0 Jun 9 08:33:52 np0000068130 haproxy[7]: 192.168.122.110:60288 [09/Jun/2026:08:33:51.780] redis redis/np0000068128.internalapi.localdomain 1/0/270 4433 -- 42/42/41/41/0 0/0 Jun 9 08:33:52 np0000068130 haproxy[7]: 192.168.122.104:47800 [09/Jun/2026:08:33:52.285] redis redis/np0000068128.internalapi.localdomain 1/0/14 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:52 np0000068130 haproxy[7]: 192.168.122.104:47788 [09/Jun/2026:08:33:52.059] redis redis/np0000068128.internalapi.localdomain 1/0/240 4433 -- 43/43/42/42/0 0/0 Jun 9 08:33:52 np0000068130 haproxy[7]: 192.168.122.110:60302 [09/Jun/2026:08:33:52.077] redis redis/np0000068128.internalapi.localdomain 1/0/278 4433 -- 44/44/43/43/0 0/0 Jun 9 08:33:52 np0000068130 haproxy[7]: 192.168.122.110:60318 [09/Jun/2026:08:33:52.343] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 44/44/42/42/0 0/0 Jun 9 08:33:52 np0000068130 haproxy[7]: 192.168.122.104:47806 [09/Jun/2026:08:33:52.329] redis redis/np0000068128.internalapi.localdomain 1/0/322 4433 -- 43/43/41/41/0 0/0 Jun 9 08:33:52 np0000068130 haproxy[7]: 192.168.122.104:47816 [09/Jun/2026:08:33:52.641] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 43/43/41/41/0 0/0 Jun 9 08:33:57 np0000068130 haproxy[7]: 192.168.122.110:53962 [09/Jun/2026:08:33:57.614] redis redis/np0000068128.internalapi.localdomain 1/1/19 10 -- 43/43/42/42/0 0/0 Jun 9 08:33:57 np0000068130 haproxy[7]: 192.168.122.110:60320 [09/Jun/2026:08:33:57.379] redis redis/np0000068128.internalapi.localdomain 1/0/254 4432 -- 42/42/41/41/0 0/0 Jun 9 08:33:57 np0000068130 haproxy[7]: 192.168.122.110:53988 [09/Jun/2026:08:33:57.884] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:57 np0000068130 haproxy[7]: 192.168.122.110:53972 [09/Jun/2026:08:33:57.651] redis redis/np0000068128.internalapi.localdomain 1/0/245 4430 -- 44/44/42/42/0 0/0 Jun 9 08:33:57 np0000068130 haproxy[7]: 192.168.122.104:43102 [09/Jun/2026:08:33:57.982] redis redis/np0000068128.internalapi.localdomain 1/0/13 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:57 np0000068130 haproxy[7]: 192.168.122.104:43100 [09/Jun/2026:08:33:57.688] redis redis/np0000068128.internalapi.localdomain 1/0/307 4432 -- 44/44/42/42/0 0/0 Jun 9 08:33:58 np0000068130 haproxy[7]: 192.168.122.110:53994 [09/Jun/2026:08:33:58.207] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:58 np0000068130 haproxy[7]: 192.168.122.110:53992 [09/Jun/2026:08:33:57.925] redis redis/np0000068128.internalapi.localdomain 1/0/294 4433 -- 44/44/42/42/0 0/0 Jun 9 08:33:58 np0000068130 haproxy[7]: 192.168.122.104:43112 [09/Jun/2026:08:33:58.306] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 44/44/43/43/0 0/0 Jun 9 08:33:58 np0000068130 haproxy[7]: 192.168.122.104:43104 [09/Jun/2026:08:33:58.029] redis redis/np0000068128.internalapi.localdomain 1/0/291 4433 -- 43/43/42/42/0 0/0 Jun 9 08:33:58 np0000068130 haproxy[7]: 192.168.122.110:54020 [09/Jun/2026:08:33:58.477] redis redis/np0000068128.internalapi.localdomain 1/0/11 10 -- 44/44/42/42/0 0/0 Jun 9 08:33:58 np0000068130 haproxy[7]: 192.168.122.110:54008 [09/Jun/2026:08:33:58.243] redis redis/np0000068128.internalapi.localdomain 1/1/245 4433 -- 44/44/42/42/0 0/0 Jun 9 08:33:58 np0000068130 haproxy[7]: 192.168.122.104:43138 [09/Jun/2026:08:33:58.594] redis redis/np0000068128.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0 Jun 9 08:33:58 np0000068130 haproxy[7]: 192.168.122.104:43122 [09/Jun/2026:08:33:58.342] redis redis/np0000068128.internalapi.localdomain 1/0/264 4433 -- 42/42/41/41/0 0/0 Jun 9 08:33:58 np0000068130 haproxy[7]: 192.168.122.104:43142 [09/Jun/2026:08:33:58.637] redis redis/np0000068128.internalapi.localdomain 1/0/260 4432 -- 43/43/42/42/0 0/0 Jun 9 08:33:58 np0000068130 haproxy[7]: 192.168.122.104:43158 [09/Jun/2026:08:33:58.883] redis redis/np0000068128.internalapi.localdomain 1/0/15 10 -- 42/42/41/41/0 0/0 Jun 9 08:34:02 np0000068130 haproxy[7]: 192.168.122.103:56672 [09/Jun/2026:08:34:02.123] redis redis/np0000068128.internalapi.localdomain 1/0/44 14 -- 42/42/41/41/0 0/0 Jun 9 08:34:08 np0000068130 haproxy[7]: Server gnocchi/np0000068128.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 9 08:44:49 np0000068130 haproxy[7]: Server aodh/np0000068128.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 9 08:44:54 np0000068130 haproxy[7]: Server aodh/np0000068129.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 9 08:44:54 np0000068130 haproxy[7]: 192.168.122.103:34300 [09/Jun/2026:08:39:24.291] redis redis/np0000068128.internalapi.localdomain 1/1/330271 6143 -- 85/85/84/84/0 0/0 Jun 9 08:44:54 np0000068130 haproxy[7]: 192.168.122.103:53866 [09/Jun/2026:08:28:22.394] redis redis/np0000068128.internalapi.localdomain 1/0/992121 15166 -- 84/84/83/83/0 0/0 Jun 9 08:44:54 np0000068130 haproxy[7]: 192.168.122.103:34288 [09/Jun/2026:08:39:24.297] redis redis/np0000068128.internalapi.localdomain 1/160/330272 6199 -- 83/83/82/82/0 0/0 Jun 9 08:44:54 np0000068130 haproxy[7]: 192.168.122.103:53896 [09/Jun/2026:08:28:23.003] redis redis/np0000068128.internalapi.localdomain 1/0/991518 15155 -- 82/82/81/81/0 0/0 Jun 9 08:44:54 np0000068130 haproxy[7]: 192.168.122.103:34272 [09/Jun/2026:08:39:24.297] redis redis/np0000068128.internalapi.localdomain 1/160/330273 10 -- 81/81/79/79/0 0/0 Jun 9 08:44:54 np0000068130 haproxy[7]: 192.168.122.103:53880 [09/Jun/2026:08:28:22.577] redis redis/np0000068128.internalapi.localdomain 1/0/991946 21347 -- 81/81/79/79/0 0/0 Jun 9 08:44:54 np0000068130 haproxy[7]: 192.168.122.103:34292 [09/Jun/2026:08:39:24.291] redis redis/np0000068128.internalapi.localdomain 1/1/330281 6227 -- 79/79/78/78/0 0/0 Jun 9 08:44:54 np0000068130 haproxy[7]: 192.168.122.103:53900 [09/Jun/2026:08:28:23.130] redis redis/np0000068128.internalapi.localdomain 1/0/991394 15157 -- 78/78/77/77/0 0/0 Jun 9 08:44:55 np0000068130 haproxy[7]: 192.168.122.104:49314 [09/Jun/2026:08:28:39.085] redis redis/np0000068128.internalapi.localdomain 1/0/976629 21233 -- 77/77/76/76/0 0/0 Jun 9 08:44:55 np0000068130 haproxy[7]: 192.168.122.104:49318 [09/Jun/2026:08:28:39.117] redis redis/np0000068128.internalapi.localdomain 1/7/976601 21267 -- 76/76/75/75/0 0/0 Jun 9 08:44:55 np0000068130 haproxy[7]: 192.168.122.104:49272 [09/Jun/2026:08:28:38.988] redis redis/np0000068128.internalapi.localdomain 1/1/976738 21289 -- 75/75/74/74/0 0/0 Jun 9 08:44:55 np0000068130 haproxy[7]: 192.168.122.104:49300 [09/Jun/2026:08:28:39.064] redis redis/np0000068128.internalapi.localdomain 1/0/976663 21316 -- 74/74/73/73/0 0/0 Jun 9 08:44:57 np0000068130 haproxy[7]: 192.168.122.110:40498 [09/Jun/2026:08:33:38.686] redis redis/np0000068128.internalapi.localdomain 1/0/678331 12345 -- 73/73/72/72/0 0/0 Jun 9 08:44:57 np0000068130 haproxy[7]: 192.168.122.110:51578 [09/Jun/2026:08:28:38.299] redis redis/np0000068128.internalapi.localdomain 1/0/978679 8913 -- 72/72/71/71/0 0/0 Jun 9 08:44:57 np0000068130 haproxy[7]: 192.168.122.110:51618 [09/Jun/2026:08:28:38.654] redis redis/np0000068128.internalapi.localdomain 1/0/978330 21275 -- 71/71/70/70/0 0/0 Jun 9 08:44:57 np0000068130 haproxy[7]: 192.168.122.110:51604 [09/Jun/2026:08:28:38.649] redis redis/np0000068128.internalapi.localdomain 1/0/978336 21302 -- 70/70/69/69/0 0/0 Jun 9 08:44:57 np0000068130 haproxy[7]: 192.168.122.110:40482 [09/Jun/2026:08:33:38.684] redis redis/np0000068128.internalapi.localdomain 1/0/678349 12429 -- 69/69/68/68/0 0/0 Jun 9 08:44:57 np0000068130 haproxy[7]: 192.168.122.110:51596 [09/Jun/2026:08:28:38.641] redis redis/np0000068128.internalapi.localdomain 1/0/978352 8911 -- 69/69/67/67/0 0/0 Jun 9 08:44:58 np0000068130 haproxy[7]: Server aodh/np0000068130.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 9 08:44:58 np0000068130 haproxy[7]: proxy aodh has no server available! Jun 9 08:46:54 np0000068130 haproxy[7]: 192.168.122.103:53916 [09/Jun/2026:08:28:23.632] redis redis/np0000068128.internalapi.localdomain 1/0/1110950 5927 -- 67/67/66/66/0 0/0 Jun 9 08:46:56 np0000068130 haproxy[7]: 192.168.122.104:49290 [09/Jun/2026:08:28:39.020] redis redis/np0000068128.internalapi.localdomain 1/0/1097052 1843 -- 66/66/65/65/0 0/0 Jun 9 08:46:56 np0000068130 haproxy[7]: 192.168.122.104:49280 [09/Jun/2026:08:28:39.000] redis redis/np0000068128.internalapi.localdomain 1/1/1097073 4418 -- 66/66/64/64/0 0/0 Jun 9 08:46:57 np0000068130 haproxy[7]: 192.168.122.110:51590 [09/Jun/2026:08:28:38.346] redis redis/np0000068128.internalapi.localdomain 1/2/1099020 5092 -- 64/64/63/63/0 0/0 Jun 9 08:46:57 np0000068130 haproxy[7]: 192.168.122.110:40468 [09/Jun/2026:08:33:38.412] redis redis/np0000068128.internalapi.localdomain 1/258/798995 992 -- 64/64/62/62/0 0/0 Jun 9 08:48:11 np0000068130 haproxy[7]: Server horizon/np0000068128.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 9 08:48:15 np0000068130 haproxy[7]: Server horizon/np0000068129.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 9 08:48:19 np0000068130 haproxy[7]: Server horizon/np0000068130.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 9 08:48:19 np0000068130 haproxy[7]: proxy horizon has no server available! Jun 9 08:48:23 np0000068130 haproxy[7]: Server keystone_public/np0000068128.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 9 08:48:23 np0000068130 haproxy[7]: Server keystone_admin/np0000068128.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 9 08:48:27 np0000068130 haproxy[7]: Server keystone_admin/np0000068129.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 9 08:48:27 np0000068130 haproxy[7]: Server keystone_public/np0000068129.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 9 08:48:31 np0000068130 haproxy[7]: Server keystone_admin/np0000068130.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 9 08:48:31 np0000068130 haproxy[7]: proxy keystone_admin has no server available! Jun 9 08:48:31 np0000068130 haproxy[7]: Server keystone_public/np0000068130.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 9 08:48:31 np0000068130 haproxy[7]: proxy keystone_public has no server available! Jun 9 08:48:38 np0000068130 haproxy[7]: Server cinder/np0000068128.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 9 08:48:42 np0000068130 haproxy[7]: Server cinder/np0000068129.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 9 08:48:46 np0000068130 haproxy[7]: Server cinder/np0000068130.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 9 08:48:46 np0000068130 haproxy[7]: proxy cinder has no server available! Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:41002 [09/Jun/2026:08:34:07.606] redis redis/np0000068128.internalapi.localdomain 1/0/988748 4761 -- 62/62/60/60/0 0/0 Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:56736 [09/Jun/2026:08:34:05.031] redis redis/np0000068128.internalapi.localdomain 1/0/991323 4770 -- 62/62/61/61/0 0/0 Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:38516 [09/Jun/2026:08:43:20.256] redis redis/np0000068128.internalapi.localdomain 1/0/436107 30 -- 60/60/59/59/0 0/0 Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:41018 [09/Jun/2026:08:34:08.524] redis redis/np0000068128.internalapi.localdomain 1/0/987833 4762 -- 59/59/58/58/0 0/0 Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:56748 [09/Jun/2026:08:34:06.065] redis redis/np0000068128.internalapi.localdomain 1/0/990291 4766 -- 58/58/56/56/0 0/0 Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:38512 [09/Jun/2026:08:43:20.185] redis redis/np0000068128.internalapi.localdomain 1/0/436180 22 -- 58/58/57/57/0 0/0 Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:41020 [09/Jun/2026:08:34:09.059] redis redis/np0000068128.internalapi.localdomain 1/0/987298 4762 -- 56/56/55/55/0 0/0 Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:56724 [09/Jun/2026:08:34:05.010] redis redis/np0000068128.internalapi.localdomain 1/0/991348 4769 -- 55/55/53/53/0 0/0 Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:38498 [09/Jun/2026:08:43:20.138] redis redis/np0000068128.internalapi.localdomain 1/0/436227 22 -- 56/56/54/54/0 0/0 Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:41008 [09/Jun/2026:08:34:07.967] redis redis/np0000068128.internalapi.localdomain 1/0/988392 4763 -- 53/53/52/52/0 0/0 Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:56742 [09/Jun/2026:08:34:05.950] redis redis/np0000068128.internalapi.localdomain 1/0/990410 4767 -- 52/52/50/50/0 0/0 Jun 9 08:50:36 np0000068130 haproxy[7]: 192.168.122.103:41290 [09/Jun/2026:08:40:41.587] redis redis/np0000068128.internalapi.localdomain 1/0/594780 22 -- 52/52/51/50/0 0/0 Jun 9 08:50:37 np0000068130 haproxy[7]: Server glance_api/np0000068128.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 9 08:50:38 np0000068130 haproxy[7]: Server glance_api/np0000068129.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 9 08:50:40 np0000068130 haproxy[7]: 192.168.122.104:41120 [09/Jun/2026:08:43:20.268] redis redis/np0000068128.internalapi.localdomain 1/0/440221 30 -- 50/50/49/49/0 0/0 Jun 9 08:50:40 np0000068130 haproxy[7]: 192.168.122.104:47870 [09/Jun/2026:08:34:07.101] redis redis/np0000068128.internalapi.localdomain 1/0/993381 4767 -- 50/50/48/48/0 0/0 Jun 9 08:50:40 np0000068130 haproxy[7]: 192.168.122.104:47320 [09/Jun/2026:08:32:40.380] redis redis/np0000068128.internalapi.localdomain 1/0/1080101 4784 -- 50/50/47/47/0 0/0 Jun 9 08:50:40 np0000068130 haproxy[7]: 192.168.122.104:47852 [09/Jun/2026:08:34:06.288] redis redis/np0000068128.internalapi.localdomain 1/0/994194 4771 -- 47/47/46/46/0 0/0 Jun 9 08:50:40 np0000068130 haproxy[7]: 192.168.122.104:41116 [09/Jun/2026:08:43:20.172] redis redis/np0000068128.internalapi.localdomain 1/0/440319 22 -- 47/47/45/45/0 0/0 Jun 9 08:50:40 np0000068130 haproxy[7]: 192.168.122.104:47336 [09/Jun/2026:08:32:41.385] redis redis/np0000068128.internalapi.localdomain 1/0/1079098 4783 -- 45/45/44/44/0 0/0 Jun 9 08:50:40 np0000068130 haproxy[7]: 192.168.122.104:47872 [09/Jun/2026:08:34:07.662] redis redis/np0000068128.internalapi.localdomain 1/0/992822 4766 -- 44/44/43/43/0 0/0 Jun 9 08:50:40 np0000068130 haproxy[7]: 192.168.122.104:47360 [09/Jun/2026:08:32:41.821] redis redis/np0000068128.internalapi.localdomain 1/1/1078664 4785 -- 43/43/42/42/0 0/0 Jun 9 08:50:40 np0000068130 haproxy[7]: 192.168.122.104:47868 [09/Jun/2026:08:34:06.706] redis redis/np0000068128.internalapi.localdomain 1/0/993780 4769 -- 42/42/41/41/0 0/0 Jun 9 08:50:40 np0000068130 haproxy[7]: 192.168.122.104:47348 [09/Jun/2026:08:32:41.386] redis redis/np0000068128.internalapi.localdomain 1/0/1079100 4784 -- 41/41/40/40/0 0/0 Jun 9 08:50:40 np0000068130 haproxy[7]: Server glance_api/np0000068130.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 9 08:50:40 np0000068130 haproxy[7]: proxy glance_api has no server available! Jun 9 08:50:44 np0000068130 haproxy[7]: Server gnocchi/np0000068128.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 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:39382 [09/Jun/2026:08:40:41.578] redis redis/np0000068128.internalapi.localdomain 1/0/603083 42 -- 40/40/39/39/0 0/0 Jun 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:56230 [09/Jun/2026:08:32:35.417] redis redis/np0000068128.internalapi.localdomain 1/2/1089237 4787 -- 40/40/37/37/0 0/0 Jun 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:54096 [09/Jun/2026:08:34:07.413] redis redis/np0000068128.internalapi.localdomain 1/0/997241 4767 -- 40/40/37/37/0 0/0 Jun 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:54080 [09/Jun/2026:08:34:07.182] redis redis/np0000068128.internalapi.localdomain 1/0/997472 4767 -- 39/39/36/36/0 0/0 Jun 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:58226 [09/Jun/2026:08:41:46.298] redis redis/np0000068128.internalapi.localdomain 1/0/538365 70 -- 36/36/35/35/0 0/0 Jun 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:56280 [09/Jun/2026:08:32:36.829] redis redis/np0000068128.internalapi.localdomain 1/0/1087827 4789 -- 35/35/34/34/0 0/0 Jun 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:39844 [09/Jun/2026:08:43:20.175] redis redis/np0000068128.internalapi.localdomain 1/0/444489 38 -- 34/34/33/33/0 0/0 Jun 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:56242 [09/Jun/2026:08:32:35.419] redis redis/np0000068128.internalapi.localdomain 1/0/1089237 4787 -- 33/33/32/32/0 0/0 Jun 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:54068 [09/Jun/2026:08:34:06.907] redis redis/np0000068128.internalapi.localdomain 1/0/997750 4769 -- 32/32/31/31/0 0/0 Jun 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:39828 [09/Jun/2026:08:43:20.156] redis redis/np0000068128.internalapi.localdomain 1/0/444510 22 -- 31/31/30/30/0 0/0 Jun 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:56278 [09/Jun/2026:08:32:36.690] redis redis/np0000068128.internalapi.localdomain 1/0/1087969 4789 -- 30/30/29/29/0 0/0 Jun 9 08:50:44 np0000068130 haproxy[7]: 192.168.122.110:54054 [09/Jun/2026:08:34:06.423] redis redis/np0000068128.internalapi.localdomain 1/0/998235 4771 -- 29/29/28/28/0 0/0 Jun 9 08:50:45 np0000068130 haproxy[7]: 192.168.122.103:56690 [09/Jun/2026:08:34:04.467] redis redis/np0000068128.internalapi.localdomain 1/0/1001518 4771 -- 28/28/27/27/0 0/0 Jun 9 08:50:45 np0000068130 haproxy[7]: 192.168.122.103:56676 [09/Jun/2026:08:34:04.337] redis redis/np0000068128.internalapi.localdomain 1/0/1001652 149 -- 27/27/26/26/0 0/0 Jun 9 08:50:46 np0000068130 haproxy[7]: 192.168.122.103:56708 [09/Jun/2026:08:34:04.934] redis redis/np0000068128.internalapi.localdomain 1/0/1001063 33147 -- 26/26/25/25/0 0/0 Jun 9 08:50:46 np0000068130 haproxy[7]: 192.168.122.103:56706 [09/Jun/2026:08:34:04.863] redis redis/np0000068128.internalapi.localdomain 1/0/1001135 2144 -- 25/25/23/23/0 0/0 Jun 9 08:50:46 np0000068130 haproxy[7]: 192.168.122.103:59578 [09/Jun/2026:08:41:59.294] redis redis/np0000068128.internalapi.localdomain 1/0/526711 20236 -- 25/25/24/24/0 0/0 Jun 9 08:50:46 np0000068130 haproxy[7]: 192.168.122.103:56696 [09/Jun/2026:08:34:04.471] redis redis/np0000068128.internalapi.localdomain 1/0/1001527 30766 -- 23/23/22/22/0 0/0 Jun 9 08:50:47 np0000068130 haproxy[7]: 192.168.122.104:47290 [09/Jun/2026:08:32:40.058] redis redis/np0000068128.internalapi.localdomain 1/0/1087127 4792 -- 22/22/21/21/0 0/0 Jun 9 08:50:47 np0000068130 haproxy[7]: 192.168.122.104:47288 [09/Jun/2026:08:32:40.052] redis redis/np0000068128.internalapi.localdomain 1/0/1087136 154 -- 21/21/20/20/0 0/0 Jun 9 08:50:47 np0000068130 haproxy[7]: 192.168.122.104:47842 [09/Jun/2026:08:34:04.255] redis redis/np0000068128.internalapi.localdomain 1/0/1002950 33250 -- 20/20/19/19/0 0/0 Jun 9 08:50:47 np0000068130 haproxy[7]: 192.168.122.104:47826 [09/Jun/2026:08:34:04.219] redis redis/np0000068128.internalapi.localdomain 1/0/1002987 2144 -- 20/20/18/18/0 0/0 Jun 9 08:50:47 np0000068130 haproxy[7]: 192.168.122.104:41124 [09/Jun/2026:08:43:20.430] redis redis/np0000068128.internalapi.localdomain 1/0/446785 19294 -- 18/18/17/17/0 0/0 Jun 9 08:50:47 np0000068130 haproxy[7]: 192.168.122.104:47818 [09/Jun/2026:08:34:03.934] redis redis/np0000068128.internalapi.localdomain 1/25/1003274 30348 -- 17/17/16/16/0 0/0 Jun 9 08:50:48 np0000068130 haproxy[7]: Server gnocchi/np0000068129.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 9 08:50:48 np0000068130 haproxy[7]: 192.168.122.110:56214 [09/Jun/2026:08:32:35.235] redis redis/np0000068128.internalapi.localdomain 1/0/1093671 4792 -- 16/16/15/15/0 0/0 Jun 9 08:50:48 np0000068130 haproxy[7]: 192.168.122.110:56198 [09/Jun/2026:08:32:35.234] redis redis/np0000068128.internalapi.localdomain 1/0/1093672 154 -- 15/15/14/14/0 0/0 Jun 9 08:50:48 np0000068130 haproxy[7]: 192.168.122.110:54046 [09/Jun/2026:08:34:04.798] redis redis/np0000068128.internalapi.localdomain 1/0/1004122 33831 -- 14/14/12/12/0 0/0 Jun 9 08:50:48 np0000068130 haproxy[7]: 192.168.122.110:58238 [09/Jun/2026:08:41:46.600] redis redis/np0000068128.internalapi.localdomain 1/0/542328 3046 -- 14/14/12/12/0 0/0 Jun 9 08:50:48 np0000068130 haproxy[7]: 192.168.122.110:54024 [09/Jun/2026:08:34:03.514] redis redis/np0000068128.internalapi.localdomain 1/0/1005406 46916 -- 14/14/11/11/0 0/0 Jun 9 08:50:48 np0000068130 haproxy[7]: 192.168.122.110:54030 [09/Jun/2026:08:34:03.754] redis redis/np0000068128.internalapi.localdomain 1/0/1005166 2144 -- 11/11/10/10/0 0/0 Jun 9 08:50:52 np0000068130 haproxy[7]: Server gnocchi/np0000068130.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 9 08:50:52 np0000068130 haproxy[7]: proxy gnocchi has no server available! Jun 9 08:51:03 np0000068130 haproxy[7]: Server manila/np0000068128.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 9 08:51:07 np0000068130 haproxy[7]: Server manila/np0000068129.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 9 08:51:11 np0000068130 haproxy[7]: Server manila/np0000068130.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 9 08:51:11 np0000068130 haproxy[7]: proxy manila has no server available! Jun 9 08:51:58 np0000068130 haproxy[7]: Server neutron/np0000068128.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 9 08:52:12 np0000068130 haproxy[7]: Server neutron/np0000068129.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 9 08:52:37 np0000068130 haproxy[7]: Server neutron/np0000068130.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 9 08:52:37 np0000068130 haproxy[7]: proxy neutron has no server available! Jun 9 08:52:45 np0000068130 haproxy[7]: Server placement/np0000068128.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 2ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Jun 9 08:52:50 np0000068130 haproxy[7]: Server placement/np0000068129.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 9 08:52:54 np0000068130 haproxy[7]: Server placement/np0000068130.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 9 08:52:54 np0000068130 haproxy[7]: proxy placement has no server available! Jun 9 08:53:03 np0000068130 haproxy[7]: Server nova_osapi/np0000068128.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 9 08:53:07 np0000068130 haproxy[7]: Server nova_osapi/np0000068129.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 9 08:53:11 np0000068130 haproxy[7]: Server nova_osapi/np0000068130.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 9 08:53:11 np0000068130 haproxy[7]: proxy nova_osapi has no server available! Jun 9 08:53:20 np0000068130 haproxy[7]: Server nova_metadata/np0000068128.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 9 08:53:25 np0000068130 haproxy[7]: Server nova_metadata/np0000068129.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 9 08:53:29 np0000068130 haproxy[7]: Server nova_metadata/np0000068130.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 9 08:53:29 np0000068130 haproxy[7]: proxy nova_metadata has no server available! Jun 9 08:54:20 np0000068130 haproxy[7]: Server nova_novncproxy/np0000068128.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 9 08:54:21 np0000068130 haproxy[7]: Server nova_novncproxy/np0000068129.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 9 08:54:23 np0000068130 haproxy[7]: Server nova_novncproxy/np0000068130.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 9 08:54:23 np0000068130 haproxy[7]: proxy nova_novncproxy has no server available! Jun 9 09:03:27 np0000068130 haproxy[7]: Backup Server mysql/np0000068129.internalapi.localdomain is DOWN, reason: Layer4 timeout, check duration: 1000ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue. Jun 9 09:03:33 np0000068130 haproxy[7]: Backup Server mysql/np0000068130.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 18ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue. Jun 9 09:03:36 np0000068130 haproxy[7]: Backup Server mysql/np0000068128.internalapi.localdomain is DOWN, reason: Layer7 invalid response, check duration: 10205ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Jun 9 09:03:36 np0000068130 haproxy[7]: proxy mysql has no server available! Jun 9 09:03:40 np0000068130 haproxy[7]: Backup Server mysql/np0000068129.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 26ms. 0 active and 1 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue. Jun 9 09:03:40 np0000068130 haproxy[7]: Backup Server mysql/np0000068128.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 17ms. 0 active and 2 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue. Jun 9 09:03:46 np0000068130 haproxy[7]: Backup Server mysql/np0000068129.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 345ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue. Jun 9 09:04:04 np0000068130 haproxy[7]: Backup Server mysql/np0000068129.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 21ms. 0 active and 2 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue. Jun 9 09:04:12 np0000068130 haproxy[7]: Backup Server mysql/np0000068130.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 9 09:14:41 np0000068130 haproxy[7]: Backup Server mysql/np0000068130.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 22ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.