mountall: Could not connect to plymouth

Bug #551062 reported by vmc on 2010-03-29
160
This bug affects 34 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
High
Scott James Remnant (Canonical)
Lucid
High
Scott James Remnant (Canonical)

Bug Description

Binary package hint: plymouth

For the past three days, using daily-live and having updated to current level.
When I boot with the following cmdline, I always get the message:

 "mountall: Could not connect to plymouth"

cat /proc/cmdline:
BOOT_IMAGE=/vmlinuz root=UUID=12b607cd-0f88-4e5b-9c21-b3e40b843052 ro quiet splash

It boots up after the mountall message and no other apparent problems.
=============================================
If I then boot with the following cmdline, I NEVER get the mountall message at boot up.
cat /proc/cmdline
BOOT_IMAGE=/vmlinuz root=UUID=12b607cd-0f88-4e5b-9c21-b3e40b843052 ro --verbose splash
==============================================================
cat /etc/lsb-release:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu lucid (development branch)"
===
P4-32bit, 1gb ram, Intel i865 integrated video
=============================

The following is from using "verbose" :

grep "plymouth\|mountall" /var/log/syslog
===
Mar 29 08:41:00 vmc-desktop init: plymouth-stop goal changed from stop to start
Mar 29 08:41:00 vmc-desktop init: plymouth-stop state changed from waiting to starting
Mar 29 08:41:00 vmc-desktop init: plymouth-stop state changed from starting to pre-start
Mar 29 08:41:00 vmc-desktop init: plymouth-stop pre-start process (598)
Mar 29 08:41:00 vmc-desktop init: plymouth-stop pre-start process (598) exited normally
Mar 29 08:41:00 vmc-desktop init: plymouth-stop state changed from pre-start to spawned
Mar 29 08:41:00 vmc-desktop init: plymouth-stop state changed from spawned to post-start
Mar 29 08:41:00 vmc-desktop init: plymouth-stop state changed from post-start to running
Mar 29 08:41:00 vmc-desktop init: plymouth-splash main process (548) exited normally
Mar 29 08:41:00 vmc-desktop init: plymouth-splash goal changed from start to stop
Mar 29 08:41:00 vmc-desktop init: plymouth-splash state changed from running to stopping
Mar 29 08:41:00 vmc-desktop init: plymouth-splash state changed from stopping to killed
Mar 29 08:41:00 vmc-desktop init: plymouth-splash state changed from killed to post-stop
Mar 29 08:41:00 vmc-desktop init: plymouth-splash state changed from post-stop to waiting
Mar 29 08:41:00 vmc-desktop init: plymouth-log main process (579) exited normally
Mar 29 08:41:00 vmc-desktop init: plymouth-log goal changed from start to stop
Mar 29 08:41:00 vmc-desktop init: plymouth-log state changed from running to stopping
Mar 29 08:41:00 vmc-desktop init: plymouth-log state changed from stopping to killed
Mar 29 08:41:00 vmc-desktop init: plymouth-log state changed from killed to post-stop
Mar 29 08:41:00 vmc-desktop init: plymouth-log state changed from post-stop to waiting
Mar 29 08:41:01 vmc-desktop init: plymouth main process (242) exited normally
Mar 29 08:41:01 vmc-desktop init: plymouth goal changed from start to stop
Mar 29 08:41:01 vmc-desktop init: plymouth state changed from running to stopping
Mar 29 08:41:01 vmc-desktop init: plymouth state changed from stopping to killed
Mar 29 08:41:01 vmc-desktop init: plymouth state changed from killed to post-stop
Mar 29 08:41:01 vmc-desktop init: plymouth state changed from post-stop to waiting
Mar 29 08:41:01 vmc-desktop init: plymouth-stop goal changed from start to stop
Mar 29 08:41:01 vmc-desktop init: plymouth-stop state changed from running to stopping
Mar 29 08:41:01 vmc-desktop init: plymouth-stop state changed from stopping to killed
Mar 29 08:41:01 vmc-desktop init: plymouth-stop state changed from killed to post-stop
Mar 29 08:41:01 vmc-desktop init: plymouth-stop state changed from post-stop to waiting
Mar 29 08:41:01 vmc-desktop init: plymouth-stop goal changed from stop to start
Mar 29 08:41:01 vmc-desktop init: plymouth-stop state changed from waiting to starting
Mar 29 08:41:01 vmc-desktop init: plymouth-stop state changed from starting to pre-start
Mar 29 08:41:01 vmc-desktop init: plymouth-stop pre-start process (878)
Mar 29 08:41:01 vmc-desktop init: plymouth-stop pre-start process (878) terminated with status 1
Mar 29 08:41:01 vmc-desktop init: plymouth-stop goal changed from start to stop
Mar 29 08:41:01 vmc-desktop init: plymouth-stop state changed from pre-start to stopping
Mar 29 08:41:01 vmc-desktop init: plymouth-stop state changed from stopping to killed
Mar 29 08:41:01 vmc-desktop init: plymouth-stop state changed from killed to post-stop
Mar 29 08:41:01 vmc-desktop init: plymouth-stop state changed from post-stop to waiting
Mar 29 08:41:03 vmc-desktop init: mountall-net goal changed from stop to start
Mar 29 08:41:03 vmc-desktop init: mountall-net state changed from waiting to starting
Mar 29 08:41:03 vmc-desktop init: mountall-net state changed from starting to pre-start
Mar 29 08:41:03 vmc-desktop init: mountall-net state changed from pre-start to spawned
Mar 29 08:41:03 vmc-desktop init: mountall-net main process (1055)
Mar 29 08:41:03 vmc-desktop init: mountall-net state changed from spawned to post-start
Mar 29 08:41:03 vmc-desktop init: mountall-net state changed from post-start to running
Mar 29 08:41:03 vmc-desktop init: mountall-net main process (1055) exited normally
Mar 29 08:41:03 vmc-desktop init: mountall-net goal changed from start to stop
Mar 29 08:41:03 vmc-desktop init: mountall-net state changed from running to stopping
Mar 29 08:41:03 vmc-desktop init: mountall-net state changed from stopping to killed
Mar 29 08:41:03 vmc-desktop init: mountall-net state changed from killed to post-stop
Mar 29 08:41:03 vmc-desktop init: mountall-net state changed from post-stop to waiting

vmc (vmclark) wrote :
vmc (vmclark) wrote :
Steve Langasek (vorlon) wrote :

What version of the initramfs-tools package do you currently have installed?

TenLeftFingers (tenleftfingers) wrote :

Steve, I have the same problem on an update machine and my package version is 0.92bubuntu71

Steve Langasek (vorlon) wrote :

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):
assignee: nobody → Scott James Remnant (scott)
importance: Undecided → High
status: New → Triaged
vmc (vmclark) wrote :

>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.

hank (thclark28) wrote :

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 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

Andy (abarringer) wrote :
Download full text (4.5 KiB)

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
INSTANCE i-4160077D emi-BDB314B8 10.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/li...

Read more...

Miguel Branco (arlanthir) wrote :

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").

dancurl@gmail.com (dancurl) wrote :

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.

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

Other bug subscribers