At the same time , I see connection errors in the proxy server. Oct 14 14:05:08 opstack-controller proxy-server: Deferring reject downstream Oct 14 14:05:08 opstack-controller proxy-server: - - 14/Oct/2016/05/05/08 HEAD /v1/AUTH_a31f7e8e9ecc4d0e9d0d6c1de6c4c004 HTTP/1.0 204 - Swift - - - - tx60f54bfed6d94357a10c0-0058006784 - 0.0268 RL - 1476421508.123720884 1476421508.150515079 - Oct 14 14:05:08 opstack-controller keystoneauth.identity.base: Failed to contact the endpoint at http://opstack-cont-manage:5000/v3 for discovery. Fallback to using that endpoint as the base url. Oct 14 14:05:08 opstack-controller keystoneauth.identity.base: Failed to contact the endpoint at http://opstack-cont-manage:5000/v3 for discovery. Fallback to using that endpoint as the base url. Oct 14 14:05:08 opstack-controller keystoneauth.session: Failure: Unable to establish connection to http://opstack-cont-manage:5000/v3/auth/tokens. Retrying in 0.5s. Oct 14 14:05:08 opstack-controller keystoneauth.session: Failure: Unable to establish connection to http://opstack-cont-manage:5000/v3/auth/tokens. Retrying in 1.0s. Oct 14 14:05:09 opstack-controller keystoneauth.session: Failure: Unable to establish connection to http://opstack-cont-manage:5000/v3/auth/tokens. Retrying in 2.0s.
Does this mean that problem lies on proxy server side? On Fri, Oct 14, 2016 at 1:51 PM, Yu Watanabe <yu.w.ten...@gmail.com> wrote: > Thanks for the reply. > > I confirmed that proxy config has account_autocreate = true defined and > restarted the openstack-swift-proxy.service. > > But still the account-server returns 404. > > Oct 14 13:46:40 opstack-objstorage1 account-server: 10.1.0.6 - - > [14/Oct/2016:04:46:40 +0000] "HEAD /sdd/292/AUTH_ > a31f7e8e9ecc4d0e9d0d6c1de6c4c004" 404 - "HEAD http://opstack-cont-manage: > 8080/v1/AUTH_a31f7e8e9ecc4d0e9d0d6c1de6c4c004" > "tx874203d701cc421fa1ec1-0058006330" > "proxy-server 28685" 0.0004 "-" 19869 - > Oct 14 13:46:40 opstack-objstorage1 account-server: 10.1.0.6 - - > [14/Oct/2016:04:46:40 +0000] "HEAD /sdc/292/AUTH_ > a31f7e8e9ecc4d0e9d0d6c1de6c4c004" 404 - "HEAD http://opstack-cont-manage: > 8080/v1/AUTH_a31f7e8e9ecc4d0e9d0d6c1de6c4c004" > "tx874203d701cc421fa1ec1-0058006330" > "proxy-server 28685" 0.0003 "-" 19868 - > > Are there any other setting I am missing? > > Thanks. > > > On Fri, Oct 14, 2016 at 12:25 PM, Mark Kirkwood < > mark.kirkw...@catalyst.net.nz> wrote: > >> On 14/10/16 16:03, Yu Watanabe wrote: >> >> Hi! >>> >>> I am verifying the installation using the swift stat command but it >>> returns 503 Service Unavailable. >>> >>> [root@opstack-controller src 2016.10.14 11:55:37]# swift stat >>> Account HEAD failed: http://opstack-cont-manage:808 >>> 0/v1/AUTH_a31f7e8e9ecc4d0e9d0d6c1de6c4c004 503 Service Unavailable >>> >>> I have checked the syslog of storage node side and account server was >>> returning 404 . >>> Oct 14 11:56:11 opstack-objstorage1 account-server: 10.1.0.6 - - >>> [14/Oct/2016:02:56:11 +0000] "HEAD >>> /sdc/292/AUTH_a31f7e8e9ecc4d0e9d0d6c1de6c4c004" >>> 404 - "HEAD http://opstack-cont-manage:8080/v1/AUTH_a31f7e8e9ecc4d0e9d0d >>> 6c1de6c4c004" "tx818ef0bc14b24f599a4b5-005800494b" "proxy-server 24158" >>> 0.0003 "-" 19870 - >>> Oct 14 11:56:11 opstack-objstorage1 account-server: 10.1.0.6 - - >>> [14/Oct/2016:02:56:11 +0000] "HEAD >>> /sdd/292/AUTH_a31f7e8e9ecc4d0e9d0d6c1de6c4c004" >>> 404 - "HEAD http://opstack-cont-manage:8080/v1/AUTH_a31f7e8e9ecc4d0e9d0d >>> 6c1de6c4c004" "tx818ef0bc14b24f599a4b5-005800494b" "proxy-server 24158" >>> 0.0002 "-" 19870 - >>> >>> My SELINUX permission of /srv/node/ is set to what the doucment says. >>> >>> http://docs.openstack.org/mitaka/install-guide-rdo/swift-verify.html >>> >>> [root@opstack-objstorage1 swift 2016.10.14 11:57:18]# ls -ltR /srv/node/ >>> /srv/node/: >>> total 0 >>> drwxr-xr-x. 3 swift swift 20 Oct 14 10:50 sdd >>> drwxr-xr-x. 3 swift swift 20 Oct 14 10:50 sdc >>> >>> /srv/node/sdd: >>> total 0 >>> drwxr-xr-x. 2 swift swift 6 Oct 14 12:02 objects >>> >>> /srv/node/sdd/objects: >>> total 0 >>> >>> /srv/node/sdc: >>> total 0 >>> drwxr-xr-x. 2 swift swift 6 Oct 14 12:02 objects >>> >>> /srv/node/sdc/objects: >>> total 0 >>> >>> I want to diagnose the problem but is there any other setting I should >>> look for? >>> >>> >>> >> Looking at the 404 from the account HEAD, you might want to see if you >> have set: >> >> account_autocreate = true >> >> in your proxy config. >> >> regards >> >> Mark >> >> _______________________________________________ >> Mailing list: http://lists.openstack.org/cgi >> -bin/mailman/listinfo/openstack >> Post to : openstack@lists.openstack.org >> Unsubscribe : http://lists.openstack.org/cgi >> -bin/mailman/listinfo/openstack >> > > > > -- > Yu Watanabe > 渡辺 裕 > > LinkedIn : jp.linkedin.com/in/yuwatanabe1 > -- Yu Watanabe 渡辺 裕 LinkedIn : jp.linkedin.com/in/yuwatanabe1
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
