[Bug 551062] Re: mountall: Could not connect to plymouth
*** This bug is a duplicate of bug 530779 *** https://bugs.launchpad.net/bugs/530779 I just installed the 10.04 RC, x64 version, and after performing some updates and rebooting, I am getting similar error messages, although using --verbose doesn't seem to solve the problem for me (it does get me a little farther along in the boot process, but an ubuntu splash screen tells me there are problems mounting the root filesystem). As of now I just can't boot into ubuntu, whether I try with recovery, a livecd, etc. -- mountall: Could not connect to plymouth https://bugs.launchpad.net/bugs/551062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551062] Re: mountall: Could not connect to plymouth
*** This bug is a duplicate of bug 530779 *** https://bugs.launchpad.net/bugs/530779 I'm not sure this is relevant to your opinion that this is a duplicate of bug #530779, but I was able to boot without problems until some updates ago (2 days - plymouth stopped showing), and now I'm getting this message (with today's update). Bug #530779 was opened a month ago, is that normal? Just wanted to make sure. I can boot all the time, I just don't see plymouth's splash (with GRUB_CMDLINE_LINUX_DEFAULT=quiet splash). -- mountall: Could not connect to plymouth https://bugs.launchpad.net/bugs/551062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551062] Re: mountall: Could not connect to plymouth
*** This bug is a duplicate of bug 530779 *** https://bugs.launchpad.net/bugs/530779 mountall will keep trying to reconnect anyway and with the main loop fixes, that initial connect goes away The remaining bug is that sometimes mountall might not prompt for boredom (but only if plymouth takes 2s to open its socket), or might not prompt for fsck failure (but only if plymouth takes longer to open its socket than fsck takes to run) Both of those cares are fairly unlikely And it's far too close to release to muck around with Upstart's ptrace code ** This bug has been marked a duplicate of bug 530779 init: does not wait for parent to exit when following forks -- mountall: Could not connect to plymouth https://bugs.launchpad.net/bugs/551062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551062] Re: mountall: Could not connect to plymouth
*** This bug is a duplicate of bug 530779 *** https://bugs.launchpad.net/bugs/530779 All, I'm attempting to test the UEC platform.. Can you tell me if this result is what would be expected from this bug? I have the cloud running with two virtual nodes etc. Everything is working great as far as the main infrastructure pieces. The first task I'm attempting is launch an image. Here's the script On master controller wget http://uec-images.ubuntu.com/server/lucid/20100330/lucid-server-uec-amd64.tar.gz uec-publish-tarball lucid-server-uec-amd64.tar.gz mybucket euca-run-instances -k mykey -t c1.medium emi-BDB314B8 #check to make sure it's running.. yea it is euca-describe-instances RESERVATION r-30360666 admin default INSTANCEi-4160077D emi-BDB314B810.16.2.177 172.19.1.4 running #ping it PING 10.16.2.177 (10.16.2.177) 56(84) bytes of data. ^C --- 10.16.2.177 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2005ms #uh oh no ping.. #get console output euca-get-console-output i-4160077D ... [3.852039] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection [3.923934] EXT3 FS on sda1, internal journal sleeping 1 sleeping 1 sleeping 1 sleeping 1 sleeping 1 sleeping 1 sleeping 1 sleeping 1 sleeping 1 sleeping 1 Could not find data source Failed to get instance datainit: cloud-init main process (569) terminated with status 1 mountall: Event failed Traceback (most recent call last): File /usr/bin/cloud-init-cfg, line 56, in module main() File /usr/bin/cloud-init-cfg, line 43, in main cc = cloudinit.CloudConfig.CloudConfig(cfg_path) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 42, in __init__ self.cfg = self.get_config_obj(cfgfile) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 53, in get_config_obj f=file(cfgfile) IOError: [Errno 2] No such file or directory: '/var/lib/cloud/data/cloud-config.txt' Traceback (most recent call last): File /usr/bin/cloud-init-cfg, line 56, in module main() File /usr/bin/cloud-init-cfg, line 43, in main cc = cloudinit.CloudConfig.CloudConfig(cfg_path) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 42, in __init__ self.cfg = self.get_config_obj(cfgfile) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 53, in get_config_obj f=file(cfgfile) IOError: [Errno 2] No such file or directory: '/var/lib/cloud/data/cloud-config.txt' Traceback (most recent call last): File /usr/bin/cloud-init-cfg, line 56, in module main() File /usr/bin/cloud-init-cfg, line 43, in main cc = cloudinit.CloudConfig.CloudConfig(cfg_path) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 42, in __init__ self.cfg = self.get_config_obj(cfgfile) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 53, in get_config_obj f=file(cfgfile) IOError: [Errno 2] No such file or directory: '/var/lib/cloud/data/cloud-config.txt' Traceback (most recent call last): File /usr/bin/cloud-init-cfg, line 56, in module main() File /usr/bin/cloud-init-cfg, line 43, in main cc = cloudinit.CloudConfig.CloudConfig(cfg_path) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 42, in __init__ self.cfg = self.get_config_obj(cfgfile) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 53, in get_config_obj f=file(cfgfile) IOError: [Errno 2] No such file or directory: '/var/lib/cloud/data/cloud-config.txt' Traceback (most recent call last): File /usr/bin/cloud-init-cfg, line 56, in module main() File /usr/bin/cloud-init-cfg, line 43, in main cc = cloudinit.CloudConfig.CloudConfig(cfg_path) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 42, in __init__ self.cfg = self.get_config_obj(cfgfile) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 53, in get_config_obj f=file(cfgfile) IOError: [Errno 2] No such file or directory: '/var/lib/cloud/data/cloud-config.txt' Traceback (most recent call last): File /usr/bin/cloud-init-cfg, line 56, in module main() File /usr/bin/cloud-init-cfg, line 43, in main cc = cloudinit.CloudConfig.CloudConfig(cfg_path) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 42, in __init__ self.cfg = self.get_config_obj(cfgfile) File /usr/lib/python2.6/dist-packages/cloudinit/CloudConfig.py, line 53, in get_config_obj f=file(cfgfile) IOError: [Errno 2] No such file or directory: '/var/lib/cloud/data/cloud-config.txt' -- mountall: Could not connect to plymouth https://bugs.launchpad.net/bugs/551062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551062] Re: mountall: Could not connect to plymouth
** Attachment added: syslog NOT using verbose http://launchpadlibrarian.net/42404023/syslog -- mountall: Could not connect to plymouth https://bugs.launchpad.net/bugs/551062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551062] Re: mountall: Could not connect to plymouth
** Attachment added: syslog using --verbose at startup http://launchpadlibrarian.net/42404139/syslog.verbose -- mountall: Could not connect to plymouth https://bugs.launchpad.net/bugs/551062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551062] Re: mountall: Could not connect to plymouth
What version of the initramfs-tools package do you currently have installed? -- mountall: Could not connect to plymouth https://bugs.launchpad.net/bugs/551062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551062] Re: mountall: Could not connect to plymouth
Steve, I have the same problem on an update machine and my package version is 0.92bubuntu71 -- mountall: Could not connect to plymouth https://bugs.launchpad.net/bugs/551062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551062] Re: mountall: Could not connect to plymouth
Ok, I believe I've pinned this bug down. Upstart's 'expect fork' doesn't appear to watch for the parent process to die, it only watches for the child process to be spawned; so when using 'expect fork', all setup work needs to be done by the parent process prior to forking. plymouth fails to do this; it calls ply_create_daemon() before calling start_boot_server(), so there's a race condition here because upstart will start mountall while plymouthd is still setting up its control socket, and when we lose the race we get this message. I'm not sure if it's possible to run initialize_environment() and attach_to_running_session() in the parent process, or if we need to switch this upstart job to use 'expect stop'. Assigning to Scott since he knows (all of) this code better than I do. ** Changed in: plymouth (Ubuntu) Importance: Undecided = High ** Changed in: plymouth (Ubuntu) Status: New = Triaged ** Changed in: plymouth (Ubuntu) Assignee: (unassigned) = Scott James Remnant (scott) ** Also affects: plymouth (Ubuntu Lucid) Importance: High Assignee: Scott James Remnant (scott) Status: Triaged -- mountall: Could not connect to plymouth https://bugs.launchpad.net/bugs/551062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551062] Re: mountall: Could not connect to plymouth
What version of the initramfs-tools package do you currently have installed? 0.92bubuntu71, same as jarlath reported. And thanks. Amazingly quick response. ...apparently verbose slowed down the boot process long enough for mountall to catch its breath. -- mountall: Could not connect to plymouth https://bugs.launchpad.net/bugs/551062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551062] Re: mountall: Could not connect to plymouth
I just clicked on update manager and got all newest updates and got the same error when I rebooted.mountall: Could not connect to plymouth -- mountall: Could not connect to plymouth https://bugs.launchpad.net/bugs/551062 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
