-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[updatenotification] use of this module creates pm2 daemon process(es) #3480
Comments
sure it's not really logical to have 2 I will inspect |
bugsounet@PC-Bugsounet:~/MagicMirror/modules$ npx jest tests/e2e/env_spec.js && grep pm2
PASS e2e ../tests/e2e/env_spec.js
App environment
✓ get request from http://localhost:8080 should return 200 (37 ms)
✓ get request from http://localhost:8080/nothing should return 404 (14 ms)
✓ should show the title MagicMirror² (201 ms)
Test Suites: 1 passed, 1 total
Tests: 3 passed, 3 total
Snapshots: 0 total
Time: 1.802 s
Ran all test suites matching /tests\/e2e\/env_spec.js/i.
(tested on my pi5, it's the same) I don't create any process with PM2. So, i don't know why you have double process, maybe double install of PM2 ??? (I don't think PM2 must avoid this) |
Thanks so far, will test this again ... |
When running mm with updatenotification module (or running tests where this module is active) we get
@bugsounet I'm not familiar with pm2, so my question is: Can we avoid these
God Daemon
processes?The text was updated successfully, but these errors were encountered: