[Bug 1301738] Re: upstart "Unable to watch configuration directory: No space left on device"
James Hunt
1301738 at bugs.launchpad.net
Thu Apr 3 07:51:57 UTC 2014
Hi Nick,
Thanks for reporting this issue. Yes, Upstart uses inotify so the error
shown is coming directly from the kernel. However, the error relates to
the lack of inotify watches, not the lack of disk space. What the error
you are seeing means is that Upstart will not recognise any changes to
the files in that directory, but aside from that it should remain fully
functional. Note that you can always force a rescan of /etc/init/ by
running:
$ sudo initctl reload-configuration
Please can you attach the output from the following commands:
a) cat /proc/sys/fs/inotify/max_user_instances
b) cat /proc/sys/fs/inotify/max_user_watches
c) grep -ir inotify /etc/sysctl*
d) sudo ls -l /proc/1/fd/
Also, a few questions:
1) Is /etc/init/ a symbolic link, or does it contain linked files?
2) Have you created a lot of sub-directories below /etc/init/ ?
3) can you try installing another tool that uses inotify to check the
behaviour:
$ sudo apt-get install inotify-tools && inotifywait -m /etc/init
4) Is trusty installed in a chroot / container / VM here?
5) If you reboot, does the message persist? (it would help if you booted
with '--debug' and without 'splash' and without 'quiet':
http://upstart.ubuntu.com/cookbook/#add-verbose-or-debug-to-the-
kernel-command-line
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1301738
Title:
upstart "Unable to watch configuration directory: No space left on
device"
Status in “upstart” package in Ubuntu:
New
Bug description:
I recently upgraded to Trusty 14.04 and receive the following messages
in dmesg:
[ 945.189268] init: upstart-udev-bridge main process (476) terminated with status 1
[ 945.189277] init: upstart-udev-bridge main process ended, respawning
[ 945.189405] init: upstart-socket-bridge main process (673) terminated with status 1
[ 945.189412] init: upstart-socket-bridge main process ended, respawning
[ 945.189507] init: upstart-file-bridge main process (1120) terminated with status 1
[ 945.189513] init: upstart-file-bridge main process ended, respawning
[ 955.783676] init: /etc/init: Unable to watch configuration directory: No space left on device
[ 969.453559] init: /etc/init: Unable to watch configuration directory: No space left on device
The last (inotify?) messages about space aren't valid -- df shows
every device has tons of space available.
semenko at exon:~$ uname -ar
Linux exon 3.13.0-20-generic #42-Ubuntu SMP Fri Mar 28 09:56:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
semenko at exon:~$ apt-cache policy upstart
upstart:
Installed: 1.12.1-0ubuntu1
Candidate: 1.12.1-0ubuntu1
Version table:
*** 1.12.1-0ubuntu1 0
500 http://cosmos.cites.illinois.edu/pub/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1301738/+subscriptions
More information about the foundations-bugs
mailing list