Sapos's profile - activity

2017-05-23 05:42:55 -0600 received badge  Famous Question (source)
2017-05-23 05:42:55 -0600 received badge  Notable Question (source)
2017-04-06 11:33:04 -0600 received badge  Popular Question (source)
2017-04-06 10:22:54 -0600 received badge  Self-Learner (source)
2017-04-06 10:22:54 -0600 received badge  Teacher (source)
2017-04-06 10:09:00 -0600 answered a question neutron 503 Service Unavailable

Problem solved! I've just recreated the neutron user with new password and now it works fine. Thanks!

2017-04-06 02:20:46 -0600 commented question neutron 503 Service Unavailable

Yes, here is the neutron.conf - http://paste.openstack.org/show/605588/

2017-04-05 10:46:43 -0600 asked a question neutron 503 Service Unavailable

Hello! Have a problem with neutron server (Mitaka release). Trying to request neutron agent-list and got error:

503 Service Unavailable

The server is currently unavailable. Please try again at a later time.


Neutron server returns request_ids: ['req-606b5567-3ba5-4196-a45f-15baa05ef9f7']

The neutron --debug agent-list says:

DEBUG: keystoneauth.session REQ: curl -g -i -X GET http://10.65.100.40:35357/v3 -H "Accept: application/json" -H "User-Agent: keystoneauth1/2.4.1 python-requests/2.9.1 CPython/2.7.12"
DEBUG: keystoneauth.session RESP: [200] Content-Length: 252 Vary: X-Auth-Token Keep-Alive: timeout=5, max=100 Server: Apache/2.4.18 (Ubuntu) Connection: Keep-Alive Date: Wed, 05 Apr 2017 15:36:39 GMT x-openstack-request-id: req-b6863870-a945-44c2-ba82-7599c84ff555 Content-Type: application/json X-Distribution: Ubuntu 
RESP BODY: {"version": {"status": "stable", "updated": "2016-04-04T00:00:00Z", "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v3+json"}], "id": "v3.6", "links": [{"href": "http://10.65.100.40:35357/v3/", "rel": "self"}]}}

DEBUG: keystoneauth.identity.v3.base Making authentication request to http://10.65.100.40:35357/v3/auth/tokens
DEBUG: keystoneauth.session REQ: curl -g -i -X GET http://10.65.100.40:9696/v2.0/agents.json -H "User-Agent: python-neutronclient" -H "Accept: application/json" -H "X-Auth-Token: {SHA1}a9f8fbe6347d8523b3e9e1cbc804fdd9f2f5f432"
DEBUG: keystoneauth.session RESP: [503] Date: Wed, 05 Apr 2017 15:36:39 GMT Connection: keep-alive Content-Type: text/plain; charset=UTF-8 Content-Length: 100 X-Openstack-Request-Id: req-f9b01550-03d5-458d-992f-e786c04b4aef 
RESP BODY: 503 Service Unavailable

The server is currently unavailable. Please try again at a later time.



DEBUG: neutronclient.v2_0.client Error message: 503 Service Unavailable

The server is currently unavailable. Please try again at a later time.


ERROR: neutronclient.shell 503 Service Unavailable

The server is currently unavailable. Please try again at a later time.


Neutron server returns request_ids: ['req-f9b01550-03d5-458d-992f-e786c04b4aef']
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/neutronclient/shell.py", line 879, in run_subcommand
    return run_command(cmd, cmd_parser, sub_argv)
  File "/usr/lib/python2.7/dist-packages/neutronclient/shell.py", line 114, in run_command
    return cmd.run(known_args)
  File "/usr/lib/python2.7/dist-packages/neutronclient/neutron/v2_0/__init__.py", line 403, in run
    return super(NeutronCommand, self).run(parsed_args)
  File "/usr/lib/python2.7/dist-packages/cliff/display.py", line 92, in run
    column_names, data = self.take_action(parsed_args)
  File "/usr/lib/python2.7/dist-packages/neutronclient/neutron/v2_0/__init__.py", line 766, in take_action
    data = self.retrieve_list(parsed_args)
  File "/usr/lib/python2.7/dist-packages/neutronclient/neutron/v2_0/__init__.py", line 730, in retrieve_list
    data = self.call_server(neutron_client, search_opts, parsed_args)
  File "/usr/lib/python2.7/dist-packages/neutronclient/neutron/v2_0/__init__.py", line 703, in call_server
    data = obj_lister(**search_opts)
  File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 97, in with_params
    ret = self.function(instance, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 1409, in list_agents
    return self.get(self.agents_path, params=_params)
  File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 358, in get
    headers=headers, params=params)
  File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 335, in retry_request
    headers=headers, params=params)
  File "/usr/lib/python2.7 ...
(more)
2017-02-09 11:47:05 -0600 received badge  Famous Question (source)
2016-09-13 08:31:40 -0600 received badge  Famous Question (source)
2016-08-19 09:53:53 -0600 received badge  Notable Question (source)
2016-06-30 08:11:14 -0600 received badge  Popular Question (source)
2016-06-29 09:21:48 -0600 answered a question Dashboard console - Keyboard and mouse issue in Linux graphical environmevt

The problem is solved, it was on CentOS xorg config side. To fix it it need to add folowing linet to /etc/X11/xorg.conf.d/xorg-auto-add-devices.conf:

Section "ServerFlags"
        Option "AutoAddDevices" "off"
EndSection

Next restart X server: init3 and then init 5

2016-06-17 08:07:00 -0600 asked a question Dashboard console - Keyboard and mouse issue in Linux graphical environmevt

Hello!

Faced a problem: nova novnc console doesn't react on any mouse movements and keyboard presses in CensOS 6.4 instance graphical environment. It does not happen in cli environment. Nevertheless, it possible to connect to the instance desktop via VNC and it works good. OpenStack: RDO Kilo.

Any ideas why?

Thanks a lot!

2016-05-23 05:26:18 -0600 received badge  Notable Question (source)
2016-05-13 03:03:51 -0600 received badge  Enthusiast
2016-05-12 00:27:09 -0600 received badge  Popular Question (source)
2016-05-11 09:53:12 -0600 received badge  Editor (source)
2016-05-11 09:04:45 -0600 asked a question Unable to change password (Horizon)

Hello!

Have an environment based on Icehouse OpenStack release (2014.1.3). An attempt to change user own password via dashboard leads to an error: "Unable to change password". The user has "_member_" role. Apache error.log shows this picture:

Not Found: The resource could not be found. (HTTP 404)
Traceback (most recent call last):
   File "/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/settings/password/forms.py", line 61, in handle
     data['new_password'])
   File "/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/keystone.py", line 401, in user_update_own_password
     return client.users.update_own_password(origpassword, password)
   File "/usr/lib/python2.7/dist-packages/keystoneclient/v2_0/users.py", line 77, in update_own_password
     management=False)
   File "/usr/lib/python2.7/dist-packages/keystoneclient/base.py", line 206, in _update
     management=management)
   File "/usr/lib/python2.7/dist-packages/keystoneclient/httpclient.py", line 602, in patch
     return self._cs_request(url, 'PATCH', **kwargs)
   File "/usr/lib/python2.7/dist-packages/keystoneclient/httpclient.py", line 582, in _cs_request
     return self.request(url, method, **kwargs)
   File "/usr/lib/python2.7/dist-packages/keystoneclient/httpclient.py", line 564, in request
     resp = super(HTTPClient, self).request(url, method, **kwargs)]   File "/usr/lib/python2.7/dist-packages/keystoneclient/baseclient.py", line 21, in request
     return self.session.request(url, method, **kwargs)
   File "/usr/lib/python2.7/dist-packages/keystoneclient/utils.py", line 318, in inner
     return func(*args, **kwargs)
   File "/usr/lib/python2.7/dist-packages/keystoneclient/session.py", line 251, in request
     raise exceptions.from_response(resp, method, url)
 NotFound: The resource could not be found. (HTTP 404)

At the same time a similar attempt to change password in Kilo (2015.1.1) ends successful. I couldn't find any significant code difference in forms.py and keystone.py.

Does anybody have any ideas why is the error occurs?

Thanks!

UPDATE

Changing password via keystone user-password-update command for the same user works fine.

2015-01-30 01:57:22 -0600 received badge  Famous Question (source)
2014-09-30 14:48:07 -0600 received badge  Notable Question (source)
2014-07-29 04:15:50 -0600 received badge  Nice Question (source)
2014-07-01 08:43:09 -0600 received badge  Popular Question (source)
2014-06-26 01:23:27 -0600 received badge  Student (source)
2014-06-04 08:25:35 -0600 received badge  Famous Question (source)
2014-05-16 12:17:24 -0600 received badge  Famous Question (source)
2014-05-12 08:50:44 -0600 asked a question swift check cluster health

Can't use swift-dispersion tools for cluster health check. Conf file crated:

[root@swift-proxy01 swift]# cat /etc/swift/dispersion.conf
[dispersion]
auth_url = http://192.168.1.29/auth/v2.0
auth_user = admin:swift
auth_key = swift
endpoint_type = http://192.168.1.30/v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb
swift_dir = /etc/swift

When I'm trying use swift-dispersion-populate command I've got error:

[root@swift-proxy01 swift]# swift-dispersion-populate
Traceback (most recent call last):
  File "/usr/bin/swift-dispersion-populate", line 133, in <module>
    insecure=insecure)
  File "/usr/lib/python2.6/site-packages/swiftclient/client.py", line 317, in get_auth
    insecure=insecure)
  File "/usr/lib/python2.6/site-packages/swiftclient/client.py", line 227, in get_auth_1_0
    {'X-Auth-User': user, 'X-Auth-Key': key})
  File "/usr/lib/python2.6/site-packages/swiftclient/client.py", line 187, in request
    files=files, **self.requests_args)
  File "/usr/lib/python2.6/site-packages/swiftclient/client.py", line 176, in _request
    return requests.request(*arg, **kwarg)
  File "/usr/lib/python2.6/site-packages/requests/api.py", line 44, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/lib/python2.6/site-packages/requests/sessions.py", line 279, in request
    resp = self.send(prep, stream=stream, timeout=timeout, verify=verify, cert=cert, proxies=proxies)
  File "/usr/lib/python2.6/site-packages/requests/sessions.py", line 374, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python2.6/site-packages/requests/adapters.py", line 206, in send
    raise ConnectionError(sockerr)
requests.exceptions.ConnectionError: [Errno 111] ECONNREFUSED

In logs I see this one:

May 12 17:43:48 swift-proxy01 abrt: detected unhandled Python exception in '/usr/bin/swift-dispersion-populate'
May 12 17:43:48 swift-proxy01 abrtd: New client connected
May 12 17:43:48 swift-proxy01 abrtd: Directory 'pyhook-2014-05-12-17:43:48-32321' creation detected
May 12 17:43:48 swift-proxy01 abrt-server[32328]: Saved Python crash dump of pid 32321 to /var/spool/abrt/pyhook-2014-05-12-17:43:48-32321
May 12 17:43:48 swift-proxy01 abrtd: Package 'openstack-swift' isn't signed with proper key
May 12 17:43:48 swift-proxy01 abrtd: 'post-create' on '/var/spool/abrt/pyhook-2014-05-12-17:43:48-32321' exited with 1
May 12 17:43:48 swift-proxy01 abrtd: Corrupted or bad directory '/var/spool/abrt/pyhook-2014-05-12-17:43:48-32321', deleting

What am I doing wrong?

Thanks!

2014-05-12 08:07:03 -0600 received badge  Notable Question (source)
2014-05-08 08:09:23 -0600 received badge  Popular Question (source)
2014-05-07 13:27:28 -0600 marked best answer swift [Errno 111] Connection refused

Hello Dears!

Have a problem with configuring Opensatck object storage with Openstack Identity service. I installed 5 Swift nodes and 1 proxy server. Also created swift user, siwft service and endpoint. But when I'm trying to verify the installation I got the error.

[root@swift-proxy01 ~]# swift -V 2.0 -A http://192.168.1.29:5000/v2.0 -U admin:swift -K $PASS stat
[Errno 111] Connection refused
[root@swift-proxy01 ~]#
[root@swift-proxy01 ~]#
[root@swift-proxy01 ~]# swift -V 2.0 -A http://192.168.1.29:5000/v2.0 -U admin:admin -K $ADMINPASS stat
[Errno 111] Connection refused

Here is my settings and created entities:

    [root@swift-keystone ~]# keystone user-list
    +----------------------------------+-------+---------+-------------------+
    |                id                |  name | enabled |       email       |
    +----------------------------------+-------+---------+-------------------+
    | 27e3dccc6bb645639ed1cba4470691cc | admin |   True  | admin@example.com |
    | e7bbd749c7da4767a4dda4ccd6f09121 | swift |   True  | swift@example.com |
    | 9502088d2f234e16a0a5c8e98a01ab7a |  test |   True  |  test@example.com |
    +----------------------------------+-------+---------+-------------------+
    [root@swift-keystone ~]# keystone tenant-list
    +----------------------------------+-------------+---------+
    |                id                |     name    | enabled |
    +----------------------------------+-------------+---------+
    | 18c35fb509b84966aa7e5734eebdf8fb |    admin    |   True  |
    | 69f602380fa244ae8e96181c39b9beb8 |   service   |   True  |
    | 2a9bdeaf88df433d8db2e8673b26f706 | test-tenant |   True  |
    +----------------------------------+-------------+---------+
    [root@swift-keystone ~]# keystone service-list
+----------------------------------+----------+--------------+---------------------------+
|                id                |   name   |     type     |        description        |
+----------------------------------+----------+--------------+---------------------------+
| 7af9c013ac084594a13aeb50bab57ef3 | keystone |   identity   | Keystone Identity Service |
| 9bac694982ae466ca53a2f9f1477d4ef |  swift   | object-store |       Swift service       |
+----------------------------------+----------+--------------+---------------------------+

Swift Endpoint URLs:

     Swift endpoint publicurl - http://192.168.1.30/v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb
     Swift endpoint internalurl -  http://192.168.1.30/v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb
     Swift endpoint adminurl - http://192.168.1.30/v1

Swift proxy config:

[DEFAULT]
bind_port = 8080
workers = 8
user = swift

[pipeline:main]
pipeline = healthcheck cache authtoken keystone proxy-server

[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true

[filter:cache]
use = egg:swift#memcache
memcache_servers = 192.168.1.30:11211

[filter:catch_errors]
use = egg:swift#catch_errors

[filter:healthcheck]
use = egg:swift#healthcheck

[filter:keystone]
use = egg:swift#keystoneauth
operator_roles = admin, SwiftOperator
is_admin = true
cache = swift.cache

[filter:authtoken]
paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory
delay_auth_decision = true
admin_tenant_name = admin
admin_user = swift
admin_password = swift
auth_host = 192.168.1.29
auth_port = 35357
auth_protocol = http
signing_dir = /tmp/keystone-signing-swift
admin_token = 1be8dc4d9d149bdd5f86
auth_uri=http://192.168.1.29:5000

Logs on keystone server are empty:

2014-05-06 12:23:49.393 2818 INFO keystone.common.environment [-] Environment configured as: eventlet
2014-05-06 12:23:49.716 2818 INFO keystone.common.environment.eventlet_server [-] Starting /usr/bin/keystone-all on 0.0.0.0:35357
2014-05-06 12:23:49.723 2818 INFO keystone.common.environment.eventlet_server [-] Starting /usr/bin/keystone-all on 0.0.0.0:5000

I have rtied to reinstall identity service and create all from scratch but there is nothing changed. Please help, I can't understand where am I wrong.

Thanks a lot!

2014-05-07 07:19:59 -0600 commented question swift Account HEAD 503 Internal Server Error

Yes, all services are started. But i think i found something. I've tried a couple of commands:

 curl http://10.10.2.31:6002
curl: (7) couldn't connect to host
[root@swift-proxy01 swift]# telnet 10.10.2.31 6002
Trying 10.10.2.31...
telnet: connect to address 10.10.2.31: Connection refused

Then I've tried to change bind_ip in account-server.conf on first storage node from 127.0.0.1 to 10.10.2.31. And it looks like it worked:

[root@swift-proxy01 swift]# swift -V 2.0 -A http://192.168.1.29:5000/v2.0 -U admin:admin -K 12345As stat
       Account: AUTH_18c35fb509b84966aa7e5734eebdf8fb
    Containers: 0
       Objects: 0
         Bytes: 0
  Content-Type: text/plain; charset=utf-8
   X-Timestamp: 1399464488.50562
    X-Trans-Id: txf9dde858cb62485ca042e-00536a2228
X-Put-Timestamp: 1399464488.50562

What about bind_ip option in account, container and object config files on storage nodes and proxy server nodes? Where exactly I ... (more)

2014-05-07 06:53:49 -0600 commented question swift Account HEAD 503 Internal Server Error

I have added option "mount_check = false" on all nodes and on proxy server in account, container and object config files, then I restarted all services, but there is no any effect. Still have the problem.

2014-05-07 04:15:10 -0600 asked a question swift Account HEAD 503 Internal Server Error

Hallo!

Can't verify swift stat:

  [root@swift-proxy01 swift]# swift -V 2.0 -A http://192.168.1.29:5000/v2.0 -U admin:admin -K 12345As stat
    Account HEAD failed: http://192.168.1.30/v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb 503 Internal Server Error

In proxy log I see:

May  7 13:04:55 swift-proxy01 proxy-server: Account HEAD returning 503 for [] (txn: tx5fedde22118b469b8e753-005369f737) (client_ip: 192.168.1.30)
May  7 13:04:59 swift-proxy01 proxy-server: ERROR with Account server 10.10.2.35:6002/sdb1 re: Trying to HEAD /v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb: Connection refused (txn: tx3faaa6270e414611895e2-005369f73b) (client_ip             : 192.168.1.30)
May  7 13:04:59 swift-proxy01 proxy-server: ERROR with Account server 10.10.2.34:6002/sdb1 re: Trying to HEAD /v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb: Connection refused (txn: tx3faaa6270e414611895e2-005369f73b) (client_ip             : 192.168.1.30)
May  7 13:04:59 swift-proxy01 proxy-server: ERROR with Account server 10.10.2.31:6002/sdb1 re: Trying to HEAD /v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb: Connection refused (txn: tx3faaa6270e414611895e2-005369f73b) (client_ip             : 192.168.1.30)
May  7 13:04:59 swift-proxy01 proxy-server: Handoff requested (1) (txn: tx3faaa6270e414611895e2-005369f73b) (client_ip: 192.168.1.30)
May  7 13:04:59 swift-proxy01 proxy-server: ERROR with Account server 10.10.2.32:6002/sdb1 re: Trying to HEAD /v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb: Host unreachable (txn: tx3faaa6270e414611895e2-005369f73b) (client_ip:              192.168.1.30)
May  7 13:04:59 swift-proxy01 proxy-server: Handoff requested (2) (txn: tx3faaa6270e414611895e2-005369f73b) (client_ip: 192.168.1.30)
May  7 13:04:59 swift-proxy01 proxy-server: ERROR with Account server 10.10.2.33:6002/sdb1 re: Trying to HEAD /v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb: Connection refused (txn: tx3faaa6270e414611895e2-005369f73b) (client_ip             : 192.168.1.30)
May  7 13:04:59 swift-proxy01 proxy-server: Account HEAD returning 503 for [] (txn: tx3faaa6270e414611895e2-005369f73b) (client_ip: 192.168.1.30)

The storage nodes are pingable, iptables was shuted down. Ring contents:

[root@swift-proxy01 swift]# swift-ring-builder account.builder
account.builder, build version 5
262144 partitions, 3.000000 replicas, 1 regions, 5 zones, 5 devices, 0.00 balance
The minimum number of hours before a partition can be reassigned is 1
Devices:    id  region  zone      ip address  port  replication ip  replication port      name weight partitions balance meta
             0       1     1      10.10.2.31  6002      10.10.2.31              6002      sdb1 100.00     157287    0.00
             1       1     2      10.10.2.32  6002      10.10.2.32              6002      sdb1 100.00     157286   -0.00
             2       1     3      10.10.2.33  6002      10.10.2.33              6002      sdb1 100.00     157286   -0.00
             3       1     4      10.10.2.34  6002      10.10.2.34              6002      sdb1 100.00     157286   -0.00
             4       1     5      10.10.2.35  6002      10.10.2.35              6002      sdb1 100.00     157287    0.00
[root@swift-proxy01 swift]#
[root@swift-proxy01 swift]# swift-ring-builder container.builder
container.builder, build version 5
262144 partitions, 3.000000 replicas, 1 regions, 5 zones, 5 devices, 0.00 balance
The minimum number of hours before a partition can be reassigned is 1
Devices:    id  region  zone      ip address  port  replication ip  replication port      name weight partitions balance meta
             0       1     1      10 ...
(more)
2014-05-07 03:57:45 -0600 received badge  Scholar (source)
2014-05-06 08:47:09 -0600 received badge  Notable Question (source)
2014-05-06 07:47:57 -0600 commented answer swift [Errno 111] Connection refused

Here

[root@swift-proxy01 ~]# cat /etc/sysconfig/memcached
PORT="11211"
USER="memcached"
MAXCONN="1024"
CACHESIZE="64"
OPTIONS="-l 192.168.1.30"
2014-05-06 06:06:48 -0600 commented answer swift [Errno 111] Connection refused

Yes, I can ping storage nodes from proxy node. And yes, I used that instruction.

 [root@swift-proxy01 ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:56:01:08:2C
          inet addr:192.168.1.30  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::250:56ff:fe01:82c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:53835 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19198 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15460928 (14.7 MiB)  TX bytes:2834284 (2.7 MiB)

eth1      Link encap:Ethernet  HWaddr 00:50:56:01:08:59
          inet addr:10.10.2.30  Bcast:10.10.2.255  Mask:255.255.255.0
          inet6 addr: fe80::250:56ff:fe01:859/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1664 errors ...
(more)
2014-05-06 06:04:18 -0600 received badge  Popular Question (source)
2014-05-06 05:36:15 -0600 commented answer swift [Errno 111] Connection refused

Yes, it seems you right. I have changed bind port to 80 and now I get different error:

[root@swift-proxy01 ~]# swift -V 2.0 -A  http://192.168.1.29:5000/v2.0 -U admin:admin -K $ADMINPASS stat
Account HEAD failed: http://192.168.1.30/v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb 503 Internal Server Error

In proxy node logs I see:

May  6 14:32:39 swift-proxy01 proxy-server: ERROR with Account server 10.10.2.34:6002/sdb1 re: Trying to HEAD /v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb: Host unreachable (txn: tx62c8d4423914449e821a5-005368ba47) (client_ip: 192.168.1.30)
May  6 14:32:39 swift-proxy01 proxy-server: ERROR with Account server 10.10.2.35:6002/sdb1 re: Trying to HEAD /v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb: Host unreachable (txn: tx62c8d4423914449e821a5-005368ba47) (client_ip: 192.168.1.30)
May  6 14:32:39 swift-proxy01 proxy-server: ERROR with Account server 10.10.2.31:6002/sdb1 re: Trying to HEAD /v1/AUTH_18c35fb509b84966aa7e5734eebdf8fb: Host unreachable (txn: tx62c8d4423914449e821a5-005368ba47 ...
(more)