[GH-ISSUE #3685] Log errors: unknown user 'npm' #2439

Open
opened 2026-02-26 07:35:34 +03:00 by kerem · 4 comments
Owner

Originally created by @DrEVILish on GitHub (Apr 6, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3685

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • No - using native Linux install
  • Are you sure you're not using someone else's docker image?
    • No
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug

Installed using:
https://github.com/tteck/Proxmox/raw/main/ct/nginxproxymanager.sh

Running a standard instance of NginxProxyManager, getting the following error message.

In 'journalctl -xe'

Apr 06 14:25:04 nginxproxymanager node[148]: [4/6/2024] [2:25:04 PM] [Setup ] <80> <9A> CommandError: error: /etc/logrotate.d/nginx-proxy-manager:2 unknown user 'npm'
Apr 06 14:25:04 nginxproxymanager node[148]: error: found error in /data/logs/_access.log /data/logs//access.log , skipping
Apr 06 14:25:04 nginxproxymanager node[148]: error: /etc/logrotate.d/nginx-proxy-manager:16 unknown user 'npm'
Apr 06 14:25:04 nginxproxymanager node[148]: error: found error in /data/logs/_error.log /data/logs//error.log , skipping
Apr 06 14:25:04 nginxproxymanager node[148]: at /app/lib/utils.js:16:13
Apr 06 14:25:04 nginxproxymanager node[148]: at ChildProcess.exithandler (node:child_process:410:5)
Apr 06 14:25:04 nginxproxymanager node[148]: at ChildProcess.emit (node:events:513:28)
Apr 06 14:25:04 nginxproxymanager node[148]: at maybeClose (node:internal/child_process:1100:16)
Apr 06 14:25:04 nginxproxymanager node[148]: at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

Originally created by @DrEVILish on GitHub (Apr 6, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3685 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - No - using native Linux install - Are you sure you're not using someone else's docker image? - No - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** Installed using: https://github.com/tteck/Proxmox/raw/main/ct/nginxproxymanager.sh Running a standard instance of NginxProxyManager, getting the following error message. In 'journalctl -xe' Apr 06 14:25:04 nginxproxymanager node[148]: [4/6/2024] [2:25:04 PM] [Setup ] <80> <9A> CommandError: error: /etc/logrotate.d/nginx-proxy-manager:2 unknown user 'npm' Apr 06 14:25:04 nginxproxymanager node[148]: error: found error in /data/logs/_access.log /data/logs//access.log , skipping Apr 06 14:25:04 nginxproxymanager node[148]: error: /etc/logrotate.d/nginx-proxy-manager:16 unknown user 'npm' Apr 06 14:25:04 nginxproxymanager node[148]: error: found error in /data/logs/_error.log /data/logs//error.log , skipping Apr 06 14:25:04 nginxproxymanager node[148]: at /app/lib/utils.js:16:13 Apr 06 14:25:04 nginxproxymanager node[148]: at ChildProcess.exithandler (node:child_process:410:5) Apr 06 14:25:04 nginxproxymanager node[148]: at ChildProcess.emit (node:events:513:28) Apr 06 14:25:04 nginxproxymanager node[148]: at maybeClose (node:internal/child_process:1100:16) Apr 06 14:25:04 nginxproxymanager node[148]: at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
Author
Owner

@rmonteremal commented on GitHub (Jul 14, 2024):

I have the exact same issue after updating my nginx proxy manager LXC using ttkeck's update script. Have you managed to solve it?

<!-- gh-comment-id:2227299197 --> @rmonteremal commented on GitHub (Jul 14, 2024): I have the exact same issue after updating my nginx proxy manager LXC using ttkeck's update script. Have you managed to solve it?
Author
Owner

@navels commented on GitHub (Jul 14, 2024):

root cause and workaround: https://github.com/tteck/Proxmox/issues/2745#issuecomment-2138811196

<!-- gh-comment-id:2227441090 --> @navels commented on GitHub (Jul 14, 2024): root cause and workaround: https://github.com/tteck/Proxmox/issues/2745#issuecomment-2138811196
Author
Owner

@rmonteremal commented on GitHub (Jul 14, 2024):

root cause and workaround: tteck/Proxmox#2745 (comment)

Thanks, I had notice this and already replaced those lines, but now it's the openresty service that doesn't seem to run:
"nginx: [emerg] open() "/run/nginx/nginx.pid" failed (2: No such file or directory)", seems like the PID file for nginx doesn't get created for whatever reason

I'll keep on digging

<!-- gh-comment-id:2227485331 --> @rmonteremal commented on GitHub (Jul 14, 2024): > root cause and workaround: [tteck/Proxmox#2745 (comment)](https://github.com/tteck/Proxmox/issues/2745#issuecomment-2138811196) Thanks, I had notice this and already replaced those lines, but now it's the openresty service that doesn't seem to run: "nginx: [emerg] open() "/run/nginx/nginx.pid" failed (2: No such file or directory)", seems like the PID file for nginx doesn't get created for whatever reason I'll keep on digging
Author
Owner

@github-actions[bot] commented on GitHub (Feb 19, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2667334569 --> @github-actions[bot] commented on GitHub (Feb 19, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#2439
No description provided.