Sfdwhf

Is Screenshot Time-tracking Common?

If angels and devils are the same species, why would their mortal offspring appear physically different?

Why is the "Domain users" group missing from this PowerShell AD query?

How would an AI self awareness kill switch work?

What's this assembly doing?

What is the wife of a henpecked husband called?

What is a good reason for every spaceship to carry a weapon on board?

Can the "Friends" spell be used without making the target hostile?

Existence of Riemann surface, holomorphic maps

Why do neural networks need so many training examples to perform?

Am I correct in stating that the study of topology is purely theoretical?

How does Leonard in "Memento" remember reading and writing?

Book where a space ship journeys to the center of the galaxy to find all the stars had gone supernova

What to do with threats of blacklisting?

How to delete duplicate text from a file?

A Missing Symbol for This Logo

Methods for writing a code review

How vim overwrites readonly mode?

How can the probability of a fumble decrease linearly with more dice?

Why does magnet wire need to be insulated?

Does it take energy to move something in a circle?

Equivalent of "illegal" for violating civil law

What's the oldest plausible frozen specimen for a Jurassic Park style story-line?

Translation needed for 130 years old church document

failed to connect to http://changelogs.ubuntu.com/meta-release

`apt-get update` cannot find Ubuntu serversCan't ssh to localhost on Ubuntu 18.04 in virtualboxSSH: Permission denied, please try again. While tryng to connect to remote 12.04 serverGetting grey hash screen when using RDP into my serverLosing connection with static IPUbuntu server 14.04 doesn't connect by wirelessUnable to access Ubuntu network share from Windows, Ubuntu web interfaces are down and unable to access via PuTTYVPN error “Socket bind failed on local address” “Address is already in use”Fresh install of ubuntu zesty server from dvd not upgradeable.local domain incompatible with Avahi networkLog in error after upgrade to 18.04 LTSI can ssh via port 42043, but not via port 7999 (connection refused)

13

2

When I log into my Ubuntu terminal tty1, I get a message

failed to connect to http://changelogs.ubuntu.com/meta-release

I try various things, then I get an error message telling me

could not resolve us.archive.ubuntu.com

My internet connectivity is apparently disabled and I could not configure it.

I tried rebooting but nothing changed.

server

share|improve this question

edited May 16 '18 at 15:34

Zanna

50.9k13136241

asked May 27 '17 at 14:37

habibhabib

66114

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please explain your issue with more details. When you see this message ? Can you use this command sudo apt update ? Do you set any proxy for your system ? Can you ping any sites ?
  
  – Ali Razmdideh
  May 27 '17 at 14:44
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  When I use sudo apt update i get the following err:1 http:/us.archive.ubuntu.com/ubuntu zesty InRelease could not resolve 'us.archive.ubuntu.com' err:2 http:/us.archive.ubuntu.com/ubuntu zesty-updates InRelease could not resolve 'us.archive.ubuntu.com'
  
  – habib
  May 27 '17 at 14:54
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Do you set proxy for your system or shell ? What the output of this command ping us.archive.ubuntu.com -c 4
  
  – Ali Razmdideh
  May 27 '17 at 14:58
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  err:3 http:/us.archive.ubuntu.com/ubuntu zesty-backports InRelease could not resolve 'us.archive.ubuntu.com
  
  – habib
  May 27 '17 at 14:59
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This question shouldn't have been closed as duplicate. The two are related for sure, but they are not duplicates. All of the answers on the other question deal with network configuration problems. However I have just experienced this error message showing up on a system which doesn't have any such configuration problems. The answer below documents why the error message persists even if there is no networking problem and provides information on how one can make the error message go away.
  
  – kasperd
  yesterday
  

  
  
  
  

 | 
show 4 more comments

13

2

When I log into my Ubuntu terminal tty1, I get a message

failed to connect to http://changelogs.ubuntu.com/meta-release

I try various things, then I get an error message telling me

could not resolve us.archive.ubuntu.com

My internet connectivity is apparently disabled and I could not configure it.

I tried rebooting but nothing changed.

server

share|improve this question

edited May 16 '18 at 15:34

Zanna

50.9k13136241

asked May 27 '17 at 14:37

habibhabib

66114

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please explain your issue with more details. When you see this message ? Can you use this command sudo apt update ? Do you set any proxy for your system ? Can you ping any sites ?
  
  – Ali Razmdideh
  May 27 '17 at 14:44
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  When I use sudo apt update i get the following err:1 http:/us.archive.ubuntu.com/ubuntu zesty InRelease could not resolve 'us.archive.ubuntu.com' err:2 http:/us.archive.ubuntu.com/ubuntu zesty-updates InRelease could not resolve 'us.archive.ubuntu.com'
  
  – habib
  May 27 '17 at 14:54
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Do you set proxy for your system or shell ? What the output of this command ping us.archive.ubuntu.com -c 4
  
  – Ali Razmdideh
  May 27 '17 at 14:58
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  err:3 http:/us.archive.ubuntu.com/ubuntu zesty-backports InRelease could not resolve 'us.archive.ubuntu.com
  
  – habib
  May 27 '17 at 14:59
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This question shouldn't have been closed as duplicate. The two are related for sure, but they are not duplicates. All of the answers on the other question deal with network configuration problems. However I have just experienced this error message showing up on a system which doesn't have any such configuration problems. The answer below documents why the error message persists even if there is no networking problem and provides information on how one can make the error message go away.
  
  – kasperd
  yesterday
  

  
  
  
  

 | 
show 4 more comments

When I log into my Ubuntu terminal tty1, I get a message

failed to connect to http://changelogs.ubuntu.com/meta-release

I try various things, then I get an error message telling me

could not resolve us.archive.ubuntu.com

My internet connectivity is apparently disabled and I could not configure it.

I tried rebooting but nothing changed.

server

share|improve this question

edited May 16 '18 at 15:34

Zanna

50.9k13136241

asked May 27 '17 at 14:37

habibhabib

66114

failed to connect to http://changelogs.ubuntu.com/meta-release

could not resolve us.archive.ubuntu.com

share|improve this question

edited May 16 '18 at 15:34

Zanna

50.9k13136241

asked May 27 '17 at 14:37

habibhabib

66114

share|improve this question

edited May 16 '18 at 15:34

Zanna

50.9k13136241

asked May 27 '17 at 14:37

habibhabib

66114

edited May 16 '18 at 15:34

Zanna

50.9k13136241

edited May 16 '18 at 15:34

Zanna

50.9k13136241

asked May 27 '17 at 14:37

habibhabib

66114

asked May 27 '17 at 14:37

habibhabib

66114

1 Answer
1

active

oldest

votes

20

I had this same problem with 17.10, but I'm betting the same applies to other recent versions as well.

Those MOTD messages are generated by scripts in /etc/update-motd.d. The exact script that generates that specific line is /etc/update-motd.d/91-release-upgrade, which also runs /usr/lib/ubuntu-release-upgrader/release-upgrade-motd. This last script will check for new releases and write output into /var/lib/ubuntu-release-upgrader/release-upgrade-available.

The script will only update the file every 24 hours. So if you wait long enough, the file will go stale and the script will update the file anyway. But, if you want to update it immediately, just remove /var/lib/ubuntu-release-upgrader/release-upgrade-available and run /etc/update-motd.d/91-release-upgrade and it should start working correctly.

I created this problem because when I first setup my 17.10 server, I had a typo in my DNS server address.

share|improve this answer

edited Jan 24 '18 at 9:41

David Foerster

28.3k1365111

answered Jan 9 '18 at 20:32

Anthony CascianelliAnthony Cascianelli

20123

• 
  
  
  

  
  7
  

  
  
  
  
  
  

  
  
  Because I can't comment on the answer of @anthony-cascianelli (reputation < 50) I'm posting an answer instead. After removing /var/lib/ubuntu-release-upgrader/release-upgrade-available, run /usr/lib/ubuntu-release-upgrader/release-upgrade-motd instead of /etc/update-motd.d/91-release-upgrade. This is what worked for me.
  
  – eiro
  Jan 24 '18 at 7:03
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  In my case, simply removing /var/lib/ubuntu-release-upgrader/release-upgrade-available was enough. Next time you login, it will see there's no cache and run the check script automatically.
  
  – Dave S
  Sep 29 '18 at 11:16
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oh my god. Thank you, man. There was lots of other suggestions around the internet for this error. The were talking about support for https proxies and whatnot - which seemed strange to me. Your answer was exact on the spot: I also had a DNS problem the first boot, which then evidently literally tainted this file "forever" (i.e. for 24 hours).
  
  – stolsvik
  Nov 18 '18 at 13:24
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I got the same problem on Ubuntu Server 18.04. The error message is the same except it has -lts at the end. In my case there appears to have been no configuration error. The error message showed up after the system has been running for weeks without any problems. So apparently the error message can show up spontaneously. Too bad this question is closed as a duplicate, since your answer clearly shows that the bad output can persist even if none of the problems mentioned in the supposed duplicate are present.
  
  – kasperd
  yesterday
  

  
  
  
  

add a comment | 

protected by Community♦ May 15 '18 at 19:09

Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?

20

I had this same problem with 17.10, but I'm betting the same applies to other recent versions as well.

Those MOTD messages are generated by scripts in /etc/update-motd.d. The exact script that generates that specific line is /etc/update-motd.d/91-release-upgrade, which also runs /usr/lib/ubuntu-release-upgrader/release-upgrade-motd. This last script will check for new releases and write output into /var/lib/ubuntu-release-upgrader/release-upgrade-available.

The script will only update the file every 24 hours. So if you wait long enough, the file will go stale and the script will update the file anyway. But, if you want to update it immediately, just remove /var/lib/ubuntu-release-upgrader/release-upgrade-available and run /etc/update-motd.d/91-release-upgrade and it should start working correctly.

I created this problem because when I first setup my 17.10 server, I had a typo in my DNS server address.

share|improve this answer

edited Jan 24 '18 at 9:41

David Foerster

28.3k1365111

answered Jan 9 '18 at 20:32

Anthony CascianelliAnthony Cascianelli

20123

• 
  
  
  

  
  7
  

  
  
  
  
  
  

  
  
  Because I can't comment on the answer of @anthony-cascianelli (reputation < 50) I'm posting an answer instead. After removing /var/lib/ubuntu-release-upgrader/release-upgrade-available, run /usr/lib/ubuntu-release-upgrader/release-upgrade-motd instead of /etc/update-motd.d/91-release-upgrade. This is what worked for me.
  
  – eiro
  Jan 24 '18 at 7:03
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  In my case, simply removing /var/lib/ubuntu-release-upgrader/release-upgrade-available was enough. Next time you login, it will see there's no cache and run the check script automatically.
  
  – Dave S
  Sep 29 '18 at 11:16
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oh my god. Thank you, man. There was lots of other suggestions around the internet for this error. The were talking about support for https proxies and whatnot - which seemed strange to me. Your answer was exact on the spot: I also had a DNS problem the first boot, which then evidently literally tainted this file "forever" (i.e. for 24 hours).
  
  – stolsvik
  Nov 18 '18 at 13:24
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I got the same problem on Ubuntu Server 18.04. The error message is the same except it has -lts at the end. In my case there appears to have been no configuration error. The error message showed up after the system has been running for weeks without any problems. So apparently the error message can show up spontaneously. Too bad this question is closed as a duplicate, since your answer clearly shows that the bad output can persist even if none of the problems mentioned in the supposed duplicate are present.
  
  – kasperd
  yesterday
  

  
  
  
  

add a comment | 

20

I had this same problem with 17.10, but I'm betting the same applies to other recent versions as well.

Those MOTD messages are generated by scripts in /etc/update-motd.d. The exact script that generates that specific line is /etc/update-motd.d/91-release-upgrade, which also runs /usr/lib/ubuntu-release-upgrader/release-upgrade-motd. This last script will check for new releases and write output into /var/lib/ubuntu-release-upgrader/release-upgrade-available.

The script will only update the file every 24 hours. So if you wait long enough, the file will go stale and the script will update the file anyway. But, if you want to update it immediately, just remove /var/lib/ubuntu-release-upgrader/release-upgrade-available and run /etc/update-motd.d/91-release-upgrade and it should start working correctly.

I created this problem because when I first setup my 17.10 server, I had a typo in my DNS server address.

share|improve this answer

edited Jan 24 '18 at 9:41

David Foerster

28.3k1365111

answered Jan 9 '18 at 20:32

Anthony CascianelliAnthony Cascianelli

20123

• 
  
  
  

  
  7
  

  
  
  
  
  
  

  
  
  Because I can't comment on the answer of @anthony-cascianelli (reputation < 50) I'm posting an answer instead. After removing /var/lib/ubuntu-release-upgrader/release-upgrade-available, run /usr/lib/ubuntu-release-upgrader/release-upgrade-motd instead of /etc/update-motd.d/91-release-upgrade. This is what worked for me.
  
  – eiro
  Jan 24 '18 at 7:03
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  In my case, simply removing /var/lib/ubuntu-release-upgrader/release-upgrade-available was enough. Next time you login, it will see there's no cache and run the check script automatically.
  
  – Dave S
  Sep 29 '18 at 11:16
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oh my god. Thank you, man. There was lots of other suggestions around the internet for this error. The were talking about support for https proxies and whatnot - which seemed strange to me. Your answer was exact on the spot: I also had a DNS problem the first boot, which then evidently literally tainted this file "forever" (i.e. for 24 hours).
  
  – stolsvik
  Nov 18 '18 at 13:24
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I got the same problem on Ubuntu Server 18.04. The error message is the same except it has -lts at the end. In my case there appears to have been no configuration error. The error message showed up after the system has been running for weeks without any problems. So apparently the error message can show up spontaneously. Too bad this question is closed as a duplicate, since your answer clearly shows that the bad output can persist even if none of the problems mentioned in the supposed duplicate are present.
  
  – kasperd
  yesterday
  

  
  
  
  

add a comment | 

I had this same problem with 17.10, but I'm betting the same applies to other recent versions as well.

Those MOTD messages are generated by scripts in /etc/update-motd.d. The exact script that generates that specific line is /etc/update-motd.d/91-release-upgrade, which also runs /usr/lib/ubuntu-release-upgrader/release-upgrade-motd. This last script will check for new releases and write output into /var/lib/ubuntu-release-upgrader/release-upgrade-available.

The script will only update the file every 24 hours. So if you wait long enough, the file will go stale and the script will update the file anyway. But, if you want to update it immediately, just remove /var/lib/ubuntu-release-upgrader/release-upgrade-available and run /etc/update-motd.d/91-release-upgrade and it should start working correctly.

I created this problem because when I first setup my 17.10 server, I had a typo in my DNS server address.

share|improve this answer

edited Jan 24 '18 at 9:41

David Foerster

28.3k1365111

answered Jan 9 '18 at 20:32

Anthony CascianelliAnthony Cascianelli

20123

share|improve this answer

edited Jan 24 '18 at 9:41

David Foerster

28.3k1365111

answered Jan 9 '18 at 20:32

Anthony CascianelliAnthony Cascianelli

20123

edited Jan 24 '18 at 9:41

David Foerster

28.3k1365111

edited Jan 24 '18 at 9:41

David Foerster

28.3k1365111

answered Jan 9 '18 at 20:32

Anthony CascianelliAnthony Cascianelli

20123

answered Jan 9 '18 at 20:32

Anthony CascianelliAnthony Cascianelli

20123