removal (not purge) breaks MOTD
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager-core (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Starting a few days ago, all of my 10.04.4 servers ceased printing the MOTD when I SSH'd into them. /etc/motd is a symlink to /var/run/motd which doesn't exist. /var/run/motd.new is being created correctly on each login, e.g.:
Linux <hostname> 2.6.32-
Ubuntu 10.04.4 LTS
Welcome to Ubuntu!
* Documentation: https:/
System information as of Wed Mar 7 10:11:33 PST 2012
System load: 0.08 Processes: 109
Usage of /: 45.4% of 362.86GB Users logged in: 0
Memory usage: 10% IP address for eth0: <addr>
Swap usage: 0% IP address for vboxnet0: <addr>
Graph this data and manage this system at https:/
0 packages can be updated.
0 updates are security updates.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: libpam-modules 1.1.1-2ubuntu5.4
ProcVersionSign
Uname: Linux 2.6.32-
Architecture: i386
Date: Wed Mar 7 10:06:23 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2)
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
SourcePackage: pam
That /var/run/motd.new has been created does not mean that it has been created correctly. Please show the output of the following command run as root:
/usr/bin/env -i PATH=/usr/ local/sbin: /usr/local/ bin:/usr/ sbin:/usr/ bin:/sbin: /bin run-parts --lsbsysinit /etc/update-motd.d > /var/run/motd.new; echo $?
It is likely that one or more of the update-motd scripts is failing on your system, in which case /var/run/motd will not be updated.