Failed to activate systemd-timesyncd.service
3
I've scanned all forums and questions and found no working answer to my problem.
The Network Time Synchronization service doesn't work. The timedatectl service seems to work just fine without it though but it shows that the systemd-timesyncd is not active
torof@OMEN:~$ timedatectl status
Local time: Fri 2019-02-08 15:12:47 CET
Universal time: Fri 2019-02-08 14:12:47 UTC
RTC time: Fri 2019-02-08 14:12:47
Time zone: Europe/Paris (CET, +0100)
System clock synchronized: yes
systemd-timesyncd.service active: no
RTC in local TZ: no
The libnss-systemd is already installed.
I have checked the syslog but couldn't figure out the problem, enabled and restarted service to no avail.
torof@OMEN:~$ systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-02-08 13:57:04 CET; 13min ago
Docs: man:systemd-timesyncd.service(8)
Process: 4383 ExecStart=/lib/systemd/systemd-timesyncd (code=exited, status=238/STATE_DIRECTORY)
Main PID: 4383 (code=exited, status=238/STATE_DIRECTORY)
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=238/STATE_DIRECTORY
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Feb 08 13:57:04 OMEN systemd[1]: Failed to start Network Time Synchronization.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Feb 08 13:57:04 OMEN systemd[1]: Stopped Network Time Synchronization.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Feb 08 13:57:04 OMEN systemd[1]: Failed to start Network Time Synchronization.
What is going wrong, where to find the problem and how to solve it ?
systemd directory ntp exit-status
edited Feb 8 at 14:27
Jeff Schaller♦
44.5k1162143
asked Feb 8 at 14:12
TorofTorof
255
add a comment |
3
I've scanned all forums and questions and found no working answer to my problem.
The Network Time Synchronization service doesn't work. The timedatectl service seems to work just fine without it though but it shows that the systemd-timesyncd is not active
torof@OMEN:~$ timedatectl status
Local time: Fri 2019-02-08 15:12:47 CET
Universal time: Fri 2019-02-08 14:12:47 UTC
RTC time: Fri 2019-02-08 14:12:47
Time zone: Europe/Paris (CET, +0100)
System clock synchronized: yes
systemd-timesyncd.service active: no
RTC in local TZ: no
The libnss-systemd is already installed.
I have checked the syslog but couldn't figure out the problem, enabled and restarted service to no avail.
torof@OMEN:~$ systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-02-08 13:57:04 CET; 13min ago
Docs: man:systemd-timesyncd.service(8)
Process: 4383 ExecStart=/lib/systemd/systemd-timesyncd (code=exited, status=238/STATE_DIRECTORY)
Main PID: 4383 (code=exited, status=238/STATE_DIRECTORY)
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=238/STATE_DIRECTORY
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Feb 08 13:57:04 OMEN systemd[1]: Failed to start Network Time Synchronization.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Feb 08 13:57:04 OMEN systemd[1]: Stopped Network Time Synchronization.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Feb 08 13:57:04 OMEN systemd[1]: Failed to start Network Time Synchronization.
What is going wrong, where to find the problem and how to solve it ?
systemd directory ntp exit-status
edited Feb 8 at 14:27
Jeff Schaller♦
44.5k1162143
asked Feb 8 at 14:12
TorofTorof
255
add a comment |
3
3
3
0
I've scanned all forums and questions and found no working answer to my problem.
The Network Time Synchronization service doesn't work. The timedatectl service seems to work just fine without it though but it shows that the systemd-timesyncd is not active
torof@OMEN:~$ timedatectl status
Local time: Fri 2019-02-08 15:12:47 CET
Universal time: Fri 2019-02-08 14:12:47 UTC
RTC time: Fri 2019-02-08 14:12:47
Time zone: Europe/Paris (CET, +0100)
System clock synchronized: yes
systemd-timesyncd.service active: no
RTC in local TZ: no
The libnss-systemd is already installed.
I have checked the syslog but couldn't figure out the problem, enabled and restarted service to no avail.
torof@OMEN:~$ systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-02-08 13:57:04 CET; 13min ago
Docs: man:systemd-timesyncd.service(8)
Process: 4383 ExecStart=/lib/systemd/systemd-timesyncd (code=exited, status=238/STATE_DIRECTORY)
Main PID: 4383 (code=exited, status=238/STATE_DIRECTORY)
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=238/STATE_DIRECTORY
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Feb 08 13:57:04 OMEN systemd[1]: Failed to start Network Time Synchronization.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Feb 08 13:57:04 OMEN systemd[1]: Stopped Network Time Synchronization.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Feb 08 13:57:04 OMEN systemd[1]: Failed to start Network Time Synchronization.
What is going wrong, where to find the problem and how to solve it ?
systemd directory ntp exit-status
edited Feb 8 at 14:27
Jeff Schaller♦
44.5k1162143
asked Feb 8 at 14:12
TorofTorof
255
I've scanned all forums and questions and found no working answer to my problem.
The Network Time Synchronization service doesn't work. The timedatectl service seems to work just fine without it though but it shows that the systemd-timesyncd is not active
torof@OMEN:~$ timedatectl status
Local time: Fri 2019-02-08 15:12:47 CET
Universal time: Fri 2019-02-08 14:12:47 UTC
RTC time: Fri 2019-02-08 14:12:47
Time zone: Europe/Paris (CET, +0100)
System clock synchronized: yes
systemd-timesyncd.service active: no
RTC in local TZ: no
The libnss-systemd is already installed.
I have checked the syslog but couldn't figure out the problem, enabled and restarted service to no avail.
torof@OMEN:~$ systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-02-08 13:57:04 CET; 13min ago
Docs: man:systemd-timesyncd.service(8)
Process: 4383 ExecStart=/lib/systemd/systemd-timesyncd (code=exited, status=238/STATE_DIRECTORY)
Main PID: 4383 (code=exited, status=238/STATE_DIRECTORY)
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=238/STATE_DIRECTORY
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Feb 08 13:57:04 OMEN systemd[1]: Failed to start Network Time Synchronization.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Feb 08 13:57:04 OMEN systemd[1]: Stopped Network Time Synchronization.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Feb 08 13:57:04 OMEN systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Feb 08 13:57:04 OMEN systemd[1]: Failed to start Network Time Synchronization.
What is going wrong, where to find the problem and how to solve it ?
systemd directory ntp exit-status
systemd directory ntp exit-status
edited Feb 8 at 14:27
Jeff Schaller♦
44.5k1162143
asked Feb 8 at 14:12
TorofTorof
255
edited Feb 8 at 14:27
Jeff Schaller♦
44.5k1162143
asked Feb 8 at 14:12
TorofTorof
255
edited Feb 8 at 14:27
Jeff Schaller♦
44.5k1162143
edited Feb 8 at 14:27
Jeff Schaller♦
44.5k1162143
edited Feb 8 at 14:27
Jeff Schaller♦
44.5k1162143
44.5k1162143
asked Feb 8 at 14:12
TorofTorof
255
asked Feb 8 at 14:12
TorofTorof
255
asked Feb 8 at 14:12
TorofTorof
255
255
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
5
This systemd Github issue lists a comment with a workaround:
chmod 0700 /var/lib/private
answered Feb 8 at 14:58
Jeff Schaller♦Jeff Schaller
44.5k1162143
That was it, but even reading the github issue I don't understand what was happening, do you ? If yes could you help me to ? Thanks a lot anyway!
– Torof
Feb 8 at 15:13
1
It looks like the fix was merged into systemd, so I'd expect distributions to pick up the fix eventually. Looks to me like it was a bug in error-checking of the directory-making functions, but I haven't traced my way all the way through it.
– Jeff Schaller♦
Feb 8 at 15:17
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
draft saved
draft discarded
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%2funix.stackexchange.com%2fquestions%2f499482%2ffailed-to-activate-systemd-timesyncd-service%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
5
This systemd Github issue lists a comment with a workaround:
chmod 0700 /var/lib/private
answered Feb 8 at 14:58
Jeff Schaller♦Jeff Schaller
44.5k1162143
That was it, but even reading the github issue I don't understand what was happening, do you ? If yes could you help me to ? Thanks a lot anyway!
– Torof
Feb 8 at 15:13
1
It looks like the fix was merged into systemd, so I'd expect distributions to pick up the fix eventually. Looks to me like it was a bug in error-checking of the directory-making functions, but I haven't traced my way all the way through it.
– Jeff Schaller♦
Feb 8 at 15:17
add a comment |
5
This systemd Github issue lists a comment with a workaround:
chmod 0700 /var/lib/private
answered Feb 8 at 14:58
Jeff Schaller♦Jeff Schaller
44.5k1162143
That was it, but even reading the github issue I don't understand what was happening, do you ? If yes could you help me to ? Thanks a lot anyway!
– Torof
Feb 8 at 15:13
1
It looks like the fix was merged into systemd, so I'd expect distributions to pick up the fix eventually. Looks to me like it was a bug in error-checking of the directory-making functions, but I haven't traced my way all the way through it.
– Jeff Schaller♦
Feb 8 at 15:17
add a comment |
5
5
5
This systemd Github issue lists a comment with a workaround:
chmod 0700 /var/lib/private
answered Feb 8 at 14:58
Jeff Schaller♦Jeff Schaller
44.5k1162143
This systemd Github issue lists a comment with a workaround:
chmod 0700 /var/lib/private
answered Feb 8 at 14:58
Jeff Schaller♦Jeff Schaller
44.5k1162143
answered Feb 8 at 14:58
Jeff Schaller♦Jeff Schaller
44.5k1162143
answered Feb 8 at 14:58
Jeff Schaller♦Jeff Schaller
44.5k1162143
answered Feb 8 at 14:58
Jeff Schaller♦Jeff Schaller
44.5k1162143
44.5k1162143
That was it, but even reading the github issue I don't understand what was happening, do you ? If yes could you help me to ? Thanks a lot anyway!
– Torof
Feb 8 at 15:13
1
It looks like the fix was merged into systemd, so I'd expect distributions to pick up the fix eventually. Looks to me like it was a bug in error-checking of the directory-making functions, but I haven't traced my way all the way through it.
– Jeff Schaller♦
Feb 8 at 15:17
add a comment |
That was it, but even reading the github issue I don't understand what was happening, do you ? If yes could you help me to ? Thanks a lot anyway!
– Torof
Feb 8 at 15:13
1
It looks like the fix was merged into systemd, so I'd expect distributions to pick up the fix eventually. Looks to me like it was a bug in error-checking of the directory-making functions, but I haven't traced my way all the way through it.
– Jeff Schaller♦
Feb 8 at 15:17
That was it, but even reading the github issue I don't understand what was happening, do you ? If yes could you help me to ? Thanks a lot anyway!
– Torof
Feb 8 at 15:13
That was it, but even reading the github issue I don't understand what was happening, do you ? If yes could you help me to ? Thanks a lot anyway!
– Torof
Feb 8 at 15:13
1
1
It looks like the fix was merged into systemd, so I'd expect distributions to pick up the fix eventually. Looks to me like it was a bug in error-checking of the directory-making functions, but I haven't traced my way all the way through it.
– Jeff Schaller♦
Feb 8 at 15:17
It looks like the fix was merged into systemd, so I'd expect distributions to pick up the fix eventually. Looks to me like it was a bug in error-checking of the directory-making functions, but I haven't traced my way all the way through it.
– Jeff Schaller♦
Feb 8 at 15:17
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
draft saved
draft discarded
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%2funix.stackexchange.com%2fquestions%2f499482%2ffailed-to-activate-systemd-timesyncd-service%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
