Feb 23 08:00:17 np0005626461 haproxy[7]: Server aodh/np0005626460.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.
Feb 23 08:00:17 np0005626461 haproxy[7]: Server aodh/np0005626459.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.
Feb 23 08:00:17 np0005626461 haproxy[7]: Server aodh/np0005626461.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.
Feb 23 08:00:17 np0005626461 haproxy[7]: proxy aodh has no server available!
Feb 23 08:00:18 np0005626461 haproxy[7]: Server cinder/np0005626459.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server cinder/np0005626460.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server cinder/np0005626461.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: proxy cinder has no server available!
Feb 23 08:00:18 np0005626461 haproxy[7]: Server glance_api/np0005626459.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server glance_api/np0005626460.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server glance_api/np0005626461.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: proxy glance_api has no server available!
Feb 23 08:00:18 np0005626461 haproxy[7]: Server glance_api_internal/np0005626459.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server glance_api_internal/np0005626460.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server glance_api_internal/np0005626461.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: proxy glance_api_internal has no server available!
Feb 23 08:00:18 np0005626461 haproxy[7]: Server gnocchi/np0005626459.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server gnocchi/np0005626460.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server gnocchi/np0005626461.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: proxy gnocchi has no server available!
Feb 23 08:00:18 np0005626461 haproxy[7]: Server heat_api/np0005626459.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server heat_api/np0005626460.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Backup Server mysql/np0005626459.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server heat_api/np0005626461.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: proxy heat_api has no server available!
Feb 23 08:00:18 np0005626461 haproxy[7]: Backup Server mysql/np0005626460.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 23ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server heat_cfn/np0005626459.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Backup Server mysql/np0005626461.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 20ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Feb 23 08:00:18 np0005626461 haproxy[7]: proxy mysql has no server available!
Feb 23 08:00:18 np0005626461 haproxy[7]: Server heat_cfn/np0005626460.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server heat_cfn/np0005626461.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: proxy heat_cfn has no server available!
Feb 23 08:00:18 np0005626461 haproxy[7]: Server horizon/np0005626459.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server horizon/np0005626460.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server horizon/np0005626461.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: proxy horizon has no server available!
Feb 23 08:00:18 np0005626461 haproxy[7]: Server keystone_admin/np0005626459.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server keystone_admin/np0005626460.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server keystone_admin/np0005626461.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: proxy keystone_admin has no server available!
Feb 23 08:00:18 np0005626461 haproxy[7]: Server keystone_public/np0005626459.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server keystone_public/np0005626460.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: Server keystone_public/np0005626461.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.
Feb 23 08:00:18 np0005626461 haproxy[7]: proxy keystone_public has no server available!
Feb 23 08:00:18 np0005626461 haproxy[7]: Server manila/np0005626459.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server manila/np0005626460.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server manila/np0005626461.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: proxy manila has no server available!
Feb 23 08:00:19 np0005626461 haproxy[7]: Server neutron/np0005626459.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server neutron/np0005626460.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server neutron/np0005626461.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: proxy neutron has no server available!
Feb 23 08:00:19 np0005626461 haproxy[7]: Server nova_metadata/np0005626459.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server nova_metadata/np0005626460.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server nova_metadata/np0005626461.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: proxy nova_metadata has no server available!
Feb 23 08:00:19 np0005626461 haproxy[7]: Server nova_novncproxy/np0005626459.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server nova_novncproxy/np0005626460.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server nova_novncproxy/np0005626461.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: proxy nova_novncproxy has no server available!
Feb 23 08:00:19 np0005626461 haproxy[7]: Server nova_osapi/np0005626459.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server nova_osapi/np0005626460.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server nova_osapi/np0005626461.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: proxy nova_osapi has no server available!
Feb 23 08:00:19 np0005626461 haproxy[7]: Server placement/np0005626459.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server placement/np0005626460.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server placement/np0005626461.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: proxy placement has no server available!
Feb 23 08:00:19 np0005626461 haproxy[7]: Server redis/np0005626459.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server redis/np0005626460.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server redis/np0005626461.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: proxy redis has no server available!
Feb 23 08:00:19 np0005626461 haproxy[7]: Server swift_proxy_server/np0005626459.storage.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server swift_proxy_server/np0005626460.storage.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 3ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Feb 23 08:00:19 np0005626461 haproxy[7]: Server swift_proxy_server/np0005626461.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.
Feb 23 08:00:19 np0005626461 haproxy[7]: proxy swift_proxy_server has no server available!
Feb 23 08:02:04 np0005626461 haproxy[7]: Backup Server mysql/np0005626461.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 22ms. 0 active and 1 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Feb 23 08:02:27 np0005626461 haproxy[7]: Backup Server mysql/np0005626461.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 22ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Feb 23 08:02:27 np0005626461 haproxy[7]: proxy mysql has no server available!
Feb 23 08:02:29 np0005626461 haproxy[7]: Backup Server mysql/np0005626461.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 21ms. 0 active and 1 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Feb 23 08:02:34 np0005626461 haproxy[7]: Backup Server mysql/np0005626460.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 874ms. 0 active and 2 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Feb 23 08:03:33 np0005626461 haproxy[7]: Backup Server mysql/np0005626460.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 66ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
Feb 23 08:03:38 np0005626461 haproxy[7]: Server redis/np0005626459.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.
Feb 23 08:03:50 np0005626461 haproxy[7]: Backup Server mysql/np0005626459.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.
Feb 23 08:03:50 np0005626461 haproxy[7]: Backup Server mysql/np0005626460.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 25ms. 0 active and 3 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Feb 23 08:04:35 np0005626461 haproxy[7]: Server keystone_admin/np0005626461.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.
Feb 23 08:04:35 np0005626461 haproxy[7]: Server keystone_public/np0005626461.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.
Feb 23 08:04:35 np0005626461 haproxy[7]: Server keystone_admin/np0005626460.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.
Feb 23 08:04:35 np0005626461 haproxy[7]: Server keystone_public/np0005626460.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.
Feb 23 08:04:38 np0005626461 haproxy[7]: Server horizon/np0005626461.internalapi.localdomain is UP, reason: Layer7 check passed, code: 301, check duration: 0ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Feb 23 08:04:39 np0005626461 haproxy[7]: Server horizon/np0005626460.internalapi.localdomain is UP, reason: Layer7 check passed, code: 301, check duration: 2ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Feb 23 08:05:17 np0005626461 haproxy[7]: Server horizon/np0005626459.internalapi.localdomain is UP, reason: Layer7 check passed, code: 301, check duration: 2ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Feb 23 08:05:41 np0005626461 haproxy[7]: Server keystone_admin/np0005626459.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 14ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Feb 23 08:05:41 np0005626461 haproxy[7]: Server keystone_public/np0005626459.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.
Feb 23 08:09:48 np0005626461 haproxy[7]: Server cinder/np0005626459.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.
Feb 23 08:09:48 np0005626461 haproxy[7]: Server heat_cfn/np0005626459.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.
Feb 23 08:09:49 np0005626461 haproxy[7]: Server heat_api/np0005626459.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.
Feb 23 08:09:49 np0005626461 haproxy[7]: Server aodh/np0005626459.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.
Feb 23 08:09:51 np0005626461 haproxy[7]: Server manila/np0005626459.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.
Feb 23 08:09:53 np0005626461 haproxy[7]: Server nova_novncproxy/np0005626459.internalapi.localdomain is UP, reason: Layer4 check passed, check duration: 1ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Feb 23 08:09:55 np0005626461 haproxy[7]: Server placement/np0005626459.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.
Feb 23 08:09:56 np0005626461 haproxy[7]: Server nova_metadata/np0005626459.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.
Feb 23 08:09:57 np0005626461 haproxy[7]: Server swift_proxy_server/np0005626459.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.
Feb 23 08:09:57 np0005626461 haproxy[7]: Server glance_api_internal/np0005626459.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.
Feb 23 08:09:57 np0005626461 haproxy[7]: Server neutron/np0005626459.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.
Feb 23 08:09:57 np0005626461 haproxy[7]: Server glance_api/np0005626459.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.
Feb 23 08:09:57 np0005626461 haproxy[7]: Server nova_osapi/np0005626459.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.
Feb 23 08:10:03 np0005626461 haproxy[7]: Server cinder/np0005626460.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.
Feb 23 08:10:03 np0005626461 haproxy[7]: Server heat_cfn/np0005626460.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.
Feb 23 08:10:03 np0005626461 haproxy[7]: Server heat_api/np0005626460.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.
Feb 23 08:10:03 np0005626461 haproxy[7]: Server aodh/np0005626460.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.
Feb 23 08:10:04 np0005626461 haproxy[7]: Server aodh/np0005626461.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.
Feb 23 08:10:05 np0005626461 haproxy[7]: Server cinder/np0005626461.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.
Feb 23 08:10:05 np0005626461 haproxy[7]: Server heat_cfn/np0005626461.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.
Feb 23 08:10:06 np0005626461 haproxy[7]: Server heat_api/np0005626461.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.
Feb 23 08:10:07 np0005626461 haproxy[7]: Server manila/np0005626460.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 978ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Feb 23 08:10:07 np0005626461 haproxy[7]: Server nova_novncproxy/np0005626460.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.
Feb 23 08:10:08 np0005626461 haproxy[7]: Server manila/np0005626461.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 909ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Feb 23 08:10:08 np0005626461 haproxy[7]: Server placement/np0005626460.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 1ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Feb 23 08:10:10 np0005626461 haproxy[7]: Server nova_novncproxy/np0005626461.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.
Feb 23 08:10:11 np0005626461 haproxy[7]: Server nova_metadata/np0005626460.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 2ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Feb 23 08:10:12 np0005626461 haproxy[7]: Server nova_osapi/np0005626460.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.
Feb 23 08:10:12 np0005626461 haproxy[7]: Server placement/np0005626461.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.
Feb 23 08:10:12 np0005626461 haproxy[7]: Server swift_proxy_server/np0005626460.storage.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 2ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Feb 23 08:10:12 np0005626461 haproxy[7]: Server glance_api/np0005626460.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.
Feb 23 08:10:12 np0005626461 haproxy[7]: Server neutron/np0005626460.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.
Feb 23 08:10:12 np0005626461 haproxy[7]: Server glance_api_internal/np0005626460.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.
Feb 23 08:10:14 np0005626461 haproxy[7]: Server nova_osapi/np0005626461.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.
Feb 23 08:10:14 np0005626461 haproxy[7]: Server swift_proxy_server/np0005626461.storage.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 1ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Feb 23 08:10:14 np0005626461 haproxy[7]: Server nova_metadata/np0005626461.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.
Feb 23 08:10:14 np0005626461 haproxy[7]: Server glance_api/np0005626461.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.
Feb 23 08:10:14 np0005626461 haproxy[7]: Server glance_api_internal/np0005626461.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.
Feb 23 08:10:15 np0005626461 haproxy[7]: Server neutron/np0005626461.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.
Feb 23 08:13:53 np0005626461 haproxy[7]: 192.168.122.110:46158 [23/Feb/2026:08:13:53.490] redis redis/np0005626459.internalapi.localdomain 1/0/9 10 -- 33/33/32/32/0 0/0
Feb 23 08:13:53 np0005626461 haproxy[7]: 192.168.122.110:46114 [23/Feb/2026:08:13:53.245] redis redis/np0005626459.internalapi.localdomain 1/1/257 4429 -- 32/32/31/31/0 0/0
Feb 23 08:13:53 np0005626461 haproxy[7]: 192.168.122.110:46194 [23/Feb/2026:08:13:53.762] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 34/34/33/33/0 0/0
Feb 23 08:13:53 np0005626461 haproxy[7]: 192.168.122.110:46166 [23/Feb/2026:08:13:53.526] redis redis/np0005626459.internalapi.localdomain 1/0/248 4429 -- 33/33/32/32/0 0/0
Feb 23 08:13:55 np0005626461 haproxy[7]: 192.168.122.104:33336 [23/Feb/2026:08:13:55.441] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Feb 23 08:13:55 np0005626461 haproxy[7]: 192.168.122.104:33300 [23/Feb/2026:08:13:55.179] redis redis/np0005626459.internalapi.localdomain 1/1/275 4429 -- 38/38/37/37/0 0/0
Feb 23 08:13:55 np0005626461 haproxy[7]: 192.168.122.104:33380 [23/Feb/2026:08:13:55.711] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 40/40/39/39/0 0/0
Feb 23 08:13:55 np0005626461 haproxy[7]: 192.168.122.104:33350 [23/Feb/2026:08:13:55.478] redis redis/np0005626459.internalapi.localdomain 1/0/245 4430 -- 40/40/38/38/0 0/0
Feb 23 08:13:56 np0005626461 haproxy[7]: Server gnocchi/np0005626461.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.
Feb 23 08:13:59 np0005626461 haproxy[7]: 192.168.122.110:50194 [23/Feb/2026:08:13:59.074] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:13:59 np0005626461 haproxy[7]: 192.168.122.110:50192 [23/Feb/2026:08:13:58.809] redis redis/np0005626459.internalapi.localdomain 1/0/275 4429 -- 43/43/41/41/0 0/0
Feb 23 08:13:59 np0005626461 haproxy[7]: 192.168.122.110:50206 [23/Feb/2026:08:13:59.111] redis redis/np0005626459.internalapi.localdomain 1/0/251 4429 -- 43/43/41/41/0 0/0
Feb 23 08:13:59 np0005626461 haproxy[7]: 192.168.122.110:50220 [23/Feb/2026:08:13:59.350] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/41/41/0 0/0
Feb 23 08:13:59 np0005626461 haproxy[7]: Server gnocchi/np0005626460.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.
Feb 23 08:13:59 np0005626461 haproxy[7]: 192.168.122.110:50248 [23/Feb/2026:08:13:59.637] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0
Feb 23 08:13:59 np0005626461 haproxy[7]: 192.168.122.110:50234 [23/Feb/2026:08:13:59.393] redis redis/np0005626459.internalapi.localdomain 1/0/256 4430 -- 42/42/41/41/0 0/0
Feb 23 08:13:59 np0005626461 haproxy[7]: 192.168.122.110:50266 [23/Feb/2026:08:13:59.879] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:13:59 np0005626461 haproxy[7]: 192.168.122.110:50256 [23/Feb/2026:08:13:59.668] redis redis/np0005626459.internalapi.localdomain 1/0/221 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:01 np0005626461 haproxy[7]: 192.168.122.104:58236 [23/Feb/2026:08:14:01.045] redis redis/np0005626459.internalapi.localdomain 1/0/13 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:01 np0005626461 haproxy[7]: 192.168.122.104:58234 [23/Feb/2026:08:14:00.759] redis redis/np0005626459.internalapi.localdomain 1/2/300 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:01 np0005626461 haproxy[7]: 192.168.122.104:58252 [23/Feb/2026:08:14:01.454] redis redis/np0005626459.internalapi.localdomain 1/0/13 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:01 np0005626461 haproxy[7]: 192.168.122.104:58240 [23/Feb/2026:08:14:01.095] redis redis/np0005626459.internalapi.localdomain 1/0/373 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:01 np0005626461 haproxy[7]: 192.168.122.104:58280 [23/Feb/2026:08:14:01.739] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:01 np0005626461 haproxy[7]: 192.168.122.104:58266 [23/Feb/2026:08:14:01.489] redis redis/np0005626459.internalapi.localdomain 1/0/262 4430 -- 43/43/41/41/0 0/0
Feb 23 08:14:02 np0005626461 haproxy[7]: 192.168.122.104:58306 [23/Feb/2026:08:14:02.044] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/41/41/0 0/0
Feb 23 08:14:02 np0005626461 haproxy[7]: 192.168.122.104:58294 [23/Feb/2026:08:14:01.783] redis redis/np0005626459.internalapi.localdomain 1/0/272 4430 -- 43/43/41/41/0 0/0
Feb 23 08:14:05 np0005626461 haproxy[7]: 192.168.122.110:42072 [23/Feb/2026:08:14:04.909] redis redis/np0005626459.internalapi.localdomain 1/0/232 4428 -- 43/43/42/42/0 0/0
Feb 23 08:14:05 np0005626461 haproxy[7]: 192.168.122.110:42078 [23/Feb/2026:08:14:05.133] redis redis/np0005626459.internalapi.localdomain 1/2/10 10 -- 42/42/41/41/0 0/0
Feb 23 08:14:05 np0005626461 haproxy[7]: 192.168.122.110:42104 [23/Feb/2026:08:14:05.403] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:05 np0005626461 haproxy[7]: 192.168.122.110:42088 [23/Feb/2026:08:14:05.158] redis redis/np0005626459.internalapi.localdomain 1/0/258 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:05 np0005626461 haproxy[7]: 192.168.122.110:42120 [23/Feb/2026:08:14:05.684] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:05 np0005626461 haproxy[7]: 192.168.122.110:42116 [23/Feb/2026:08:14:05.441] redis redis/np0005626459.internalapi.localdomain 1/1/253 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:05 np0005626461 haproxy[7]: 192.168.122.110:42138 [23/Feb/2026:08:14:05.963] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:05 np0005626461 haproxy[7]: 192.168.122.110:42126 [23/Feb/2026:08:14:05.718] redis redis/np0005626459.internalapi.localdomain 1/0/255 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:07 np0005626461 haproxy[7]: 192.168.122.104:55798 [23/Feb/2026:08:14:07.327] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:07 np0005626461 haproxy[7]: 192.168.122.104:55792 [23/Feb/2026:08:14:07.090] redis redis/np0005626459.internalapi.localdomain 1/0/250 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:07 np0005626461 haproxy[7]: 192.168.122.104:55814 [23/Feb/2026:08:14:07.632] redis redis/np0005626459.internalapi.localdomain 1/0/13 10 -- 43/43/41/41/0 0/0
Feb 23 08:14:07 np0005626461 haproxy[7]: 192.168.122.104:55800 [23/Feb/2026:08:14:07.366] redis redis/np0005626459.internalapi.localdomain 1/0/279 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:07 np0005626461 haproxy[7]: 192.168.122.104:55832 [23/Feb/2026:08:14:07.927] redis redis/np0005626459.internalapi.localdomain 1/0/16 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:07 np0005626461 haproxy[7]: 192.168.122.104:55826 [23/Feb/2026:08:14:07.678] redis redis/np0005626459.internalapi.localdomain 1/0/265 4428 -- 42/42/41/41/0 0/0
Feb 23 08:14:08 np0005626461 haproxy[7]: 192.168.122.104:55854 [23/Feb/2026:08:14:08.205] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:08 np0005626461 haproxy[7]: 192.168.122.104:55838 [23/Feb/2026:08:14:07.965] redis redis/np0005626459.internalapi.localdomain 1/0/252 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:11 np0005626461 haproxy[7]: 192.168.122.110:42146 [23/Feb/2026:08:14:11.008] redis redis/np0005626459.internalapi.localdomain 1/0/258 4429 -- 43/43/42/42/0 0/0
Feb 23 08:14:11 np0005626461 haproxy[7]: 192.168.122.110:42158 [23/Feb/2026:08:14:11.255] redis redis/np0005626459.internalapi.localdomain 1/0/13 10 -- 42/42/41/41/0 0/0
Feb 23 08:14:11 np0005626461 haproxy[7]: 192.168.122.110:42186 [23/Feb/2026:08:14:11.560] redis redis/np0005626459.internalapi.localdomain 1/0/13 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:11 np0005626461 haproxy[7]: 192.168.122.110:42172 [23/Feb/2026:08:14:11.297] redis redis/np0005626459.internalapi.localdomain 1/0/277 4430 -- 43/43/41/41/0 0/0
Feb 23 08:14:11 np0005626461 haproxy[7]: 192.168.122.110:42194 [23/Feb/2026:08:14:11.832] redis redis/np0005626459.internalapi.localdomain 1/0/7 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:11 np0005626461 haproxy[7]: 192.168.122.110:42192 [23/Feb/2026:08:14:11.609] redis redis/np0005626459.internalapi.localdomain 1/0/231 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:12 np0005626461 haproxy[7]: 192.168.122.110:42208 [23/Feb/2026:08:14:12.109] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:12 np0005626461 haproxy[7]: 192.168.122.110:42200 [23/Feb/2026:08:14:11.868] redis redis/np0005626459.internalapi.localdomain 1/0/251 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:13 np0005626461 haproxy[7]: 192.168.122.104:55868 [23/Feb/2026:08:14:13.498] redis redis/np0005626459.internalapi.localdomain 1/0/8 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:13 np0005626461 haproxy[7]: 192.168.122.104:55862 [23/Feb/2026:08:14:13.253] redis redis/np0005626459.internalapi.localdomain 1/0/254 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:13 np0005626461 haproxy[7]: 192.168.122.104:55890 [23/Feb/2026:08:14:13.813] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:13 np0005626461 haproxy[7]: 192.168.122.104:55878 [23/Feb/2026:08:14:13.529] redis redis/np0005626459.internalapi.localdomain 1/0/295 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:14 np0005626461 haproxy[7]: 192.168.122.104:55920 [23/Feb/2026:08:14:14.130] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:14 np0005626461 haproxy[7]: 192.168.122.104:55904 [23/Feb/2026:08:14:13.853] redis redis/np0005626459.internalapi.localdomain 1/0/289 4428 -- 42/42/41/41/0 0/0
Feb 23 08:14:14 np0005626461 haproxy[7]: 192.168.122.104:55946 [23/Feb/2026:08:14:14.427] redis redis/np0005626459.internalapi.localdomain 1/0/15 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:14 np0005626461 haproxy[7]: 192.168.122.104:55934 [23/Feb/2026:08:14:14.173] redis redis/np0005626459.internalapi.localdomain 1/0/269 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:17 np0005626461 haproxy[7]: 192.168.122.110:56794 [23/Feb/2026:08:14:17.368] redis redis/np0005626459.internalapi.localdomain 1/0/7 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:17 np0005626461 haproxy[7]: 192.168.122.110:56784 [23/Feb/2026:08:14:17.145] redis redis/np0005626459.internalapi.localdomain 1/0/231 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:17 np0005626461 haproxy[7]: 192.168.122.110:56808 [23/Feb/2026:08:14:17.400] redis redis/np0005626459.internalapi.localdomain 1/0/244 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:17 np0005626461 haproxy[7]: 192.168.122.110:56814 [23/Feb/2026:08:14:17.633] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:17 np0005626461 haproxy[7]: 192.168.122.110:56822 [23/Feb/2026:08:14:17.891] redis redis/np0005626459.internalapi.localdomain 1/0/9 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:17 np0005626461 haproxy[7]: 192.168.122.110:56818 [23/Feb/2026:08:14:17.670] redis redis/np0005626459.internalapi.localdomain 1/0/230 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:18 np0005626461 haproxy[7]: 192.168.122.110:56828 [23/Feb/2026:08:14:18.124] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:18 np0005626461 haproxy[7]: 192.168.122.110:56824 [23/Feb/2026:08:14:17.918] redis redis/np0005626459.internalapi.localdomain 1/0/216 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:19 np0005626461 haproxy[7]: 192.168.122.104:60394 [23/Feb/2026:08:14:19.480] redis redis/np0005626459.internalapi.localdomain 1/0/263 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:19 np0005626461 haproxy[7]: 192.168.122.104:60400 [23/Feb/2026:08:14:19.732] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/41/41/0 0/0
Feb 23 08:14:19 np0005626461 haproxy[7]: 192.168.122.104:60420 [23/Feb/2026:08:14:19.979] redis redis/np0005626459.internalapi.localdomain 1/0/14 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:19 np0005626461 haproxy[7]: 192.168.122.104:60414 [23/Feb/2026:08:14:19.759] redis redis/np0005626459.internalapi.localdomain 1/2/234 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:20 np0005626461 haproxy[7]: 192.168.122.104:60446 [23/Feb/2026:08:14:20.249] redis redis/np0005626459.internalapi.localdomain 1/0/16 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:20 np0005626461 haproxy[7]: 192.168.122.104:60436 [23/Feb/2026:08:14:20.020] redis redis/np0005626459.internalapi.localdomain 1/0/246 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:20 np0005626461 haproxy[7]: 192.168.122.104:60456 [23/Feb/2026:08:14:20.591] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:20 np0005626461 haproxy[7]: 192.168.122.104:60448 [23/Feb/2026:08:14:20.302] redis redis/np0005626459.internalapi.localdomain 1/0/301 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:23 np0005626461 haproxy[7]: 192.168.122.110:56854 [23/Feb/2026:08:14:23.425] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:23 np0005626461 haproxy[7]: 192.168.122.110:56840 [23/Feb/2026:08:14:23.170] redis redis/np0005626459.internalapi.localdomain 1/0/266 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:23 np0005626461 haproxy[7]: 192.168.122.110:56866 [23/Feb/2026:08:14:23.678] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:23 np0005626461 haproxy[7]: 192.168.122.110:56864 [23/Feb/2026:08:14:23.453] redis redis/np0005626459.internalapi.localdomain 1/0/236 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:23 np0005626461 haproxy[7]: 192.168.122.110:56882 [23/Feb/2026:08:14:23.978] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:23 np0005626461 haproxy[7]: 192.168.122.110:56868 [23/Feb/2026:08:14:23.722] redis redis/np0005626459.internalapi.localdomain 1/0/267 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:24 np0005626461 haproxy[7]: 192.168.122.110:56892 [23/Feb/2026:08:14:24.288] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:24 np0005626461 haproxy[7]: 192.168.122.110:56884 [23/Feb/2026:08:14:24.017] redis redis/np0005626459.internalapi.localdomain 1/0/282 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:25 np0005626461 haproxy[7]: 192.168.122.104:60468 [23/Feb/2026:08:14:25.636] redis redis/np0005626459.internalapi.localdomain 1/0/260 4429 -- 43/43/42/42/0 0/0
Feb 23 08:14:25 np0005626461 haproxy[7]: 192.168.122.104:60474 [23/Feb/2026:08:14:25.882] redis redis/np0005626459.internalapi.localdomain 1/1/14 10 -- 42/42/41/41/0 0/0
Feb 23 08:14:26 np0005626461 haproxy[7]: 192.168.122.104:60484 [23/Feb/2026:08:14:26.196] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:26 np0005626461 haproxy[7]: 192.168.122.104:60482 [23/Feb/2026:08:14:25.935] redis redis/np0005626459.internalapi.localdomain 1/0/272 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:26 np0005626461 haproxy[7]: 192.168.122.104:60500 [23/Feb/2026:08:14:26.513] redis redis/np0005626459.internalapi.localdomain 1/0/13 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:26 np0005626461 haproxy[7]: 192.168.122.104:60486 [23/Feb/2026:08:14:26.233] redis redis/np0005626459.internalapi.localdomain 1/0/294 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:26 np0005626461 haproxy[7]: 192.168.122.104:60508 [23/Feb/2026:08:14:26.549] redis redis/np0005626459.internalapi.localdomain 1/0/268 4430 -- 43/43/42/42/0 0/0
Feb 23 08:14:26 np0005626461 haproxy[7]: 192.168.122.104:48152 [23/Feb/2026:08:14:26.801] redis redis/np0005626459.internalapi.localdomain 1/0/15 10 -- 42/42/41/41/0 0/0
Feb 23 08:14:29 np0005626461 haproxy[7]: 192.168.122.110:54756 [23/Feb/2026:08:14:29.328] redis redis/np0005626459.internalapi.localdomain 1/0/255 4429 -- 43/43/42/42/0 0/0
Feb 23 08:14:29 np0005626461 haproxy[7]: 192.168.122.110:54770 [23/Feb/2026:08:14:29.573] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 42/42/41/41/0 0/0
Feb 23 08:14:29 np0005626461 haproxy[7]: 192.168.122.110:54780 [23/Feb/2026:08:14:29.879] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:29 np0005626461 haproxy[7]: 192.168.122.110:54772 [23/Feb/2026:08:14:29.617] redis redis/np0005626459.internalapi.localdomain 1/0/272 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:30 np0005626461 haproxy[7]: 192.168.122.110:54806 [23/Feb/2026:08:14:30.125] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:30 np0005626461 haproxy[7]: 192.168.122.110:54792 [23/Feb/2026:08:14:29.909] redis redis/np0005626459.internalapi.localdomain 1/0/227 4428 -- 42/42/41/41/0 0/0
Feb 23 08:14:30 np0005626461 haproxy[7]: 192.168.122.110:54816 [23/Feb/2026:08:14:30.391] redis redis/np0005626459.internalapi.localdomain 1/0/9 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:30 np0005626461 haproxy[7]: 192.168.122.110:54808 [23/Feb/2026:08:14:30.159] redis redis/np0005626459.internalapi.localdomain 1/0/242 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:32 np0005626461 haproxy[7]: 192.168.122.104:48174 [23/Feb/2026:08:14:32.116] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:32 np0005626461 haproxy[7]: 192.168.122.104:48160 [23/Feb/2026:08:14:31.853] redis redis/np0005626459.internalapi.localdomain 1/0/275 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:32 np0005626461 haproxy[7]: 192.168.122.104:48184 [23/Feb/2026:08:14:32.432] redis redis/np0005626459.internalapi.localdomain 1/2/13 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:32 np0005626461 haproxy[7]: 192.168.122.104:48182 [23/Feb/2026:08:14:32.155] redis redis/np0005626459.internalapi.localdomain 1/0/291 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:32 np0005626461 haproxy[7]: 192.168.122.104:48200 [23/Feb/2026:08:14:32.734] redis redis/np0005626459.internalapi.localdomain 1/0/8 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:32 np0005626461 haproxy[7]: 192.168.122.104:48186 [23/Feb/2026:08:14:32.467] redis redis/np0005626459.internalapi.localdomain 1/0/276 4431 -- 42/42/41/41/0 0/0
Feb 23 08:14:33 np0005626461 haproxy[7]: 192.168.122.104:48214 [23/Feb/2026:08:14:33.039] redis redis/np0005626459.internalapi.localdomain 1/0/8 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:33 np0005626461 haproxy[7]: 192.168.122.104:48204 [23/Feb/2026:08:14:32.760] redis redis/np0005626459.internalapi.localdomain 1/0/287 4431 -- 42/42/41/41/0 0/0
Feb 23 08:14:35 np0005626461 haproxy[7]: 192.168.122.110:41996 [23/Feb/2026:08:14:35.718] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:35 np0005626461 haproxy[7]: 192.168.122.110:41986 [23/Feb/2026:08:14:35.433] redis redis/np0005626459.internalapi.localdomain 1/0/296 4431 -- 43/43/41/41/0 0/0
Feb 23 08:14:35 np0005626461 haproxy[7]: 192.168.122.110:42004 [23/Feb/2026:08:14:35.970] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:35 np0005626461 haproxy[7]: 192.168.122.110:42002 [23/Feb/2026:08:14:35.750] redis redis/np0005626459.internalapi.localdomain 1/0/230 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:36 np0005626461 haproxy[7]: 192.168.122.110:42022 [23/Feb/2026:08:14:36.202] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:36 np0005626461 haproxy[7]: 192.168.122.110:42020 [23/Feb/2026:08:14:35.998] redis redis/np0005626459.internalapi.localdomain 1/0/214 4431 -- 42/42/41/41/0 0/0
Feb 23 08:14:36 np0005626461 haproxy[7]: 192.168.122.110:42050 [23/Feb/2026:08:14:36.439] redis redis/np0005626459.internalapi.localdomain 1/0/14 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:36 np0005626461 haproxy[7]: 192.168.122.110:42034 [23/Feb/2026:08:14:36.235] redis redis/np0005626459.internalapi.localdomain 1/0/219 4432 -- 42/42/41/41/0 0/0
Feb 23 08:14:38 np0005626461 haproxy[7]: 192.168.122.104:41418 [23/Feb/2026:08:14:38.086] redis redis/np0005626459.internalapi.localdomain 1/0/303 4431 -- 43/43/42/42/0 0/0
Feb 23 08:14:38 np0005626461 haproxy[7]: 192.168.122.104:41434 [23/Feb/2026:08:14:38.376] redis redis/np0005626459.internalapi.localdomain 1/0/13 10 -- 42/42/41/41/0 0/0
Feb 23 08:14:38 np0005626461 haproxy[7]: 192.168.122.104:41436 [23/Feb/2026:08:14:38.401] redis redis/np0005626459.internalapi.localdomain 1/0/241 4431 -- 43/43/42/42/0 0/0
Feb 23 08:14:38 np0005626461 haproxy[7]: 192.168.122.104:41440 [23/Feb/2026:08:14:38.627] redis redis/np0005626459.internalapi.localdomain 1/0/15 10 -- 43/43/41/41/0 0/0
Feb 23 08:14:38 np0005626461 haproxy[7]: 192.168.122.104:41454 [23/Feb/2026:08:14:38.935] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:38 np0005626461 haproxy[7]: 192.168.122.104:41448 [23/Feb/2026:08:14:38.668] redis redis/np0005626459.internalapi.localdomain 1/0/278 4431 -- 42/42/41/41/0 0/0
Feb 23 08:14:39 np0005626461 haproxy[7]: 192.168.122.104:41470 [23/Feb/2026:08:14:39.189] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:39 np0005626461 haproxy[7]: 192.168.122.104:41464 [23/Feb/2026:08:14:38.963] redis redis/np0005626459.internalapi.localdomain 1/0/236 4432 -- 42/42/41/41/0 0/0
Feb 23 08:14:41 np0005626461 haproxy[7]: 192.168.122.110:42058 [23/Feb/2026:08:14:41.483] redis redis/np0005626459.internalapi.localdomain 1/0/252 4429 -- 43/43/42/42/0 0/0
Feb 23 08:14:41 np0005626461 haproxy[7]: 192.168.122.110:42060 [23/Feb/2026:08:14:41.725] redis redis/np0005626459.internalapi.localdomain 1/0/14 10 -- 42/42/41/41/0 0/0
Feb 23 08:14:42 np0005626461 haproxy[7]: 192.168.122.110:42066 [23/Feb/2026:08:14:41.765] redis redis/np0005626459.internalapi.localdomain 1/0/276 4428 -- 43/43/42/42/0 0/0
Feb 23 08:14:42 np0005626461 haproxy[7]: 192.168.122.110:42082 [23/Feb/2026:08:14:42.031] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 42/42/41/41/0 0/0
Feb 23 08:14:42 np0005626461 haproxy[7]: 192.168.122.110:42102 [23/Feb/2026:08:14:42.319] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:42 np0005626461 haproxy[7]: 192.168.122.110:42096 [23/Feb/2026:08:14:42.069] redis redis/np0005626459.internalapi.localdomain 1/0/261 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:42 np0005626461 haproxy[7]: 192.168.122.110:42114 [23/Feb/2026:08:14:42.614] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:42 np0005626461 haproxy[7]: 192.168.122.110:42112 [23/Feb/2026:08:14:42.357] redis redis/np0005626459.internalapi.localdomain 1/0/268 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:44 np0005626461 haproxy[7]: 192.168.122.104:41482 [23/Feb/2026:08:14:44.236] redis redis/np0005626459.internalapi.localdomain 1/0/281 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:44 np0005626461 haproxy[7]: 192.168.122.104:41492 [23/Feb/2026:08:14:44.506] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/41/41/0 0/0
Feb 23 08:14:44 np0005626461 haproxy[7]: 192.168.122.104:41516 [23/Feb/2026:08:14:44.841] redis redis/np0005626459.internalapi.localdomain 1/0/8 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:44 np0005626461 haproxy[7]: 192.168.122.104:41504 [23/Feb/2026:08:14:44.545] redis redis/np0005626459.internalapi.localdomain 1/0/303 4429 -- 43/43/41/41/0 0/0
Feb 23 08:14:45 np0005626461 haproxy[7]: 192.168.122.104:41524 [23/Feb/2026:08:14:45.100] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:45 np0005626461 haproxy[7]: 192.168.122.104:41522 [23/Feb/2026:08:14:44.871] redis redis/np0005626459.internalapi.localdomain 1/0/242 4429 -- 42/42/41/41/0 0/0
Feb 23 08:14:45 np0005626461 haproxy[7]: 192.168.122.104:41532 [23/Feb/2026:08:14:45.131] redis redis/np0005626459.internalapi.localdomain 1/1/236 4430 -- 43/43/42/42/0 0/0
Feb 23 08:14:45 np0005626461 haproxy[7]: 192.168.122.104:41542 [23/Feb/2026:08:14:45.355] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 42/42/41/41/0 0/0
Feb 23 08:14:47 np0005626461 haproxy[7]: 192.168.122.110:40614 [23/Feb/2026:08:14:47.657] redis redis/np0005626459.internalapi.localdomain 1/0/264 4430 -- 43/43/42/42/0 0/0
Feb 23 08:14:47 np0005626461 haproxy[7]: 192.168.122.110:40630 [23/Feb/2026:08:14:47.912] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 42/42/41/41/0 0/0
Feb 23 08:14:48 np0005626461 haproxy[7]: 192.168.122.110:40632 [23/Feb/2026:08:14:47.939] redis redis/np0005626459.internalapi.localdomain 1/0/220 4430 -- 43/43/41/41/0 0/0
Feb 23 08:14:48 np0005626461 haproxy[7]: 192.168.122.110:40642 [23/Feb/2026:08:14:48.149] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/41/41/0 0/0
Feb 23 08:14:48 np0005626461 haproxy[7]: 192.168.122.110:40660 [23/Feb/2026:08:14:48.393] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:48 np0005626461 haproxy[7]: 192.168.122.110:40650 [23/Feb/2026:08:14:48.179] redis redis/np0005626459.internalapi.localdomain 1/0/227 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:48 np0005626461 haproxy[7]: 192.168.122.110:40670 [23/Feb/2026:08:14:48.638] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:48 np0005626461 haproxy[7]: 192.168.122.110:40662 [23/Feb/2026:08:14:48.423] redis redis/np0005626459.internalapi.localdomain 1/0/225 4431 -- 42/42/41/41/0 0/0
Feb 23 08:14:50 np0005626461 haproxy[7]: 192.168.122.104:60928 [23/Feb/2026:08:14:50.646] redis redis/np0005626459.internalapi.localdomain 1/0/17 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:50 np0005626461 haproxy[7]: 192.168.122.104:60914 [23/Feb/2026:08:14:50.405] redis redis/np0005626459.internalapi.localdomain 1/0/258 4430 -- 43/43/41/41/0 0/0
Feb 23 08:14:50 np0005626461 haproxy[7]: 192.168.122.104:60942 [23/Feb/2026:08:14:50.975] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:50 np0005626461 haproxy[7]: 192.168.122.104:60938 [23/Feb/2026:08:14:50.705] redis redis/np0005626459.internalapi.localdomain 1/0/280 4430 -- 43/43/41/41/0 0/0
Feb 23 08:14:51 np0005626461 haproxy[7]: 192.168.122.104:60952 [23/Feb/2026:08:14:51.225] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:51 np0005626461 haproxy[7]: 192.168.122.104:60946 [23/Feb/2026:08:14:51.004] redis redis/np0005626459.internalapi.localdomain 1/0/232 4431 -- 42/42/41/41/0 0/0
Feb 23 08:14:51 np0005626461 haproxy[7]: 192.168.122.104:60978 [23/Feb/2026:08:14:51.484] redis redis/np0005626459.internalapi.localdomain 1/0/14 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:51 np0005626461 haproxy[7]: 192.168.122.104:60966 [23/Feb/2026:08:14:51.257] redis redis/np0005626459.internalapi.localdomain 1/0/243 4431 -- 42/42/41/41/0 0/0
Feb 23 08:14:53 np0005626461 haproxy[7]: 192.168.122.110:40680 [23/Feb/2026:08:14:53.682] redis redis/np0005626459.internalapi.localdomain 1/0/262 4430 -- 43/43/41/41/0 0/0
Feb 23 08:14:53 np0005626461 haproxy[7]: 192.168.122.110:40694 [23/Feb/2026:08:14:53.933] redis redis/np0005626459.internalapi.localdomain 1/1/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:54 np0005626461 haproxy[7]: 192.168.122.110:40696 [23/Feb/2026:08:14:53.972] redis redis/np0005626459.internalapi.localdomain 1/0/249 4430 -- 43/43/41/41/0 0/0
Feb 23 08:14:54 np0005626461 haproxy[7]: 192.168.122.110:40708 [23/Feb/2026:08:14:54.209] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 43/43/41/41/0 0/0
Feb 23 08:14:54 np0005626461 haproxy[7]: 192.168.122.110:40732 [23/Feb/2026:08:14:54.452] redis redis/np0005626459.internalapi.localdomain 1/0/13 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:54 np0005626461 haproxy[7]: 192.168.122.110:40722 [23/Feb/2026:08:14:54.241] redis redis/np0005626459.internalapi.localdomain 1/0/225 4430 -- 42/42/41/41/0 0/0
Feb 23 08:14:54 np0005626461 haproxy[7]: 192.168.122.110:43776 [23/Feb/2026:08:14:54.748] redis redis/np0005626459.internalapi.localdomain 1/0/9 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:54 np0005626461 haproxy[7]: 192.168.122.110:40734 [23/Feb/2026:08:14:54.481] redis redis/np0005626459.internalapi.localdomain 1/0/276 4431 -- 42/42/41/41/0 0/0
Feb 23 08:14:56 np0005626461 haproxy[7]: 192.168.122.104:39390 [23/Feb/2026:08:14:56.751] redis redis/np0005626459.internalapi.localdomain 1/0/13 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:56 np0005626461 haproxy[7]: 192.168.122.104:60986 [23/Feb/2026:08:14:56.522] redis redis/np0005626459.internalapi.localdomain 1/0/242 4430 -- 43/43/41/41/0 0/0
Feb 23 08:14:57 np0005626461 haproxy[7]: 192.168.122.104:39402 [23/Feb/2026:08:14:56.794] redis redis/np0005626459.internalapi.localdomain 1/0/261 4430 -- 43/43/41/41/0 0/0
Feb 23 08:14:57 np0005626461 haproxy[7]: 192.168.122.104:39404 [23/Feb/2026:08:14:57.044] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/41/41/0 0/0
Feb 23 08:14:57 np0005626461 haproxy[7]: 192.168.122.104:39422 [23/Feb/2026:08:14:57.291] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:57 np0005626461 haproxy[7]: 192.168.122.104:39414 [23/Feb/2026:08:14:57.079] redis redis/np0005626459.internalapi.localdomain 1/0/223 4431 -- 42/42/41/41/0 0/0
Feb 23 08:14:57 np0005626461 haproxy[7]: 192.168.122.104:39446 [23/Feb/2026:08:14:57.587] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:14:57 np0005626461 haproxy[7]: 192.168.122.104:39432 [23/Feb/2026:08:14:57.321] redis redis/np0005626459.internalapi.localdomain 1/0/277 4431 -- 42/42/41/41/0 0/0
Feb 23 08:15:00 np0005626461 haproxy[7]: 192.168.122.110:43802 [23/Feb/2026:08:15:00.029] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:00 np0005626461 haproxy[7]: 192.168.122.110:43790 [23/Feb/2026:08:14:59.797] redis redis/np0005626459.internalapi.localdomain 1/0/243 4430 -- 43/43/41/41/0 0/0
Feb 23 08:15:00 np0005626461 haproxy[7]: 192.168.122.110:43830 [23/Feb/2026:08:15:00.352] redis redis/np0005626459.internalapi.localdomain 1/0/8 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:00 np0005626461 haproxy[7]: 192.168.122.110:43818 [23/Feb/2026:08:15:00.069] redis redis/np0005626459.internalapi.localdomain 1/0/292 4430 -- 43/43/41/41/0 0/0
Feb 23 08:15:00 np0005626461 haproxy[7]: 192.168.122.110:43844 [23/Feb/2026:08:15:00.598] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:00 np0005626461 haproxy[7]: 192.168.122.110:43840 [23/Feb/2026:08:15:00.377] redis redis/np0005626459.internalapi.localdomain 1/0/231 4432 -- 42/42/41/41/0 0/0
Feb 23 08:15:00 np0005626461 haproxy[7]: 192.168.122.110:43872 [23/Feb/2026:08:15:00.848] redis redis/np0005626459.internalapi.localdomain 1/1/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:00 np0005626461 haproxy[7]: 192.168.122.110:43856 [23/Feb/2026:08:15:00.626] redis redis/np0005626459.internalapi.localdomain 1/0/232 4432 -- 42/42/41/41/0 0/0
Feb 23 08:15:02 np0005626461 haproxy[7]: 192.168.122.104:39454 [23/Feb/2026:08:15:02.876] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:02 np0005626461 haproxy[7]: 192.168.122.104:39452 [23/Feb/2026:08:15:02.630] redis redis/np0005626459.internalapi.localdomain 1/0/257 4432 -- 43/43/41/41/0 0/0
Feb 23 08:15:03 np0005626461 haproxy[7]: 192.168.122.104:39484 [23/Feb/2026:08:15:03.217] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:03 np0005626461 haproxy[7]: 192.168.122.104:39470 [23/Feb/2026:08:15:02.917] redis redis/np0005626459.internalapi.localdomain 1/0/311 4431 -- 43/43/41/41/0 0/0
Feb 23 08:15:03 np0005626461 haproxy[7]: 192.168.122.104:39498 [23/Feb/2026:08:15:03.254] redis redis/np0005626459.internalapi.localdomain 1/0/256 4432 -- 43/43/42/42/0 0/0
Feb 23 08:15:03 np0005626461 haproxy[7]: 192.168.122.104:39508 [23/Feb/2026:08:15:03.501] redis redis/np0005626459.internalapi.localdomain 1/0/9 10 -- 42/42/41/41/0 0/0
Feb 23 08:15:03 np0005626461 haproxy[7]: 192.168.122.104:39522 [23/Feb/2026:08:15:03.758] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:03 np0005626461 haproxy[7]: 192.168.122.104:39510 [23/Feb/2026:08:15:03.526] redis redis/np0005626459.internalapi.localdomain 1/0/244 4433 -- 42/42/41/41/0 0/0
Feb 23 08:15:06 np0005626461 haproxy[7]: 192.168.122.110:34304 [23/Feb/2026:08:15:06.141] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:06 np0005626461 haproxy[7]: 192.168.122.110:34300 [23/Feb/2026:08:15:05.896] redis redis/np0005626459.internalapi.localdomain 1/0/257 4431 -- 42/42/41/41/0 0/0
Feb 23 08:15:06 np0005626461 haproxy[7]: 192.168.122.110:34318 [23/Feb/2026:08:15:06.425] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/41/41/0 0/0
Feb 23 08:15:06 np0005626461 haproxy[7]: 192.168.122.110:34312 [23/Feb/2026:08:15:06.177] redis redis/np0005626459.internalapi.localdomain 1/0/259 4433 -- 43/43/42/42/0 0/0
Feb 23 08:15:06 np0005626461 haproxy[7]: 192.168.122.110:34334 [23/Feb/2026:08:15:06.734] redis redis/np0005626459.internalapi.localdomain 1/0/7 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:06 np0005626461 haproxy[7]: 192.168.122.110:34330 [23/Feb/2026:08:15:06.465] redis redis/np0005626459.internalapi.localdomain 1/1/276 4434 -- 42/42/41/41/0 0/0
Feb 23 08:15:07 np0005626461 haproxy[7]: 192.168.122.110:34340 [23/Feb/2026:08:15:06.761] redis redis/np0005626459.internalapi.localdomain 1/0/269 4434 -- 43/43/42/42/0 0/0
Feb 23 08:15:07 np0005626461 haproxy[7]: 192.168.122.110:34352 [23/Feb/2026:08:15:07.020] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 42/42/41/41/0 0/0
Feb 23 08:15:09 np0005626461 haproxy[7]: 192.168.122.104:52642 [23/Feb/2026:08:15:09.059] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:09 np0005626461 haproxy[7]: 192.168.122.104:52626 [23/Feb/2026:08:15:08.806] redis redis/np0005626459.internalapi.localdomain 1/0/264 4433 -- 43/43/41/41/0 0/0
Feb 23 08:15:09 np0005626461 haproxy[7]: 192.168.122.104:52654 [23/Feb/2026:08:15:09.099] redis redis/np0005626459.internalapi.localdomain 1/0/253 4433 -- 43/43/41/41/0 0/0
Feb 23 08:15:09 np0005626461 haproxy[7]: 192.168.122.104:52656 [23/Feb/2026:08:15:09.340] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/41/41/0 0/0
Feb 23 08:15:09 np0005626461 haproxy[7]: 192.168.122.104:52678 [23/Feb/2026:08:15:09.638] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:09 np0005626461 haproxy[7]: 192.168.122.104:52664 [23/Feb/2026:08:15:09.383] redis redis/np0005626459.internalapi.localdomain 1/0/267 4434 -- 42/42/41/41/0 0/0
Feb 23 08:15:09 np0005626461 haproxy[7]: 192.168.122.104:52696 [23/Feb/2026:08:15:09.912] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:09 np0005626461 haproxy[7]: 192.168.122.104:52684 [23/Feb/2026:08:15:09.675] redis redis/np0005626459.internalapi.localdomain 1/0/248 4434 -- 42/42/41/41/0 0/0
Feb 23 08:15:12 np0005626461 haproxy[7]: 192.168.122.110:34368 [23/Feb/2026:08:15:12.061] redis redis/np0005626459.internalapi.localdomain 1/0/258 4433 -- 43/43/42/42/0 0/0
Feb 23 08:15:12 np0005626461 haproxy[7]: 192.168.122.110:34380 [23/Feb/2026:08:15:12.306] redis redis/np0005626459.internalapi.localdomain 1/0/13 10 -- 42/42/41/41/0 0/0
Feb 23 08:15:12 np0005626461 haproxy[7]: 192.168.122.110:34394 [23/Feb/2026:08:15:12.349] redis redis/np0005626459.internalapi.localdomain 1/0/282 4433 -- 43/43/42/42/0 0/0
Feb 23 08:15:12 np0005626461 haproxy[7]: 192.168.122.110:34402 [23/Feb/2026:08:15:12.622] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 42/42/41/41/0 0/0
Feb 23 08:15:12 np0005626461 haproxy[7]: 192.168.122.110:34408 [23/Feb/2026:08:15:12.975] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:12 np0005626461 haproxy[7]: 192.168.122.110:34404 [23/Feb/2026:08:15:12.663] redis redis/np0005626459.internalapi.localdomain 1/0/322 4434 -- 42/42/41/41/0 0/0
Feb 23 08:15:13 np0005626461 haproxy[7]: 192.168.122.110:34424 [23/Feb/2026:08:15:13.219] redis redis/np0005626459.internalapi.localdomain 1/0/13 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:13 np0005626461 haproxy[7]: 192.168.122.110:34420 [23/Feb/2026:08:15:13.004] redis redis/np0005626459.internalapi.localdomain 1/0/229 4434 -- 42/42/41/41/0 0/0
Feb 23 08:15:15 np0005626461 haproxy[7]: 192.168.122.104:52706 [23/Feb/2026:08:15:15.199] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:15 np0005626461 haproxy[7]: 192.168.122.104:52698 [23/Feb/2026:08:15:14.953] redis redis/np0005626459.internalapi.localdomain 1/0/259 4433 -- 42/42/41/41/0 0/0
Feb 23 08:15:15 np0005626461 haproxy[7]: 192.168.122.104:52730 [23/Feb/2026:08:15:15.513] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:15 np0005626461 haproxy[7]: 192.168.122.104:52714 [23/Feb/2026:08:15:15.237] redis redis/np0005626459.internalapi.localdomain 1/0/288 4433 -- 42/42/41/41/0 0/0
Feb 23 08:15:15 np0005626461 haproxy[7]: 192.168.122.104:52748 [23/Feb/2026:08:15:15.799] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:15 np0005626461 haproxy[7]: 192.168.122.104:52744 [23/Feb/2026:08:15:15.551] redis redis/np0005626459.internalapi.localdomain 1/0/259 4434 -- 42/42/41/41/0 0/0
Feb 23 08:15:16 np0005626461 haproxy[7]: 192.168.122.104:52760 [23/Feb/2026:08:15:16.118] redis redis/np0005626459.internalapi.localdomain 1/0/14 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:16 np0005626461 haproxy[7]: 192.168.122.104:52754 [23/Feb/2026:08:15:15.838] redis redis/np0005626459.internalapi.localdomain 1/0/294 4433 -- 42/42/41/41/0 0/0
Feb 23 08:15:18 np0005626461 haproxy[7]: 192.168.122.110:33028 [23/Feb/2026:08:15:18.516] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:18 np0005626461 haproxy[7]: 192.168.122.110:33020 [23/Feb/2026:08:15:18.267] redis redis/np0005626459.internalapi.localdomain 1/0/260 4433 -- 43/43/41/41/0 0/0
Feb 23 08:15:18 np0005626461 haproxy[7]: 192.168.122.110:33032 [23/Feb/2026:08:15:18.554] redis redis/np0005626459.internalapi.localdomain 1/0/263 4433 -- 43/43/42/42/0 0/0
Feb 23 08:15:18 np0005626461 haproxy[7]: 192.168.122.110:33036 [23/Feb/2026:08:15:18.806] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 42/42/41/41/0 0/0
Feb 23 08:15:19 np0005626461 haproxy[7]: 192.168.122.110:33060 [23/Feb/2026:08:15:19.127] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:19 np0005626461 haproxy[7]: 192.168.122.110:33050 [23/Feb/2026:08:15:18.847] redis redis/np0005626459.internalapi.localdomain 1/0/290 4432 -- 42/42/41/41/0 0/0
Feb 23 08:15:19 np0005626461 haproxy[7]: 192.168.122.110:33074 [23/Feb/2026:08:15:19.402] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:19 np0005626461 haproxy[7]: 192.168.122.110:33064 [23/Feb/2026:08:15:19.166] redis redis/np0005626459.internalapi.localdomain 1/0/248 4434 -- 42/42/41/41/0 0/0
Feb 23 08:15:21 np0005626461 haproxy[7]: 192.168.122.104:41486 [23/Feb/2026:08:15:21.432] redis redis/np0005626459.internalapi.localdomain 1/0/10 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:21 np0005626461 haproxy[7]: 192.168.122.104:41484 [23/Feb/2026:08:15:21.172] redis redis/np0005626459.internalapi.localdomain 1/0/272 4433 -- 43/43/41/41/0 0/0
Feb 23 08:15:21 np0005626461 haproxy[7]: 192.168.122.104:41496 [23/Feb/2026:08:15:21.473] redis redis/np0005626459.internalapi.localdomain 1/0/264 4433 -- 43/43/41/41/0 0/0
Feb 23 08:15:21 np0005626461 haproxy[7]: 192.168.122.104:41512 [23/Feb/2026:08:15:21.725] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 43/43/41/41/0 0/0
Feb 23 08:15:22 np0005626461 haproxy[7]: 192.168.122.104:41534 [23/Feb/2026:08:15:22.020] redis redis/np0005626459.internalapi.localdomain 1/0/11 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:22 np0005626461 haproxy[7]: 192.168.122.104:41520 [23/Feb/2026:08:15:21.767] redis redis/np0005626459.internalapi.localdomain 1/0/263 4433 -- 42/42/41/41/0 0/0
Feb 23 08:15:22 np0005626461 haproxy[7]: 192.168.122.104:41558 [23/Feb/2026:08:15:22.308] redis redis/np0005626459.internalapi.localdomain 1/0/12 10 -- 43/43/42/42/0 0/0
Feb 23 08:15:22 np0005626461 haproxy[7]: 192.168.122.104:41546 [23/Feb/2026:08:15:22.058] redis redis/np0005626459.internalapi.localdomain 1/0/262 4434 -- 42/42/41/41/0 0/0
Feb 23 08:15:22 np0005626461 haproxy[7]: 192.168.122.103:60424 [23/Feb/2026:08:15:22.849] redis redis/np0005626459.internalapi.localdomain 1/0/24 14 -- 42/42/41/41/0 0/0
Feb 23 08:15:27 np0005626461 haproxy[7]: Server gnocchi/np0005626459.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.
Feb 23 08:27:10 np0005626461 haproxy[7]: Server aodh/np0005626459.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 501ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Feb 23 08:27:14 np0005626461 haproxy[7]: Server aodh/np0005626460.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.
Feb 23 08:27:15 np0005626461 haproxy[7]: 192.168.122.103:38150 [23/Feb/2026:08:09:44.294] redis redis/np0005626459.internalapi.localdomain 1/0/1050232 22382 -- 84/84/83/83/0 0/0
Feb 23 08:27:15 np0005626461 haproxy[7]: 192.168.122.103:50376 [23/Feb/2026:08:17:44.322] redis redis/np0005626459.internalapi.localdomain 1/0/570279 10 -- 84/84/82/82/0 0/0
Feb 23 08:27:15 np0005626461 haproxy[7]: 192.168.122.103:55318 [23/Feb/2026:08:16:44.292] redis redis/np0005626459.internalapi.localdomain 1/0/630315 10702 -- 82/82/81/81/0 0/0
Feb 23 08:27:15 np0005626461 haproxy[7]: 192.168.122.103:38128 [23/Feb/2026:08:09:44.227] redis redis/np0005626459.internalapi.localdomain 1/0/1050304 11720 -- 81/81/80/80/0 0/0
Feb 23 08:27:15 np0005626461 haproxy[7]: 192.168.122.103:38114 [23/Feb/2026:08:09:44.157] redis redis/np0005626459.internalapi.localdomain 1/0/1050375 22428 -- 80/80/79/79/0 0/0
Feb 23 08:27:15 np0005626461 haproxy[7]: 192.168.122.103:50374 [23/Feb/2026:08:17:44.321] redis redis/np0005626459.internalapi.localdomain 1/0/570289 10425 -- 79/79/78/78/0 0/0
Feb 23 08:27:15 np0005626461 haproxy[7]: 192.168.122.103:38144 [23/Feb/2026:08:09:44.274] redis redis/np0005626459.internalapi.localdomain 1/0/1050261 12031 -- 78/78/77/77/0 0/0
Feb 23 08:27:16 np0005626461 haproxy[7]: 192.168.122.104:50096 [23/Feb/2026:08:09:59.446] redis redis/np0005626459.internalapi.localdomain 1/0/1036334 22306 -- 77/77/76/76/0 0/0
Feb 23 08:27:16 np0005626461 haproxy[7]: 192.168.122.104:50062 [23/Feb/2026:08:09:59.220] redis redis/np0005626459.internalapi.localdomain 1/0/1036563 22331 -- 76/76/75/75/0 0/0
Feb 23 08:27:16 np0005626461 haproxy[7]: 192.168.122.104:50102 [23/Feb/2026:08:09:59.456] redis redis/np0005626459.internalapi.localdomain 1/0/1036330 22391 -- 75/75/74/74/0 0/0
Feb 23 08:27:16 np0005626461 haproxy[7]: 192.168.122.104:50052 [23/Feb/2026:08:09:59.126] redis redis/np0005626459.internalapi.localdomain 1/0/1036666 22385 -- 74/74/73/73/0 0/0
Feb 23 08:27:16 np0005626461 haproxy[7]: Server aodh/np0005626461.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.
Feb 23 08:27:16 np0005626461 haproxy[7]: proxy aodh has no server available!
Feb 23 08:27:17 np0005626461 haproxy[7]: 192.168.122.110:45776 [23/Feb/2026:08:10:00.916] redis redis/np0005626459.internalapi.localdomain 1/0/1036116 22324 -- 73/73/72/72/0 0/0
Feb 23 08:27:17 np0005626461 haproxy[7]: 192.168.122.110:45790 [23/Feb/2026:08:10:01.136] redis redis/np0005626459.internalapi.localdomain 1/0/1035900 22355 -- 72/72/71/71/0 0/0
Feb 23 08:27:17 np0005626461 haproxy[7]: 192.168.122.110:45770 [23/Feb/2026:08:10:00.886] redis redis/np0005626459.internalapi.localdomain 1/7/1036153 22328 -- 71/71/70/70/0 0/0
Feb 23 08:27:17 np0005626461 haproxy[7]: 192.168.122.110:45778 [23/Feb/2026:08:10:01.119] redis redis/np0005626459.internalapi.localdomain 1/2/1035921 22349 -- 70/70/69/69/0 0/0
Feb 23 08:29:17 np0005626461 haproxy[7]: 192.168.122.103:38152 [23/Feb/2026:08:09:44.544] redis redis/np0005626459.internalapi.localdomain 1/0/1169633 5948 -- 69/69/68/68/0 0/0
Feb 23 08:29:20 np0005626461 haproxy[7]: 192.168.122.104:50084 [23/Feb/2026:08:09:59.285] redis redis/np0005626459.internalapi.localdomain 1/0/1157254 1689 -- 68/68/67/67/0 0/0
Feb 23 08:29:20 np0005626461 haproxy[7]: 192.168.122.104:50074 [23/Feb/2026:08:09:59.279] redis redis/np0005626459.internalapi.localdomain 1/0/1157260 4419 -- 67/67/66/66/0 0/0
Feb 23 08:29:21 np0005626461 haproxy[7]: 192.168.122.110:45798 [23/Feb/2026:08:10:02.268] redis redis/np0005626459.internalapi.localdomain 1/0/1155769 1858 -- 66/66/65/65/0 0/0
Feb 23 08:29:21 np0005626461 haproxy[7]: 192.168.122.110:45792 [23/Feb/2026:08:10:02.260] redis redis/np0005626459.internalapi.localdomain 1/0/1155778 4425 -- 65/65/64/64/0 0/0
Feb 23 08:30:15 np0005626461 haproxy[7]: Server horizon/np0005626459.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 237ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Feb 23 08:30:20 np0005626461 haproxy[7]: Server horizon/np0005626460.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.
Feb 23 08:30:24 np0005626461 haproxy[7]: Server horizon/np0005626461.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.
Feb 23 08:30:24 np0005626461 haproxy[7]: proxy horizon has no server available!
Feb 23 08:30:32 np0005626461 haproxy[7]: Server keystone_public/np0005626459.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.
Feb 23 08:30:32 np0005626461 haproxy[7]: Server keystone_admin/np0005626459.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.
Feb 23 08:30:35 np0005626461 haproxy[7]: Server keystone_public/np0005626460.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.
Feb 23 08:30:35 np0005626461 haproxy[7]: Server keystone_admin/np0005626460.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.
Feb 23 08:30:40 np0005626461 haproxy[7]: Server keystone_public/np0005626461.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.
Feb 23 08:30:40 np0005626461 haproxy[7]: proxy keystone_public has no server available!
Feb 23 08:30:40 np0005626461 haproxy[7]: Server keystone_admin/np0005626461.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.
Feb 23 08:30:40 np0005626461 haproxy[7]: proxy keystone_admin has no server available!
Feb 23 08:30:47 np0005626461 haproxy[7]: Server cinder/np0005626459.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.
Feb 23 08:30:51 np0005626461 haproxy[7]: Server cinder/np0005626460.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.
Feb 23 08:30:55 np0005626461 haproxy[7]: Server cinder/np0005626461.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.
Feb 23 08:30:55 np0005626461 haproxy[7]: proxy cinder has no server available!
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:57584 [23/Feb/2026:08:24:42.828] redis redis/np0005626459.internalapi.localdomain 1/0/512876 46 -- 66/66/65/65/0 0/0
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:60520 [23/Feb/2026:08:15:26.171] redis redis/np0005626459.internalapi.localdomain 1/0/1069319 4797 -- 66/66/64/64/0 0/0
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:57572 [23/Feb/2026:08:24:42.744] redis redis/np0005626459.internalapi.localdomain 1/0/512962 38 -- 66/66/63/63/0 0/0
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:57590 [23/Feb/2026:08:24:42.851] redis redis/np0005626459.internalapi.localdomain 1/0/512855 30 -- 63/63/61/61/0 0/0
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:60548 [23/Feb/2026:08:15:29.302] redis redis/np0005626459.internalapi.localdomain 1/0/1066187 4796 -- 65/65/62/62/0 0/0
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:60528 [23/Feb/2026:08:15:28.739] redis redis/np0005626459.internalapi.localdomain 1/0/1066751 4796 -- 62/62/60/60/0 0/0
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:60514 [23/Feb/2026:08:15:25.534] redis redis/np0005626459.internalapi.localdomain 1/0/1069956 4794 -- 60/60/59/59/0 0/0
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:60488 [23/Feb/2026:08:15:25.466] redis redis/np0005626459.internalapi.localdomain 1/0/1070023 4793 -- 60/60/58/58/0 0/0
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:60534 [23/Feb/2026:08:15:29.004] redis redis/np0005626459.internalapi.localdomain 1/0/1066487 4796 -- 58/58/57/57/0 0/0
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:57578 [23/Feb/2026:08:24:42.813] redis redis/np0005626459.internalapi.localdomain 1/0/512894 30 -- 57/57/56/56/0 0/0
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:60502 [23/Feb/2026:08:15:25.512] redis redis/np0005626459.internalapi.localdomain 1/0/1069980 4794 -- 56/56/55/55/0 0/0
Feb 23 08:33:20 np0005626461 haproxy[7]: 192.168.122.103:60554 [23/Feb/2026:08:15:29.519] redis redis/np0005626459.internalapi.localdomain 1/0/1065973 4796 -- 55/55/54/54/0 0/0
Feb 23 08:33:21 np0005626461 haproxy[7]: Server glance_api/np0005626459.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.
Feb 23 08:33:24 np0005626461 haproxy[7]: Server glance_api/np0005626460.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.
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:54218 [23/Feb/2026:08:23:13.434] redis redis/np0005626459.internalapi.localdomain 1/0/606180 78 -- 54/54/53/53/0 0/0
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:38560 [23/Feb/2026:08:15:28.048] redis redis/np0005626459.internalapi.localdomain 1/0/1071516 4797 -- 54/54/52/52/0 0/0
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:58224 [23/Feb/2026:08:13:57.337] redis redis/np0005626459.internalapi.localdomain 1/0/1162214 4814 -- 54/54/51/51/0 0/0
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:38522 [23/Feb/2026:08:15:27.049] redis redis/np0005626459.internalapi.localdomain 1/0/1072516 4796 -- 51/51/50/50/0 0/0
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:58212 [23/Feb/2026:08:13:57.317] redis redis/np0005626459.internalapi.localdomain 1/0/1162235 4814 -- 50/50/49/49/0 0/0
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:47058 [23/Feb/2026:08:24:42.855] redis redis/np0005626459.internalapi.localdomain 1/0/516925 38 -- 49/49/48/48/0 0/0
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:33374 [23/Feb/2026:08:21:59.875] redis redis/np0005626459.internalapi.localdomain 1/0/679713 46 -- 48/48/47/47/0 0/0
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:38538 [23/Feb/2026:08:15:27.431] redis redis/np0005626459.internalapi.localdomain 1/1/1072134 4796 -- 48/48/46/46/0 0/0
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:58200 [23/Feb/2026:08:13:57.219] redis redis/np0005626459.internalapi.localdomain 1/0/1162336 4814 -- 46/46/45/45/0 0/0
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:33364 [23/Feb/2026:08:13:55.647] redis redis/np0005626459.internalapi.localdomain 1/0/1163909 4815 -- 45/45/44/44/0 0/0
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:59372 [23/Feb/2026:08:23:03.575] redis redis/np0005626459.internalapi.localdomain 1/0/616042 38 -- 44/44/43/43/0 0/0
Feb 23 08:33:24 np0005626461 haproxy[7]: 192.168.122.104:38554 [23/Feb/2026:08:15:27.837] redis redis/np0005626459.internalapi.localdomain 1/0/1071731 4795 -- 43/43/42/42/0 0/0
Feb 23 08:33:25 np0005626461 haproxy[7]: Server glance_api/np0005626461.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.
Feb 23 08:33:25 np0005626461 haproxy[7]: proxy glance_api has no server available!
Feb 23 08:33:28 np0005626461 haproxy[7]: Server gnocchi/np0005626459.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.
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:46206 [23/Feb/2026:08:13:54.323] redis redis/np0005626459.internalapi.localdomain 1/0/1169341 4820 -- 42/42/41/41/0 0/0
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:45416 [23/Feb/2026:08:15:27.554] redis redis/np0005626459.internalapi.localdomain 1/0/1076121 4796 -- 42/42/40/40/0 0/0
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:51638 [23/Feb/2026:08:29:42.609] redis redis/np0005626459.internalapi.localdomain 1/0/225086 22 -- 40/40/39/39/0 0/0
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:50182 [23/Feb/2026:08:13:55.217] redis redis/np0005626459.internalapi.localdomain 1/0/1168449 4819 -- 39/39/38/38/0 0/0
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:49708 [23/Feb/2026:08:22:00.330] redis redis/np0005626459.internalapi.localdomain 1/0/683370 46 -- 39/39/37/37/0 0/0
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:37654 [23/Feb/2026:08:24:42.829] redis redis/np0005626459.internalapi.localdomain 1/0/521064 30 -- 37/37/36/36/0 0/0
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:46178 [23/Feb/2026:08:13:53.588] redis redis/np0005626459.internalapi.localdomain 1/0/1170078 4820 -- 37/37/35/34/0 0/0
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:50860 [23/Feb/2026:08:29:46.255] redis redis/np0005626459.internalapi.localdomain 1/0/221920 30 -- 37/37/34/34/0 0/0
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:45426 [23/Feb/2026:08:15:28.483] redis redis/np0005626459.internalapi.localdomain 1/0/1075195 4796 -- 37/37/33/33/0 0/0
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:50190 [23/Feb/2026:08:13:55.348] redis redis/np0005626459.internalapi.localdomain 1/0/1168318 4820 -- 34/34/32/32/0 0/0
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:45424 [23/Feb/2026:08:15:28.184] redis redis/np0005626459.internalapi.localdomain 1/0/1075496 4796 -- 33/33/31/31/0 0/0
Feb 23 08:33:28 np0005626461 haproxy[7]: 192.168.122.110:45404 [23/Feb/2026:08:15:27.186] redis redis/np0005626459.internalapi.localdomain 1/0/1076494 4796 -- 33/33/30/30/0 0/0
Feb 23 08:33:30 np0005626461 haproxy[7]: 192.168.122.103:60460 [23/Feb/2026:08:15:24.946] redis redis/np0005626459.internalapi.localdomain 1/0/1079858 4797 -- 30/30/29/29/0 0/0
Feb 23 08:33:30 np0005626461 haproxy[7]: 192.168.122.103:60444 [23/Feb/2026:08:15:24.931] redis redis/np0005626459.internalapi.localdomain 1/0/1079874 164 -- 29/29/28/28/0 0/0
Feb 23 08:33:30 np0005626461 haproxy[7]: 192.168.122.103:60472 [23/Feb/2026:08:15:25.264] redis redis/np0005626459.internalapi.localdomain 1/0/1079559 36661 -- 28/28/27/27/0 0/0
Feb 23 08:33:30 np0005626461 haproxy[7]: 192.168.122.103:60438 [23/Feb/2026:08:15:24.918] redis redis/np0005626459.internalapi.localdomain 1/0/1079905 49761 -- 27/27/26/26/0 0/0
Feb 23 08:33:30 np0005626461 haproxy[7]: 192.168.122.103:46340 [23/Feb/2026:08:23:14.648] redis redis/np0005626459.internalapi.localdomain 1/0/610226 4140 -- 26/26/25/25/0 0/0
Feb 23 08:33:30 np0005626461 haproxy[7]: 192.168.122.103:60470 [23/Feb/2026:08:15:25.230] redis redis/np0005626459.internalapi.localdomain 1/0/1079594 3512 -- 25/25/24/24/0 0/0
Feb 23 08:33:31 np0005626461 haproxy[7]: 192.168.122.104:33322 [23/Feb/2026:08:13:55.230] redis redis/np0005626459.internalapi.localdomain 1/0/1170845 4823 -- 24/24/23/23/0 0/0
Feb 23 08:33:31 np0005626461 haproxy[7]: 192.168.122.104:33316 [23/Feb/2026:08:13:55.200] redis redis/np0005626459.internalapi.localdomain 1/0/1170877 154 -- 23/23/22/22/0 0/0
Feb 23 08:33:31 np0005626461 haproxy[7]: 192.168.122.104:38550 [23/Feb/2026:08:15:27.686] redis redis/np0005626459.internalapi.localdomain 1/0/1078418 36759 -- 22/22/21/21/0 0/0
Feb 23 08:33:31 np0005626461 haproxy[7]: 192.168.122.104:38530 [23/Feb/2026:08:15:27.348] redis redis/np0005626459.internalapi.localdomain 1/0/1078757 40109 -- 22/22/20/20/0 0/0
Feb 23 08:33:31 np0005626461 haproxy[7]: 192.168.122.104:47068 [23/Feb/2026:08:24:42.995] redis redis/np0005626459.internalapi.localdomain 1/0/523325 13960 -- 20/20/19/19/0 0/0
Feb 23 08:33:31 np0005626461 haproxy[7]: 192.168.122.104:38544 [23/Feb/2026:08:15:27.628] redis redis/np0005626459.internalapi.localdomain 1/0/1078477 3512 -- 19/19/18/18/0 0/0
Feb 23 08:33:32 np0005626461 haproxy[7]: 192.168.122.110:46146 [23/Feb/2026:08:13:53.272] redis redis/np0005626459.internalapi.localdomain 1/0/1173968 4823 -- 18/18/17/17/0 0/0
Feb 23 08:33:32 np0005626461 haproxy[7]: 192.168.122.110:46130 [23/Feb/2026:08:13:53.260] redis redis/np0005626459.internalapi.localdomain 1/0/1173983 154 -- 17/17/16/16/0 0/0
Feb 23 08:33:32 np0005626461 haproxy[7]: 192.168.122.110:37666 [23/Feb/2026:08:24:42.991] redis redis/np0005626459.internalapi.localdomain 1/0/524494 13031 -- 16/16/15/15/0 0/0
Feb 23 08:33:32 np0005626461 haproxy[7]: 192.168.122.110:33076 [23/Feb/2026:08:15:24.449] redis redis/np0005626459.internalapi.localdomain 1/0/1082821 41252 -- 16/16/14/14/0 0/0
Feb 23 08:33:32 np0005626461 haproxy[7]: 192.168.122.110:45372 [23/Feb/2026:08:15:24.722] redis redis/np0005626459.internalapi.localdomain 1/0/1082548 3512 -- 14/14/12/12/0 0/0
Feb 23 08:33:32 np0005626461 haproxy[7]: 192.168.122.110:45388 [23/Feb/2026:08:15:25.757] redis redis/np0005626459.internalapi.localdomain 1/0/1081513 37487 -- 16/16/13/13/0 0/0
Feb 23 08:33:32 np0005626461 haproxy[7]: Server gnocchi/np0005626460.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.
Feb 23 08:33:36 np0005626461 haproxy[7]: Server gnocchi/np0005626461.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.
Feb 23 08:33:36 np0005626461 haproxy[7]: proxy gnocchi has no server available!
Feb 23 08:33:46 np0005626461 haproxy[7]: Server manila/np0005626459.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.
Feb 23 08:33:51 np0005626461 haproxy[7]: Server manila/np0005626460.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.
Feb 23 08:33:55 np0005626461 haproxy[7]: Server manila/np0005626461.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.
Feb 23 08:33:55 np0005626461 haproxy[7]: proxy manila has no server available!
Feb 23 08:34:45 np0005626461 haproxy[7]: Server neutron/np0005626459.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.
Feb 23 08:35:01 np0005626461 haproxy[7]: Server neutron/np0005626460.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.
Feb 23 08:35:31 np0005626461 haproxy[7]: Server neutron/np0005626461.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.
Feb 23 08:35:31 np0005626461 haproxy[7]: proxy neutron has no server available!
Feb 23 08:35:40 np0005626461 haproxy[7]: Server placement/np0005626459.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.
Feb 23 08:35:44 np0005626461 haproxy[7]: Server placement/np0005626460.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.
Feb 23 08:35:48 np0005626461 haproxy[7]: Server placement/np0005626461.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.
Feb 23 08:35:48 np0005626461 haproxy[7]: proxy placement has no server available!
Feb 23 08:35:55 np0005626461 haproxy[7]: Server nova_osapi/np0005626459.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.
Feb 23 08:35:59 np0005626461 haproxy[7]: Server nova_osapi/np0005626460.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.
Feb 23 08:36:04 np0005626461 haproxy[7]: Server nova_osapi/np0005626461.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.
Feb 23 08:36:04 np0005626461 haproxy[7]: proxy nova_osapi has no server available!
Feb 23 08:36:18 np0005626461 haproxy[7]: Server nova_metadata/np0005626459.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.
Feb 23 08:36:22 np0005626461 haproxy[7]: Server nova_metadata/np0005626460.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.
Feb 23 08:36:26 np0005626461 haproxy[7]: Server nova_metadata/np0005626461.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.
Feb 23 08:36:26 np0005626461 haproxy[7]: proxy nova_metadata has no server available!
Feb 23 08:37:21 np0005626461 haproxy[7]: Server nova_novncproxy/np0005626459.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.
Feb 23 08:37:22 np0005626461 haproxy[7]: Server nova_novncproxy/np0005626460.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 234ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Feb 23 08:37:24 np0005626461 haproxy[7]: Server nova_novncproxy/np0005626461.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.
Feb 23 08:37:24 np0005626461 haproxy[7]: proxy nova_novncproxy has no server available!
Feb 23 08:54:14 np0005626461 haproxy[7]: Backup Server mysql/np0005626461.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 16ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
Feb 23 08:54:16 np0005626461 haproxy[7]: Backup Server mysql/np0005626461.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 23ms. 0 active and 3 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Feb 23 08:57:42 np0005626461 haproxy[7]: Backup Server mysql/np0005626461.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 19ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.