If creation of ~/.forever fails, no error but CLI stops working (i.e. forever list says "No forever processes running")

[tjunnone]

If ~/.forever cannot be created while starting as a daemon (and it always tries to, see issue #414), the daemon still starts and everything looks OK and there's nothing to indicate the failure in the logs.

After this however, "forever list" will give: "No forever processes running".
"forever stop" will give: "Forever cannot find process with index: myScript"

I noticed this because when I start Forever from a init script, there's no HOME environment and it tries to write to /root/.forever which it doesn't have permissions for. In addition to obeying the -p parameter, I think there should be an error in the log and perhaps the daemon should even fail to start since it becomes uncontrollable from the cli.

[indexzero]

This feels like a duplicate of #544 and may be related to the root cause of all the empty log files.

[indexzero]

Duplicate of #483.

[xprt64]

I had the same issue: I added an init script that started a node.js application with PM2 but pm2 list showed no application running although ps aux | grep node listed the process correctly.
The solution in my case was to start the init script AFTER the network; I think the sockets were needed for communication between pm2 instances .
This is my working init script (notice $network at Required-Start line):

#! /usr/bin/php
<?php
#
### BEGIN INIT INFO
# Provides:          crm
# Required-Start:    $remote_fs $syslog $network $mysql $apache2 $cron $pm2
# Required-Stop:     $remote_fs $syslog $network $mysql $apache2 $cron $pm2
# Should-Start:      $network $time
# Should-Stop:       $network $time
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description:  blah blah blah
# Description:       blah blah blah 
### END INIT INFO
#


require 'startup.php';

[swapnilgt]

Any solutions for this yet?

[JulianNorton]

3 years later, still an issue.

[petercunha]

Please fix this...

[meherchandan]

Any update on this one? I am still facing this issue

[kibertoad]

Will check it today, sorry!

[kibertoad]

@meherchandan @tjunnone @petercunha Please review #1017

[petercunha]

Thank you! @kibertoad

[kibertoad]

New version is out with a fix!

[kentaguilar]

A fix would be great for this.
Encountered this one as well.
What I could recommend for now is to find the process that's using your node port e.g. 3000. Like so,
sudo lsof -t -i:3000

That command will show the process id. Then perform,

kill PID