Hi, I'm using the 3.3.0p3, and I've noticed an error occurring. It happens every night, so it's a cron thing. This is in the ispconfig.log every day at midnight: Code: 20.01.2026-00:19 - ERROR - Error executing jk_init command: ERROR: jail directory coreutils is not safe Usage: /usr/sbin/jk_init [OPTIONS] Usage: /usr/sbin/jk_init [OPTIONS] -j jaildir sections... -h --help : this help screen -c, --configfile=FILE : specify configfile location -l, --list : list all available sections in the configfile -j, --jail= : specify the jail to use. For backwards compatibility, if no jail is specified, the first argument after the options will be used as jail -v, --verbose : show what is being done -f, --force : force overwriting of existing files -k, --hardlink : use hardlinks if possible I have only 1 user with SSH access. The Server config - Jailkit looks like this: I have no idea what's going on. I've found the same issue in a different thread, but that is a locked one, so I couldn't rely there: https://forum.howtoforge.com/threads/error-on-log.94235/ Also, there was no solution at the end. Does anyone have any ideas? Thanks in advance!
I am quite sure that the solution I found in the thread linked above was related with permisions. Please check the site in which the jailkit user belongs using a root ssh session. Find for folders that should be owned by root:root and are owned by clientXXX:webXXX. You can compare the permisions with another site you have. If you don't have more websites, create one just for check which permisions it is asigned. In my case, both the whole client folder and the whole site folder was owned by clientXXX:webXXX, and they should be owned by root:root. I expect this is helpful for you, please check and share your results. Best.
Thank you, I've checked all the folders, and I've found only one that had different owners from the other user's folder. Let's see what happens this night...
I've checked the DB, and in the sys_cron table, these tasks ran around the similar time when the issue happened: Code: cronjob_backup 2026-01-22 00:16:02 cronjob_ftplogfiles 2026-01-22 00:15:25 cronjob_goaccess 2026-01-22 00:15:25 cronjob_logfiles 2026-01-22 00:15:25 cronjob_monitor_rkhunter 2026-01-22 00:00:03 cronjob_openvz 2026-01-22 00:16:02 cronjob_quota_notify 2026-01-22 00:15:27 cronjob_webalizer 2026-01-22 00:15:25 The log entry was created at 00:19. I don't use goaccess, openvz and webalizer, so I don't think any of those triggered this issue. I'll keep investigating.
What I would do is to create a new site, then a new ssh user, and then to check for any differences between owners (I think you have done this yet) and also permisions on the newly created site and the production site you have with the ssh user. Another thing to try is to delete the ssh user, if you can do this without losing information, and check if the error persists.
