Machines occasionally fail to start the machine agent correctly because of an unhandled ConnectionTimeoutException
Bug #995823 reported by
Clint Byrum
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Triaged
|
Low
|
Unassigned | ||
| juju (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
I have seen, multiple times, this happen that prevents the machine agent from working:
$ sudo cat /var/log/
2012-05-07 08:03:44,662: twisted@ERROR: Unhandled error in Deferred:
2012-05-07 08:03:44,662: twisted@ERROR: Unhandled Error
Traceback (most recent call last):
Failure: txzookeeper.
I believe it happens if the zookeeper server is slow to respond, perhaps if it has been swapped out or something else.
ii juju 0.5+bzr535-
Also, restarting the juju-machine-agent upstart job starts the agent properly.
| description: | updated |
| Changed in juju (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| Changed in juju: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
To post a comment you must log in.
