Upgrade to 20.04.1 no internet

Chris chris.pollock1948 at gmail.com
Sat Oct 3 15:01:34 UTC 2020


On Sun, 2020-10-04 at 00:35 +1000, Karl Auer wrote:
> On Sat, 2020-10-03 at 09:20 -0500, Chris wrote:
> > On Sat, 2020-10-03 at 14:54 +0100, Colin Law wrote:
> > > On Sat, 3 Oct 2020 at 14:42, Chris <chris.pollock1948 at gmail.com>
> > > wrote:
> > > > A little after 11pm CDT last night suddenly the internet came
> > > > back
> > > > up
> > > > however I'm not sure if it's permanent or not. Here's the
> > > > output
> > > > of
> > > > ip
> > > > addr and I added the output of route:
> > > 
> > > Are you saying it has now fixed itself and the problem is, at
> > > least
> > > for the moment, gone?
> > > You say the internet came back up but lack of internet was not
> > > the
> > > fundamental problem. You said you had no network connectivity
> > > which
> > > suggests that networking was completely down so you couldn't even
> > > access your router or other devices on the local network.
> > > 
> > Yes, I have no outside connectivity. I could access my DSL modem by
> > pinging 192.168.0.220 and BIND DNS 127.0.0.1 but nothing outside of
> > that on the desktop.
> 
> 192.168.0.220 was (is?) the IPv4 address of your computer's
> interface;
> the router is on 192.168.0.1. At least, according to the log you put
> in
> Pastebin.
> 
> Did you try pinging an IP address (NOT repeat NOT a domain name)
> outside your network?
> 
I've found the problem. I run Bind9 as a caching name server and for
some unknown reason it's not starting since the upgrade:

localhost named[290337]: using default UDP/IPv4 port range: [32768,
60999]
localhost named[290337]: listening on IPv4 interface lo, 127.0.0.1#53
localhost named[290337]: creating TCP socket: address in use
localhost named[290337]: unable to listen on any configured interfaces
localhost named[290337]: loading configuration: failure
localhost named[290337]: exiting (due to fatal error)
localhost systemd[1]: bind9.service: Main process exited, code=exited,
status=1/FAILURE
localhost systemd[1]: bind9.service: Failed with result 'exit-code'.

I 'think' if I can get that figured out I may be on the way to getting
this back up again.

-- 
Chris
31.11972; -97.90167 (Elev. 1092 ft)
09:57:40 up 10:13, 1 user, load average: 0.27, 0.53, 0.66
Description:	Ubuntu 20.04.1 LTS, kernel 5.4.0-48-generic





More information about the ubuntu-users mailing list