ntp.service not getting started on bootup
I am upgrading my system from 14.04 to 16.04, I am facing this issue of ntp.service
not getting started on bootup.
$ sudo systemctl status ntp.service
● ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
Active: active (exited) since Mon 2017-09-11 12:29:11 UTC; 26min ago
Docs: man:systemd-sysv-generator(8)
Tasks: 0
Memory: 0B
CPU: 0
Sep 11 12:29:11 ip-10-1-1-20 systemd[1]: Starting LSB: Start NTP daemon...
Sep 11 12:29:11 ip-10-1-1-20 ntp[1254]: * Starting NTP server ntpd
Sep 11 12:29:11 ip-10-1-1-20 ntp[1254]: ...done.
Sep 11 12:29:11 ip-10-1-1-20 systemd[1]: Started LSB: Start NTP daemon.
Sep 11 12:29:11 ip-10-1-1-20 ntpd[1372]: proto: precision = 0.222 usec (-22)
The contents of the ntp.service
file is being generated by sysv
services if I am not wrong. Content of which is
$ sudo systemctl cat ntp.service
# /run/systemd/generator.late/ntp.service
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/ntp
Description=LSB: Start NTP daemon
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
After=network-online.target
After=remote-fs.target
After=systemd-journald-dev-log.socket
Wants=network-online.target
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=/etc/init.d/ntp start
ExecStop=/etc/init.d/ntp stop
Relevant bug files:
- https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596
- https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1593907
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802040
I asked around in the IRC's and they said, the system generated file from the init service to a systemd service file is sometimes's buggy and asked me to replace it from one of the upstream versions of ntp.service.
Right now, the fix I have been able to come up with is that I have to manually start and stop the ntpd service
$ sudo systemctl stop ntp.service
$ sudo systemctl start ntp.service
But this defeats the purpose of the automatic start of the ntp.service at boot time
Would appreciate any help on this.
16.04 systemd amazon-ec2 init.d ntp
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am upgrading my system from 14.04 to 16.04, I am facing this issue of ntp.service
not getting started on bootup.
$ sudo systemctl status ntp.service
● ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
Active: active (exited) since Mon 2017-09-11 12:29:11 UTC; 26min ago
Docs: man:systemd-sysv-generator(8)
Tasks: 0
Memory: 0B
CPU: 0
Sep 11 12:29:11 ip-10-1-1-20 systemd[1]: Starting LSB: Start NTP daemon...
Sep 11 12:29:11 ip-10-1-1-20 ntp[1254]: * Starting NTP server ntpd
Sep 11 12:29:11 ip-10-1-1-20 ntp[1254]: ...done.
Sep 11 12:29:11 ip-10-1-1-20 systemd[1]: Started LSB: Start NTP daemon.
Sep 11 12:29:11 ip-10-1-1-20 ntpd[1372]: proto: precision = 0.222 usec (-22)
The contents of the ntp.service
file is being generated by sysv
services if I am not wrong. Content of which is
$ sudo systemctl cat ntp.service
# /run/systemd/generator.late/ntp.service
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/ntp
Description=LSB: Start NTP daemon
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
After=network-online.target
After=remote-fs.target
After=systemd-journald-dev-log.socket
Wants=network-online.target
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=/etc/init.d/ntp start
ExecStop=/etc/init.d/ntp stop
Relevant bug files:
- https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596
- https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1593907
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802040
I asked around in the IRC's and they said, the system generated file from the init service to a systemd service file is sometimes's buggy and asked me to replace it from one of the upstream versions of ntp.service.
Right now, the fix I have been able to come up with is that I have to manually start and stop the ntpd service
$ sudo systemctl stop ntp.service
$ sudo systemctl start ntp.service
But this defeats the purpose of the automatic start of the ntp.service at boot time
Would appreciate any help on this.
16.04 systemd amazon-ec2 init.d ntp
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Are you running on a SSD? Once the network is up, don't you find that ntp starts itself properly? Check the syslog to confirm.
– heynnema
Sep 11 '17 at 13:31
I am running on a SSD. This is an ec2 instance, > Check the syslog to confirm. But the status of the service is shown as exited right? Wouldn't it be already down
– Tasdik Rahman
Sep 11 '17 at 14:02
Typically if a service doesn't start properly, but you can start it properly manually, and you're booting from an SSD, it's because the machine boots too fast, and not all services have fully started by the time other services need them. It's a timing issue. It looks like your ntp.service file has the requirednetwork-online.target
that tell it to wait until the network is up. You mightgrep -i ntp /var/log/syslog*
and see if there's any more clues.
– heynnema
Sep 11 '17 at 14:20
add a comment |
I am upgrading my system from 14.04 to 16.04, I am facing this issue of ntp.service
not getting started on bootup.
$ sudo systemctl status ntp.service
● ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
Active: active (exited) since Mon 2017-09-11 12:29:11 UTC; 26min ago
Docs: man:systemd-sysv-generator(8)
Tasks: 0
Memory: 0B
CPU: 0
Sep 11 12:29:11 ip-10-1-1-20 systemd[1]: Starting LSB: Start NTP daemon...
Sep 11 12:29:11 ip-10-1-1-20 ntp[1254]: * Starting NTP server ntpd
Sep 11 12:29:11 ip-10-1-1-20 ntp[1254]: ...done.
Sep 11 12:29:11 ip-10-1-1-20 systemd[1]: Started LSB: Start NTP daemon.
Sep 11 12:29:11 ip-10-1-1-20 ntpd[1372]: proto: precision = 0.222 usec (-22)
The contents of the ntp.service
file is being generated by sysv
services if I am not wrong. Content of which is
$ sudo systemctl cat ntp.service
# /run/systemd/generator.late/ntp.service
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/ntp
Description=LSB: Start NTP daemon
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
After=network-online.target
After=remote-fs.target
After=systemd-journald-dev-log.socket
Wants=network-online.target
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=/etc/init.d/ntp start
ExecStop=/etc/init.d/ntp stop
Relevant bug files:
- https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596
- https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1593907
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802040
I asked around in the IRC's and they said, the system generated file from the init service to a systemd service file is sometimes's buggy and asked me to replace it from one of the upstream versions of ntp.service.
Right now, the fix I have been able to come up with is that I have to manually start and stop the ntpd service
$ sudo systemctl stop ntp.service
$ sudo systemctl start ntp.service
But this defeats the purpose of the automatic start of the ntp.service at boot time
Would appreciate any help on this.
16.04 systemd amazon-ec2 init.d ntp
I am upgrading my system from 14.04 to 16.04, I am facing this issue of ntp.service
not getting started on bootup.
$ sudo systemctl status ntp.service
● ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
Active: active (exited) since Mon 2017-09-11 12:29:11 UTC; 26min ago
Docs: man:systemd-sysv-generator(8)
Tasks: 0
Memory: 0B
CPU: 0
Sep 11 12:29:11 ip-10-1-1-20 systemd[1]: Starting LSB: Start NTP daemon...
Sep 11 12:29:11 ip-10-1-1-20 ntp[1254]: * Starting NTP server ntpd
Sep 11 12:29:11 ip-10-1-1-20 ntp[1254]: ...done.
Sep 11 12:29:11 ip-10-1-1-20 systemd[1]: Started LSB: Start NTP daemon.
Sep 11 12:29:11 ip-10-1-1-20 ntpd[1372]: proto: precision = 0.222 usec (-22)
The contents of the ntp.service
file is being generated by sysv
services if I am not wrong. Content of which is
$ sudo systemctl cat ntp.service
# /run/systemd/generator.late/ntp.service
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/ntp
Description=LSB: Start NTP daemon
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
After=network-online.target
After=remote-fs.target
After=systemd-journald-dev-log.socket
Wants=network-online.target
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=/etc/init.d/ntp start
ExecStop=/etc/init.d/ntp stop
Relevant bug files:
- https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596
- https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1593907
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802040
I asked around in the IRC's and they said, the system generated file from the init service to a systemd service file is sometimes's buggy and asked me to replace it from one of the upstream versions of ntp.service.
Right now, the fix I have been able to come up with is that I have to manually start and stop the ntpd service
$ sudo systemctl stop ntp.service
$ sudo systemctl start ntp.service
But this defeats the purpose of the automatic start of the ntp.service at boot time
Would appreciate any help on this.
16.04 systemd amazon-ec2 init.d ntp
16.04 systemd amazon-ec2 init.d ntp
edited Sep 11 '17 at 13:56
Tasdik Rahman
asked Sep 11 '17 at 13:01
Tasdik RahmanTasdik Rahman
2571921
2571921
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Are you running on a SSD? Once the network is up, don't you find that ntp starts itself properly? Check the syslog to confirm.
– heynnema
Sep 11 '17 at 13:31
I am running on a SSD. This is an ec2 instance, > Check the syslog to confirm. But the status of the service is shown as exited right? Wouldn't it be already down
– Tasdik Rahman
Sep 11 '17 at 14:02
Typically if a service doesn't start properly, but you can start it properly manually, and you're booting from an SSD, it's because the machine boots too fast, and not all services have fully started by the time other services need them. It's a timing issue. It looks like your ntp.service file has the requirednetwork-online.target
that tell it to wait until the network is up. You mightgrep -i ntp /var/log/syslog*
and see if there's any more clues.
– heynnema
Sep 11 '17 at 14:20
add a comment |
Are you running on a SSD? Once the network is up, don't you find that ntp starts itself properly? Check the syslog to confirm.
– heynnema
Sep 11 '17 at 13:31
I am running on a SSD. This is an ec2 instance, > Check the syslog to confirm. But the status of the service is shown as exited right? Wouldn't it be already down
– Tasdik Rahman
Sep 11 '17 at 14:02
Typically if a service doesn't start properly, but you can start it properly manually, and you're booting from an SSD, it's because the machine boots too fast, and not all services have fully started by the time other services need them. It's a timing issue. It looks like your ntp.service file has the requirednetwork-online.target
that tell it to wait until the network is up. You mightgrep -i ntp /var/log/syslog*
and see if there's any more clues.
– heynnema
Sep 11 '17 at 14:20
Are you running on a SSD? Once the network is up, don't you find that ntp starts itself properly? Check the syslog to confirm.
– heynnema
Sep 11 '17 at 13:31
Are you running on a SSD? Once the network is up, don't you find that ntp starts itself properly? Check the syslog to confirm.
– heynnema
Sep 11 '17 at 13:31
I am running on a SSD. This is an ec2 instance, > Check the syslog to confirm. But the status of the service is shown as exited right? Wouldn't it be already down
– Tasdik Rahman
Sep 11 '17 at 14:02
I am running on a SSD. This is an ec2 instance, > Check the syslog to confirm. But the status of the service is shown as exited right? Wouldn't it be already down
– Tasdik Rahman
Sep 11 '17 at 14:02
Typically if a service doesn't start properly, but you can start it properly manually, and you're booting from an SSD, it's because the machine boots too fast, and not all services have fully started by the time other services need them. It's a timing issue. It looks like your ntp.service file has the required
network-online.target
that tell it to wait until the network is up. You might grep -i ntp /var/log/syslog*
and see if there's any more clues.– heynnema
Sep 11 '17 at 14:20
Typically if a service doesn't start properly, but you can start it properly manually, and you're booting from an SSD, it's because the machine boots too fast, and not all services have fully started by the time other services need them. It's a timing issue. It looks like your ntp.service file has the required
network-online.target
that tell it to wait until the network is up. You might grep -i ntp /var/log/syslog*
and see if there's any more clues.– heynnema
Sep 11 '17 at 14:20
add a comment |
2 Answers
2
active
oldest
votes
There are more than some ways to fix this issue documented here https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596
sed -i -- 's/NTPOPTIONS=""/NTPOPTIONS="-u"/g' /etc/default/ntpdate
Replace the content of
/etc/network/if-up.d/ntpdate
with https://launchpadlibrarian.net/295277086/ntpdate_HH
After you do any of the above,
$ systemctl stop ntp.service
$ systemctl start ntp.service
ntp.service
should be up now
add a comment |
As of Ubuntu 16.04, the ntp service has been replaced by a native systemd service named systemd-timesyncd (or prefer-timesyncd) and it is running by default.
If you just want an NTP-synced clock, leave ntp.service disabled and use timedatectl status
to check status:
lar@rv-server:~$ timedatectl status
Local time: Fri 2018-11-09 14:16:52 PST
Universal time: Fri 2018-11-09 22:16:52 UTC
RTC time: n/a
Time zone: America/Los_Angeles (PST, -0800)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
If NTP is not synchronized, use sudo timedatectl set-ntp on
to turn it on.
For an NTP server (not just client), you will either need to replace timedatectl with ntpd or install chrony (recommended).
Read more here: https://help.ubuntu.com/lts/serverguide/NTP.html
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f954768%2fntp-service-not-getting-started-on-bootup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are more than some ways to fix this issue documented here https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596
sed -i -- 's/NTPOPTIONS=""/NTPOPTIONS="-u"/g' /etc/default/ntpdate
Replace the content of
/etc/network/if-up.d/ntpdate
with https://launchpadlibrarian.net/295277086/ntpdate_HH
After you do any of the above,
$ systemctl stop ntp.service
$ systemctl start ntp.service
ntp.service
should be up now
add a comment |
There are more than some ways to fix this issue documented here https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596
sed -i -- 's/NTPOPTIONS=""/NTPOPTIONS="-u"/g' /etc/default/ntpdate
Replace the content of
/etc/network/if-up.d/ntpdate
with https://launchpadlibrarian.net/295277086/ntpdate_HH
After you do any of the above,
$ systemctl stop ntp.service
$ systemctl start ntp.service
ntp.service
should be up now
add a comment |
There are more than some ways to fix this issue documented here https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596
sed -i -- 's/NTPOPTIONS=""/NTPOPTIONS="-u"/g' /etc/default/ntpdate
Replace the content of
/etc/network/if-up.d/ntpdate
with https://launchpadlibrarian.net/295277086/ntpdate_HH
After you do any of the above,
$ systemctl stop ntp.service
$ systemctl start ntp.service
ntp.service
should be up now
There are more than some ways to fix this issue documented here https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596
sed -i -- 's/NTPOPTIONS=""/NTPOPTIONS="-u"/g' /etc/default/ntpdate
Replace the content of
/etc/network/if-up.d/ntpdate
with https://launchpadlibrarian.net/295277086/ntpdate_HH
After you do any of the above,
$ systemctl stop ntp.service
$ systemctl start ntp.service
ntp.service
should be up now
answered Sep 11 '17 at 20:10
Tasdik RahmanTasdik Rahman
2571921
2571921
add a comment |
add a comment |
As of Ubuntu 16.04, the ntp service has been replaced by a native systemd service named systemd-timesyncd (or prefer-timesyncd) and it is running by default.
If you just want an NTP-synced clock, leave ntp.service disabled and use timedatectl status
to check status:
lar@rv-server:~$ timedatectl status
Local time: Fri 2018-11-09 14:16:52 PST
Universal time: Fri 2018-11-09 22:16:52 UTC
RTC time: n/a
Time zone: America/Los_Angeles (PST, -0800)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
If NTP is not synchronized, use sudo timedatectl set-ntp on
to turn it on.
For an NTP server (not just client), you will either need to replace timedatectl with ntpd or install chrony (recommended).
Read more here: https://help.ubuntu.com/lts/serverguide/NTP.html
add a comment |
As of Ubuntu 16.04, the ntp service has been replaced by a native systemd service named systemd-timesyncd (or prefer-timesyncd) and it is running by default.
If you just want an NTP-synced clock, leave ntp.service disabled and use timedatectl status
to check status:
lar@rv-server:~$ timedatectl status
Local time: Fri 2018-11-09 14:16:52 PST
Universal time: Fri 2018-11-09 22:16:52 UTC
RTC time: n/a
Time zone: America/Los_Angeles (PST, -0800)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
If NTP is not synchronized, use sudo timedatectl set-ntp on
to turn it on.
For an NTP server (not just client), you will either need to replace timedatectl with ntpd or install chrony (recommended).
Read more here: https://help.ubuntu.com/lts/serverguide/NTP.html
add a comment |
As of Ubuntu 16.04, the ntp service has been replaced by a native systemd service named systemd-timesyncd (or prefer-timesyncd) and it is running by default.
If you just want an NTP-synced clock, leave ntp.service disabled and use timedatectl status
to check status:
lar@rv-server:~$ timedatectl status
Local time: Fri 2018-11-09 14:16:52 PST
Universal time: Fri 2018-11-09 22:16:52 UTC
RTC time: n/a
Time zone: America/Los_Angeles (PST, -0800)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
If NTP is not synchronized, use sudo timedatectl set-ntp on
to turn it on.
For an NTP server (not just client), you will either need to replace timedatectl with ntpd or install chrony (recommended).
Read more here: https://help.ubuntu.com/lts/serverguide/NTP.html
As of Ubuntu 16.04, the ntp service has been replaced by a native systemd service named systemd-timesyncd (or prefer-timesyncd) and it is running by default.
If you just want an NTP-synced clock, leave ntp.service disabled and use timedatectl status
to check status:
lar@rv-server:~$ timedatectl status
Local time: Fri 2018-11-09 14:16:52 PST
Universal time: Fri 2018-11-09 22:16:52 UTC
RTC time: n/a
Time zone: America/Los_Angeles (PST, -0800)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
If NTP is not synchronized, use sudo timedatectl set-ntp on
to turn it on.
For an NTP server (not just client), you will either need to replace timedatectl with ntpd or install chrony (recommended).
Read more here: https://help.ubuntu.com/lts/serverguide/NTP.html
answered Nov 9 '18 at 23:14
patricktokeeffepatricktokeeffe
1114
1114
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f954768%2fntp-service-not-getting-started-on-bootup%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are you running on a SSD? Once the network is up, don't you find that ntp starts itself properly? Check the syslog to confirm.
– heynnema
Sep 11 '17 at 13:31
I am running on a SSD. This is an ec2 instance, > Check the syslog to confirm. But the status of the service is shown as exited right? Wouldn't it be already down
– Tasdik Rahman
Sep 11 '17 at 14:02
Typically if a service doesn't start properly, but you can start it properly manually, and you're booting from an SSD, it's because the machine boots too fast, and not all services have fully started by the time other services need them. It's a timing issue. It looks like your ntp.service file has the required
network-online.target
that tell it to wait until the network is up. You mightgrep -i ntp /var/log/syslog*
and see if there's any more clues.– heynnema
Sep 11 '17 at 14:20