Speed up boot, timesyncd and resolved
0
My fresh installation of 18.04 is taking 1 to 1.5 minutes to boot, while it took <10 seconds before reinstalling.
~$ systemd-analyze time
Startup finished in 7.942s (firmware) + 11.813s (loader) + 5.323s (kernel) + 41.406s (userspace) = 1min 6.486s
graphical.target reached after 41.308s in userspace
~$ systemd-analyze blame
33.987s systemd-timesyncd.service
33.979s systemd-resolved.service
5.507s NetworkManager-wait-online.service
1.099s dev-sdb2.device
...
But when looking in the logs I see nothing suspicious, except that it's taking 30 seconds...
~$ journalctl -u systemd-timesyncd.service
-- Reboot --
Jan 15 12:27:18 ubuntu systemd[1]: Starting Network Time Synchronization...
Jan 15 12:27:52 ubuntu systemd[1]: Started Network Time Synchronization.
Jan 15 12:28:22 ubuntu systemd-timesyncd[719]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com).
~$ journalctl -u systemd-resolved.service
-- Reboot --
Jan 15 12:27:18 ubuntu systemd[1]: Starting Network Name Resolution...
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Positive Trust Anchors:
Jan 15 12:27:52 ubuntu systemd-resolved[721]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb4
Jan 15 12:27:52 ubuntu systemd-resolved[721]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104227c7f8ec8d
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Using system hostname 'ubuntu'.
Jan 15 12:27:52 ubuntu systemd[1]: Started Network Name Resolution.
Sometimes apparmor.service also takes ~30s which was not the case this time.
How can I speed those up?
EDIT: Changed my dns to 8.8.8.8 and now blame says this
34.420s console-setup.service
34.416s snap-vscode-74.mount
34.381s snap-core-6130.mount
33.962s apparmor.service
33.927s systemd-tmpfiles-setup.service
5.400s NetworkManager-wait-online.service
1.543s dev-sdb2.device
1.092s keyboard-setup.service
...
However after another reboot timesyncd and resolved are still there, it appears the problem is not caused by the services as implied in the title.
boot
asked Jan 15 at 10:44
php_nub_qqphp_nub_qq
4042513
add a comment |
0
My fresh installation of 18.04 is taking 1 to 1.5 minutes to boot, while it took <10 seconds before reinstalling.
~$ systemd-analyze time
Startup finished in 7.942s (firmware) + 11.813s (loader) + 5.323s (kernel) + 41.406s (userspace) = 1min 6.486s
graphical.target reached after 41.308s in userspace
~$ systemd-analyze blame
33.987s systemd-timesyncd.service
33.979s systemd-resolved.service
5.507s NetworkManager-wait-online.service
1.099s dev-sdb2.device
...
But when looking in the logs I see nothing suspicious, except that it's taking 30 seconds...
~$ journalctl -u systemd-timesyncd.service
-- Reboot --
Jan 15 12:27:18 ubuntu systemd[1]: Starting Network Time Synchronization...
Jan 15 12:27:52 ubuntu systemd[1]: Started Network Time Synchronization.
Jan 15 12:28:22 ubuntu systemd-timesyncd[719]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com).
~$ journalctl -u systemd-resolved.service
-- Reboot --
Jan 15 12:27:18 ubuntu systemd[1]: Starting Network Name Resolution...
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Positive Trust Anchors:
Jan 15 12:27:52 ubuntu systemd-resolved[721]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb4
Jan 15 12:27:52 ubuntu systemd-resolved[721]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104227c7f8ec8d
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Using system hostname 'ubuntu'.
Jan 15 12:27:52 ubuntu systemd[1]: Started Network Name Resolution.
Sometimes apparmor.service also takes ~30s which was not the case this time.
How can I speed those up?
EDIT: Changed my dns to 8.8.8.8 and now blame says this
34.420s console-setup.service
34.416s snap-vscode-74.mount
34.381s snap-core-6130.mount
33.962s apparmor.service
33.927s systemd-tmpfiles-setup.service
5.400s NetworkManager-wait-online.service
1.543s dev-sdb2.device
1.092s keyboard-setup.service
...
However after another reboot timesyncd and resolved are still there, it appears the problem is not caused by the services as implied in the title.
boot
asked Jan 15 at 10:44
php_nub_qqphp_nub_qq
4042513
I would guess there is a problem with DNS resolution, which is necessary for the time sync service. Are your DNS servers reachable?
– Jos
Jan 15 at 11:19
@Jos well after the system boots I don't experience any issues, howevernmcli -t -f IP4.DNS device show eth0shows my router address andcat /etc/resolv.confhas127.0.0.53in there, not really sure if that's an issue
– php_nub_qq
Jan 15 at 11:26
@Jos Just changed my dns adresses and still experiencing this but this time with other services, I'll update the question
– php_nub_qq
Jan 15 at 11:36
add a comment |
0
0
0
My fresh installation of 18.04 is taking 1 to 1.5 minutes to boot, while it took <10 seconds before reinstalling.
~$ systemd-analyze time
Startup finished in 7.942s (firmware) + 11.813s (loader) + 5.323s (kernel) + 41.406s (userspace) = 1min 6.486s
graphical.target reached after 41.308s in userspace
~$ systemd-analyze blame
33.987s systemd-timesyncd.service
33.979s systemd-resolved.service
5.507s NetworkManager-wait-online.service
1.099s dev-sdb2.device
...
But when looking in the logs I see nothing suspicious, except that it's taking 30 seconds...
~$ journalctl -u systemd-timesyncd.service
-- Reboot --
Jan 15 12:27:18 ubuntu systemd[1]: Starting Network Time Synchronization...
Jan 15 12:27:52 ubuntu systemd[1]: Started Network Time Synchronization.
Jan 15 12:28:22 ubuntu systemd-timesyncd[719]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com).
~$ journalctl -u systemd-resolved.service
-- Reboot --
Jan 15 12:27:18 ubuntu systemd[1]: Starting Network Name Resolution...
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Positive Trust Anchors:
Jan 15 12:27:52 ubuntu systemd-resolved[721]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb4
Jan 15 12:27:52 ubuntu systemd-resolved[721]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104227c7f8ec8d
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Using system hostname 'ubuntu'.
Jan 15 12:27:52 ubuntu systemd[1]: Started Network Name Resolution.
Sometimes apparmor.service also takes ~30s which was not the case this time.
How can I speed those up?
EDIT: Changed my dns to 8.8.8.8 and now blame says this
34.420s console-setup.service
34.416s snap-vscode-74.mount
34.381s snap-core-6130.mount
33.962s apparmor.service
33.927s systemd-tmpfiles-setup.service
5.400s NetworkManager-wait-online.service
1.543s dev-sdb2.device
1.092s keyboard-setup.service
...
However after another reboot timesyncd and resolved are still there, it appears the problem is not caused by the services as implied in the title.
boot
asked Jan 15 at 10:44
php_nub_qqphp_nub_qq
4042513
My fresh installation of 18.04 is taking 1 to 1.5 minutes to boot, while it took <10 seconds before reinstalling.
~$ systemd-analyze time
Startup finished in 7.942s (firmware) + 11.813s (loader) + 5.323s (kernel) + 41.406s (userspace) = 1min 6.486s
graphical.target reached after 41.308s in userspace
~$ systemd-analyze blame
33.987s systemd-timesyncd.service
33.979s systemd-resolved.service
5.507s NetworkManager-wait-online.service
1.099s dev-sdb2.device
...
But when looking in the logs I see nothing suspicious, except that it's taking 30 seconds...
~$ journalctl -u systemd-timesyncd.service
-- Reboot --
Jan 15 12:27:18 ubuntu systemd[1]: Starting Network Time Synchronization...
Jan 15 12:27:52 ubuntu systemd[1]: Started Network Time Synchronization.
Jan 15 12:28:22 ubuntu systemd-timesyncd[719]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com).
~$ journalctl -u systemd-resolved.service
-- Reboot --
Jan 15 12:27:18 ubuntu systemd[1]: Starting Network Name Resolution...
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Positive Trust Anchors:
Jan 15 12:27:52 ubuntu systemd-resolved[721]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb4
Jan 15 12:27:52 ubuntu systemd-resolved[721]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104227c7f8ec8d
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa
Jan 15 12:27:52 ubuntu systemd-resolved[721]: Using system hostname 'ubuntu'.
Jan 15 12:27:52 ubuntu systemd[1]: Started Network Name Resolution.
Sometimes apparmor.service also takes ~30s which was not the case this time.
How can I speed those up?
EDIT: Changed my dns to 8.8.8.8 and now blame says this
34.420s console-setup.service
34.416s snap-vscode-74.mount
34.381s snap-core-6130.mount
33.962s apparmor.service
33.927s systemd-tmpfiles-setup.service
5.400s NetworkManager-wait-online.service
1.543s dev-sdb2.device
1.092s keyboard-setup.service
...
However after another reboot timesyncd and resolved are still there, it appears the problem is not caused by the services as implied in the title.
boot
boot
asked Jan 15 at 10:44
php_nub_qqphp_nub_qq
4042513
asked Jan 15 at 10:44
php_nub_qqphp_nub_qq
4042513
edited Jan 15 at 11:46
php_nub_qq
asked Jan 15 at 10:44
php_nub_qqphp_nub_qq
4042513
asked Jan 15 at 10:44
php_nub_qqphp_nub_qq
4042513
asked Jan 15 at 10:44
php_nub_qqphp_nub_qq
4042513
4042513
I would guess there is a problem with DNS resolution, which is necessary for the time sync service. Are your DNS servers reachable?
– Jos
Jan 15 at 11:19
@Jos well after the system boots I don't experience any issues, howevernmcli -t -f IP4.DNS device show eth0shows my router address andcat /etc/resolv.confhas127.0.0.53in there, not really sure if that's an issue
– php_nub_qq
Jan 15 at 11:26
@Jos Just changed my dns adresses and still experiencing this but this time with other services, I'll update the question
– php_nub_qq
Jan 15 at 11:36
add a comment |
I would guess there is a problem with DNS resolution, which is necessary for the time sync service. Are your DNS servers reachable?
– Jos
Jan 15 at 11:19
@Jos well after the system boots I don't experience any issues, howevernmcli -t -f IP4.DNS device show eth0shows my router address andcat /etc/resolv.confhas127.0.0.53in there, not really sure if that's an issue
– php_nub_qq
Jan 15 at 11:26
@Jos Just changed my dns adresses and still experiencing this but this time with other services, I'll update the question
– php_nub_qq
Jan 15 at 11:36
I would guess there is a problem with DNS resolution, which is necessary for the time sync service. Are your DNS servers reachable?
– Jos
Jan 15 at 11:19
I would guess there is a problem with DNS resolution, which is necessary for the time sync service. Are your DNS servers reachable?
– Jos
Jan 15 at 11:19
@Jos well after the system boots I don't experience any issues, however
nmcli -t -f IP4.DNS device show eth0 shows my router address and cat /etc/resolv.conf has 127.0.0.53 in there, not really sure if that's an issue– php_nub_qq
Jan 15 at 11:26
@Jos well after the system boots I don't experience any issues, however
nmcli -t -f IP4.DNS device show eth0 shows my router address and cat /etc/resolv.conf has 127.0.0.53 in there, not really sure if that's an issue– php_nub_qq
Jan 15 at 11:26
@Jos Just changed my dns adresses and still experiencing this but this time with other services, I'll update the question
– php_nub_qq
Jan 15 at 11:36
@Jos Just changed my dns adresses and still experiencing this but this time with other services, I'll update the question
– php_nub_qq
Jan 15 at 11:36
add a comment |
0
active
oldest
votes
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
});
}
});
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%2faskubuntu.com%2fquestions%2f1109892%2fspeed-up-boot-timesyncd-and-resolved%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
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%2faskubuntu.com%2fquestions%2f1109892%2fspeed-up-boot-timesyncd-and-resolved%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
I would guess there is a problem with DNS resolution, which is necessary for the time sync service. Are your DNS servers reachable?
– Jos
Jan 15 at 11:19
@Jos well after the system boots I don't experience any issues, however
nmcli -t -f IP4.DNS device show eth0shows my router address andcat /etc/resolv.confhas127.0.0.53in there, not really sure if that's an issue– php_nub_qq
Jan 15 at 11:26
@Jos Just changed my dns adresses and still experiencing this but this time with other services, I'll update the question
– php_nub_qq
Jan 15 at 11:36