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
> 

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to