System log had some odd ntp related stuff, anyone able to interpret to me?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
System log had some odd ntp related stuff, anyone able to interpret to me?
Hello! Is anyone able to shed a light what was going on in my Mint system? I didn't notice any odd behaviour. But syslog makes me ponder that maybe everything wasn't allright? And my router seemed to have those IP:s in the UDP connection list in port 123.
Code:
May 11 14:38:59 SUPERSYSTEMNAME ntpd[901]: ntpd exiting on signal 15 (Terminated)
May 11 14:38:59 SUPERSYSTEMNAME ntpd[901]: 162.159.200.123 local addr 192.168.0.111 -> <null>
May 11 14:38:59 SUPERSYSTEMNAME systemd[1]: Stopping Network Time Service...
May 11 14:38:59 SUPERSYSTEMNAME ntpd[901]: 95.217.188.206 local addr 192.168.0.111 -> <null>
May 11 14:38:59 SUPERSYSTEMNAME ntpd[901]: 95.216.147.242 local addr 192.168.0.111 -> <null>
May 11 14:38:59 SUPERSYSTEMNAME ntpd[901]: 95.216.154.135 local addr 192.168.0.111 -> <null>
May 11 14:38:59 SUPERSYSTEMNAME ntpd[901]: 95.216.71.38 local addr 192.168.0.111 -> <null>
May 11 14:38:59 SUPERSYSTEMNAME systemd[1]: Stopped Network Time Service.
May 11 14:38:59 SUPERSYSTEMNAME system-tools-ba[20086]: No such method ServiceConfig->getFiles
May 11 14:39:03 SUPERSYSTEMNAME systemd[1]: Starting Network Time Service...
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20399]: ntpd 4.2.8p10@1.3728-o (1): Starting
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20399]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 111:117
May 11 14:39:03 SUPERSYSTEMNAME systemd[1]: Started Network Time Service.
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20402]: proto: precision = 0.141 usec (-23)
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20402]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20402]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2020-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20402]: Listen and drop on 0 v6wildcard [::]:123
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20402]: Listen and drop on 1 v4wildcard 0.0.0.0:123
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20402]: Listen normally on 2 lo 127.0.0.1:123
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20402]: Listen normally on 3 enp5s0 192.168.0.111:123
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20402]: Listen normally on 4 lo [::1]:123
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20402]: Listen normally on 5 enp5s0 [mac-address]:123
May 11 14:39:03 SUPERSYSTEMNAME ntpd[20402]: Listening on routing socket on fd #22 for interface updates
May 11 14:39:03 SUPERSYSTEMNAME system-tools-ba[20086]: No such method ServiceConfig->getFiles
May 11 14:39:04 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 95.216.24.230
May 11 14:39:05 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 193.166.4.60
May 11 14:39:05 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 95.216.136.148
May 11 14:39:06 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 95.216.154.135
May 11 14:39:06 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 185.103.110.248
May 11 14:39:07 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 62.237.86.234
May 11 14:39:07 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 95.216.147.242
May 11 14:39:07 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 95.216.138.141
May 11 14:39:07 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 62.236.120.71
May 11 14:39:07 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 213.28.138.38
May 11 14:39:08 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 62.241.198.251
May 11 14:39:08 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 95.216.218.15
May 11 14:39:08 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 95.216.238.58
May 11 14:39:08 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 91.189.89.198
May 11 14:39:10 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 91.189.94.4
May 11 14:39:10 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 162.159.200.1
May 11 14:39:10 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 91.189.91.157
Code:
May 11 15:46:48 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 2606:4700:f1::1
May 11 15:46:49 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:46:53 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:46:55 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 91.189.89.199
May 11 15:47:05 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:47:54 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 2a01:4f9:2a:1919::9302
May 11 15:47:54 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:47:59 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 2001:67c:1560:8003::c8
May 11 15:47:59 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:48:09 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:48:58 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 2a01:4f9:c010:1eba::1
May 11 15:48:59 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:49:03 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 2001:67c:1560:8003::c7
May 11 15:49:04 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:49:14 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:50:03 SUPERSYSTEMNAME ntpd[20402]: Soliciting pool server 2606:4700:f1::123
May 11 15:50:05 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:50:08 SUPERSYSTEMNAME ntpd[20402]: error resolving pool ntp.ubuntu.com: Name or service not known (-2)
May 11 15:50:08 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:50:19 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:51:09 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 2.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:51:10 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:51:15 SUPERSYSTEMNAME ntpd[20402]: error resolving pool ntp.ubuntu.com: Name or service not known (-2)
May 11 15:51:15 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:51:25 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:52:13 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 2.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:52:16 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:52:19 SUPERSYSTEMNAME ntpd[20402]: error resolving pool ntp.ubuntu.com: Name or service not known (-2)
May 11 15:52:21 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:52:29 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:53:17 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 2.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:53:23 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
May 11 15:53:26 SUPERSYSTEMNAME ntpd[20402]: error resolving pool ntp.ubuntu.com: Name or service not known (-2)
May 11 15:53:26 SUPERSYSTEMNAME ntpd[20402]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
You do seem to have an ill-configured DNS if the names of the NTP pools can't be resolved. On the other hand, the command ntpq -pn should tell you more about NTP health.
You do seem to have an ill-configured DNS if the names of the NTP pools can't be resolved. On the other hand, the command ntpq -pn should tell you more about NTP health.
Thanks for the reply!
Those were new lines to me in syslog and router had so many adresses in 123 port, never seen them there. So wasn't sure what was going on. However i didn't change any DNS things in system, i don't even know how And in router, i had my ISP:s DNS-servers
I see your time server contacting various internet time server, and failing to contact Ubuntu pool servers. I don't know whether the latter is worrying; probably not. The former is normal, I'd say.
Your Mint system's DNS configuration starts with /etc/resolv.conf.
EDIT: Those name resolution problems may be global. I can't resolve 3.ubuntu.pool.ntp.org right now either.
Last edited by berndbausch; 05-16-2020 at 09:48 AM.
^
Thanks for the reply! I hadn't change anything in the load up or internet related things in the system. Only updates could have change something.
Unfortunately i'm unable anymore do any testing on that system. I had on to-do-list to have a fresh start as it was already 2 years old installation so decided this was good moment to start on clean table as seemed things might go out of my hands and knowledge level.
However, it is interesting to know what was going on for future problems
3.ubuntu.pool.ntp.org can be resolved again. I say you are the victim of a temporary glitch.
Thanks for the reply!
I checked logs i had backuped. It seems something had been going on for a while in this matter i think:
On may 5 there was also in log these same things: "error resolving pool 2.ubuntu.pool.ntp.org: Name or service not known (-2)"
Also on may 10.
Then there was also these:
Code:
May 6 07:18:14 SUPERSYSTEMNAME ntpd[912]: receive: Unexpected origin timestamp 0xe25cb907.12652d6b does not match aorg 0000000000.00000000 from server@62.241.198.253 xmt 0xe25cb906.d22325cc
May 6 07:18:14 SUPERSYSTEMNAME ntpd[912]: receive: Unexpected origin timestamp 0xe25cb907.1265fa78 does not match aorg 0000000000.00000000 from server@62.241.198.251 xmt 0xe25cb906.d22312cb
May 7 06:52:39 SUPERSYSTEMNAME ntpd[917]: receive: Unexpected origin timestamp 0xe25e0487.3e04ce5a does not match aorg 0000000000.00000000 from server@185.103.110.248 xmt 0xe25e0487.0f71eaec
May 7 06:52:39 SUPERSYSTEMNAME ntpd[917]: receive: Unexpected origin timestamp 0xe25e0487.3e06f44f does not match aorg 0000000000.00000000 from server@194.100.2.194 xmt 0xe25e0487.0f61c492
May 7 06:52:39 SUPERSYSTEMNAME ntpd[917]: receive: Unexpected origin timestamp 0xe25e0487.3e08904e does not match aorg 0000000000.00000000 from server@162.159.200.1 xmt 0xe25e0487.0ed06b4e
May 7 06:52:39 SUPERSYSTEMNAME ntpd[917]: receive: Unexpected origin timestamp 0xe25e0487.3e08337b does not match aorg 0000000000.00000000 from server@213.28.138.38 xmt 0xe25e0487.0f528d11
May 7 06:52:39 SUPERSYSTEMNAME ntpd[917]: receive: Unexpected origin timestamp 0xe25e0487.3c10ff8d does not match aorg 0000000000.00000000 from server@91.189.91.157 xmt 0xe25e0487.1931eafc
May 10 06:33:48 SUPERSYSTEMNAME ntpd[902]: receive: Unexpected origin timestamp 0xe261f49b.e0ff4774 does not match aorg 0000000000.00000000 from server@95.216.24.230 xmt 0xe261f49c.2da997e3
May 10 06:33:48 SUPERSYSTEMNAME ntpd[902]: receive: Unexpected origin timestamp 0xe261f49b.e0fcdb9d does not match aorg 0000000000.00000000 from server@62.241.198.253 xmt 0xe261f49c.2f669f9a
May 10 06:33:48 SUPERSYSTEMNAME ntpd[902]: receive: Unexpected origin timestamp 0xe261f49b.e0fe84d7 does not match aorg 0000000000.00000000 from server@162.159.200.123 xmt 0xe261f49c.2ee77b87
May 10 06:33:48 SUPERSYSTEMNAME ntpd[902]: receive: Unexpected origin timestamp 0xe261f49b.ddb50dd0 does not match aorg 0000000000.00000000 from server@91.189.89.198 xmt 0xe261f49c.2f8eb447
But yes, could be temperary glitches i don't really have knowledge about these kind of things
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.