File/directory not being deleted?
Please see the screenshot. The image on the left says existing x installation found at /opt/x
The image on the right shows the terminal where I attempt to delete the same directory.
The terminal on the right shows sudo rm -f -r -d /opt/x and it has no output.
ls also doesnt show /opt/x.
Is anybody able to figure out what's going on here? ls shows no such directory and rm doesnt seem to remove it, yet the application manages to find something. FWIW, I was trying to remove a Postgresql component. Should I also post this in dba.stackexchange.com?
files rm postgresql
asked Aug 10 '15 at 18:15
YogeschYogesch
18415
add a comment |
Please see the screenshot. The image on the left says existing x installation found at /opt/x
The image on the right shows the terminal where I attempt to delete the same directory.
The terminal on the right shows sudo rm -f -r -d /opt/x and it has no output.
ls also doesnt show /opt/x.
Is anybody able to figure out what's going on here? ls shows no such directory and rm doesnt seem to remove it, yet the application manages to find something. FWIW, I was trying to remove a Postgresql component. Should I also post this in dba.stackexchange.com?
files rm postgresql
asked Aug 10 '15 at 18:15
YogeschYogesch
18415
1
Use the command line, and give the commands and their output as code (add four spaces in front of each line) in your question. Your image is unreadable, so edit your question to improve it.
– Basile Starynkevitch
Aug 10 '15 at 18:17
@BasileStarynkevitch done, hope it's better now
– Yogesch
Aug 10 '15 at 18:23
Probably a postgresql.conf file still in /etc/postgresql that points at /opt/pgAgent
– steve
Aug 10 '15 at 18:28
I had done adpkg --purge $(dpkg -l | grep rc | grep pg)anddpkg --purge $(dpkg -l | grep rc | grep post). Could any .conf files still remain after that?
– Yogesch
Aug 10 '15 at 18:37
1
@steve Yes, indeed. It seems to work now after doing a thorough cleanup of all possible postgres files in all the /etc, /bin, /usr, /usr, /var, /tmp, /opt directories. thanks :) seems like the purge options (in dpkg, as well as apt-get of course) don't really purge everything and leave lingering bits behind. I didn't retry after cleaning through each location, so can't pinpoint it precisely, but it was a leftover...
– Yogesch
Aug 10 '15 at 20:10
add a comment |
Please see the screenshot. The image on the left says existing x installation found at /opt/x
The image on the right shows the terminal where I attempt to delete the same directory.
The terminal on the right shows sudo rm -f -r -d /opt/x and it has no output.
ls also doesnt show /opt/x.
Is anybody able to figure out what's going on here? ls shows no such directory and rm doesnt seem to remove it, yet the application manages to find something. FWIW, I was trying to remove a Postgresql component. Should I also post this in dba.stackexchange.com?
files rm postgresql
asked Aug 10 '15 at 18:15
YogeschYogesch
18415
Please see the screenshot. The image on the left says existing x installation found at /opt/x
The image on the right shows the terminal where I attempt to delete the same directory.
The terminal on the right shows sudo rm -f -r -d /opt/x and it has no output.
ls also doesnt show /opt/x.
Is anybody able to figure out what's going on here? ls shows no such directory and rm doesnt seem to remove it, yet the application manages to find something. FWIW, I was trying to remove a Postgresql component. Should I also post this in dba.stackexchange.com?
files rm postgresql
files rm postgresql
asked Aug 10 '15 at 18:15
YogeschYogesch
18415
asked Aug 10 '15 at 18:15
YogeschYogesch
18415
edited Aug 10 '15 at 18:20
Yogesch
asked Aug 10 '15 at 18:15
YogeschYogesch
18415
asked Aug 10 '15 at 18:15
YogeschYogesch
18415
asked Aug 10 '15 at 18:15
YogeschYogesch
18415
18415
1
Use the command line, and give the commands and their output as code (add four spaces in front of each line) in your question. Your image is unreadable, so edit your question to improve it.
– Basile Starynkevitch
Aug 10 '15 at 18:17
@BasileStarynkevitch done, hope it's better now
– Yogesch
Aug 10 '15 at 18:23
Probably a postgresql.conf file still in /etc/postgresql that points at /opt/pgAgent
– steve
Aug 10 '15 at 18:28
I had done adpkg --purge $(dpkg -l | grep rc | grep pg)anddpkg --purge $(dpkg -l | grep rc | grep post). Could any .conf files still remain after that?
– Yogesch
Aug 10 '15 at 18:37
1
@steve Yes, indeed. It seems to work now after doing a thorough cleanup of all possible postgres files in all the /etc, /bin, /usr, /usr, /var, /tmp, /opt directories. thanks :) seems like the purge options (in dpkg, as well as apt-get of course) don't really purge everything and leave lingering bits behind. I didn't retry after cleaning through each location, so can't pinpoint it precisely, but it was a leftover...
– Yogesch
Aug 10 '15 at 20:10
add a comment |
1
Use the command line, and give the commands and their output as code (add four spaces in front of each line) in your question. Your image is unreadable, so edit your question to improve it.
– Basile Starynkevitch
Aug 10 '15 at 18:17
@BasileStarynkevitch done, hope it's better now
– Yogesch
Aug 10 '15 at 18:23
Probably a postgresql.conf file still in /etc/postgresql that points at /opt/pgAgent
– steve
Aug 10 '15 at 18:28
I had done adpkg --purge $(dpkg -l | grep rc | grep pg)anddpkg --purge $(dpkg -l | grep rc | grep post). Could any .conf files still remain after that?
– Yogesch
Aug 10 '15 at 18:37
1
@steve Yes, indeed. It seems to work now after doing a thorough cleanup of all possible postgres files in all the /etc, /bin, /usr, /usr, /var, /tmp, /opt directories. thanks :) seems like the purge options (in dpkg, as well as apt-get of course) don't really purge everything and leave lingering bits behind. I didn't retry after cleaning through each location, so can't pinpoint it precisely, but it was a leftover...
– Yogesch
Aug 10 '15 at 20:10
1
1
Use the command line, and give the commands and their output as code (add four spaces in front of each line) in your question. Your image is unreadable, so edit your question to improve it.
– Basile Starynkevitch
Aug 10 '15 at 18:17
Use the command line, and give the commands and their output as code (add four spaces in front of each line) in your question. Your image is unreadable, so edit your question to improve it.
– Basile Starynkevitch
Aug 10 '15 at 18:17
@BasileStarynkevitch done, hope it's better now
– Yogesch
Aug 10 '15 at 18:23
@BasileStarynkevitch done, hope it's better now
– Yogesch
Aug 10 '15 at 18:23
Probably a postgresql.conf file still in /etc/postgresql that points at /opt/pgAgent
– steve
Aug 10 '15 at 18:28
Probably a postgresql.conf file still in /etc/postgresql that points at /opt/pgAgent
– steve
Aug 10 '15 at 18:28
I had done a
dpkg --purge $(dpkg -l | grep rc | grep pg) and dpkg --purge $(dpkg -l | grep rc | grep post). Could any .conf files still remain after that?– Yogesch
Aug 10 '15 at 18:37
I had done a
dpkg --purge $(dpkg -l | grep rc | grep pg) and dpkg --purge $(dpkg -l | grep rc | grep post). Could any .conf files still remain after that?– Yogesch
Aug 10 '15 at 18:37
1
1
@steve Yes, indeed. It seems to work now after doing a thorough cleanup of all possible postgres files in all the /etc, /bin, /usr, /usr, /var, /tmp, /opt directories. thanks :) seems like the purge options (in dpkg, as well as apt-get of course) don't really purge everything and leave lingering bits behind. I didn't retry after cleaning through each location, so can't pinpoint it precisely, but it was a leftover...
– Yogesch
Aug 10 '15 at 20:10
@steve Yes, indeed. It seems to work now after doing a thorough cleanup of all possible postgres files in all the /etc, /bin, /usr, /usr, /var, /tmp, /opt directories. thanks :) seems like the purge options (in dpkg, as well as apt-get of course) don't really purge everything and leave lingering bits behind. I didn't retry after cleaning through each location, so can't pinpoint it precisely, but it was a leftover...
– Yogesch
Aug 10 '15 at 20:10
add a comment |
2 Answers
2
active
oldest
votes
See comments, but essentially removing some lingering configuration files which still pointed at /opt/pgAgent solved this. Suggest it is marked as answered.
(OP did a manual cleanup of remaining configuration files and this enabled the install to work correctly)
answered Aug 10 '15 at 20:47
stevesteve
13.9k22452
add a comment |
If you use, for example, a mountable USB device, the connection may have loosened after the mount. The directories will appear clobbered (as you described). You may unmount and then remount the device once it is plugged in properly. An alternative may be just to plug in correctly before even unmounting and checking whether the directories became available. I'm not sure which may be the safer way to avoid data loss. I went only through the first approach.
answered Jan 1 at 22:32
Wolfram JWolfram J
1
discovered on another screen the message : unable to stop the drive, timeout was reached (RHEL)
– Wolfram J
Jan 2 at 1:23
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
});
}
});
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%2f222354%2ffile-directory-not-being-deleted%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
See comments, but essentially removing some lingering configuration files which still pointed at /opt/pgAgent solved this. Suggest it is marked as answered.
(OP did a manual cleanup of remaining configuration files and this enabled the install to work correctly)
answered Aug 10 '15 at 20:47
stevesteve
13.9k22452
add a comment |
See comments, but essentially removing some lingering configuration files which still pointed at /opt/pgAgent solved this. Suggest it is marked as answered.
(OP did a manual cleanup of remaining configuration files and this enabled the install to work correctly)
answered Aug 10 '15 at 20:47
stevesteve
13.9k22452
add a comment |
See comments, but essentially removing some lingering configuration files which still pointed at /opt/pgAgent solved this. Suggest it is marked as answered.
(OP did a manual cleanup of remaining configuration files and this enabled the install to work correctly)
answered Aug 10 '15 at 20:47
stevesteve
13.9k22452
See comments, but essentially removing some lingering configuration files which still pointed at /opt/pgAgent solved this. Suggest it is marked as answered.
(OP did a manual cleanup of remaining configuration files and this enabled the install to work correctly)
answered Aug 10 '15 at 20:47
stevesteve
13.9k22452
answered Aug 10 '15 at 20:47
stevesteve
13.9k22452
answered Aug 10 '15 at 20:47
stevesteve
13.9k22452
answered Aug 10 '15 at 20:47
stevesteve
13.9k22452
13.9k22452
add a comment |
add a comment |
If you use, for example, a mountable USB device, the connection may have loosened after the mount. The directories will appear clobbered (as you described). You may unmount and then remount the device once it is plugged in properly. An alternative may be just to plug in correctly before even unmounting and checking whether the directories became available. I'm not sure which may be the safer way to avoid data loss. I went only through the first approach.
answered Jan 1 at 22:32
Wolfram JWolfram J
1
discovered on another screen the message : unable to stop the drive, timeout was reached (RHEL)
– Wolfram J
Jan 2 at 1:23
add a comment |
If you use, for example, a mountable USB device, the connection may have loosened after the mount. The directories will appear clobbered (as you described). You may unmount and then remount the device once it is plugged in properly. An alternative may be just to plug in correctly before even unmounting and checking whether the directories became available. I'm not sure which may be the safer way to avoid data loss. I went only through the first approach.
answered Jan 1 at 22:32
Wolfram JWolfram J
1
discovered on another screen the message : unable to stop the drive, timeout was reached (RHEL)
– Wolfram J
Jan 2 at 1:23
add a comment |
If you use, for example, a mountable USB device, the connection may have loosened after the mount. The directories will appear clobbered (as you described). You may unmount and then remount the device once it is plugged in properly. An alternative may be just to plug in correctly before even unmounting and checking whether the directories became available. I'm not sure which may be the safer way to avoid data loss. I went only through the first approach.
answered Jan 1 at 22:32
Wolfram JWolfram J
1
If you use, for example, a mountable USB device, the connection may have loosened after the mount. The directories will appear clobbered (as you described). You may unmount and then remount the device once it is plugged in properly. An alternative may be just to plug in correctly before even unmounting and checking whether the directories became available. I'm not sure which may be the safer way to avoid data loss. I went only through the first approach.
answered Jan 1 at 22:32
Wolfram JWolfram J
1
answered Jan 1 at 22:32
Wolfram JWolfram J
1
answered Jan 1 at 22:32
Wolfram JWolfram J
1
answered Jan 1 at 22:32
Wolfram JWolfram J
1
1
discovered on another screen the message : unable to stop the drive, timeout was reached (RHEL)
– Wolfram J
Jan 2 at 1:23
add a comment |
discovered on another screen the message : unable to stop the drive, timeout was reached (RHEL)
– Wolfram J
Jan 2 at 1:23
discovered on another screen the message : unable to stop the drive, timeout was reached (RHEL)
– Wolfram J
Jan 2 at 1:23
discovered on another screen the message : unable to stop the drive, timeout was reached (RHEL)
– Wolfram J
Jan 2 at 1:23
add a comment |
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.
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%2f222354%2ffile-directory-not-being-deleted%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
1
Use the command line, and give the commands and their output as code (add four spaces in front of each line) in your question. Your image is unreadable, so edit your question to improve it.
– Basile Starynkevitch
Aug 10 '15 at 18:17
@BasileStarynkevitch done, hope it's better now
– Yogesch
Aug 10 '15 at 18:23
Probably a postgresql.conf file still in /etc/postgresql that points at /opt/pgAgent
– steve
Aug 10 '15 at 18:28
I had done a
dpkg --purge $(dpkg -l | grep rc | grep pg)anddpkg --purge $(dpkg -l | grep rc | grep post). Could any .conf files still remain after that?– Yogesch
Aug 10 '15 at 18:37
1
@steve Yes, indeed. It seems to work now after doing a thorough cleanup of all possible postgres files in all the /etc, /bin, /usr, /usr, /var, /tmp, /opt directories. thanks :) seems like the purge options (in dpkg, as well as apt-get of course) don't really purge everything and leave lingering bits behind. I didn't retry after cleaning through each location, so can't pinpoint it precisely, but it was a leftover...
– Yogesch
Aug 10 '15 at 20:10