Mar 14 08:13:40 np0005647024 haproxy[7]: Server aodh/np0005647022.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: Server aodh/np0005647023.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: Server aodh/np0005647024.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: proxy aodh has no server available!
Mar 14 08:13:40 np0005647024 haproxy[7]: Server cinder/np0005647022.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: Server cinder/np0005647023.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: Server cinder/np0005647024.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: proxy cinder has no server available!
Mar 14 08:13:40 np0005647024 haproxy[7]: Server glance_api/np0005647022.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: Server glance_api/np0005647023.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: Server glance_api/np0005647024.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: proxy glance_api has no server available!
Mar 14 08:13:40 np0005647024 haproxy[7]: Server glance_api_internal/np0005647022.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: Server glance_api_internal/np0005647023.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: Server glance_api_internal/np0005647024.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.
Mar 14 08:13:40 np0005647024 haproxy[7]: proxy glance_api_internal has no server available!
Mar 14 08:13:40 np0005647024 haproxy[7]: Server gnocchi/np0005647022.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server gnocchi/np0005647023.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server gnocchi/np0005647024.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: proxy gnocchi has no server available!
Mar 14 08:13:41 np0005647024 haproxy[7]: Server heat_api/np0005647022.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server heat_api/np0005647023.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Backup Server mysql/np0005647022.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server heat_api/np0005647024.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: proxy heat_api has no server available!
Mar 14 08:13:41 np0005647024 haproxy[7]: Backup Server mysql/np0005647023.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 22ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
Mar 14 08:13:41 np0005647024 haproxy[7]: Backup Server mysql/np0005647024.internalapi.localdomain is DOWN, reason: Layer7 wrong status, code: 503, info: "Service Unavailable", check duration: 17ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Mar 14 08:13:41 np0005647024 haproxy[7]: proxy mysql has no server available!
Mar 14 08:13:41 np0005647024 haproxy[7]: Server heat_cfn/np0005647022.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server heat_cfn/np0005647023.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server heat_cfn/np0005647024.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: proxy heat_cfn has no server available!
Mar 14 08:13:41 np0005647024 haproxy[7]: Server horizon/np0005647022.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server horizon/np0005647023.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server horizon/np0005647024.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: proxy horizon has no server available!
Mar 14 08:13:41 np0005647024 haproxy[7]: Server keystone_admin/np0005647022.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server keystone_admin/np0005647023.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server keystone_admin/np0005647024.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: proxy keystone_admin has no server available!
Mar 14 08:13:41 np0005647024 haproxy[7]: Server keystone_public/np0005647022.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server keystone_public/np0005647023.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server keystone_public/np0005647024.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: proxy keystone_public has no server available!
Mar 14 08:13:41 np0005647024 haproxy[7]: Server manila/np0005647022.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server manila/np0005647023.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server manila/np0005647024.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: proxy manila has no server available!
Mar 14 08:13:41 np0005647024 haproxy[7]: Server neutron/np0005647022.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 6ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server neutron/np0005647023.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server neutron/np0005647024.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: proxy neutron has no server available!
Mar 14 08:13:41 np0005647024 haproxy[7]: Server nova_metadata/np0005647022.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server nova_metadata/np0005647023.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: Server nova_metadata/np0005647024.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.
Mar 14 08:13:41 np0005647024 haproxy[7]: proxy nova_metadata has no server available!
Mar 14 08:13:42 np0005647024 haproxy[7]: Server nova_novncproxy/np0005647022.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: Server nova_novncproxy/np0005647023.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: Server nova_novncproxy/np0005647024.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: proxy nova_novncproxy has no server available!
Mar 14 08:13:42 np0005647024 haproxy[7]: Server nova_osapi/np0005647022.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: Server nova_osapi/np0005647023.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: Server nova_osapi/np0005647024.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: proxy nova_osapi has no server available!
Mar 14 08:13:42 np0005647024 haproxy[7]: Server placement/np0005647022.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: Server placement/np0005647023.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: Server placement/np0005647024.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: proxy placement has no server available!
Mar 14 08:13:42 np0005647024 haproxy[7]: Server redis/np0005647022.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: Server redis/np0005647023.internalapi.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused at step 1 of tcp-check (connect port 6379)", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Mar 14 08:13:42 np0005647024 haproxy[7]: Server redis/np0005647024.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: proxy redis has no server available!
Mar 14 08:13:42 np0005647024 haproxy[7]: Server swift_proxy_server/np0005647022.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: Server swift_proxy_server/np0005647023.storage.localdomain is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 4ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Mar 14 08:13:42 np0005647024 haproxy[7]: Server swift_proxy_server/np0005647024.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.
Mar 14 08:13:42 np0005647024 haproxy[7]: proxy swift_proxy_server has no server available!
Mar 14 08:15:27 np0005647024 haproxy[7]: Backup Server mysql/np0005647024.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.
Mar 14 08:15:47 np0005647024 haproxy[7]: Backup Server mysql/np0005647024.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.
Mar 14 08:15:47 np0005647024 haproxy[7]: proxy mysql has no server available!
Mar 14 08:15:49 np0005647024 haproxy[7]: Backup Server mysql/np0005647024.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.
Mar 14 08:15:50 np0005647024 haproxy[7]: Backup Server mysql/np0005647023.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 23ms. 0 active and 2 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Mar 14 08:16:57 np0005647024 haproxy[7]: Server redis/np0005647022.internalapi.localdomain is UP, reason: Layer7 check passed, code: 0, info: "(tcp-check)", check duration: 1ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:17:06 np0005647024 haproxy[7]: Backup Server mysql/np0005647022.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 22ms. 0 active and 3 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Mar 14 08:17:51 np0005647024 haproxy[7]: Server keystone_admin/np0005647023.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.
Mar 14 08:17:51 np0005647024 haproxy[7]: Server keystone_public/np0005647023.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.
Mar 14 08:17:52 np0005647024 haproxy[7]: Server keystone_admin/np0005647024.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.
Mar 14 08:17:52 np0005647024 haproxy[7]: Server keystone_public/np0005647024.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 9ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:17:53 np0005647024 haproxy[7]: Server horizon/np0005647023.internalapi.localdomain is UP, reason: Layer7 check passed, code: 301, check duration: 1ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:17:55 np0005647024 haproxy[7]: Server horizon/np0005647024.internalapi.localdomain is UP, reason: Layer7 check passed, code: 301, check duration: 0ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:18:29 np0005647024 haproxy[7]: Server horizon/np0005647022.internalapi.localdomain is UP, reason: Layer7 check passed, code: 301, check duration: 1ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:18:56 np0005647024 haproxy[7]: Server keystone_admin/np0005647022.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 9ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:18:56 np0005647024 haproxy[7]: Server keystone_public/np0005647022.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 12ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:22:59 np0005647024 haproxy[7]: Server aodh/np0005647022.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 10ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:22:59 np0005647024 haproxy[7]: Server heat_cfn/np0005647022.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 3ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:22:59 np0005647024 haproxy[7]: Server heat_api/np0005647022.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.
Mar 14 08:23:00 np0005647024 haproxy[7]: Server cinder/np0005647022.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 3ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:23:02 np0005647024 haproxy[7]: Server manila/np0005647022.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.
Mar 14 08:23:04 np0005647024 haproxy[7]: Server nova_novncproxy/np0005647022.internalapi.localdomain is UP, reason: Layer4 check passed, check duration: 0ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:23:06 np0005647024 haproxy[7]: Server placement/np0005647022.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 0ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:23:08 np0005647024 haproxy[7]: Server nova_metadata/np0005647022.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.
Mar 14 08:23:08 np0005647024 haproxy[7]: Server neutron/np0005647022.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.
Mar 14 08:23:08 np0005647024 haproxy[7]: Server nova_osapi/np0005647022.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.
Mar 14 08:23:08 np0005647024 haproxy[7]: Server swift_proxy_server/np0005647022.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.
Mar 14 08:23:09 np0005647024 haproxy[7]: Server glance_api_internal/np0005647022.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 3ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:23:09 np0005647024 haproxy[7]: Server glance_api/np0005647022.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.
Mar 14 08:23:13 np0005647024 haproxy[7]: Server aodh/np0005647024.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 12ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:23:15 np0005647024 haproxy[7]: Server cinder/np0005647023.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 13ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:23:15 np0005647024 haproxy[7]: Server heat_api/np0005647023.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.
Mar 14 08:23:15 np0005647024 haproxy[7]: Server cinder/np0005647024.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.
Mar 14 08:23:15 np0005647024 haproxy[7]: Server aodh/np0005647023.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 13ms. 3 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:23:15 np0005647024 haproxy[7]: Server heat_cfn/np0005647023.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.
Mar 14 08:23:15 np0005647024 haproxy[7]: Server heat_api/np0005647024.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.
Mar 14 08:23:15 np0005647024 haproxy[7]: Server heat_cfn/np0005647024.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.
Mar 14 08:23:16 np0005647024 haproxy[7]: Server manila/np0005647023.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 12ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:23:18 np0005647024 haproxy[7]: Server manila/np0005647024.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.
Mar 14 08:23:19 np0005647024 haproxy[7]: Server nova_novncproxy/np0005647023.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.
Mar 14 08:23:20 np0005647024 haproxy[7]: Server nova_novncproxy/np0005647024.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.
Mar 14 08:23:20 np0005647024 haproxy[7]: Server placement/np0005647024.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 0ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:23:21 np0005647024 haproxy[7]: Server placement/np0005647023.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.
Mar 14 08:23:22 np0005647024 haproxy[7]: Server neutron/np0005647023.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.
Mar 14 08:23:23 np0005647024 haproxy[7]: Server glance_api_internal/np0005647023.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 6ms. 2 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:23:23 np0005647024 haproxy[7]: Server glance_api/np0005647023.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.
Mar 14 08:23:23 np0005647024 haproxy[7]: Server swift_proxy_server/np0005647023.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.
Mar 14 08:23:23 np0005647024 haproxy[7]: Server nova_metadata/np0005647023.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.
Mar 14 08:23:24 np0005647024 haproxy[7]: Server neutron/np0005647024.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.
Mar 14 08:23:24 np0005647024 haproxy[7]: Server nova_metadata/np0005647024.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.
Mar 14 08:23:24 np0005647024 haproxy[7]: Server nova_osapi/np0005647023.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.
Mar 14 08:23:24 np0005647024 haproxy[7]: Server nova_osapi/np0005647024.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.
Mar 14 08:23:25 np0005647024 haproxy[7]: Server swift_proxy_server/np0005647024.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.
Mar 14 08:23:25 np0005647024 haproxy[7]: Server glance_api/np0005647024.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.
Mar 14 08:23:25 np0005647024 haproxy[7]: Server glance_api_internal/np0005647024.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.
Mar 14 08:27:03 np0005647024 haproxy[7]: 192.168.122.104:38762 [14/Mar/2026:08:27:03.293] redis redis/np0005647022.internalapi.localdomain 1/0/8 10 -- 30/30/29/29/0 0/0
Mar 14 08:27:03 np0005647024 haproxy[7]: 192.168.122.104:38736 [14/Mar/2026:08:27:03.037] redis redis/np0005647022.internalapi.localdomain 1/0/265 4428 -- 30/30/28/28/0 0/0
Mar 14 08:27:03 np0005647024 haproxy[7]: 192.168.122.104:38776 [14/Mar/2026:08:27:03.615] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 30/30/29/29/0 0/0
Mar 14 08:27:03 np0005647024 haproxy[7]: 192.168.122.104:38770 [14/Mar/2026:08:27:03.332] redis redis/np0005647022.internalapi.localdomain 1/0/295 4429 -- 30/30/28/28/0 0/0
Mar 14 08:27:04 np0005647024 haproxy[7]: 192.168.122.110:34306 [14/Mar/2026:08:27:04.875] redis redis/np0005647022.internalapi.localdomain 1/0/16 10 -- 36/36/35/35/0 0/0
Mar 14 08:27:04 np0005647024 haproxy[7]: 192.168.122.110:34262 [14/Mar/2026:08:27:04.611] redis redis/np0005647022.internalapi.localdomain 1/0/281 4429 -- 36/36/34/34/0 0/0
Mar 14 08:27:05 np0005647024 haproxy[7]: 192.168.122.110:34322 [14/Mar/2026:08:27:05.179] redis redis/np0005647022.internalapi.localdomain 1/0/8 10 -- 37/37/36/36/0 0/0
Mar 14 08:27:05 np0005647024 haproxy[7]: 192.168.122.110:34314 [14/Mar/2026:08:27:04.920] redis redis/np0005647022.internalapi.localdomain 1/0/268 4430 -- 36/36/35/35/0 0/0
Mar 14 08:27:05 np0005647024 haproxy[7]: Server gnocchi/np0005647023.internalapi.localdomain is UP, reason: Layer7 check passed, code: 200, check duration: 3ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
Mar 14 08:27:07 np0005647024 haproxy[7]: Server gnocchi/np0005647024.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.
Mar 14 08:27:08 np0005647024 haproxy[7]: 192.168.122.104:38820 [14/Mar/2026:08:27:08.919] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:08 np0005647024 haproxy[7]: 192.168.122.104:38814 [14/Mar/2026:08:27:08.649] redis redis/np0005647022.internalapi.localdomain 1/0/280 4429 -- 38/38/37/37/0 0/0
Mar 14 08:27:09 np0005647024 haproxy[7]: 192.168.122.104:38836 [14/Mar/2026:08:27:08.952] redis redis/np0005647022.internalapi.localdomain 1/0/285 4429 -- 39/39/38/38/0 0/0
Mar 14 08:27:09 np0005647024 haproxy[7]: 192.168.122.104:38846 [14/Mar/2026:08:27:09.227] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:09 np0005647024 haproxy[7]: 192.168.122.104:38860 [14/Mar/2026:08:27:09.254] redis redis/np0005647022.internalapi.localdomain 1/0/246 4429 -- 39/39/38/38/0 0/0
Mar 14 08:27:09 np0005647024 haproxy[7]: 192.168.122.104:38876 [14/Mar/2026:08:27:09.489] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:09 np0005647024 haproxy[7]: 192.168.122.104:38902 [14/Mar/2026:08:27:09.795] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:09 np0005647024 haproxy[7]: 192.168.122.104:38890 [14/Mar/2026:08:27:09.516] redis redis/np0005647022.internalapi.localdomain 1/0/290 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:10 np0005647024 haproxy[7]: 192.168.122.110:34346 [14/Mar/2026:08:27:10.514] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:10 np0005647024 haproxy[7]: 192.168.122.110:34336 [14/Mar/2026:08:27:10.223] redis redis/np0005647022.internalapi.localdomain 1/0/304 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:10 np0005647024 haproxy[7]: 192.168.122.110:43248 [14/Mar/2026:08:27:10.800] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:10 np0005647024 haproxy[7]: 192.168.122.110:43246 [14/Mar/2026:08:27:10.554] redis redis/np0005647022.internalapi.localdomain 1/0/258 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:11 np0005647024 haproxy[7]: 192.168.122.110:43274 [14/Mar/2026:08:27:11.086] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:11 np0005647024 haproxy[7]: 192.168.122.110:43258 [14/Mar/2026:08:27:10.839] redis redis/np0005647022.internalapi.localdomain 1/0/257 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:11 np0005647024 haproxy[7]: 192.168.122.110:43290 [14/Mar/2026:08:27:11.353] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:11 np0005647024 haproxy[7]: 192.168.122.110:43276 [14/Mar/2026:08:27:11.120] redis redis/np0005647022.internalapi.localdomain 1/2/244 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:15 np0005647024 haproxy[7]: 192.168.122.104:56278 [14/Mar/2026:08:27:15.083] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:15 np0005647024 haproxy[7]: 192.168.122.104:56266 [14/Mar/2026:08:27:14.836] redis redis/np0005647022.internalapi.localdomain 1/1/259 4429 -- 39/39/37/37/0 0/0
Mar 14 08:27:15 np0005647024 haproxy[7]: 192.168.122.104:56294 [14/Mar/2026:08:27:15.389] redis redis/np0005647022.internalapi.localdomain 1/0/7 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:15 np0005647024 haproxy[7]: 192.168.122.104:56292 [14/Mar/2026:08:27:15.127] redis redis/np0005647022.internalapi.localdomain 1/0/271 4429 -- 38/38/37/37/0 0/0
Mar 14 08:27:15 np0005647024 haproxy[7]: 192.168.122.104:56306 [14/Mar/2026:08:27:15.424] redis redis/np0005647022.internalapi.localdomain 1/0/303 4429 -- 39/39/37/37/0 0/0
Mar 14 08:27:15 np0005647024 haproxy[7]: 192.168.122.104:56314 [14/Mar/2026:08:27:15.717] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:15 np0005647024 haproxy[7]: 192.168.122.104:56332 [14/Mar/2026:08:27:15.973] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:15 np0005647024 haproxy[7]: 192.168.122.104:56324 [14/Mar/2026:08:27:15.744] redis redis/np0005647022.internalapi.localdomain 1/0/240 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:16 np0005647024 haproxy[7]: 192.168.122.110:43316 [14/Mar/2026:08:27:16.644] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:16 np0005647024 haproxy[7]: 192.168.122.110:43304 [14/Mar/2026:08:27:16.393] redis redis/np0005647022.internalapi.localdomain 1/0/263 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:17 np0005647024 haproxy[7]: 192.168.122.110:43326 [14/Mar/2026:08:27:16.689] redis redis/np0005647022.internalapi.localdomain 1/0/348 4430 -- 39/39/38/38/0 0/0
Mar 14 08:27:17 np0005647024 haproxy[7]: 192.168.122.110:43328 [14/Mar/2026:08:27:17.019] redis redis/np0005647022.internalapi.localdomain 1/0/17 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:17 np0005647024 haproxy[7]: 192.168.122.110:43338 [14/Mar/2026:08:27:17.054] redis redis/np0005647022.internalapi.localdomain 1/0/242 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:17 np0005647024 haproxy[7]: 192.168.122.110:43344 [14/Mar/2026:08:27:17.284] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:17 np0005647024 haproxy[7]: 192.168.122.110:43354 [14/Mar/2026:08:27:17.311] redis redis/np0005647022.internalapi.localdomain 1/0/238 4430 -- 39/39/38/38/0 0/0
Mar 14 08:27:17 np0005647024 haproxy[7]: 192.168.122.110:43358 [14/Mar/2026:08:27:17.540] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:21 np0005647024 haproxy[7]: 192.168.122.104:56346 [14/Mar/2026:08:27:21.276] redis redis/np0005647022.internalapi.localdomain 1/0/7 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:21 np0005647024 haproxy[7]: 192.168.122.104:56340 [14/Mar/2026:08:27:21.019] redis redis/np0005647022.internalapi.localdomain 1/0/264 4429 -- 38/38/37/37/0 0/0
Mar 14 08:27:21 np0005647024 haproxy[7]: 192.168.122.104:56352 [14/Mar/2026:08:27:21.311] redis redis/np0005647022.internalapi.localdomain 1/0/256 4429 -- 39/39/38/38/0 0/0
Mar 14 08:27:21 np0005647024 haproxy[7]: 192.168.122.104:56364 [14/Mar/2026:08:27:21.559] redis redis/np0005647022.internalapi.localdomain 1/0/8 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:21 np0005647024 haproxy[7]: 192.168.122.104:56370 [14/Mar/2026:08:27:21.590] redis redis/np0005647022.internalapi.localdomain 1/0/293 4430 -- 39/39/38/38/0 0/0
Mar 14 08:27:21 np0005647024 haproxy[7]: 192.168.122.104:56374 [14/Mar/2026:08:27:21.874] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 38/38/37/37/0 0/0
Mar 14 08:27:22 np0005647024 haproxy[7]: 192.168.122.104:56398 [14/Mar/2026:08:27:22.163] redis redis/np0005647022.internalapi.localdomain 1/0/14 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:22 np0005647024 haproxy[7]: 192.168.122.104:56384 [14/Mar/2026:08:27:21.899] redis redis/np0005647022.internalapi.localdomain 1/0/278 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:22 np0005647024 haproxy[7]: 192.168.122.110:38194 [14/Mar/2026:08:27:22.939] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:22 np0005647024 haproxy[7]: 192.168.122.110:38186 [14/Mar/2026:08:27:22.587] redis redis/np0005647022.internalapi.localdomain 1/0/362 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:23 np0005647024 haproxy[7]: 192.168.122.110:38218 [14/Mar/2026:08:27:23.240] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:23 np0005647024 haproxy[7]: 192.168.122.110:38208 [14/Mar/2026:08:27:22.981] redis redis/np0005647022.internalapi.localdomain 1/0/269 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:23 np0005647024 haproxy[7]: 192.168.122.110:38240 [14/Mar/2026:08:27:23.569] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:23 np0005647024 haproxy[7]: 192.168.122.110:38224 [14/Mar/2026:08:27:23.266] redis redis/np0005647022.internalapi.localdomain 1/0/314 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:23 np0005647024 haproxy[7]: 192.168.122.110:38268 [14/Mar/2026:08:27:23.819] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:23 np0005647024 haproxy[7]: 192.168.122.110:38256 [14/Mar/2026:08:27:23.595] redis redis/np0005647022.internalapi.localdomain 1/0/234 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:27 np0005647024 haproxy[7]: 192.168.122.104:54196 [14/Mar/2026:08:27:27.492] redis redis/np0005647022.internalapi.localdomain 1/0/6 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:27 np0005647024 haproxy[7]: 192.168.122.104:54184 [14/Mar/2026:08:27:27.209] redis redis/np0005647022.internalapi.localdomain 1/0/291 4429 -- 38/38/37/37/0 0/0
Mar 14 08:27:27 np0005647024 haproxy[7]: 192.168.122.104:54206 [14/Mar/2026:08:27:27.520] redis redis/np0005647022.internalapi.localdomain 1/0/293 4428 -- 39/39/38/38/0 0/0
Mar 14 08:27:27 np0005647024 haproxy[7]: 192.168.122.104:54210 [14/Mar/2026:08:27:27.800] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 38/38/37/37/0 0/0
Mar 14 08:27:28 np0005647024 haproxy[7]: 192.168.122.104:54224 [14/Mar/2026:08:27:28.094] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:28 np0005647024 haproxy[7]: 192.168.122.104:54214 [14/Mar/2026:08:27:27.835] redis redis/np0005647022.internalapi.localdomain 1/0/269 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:28 np0005647024 haproxy[7]: 192.168.122.104:54226 [14/Mar/2026:08:27:28.138] redis redis/np0005647022.internalapi.localdomain 1/0/289 4430 -- 39/39/38/38/0 0/0
Mar 14 08:27:28 np0005647024 haproxy[7]: 192.168.122.104:54230 [14/Mar/2026:08:27:28.413] redis redis/np0005647022.internalapi.localdomain 1/0/13 10 -- 38/38/37/37/0 0/0
Mar 14 08:27:29 np0005647024 haproxy[7]: 192.168.122.110:38282 [14/Mar/2026:08:27:29.160] redis redis/np0005647022.internalapi.localdomain 1/0/9 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:29 np0005647024 haproxy[7]: 192.168.122.110:38280 [14/Mar/2026:08:27:28.867] redis redis/np0005647022.internalapi.localdomain 1/0/301 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:29 np0005647024 haproxy[7]: 192.168.122.110:38294 [14/Mar/2026:08:27:29.431] redis redis/np0005647022.internalapi.localdomain 1/0/13 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:29 np0005647024 haproxy[7]: 192.168.122.110:38288 [14/Mar/2026:08:27:29.190] redis redis/np0005647022.internalapi.localdomain 1/0/255 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:29 np0005647024 haproxy[7]: 192.168.122.110:38324 [14/Mar/2026:08:27:29.706] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:29 np0005647024 haproxy[7]: 192.168.122.110:38308 [14/Mar/2026:08:27:29.468] redis redis/np0005647022.internalapi.localdomain 1/0/249 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:30 np0005647024 haproxy[7]: 192.168.122.110:38326 [14/Mar/2026:08:27:29.738] redis redis/np0005647022.internalapi.localdomain 1/0/268 4430 -- 39/39/38/38/0 0/0
Mar 14 08:27:30 np0005647024 haproxy[7]: 192.168.122.110:38336 [14/Mar/2026:08:27:29.995] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 38/38/37/37/0 0/0
Mar 14 08:27:33 np0005647024 haproxy[7]: 192.168.122.104:49714 [14/Mar/2026:08:27:33.708] redis redis/np0005647022.internalapi.localdomain 1/0/7 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:33 np0005647024 haproxy[7]: 192.168.122.104:49708 [14/Mar/2026:08:27:33.463] redis redis/np0005647022.internalapi.localdomain 1/0/253 4429 -- 38/38/37/37/0 0/0
Mar 14 08:27:33 np0005647024 haproxy[7]: 192.168.122.104:49742 [14/Mar/2026:08:27:33.957] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:33 np0005647024 haproxy[7]: 192.168.122.104:49728 [14/Mar/2026:08:27:33.735] redis redis/np0005647022.internalapi.localdomain 1/0/232 4429 -- 39/39/37/37/0 0/0
Mar 14 08:27:34 np0005647024 haproxy[7]: 192.168.122.104:49770 [14/Mar/2026:08:27:34.288] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:34 np0005647024 haproxy[7]: 192.168.122.104:49758 [14/Mar/2026:08:27:33.999] redis redis/np0005647022.internalapi.localdomain 1/0/301 4429 -- 39/39/37/37/0 0/0
Mar 14 08:27:34 np0005647024 haproxy[7]: 192.168.122.104:49794 [14/Mar/2026:08:27:34.580] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:34 np0005647024 haproxy[7]: 192.168.122.104:49778 [14/Mar/2026:08:27:34.329] redis redis/np0005647022.internalapi.localdomain 1/0/263 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:35 np0005647024 haproxy[7]: 192.168.122.110:42188 [14/Mar/2026:08:27:35.302] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:35 np0005647024 haproxy[7]: 192.168.122.110:42184 [14/Mar/2026:08:27:35.042] redis redis/np0005647022.internalapi.localdomain 1/0/273 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:35 np0005647024 haproxy[7]: 192.168.122.110:42192 [14/Mar/2026:08:27:35.347] redis redis/np0005647022.internalapi.localdomain 1/0/282 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:35 np0005647024 haproxy[7]: 192.168.122.110:42206 [14/Mar/2026:08:27:35.619] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:35 np0005647024 haproxy[7]: 192.168.122.110:42222 [14/Mar/2026:08:27:35.658] redis redis/np0005647022.internalapi.localdomain 1/0/276 4430 -- 39/39/38/38/0 0/0
Mar 14 08:27:35 np0005647024 haproxy[7]: 192.168.122.110:42232 [14/Mar/2026:08:27:35.925] redis redis/np0005647022.internalapi.localdomain 1/1/10 10 -- 38/38/37/37/0 0/0
Mar 14 08:27:36 np0005647024 haproxy[7]: 192.168.122.110:42252 [14/Mar/2026:08:27:36.196] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:36 np0005647024 haproxy[7]: 192.168.122.110:42242 [14/Mar/2026:08:27:35.968] redis redis/np0005647022.internalapi.localdomain 1/0/238 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:39 np0005647024 haproxy[7]: 192.168.122.104:49818 [14/Mar/2026:08:27:39.889] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:39 np0005647024 haproxy[7]: 192.168.122.104:49806 [14/Mar/2026:08:27:39.630] redis redis/np0005647022.internalapi.localdomain 1/0/270 4429 -- 38/38/37/37/0 0/0
Mar 14 08:27:40 np0005647024 haproxy[7]: 192.168.122.104:49826 [14/Mar/2026:08:27:40.174] redis redis/np0005647022.internalapi.localdomain 1/0/8 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:40 np0005647024 haproxy[7]: 192.168.122.104:49824 [14/Mar/2026:08:27:39.930] redis redis/np0005647022.internalapi.localdomain 1/0/253 4429 -- 39/39/37/37/0 0/0
Mar 14 08:27:40 np0005647024 haproxy[7]: 192.168.122.104:49838 [14/Mar/2026:08:27:40.205] redis redis/np0005647022.internalapi.localdomain 1/0/268 4429 -- 39/39/38/38/0 0/0
Mar 14 08:27:40 np0005647024 haproxy[7]: 192.168.122.104:49850 [14/Mar/2026:08:27:40.461] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:40 np0005647024 haproxy[7]: 192.168.122.104:49878 [14/Mar/2026:08:27:40.751] redis redis/np0005647022.internalapi.localdomain 1/0/17 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:40 np0005647024 haproxy[7]: 192.168.122.104:49864 [14/Mar/2026:08:27:40.502] redis redis/np0005647022.internalapi.localdomain 1/0/267 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:41 np0005647024 haproxy[7]: 192.168.122.110:43508 [14/Mar/2026:08:27:41.503] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:41 np0005647024 haproxy[7]: 192.168.122.110:43492 [14/Mar/2026:08:27:41.241] redis redis/np0005647022.internalapi.localdomain 1/0/274 4431 -- 38/38/37/37/0 0/0
Mar 14 08:27:41 np0005647024 haproxy[7]: 192.168.122.110:43516 [14/Mar/2026:08:27:41.539] redis redis/np0005647022.internalapi.localdomain 1/0/273 4431 -- 39/39/38/38/0 0/0
Mar 14 08:27:41 np0005647024 haproxy[7]: 192.168.122.110:43526 [14/Mar/2026:08:27:41.802] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 38/38/37/37/0 0/0
Mar 14 08:27:42 np0005647024 haproxy[7]: 192.168.122.110:43542 [14/Mar/2026:08:27:41.830] redis redis/np0005647022.internalapi.localdomain 1/0/241 4431 -- 39/39/38/38/0 0/0
Mar 14 08:27:42 np0005647024 haproxy[7]: 192.168.122.110:43544 [14/Mar/2026:08:27:42.064] redis redis/np0005647022.internalapi.localdomain 1/0/7 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:42 np0005647024 haproxy[7]: 192.168.122.110:43552 [14/Mar/2026:08:27:42.101] redis redis/np0005647022.internalapi.localdomain 1/0/255 4431 -- 39/39/38/38/0 0/0
Mar 14 08:27:42 np0005647024 haproxy[7]: 192.168.122.110:43568 [14/Mar/2026:08:27:42.344] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 38/38/37/37/0 0/0
Mar 14 08:27:46 np0005647024 haproxy[7]: 192.168.122.104:53668 [14/Mar/2026:08:27:46.097] redis redis/np0005647022.internalapi.localdomain 1/0/7 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:46 np0005647024 haproxy[7]: 192.168.122.104:53654 [14/Mar/2026:08:27:45.814] redis redis/np0005647022.internalapi.localdomain 1/0/292 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:46 np0005647024 haproxy[7]: 192.168.122.104:53682 [14/Mar/2026:08:27:46.341] redis redis/np0005647022.internalapi.localdomain 1/0/16 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:46 np0005647024 haproxy[7]: 192.168.122.104:53676 [14/Mar/2026:08:27:46.123] redis redis/np0005647022.internalapi.localdomain 1/0/235 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:46 np0005647024 haproxy[7]: 192.168.122.104:53698 [14/Mar/2026:08:27:46.679] redis redis/np0005647022.internalapi.localdomain 1/0/14 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:46 np0005647024 haproxy[7]: 192.168.122.104:53684 [14/Mar/2026:08:27:46.390] redis redis/np0005647022.internalapi.localdomain 1/0/303 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:47 np0005647024 haproxy[7]: 192.168.122.104:53726 [14/Mar/2026:08:27:47.005] redis redis/np0005647022.internalapi.localdomain 1/0/7 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:47 np0005647024 haproxy[7]: 192.168.122.104:53714 [14/Mar/2026:08:27:46.719] redis redis/np0005647022.internalapi.localdomain 1/0/293 4431 -- 39/39/37/37/0 0/0
Mar 14 08:27:47 np0005647024 haproxy[7]: 192.168.122.110:43596 [14/Mar/2026:08:27:47.638] redis redis/np0005647022.internalapi.localdomain 1/0/9 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:47 np0005647024 haproxy[7]: 192.168.122.110:43582 [14/Mar/2026:08:27:47.390] redis redis/np0005647022.internalapi.localdomain 1/0/257 4432 -- 38/38/37/37/0 0/0
Mar 14 08:27:47 np0005647024 haproxy[7]: 192.168.122.110:43614 [14/Mar/2026:08:27:47.919] redis redis/np0005647022.internalapi.localdomain 1/0/8 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:47 np0005647024 haproxy[7]: 192.168.122.110:43598 [14/Mar/2026:08:27:47.676] redis redis/np0005647022.internalapi.localdomain 1/0/251 4432 -- 39/39/37/37/0 0/0
Mar 14 08:27:48 np0005647024 haproxy[7]: 192.168.122.110:43626 [14/Mar/2026:08:27:47.958] redis redis/np0005647022.internalapi.localdomain 1/0/292 4432 -- 39/39/38/38/0 0/0
Mar 14 08:27:48 np0005647024 haproxy[7]: 192.168.122.110:43630 [14/Mar/2026:08:27:48.242] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 38/38/37/37/0 0/0
Mar 14 08:27:48 np0005647024 haproxy[7]: 192.168.122.110:43652 [14/Mar/2026:08:27:48.547] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:48 np0005647024 haproxy[7]: 192.168.122.110:43638 [14/Mar/2026:08:27:48.275] redis redis/np0005647022.internalapi.localdomain 1/0/283 4432 -- 39/39/37/37/0 0/0
Mar 14 08:27:52 np0005647024 haproxy[7]: 192.168.122.104:53748 [14/Mar/2026:08:27:52.347] redis redis/np0005647022.internalapi.localdomain 1/3/13 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:52 np0005647024 haproxy[7]: 192.168.122.104:53734 [14/Mar/2026:08:27:52.051] redis redis/np0005647022.internalapi.localdomain 1/1/310 4429 -- 38/38/37/37/0 0/0
Mar 14 08:27:52 np0005647024 haproxy[7]: 192.168.122.104:53754 [14/Mar/2026:08:27:52.378] redis redis/np0005647022.internalapi.localdomain 1/0/241 4429 -- 39/39/38/38/0 0/0
Mar 14 08:27:52 np0005647024 haproxy[7]: 192.168.122.104:35394 [14/Mar/2026:08:27:52.610] redis redis/np0005647022.internalapi.localdomain 1/0/9 10 -- 38/38/37/37/0 0/0
Mar 14 08:27:52 np0005647024 haproxy[7]: 192.168.122.104:35416 [14/Mar/2026:08:27:52.882] redis redis/np0005647022.internalapi.localdomain 1/0/8 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:52 np0005647024 haproxy[7]: 192.168.122.104:35404 [14/Mar/2026:08:27:52.640] redis redis/np0005647022.internalapi.localdomain 1/0/250 4429 -- 39/39/37/37/0 0/0
Mar 14 08:27:53 np0005647024 haproxy[7]: 192.168.122.104:35432 [14/Mar/2026:08:27:52.914] redis redis/np0005647022.internalapi.localdomain 1/0/329 4430 -- 39/39/38/38/0 0/0
Mar 14 08:27:53 np0005647024 haproxy[7]: 192.168.122.104:35446 [14/Mar/2026:08:27:53.233] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/37/37/0 0/0
Mar 14 08:27:53 np0005647024 haproxy[7]: 192.168.122.110:54796 [14/Mar/2026:08:27:53.853] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:53 np0005647024 haproxy[7]: 192.168.122.110:54788 [14/Mar/2026:08:27:53.594] redis redis/np0005647022.internalapi.localdomain 1/0/269 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:54 np0005647024 haproxy[7]: 192.168.122.110:54812 [14/Mar/2026:08:27:54.170] redis redis/np0005647022.internalapi.localdomain 1/0/13 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:54 np0005647024 haproxy[7]: 192.168.122.110:54810 [14/Mar/2026:08:27:53.894] redis redis/np0005647022.internalapi.localdomain 1/0/293 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:54 np0005647024 haproxy[7]: 192.168.122.110:54830 [14/Mar/2026:08:27:54.452] redis redis/np0005647022.internalapi.localdomain 1/0/16 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:54 np0005647024 haproxy[7]: 192.168.122.110:54814 [14/Mar/2026:08:27:54.214] redis redis/np0005647022.internalapi.localdomain 1/0/255 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:54 np0005647024 haproxy[7]: 192.168.122.110:54836 [14/Mar/2026:08:27:54.502] redis redis/np0005647022.internalapi.localdomain 1/0/273 4430 -- 39/39/38/38/0 0/0
Mar 14 08:27:54 np0005647024 haproxy[7]: 192.168.122.110:54840 [14/Mar/2026:08:27:54.760] redis redis/np0005647022.internalapi.localdomain 1/0/16 10 -- 38/38/37/37/0 0/0
Mar 14 08:27:58 np0005647024 haproxy[7]: 192.168.122.104:35476 [14/Mar/2026:08:27:58.483] redis redis/np0005647022.internalapi.localdomain 1/0/9 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:58 np0005647024 haproxy[7]: 192.168.122.104:35460 [14/Mar/2026:08:27:58.266] redis redis/np0005647022.internalapi.localdomain 1/0/228 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:58 np0005647024 haproxy[7]: 192.168.122.104:35504 [14/Mar/2026:08:27:58.774] redis redis/np0005647022.internalapi.localdomain 1/0/9 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:58 np0005647024 haproxy[7]: 192.168.122.104:35492 [14/Mar/2026:08:27:58.522] redis redis/np0005647022.internalapi.localdomain 1/0/261 4430 -- 38/38/37/37/0 0/0
Mar 14 08:27:59 np0005647024 haproxy[7]: 192.168.122.104:35520 [14/Mar/2026:08:27:59.022] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:59 np0005647024 haproxy[7]: 192.168.122.104:35508 [14/Mar/2026:08:27:58.806] redis redis/np0005647022.internalapi.localdomain 1/0/226 4430 -- 39/39/37/37/0 0/0
Mar 14 08:27:59 np0005647024 haproxy[7]: 192.168.122.104:35536 [14/Mar/2026:08:27:59.312] redis redis/np0005647022.internalapi.localdomain 1/0/9 10 -- 39/39/38/38/0 0/0
Mar 14 08:27:59 np0005647024 haproxy[7]: 192.168.122.104:35532 [14/Mar/2026:08:27:59.069] redis redis/np0005647022.internalapi.localdomain 1/0/254 4431 -- 38/38/37/37/0 0/0
Mar 14 08:28:00 np0005647024 haproxy[7]: 192.168.122.110:54856 [14/Mar/2026:08:28:00.060] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:00 np0005647024 haproxy[7]: 192.168.122.110:54842 [14/Mar/2026:08:27:59.811] redis redis/np0005647022.internalapi.localdomain 1/0/260 4431 -- 38/38/37/37/0 0/0
Mar 14 08:28:00 np0005647024 haproxy[7]: 192.168.122.110:54858 [14/Mar/2026:08:28:00.102] redis redis/np0005647022.internalapi.localdomain 1/0/275 4431 -- 39/39/37/37/0 0/0
Mar 14 08:28:00 np0005647024 haproxy[7]: 192.168.122.110:54860 [14/Mar/2026:08:28:00.364] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 39/39/37/37/0 0/0
Mar 14 08:28:00 np0005647024 haproxy[7]: 192.168.122.110:54874 [14/Mar/2026:08:28:00.399] redis redis/np0005647022.internalapi.localdomain 1/0/284 4431 -- 39/39/38/38/0 0/0
Mar 14 08:28:00 np0005647024 haproxy[7]: 192.168.122.110:50506 [14/Mar/2026:08:28:00.671] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 38/38/37/37/0 0/0
Mar 14 08:28:00 np0005647024 haproxy[7]: 192.168.122.110:50512 [14/Mar/2026:08:28:00.726] redis redis/np0005647022.internalapi.localdomain 1/0/238 4431 -- 39/39/37/37/0 0/0
Mar 14 08:28:00 np0005647024 haproxy[7]: 192.168.122.110:50516 [14/Mar/2026:08:28:00.953] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/37/37/0 0/0
Mar 14 08:28:04 np0005647024 haproxy[7]: 192.168.122.104:54962 [14/Mar/2026:08:28:04.589] redis redis/np0005647022.internalapi.localdomain 1/0/7 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:04 np0005647024 haproxy[7]: 192.168.122.104:54954 [14/Mar/2026:08:28:04.347] redis redis/np0005647022.internalapi.localdomain 1/0/249 4430 -- 38/38/37/37/0 0/0
Mar 14 08:28:04 np0005647024 haproxy[7]: 192.168.122.104:54988 [14/Mar/2026:08:28:04.884] redis redis/np0005647022.internalapi.localdomain 1/0/7 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:04 np0005647024 haproxy[7]: 192.168.122.104:54974 [14/Mar/2026:08:28:04.632] redis redis/np0005647022.internalapi.localdomain 1/0/259 4430 -- 39/39/37/37/0 0/0
Mar 14 08:28:05 np0005647024 haproxy[7]: 192.168.122.104:55012 [14/Mar/2026:08:28:05.160] redis redis/np0005647022.internalapi.localdomain 1/0/19 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:05 np0005647024 haproxy[7]: 192.168.122.104:55004 [14/Mar/2026:08:28:04.912] redis redis/np0005647022.internalapi.localdomain 1/0/267 4431 -- 39/39/37/37/0 0/0
Mar 14 08:28:05 np0005647024 haproxy[7]: 192.168.122.104:55028 [14/Mar/2026:08:28:05.464] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:05 np0005647024 haproxy[7]: 192.168.122.104:55018 [14/Mar/2026:08:28:05.213] redis redis/np0005647022.internalapi.localdomain 1/0/263 4431 -- 39/39/37/37/0 0/0
Mar 14 08:28:06 np0005647024 haproxy[7]: 192.168.122.110:50546 [14/Mar/2026:08:28:06.263] redis redis/np0005647022.internalapi.localdomain 1/0/9 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:06 np0005647024 haproxy[7]: 192.168.122.110:50532 [14/Mar/2026:08:28:05.999] redis redis/np0005647022.internalapi.localdomain 1/0/272 4431 -- 38/38/37/37/0 0/0
Mar 14 08:28:06 np0005647024 haproxy[7]: 192.168.122.110:50550 [14/Mar/2026:08:28:06.297] redis redis/np0005647022.internalapi.localdomain 1/0/290 4431 -- 39/39/37/37/0 0/0
Mar 14 08:28:06 np0005647024 haproxy[7]: 192.168.122.110:50554 [14/Mar/2026:08:28:06.576] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:06 np0005647024 haproxy[7]: 192.168.122.110:50558 [14/Mar/2026:08:28:06.835] redis redis/np0005647022.internalapi.localdomain 1/2/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:06 np0005647024 haproxy[7]: 192.168.122.110:50556 [14/Mar/2026:08:28:06.605] redis redis/np0005647022.internalapi.localdomain 1/0/241 4431 -- 39/39/37/37/0 0/0
Mar 14 08:28:07 np0005647024 haproxy[7]: 192.168.122.110:50566 [14/Mar/2026:08:28:07.120] redis redis/np0005647022.internalapi.localdomain 1/0/8 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:07 np0005647024 haproxy[7]: 192.168.122.110:50564 [14/Mar/2026:08:28:06.876] redis redis/np0005647022.internalapi.localdomain 1/0/252 4431 -- 38/38/37/37/0 0/0
Mar 14 08:28:10 np0005647024 haproxy[7]: 192.168.122.104:55046 [14/Mar/2026:08:28:10.763] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:10 np0005647024 haproxy[7]: 192.168.122.104:55030 [14/Mar/2026:08:28:10.510] redis redis/np0005647022.internalapi.localdomain 1/0/265 4430 -- 38/38/37/37/0 0/0
Mar 14 08:28:11 np0005647024 haproxy[7]: 192.168.122.104:55054 [14/Mar/2026:08:28:10.795] redis redis/np0005647022.internalapi.localdomain 1/1/283 4430 -- 39/39/37/37/0 0/0
Mar 14 08:28:11 np0005647024 haproxy[7]: 192.168.122.104:55056 [14/Mar/2026:08:28:11.069] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:11 np0005647024 haproxy[7]: 192.168.122.104:55060 [14/Mar/2026:08:28:11.358] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:11 np0005647024 haproxy[7]: 192.168.122.104:55058 [14/Mar/2026:08:28:11.111] redis redis/np0005647022.internalapi.localdomain 1/0/259 4432 -- 39/39/37/37/0 0/0
Mar 14 08:28:11 np0005647024 haproxy[7]: 192.168.122.104:55078 [14/Mar/2026:08:28:11.652] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:11 np0005647024 haproxy[7]: 192.168.122.104:55076 [14/Mar/2026:08:28:11.399] redis redis/np0005647022.internalapi.localdomain 1/0/264 4433 -- 38/38/37/37/0 0/0
Mar 14 08:28:12 np0005647024 haproxy[7]: 192.168.122.110:42978 [14/Mar/2026:08:28:12.402] redis redis/np0005647022.internalapi.localdomain 1/0/18 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:12 np0005647024 haproxy[7]: 192.168.122.110:42964 [14/Mar/2026:08:28:12.160] redis redis/np0005647022.internalapi.localdomain 1/0/261 4433 -- 38/38/37/37/0 0/0
Mar 14 08:28:12 np0005647024 haproxy[7]: 192.168.122.110:42998 [14/Mar/2026:08:28:12.700] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:12 np0005647024 haproxy[7]: 192.168.122.110:42994 [14/Mar/2026:08:28:12.447] redis redis/np0005647022.internalapi.localdomain 1/0/264 4433 -- 39/39/37/37/0 0/0
Mar 14 08:28:13 np0005647024 haproxy[7]: 192.168.122.110:43012 [14/Mar/2026:08:28:13.012] redis redis/np0005647022.internalapi.localdomain 1/0/8 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:13 np0005647024 haproxy[7]: 192.168.122.110:43000 [14/Mar/2026:08:28:12.727] redis redis/np0005647022.internalapi.localdomain 1/0/296 4433 -- 38/38/37/37/0 0/0
Mar 14 08:28:13 np0005647024 haproxy[7]: 192.168.122.110:43026 [14/Mar/2026:08:28:13.303] redis redis/np0005647022.internalapi.localdomain 1/0/6 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:13 np0005647024 haproxy[7]: 192.168.122.110:43014 [14/Mar/2026:08:28:13.047] redis redis/np0005647022.internalapi.localdomain 1/0/263 4433 -- 39/39/37/37/0 0/0
Mar 14 08:28:16 np0005647024 haproxy[7]: 192.168.122.104:60182 [14/Mar/2026:08:28:16.959] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:16 np0005647024 haproxy[7]: 192.168.122.104:60166 [14/Mar/2026:08:28:16.702] redis redis/np0005647022.internalapi.localdomain 1/0/267 4432 -- 38/38/37/37/0 0/0
Mar 14 08:28:17 np0005647024 haproxy[7]: 192.168.122.104:60192 [14/Mar/2026:08:28:17.231] redis redis/np0005647022.internalapi.localdomain 1/0/13 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:17 np0005647024 haproxy[7]: 192.168.122.104:60186 [14/Mar/2026:08:28:16.992] redis redis/np0005647022.internalapi.localdomain 1/0/252 4432 -- 39/39/37/37/0 0/0
Mar 14 08:28:17 np0005647024 haproxy[7]: 192.168.122.104:60210 [14/Mar/2026:08:28:17.528] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:17 np0005647024 haproxy[7]: 192.168.122.104:60194 [14/Mar/2026:08:28:17.262] redis redis/np0005647022.internalapi.localdomain 1/0/278 4433 -- 38/38/37/37/0 0/0
Mar 14 08:28:17 np0005647024 haproxy[7]: 192.168.122.104:60226 [14/Mar/2026:08:28:17.806] redis redis/np0005647022.internalapi.localdomain 1/0/9 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:17 np0005647024 haproxy[7]: 192.168.122.104:60214 [14/Mar/2026:08:28:17.561] redis redis/np0005647022.internalapi.localdomain 1/0/254 4433 -- 38/38/37/37/0 0/0
Mar 14 08:28:18 np0005647024 haproxy[7]: 192.168.122.110:43056 [14/Mar/2026:08:28:18.592] redis redis/np0005647022.internalapi.localdomain 1/0/13 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:18 np0005647024 haproxy[7]: 192.168.122.110:43042 [14/Mar/2026:08:28:18.364] redis redis/np0005647022.internalapi.localdomain 1/0/241 4434 -- 38/38/37/37/0 0/0
Mar 14 08:28:18 np0005647024 haproxy[7]: 192.168.122.110:43070 [14/Mar/2026:08:28:18.627] redis redis/np0005647022.internalapi.localdomain 1/0/290 4434 -- 39/39/38/38/0 0/0
Mar 14 08:28:18 np0005647024 haproxy[7]: 192.168.122.110:43084 [14/Mar/2026:08:28:18.903] redis redis/np0005647022.internalapi.localdomain 1/0/15 10 -- 38/38/37/37/0 0/0
Mar 14 08:28:19 np0005647024 haproxy[7]: 192.168.122.110:43090 [14/Mar/2026:08:28:18.938] redis redis/np0005647022.internalapi.localdomain 1/0/283 4434 -- 39/39/38/38/0 0/0
Mar 14 08:28:19 np0005647024 haproxy[7]: 192.168.122.110:43106 [14/Mar/2026:08:28:19.206] redis redis/np0005647022.internalapi.localdomain 1/0/14 10 -- 39/39/37/37/0 0/0
Mar 14 08:28:19 np0005647024 haproxy[7]: 192.168.122.110:43124 [14/Mar/2026:08:28:19.517] redis redis/np0005647022.internalapi.localdomain 1/0/12 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:19 np0005647024 haproxy[7]: 192.168.122.110:43108 [14/Mar/2026:08:28:19.254] redis redis/np0005647022.internalapi.localdomain 1/0/276 4434 -- 38/38/37/37/0 0/0
Mar 14 08:28:23 np0005647024 haproxy[7]: 192.168.122.104:59552 [14/Mar/2026:08:28:22.843] redis redis/np0005647022.internalapi.localdomain 1/0/236 4433 -- 39/39/38/38/0 0/0
Mar 14 08:28:23 np0005647024 haproxy[7]: 192.168.122.104:59566 [14/Mar/2026:08:28:23.069] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 38/38/37/37/0 0/0
Mar 14 08:28:23 np0005647024 haproxy[7]: 192.168.122.104:59588 [14/Mar/2026:08:28:23.355] redis redis/np0005647022.internalapi.localdomain 1/1/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:23 np0005647024 haproxy[7]: 192.168.122.104:59576 [14/Mar/2026:08:28:23.104] redis redis/np0005647022.internalapi.localdomain 1/0/263 4433 -- 39/39/37/37/0 0/0
Mar 14 08:28:23 np0005647024 haproxy[7]: 192.168.122.104:59614 [14/Mar/2026:08:28:23.637] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:23 np0005647024 haproxy[7]: 192.168.122.104:59604 [14/Mar/2026:08:28:23.389] redis redis/np0005647022.internalapi.localdomain 1/0/259 4433 -- 38/38/37/37/0 0/0
Mar 14 08:28:23 np0005647024 haproxy[7]: 192.168.122.104:59620 [14/Mar/2026:08:28:23.668] redis redis/np0005647022.internalapi.localdomain 1/0/270 4434 -- 39/39/38/38/0 0/0
Mar 14 08:28:23 np0005647024 haproxy[7]: 192.168.122.104:59636 [14/Mar/2026:08:28:23.927] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/37/37/0 0/0
Mar 14 08:28:24 np0005647024 haproxy[7]: 192.168.122.110:56526 [14/Mar/2026:08:28:24.801] redis redis/np0005647022.internalapi.localdomain 1/0/9 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:24 np0005647024 haproxy[7]: 192.168.122.110:56524 [14/Mar/2026:08:28:24.558] redis redis/np0005647022.internalapi.localdomain 1/0/253 4434 -- 38/38/37/37/0 0/0
Mar 14 08:28:25 np0005647024 haproxy[7]: 192.168.122.110:56550 [14/Mar/2026:08:28:25.067] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:25 np0005647024 haproxy[7]: 192.168.122.110:56536 [14/Mar/2026:08:28:24.834] redis redis/np0005647022.internalapi.localdomain 1/0/243 4434 -- 39/39/37/37/0 0/0
Mar 14 08:28:25 np0005647024 haproxy[7]: 192.168.122.110:56566 [14/Mar/2026:08:28:25.376] redis redis/np0005647022.internalapi.localdomain 1/0/11 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:25 np0005647024 haproxy[7]: 192.168.122.110:56562 [14/Mar/2026:08:28:25.107] redis redis/np0005647022.internalapi.localdomain 1/0/281 4434 -- 39/39/37/37/0 0/0
Mar 14 08:28:25 np0005647024 haproxy[7]: 192.168.122.110:56582 [14/Mar/2026:08:28:25.635] redis redis/np0005647022.internalapi.localdomain 1/0/8 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:25 np0005647024 haproxy[7]: 192.168.122.110:56578 [14/Mar/2026:08:28:25.409] redis redis/np0005647022.internalapi.localdomain 1/0/233 4434 -- 39/39/37/37/0 0/0
Mar 14 08:28:29 np0005647024 haproxy[7]: 192.168.122.104:59660 [14/Mar/2026:08:28:29.185] redis redis/np0005647022.internalapi.localdomain 1/0/9 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:29 np0005647024 haproxy[7]: 192.168.122.104:59648 [14/Mar/2026:08:28:28.958] redis redis/np0005647022.internalapi.localdomain 1/0/237 4433 -- 38/38/37/37/0 0/0
Mar 14 08:28:29 np0005647024 haproxy[7]: 192.168.122.104:59684 [14/Mar/2026:08:28:29.448] redis redis/np0005647022.internalapi.localdomain 1/0/10 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:29 np0005647024 haproxy[7]: 192.168.122.104:59674 [14/Mar/2026:08:28:29.213] redis redis/np0005647022.internalapi.localdomain 1/0/245 4433 -- 38/38/37/37/0 0/0
Mar 14 08:28:29 np0005647024 haproxy[7]: 192.168.122.104:59696 [14/Mar/2026:08:28:29.489] redis redis/np0005647022.internalapi.localdomain 1/0/286 4434 -- 39/39/38/38/0 0/0
Mar 14 08:28:29 np0005647024 haproxy[7]: 192.168.122.104:59700 [14/Mar/2026:08:28:29.768] redis redis/np0005647022.internalapi.localdomain 1/0/8 10 -- 38/38/37/37/0 0/0
Mar 14 08:28:30 np0005647024 haproxy[7]: 192.168.122.104:59728 [14/Mar/2026:08:28:30.082] redis redis/np0005647022.internalapi.localdomain 1/0/8 10 -- 39/39/38/38/0 0/0
Mar 14 08:28:30 np0005647024 haproxy[7]: 192.168.122.104:59716 [14/Mar/2026:08:28:29.800] redis redis/np0005647022.internalapi.localdomain 1/0/289 4434 -- 39/39/37/37/0 0/0
Mar 14 08:28:30 np0005647024 haproxy[7]: 192.168.122.103:40892 [14/Mar/2026:08:28:30.839] redis redis/np0005647022.internalapi.localdomain 1/0/33 14 -- 39/39/38/38/0 0/0
Mar 14 08:28:36 np0005647024 haproxy[7]: Server gnocchi/np0005647022.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.