Binding "MY_HOSTNAME" on HP Cloud doesn't actually bind the port properly

Bug #1029645 reported by Marco Ceppi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
redis-master (Juju Charms Collection)
New
Undecided
Unassigned
redis-slave (Juju Charms Collection)
New
Undecided
Unassigned

Bug Description

After deploying and exposing the charm, on HP Cloud the port doesn't get bound properly.

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 juju-hpcloud-inst:45642 10.5.189.135:2181 ESTABLISHED
tcp 0 0 juju-hpcloud-inst:45640 10.5.189.135:2181 ESTABLISHED
tcp 0 272 juju-hpcloud-instan:ssh 38.104.238.138:49958 ESTABLISHED
tcp6 0 0 [::]:ssh [::]:* LISTEN
udp 0 0 *:bootpc *:*

While the hostname is properly set up in HPs DNS, Redis doesn't seem to work properly. I propose just removing the bind line all together and having Reids bind to *:6379 - After removing the bind line from the Redis config and restarting the service, the service was exposed properly.

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 *:6379 *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 juju-hpcloud-inst:45642 10.5.189.135:2181 ESTABLISHED
tcp 0 0 juju-hpcloud-inst:45640 10.5.189.135:2181 ESTABLISHED
tcp 0 272 juju-hpcloud-instan:ssh 38.104.238.138:49958 ESTABLISHED
tcp6 0 0 [::]:ssh [::]:* LISTEN
udp 0 0 *:bootpc *:*

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.