Cannot connect to EC2 instance after bootstrap

Bug #905872 reported by Chris Hardee
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
juju (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After configuring environment for ec2 and bootstrapping, I am unable to connect to check status or ssh into machine. Running juju -v status results in:
2011-12-17 23:23:55,110:1685(0x7fe2732a7720):ZOO_INFO@zookeeper_init@727: Initiating client connection, host=localhost:59459 sessionTimeout=10000 watcher=0x7fe271160650 sessionId=0 sessionPasswd=<null> context=0x285dab0 flags=0
2011-12-17 23:23:55,110:1685(0x7fe26a73a700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:59459] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2011-12-17 23:23:58,447:1685(0x7fe26a73a700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:59459] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2011-12-17 23:24:01,783:1685(0x7fe26a73a700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:59459] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
and so on

Sometimes deleting the environments.yaml and regenerating it by calling juju and adding aws keys will allow me to connect, but not consistently.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

shazzner, I think this is a duplicate of bug #901311 .. its possible your control buckets are getting confused. Can you make sure you clear out all of the control buckets you have used for juju, and then try to reproduce this?

Changed in juju (Ubuntu):
status: New → Incomplete
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Hi shazzner. Its been almost a month with no reply. Are you still affected by this problem?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju (Ubuntu) because there has been no activity for 60 days.]

Changed in juju (Ubuntu):
status: Incomplete → Expired
Dayo Olutayo (xplora)
Changed in juju (Ubuntu):
status: Expired → New
Revision history for this message
Dayo Olutayo (xplora) wrote :

I have regenerated the environment 3 times, runing juju status still end up in this:

2012-10-28 19:19:17,619 INFO Connecting to environment...
2012-10-28 19:19:24,678 ERROR SSH forwarding error: -bash: warning: setlocale: LC_ALL: cannot change locale (en_NG.UTF-8)

2012-10-28 19:19:56,840 ERROR SSH forwarding error: -bash: warning: setlocale: LC_ALL: cannot change locale (en_NG.UTF-8)

2012-10-28 19:20:29,200 ERROR SSH forwarding error: -bash: warning: setlocale: LC_ALL: cannot change locale (en_NG.UTF-8)

2012-10-28 19:21:02,393 ERROR SSH forwarding error: -bash: warning: setlocale: LC_ALL: cannot change locale (en_NG.UTF-8)

2012-10-28 19:21:02,397 ERROR Cannot connect to environment: an integer is required
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/juju/providers/common/connect.py", line 42, in run
    client = yield self._internal_connect(share)
TypeError: an integer is required
an integer is required
2012-10-28 19:21:02,398 ERROR an integer is required

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

olutayo - could you please file a new bug for your issue using 'ubuntu-bug juju' ? This appears to be a different issue. Please make sure to append a (sanitized) copy of your environments.yaml.

Changed in juju (Ubuntu):
status: New → Invalid
Revision history for this message
Dayo Olutayo (xplora) wrote :

Serge, I just did that now, this is the link https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1084514

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

Other bug subscribers

Related questions

Remote bug watches

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