Not able to access containers or objects due to change of IP

asked 2013-06-27 11:40:00 -0600

anilbhargava777 gravatar image

Hello,

I am running the swift cluster on a single server with 2 zones having total 2TB storage space & all services running over the same server. Due to change of IP range in my network I had to update my IP for 92.168.62.4 to 10.180.32.20. I have updated all the configuration files accordingly to have the new IP (10.180.32.20). I created the builder files again having new IP and did the rebalancing and started all the services.

Below is the snapshot of syslog:

swift@cloudvault:~$ sudo tail -n 40 /var/log/syslog Jun 27 16:39:06 cloudvault object-auditor Object audit (ALL) "forever" mode completed: 0.00s. Total quarantined: 0, Total errors: 0, Total files/sec: 0.00 , Total bytes/sec: 0.00, Auditing time: 0.00, Rate: 0.00 Jun 27 16:39:06 cloudvault container-replicator Beginning replication run Jun 27 16:39:06 cloudvault container-replicator Replication run OVER Jun 27 16:39:06 cloudvault container-replicator Attempted to replicate 98 dbs in 0.38346 seconds (255.56969/s) Jun 27 16:39:06 cloudvault container-replicator Removed 0 dbs Jun 27 16:39:06 cloudvault container-replicator 0 successes, 0 failures Jun 27 16:39:06 cloudvault container-replicator no_change:0 ts_repl:0 diff:0 rsync:0 diff_capped:0 hashmatch:0 empty:0 Jun 27 16:39:08 cloudvault account-auditor Account audit pass completed: 0.00s Jun 27 16:39:08 cloudvault account-auditor Begin account audit pass Jun 27 16:39:11 cloudvault object-auditor Begin object audit "forever" mode (ZBF) Jun 27 16:39:11 cloudvault object-auditor Object audit (ZBF) "forever" mode completed: 0.00s. Total quarantined: 0, Total errors: 0, Total files/sec: 0.00 , Total bytes/sec: 0.00, Auditing time: 0.00, Rate: 0.00 Jun 27 16:39:14 cloudvault object-replicator Starting object replication pass. Jun 27 16:39:14 cloudvault object-replicator Nothing replicated for 0.00204992294312 seconds. Jun 27 16:39:14 cloudvault object-replicator Object replication complete. (0.00 minutes) Jun 27 16:39:16 cloudvault account-replicator Beginning replication run Jun 27 16:39:16 cloudvault account-replicator Replication run OVER Jun 27 16:39:16 cloudvault account-replicator Attempted to replicate 1 dbs in 0.00766 seconds (130.47500/s) Jun 27 16:39:16 cloudvault account-replicator Removed 0 dbs Jun 27 16:39:16 cloudvault account-replicator 0 successes, 0 failures Jun 27 16:39:16 cloudvault account-replicator no_change:0 ts_repl:0 diff:0 rsync:0 diff_capped:0 hashmatch:0 empty:0 Jun 27 16:39:20 cloudvault container-replicator Beginning replication run Jun 27 16:39:20 cloudvault container-replicator Replication run OVER Jun 27 16:39:20 cloudvault container-replicator Attempted to replicate 92 dbs in 0.31415 seconds (292.84888/s) Jun 27 16:39:20 cloudvault container-replicator Removed 0 dbs Jun 27 16:39:20 cloudvault container-replicator 0 successes, 0 failures Jun 27 16:39:20 cloudvault container-replicator no_change:0 ts_repl:0 diff:0 rsync:0 diff_capped:0 hashmatch:0 empty:0 Jun 27 16:39:21 cloudvault ... (more)

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2013-07-06 11:45:01 -0600

anilbhargava777 gravatar image

Solved myself.

edit flag offensive delete link more
0

answered 2013-07-23 13:57:56 -0600

Can you explain how you solved it ?

edit flag offensive delete link more
0

answered 2013-07-24 04:22:28 -0600

anilbhargava777 gravatar image

I am not very sure about what solved my problem but I took two steps:

1) Changed the weight little bit and re-balanced to force the data & db files to move around. 2) After checking the log status, for confirmation of re-balance, I executed the the SWAUTH-PREP again for initializing the SWAUTH.

after doing above two things I got the access back.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-06-27 11:40:00 -0600

Seen: 42 times

Last updated: Jul 24 '13