Pm2 overwriting dump.pm2 at restart

Question

0.00/5 (No votes)

See more:

I'm working in Centos 7, trying to get a node.js app to automatically start at boot.

I'm using PM2 for this, and all seems fine until I reboot the server, at which point the dump.pm2 file is overwritten and is blank.

Any ideas?

What I have tried:

I can 'pm2 delete process' and 'pm2 resurrect' to my heart's content while the system's up, but if I restart the server it fails.

As a test, I made a copy of the dump.pm2 file and rebooted the server. the dump.pm2 file was empty after reboot, but I restored my backup copy after which the 'pm2 resurrect' command successfully started my application list.

Posted 5-Mar-16 9:26am

David Cunningham5.9K

Updated 27-Apr-16 8:42am

Add a Solution

2 solutions

Solution 2

I had the same issue on a Raspberry Pi running Debian. Please look at the following solution:

Startup is not starting pm2 daemon and saved process · Issue #1055 · Unitech/pm2 · GitHub[^]

It seems that you will need to comment the following line:

Java

#super $PM2 dump

This line is located in the stop() function inside the /etc/init.d/pm2-init.sh file.

Hope it helps.

Posted 6-Mar-16 14:27pm

mariossavva

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

David Cunningham · Accepted Answer · 2016-03-06T01:50:00

It would appear that there is a bug in the current pm2 implementation.

The bug appears when you try to run pm2 in a non root account. Somehow, during boot and while pm2 is loading, it appears to be examining the incorrect folder for the existence of a dump.pm2 file (which holds the desired application list and parameters). When it doesn't find the file, it makes note that it needs to create one. Later, after switching into the appropriate user account, it then writes a blank dump.pm2 file which overwrites the previously created one.

This GitHub submission identifies the issue:

https://github.com/Unitech/PM2/pull/1120/files?diff=split

You can also temporarily remedy the issue by making making the dump.pm2 file immutable after you save your desired startup application list

i.e.

C++

pm2 save                        // store current running application list to dump.pm2
su                              // switch to root account
cd /home/{pm2useraccount}/.pm2  // move to .pm2 folder for user in which pm2 is running
chattr +i dump.pm2              // mark dump.pm2 file as immutable.