flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror
I recently upgraded an Ubuntu 16.04 virtual machine to 18.04. I regularly use this VM to run apt-mirror at school on their high-speed internet, then rsync these files to my rack-mount server at home for updating multiple computers at home without wasting the tiny amount of bandwidth I have there. Since updating I can't get apt-mirror to run on my VM. It keeps giving the error:
flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror line 214
immediately followed by:
apt-mirror is already running, exiting at /usr/bin/apt-mirror line 217
apt-mirror is NOT running, and does not have a cron job. I've tried rebooting, and even looked for the old-style lockfile to delete, but I guess that method is no longer used. Is there some way to force unlock this so I can run apt-mirror?
UPDATE: So... I finally tried running apt-mirror as sudo. This is currently working, but I'm pretty sure when I rsync these files at home I'm going to be forced to chown the files so that I can actually access them. Is there some way to fix this, and why is apt-mirror giving me an flock() error, and not simply telling me I need to be su to run?
apt-mirror
asked Feb 27 at 21:06
BenBen
266
add a comment |
I recently upgraded an Ubuntu 16.04 virtual machine to 18.04. I regularly use this VM to run apt-mirror at school on their high-speed internet, then rsync these files to my rack-mount server at home for updating multiple computers at home without wasting the tiny amount of bandwidth I have there. Since updating I can't get apt-mirror to run on my VM. It keeps giving the error:
flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror line 214
immediately followed by:
apt-mirror is already running, exiting at /usr/bin/apt-mirror line 217
apt-mirror is NOT running, and does not have a cron job. I've tried rebooting, and even looked for the old-style lockfile to delete, but I guess that method is no longer used. Is there some way to force unlock this so I can run apt-mirror?
UPDATE: So... I finally tried running apt-mirror as sudo. This is currently working, but I'm pretty sure when I rsync these files at home I'm going to be forced to chown the files so that I can actually access them. Is there some way to fix this, and why is apt-mirror giving me an flock() error, and not simply telling me I need to be su to run?
apt-mirror
asked Feb 27 at 21:06
BenBen
266
add a comment |
I recently upgraded an Ubuntu 16.04 virtual machine to 18.04. I regularly use this VM to run apt-mirror at school on their high-speed internet, then rsync these files to my rack-mount server at home for updating multiple computers at home without wasting the tiny amount of bandwidth I have there. Since updating I can't get apt-mirror to run on my VM. It keeps giving the error:
flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror line 214
immediately followed by:
apt-mirror is already running, exiting at /usr/bin/apt-mirror line 217
apt-mirror is NOT running, and does not have a cron job. I've tried rebooting, and even looked for the old-style lockfile to delete, but I guess that method is no longer used. Is there some way to force unlock this so I can run apt-mirror?
UPDATE: So... I finally tried running apt-mirror as sudo. This is currently working, but I'm pretty sure when I rsync these files at home I'm going to be forced to chown the files so that I can actually access them. Is there some way to fix this, and why is apt-mirror giving me an flock() error, and not simply telling me I need to be su to run?
apt-mirror
asked Feb 27 at 21:06
BenBen
266
I recently upgraded an Ubuntu 16.04 virtual machine to 18.04. I regularly use this VM to run apt-mirror at school on their high-speed internet, then rsync these files to my rack-mount server at home for updating multiple computers at home without wasting the tiny amount of bandwidth I have there. Since updating I can't get apt-mirror to run on my VM. It keeps giving the error:
flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror line 214
immediately followed by:
apt-mirror is already running, exiting at /usr/bin/apt-mirror line 217
apt-mirror is NOT running, and does not have a cron job. I've tried rebooting, and even looked for the old-style lockfile to delete, but I guess that method is no longer used. Is there some way to force unlock this so I can run apt-mirror?
UPDATE: So... I finally tried running apt-mirror as sudo. This is currently working, but I'm pretty sure when I rsync these files at home I'm going to be forced to chown the files so that I can actually access them. Is there some way to fix this, and why is apt-mirror giving me an flock() error, and not simply telling me I need to be su to run?
apt-mirror
apt-mirror
asked Feb 27 at 21:06
BenBen
266
asked Feb 27 at 21:06
BenBen
266
edited Mar 1 at 15:06
Ben
asked Feb 27 at 21:06
BenBen
266
asked Feb 27 at 21:06
BenBen
266
asked Feb 27 at 21:06
BenBen
266
266
add a comment |
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
});
}
});
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%2f1121803%2fflock-on-closed-filehandle-lock-file-at-usr-bin-apt-mirror%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
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%2f1121803%2fflock-on-closed-filehandle-lock-file-at-usr-bin-apt-mirror%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
