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;
I fixed this before seeing comment #2:
run-parts was returning an error code (2 IIRC) because I had removed,
but not purged, update-manager-core from these systems a few days ago.
That resulted in /etc/update-motd.d/91-release-upgrade being left
behind, which would attempt to run
Root cause is update-manager-core removal does not clear no-longer-
functional /etc/update-motd.d script, breaking MOTD. Requires purge.
** Package changed: pam (Ubuntu) = update-manager-core (Ubuntu)
** Summary changed:
- /var/run/motd is not created even though /var/run/motd.new is created
+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949256
Title:
/var/run/motd is not created even though /var/run/motd.new is created
To manage notifications about this bug go to:
