swift-proxy changes listen port for memcached, but doesn't restart it
Bug #1167540 reported by
Andreas Hasenack
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| swift-proxy (Juju Charms Collection) |
Fix Released
|
Undecided
|
Andreas Hasenack | ||
Bug Description
The swift-proxy sets memcached up to listen on <ip>:<port>, changing it from the default of 127.0.0.1:<port>, but doesn't restart it.
As a result, once deployed, memcached is running on the unit, but listening only on the 127.0.0.1 address, whereas swift-proxy is configured to connect to <ip>, which fails because noone is listening there.
/var/log/syslog gets these:
Apr 10 15:00:18 inst-023 proxy-server STDOUT: ERROR:root:Error connecting to memcached: 192.168.
Just restarting memcached fixes it, since its configuration file is already correct.
Related branches
lp://staging/~ahasenack/charms/precise/swift-proxy/restart-memcached
- OpenStack Charmers: Pending requested
-
Diff: 18 lines (+2/-1)2 files modifiedhooks/swift_hooks.py (+1/-0)
revision (+1/-1)
| Changed in swift-proxy (Juju Charms Collection): | |
| assignee: | nobody → Andreas Hasenack (ahasenack) |
| status: | New → In Progress |
| Changed in swift-proxy (Juju Charms Collection): | |
| status: | In Progress → Fix Committed |
| tags: | added: landscape |
| tags: | added: openstack |
| Changed in swift-proxy (Juju Charms Collection): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
