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

Updated init script for Amazon and CentOS #1156

Closed
wants to merge 2 commits into from
Closed

Updated init script for Amazon and CentOS #1156

wants to merge 2 commits into from

Conversation

ItalyPaleAle
Copy link

This fixes #1100

The script contains the fixes from the "centos" one to change user.
In addition, contains @ObjectIsAdvantag 's fix for PM2_HOME

EgoAleSum added 2 commits April 8, 2015 14:06
This fixes #1100
The script contains the fixes from the "centos" one to change user.
In addition, contains @ObjectIsAdvantag 's fix for PM2_HOME
@soyuka
Copy link
Collaborator

soyuka commented Apr 9, 2015

Could you please take a look at #1120 (centos startup fix) to see if it corrects the same issue you had regarding centos? If not, please comment on there so we get along with those pull requests, thanks!

@claflico
Copy link

What version of CentOS would this be for? I'm trying to puppetize the install and configuration of pm2 as a service on CentOS 7 and the deployment fails when I use the pm2-init-centos.sh file as a template.

@ItalyPaleAle
Copy link
Author

@claflico what error do you get?

@claflico
Copy link

Since CentOS 7 uses systemd Puppet wants to use "systemctl enable name" to define a service and that fails because it can't find the /usr/lib/systemd/system/pm2.service file. I was able to resolve it by doing away with using the chckonfig/pm2-init-centos.sh method and using the pm2.service file method instead.

@Unitech
Copy link
Owner

Unitech commented Dec 16, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Amazon EC2 : saved PM2 configuration is not recognized at startup (when running pm2 in user mode)
4 participants