Hardware clock: BIOS clock unstable.

stf92 · 08-17-2020, 04:42 PM

Code:

root@darkstar:~# ntpdate pool.ntp.org
17 Aug 21:40:03 ntpdate[1131]: the NTP socket is in use, exiting
root@darkstar:~#

This was under debian 10. I first, by mistake, installed ntp. Then, recognizing my error, install ntpdate. Now, this is the output I get. Why?

I even reboot and ran the command again.

michaelk · 08-17-2020, 05:18 PM

Quote:

Originally Posted by stf92

I have first to set the hardware clock to the correct time in the BIOS menu. Once this is done, I'll issue the above command and see what happens.

No, use the date --set="string" to set the system clock.

[/quote]date --set="17 AUG 2020 18:00:00" [/quote]

You can not run ntp and command ntpdate at the same time since they both use the same port. Stop ntp first.

ntpdate is run once to sync time but ntp runs continuously.

stf92 · 08-17-2020, 06:50 PM

Code:

root@darkstar:/etc/init.d# ntpd stop
root@darkstar:/etc/init.d# ntpdate pool.ntp.org
17 Aug 23:45:16 ntpdate[1368]: the NTP socket is in use, exiting
root@darkstar:/etc/init.d# update-rc.d -f ntpd remove
root@darkstar:/etc/init.d# ntpdate pool.ntp.org
17 Aug 23:48:03 ntpdate[1421]: the NTP socket is in use, exiting
root@darkstar:/etc/init.d#

How do I stop ntp?

michaelk · 08-17-2020, 07:05 PM

Check processes to see if it is really running

stf92 · 08-17-2020, 07:08 PM

Code:

root@darkstar:/etc/init.d# ps -e|grep ntp
  504 ?        00:00:00 ntpd
root@darkstar:/etc/init.d#

michaelk · 08-17-2020, 07:35 PM

ntp is still running.

update-rc will remove the service from automatically starting at boot but not stop a running service.

/etc/rc.d/rc.ntpd stop

stf92 · 08-17-2020, 07:44 PM

My fault. I am in Debian. No /etc/rc.d in Debian. But Debian is the OS that seems to have the problem. Should I stay on it?

michaelk · 08-17-2020, 08:51 PM

debian 10 uses systemd. ntpdate has been deprecated but it is still in the repositories.

systemctl status ntp

systemctl stop ntp

timedatectl status should show RTC in local TZ: no. To match slackware run the command.

timedatectl set-local-rtc 1

stf92 · 08-18-2020, 06:09 AM

Code:

root@darkstar:~# systemctl status ntp
● ntp.service - Network Time Service
   Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-08-18 07:17:04 UTC; 3h 44min ago
     Docs: man:ntpd(8)
  Process: 492 ExecStart=/usr/lib/ntp/ntp-systemd-wrapper (code=exited, status=0/SUCCESS)
 Main PID: 503 (ntpd)
    Tasks: 2 (limit: 2249)
   Memory: 2.5M
   CGroup: /system.slice/ntp.service
           └─503 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 115:123

Aug 18 10:31:05 darkstar ntpd[503]: Soliciting pool server 159.69.38.175
Aug 18 10:31:05 darkstar ntpd[503]: Soliciting pool server 195.21.137.209
Aug 18 10:43:36 darkstar ntpd[503]: 151.80.124.104 local addr 192.168.0.107 -> <null>
Aug 18 10:43:41 darkstar ntpd[503]: 195.21.137.209 local addr 192.168.0.107 -> <null>
Aug 18 10:43:44 darkstar ntpd[503]: 158.174.65.248 local addr 192.168.0.107 -> <null>
Aug 18 10:43:45 darkstar ntpd[503]: 159.69.38.175 local addr 192.168.0.107 -> <null>
Aug 18 10:44:36 darkstar ntpd[503]: 103.120.116.13 local addr 192.168.0.107 -> <null>
Aug 18 10:49:13 darkstar ntpd[503]: 31.131.0.123 local addr 192.168.0.107 -> <null>
Aug 18 10:51:27 darkstar ntpd[503]: 103.76.40.123 local addr 192.168.0.107 -> <null>
Aug 18 10:57:05 darkstar ntpd[503]: 95.97.2.35 local addr 192.168.0.107 -> <null>
root@darkstar:~# systemctl stop ntp

Code:

root@darkstar:~# timedatectl status 
               Local time: Tue 2020-08-18 11:06:04 UTC
           Universal time: Tue 2020-08-18 11:06:04 UTC
                 RTC time: Tue 2020-08-18 11:06:04
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: yes

Warning: The system is configured to read the RTC time in the local time zone.
         This mode cannot be fully supported. It will create various problems
         with time zone changes and daylight saving time adjustments. The RTC
         time is never updated, it relies on external facilities to maintain it.
         If at all possible, use RTC in UTC by calling
         'timedatectl set-local-rtc 0'.
root@darkstar:~#

This is really weird. I had both Arch and Debian in this machine and had no problems with the clock except it couldn't be written. At most, when the machine hanged, I had to manually turn off the machine using the power button and, in this case, maybe I found the RTC contained an incorrect value.