PM2 Start Probleme

Gothic · 18. Februar 2015

Guten Tag,
ich habe eben versucht das nodePush bei mir zu installieren uns es Funktioniert auch fast wenn ich npm start nutze geht auch alles wunderbar.
Dann habe ich es versucht mit PM2 zu starten was nicht funktioniert.
npm start:

Code

[website@ns508025 be.bastelstu.wcf.nodePush]$ npm start


> be.bastelstu.wcf.nodePush@1.0.0 start /home/website/public_html/wcf/acp/be.bastelstu.wcf.nodePush
> coffee app.coffee


nodePush (pid:17933)
====================
warning: Cannot load config: Error: ENOENT, no such file or directory '/home/website/public_html/wcf/acp/be.bastelstu.wcf.nodePush/config'
info: Inbound-Socket: /home/website/public_html/wcf/acp/be.bastelstu.wcf.nodePush/tmp/inbound.sock
info: Outbound-Socket: 0.0.0.0:9001
info: Done

Alles anzeigen

PM2:

Code

2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Starting execution sequence in -fork mode- for app name:config id:4
2015-02-18 04:52:30: App name:config id:4 online
2015-02-18 04:52:30: App closed with code: 0
2015-02-18 04:52:30: App name:config id:4 exited
2015-02-18 04:52:30: Script /home/website/public_html/wcf/acp/be.bastelstu.wcf.nodePush/config.js had too many unstable restarts (15). Stopped. "errored"

Alles anzeigen

**Tim** · 18. Februar 2015

Hallo,

du solltest ausführen, wie genau du pm2 verwendest…

Gothic · 18. Februar 2015

Ich habe verschiedene sachen versucht was mir zu erst logisch vorkam,

laut pm2 mp2 start app.js

also habe ich versucht:
mp2 start config.js = error
mp2 start app.coffee = error
mp2 start package.json = error

habe es jetzt über ein bash Script geschrieben:
#!/bin/shnpm start

**Tim** · 20. Februar 2015

Hallo,

bitte entschuldige die etwas spätere Antwort: Du müsstest von Forever noch andere Log-Dateien haben (~/.pm2/logs), kannst du da mal rein schauen, ob du mehr Infos findest?

Gothic · 21. Februar 2015

Die sind lehr ich habe nur die logs die ich oben schon mal gepostet habe -.-

http://i.imgur.com/exQ9Cj7.png

**Tim** · 21. Februar 2015

Hallo,

das im Screenshot ist definitiv verkehrt, da hast du die config.js gestartet. Wenn es funktionieren soll, dann muss es die app.coffee. Du sagtest aber, das hättest du bereits ausprobiert und keine weiteren Logdateien. Dann kann ich an dieser Stelle nicht weiter helfen.