Duplicate fsck information in /etc/motd

Bug #1240549 reported by Marius Gedminas
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Fix Released
Medium
Brian Murray

Bug Description

Occasionaly I ssh into an Ubuntu 12.04 LTS server and see this:

    *** /dev/md0 will be checked for errors at next reboot ***
    *** /dev/md0 will be checked for errors at next reboot ***
    *** /dev/md3 will be checked for errors at next reboot ***
    *** /dev/md3 will be checked for errors at next reboot ***
    *** /dev/md4 will be checked for errors at next reboot ***
    *** /dev/md4 will be checked for errors at next reboot ***
    *** /dev/md2 will be checked for errors at next reboot ***
    *** /dev/md2 will be checked for errors at next reboot ***
    *** /dev/md1 will be checked for errors at next reboot ***
    *** /dev/md1 will be checked for errors at next reboot ***

As far as I can tell this happens if two logins happen more or less simultaneously, since /usr/lib/update-notifier/update-motd-fsck-at-reboot does not use any locking.

Once I've seen the information repeated three times.

This is very similar to LP#1146170, except in a different script.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: update-notifier-common 0.119ubuntu8.6 [modified: usr/lib/update-notifier/update-motd-updates-available]
ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
Uname: Linux 3.2.0-52-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.5
Architecture: amd64
Date: Wed Oct 16 17:28:40 2013
MarkForUpload: True
PackageArchitecture: all
SourcePackage: update-notifier
UpgradeStatus: Upgraded to precise on 2012-07-31 (442 days ago)

Related branches

Revision history for this message
Marius Gedminas (mgedmin) wrote :
Changed in update-notifier (Ubuntu):
importance: Undecided → Medium
Changed in update-notifier (Ubuntu):
status: New → Triaged
Revision history for this message
Marius Gedminas (mgedmin) wrote :

Similar to bug 1146170, I could reproduce this with

    bzr branch lp:update-notifier && cd update-notifier
    sudo -s
    rm /var/lib/update-notifier/fsck-at-reboot; data/update-motd-fsck-at-reboot & data/update-motd-fsck-at-reboot

and I cannot reproduce it any more after my fix in http://bazaar.launchpad.net/~mgedmin/update-notifier/fix-lp1240549/revision/830

Revision history for this message
Brian Murray (brian-murray) wrote :

I've merged this, thanks!

Changed in update-notifier (Ubuntu):
assignee: nobody → Brian Murray (brian-murray)
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-notifier - 0.148

---------------
update-notifier (0.148) trusty; urgency=low

  [ Iain Lane ]
  * data/update-motd-updates-available: Update the stamp file atomically.
    Thanks to Marius Gedminas! (LP: #1146170)

  [ Brian Murray ]
  * In the upstart crash notification job fix the path for watershed.
  * debian/update-notifier-crash.conf: check that we have read permission on
    the crash file before launching apport-gtk, additionally just launch
    apport-gtk or system-crash-notification as they will check for new crashes
    and start bug filing for each one (LP: #1193509)
  * data/update-motd-fsck-at-reboot: Update the stamp file atomically.
    Thanks to Marius Gedminas! (LP: #1240549)
 -- Brian Murray <email address hidden> Fri, 08 Nov 2013 15:32:25 -0800

Changed in update-notifier (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.