PDA

View Full Version : [SOLVED] 16.04lts to 18.04lts slow boot, apache problems,



Frank P
June 22nd, 2019, 06:22 PM
Updated fully operational Ubuntu 16.04lts server to 18.04lts. Problems

Extremely slow boot

Accessing Web page from other PCs - page will not open - can only download
apache2 access.log and error.log entries are identical to a functioning server

Message on boot
Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings

Where do I start looking?

Thanks

Frank P
June 24th, 2019, 09:49 PM
This is an update with more information for a question I posted earlier

Upgraded to 18.04 lts server from 16.04lts server 2 days ago. Upgrade completed with no errors.
However receive the following error message when logging on. My internet connection seems okay - I can ping & ssh to server. When I access apache2 via IP page doesn't display - wants to download


Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings



And this when trying to check for updates


Err:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:2 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Temporary failure resolving 'us.archive.ubuntu.com'
Err:3 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
Temporary failure resolving 'us.archive.ubuntu.com'
Err:4 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
Temporary failure resolving 'us.archive.ubuntu.com'
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/bionic/InRelease Temporary failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Temporary failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Temporary failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease Temporary failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
woodpig@vostro1310:~$ Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings
Failed: command not found


Any suggestions?
Thanks
Frank P

oldos2er
June 25th, 2019, 04:08 PM
Threads merged. If you post additional information please keep it in the original thread rather than starting a new one, less confusion that way.

CatKiller
June 25th, 2019, 04:21 PM
I can't actually help with the problems you're having, but they do seem to be related, and the fundamental issue seems to me that DNS isn't working on that machine.

By default services get 90 seconds each to start up or shut down. So during boot something is looking for an address to connect to and can't, and your boot process is just twiddling its thumbs for a minute and a half.

Finding out why addresses aren't being resolved seems like the thing to do.

Frank P
June 25th, 2019, 04:52 PM
Found this on StackExchange

echo "nameserver 8.8.8.8" | sudo tee/etc/resolvconf/resolv.conf.d/base > /dev/null


It seems to have eliminated the error messages and Apche2 is serving pages. Will wait and see if its permanent

rsteinmetz70112
June 26th, 2019, 07:44 PM
There were a lot of changes in networking from 16.04 to 18.04 and if you customized things the upgrade doesn't always work right. Even if you didn't it sometimes doesn't work.

Frank P
June 26th, 2019, 07:53 PM
Yes, the 16.04 config file was customized so I guess that's what happened. .
Found an excellent tutorial on installing 18.04 on Digital Ocean
I've done a 'clean' install using ethernet that basically works - apache2 will serve pages and parse PHP files.

Now trying to set a static ip and next get wireless working

Then find out why it still takes over a minute to boot

Thanks

Frank

CatKiller
June 27th, 2019, 12:55 AM
Then find out why it still takes over a minute to boot

systemd-analyze blame might help with that. It shows the amount of time different services take for one part of the bootup process - I can't remember which. I suspect that one of them will be taking a long time, and then being stopped after 90 seconds.

Frank P
June 27th, 2019, 01:19 AM
I'll give that a try and post results
Thanks

Frank P
June 28th, 2019, 06:17 PM
I'm going to mark this "solved" because I can't mark it "given up" :-)
I don't know who switching to NetPlan was suppsed to benifit, but it sure wasn't me.
Going to reinstall 16.04LTS and hang on for another 2 years

Thanks

Frank P