Ubuntu 18.10 - Unattended-upgrades-shutdown --wait-for-signal
up vote
1
down vote
favorite
I have a process as listed in htop under Command stating the following:
/usr/bin/python3
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
--wait-for-signal
Judging by the:
--wait-for-signal
and some researching about what unattended-upgrades is, it makes me think there's something else that needs to be updated so i tried shutting down the server a couple of times, running:
sudo unattended-upgrade
and following these steps but it's still there even though the system is up-to-date.
Is it just there to check for when there's another upgrade to be done?
Should i worry about it or just leave it be?
Thanks in advance.
server upgrade shutdown 18.10 unattended-upgrades
asked Dec 5 at 20:33
Marco Rivas
84
add a comment |
up vote
1
down vote
favorite
I have a process as listed in htop under Command stating the following:
/usr/bin/python3
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
--wait-for-signal
Judging by the:
--wait-for-signal
and some researching about what unattended-upgrades is, it makes me think there's something else that needs to be updated so i tried shutting down the server a couple of times, running:
sudo unattended-upgrade
and following these steps but it's still there even though the system is up-to-date.
Is it just there to check for when there's another upgrade to be done?
Should i worry about it or just leave it be?
Thanks in advance.
server upgrade shutdown 18.10 unattended-upgrades
asked Dec 5 at 20:33
Marco Rivas
84
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a process as listed in htop under Command stating the following:
/usr/bin/python3
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
--wait-for-signal
Judging by the:
--wait-for-signal
and some researching about what unattended-upgrades is, it makes me think there's something else that needs to be updated so i tried shutting down the server a couple of times, running:
sudo unattended-upgrade
and following these steps but it's still there even though the system is up-to-date.
Is it just there to check for when there's another upgrade to be done?
Should i worry about it or just leave it be?
Thanks in advance.
server upgrade shutdown 18.10 unattended-upgrades
asked Dec 5 at 20:33
Marco Rivas
84
I have a process as listed in htop under Command stating the following:
/usr/bin/python3
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
--wait-for-signal
Judging by the:
--wait-for-signal
and some researching about what unattended-upgrades is, it makes me think there's something else that needs to be updated so i tried shutting down the server a couple of times, running:
sudo unattended-upgrade
and following these steps but it's still there even though the system is up-to-date.
Is it just there to check for when there's another upgrade to be done?
Should i worry about it or just leave it be?
Thanks in advance.
server upgrade shutdown 18.10 unattended-upgrades
server upgrade shutdown 18.10 unattended-upgrades
asked Dec 5 at 20:33
Marco Rivas
84
asked Dec 5 at 20:33
Marco Rivas
84
edited Dec 5 at 20:41
asked Dec 5 at 20:33
Marco Rivas
84
asked Dec 5 at 20:33
Marco Rivas
84
asked Dec 5 at 20:33
Marco Rivas
84
84
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
accepted
It's a safety feature. Leave it alone.
Apt data (packages and metadata) can be corrupted if apt happens to be running when the system halts (shuts down). The unattended-updates-shutdown script temporarily inhibits a shutdown signal until apt finishes.
The script cannot prevent corruption due to a sudden power loss, or holding the power button, while apt happens to be running. Another reason to avoid those, and to keep regular backups.
The script is in Python, including the developer's comments. Feel free to read it and see for yourself.
answered Dec 5 at 20:59
user535733
7,53222941
add a comment |
up vote
1
down vote
I ran into this same issue recently as well, while checking for unattended-upgrades running in the background during my image baking process. Basically, I would wait for apt locks to be released, then proceed with my updates.
I used to run this:
while pgrep unattended; do sleep 10; done;
before executing any of my scripts as they would randomly fail at some odd intervals with unattended-upgrades running while me trying to do apt install/upgrade/update with a dpkg lock error.
So I asked for the right way to check for unattended upgrades working in the background and TJ- from IRC gave me a really elegant solution! Disable the u-u service whilst bootstrap scripts are busy. As in:
systemctl mask unattended-upgrades.service
systemctl stop unattended-upgrades.service
then re-enable after you finish your bake:
systemctl unmask unattended-upgrades.service
systemctl start unattended-upgrades.service
In addition, you can run this to make sure you don't kick off your process prematurely:
while systemctl is-active --quiet unattended-upgrades.service; do sleep 1; done
Probably not what you were looking for but this was extremely helpful for me. This might be related to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1803137
answered Dec 7 at 19:27
jvasallo
111
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',
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%2f1098757%2fubuntu-18-10-unattended-upgrades-shutdown-wait-for-signal%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
up vote
0
down vote
accepted
It's a safety feature. Leave it alone.
Apt data (packages and metadata) can be corrupted if apt happens to be running when the system halts (shuts down). The unattended-updates-shutdown script temporarily inhibits a shutdown signal until apt finishes.
The script cannot prevent corruption due to a sudden power loss, or holding the power button, while apt happens to be running. Another reason to avoid those, and to keep regular backups.
The script is in Python, including the developer's comments. Feel free to read it and see for yourself.
answered Dec 5 at 20:59
user535733
7,53222941
add a comment |
up vote
0
down vote
accepted
It's a safety feature. Leave it alone.
Apt data (packages and metadata) can be corrupted if apt happens to be running when the system halts (shuts down). The unattended-updates-shutdown script temporarily inhibits a shutdown signal until apt finishes.
The script cannot prevent corruption due to a sudden power loss, or holding the power button, while apt happens to be running. Another reason to avoid those, and to keep regular backups.
The script is in Python, including the developer's comments. Feel free to read it and see for yourself.
answered Dec 5 at 20:59
user535733
7,53222941
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
It's a safety feature. Leave it alone.
Apt data (packages and metadata) can be corrupted if apt happens to be running when the system halts (shuts down). The unattended-updates-shutdown script temporarily inhibits a shutdown signal until apt finishes.
The script cannot prevent corruption due to a sudden power loss, or holding the power button, while apt happens to be running. Another reason to avoid those, and to keep regular backups.
The script is in Python, including the developer's comments. Feel free to read it and see for yourself.
answered Dec 5 at 20:59
user535733
7,53222941
It's a safety feature. Leave it alone.
Apt data (packages and metadata) can be corrupted if apt happens to be running when the system halts (shuts down). The unattended-updates-shutdown script temporarily inhibits a shutdown signal until apt finishes.
The script cannot prevent corruption due to a sudden power loss, or holding the power button, while apt happens to be running. Another reason to avoid those, and to keep regular backups.
The script is in Python, including the developer's comments. Feel free to read it and see for yourself.
answered Dec 5 at 20:59
user535733
7,53222941
edited Dec 5 at 21:05
answered Dec 5 at 20:59
user535733
7,53222941
answered Dec 5 at 20:59
user535733
7,53222941
answered Dec 5 at 20:59
user535733
7,53222941
7,53222941
add a comment |
add a comment |
up vote
1
down vote
I ran into this same issue recently as well, while checking for unattended-upgrades running in the background during my image baking process. Basically, I would wait for apt locks to be released, then proceed with my updates.
I used to run this:
while pgrep unattended; do sleep 10; done;
before executing any of my scripts as they would randomly fail at some odd intervals with unattended-upgrades running while me trying to do apt install/upgrade/update with a dpkg lock error.
So I asked for the right way to check for unattended upgrades working in the background and TJ- from IRC gave me a really elegant solution! Disable the u-u service whilst bootstrap scripts are busy. As in:
systemctl mask unattended-upgrades.service
systemctl stop unattended-upgrades.service
then re-enable after you finish your bake:
systemctl unmask unattended-upgrades.service
systemctl start unattended-upgrades.service
In addition, you can run this to make sure you don't kick off your process prematurely:
while systemctl is-active --quiet unattended-upgrades.service; do sleep 1; done
Probably not what you were looking for but this was extremely helpful for me. This might be related to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1803137
answered Dec 7 at 19:27
jvasallo
111
add a comment |
up vote
1
down vote
I ran into this same issue recently as well, while checking for unattended-upgrades running in the background during my image baking process. Basically, I would wait for apt locks to be released, then proceed with my updates.
I used to run this:
while pgrep unattended; do sleep 10; done;
before executing any of my scripts as they would randomly fail at some odd intervals with unattended-upgrades running while me trying to do apt install/upgrade/update with a dpkg lock error.
So I asked for the right way to check for unattended upgrades working in the background and TJ- from IRC gave me a really elegant solution! Disable the u-u service whilst bootstrap scripts are busy. As in:
systemctl mask unattended-upgrades.service
systemctl stop unattended-upgrades.service
then re-enable after you finish your bake:
systemctl unmask unattended-upgrades.service
systemctl start unattended-upgrades.service
In addition, you can run this to make sure you don't kick off your process prematurely:
while systemctl is-active --quiet unattended-upgrades.service; do sleep 1; done
Probably not what you were looking for but this was extremely helpful for me. This might be related to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1803137
answered Dec 7 at 19:27
jvasallo
111
add a comment |
up vote
1
down vote
up vote
1
down vote
I ran into this same issue recently as well, while checking for unattended-upgrades running in the background during my image baking process. Basically, I would wait for apt locks to be released, then proceed with my updates.
I used to run this:
while pgrep unattended; do sleep 10; done;
before executing any of my scripts as they would randomly fail at some odd intervals with unattended-upgrades running while me trying to do apt install/upgrade/update with a dpkg lock error.
So I asked for the right way to check for unattended upgrades working in the background and TJ- from IRC gave me a really elegant solution! Disable the u-u service whilst bootstrap scripts are busy. As in:
systemctl mask unattended-upgrades.service
systemctl stop unattended-upgrades.service
then re-enable after you finish your bake:
systemctl unmask unattended-upgrades.service
systemctl start unattended-upgrades.service
In addition, you can run this to make sure you don't kick off your process prematurely:
while systemctl is-active --quiet unattended-upgrades.service; do sleep 1; done
Probably not what you were looking for but this was extremely helpful for me. This might be related to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1803137
answered Dec 7 at 19:27
jvasallo
111
I ran into this same issue recently as well, while checking for unattended-upgrades running in the background during my image baking process. Basically, I would wait for apt locks to be released, then proceed with my updates.
I used to run this:
while pgrep unattended; do sleep 10; done;
before executing any of my scripts as they would randomly fail at some odd intervals with unattended-upgrades running while me trying to do apt install/upgrade/update with a dpkg lock error.
So I asked for the right way to check for unattended upgrades working in the background and TJ- from IRC gave me a really elegant solution! Disable the u-u service whilst bootstrap scripts are busy. As in:
systemctl mask unattended-upgrades.service
systemctl stop unattended-upgrades.service
then re-enable after you finish your bake:
systemctl unmask unattended-upgrades.service
systemctl start unattended-upgrades.service
In addition, you can run this to make sure you don't kick off your process prematurely:
while systemctl is-active --quiet unattended-upgrades.service; do sleep 1; done
Probably not what you were looking for but this was extremely helpful for me. This might be related to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1803137
answered Dec 7 at 19:27
jvasallo
111
answered Dec 7 at 19:27
jvasallo
111
answered Dec 7 at 19:27
jvasallo
111
answered Dec 7 at 19:27
jvasallo
111
111
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1098757%2fubuntu-18-10-unattended-upgrades-shutdown-wait-for-signal%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
