Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I keep getting this message when I logged into my server in ec2 via ssh

think this is called MOTD

43 packages can be updated.
22 updates are security updates.

but I have already done

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

I have also restarted my instance.

Please advise.

share|improve this question
Is your instance ephemeral or EBS backed? – Caleb Apr 23 '11 at 12:54
EBS backed instance – Kim Stacks Apr 27 '11 at 9:46
up vote 11 down vote accepted

Another one of these "fine" Ubuntu-bugs... Check Ubuntu Bug #634387:

I deleted the files "/etc/motd.tail" and "/etc/motd.tail.old" and did a logout / login to re-genereate a propper /etc/motd.

share|improve this answer

This is coming from the MOTD (Message Of The Day). The MOTD is pieced together from the commands in /etc/update-motd.d. The specific message comes from running /etc/update-motd.d/90-updates-available.

I have seen this happen on systems where after running sudo apt-get update and packages are kept back

The following packages have been kept back:
  linux-generic linux-headers-generic linux-image-generic
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

The message can mean several things e.g. there may be dependency issues etc. there is more on this in the APT HowTo.

I have managed to stop the messages with

sudo aptitude update
sudo aptitude safe-upgrade

If that doesn't work then the link above does give advice on how to track down the problem packages.

share|improve this answer

I was seeing this same issue on Ubuntu 14.04

I edited /etc/pam.d/sshd

and changed this line
session optional motd=/run/motd.dynamic noupdate

by removing the noupdate

now the banner displays correctly.

share|improve this answer
I think this answer is moving in the right direction for 14.04. On my own server (Ubuntu Server in a virtual machine), the motd changed after sudo apt-get dist-upgrade. In my case, that required a server restart, so I don't know whether the change to motd was little bit of a coincidence. I did not have to edit any of the files in /etc/pam.d, but I think I'd have first tried editing /etc/pam.d/login. That files has the same motd lines as sshd. – Mike Sherrill 'Cat Recall' Mar 16 '15 at 14:59
I've simply restarted after sudo apt-get dist-upgrade and the message was fixed. – Kimi Apr 20 '15 at 16:46

Try this: sudo apt-get install unattended-upgrades

sudo dpkg-reconfigure --priority=low unattended-upgrades

sudo dpkg-reconfigure -plow unattended-upgrades -f noninteractive -p critical

For more details:

share|improve this answer
You give a recipe, but you're not giving any explanation or justification. – Law29 May 22 at 13:34

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.