[Bug 1007433] Re: zookeeperd not running after installation of zookeeperd

Vincent Ladeuil 1007433 at bugs.launchpad.net
Fri Jun 1 14:02:21 UTC 2012


I encounter the same issue while trying to use the same image for juju.

If I use a precise image, cloud-init-output.log ends with:


Installed /usr/lib/juju/juju
Processing dependencies for juju==0.5
Finished processing dependencies for juju==0.5
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100    10  100    10    0     0     80      0 --:--:-- --:--:-- --:--:--    81
2012-06-01 09:42:15,150 INFO Initializing zookeeper hierarchy
2012-06-01 09:42:15,203 INFO 'initialize' command finished successfully
juju-machine-agent start/running, process 4776
juju-provision-agent start/running, process 4779


with the quantal image that's:

Installed /usr/lib/juju/juju
Processing dependencies for juju==0.5
Finished processing dependencies for juju==0.5
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100    10  100    10    0     0    118      0 --:--:-- --:--:-- --:--:--   120
could not connect before timeout
2012-06-01 13:43:21,156 ERROR could not connect before timeout


Accordingly, (fuzzily matching the /var/log/syslog files) in precise:

Jun  1 09:41:16 server-11237 acpid: 1 rule loaded
Jun  1 09:41:16 server-11237 acpid: waiting for events: event logging is off
Jun  1 09:41:16 server-11237 cron[874]: (CRON) INFO (Running @reboot jobs)
Jun  1 09:41:16 server-11237 kernel: [   10.366463] init: plymouth-upstart-bridge main process (781) killed by TERM signal
Jun  1 09:41:21 server-11237 ntpdate[597]: step time server 91.189.94.4 offset 1.815666 sec
Jun  1 09:42:03 server-11237 dhclient: DHCPREQUEST of 10.55.60.51 on eth0 to 10.55.60.1 port 67


in quantal:

Jun  1 13:42:04 server-11254 acpid: 1 rule loaded
Jun  1 13:42:04 server-11254 acpid: waiting for events: event logging is off
Jun  1 13:42:04 server-11254 cron[915]: (CRON) INFO (Running @reboot jobs)
Jun  1 13:42:05 server-11254 kernel: [   10.863797] init: plymouth-stop pre-start process (1010) terminated with status 1
Jun  1 13:42:09 server-11254 ntpdate[669]: step time server 91.189.94.4 offset 1.476571 sec
Jun  1 13:42:17 server-11254 ntpdate[1043]: adjust time server 91.189.94.4 offset -0.000002 sec
Jun  1 13:42:39 server-11254 ntpdate[1565]: adjust time server 91.189.94.4 offset 0.000011 sec
Jun  1 13:42:49 server-11254 kernel: [   53.716385] init: zookeeper main process (7600) terminated with status 2
Jun  1 13:42:49 server-11254 kernel: [   53.716407] init: zookeeper main process ended, respawning
Jun  1 13:42:49 server-11254 kernel: [   53.721173] init: zookeeper main process (7603) terminated with status 2
Jun  1 13:42:49 server-11254 kernel: [   53.721194] init: zookeeper main process ended, respawning
Jun  1 13:42:49 server-11254 kernel: [   53.726910] init: zookeeper main process (7606) terminated with status 2
Jun  1 13:42:49 server-11254 kernel: [   53.726933] init: zookeeper main process ended, respawning
Jun  1 13:42:49 server-11254 kernel: [   53.731772] init: zookeeper main process (7610) terminated with status 2
Jun  1 13:42:49 server-11254 kernel: [   53.731809] init: zookeeper main process ended, respawning
Jun  1 13:42:49 server-11254 kernel: [   53.736305] init: zookeeper main process (7613) terminated with status 2
Jun  1 13:42:49 server-11254 kernel: [   53.736326] init: zookeeper main process ended, respawning
Jun  1 13:42:49 server-11254 kernel: [   53.745407] init: zookeeper main process (7616) terminated with status 2
Jun  1 13:42:49 server-11254 kernel: [   53.745429] init: zookeeper main process ended, respawning
Jun  1 13:42:49 server-11254 kernel: [   53.749924] init: zookeeper main process (7619) terminated with status 2
Jun  1 13:42:49 server-11254 kernel: [   53.749946] init: zookeeper main process ended, respawning
Jun  1 13:42:49 server-11254 kernel: [   53.754772] init: zookeeper main process (7622) terminated with status 2
Jun  1 13:42:49 server-11254 kernel: [   53.754798] init: zookeeper main process ended, respawning
Jun  1 13:42:49 server-11254 kernel: [   53.759302] init: zookeeper main process (7625) terminated with status 2
Jun  1 13:42:49 server-11254 kernel: [   53.759327] init: zookeeper main process ended, respawning
Jun  1 13:42:49 server-11254 kernel: [   53.765900] init: zookeeper main process (7628) terminated with status 2
Jun  1 13:42:49 server-11254 kernel: [   53.765922] init: zookeeper main process ended, respawning
Jun  1 13:42:49 server-11254 kernel: [   53.770424] init: zookeeper main process (7631) terminated with status 2
Jun  1 13:42:49 server-11254 kernel: [   53.770445] init: zookeeper respawning too fast, stopped
Jun  1 13:42:53 server-11254 dhclient: DHCPREQUEST of 10.55.60.114 on eth0 to 10.55.60.1 port 67

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to zookeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1007433

Title:
  zookeeperd not running after installation of zookeeperd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zookeeper/+bug/1007433/+subscriptions



More information about the Ubuntu-server-bugs mailing list