# ntpd will not start on reboot

**URL:** <https://forums.suse.com/t/ntpd-will-not-start-on-reboot/33796>\
**Category:** SLES Configure-Administer\
**Created:** [April 9, 2019, 4:14pm UTC](https://forums.suse.com/t/ntpd-will-not-start-on-reboot/33796 "2019-04-09T16:14:06Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![cisaksen](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@cisaksen](https://forums.suse.com/u/cisaksen)\
**Post date:** [April 9, 2019, 4:14pm UTC](https://forums.suse.com/t/ntpd-will-not-start-on-reboot/33796/1 "2019-04-09T16:14:06Z")

</div>

Recently configured ntpd on SUSE 15 server (physical) and it is set to enabled but it doesn’t start on a reboot.

I see in messages that the NTP client\server started successfully but I believe that’s the YAST client version of ntp. I see no signs that the actual ntpd.service file is ever tried to start.

Any ideas on how I might get a closer look at the boot up process ? It there is an ntp.log file I set in ntp.conf but I’m not sure the proper syntax to set the logging to debug.

Thanks

---

<div class="post-metadata">

**Author:** ![Andreas1](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@Andreas1](https://forums.suse.com/u/Andreas1)\
**Post date:** [April 9, 2019, 9:16pm UTC](https://forums.suse.com/t/ntpd-will-not-start-on-reboot/33796/2 "2019-04-09T21:16:27Z")

</div>

Please read SLE Administration Guide, chaptre “13.2”:

[https://www.suse.com/documentation/](https://www.suse.com/documentation/)

[https://www.suse.com/documentation/sles-15/book\_sle\_admin/data/sec\_boot\_systemd\_basics.html](https://www.suse.com/documentation/sles-15/book_sle_admin/data/sec_boot_systemd_basics.html)

Hint: MY\_SERVICE =\> ntpd.service

---

<div class="post-metadata">

**Author:** ![cisaksen](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@cisaksen](https://forums.suse.com/u/cisaksen)\
**Post date:** [April 9, 2019, 11:02pm UTC](https://forums.suse.com/t/ntpd-will-not-start-on-reboot/33796/3 "2019-04-09T23:02:36Z")

</div>

What exactly are you referring to by this ? The service is enabled - systemctl enable ntpd or systemctl is-enabled ntpd = enabled The service starts just fine manually - systemctl start ntpd

What I saying is that there is no indication that the service is even trying to start during the boot process. There are no log message anywhere that I can find that even shows the ntpd is even attempted to be started or even started and failed.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [April 10, 2019, 12:12am UTC](https://forums.suse.com/t/ntpd-will-not-start-on-reboot/33796/4 "2019-04-10T00:12:59Z")

</div>

A few things may give you clues:

```auto
systemctl status ntpd
```

That should tell you anything about the service that is current, including  
when it last ran.

```auto
systemctl is-active ntpd
```

Indicates whether or not the service is currently active.

```auto
systemd-analyze blame
```

Look through the output looking for your service. The idea with this  
command is to show what caused the startup to take as long as it did (so  
you can optimize that), but as a result it shows all of the starting  
services, in order, which may be useful.

Along with all of that it may be useful to know how you are testing  
whether or not the service is running, just in case your test is invalid.

Finally, "Yast’ doesn’t have an NTP client or service of its own; it  
configures the system one. I only mention this in case you feel Yast is  
somehow doing something other than setting things up, or if you believe  
its tool is a separate one; it’s not.

–  
Good luck.

If you find this post helpful and are logged into the web interface,  
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the  
forum as I do not use the web interface often.

---

<div class="post-metadata">

**Author:** ![cisaksen](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@cisaksen](https://forums.suse.com/u/cisaksen)\
**Post date:** [April 10, 2019, 12:44am UTC](https://forums.suse.com/t/ntpd-will-not-start-on-reboot/33796/5 "2019-04-10T00:44:22Z")

</div>

After a reboot  
systemctl status ntpd  
ntpd.service - NTP Server Daemon  
Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled)  
Active: inactive (dead)  
Docs: man:ntpd(1)

systemd-analyze blame  
ntpd.service is not listed

yet  
systemctl is-enabled ntpd  
enabled

Something is amiss - I’m opening a case.

Thanks

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [April 10, 2019, 2:58am UTC](https://forums.suse.com/t/ntpd-will-not-start-on-reboot/33796/6 "2019-04-10T02:58:14Z")

</div>

> [@](#):
>
> On Tue 09 Apr 2019 09:54:02 PM CDT, cisaksen wrote:
> 
> After a reboot  
> systemctl status ntpd  
> ntpd.service - NTP Server Daemon  
> Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor  
> preset: disabled)  
> Active: inactive (dead)  
> Docs: man:ntpd(1)
> 
> systemd-analyze blame  
> ntpd.service is not listed
> 
> yet  
> systemctl is-enabled ntpd  
> enabled
> 
> Something is amiss - I’m opening a case.
> 
> Thanks

Hi  
Not at all, it’s using chronyd these days…

[https://www.suse.com/releasenotes/x86\_64/SUSE-SLES/15/](https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/)

Section 9.1.7 ntpd Has Been Replaced With Chrony

–  
Cheers Malcolm Â°Â¿Â° SUSE Knowledge Partner (Linux Counter #276890)  
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-150.14-default  
If you find this post helpful and are logged into the web interface,  
please show your appreciation and click on the star below… Thanks!

---

<div class="post-metadata">

**Author:** ![cisaksen](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@cisaksen](https://forums.suse.com/u/cisaksen)\
**Post date:** [April 10, 2019, 6:47pm UTC](https://forums.suse.com/t/ntpd-will-not-start-on-reboot/33796/7 "2019-04-10T18:47:57Z")

</div>

Support confirmed that chrony was conflicting with the ntpd service. Once I disabled chronyd service ntpd start just fine now.

---

<div class="post-metadata">

**Author:** ![Andreas1](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@Andreas1](https://forums.suse.com/u/Andreas1)\
**Post date:** [April 10, 2019, 8:18pm UTC](https://forums.suse.com/t/ntpd-will-not-start-on-reboot/33796/8 "2019-04-10T20:18:44Z")

</div>

You should replace ntpd with chrony if possible.  
[https://chrony.tuxfamily.org/faq.html](https://chrony.tuxfamily.org/faq.html)
