Re: How to get around ntpd catch-22?
Good to know. I was going to suggest that maybe your Internet connection was failing, but I did not do so because you checked it with another machine. On 17/08/17 11:04, Kynn Jones wrote: > It appears that the problem was a network misconfiguration (outside of my > control), and it is now resolved. > > Sorry for the confusing query. signature.asc Description: OpenPGP digital signature
Re: How to get around ntpd catch-22?
Dear sir, unfortunately I do not have a solution to your problem, but I want to note that in “Failed to start ntpd.service: Unit nptd.service not found.” the name of ntpd was spelled “nptd”; maybe that is the source of the problem. It does not appear to me that ntp is preventing the network from restarting, because I see a line “-- The start-up result is done.”. Though I can easily be wrong, as I am no expert in systemd. However, if the ntp package is really causing a problem, and reinstalling is not possible, the obvious solution would be to remove it, and install it again if required after Internet connection is established. I use chrony instead of ntp. It appears to be better documented, designed and maintained. Regards. On 17/08/17 09:51, Kynn Jones wrote: > I installed Debian on a (legacy) Optiplex 9010 desktop, using a minimal USB > installation image, and netinst. IOW, most of the contents of this > installation came in through the network (which rules out the most serious > hardware issues). > > One day later, the network connection suddenly stopped working, at all. > For example, the response to `ping 8.8.8.8` is now `connect: Network is > unreachable`. > > The problem is with the computer not with the jack, because if I plug a > different computer to the same jack the connection works fine. > > I did not touch any network-related config files, so I can't begin to guess > what could have caused this sudden failure. > > If I run `/etc/init.d/networking restart`, the output just says `Restarting > networking (via systemctl): networking.service`. At the end of this > message I post the relevant lines from the output I get if I then run > `journalctl -xe` immediately after. > > One can see that the restart of the network is failing due to an ntpd > problem. > > If I attempt to restart ntpd, I get the error "Failed to start > ntpd.service: Unit nptd.service not found." > > This makes no sense to me: ntpd was clearly available and working for > several hours before this sudden failure. The package is definitely > installed, and the error above persists even after I run `dpkg-reconfigure > -p low ntp` (which requires no input from me). > > The only fix I can think of at this point would be to reinstall ntp > altogether, but I can't do this without an internet connection, so I have a > Catch-22 situation. > > How can I fix this problem without having an internet connection? > > --- > > Aug 17 10:00:42 myhost ntpd[757]: error resolving pool 3.debian.pool.ntp.org: > Temporary failure in name resolution (-3) > Aug 17 10:00:45 myhost systemd[1]: Stopping Raise network interfaces... > -- Subject: Unit networking.service has begun shutting down > -- Defined-By: systemd > -- Support: https://www.debian.org/support > signature.asc Description: OpenPGP digital signature
Re: How to get around ntpd catch-22?
settings for this are in /etc/systemd/timesyncd.conf. On Thu, 17 Aug 2017, Kynn Jones wrote: Date: Thu, 17 Aug 2017 10:51:15 From: Kynn Jones To: Debian User Subject: How to get around ntpd catch-22? Resent-Date: Thu, 17 Aug 2017 14:51:44 + (UTC) Resent-From: debian-user@lists.debian.org I installed Debian on a (legacy) Optiplex 9010 desktop, using a minimal USB installation image, and netinst. IOW, most of the contents of this installation came in through the network (which rules out the most serious hardware issues). One day later, the network connection suddenly stopped working, at all. For example, the response to `ping 8.8.8.8` is now `connect: Network is unreachable`. The problem is with the computer not with the jack, because if I plug a different computer to the same jack the connection works fine. I did not touch any network-related config files, so I can't begin to guess what could have caused this sudden failure. If I run `/etc/init.d/networking restart`, the output just says `Restarting networking (via systemctl): networking.service`. At the end of this message I post the relevant lines from the output I get if I then run `journalctl -xe` immediately after. One can see that the restart of the network is failing due to an ntpd problem. If I attempt to restart ntpd, I get the error "Failed to start ntpd.service: Unit nptd.service not found." This makes no sense to me: ntpd was clearly available and working for several hours before this sudden failure. The package is definitely installed, and the error above persists even after I run `dpkg-reconfigure -p low ntp` (which requires no input from me). The only fix I can think of at this point would be to reinstall ntp altogether, but I can't do this without an internet connection, so I have a Catch-22 situation. How can I fix this problem without having an internet connection? --- Aug 17 10:00:42 myhost ntpd[757]: error resolving pool 3.debian.pool.ntp.org: Temporary failure in name resolution (-3) Aug 17 10:00:45 myhost systemd[1]: Stopping Raise network interfaces... -- Subject: Unit networking.service has begun shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support --
Re: How to get around ntpd catch-22?
Have you tried: sudo -H systemd-timesyncd.service sudo -H timedatectl set-ntp true timedatectl or journalctl -f -u systemd-timesyncd.service to monitor the service? On Thu, 17 Aug 2017, Kynn Jones wrote: Date: Thu, 17 Aug 2017 10:51:15 From: Kynn Jones To: Debian User Subject: How to get around ntpd catch-22? Resent-Date: Thu, 17 Aug 2017 14:51:44 + (UTC) Resent-From: debian-user@lists.debian.org I installed Debian on a (legacy) Optiplex 9010 desktop, using a minimal USB installation image, and netinst. IOW, most of the contents of this installation came in through the network (which rules out the most serious hardware issues). One day later, the network connection suddenly stopped working, at all. For example, the response to `ping 8.8.8.8` is now `connect: Network is unreachable`. The problem is with the computer not with the jack, because if I plug a different computer to the same jack the connection works fine. I did not touch any network-related config files, so I can't begin to guess what could have caused this sudden failure. If I run `/etc/init.d/networking restart`, the output just says `Restarting networking (via systemctl): networking.service`. At the end of this message I post the relevant lines from the output I get if I then run `journalctl -xe` immediately after. One can see that the restart of the network is failing due to an ntpd problem. If I attempt to restart ntpd, I get the error "Failed to start ntpd.service: Unit nptd.service not found." This makes no sense to me: ntpd was clearly available and working for several hours before this sudden failure. The package is definitely installed, and the error above persists even after I run `dpkg-reconfigure -p low ntp` (which requires no input from me). The only fix I can think of at this point would be to reinstall ntp altogether, but I can't do this without an internet connection, so I have a Catch-22 situation. How can I fix this problem without having an internet connection? --- Aug 17 10:00:42 myhost ntpd[757]: error resolving pool 3.debian.pool.ntp.org: Temporary failure in name resolution (-3) Aug 17 10:00:45 myhost systemd[1]: Stopping Raise network interfaces... -- Subject: Unit networking.service has begun shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support --
Re: How to get around ntpd catch-22?
It appears that the problem was a network misconfiguration (outside of my control), and it is now resolved. Sorry for the confusing query.
Re: How to get around ntpd catch-22?
On Thu, Aug 17, 2017 at 10:00:48AM -0500, Mario Castelán Castro wrote: > Dear sir, unfortunately I do not have a solution to your problem, but I > want to note that in “Failed to start ntpd.service: Unit nptd.service > not found.” the name of ntpd was spelled “nptd”; maybe that is the > source of the problem. In fact, they are both wrong, at least in stretch. wooledg:~$ LC_ALL=C systemctl status ntp * ntp.service - LSB: Start NTP daemon Loaded: loaded (/etc/init.d/ntp; generated; vendor preset: enabled) Active: active (running) since Mon 2017-08-07 08:07:33 EDT; 1 weeks 3 days ag Docs: man:systemd-sysv-generator(8) Process: 580 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS) Tasks: 2 (limit: 4915) CGroup: /system.slice/ntp.service `-606 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 109:113 The service is spelled "ntp.service". There is not currently a systemd unit file for it; it's using the init.d script named "ntp" instead. Beyond that, I have no idea what caused the OP's problem.
How to get around ntpd catch-22?
I installed Debian on a (legacy) Optiplex 9010 desktop, using a minimal USB installation image, and netinst. IOW, most of the contents of this installation came in through the network (which rules out the most serious hardware issues). One day later, the network connection suddenly stopped working, at all. For example, the response to `ping 8.8.8.8` is now `connect: Network is unreachable`. The problem is with the computer not with the jack, because if I plug a different computer to the same jack the connection works fine. I did not touch any network-related config files, so I can't begin to guess what could have caused this sudden failure. If I run `/etc/init.d/networking restart`, the output just says `Restarting networking (via systemctl): networking.service`. At the end of this message I post the relevant lines from the output I get if I then run `journalctl -xe` immediately after. One can see that the restart of the network is failing due to an ntpd problem. If I attempt to restart ntpd, I get the error "Failed to start ntpd.service: Unit nptd.service not found." This makes no sense to me: ntpd was clearly available and working for several hours before this sudden failure. The package is definitely installed, and the error above persists even after I run `dpkg-reconfigure -p low ntp` (which requires no input from me). The only fix I can think of at this point would be to reinstall ntp altogether, but I can't do this without an internet connection, so I have a Catch-22 situation. How can I fix this problem without having an internet connection? --- Aug 17 10:00:42 myhost ntpd[757]: error resolving pool 3.debian.pool.ntp.org: Temporary failure in name resolution (-3) Aug 17 10:00:45 myhost systemd[1]: Stopping Raise network interfaces... -- Subject: Unit networking.service has begun shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit networking.service has begun shutting down. Aug 17 10:00:46 myhost systemd[1]: Stopped Raise network interfaces. -- Subject: Unit networking.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit networking.service has finished shutting down. Aug 17 10:00:46 myhost systemd[1]: Starting Raise network interfaces... -- Subject: Unit networking.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit networking.service has begun starting up. Aug 17 10:00:46 myhost systemd[1]: Started Raise network interfaces. -- Subject: Unit networking.service has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit networking.service has finished starting up. -- -- The start-up result is done. Aug 17 10:00:48 myhost ntpd[757]: error resolving pool 2.debian.pool.ntp.org: Temporary failure in name resolution (-3) Aug 17 10:00:49 myhost ntpd[757]: error resolving pool 1.debian.pool.ntp.org: Temporary failure in name resolution (-3)
