You are not logged in.

Pages: 1

#1 2024-06-07 15:34:50

0liver
Member
Registered: 2014-05-20
Posts: 42

[solved] ntpd segfault at boot after upgrade

[   16.918299] ntpd[697]: segfault at 24 ip 000059554d0a22d2 sp 00007ffd1adcd5f0 error 4 in ntpd[59554d03c000+7f000] likely on CPU 2 (core 2, socket 0)
[   16.918309] Code: 1c 25 28 00 00 00 48 89 5d c8 48 89 fb ff 15 6d 42 04 00 44 8b 30 49 89 c5 e8 ca 5a ff ff 49 89 c4 48 85 db 0f 84 e6 00 00 00 <44> 0f b7 0b 66 41 83 f9 02 0f 84 f7 00 00 00 66 41 83 f9 0a 74 58

$ systemctl status ntpd
● ntpd.service - Network Time Service
     Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; preset: disabled)
     Active: active (running) since Fri 2024-06-07 16:42:32 CEST; 49min ago
    Process: 745 ExecStart=/usr/bin/ntpd -g -u ntp:ntp (code=exited, status=0/SUCCESS)
   Main PID: 747 (ntpd)
      Tasks: 2 (limit: 18846)
     Memory: 1.1M (peak: 2.1M)
        CPU: 280ms
     CGroup: /system.slice/ntpd.service
             └─747 /usr/bin/ntpd -g -u ntp:ntp

Jun 07 16:42:32 L3800 ntpd[747]: Listen normally on 3 enp0s20f0u2u4 192.168.178.41:123
Jun 07 16:42:32 L3800 ntpd[747]: Listen normally on 4 lo [::1]:123
Jun 07 16:42:32 L3800 ntpd[747]: Listen normally on 5 enp0s20f0u2u4 [fe80::6d75:88c7:302f:78c5%2]:123
Jun 07 16:42:32 L3800 ntpd[747]: Listening on routing socket on fd #22 for interface updates
Jun 07 16:42:32 L3800 ntpd[747]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Jun 07 16:42:32 L3800 ntpd[747]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Jun 07 16:42:32 L3800 systemd[1]: Started Network Time Service.
Jun 07 16:42:49 L3800 ntpd[747]: Listen normally on 6 wlp2s0 192.168.178.29:123
Jun 07 16:42:49 L3800 ntpd[747]: Listen normally on 7 wlp2s0 [fe80::796b:3d42:6c74:265f%4]:123
Jun 07 16:42:49 L3800 ntpd[747]: new interface(s) found: waking up resolver

 systemctl status systemd-timesyncd
○ systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: enabled)
     Active: inactive (dead) since Fri 2024-06-07 16:42:31 CEST; 46min ago
   Duration: 1.233s
       Docs: man:systemd-timesyncd.service(8)
    Process: 585 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=0/SUCCESS)
   Main PID: 585 (code=exited, status=0/SUCCESS)
     Status: "Idle."
        CPU: 74ms

Jun 07 16:42:29 L3800 systemd[1]: Starting Network Time Synchronization...
Jun 07 16:42:30 L3800 systemd[1]: Started Network Time Synchronization.
Jun 07 16:42:31 L3800 systemd[1]: Stopping Network Time Synchronization...
Jun 07 16:42:31 L3800 systemd[1]: systemd-timesyncd.service: Deactivated successfully.
Jun 07 16:42:31 L3800 systemd[1]: Stopped Network Time Synchronization.

Last edited by 0liver (2024-06-07 21:01:21)

Offline

#2 2024-06-07 18:33:55

loqs
Member
Registered: 2014-03-06
Posts: 17,861

Re: [solved] ntpd segfault at boot after upgrade

Please post the backtrace with debug symbols from the coredump the segfault should have produced.

Offline

#3 2024-06-07 19:23:07

0liver
Member
Registered: 2014-05-20
Posts: 42

Re: [solved] ntpd segfault at boot after upgrade

i disabled coredump long time ago since the dumps took too much disk space.

if nobody else has this error and you believe the segfault it is worth tracking down, i'll reenable coredump, reboot, and send the backtrace.

Offline

#4 2024-06-07 19:58:36

seth
Member
Registered: 2012-09-03
Posts: 56,103

Re: [solved] ntpd segfault at boot after upgrade

i disabled coredump long time ago since the dumps took too much disk space.

DOwuJt.gif

Why do you run timesyncd next to ntpd?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2024-06-07 20:37:24

0liver
Member
Registered: 2014-05-20
Posts: 42

Re: [solved] ntpd segfault at boot after upgrade

i only run ntpd and included the status output of timesyncd which shows it is inactive.

that both are installed is a relict because at arch linux installation (in 2019) i had problems getting up the time synchronization..

should i uninstall timesyncd?

Offline

#6 2024-06-07 20:41:16

seth
Member
Registered: 2012-09-03
Posts: 56,103

Re: [solved] ntpd segfault at boot after upgrade

timesyncd is inactive *now* but it  certainly ran at 16:42:31

should i uninstall timesyncd?

It's part of the systemd-moloch, so you cannot uninstall it, but you can certainly "systemctl disable systemd-timesyncd" and shoud if you want to use ntpd for time synchronization.
If the ntpd crashes remain we'll however require a coredump for any chance to tell "why is that?"

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2024-06-07 20:48:36

0liver
Member
Registered: 2014-05-20
Posts: 42

Re: [solved] ntpd segfault at boot after upgrade

seth wrote:

timesyncd is inactive *now* but it  certainly ran at 16:42:31

yes, only because i ran:

$ systemctl status systemd-timesyncd

ok. i'll do:

$ systemctl disable systemd-timesyncd

and report back after reboot.

...

the ntpd segfault disappeared after reboot.

thank you for your help!

Last edited by 0liver (2024-06-07 21:08:30)

Offline

#8 2024-06-07 21:01:54

seth
Member
Registered: 2012-09-03
Posts: 56,103

Re: [solved] ntpd segfault at boot after upgrade

First expectable result would be

◉ systemctl status systemd-timesyncd                    
○ systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disabled; preset: enabled)
     Active: inactive (dead)
       Docs: man:systemd-timesyncd.service(8)

Calling the status does not somehow activate and run the service.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2024-06-08 10:41:01

Lone_Wolf
Forum Moderator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 12,616

Re: [solved] ntpd segfault at boot after upgrade

trilby wrote:

Calling the status does not somehow activate and run the service.

Agreed, but I'm 99% sure timedatectl queries systemd-timesyncd for information .
To answer that request systemd-timesyncd is started on-demand through socket activation .

Maybe Oliver ran timedatectl  ?

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#10 2024-06-08 11:42:50

0liver
Member
Registered: 2014-05-20
Posts: 42

Re: [solved] ntpd segfault at boot after upgrade

Lone_Wolf wrote:

Maybe Oliver ran timedatectl  ?

see my first post; i ran

$ systemctl status systemd-timesyncd

Offline

#11 2024-06-08 11:51:12

seth
Member
Registered: 2012-09-03
Posts: 56,103

Re: [solved] ntpd segfault at boot after upgrade

The service was actually "enabled", there's no socket.

 ◉ systemctl status systemd-timesyncd.socket                    
Unit systemd-timesyncd.socket could not be found.
 ◉ timedatectl status                                                                                    
…
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: no
◉ systemctl status systemd-timesyncd                    
○ systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disabled; preset: enabled)
     Active: inactive (dead)
       Docs: man:systemd-timesyncd.service(8)
◉ pacman -Ql systemd | grep time | grep socket
◉

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB