Public bug reported:
1. After run the script of https://git.openstack.org/cgit/openstack-infra/system-config/plain/install_puppet.sh; execute the command of "restart ssh" but it gets hang. 2. And if we use "status ssh", we can see there is pid in the output. 3. I noticed that there are multiple upstart-* daemon processes running: e.g. there are two upstart-socket-bridge. 4. it can get recover via a machine reboot. root@devstack:~# ps -ef | grep start root 293 1 0 05:23 ? 00:00:00 upstart-udev-bridge --daemon root 653 1 0 05:23 ? 00:00:00 upstart-file-bridge --daemon root 676 1 0 05:23 ? 00:00:00 upstart-socket-bridge --daemon root 5192 1 0 05:32 ? 00:00:00 upstart-udev-bridge --daemon root 5379 1 0 05:32 ? 00:00:00 upstart-file-bridge --daemon root 5382 1 0 05:32 ? 00:00:00 upstart-socket-bridge --daemon root 13584 1 0 05:33 ? 00:00:00 upstart-udev-bridge --daemon $restart ssh ---> hang at here $ status ssh ssh start/running ---> no pid # the running sshd started before running the script; restart didn't terminate it and of course it can't start a new instance as sshd limited to be run single instance. Another observation is that the additinal upstart-* processes started during the install_puppet.sh running. root 1875 1 0 05:27 ? 00:00:00 /usr/sbin/sshd -D root 19284 1 0 05:35 ? 00:00:00 [sshd] <defunct> root@one-dev-ci-controller:/etc/nodepool# uname -a Linux one-dev-ci-controller 3.13.0-58-generic #97-Ubuntu SMP Wed Jul 8 02:56:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ** Affects: nova Importance: Undecided Status: Invalid ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1493792 Title: upstart hang after running install_puppet.sh Status in OpenStack Compute (nova): Invalid Bug description: 1. After run the script of https://git.openstack.org/cgit/openstack-infra/system-config/plain/install_puppet.sh; execute the command of "restart ssh" but it gets hang. 2. And if we use "status ssh", we can see there is pid in the output. 3. I noticed that there are multiple upstart-* daemon processes running: e.g. there are two upstart-socket-bridge. 4. it can get recover via a machine reboot. root@devstack:~# ps -ef | grep start root 293 1 0 05:23 ? 00:00:00 upstart-udev-bridge --daemon root 653 1 0 05:23 ? 00:00:00 upstart-file-bridge --daemon root 676 1 0 05:23 ? 00:00:00 upstart-socket-bridge --daemon root 5192 1 0 05:32 ? 00:00:00 upstart-udev-bridge --daemon root 5379 1 0 05:32 ? 00:00:00 upstart-file-bridge --daemon root 5382 1 0 05:32 ? 00:00:00 upstart-socket-bridge --daemon root 13584 1 0 05:33 ? 00:00:00 upstart-udev-bridge --daemon $restart ssh ---> hang at here $ status ssh ssh start/running ---> no pid # the running sshd started before running the script; restart didn't terminate it and of course it can't start a new instance as sshd limited to be run single instance. Another observation is that the additinal upstart-* processes started during the install_puppet.sh running. root 1875 1 0 05:27 ? 00:00:00 /usr/sbin/sshd -D root 19284 1 0 05:35 ? 00:00:00 [sshd] <defunct> root@one-dev-ci-controller:/etc/nodepool# uname -a Linux one-dev-ci-controller 3.13.0-58-generic #97-Ubuntu SMP Wed Jul 8 02:56:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1493792/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
