You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since installing immich-public-proxy on my server, I noticed that every once in a while, there are zombie processes.
I previously never had zombie processes on my system, so I checked what is causing the processes.
The processes are the wget cmd, apparently executed by dist/index.js, caused by pm2-runtime which is started by the docker container of immich-public-proxy.
I don't know, what exactly is causing the zombie processes, but here is an excerpt of my docker container log with the PM2 messages:
2025-02-08T00:12:38: PM2 log: Stopping app:index id:0
2025-02-08T00:12:38: PM2 error: Error: spawn ps ENOENT
2025-02-08T00:12:39: PM2 log: App [index:0] exited with code [0] via signal [SIGINT]
2025-02-08T00:12:39: PM2 log: pid=18 msg=process killed
2025-02-08T00:12:39: PM2 log: PM2 successfully stopped
2025-02-08T00:13:14: PM2 log: Launching in no daemon mode
2025-02-08T00:13:14: PM2 log: App [index:0] starting in -fork mode-
2025-02-08T00:13:14: PM2 log: App [index:0] online
Is this caused by something in the immich-public-proxy code or is it a bug in dependencies?
Thanks for your help 😊
The text was updated successfully, but these errors were encountered:
Thanks for the info - I was thinking of removing PM2 anyway, as I'm not convinced it does anything useful. That should solve the issue after I do that.
Hi 😊
Since installing immich-public-proxy on my server, I noticed that every once in a while, there are zombie processes.
I previously never had zombie processes on my system, so I checked what is causing the processes.
The processes are the wget cmd, apparently executed by
dist/index.js
, caused by pm2-runtime which is started by the docker container of immich-public-proxy.I don't know, what exactly is causing the zombie processes, but here is an excerpt of my docker container log with the PM2 messages:
Is this caused by something in the immich-public-proxy code or is it a bug in dependencies?
Thanks for your help 😊
The text was updated successfully, but these errors were encountered: