proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: Starting Keystone auth_token middleware
The option "bind_ip" is not known to keystonemiddleware
The option "bind_port" is not known to keystonemiddleware
The option "log_name" is not known to keystonemiddleware
The option "auth_url" is not known to keystonemiddleware
The option "project_domain_id" is not known to keystonemiddleware
The option "user_domain_id" is not known to keystonemiddleware
The option "project_name" is not known to keystonemiddleware
The option "username" is not known to keystonemiddleware
The option "password" is not known to keystonemiddleware
The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: Started child 5 from parent 1
proxy-server: Started child 6 from parent 1
proxy-server: Started child 7 from parent 1
proxy-server: Started child 8 from parent 1
proxy-server: Started child 9 from parent 1
proxy-server: Started child 10 from parent 1
proxy-server: Started child 11 from parent 1
proxy-server: Started child 12 from parent 1
proxy-server: Started child 13 from parent 1
proxy-server: Started child 14 from parent 1
proxy-server: Started child 15 from parent 1
proxy-server: Started child 16 from parent 1
proxy-server: Started child 17 from parent 1
proxy-server: Started child 18 from parent 1
proxy-server: Started child 19 from parent 1
proxy-server: Started child 20 from parent 1
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: Starting Keystone auth_token middleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: Starting Keystone auth_token middleware
proxy-server: Starting Keystone auth_token middleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: Starting Keystone auth_token middleware
proxy-server: Starting Keystone auth_token middleware
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: Starting Keystone auth_token middleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: Starting Keystone auth_token middleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: Starting Keystone auth_token middleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: Starting Keystone auth_token middleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: Starting Keystone auth_token middleware
proxy-server: Starting Keystone auth_token middleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: Starting Keystone auth_token middleware
proxy-server: Starting Keystone auth_token middleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: The following digest algorithms are allowed by default but deprecated: sha1. Support will be disabled by default in a future release, and later removed entirely.
proxy-server: Starting Keystone auth_token middleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: Starting Keystone auth_token middleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: Starting Keystone auth_token middleware
proxy-server: STDERR: The option "bind_ip" is not known to keystonemiddleware
proxy-server: STDERR: The option "bind_port" is not known to keystonemiddleware
proxy-server: STDERR: The option "log_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "auth_url" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "user_domain_id" is not known to keystonemiddleware
proxy-server: STDERR: The option "project_name" is not known to keystonemiddleware
proxy-server: STDERR: The option "username" is not known to keystonemiddleware
proxy-server: STDERR: The option "password" is not known to keystonemiddleware
proxy-server: STDERR: The option "__name__" is not known to keystonemiddleware
proxy-server: AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.143 127.0.0.1 11/Oct/2025/10/55/50 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6je149AU... - 2 - txba84ec08a5fa4dfcb54fd-0068ea37b6 - 0.7346 - - 1760180150.217203856 1760180150.951785326 -
proxy-server: 10.129.0.143 127.0.0.1 11/Oct/2025/10/55/51 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6je149AU... - 2 - tx3240dcb9278f4d9086cdb-0068ea37b6 - 0.0349 - - 1760180150.966442585 1760180151.001372576 -
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.143 127.0.0.1 11/Oct/2025/10/55/51 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6je149AU... - - - tx30978fb89bcd480ca63fd-0068ea37b7 - 0.6394 - - 1760180151.017194033 1760180151.656624794 -
proxy-server: 10.129.0.143 127.0.0.1 11/Oct/2025/10/55/51 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6je149AU... - - - tx66c3424f550747afb5109-0068ea37b7 - 0.0256 - - 1760180151.672572613 1760180151.698153019 -
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.147 127.0.0.1 11/Oct/2025/10/56/05 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jfELWLJ... - - - tx19a8387dd269467a9b6d1-0068ea37c5 - 0.5956 - - 1760180165.060828447 1760180165.656474590 -
proxy-server: 10.129.0.147 127.0.0.1 11/Oct/2025/10/56/05 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jfELWLJ... - - - tx3ffbaced76594294ab3ae-0068ea37c5 - 0.0234 - - 1760180165.673862219 1760180165.697301388 -
proxy-server: 10.129.0.147 127.0.0.1 11/Oct/2025/10/56/06 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jfELWLJ... - 2 - tx718068ecb4f04320806a7-0068ea37c6 - 0.0131 - - 1760180166.534561396 1760180166.547647953 -
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.147 127.0.0.1 11/Oct/2025/10/56/07 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jfELWLJ... - 2 - tx1bac506d592044f4ae068-0068ea37c6 - 0.5112 - - 1760180166.566981077 1760180167.078189850 -
proxy-server: 10.129.0.163 127.0.0.1 11/Oct/2025/10/56/52 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jf09osF... - - - tx88080d1b6bab452ab7569-0068ea37f4 - 0.1901 - - 1760180212.368843079 1760180212.558970690 -
proxy-server: 10.129.0.163 127.0.0.1 11/Oct/2025/10/56/52 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jf09osF... - - - txfbc0ad625be345bbb567b-0068ea37f4 - 0.0215 - - 1760180212.588149548 1760180212.609618902 -
proxy-server: 10.129.0.163 127.0.0.1 11/Oct/2025/10/56/55 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jf09osF... - 2 - tx2b082d7ed38b4c78a89d5-0068ea37f7 - 0.1067 - - 1760180215.582471371 1760180215.689133167 -
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.163 127.0.0.1 11/Oct/2025/10/56/56 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jf09osF... - 2 - txbd803ccfc95b443bb2b27-0068ea37f7 - 0.4574 - - 1760180215.719039917 1760180216.176403046 -
proxy-server: 10.129.0.165 127.0.0.1 11/Oct/2025/10/57/03 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jf_-3NR... - 2 - tx78a950f82c8049bc93335-0068ea37ff - 0.0793 - - 1760180223.906056643 1760180223.985378504 -
proxy-server: 10.129.0.165 127.0.0.1 11/Oct/2025/10/57/04 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jf_-3NR... - 2 - tx1e4f6bcb3afd4948bb166-0068ea3800 - 0.0874 - - 1760180224.016222477 1760180224.103610039 -
proxy-server: 10.129.0.165 127.0.0.1 11/Oct/2025/10/57/04 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jf_-3NR... - - - tx7322a53c6e96479f803d8-0068ea3800 - 0.1065 - - 1760180224.131885529 1760180224.238360882 -
proxy-server: 10.129.0.165 127.0.0.1 11/Oct/2025/10/57/04 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jf_-3NR... - - - tx86401d5f3bd4401892ceb-0068ea3800 - 0.0088 - - 1760180224.270505190 1760180224.279274225 -
proxy-server: 10.129.0.169 127.0.0.1 11/Oct/2025/10/57/18 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jgNMQWI... - - - txc6b88579fb234d24b9a74-0068ea380e - 0.3480 - - 1760180238.029424191 1760180238.377416372 -
proxy-server: 10.129.0.169 127.0.0.1 11/Oct/2025/10/57/18 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jgNMQWI... - - - tx0565791eb911425b9abe3-0068ea380e - 0.0135 - - 1760180238.401890755 1760180238.415352106 -
proxy-server: 10.129.0.169 127.0.0.1 11/Oct/2025/10/57/19 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jgNMQWI... - 2 - tx5f87e8f3ae97417e880ac-0068ea380f - 0.0729 - - 1760180239.854161739 1760180239.927033663 -
proxy-server: 10.129.0.169 127.0.0.1 11/Oct/2025/10/57/19 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jgNMQWI... - 2 - tx7bf6af252fa94f86a8ca7-0068ea380f - 0.0081 - - 1760180239.974471331 1760180239.982601643 -
proxy-server: 10.129.0.173 127.0.0.1 11/Oct/2025/10/57/28 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jgY1K4T... - - - tx0098c03b9a05484fb7603-0068ea3818 - 0.1048 - - 1760180248.388390064 1760180248.493173838 -
proxy-server: 10.129.0.173 127.0.0.1 11/Oct/2025/10/57/28 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jgY1K4T... - - - txafe1a933dfdb4fb385466-0068ea3818 - 0.0167 - - 1760180248.522877693 1760180248.539554596 -
proxy-server: 10.129.0.173 127.0.0.1 11/Oct/2025/10/57/29 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jgY1K4T... - 2 - tx991be6b468364ac8b089e-0068ea3819 - 0.0168 - - 1760180249.823089361 1760180249.839872837 -
proxy-server: 10.129.0.173 127.0.0.1 11/Oct/2025/10/57/29 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jgY1K4T... - 2 - txadc7649af8c440cab03ec-0068ea3819 - 0.0877 - - 1760180249.879645109 1760180249.967355251 -
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.173 127.0.0.1 11/Oct/2025/11/02/26 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jlBKBUF... - 2 - tx397d6fa6c2954d7881d7e-0068ea3942 - 0.4719 - - 1760180546.041888714 1760180546.513786793 -
proxy-server: 10.129.0.173 127.0.0.1 11/Oct/2025/11/02/26 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jlBKBUF... - 2 - txa72a5a981963438a9aefd-0068ea3942 - 0.0279 - - 1760180546.577347517 1760180546.605210543 -
proxy-server: 10.129.0.173 127.0.0.1 11/Oct/2025/11/02/26 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jlBKBUF... - - - tx89972f8a286f482189848-0068ea3942 - 0.0087 - - 1760180546.635130405 1760180546.643826723 -
proxy-server: 10.129.0.173 127.0.0.1 11/Oct/2025/11/02/26 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jlBKBUF... - - - txc9201136fb3e4c8a8c7ab-0068ea3942 - 0.0085 - - 1760180546.669759989 1760180546.678231716 -
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.185 127.0.0.1 11/Oct/2025/11/03/07 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jlqQH_w... - 2 - tx8a322ba73c084fcf996f3-0068ea396a - 0.7512 - - 1760180586.785142183 1760180587.536319494 -
proxy-server: 10.129.0.185 127.0.0.1 11/Oct/2025/11/03/07 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jlqQH_w... - 2 - txe855a8b13c1146da9dcb8-0068ea396b - 0.0193 - - 1760180587.559552431 1760180587.578826427 -
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.185 127.0.0.1 11/Oct/2025/11/03/08 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jlqQH_w... - - - txa7f94b13ffbb49b4b8717-0068ea396b - 0.4542 - - 1760180587.598612785 1760180588.052806616 -
proxy-server: 10.129.0.185 127.0.0.1 11/Oct/2025/11/03/08 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jlqQH_w... - - - tx862a749cb995407dbfcc5-0068ea396c - 0.0886 - - 1760180588.076192856 1760180588.164769173 -
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.148 127.0.0.1 11/Oct/2025/11/03/32 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8/glance%3Fformat%3Djson HTTP/1.0 404 - python-swiftclient-4.2.0 gAAAAABo6jmEJxJZ... - - - tx76ad357990cc476f9afaa-0068ea3984 - 0.5333 - - 1760180612.447512388 1760180612.980820894 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/03/33 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jmEZWCY... - 2 - tx9b8d8687b7a94eaabb692-0068ea3984 - 0.5747 - - 1760180612.450173140 1760180613.024828434 -
proxy-server: autocreate account '/AUTH_18af13ddd95e45ae9810b2bdd9367db8' (txn: txff49c6809b7e4c64aa105-0068ea3984)
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/03/33 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jmEZWCY... - 91 - txa818057cf87f4bbe8186f-0068ea3985 - 0.1161 - - 1760180613.054800749 1760180613.170910358 -
proxy-server: 10.129.0.148 127.0.0.1 11/Oct/2025/11/03/33 PUT /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8/glance HTTP/1.0 201 - python-swiftclient-4.2.0 gAAAAABo6jmEJxJZ... - - - txff49c6809b7e4c64aa105-0068ea3984 - 0.1805 - - 1760180612.995194674 1760180613.175668001 0
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/03/33 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jmEZWCY... - - - txfc0bb30b0b304398bc221-0068ea3985 - 0.0125 - - 1760180613.277570963 1760180613.290057659 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/03/33 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 204 - python-swiftclient-4.2.0 gAAAAABo6jmEZWCY... - - - tx7224e5f630e94b77ad8af-0068ea3985 - 0.0216 - - 1760180613.334808350 1760180613.356428385 -
proxy-server: 10.129.0.148 127.0.0.1 11/Oct/2025/11/03/34 PUT /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8/glance/29e6b576-dfeb-4e24-9911-7463f66f364b-00001 HTTP/1.0 201 - python-swiftclient-4.2.0 gAAAAABo6jmEJxJZ... 204800000 - - tx5748135261c14e64a57d8-0068ea3985 - 1.6708 - - 1760180613.223775148 1760180614.894581556 0
proxy-server: 10.129.0.148 127.0.0.1 11/Oct/2025/11/03/36 PUT /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8/glance/29e6b576-dfeb-4e24-9911-7463f66f364b-00002 HTTP/1.0 201 - python-swiftclient-4.2.0 gAAAAABo6jmEJxJZ... 204800000 - - tx1e7b70752c1b4ac88278e-0068ea3986 - 1.6639 - - 1760180614.908407927 1760180616.572282553 0
proxy-server: 10.129.0.148 127.0.0.1 11/Oct/2025/11/03/37 PUT /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8/glance/29e6b576-dfeb-4e24-9911-7463f66f364b-00003 HTTP/1.0 201 - python-swiftclient-4.2.0 gAAAAABo6jmEJxJZ... 120611328 - - tx1c757c5b57684d9a8314e-0068ea3988 - 0.9450 - - 1760180616.584698439 1760180617.529719830 0
proxy-server: 10.129.0.148 127.0.0.1 11/Oct/2025/11/03/37 PUT /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8/glance/29e6b576-dfeb-4e24-9911-7463f66f364b HTTP/1.0 201 - python-swiftclient-4.2.0 gAAAAABo6jmEJxJZ... - - - tx01d1aa1042814dbc8cc83-0068ea3989 - 0.0802 - - 1760180617.541702986 1760180617.621886969 0
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/08/32 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jquvfUM... - 2 - txa84c512247d74bb8bf990-0068ea3aaf - 0.6109 - - 1760180911.493869781 1760180912.104767799 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/08/32 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jquvfUM... - 99 - tx111e46eb4964426dbb673-0068ea3ab0 - 0.0335 - - 1760180912.148351908 1760180912.181878805 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/08/32 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jquvfUM... - - - txbb638d83ab6a4fd7899e8-0068ea3ab0 - 0.0125 - - 1760180912.223971128 1760180912.236460686 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/08/32 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 204 - python-swiftclient-4.2.0 gAAAAABo6jquvfUM... - - - txfffc6c8df8754f0fbe1bc-0068ea3ab0 - 0.0717 - - 1760180912.259152651 1760180912.330874920 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/13/31 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jva4XHb... - - - tx874ddd8c4ec14ca799900-0068ea3bdb - 0.1239 - - 1760181211.120049953 1760181211.243962288 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/13/31 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 204 - python-swiftclient-4.2.0 gAAAAABo6jva4XHb... - - - tx82bfb938fe5f4337b633e-0068ea3bdb - 0.0826 - - 1760181211.275506973 1760181211.358127594 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/13/31 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jva4XHb... - 2 - tx20e426ebe768452d991b0-0068ea3bdb - 0.0108 - - 1760181211.409854889 1760181211.420694113 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/13/31 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6jva4XHb... - 99 - tx7f0a76a36ea440a19b9b0-0068ea3bdb - 0.0174 - - 1760181211.451329231 1760181211.468732119 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/18/31 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6j0HLozM... - - - txca4152e609df42e8b30d3-0068ea3d07 - 0.1745 - - 1760181511.421575785 1760181511.596031904 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/18/31 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 204 - python-swiftclient-4.2.0 gAAAAABo6j0HLozM... - - - tx45b6d88d70d54bcb8589d-0068ea3d07 - 0.1720 - - 1760181511.629271746 1760181511.801271439 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/18/31 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6j0HLozM... - 2 - txa12738d5c6dc4999bd4d8-0068ea3d07 - 0.0092 - - 1760181511.857026815 1760181511.866192102 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/18/31 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6j0HLozM... - 99 - tx1cf8b453c42c4ae78a1bf-0068ea3d07 - 0.0145 - - 1760181511.889855862 1760181511.904334068 -
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/23/32 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6j4ydMY_... - - - tx0fc22838c1d94805ad530-0068ea3e33 - 0.6252 - - 1760181811.536603689 1760181812.161830425 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/23/32 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 204 - python-swiftclient-4.2.0 gAAAAABo6j4ydMY_... - - - tx6672fb5292744bdeab98c-0068ea3e34 - 0.0441 - - 1760181812.201315165 1760181812.245381117 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/23/32 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6j4ydMY_... - 2 - tx4560fbfe7c94408aafb86-0068ea3e34 - 0.1262 - - 1760181812.549671412 1760181812.675870419 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/23/32 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6j4ydMY_... - 99 - tx5ae8613d20ef48e799d57-0068ea3e34 - 0.0120 - - 1760181812.703176260 1760181812.715177774 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/28/31 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6j9eEQMi... - - - tx18225a88163a4abbbfb87-0068ea3f5f - 0.1014 - - 1760182111.075098515 1760182111.176529646 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/28/31 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 204 - python-swiftclient-4.2.0 gAAAAABo6j9eEQMi... - - - txe89c1c63807544ba9ae28-0068ea3f5f - 0.1474 - - 1760182111.216654301 1760182111.364061594 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/28/31 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6j9eEQMi... - 2 - tx9b837304e2174054882d6-0068ea3f5f - 0.0997 - - 1760182111.839484930 1760182111.939171553 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/28/31 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6j9eEQMi... - 99 - txc581345b4595465885552-0068ea3f5f - 0.0140 - - 1760182111.977526426 1760182111.991508484 -
proxy-server: Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/33/31 GET /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6kCKtU6w... - 2 - tx660d6b42a9784bf29a36c-0068ea408b - 0.5063 - - 1760182411.265580654 1760182411.771928787 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/33/31 GET /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6kCKtU6w... - 99 - tx4f1cebb7b7034947bec99-0068ea408b - 0.1755 - - 1760182411.801975250 1760182411.977451086 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/33/32 HEAD /v1/AUTH_2332d0b478da4463a529bc6a41906a80%3Fformat%3Djson HTTP/1.0 200 - python-swiftclient-4.2.0 gAAAAABo6kCKtU6w... - - - tx1e6ce28eea1d49228d8b7-0068ea408c - 0.0073 - - 1760182412.016136885 1760182412.023484707 -
proxy-server: 10.129.0.190 127.0.0.1 11/Oct/2025/11/33/32 HEAD /v1/AUTH_18af13ddd95e45ae9810b2bdd9367db8%3Fformat%3Djson HTTP/1.0 204 - python-swiftclient-4.2.0 gAAAAABo6kCKtU6w... - - - txf347bedc1a854a47a2487-0068ea408c - 0.0120 - - 1760182412.044280052 1760182412.056246042 -