Hi,
J Bauer wrote:
> systemd-u (275)
> ----- End ------
>
> "systemd-u" is really the process "/lib/systemd/systemd-udevd --daemon"
> which is part of udev.
This issue is already fixed in git. lsof in the default (human- but
not machine-readable) output truncates the binary names.
> ---- Begin -----
> systemd-u 275 root DEL REG 252,0
> 655405 /lib/modules/3.13.0-24-generic/modules.symbols.bin
> systemd-u 275 root DEL REG 252,0
> 655402 /lib/modules/3.13.0-24-generic/modules.alias.bin
> systemd-u 275 root DEL REG 252,0
> 655411 /lib/modules/3.13.0-24-generic/modules.dep.bin
> systemd-u 275 root DEL REG 252,0
> 655406 /lib/modules/3.13.0-24-generic/modules.builtin.bin
> ---- End ----
>
> It is seeing the "DEL" in the fd field and /lib/modules is not one of
> the paths that are exempted.
We can not reproduce this issue on trusty, lsof doesn't show these
files as deleted.
> Those files *DO* exist, but the modification time indicates they were
> recreated at boot.
... which makes the old ones "deleted", yes.
But those files are not recreated on boot here:
# uprecords -Bm1
# Uptime | System Boot up
----------------------------+---------------------------------------------------
-> 1 7 days, 06:02:38 | Linux 3.13.0-5-generic Tue Apr 15 09:11:27 2014
# ps auxwww | fgrep systemd-udev
root 13786 0.0 0.0 4612 644 pts/3 S+ 15:12 0:00 fgrep
systemd-udev
root 25428 0.0 0.1 12248 1520 ? Ss Apr15 0:00
/lib/systemd/systemd-udevd --daemon
# lsof -p 25428 | fgrep /lib/modules
systemd-u 25428 root mem REG 252,0 520141 2884602
/lib/modules/3.13.0-5-generic/modules.symbols.bin
systemd-u 25428 root mem REG 252,0 909182 2883868
/lib/modules/3.13.0-5-generic/modules.alias.bin
systemd-u 25428 root mem REG 252,0 582934 2883866
/lib/modules/3.13.0-5-generic/modules.dep.bin
systemd-u 25428 root mem REG 252,0 9158 2884603
/lib/modules/3.13.0-5-generic/modules.builtin.bin
# lsof -p 25428 | fgrep /lib/modules | awk '{print $9}' | xargs ls -l
-rw-r--r-- 1 root root 909182 Feb 6 14:12
/lib/modules/3.13.0-5-generic/modules.alias.bin
-rw-r--r-- 1 root root 9158 Feb 6 14:12
/lib/modules/3.13.0-5-generic/modules.builtin.bin
-rw-r--r-- 1 root root 582934 Feb 6 14:12
/lib/modules/3.13.0-5-generic/modules.dep.bin
-rw-r--r-- 1 root root 520141 Feb 6 14:12
/lib/modules/3.13.0-5-generic/modules.symbols.bin
# uname -a
Linux athens 3.13.0-5-generic #20-Ubuntu SMP Mon Jan 20 19:58:23 UTC 2014 i686
i686 i686 GNU/Linux
# uprecords -Bm8
# Uptime | System Boot up
----------------------------+---------------------------------------------------
-> 1 7 days, 06:04:53 | Linux 3.13.0-5-generic Tue Apr 15 09:11:27 2014
2 0 days, 13:11:06 | Linux 3.13.0-5-generic Mon Apr 14 19:59:50 2014
3 6 days, 03:02:13 | Linux 3.13.0-5-generic Tue Apr 8 16:57:04 2014
4 39 days, 02:11:56 | Linux 3.13.0-5-generic Fri Feb 28 13:44:34 2014
5 1 day , 21:34:05 | Linux 3.13.0-5-generic Wed Feb 19 11:07:29 2014
6 1 day , 00:55:08 | Linux 3.13.0-5-generic Tue Feb 18 09:45:48 2014
7 5 days, 19:13:24 | Linux 3.13.0-5-generic Wed Feb 12 14:21:42 2014
8 20 days, 02:54:47 | Linux 3.13.0-5-generic Thu Jan 23 11:26:18 2014
#
So the last modification details seem to not correlate with the boot
time -- neither with the last boot nor with any previous boot time.
(And yes, the kernel on that box was not uptodate. It is now. :-)
After the reboot it still looks fine with an uptodate kernel:
# uprecords -Bm1
# Uptime | System Boot up
----------------------------+---------------------------------------------------
-> 1 0 days, 00:07:08 | Linux 3.13.0-24-generic Tue Apr 22 16:04:09 2014
# ps auxwww | fgrep systemd-udev
root 265 0.2 0.1 12260 1672 ? Ss 16:04 0:01
/lib/systemd/systemd-udevd --daemon
root 9653 0.0 0.0 4644 640 pts/0 S+ 16:11 0:00 fgrep
systemd-udev
# lsof -p 265 | fgrep /lib/modules
systemd-u 265 root mem REG 252,0 535555 2499761
/lib/modules/3.13.0-24-generic/modules.symbols.bin
systemd-u 265 root mem REG 252,0 910600 2499757
/lib/modules/3.13.0-24-generic/modules.alias.bin
systemd-u 265 root mem REG 252,0 584127 2499773
/lib/modules/3.13.0-24-generic/modules.dep.bin
systemd-u 265 root mem REG 252,0 9440 2499762
/lib/modules/3.13.0-24-generic/modules.builtin.bin
# lsof -p 265 | fgrep /lib/modules | awk '{print $9}' | xargs ls -l
-rw-r--r-- 1 root root 910600 Apr 22 15:58
/lib/modules/3.13.0-24-generic/modules.alias.bin
-rw-r--r-- 1 root root 9440 Apr 22 15:58
/lib/modules/3.13.0-24-generic/modules.builtin.bin
-rw-r--r-- 1 root root 584127 Apr 22 15:58
/lib/modules/3.13.0-24-generic/modules.dep.bin
-rw-r--r-- 1 root root 535555 Apr 22 15:58
/lib/modules/3.13.0-24-generic/modules.symbols.bin
#
Excerpt from /var/log/aptitude.log:
---8<---
Aptitude 0.6.8.2: log report
Tue, Apr 22 2014 15:51:26 +0200
IMPORTANT: this log only lists intended actions; actions which fail due to
dpkg problems may not be completed.
Will install 7 packages, and remove 0 packages.
222 MB of disk space will be used
===============================================================================
[INSTALL, DEPENDENCIES] linux-headers-3.13.0-24:i386
[INSTALL, DEPENDENCIES] linux-headers-3.13.0-24-generic:i386
[INSTALL, DEPENDENCIES] linux-headers-generic:i386
[INSTALL, DEPENDENCIES] linux-image-3.13.0-24-generic:i386
[INSTALL, DEPENDENCIES] linux-image-extra-3.13.0-24-generic:i386
[INSTALL] linux-generic:i386
[INSTALL] linux-image-generic:i386
===============================================================================
Log complete.
--->8---
The files are clearly touched upon package installation/upgrade, but
not upon boot.
> I can temporarly "fix" this by running "sudo service udev restart"
> (it takes about 5-10 minutes for the change to propergate to the
> xymon server). It'll be ok till the next reboot.
Are you sure that there wasn't a kernel update applied shortly after
the boot, i.e. by running unattended-upgrades via anacron (which often
runs shortly after the boot) or such?
In that case it would be a "true positive" since you got a newer
kernel and haven't rebooted yet.
The only other cause I can imagine for this issue is that you have
some additional package installed which we don't have installed, but
which causes these files to be rebuild at boot time. Any idea which
package could cause such a behaviour?
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310638
Title:
xymon-client libs test gives "libs NOT ok" false positive with
/lib/systemd/systemd-udevd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hobbit-plugins/+bug/1310638/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
