Swift 1.9.0: swauth prep error
Hi,
We are in the process of implementation of new "object storage" infra.
Infra:
1. Swift version: 1.9.0
2. Swauth : 1.0.9
Changes:
1. We have added each and every HDD present on the node/storage server as individual disk.
2. LABELed each HDD as "HDD001, HDD002.... HDD012 etc" using xfs_admin and used the same label to mount the partitions under "/srv/node/
3. The disks are added into the ring with LABEL names and not the device names
e.g.
swift-ring-builder object.builder add r2z1-XX.
Below is the error we are getting when trying to prep the swauth:
Command:
#swauth-prep -A https://<domain>/auth/ -U .super_admin -K swauthkey
Error in proxys syslog:
===============
Jul 25 17:48:51 MUM-Swift-Proxy1 proxy-server STDOUT: EXCEPTION IN handle: Traceback (most recent call last):#012 File "/usr/local/
Jul 25 17:48:51 MUM-Swift-Proxy1 proxy-server - - 25/Jul/
===============
Regards,
VIshal
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Netmagic Solutions
- Solved:
- 2013-07-25
- Last query:
- 2013-07-25
- Last reply:
- 2013-07-25
clayg (clay-gerrard) said : | #1 |
I think swauth 1.0.8 is the last stable release of swauth, you might try installing a tagged release; or you could try posing the question on gholt's github page for swauth:
https:/
But it looks like it's probably something weird with the swift cluster... The proxy-logger is showing the response as 499, which makes me think there's some more error responses from the backend servers that didn't get pasted here.
Looking at the swauth.middleware around 549 it looks like it uses a pre_auth_request, and then calls get_response with the app then checks the status code with out ever reading the body. I wonder if there's something interesting in this 503/499 resp.body?
Samuel Merritt (torgomatic) said : | #2 |
Hint for troubleshooting: the proxy entry has a transaction id in it: "tx8ddc3854d3d7
Sorry Guys,
it was due to mis config of separate replication network.
Fixed it and things are working fine now.
Thanks for all the replies :)
Regards,
Vishal
We have started from scratch and reconfigured everything as per below link which worked for us.
http://
Regards,
Vishal