Skip to content
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

Logrotate Service fails with default npm installation #183

Open
Wolvan opened this issue Aug 10, 2024 · 0 comments
Open

Logrotate Service fails with default npm installation #183

Wolvan opened this issue Aug 10, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@Wolvan
Copy link

Wolvan commented Aug 10, 2024

Script
nginx-proxy-manager

Describe the bug
Using the script to install nginx proxy manager on a Debian 12 baremetal/VM leads to setting up the logrotate service. The service fails to run because by default both log rotate definitions under /etc/logrotate.d/nginx-proxy-manager require the user npm (su npm npm).
Removing the su npm npm line makes logrotate start normally. The log files are owned by the user root anyways.

System info:

  • Debian Version: 12

Screenshots
image

Additional context
Default nginx-proxy-manager file

/data/logs/*_access.log /data/logs/*/access.log {
    su npm npm
    create 0644
    weekly
    rotate 4
    missingok
    notifempty
    compress
    sharedscripts
    postrotate
    /bin/kill -USR1 `cat /run/nginx.pid 2>/dev/null` 2>/dev/null || true
    endscript
}

/data/logs/*_error.log /data/logs/*/error.log {
    su npm npm
    create 0644
    weekly
    rotate 10
    missingok
    notifempty
    compress
    sharedscripts
    postrotate
    /bin/kill -USR1 `cat /run/nginx.pid 2>/dev/null` 2>/dev/null || true
    endscript
}
@Wolvan Wolvan added the bug Something isn't working label Aug 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants