mirror of
https://github.com/plankanban/planka.git
synced 2026-02-05 00:39:58 +03:00
planka.log is not created #556
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ipod86 on GitHub (Aug 15, 2024).
Where is the problem occurring?
I'm not sure
What browsers are you seeing the problem on?
Other
Current behaviour
Hello,
I would like to monitor Planka with fail2ban. To do this, I have mounted the logs locally. However, my logs folder remains empty.
I have tried to log in incorrectly twice and correctly twice. Is this a bug or have I configured something incorrectly?
Desired behaviour
See Logfile
Steps to reproduce
Other information
No response
@meltyshev commented on GitHub (Aug 16, 2024):
Hi! I've just tested this and everything works fine for me, I can see
planka.login the mounted folder. It looks like you're using an outdateddocker-compose.ymlfile. Please try to use the latest version, I think it might be the issue.@ipod86 commented on GitHub (Aug 16, 2024):
It still doesn't seem to work.
The folder remains empty.
Attached is my (testing) docker compose. I used the posted version. Could it be because of Portainer, which I use to run the compose?
@meltyshev commented on GitHub (Aug 16, 2024):
Hm...
Have you checked if the log file is being created in the
/app/logsdirectory of the Planka container (if the folder isn't mounted)?It could be a problem with write permissions for the mounted folder. You can try to change an owner before mounting by:
@ipod86 commented on GitHub (Aug 16, 2024):
How can I check if the folder is not mounted? I don't see any log in the mounted folder. I changed the permissions and ran compose again. No change.
@meltyshev commented on GitHub (Aug 16, 2024):
Unfortunately, I don't know what else it could be. We'll try to check it on our Portainer, but a little later.
@ipod86 commented on GitHub (Aug 16, 2024):
I just mounted the App folder without the logs. I see some folders there, but all of them have no content.
@ipod86 commented on GitHub (Aug 18, 2024):
I just had a problem in another container where I couldn't see all the files in the mount.
The option
helped there. Is there a parameter like this in planka too?
@ipod86 commented on GitHub (Aug 18, 2024):
I just tried something else. I changed my user picture and uploaded an attachment in a card. The "attachments" and "user avatars" folders are also empty. But I can see everything in planka.
So is all integrated:
@Nounoursdestavernes commented on GitHub (Aug 24, 2024):
Hi @ipod86
I had the same issue. I tried with the raw docker-compose.yml (with the ./logs volume) and the problem is, in my case (on test and on my server), a permissions issue. The
chown 1000:1000 ./logssolved the problem.Could you maybe retry this solution and update us ?
For that part:
If I understand well, you have no problem with attachment and avatars ? If it is the case, it seems to confirm the permissions problem. Because in the case of
user-avatarsand the other volumes (excepted logs) docker will handle everything about volumes and "hide" them on/var/lib/docker/volumesIf the chown command doesn't work you can investigate with the following idea:
In the docker compose file use
instead of the
Check the permissions of the user-avatars folder in the host machine and try to upload an avatar.
If the upload does'nt work this is a permissions issue for sure. (and the chown should work)
Otherwise check the difference in permissions between the two folders (logs and user-avatars)
If there is no difference then remove the logs volume in the docker file and run the container.
Then use the following command to have a bash in the docker:
docker exec -ti <container name> /bin/bashwith the right container name that you can get with docker psThen inside the docker check that the logs/planka.log file exist.
If it's the case then it is a permissions problem but here I have no idea
If the file does'nt exist that mean there is a problem elsewhere (and actually have no idea where it is)
Hope this will help. Don't hesitate to ask anything if something is unclear or weird :)
@ipod86 commented on GitHub (Aug 24, 2024):
It works with chmod 1000.
Thank you