Cron error after update to 2.0.20

Issue #516 resolved
Stephan Krebernik created an issue

Hi,

after the last update to 2.0.20 I get this error by mail:

/etc/cron.daily/logrotate: error: skipping "/var/log/admin-app/dev.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/admin-app/prod.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/admin-app/test.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. run-parts: /etc/cron.daily/logrotate exited with return code 1

any hint how to fix this?

thanks a lot!

Comments (7)

  1. Scott MacDonald

    Hi... do you continue to receive this error after restarting your poste.io container? What version did you upgrade from?

  2. Stephan Krebernik reporter

    Yes, after restarting the container I keep receiving the error by mail.

    I upgraded from 2.0.19 to 20.0.20

  3. real3x

    Hi, after upgrading to 2.0.23 i still have the same cron error :

    #!
    /etc/cron.daily/logrotate: 
    error: skipping "/var/log/admin-app/dev.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. 
    error: skipping "/var/log/admin-app/prod.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. 
    error: skipping "/var/log/admin-app/test.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. 
    run-parts: /etc/cron.daily/logrotate exited with return code 1 
    

    My data directory :

    poladroid 2018-12-24 à 09.53.29.png

    Happy xmas :)

  4. Log in to comment