-
-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Folder "logs" can not be created, if a symlink with same name exists. #1367
Comments
Is this only a problem when running in docker, or does the native run also show it? Is this perhaps a docker-specific thing unrelated to PMM? |
I have no idea, but I would be happy to test this, IF I knew how... (I only got PMM installed via the unraid "docker manager" and can't see how to run it native) |
@gitttt54 is this still an issue? |
Unfortunately, yes, there is no difference since my initial post: I just reproduced it via:
I reverted the changes (removed link and created a log folder) and it worked flawlessly. |
I noticed that you are using pmm.logs as the folder for symlink. Perhaps PMM is seeing the .logs and thinks it's a file rather than directory, causing the error? Do you have any change in behavior if you use '/tmp/pmm/logs'? |
@gitttt54 can you test with the latest nightly i think i figured out a fix |
atm, I can‘t test. It‘ll take a month at least I think. EDIT: works great! thank you! EDIT EDIT: it runs smoothy, with this:
but not with this:
Dunno, what the problem is here... |
Version Number
1.18.3-nightly170 (Docker)
What branch are you on?
nightly
Describe the Bug
Coming from here: #1350
I'm not sure, this is really a bug, but -to be honest- I would like to have a nicer handling. So let me explain:
I'm trying to "move" the PMM
logs
folder to/tmp
because they don't need to be permanent IMHO.I stopped the container, deleted the old
logs
folder, created a symlink, restarted the container and started PMM:I guess, the message tells me, that PMM can not create its
logs
folder, because something (the symlink?) is in the way.There is a workaround, to tell the docker container config to use that
/tmp
path directly, like-v '/tmp/pmm.logs/':'/config/logs':'rw'
, and then create a symlink, saylogs2
which points to/tmp/pmm.logs
, but PMM still creates its ownlogs
folder.So there is an empty
logs
folder and the user needs to use the symlinkedlogs2
.Not exactly nice/transparent.
So my request would be:
Can we have the option to let PMM use the symlink instead of quitting with an error?
Thank you.
The text was updated successfully, but these errors were encountered: