Charm fails to start redis-server on EC2

Bug #1021157 reported by Dixon Dick on 2012-07-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
redis-master (Juju Charms Collection)
Undecided
Unassigned

Bug Description

When starting with "juju deploy redis-master" the redis-server will not start. Log error is : "# Opening port: invalid bind address"

The "bind" can be filled in by either "localhost" or the EC2 name e.g. "domU-ec2-50-19-0-204.compute-1.internal" and both fail.

By commenting out the bind entry in the redis.conf the server will start.

Duuuude!

On Thu, Jul 05, 2012 at 07:35:57AM -0000, Dixon Dick wrote:
> Public bug reported:
>
> When starting with "juju deploy redis-master" the redis-server will not
> start. Log error is : "# Opening port: invalid bind address"
>
> The "bind" can be filled in by either "localhost" or the EC2 name e.g.
> "domU-ec2-50-19-0-204.compute-1.internal" and both fail.
>
> By commenting out the bind entry in the redis.conf the server will
> start.
>
> ** Affects: redis-master (Juju Charms Collection)
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to Juju
> Charms Collection.
> Matching subscriptions: principia
> https://bugs.launchpad.net/bugs/1021157
>
> Title:
> Charm fails to start redis-server on EC2
>
> Status in “redis-master” package in Juju Charms Collection:
> New
>
> Bug description:
> When starting with "juju deploy redis-master" the redis-server will
> not start. Log error is : "# Opening port: invalid bind address"
>
> The "bind" can be filled in by either "localhost" or the EC2 name e.g.
> "domU-ec2-50-19-0-204.compute-1.internal" and both fail.
>
> By commenting out the bind entry in the redis.conf the server will
> start.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/charms/+source/redis-master/+bug/1021157/+subscriptions
>

--
Mark Mims, Ph.D.
Ubuntu Server Team
Canonical Ltd.
<email address hidden>
+1(512)981-6467

Dixon Dick (dixon1e) wrote :

though it is sufficient to use:

bind 127.0.0.1

the charm should not set up a configuration that does not work "out of the box."

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

Other bug subscribers