如何在Windows上使用forever模块停止Node.js应用程序？

Question

关于nodejs APP的永久模块，我经历了很多问题，但没有找到答案。

Forever模块在​​Linux机器上工作正常，但现在我将我的APP放在Windows 7上并试图永远运行它。 首先，我将永久模块安装为

npm install forever -g

之后我将我的应用程序作为

运行

forever start app.js

通过说文件app.js永远运行并且我正在成功访问我的应用程序，它运行正常。

当我执行命令forever stop app.js时，我收到错误

  

没有永远正在运行的文件

如果有人在Windows上永远使用过，我建议我如何在Windows上停止我的应用程序。

Answer 1

使用forever list 然后永远停止与id，例如forever stop 0

这是一个示例输出

user@some-server]$ forever list
info:    Forever processes running
data:        uid  command                                                  script forever pid   id logfile                          uptime        
data:    [0] 9Xzw ng serve --host 0.0.0.0 --port 4009         13164   29579    /home/ec2-user/.forever/9Xzw.log 7:1:20:50.412 
data:    [1] wOj1 npm run-script app-start-dev                                    29500   24978    /home/ec2-user/.forever/wOj1.log 0:0:5:3.433

这里0就像一个索引，它位于输出的第一列。如果有两个进程在运行，我们可以使用0或1之类的索引来停止第一个或第二个进程。

forever stop 0或forever stop 1

Answer 2

我遇到了同样的问题，发现这是因为我一直在运行sudo（在Linux上），所以我可以在端口80上运行一个生产站点。这就是诀窍：

sudo forever list

Answer 3

这是Windows https://github.com/nodejitsu/forever/issues/337中的一个错误 如果您需要停止您的应用程序，只需打开任务管理器并找到node.js进程并将其终止。努力工作。

Answer 4

这只是为了扩展@ laktak的答案。 Windows上forever list的结果如下所示：

info:    Forever processes running
data:        uid  command              script                          forever p
id   id logfile                               uptime
data:    [0] an1b "C:\nodejs\node.exe" C:\sbSerialWidget\server.js 8780    1
0152    C:\Users\username\.forever\an1b.log STOPPED

我不确定最初是哪一个ID，但我发现它是上面第二个data字段之后的第一个条目，所以你感兴趣的行是ID加粗和放大器;斜体：

数据： [0] an1b C:\nodejs\node.exe C:\sbSerialWidget\server.js 8780 1 0152 C：\ Users \ username.forever \ an1b.log STOPPED

因此，要停止此特定实例，请运行：

forever stop 0

希望这可以帮助像我一样感到困惑的其他人

Answer 5

您可以遵循永久文档，那里有与永久相关的所有命令。

Forever

 $ forever --help
      usage: forever [action] [options] SCRIPT [script-options]
    
      Monitors the script specified in the current process or as a daemon
    
      actions:
        start               Start SCRIPT as a daemon
        stop                Stop the daemon SCRIPT by Id|Uid|Pid|Index|Script
        stopall             Stop all running forever scripts
        restart             Restart the daemon SCRIPT
        restartall          Restart all running forever scripts
        list                List all running forever scripts
        config              Lists all forever user configuration
        set <key> <val>     Sets the specified forever config <key>
        clear <key>         Clears the specified forever config <key>
        logs                Lists log files for all forever processes
        logs <script|index> Tails the logs for <script|index>
        columns add <col>   Adds the specified column to the output in `forever list`. Supported columns: 'uid', 'command', 'script', 'forever', 'pid', 'id', 'logfile', 'uptime'
        columns rm <col>    Removed the specified column from the output in `forever list`
        columns set <cols>  Set all columns for the output in `forever list`
        cleanlogs           [CAREFUL] Deletes all historical forever log files

  options:
    -m  MAX          Only run the specified script MAX times
    -l  LOGFILE      Logs the forever output to LOGFILE
    -o  OUTFILE      Logs stdout from child script to OUTFILE
    -e  ERRFILE      Logs stderr from child script to ERRFILE
    -p  PATH         Base path for all forever related files (pid files, etc.)
    -c  COMMAND      COMMAND to execute (defaults to node)
    -a, --append     Append logs
    -f, --fifo       Stream logs to stdout
    -n, --number     Number of log lines to print
    --pidFile        The pid file
    --uid            DEPRECATED. Process uid, useful as a namespace for processes (must wrap in a string)
                     e.g. forever start --uid "production" app.js
                         forever stop production
    --id             DEPRECATED. Process id, similar to uid, useful as a namespace for processes (must wrap in a string)
                     e.g. forever start --id "test" app.js
                         forever stop test
    --sourceDir      The source directory for which SCRIPT is relative to
    --workingDir     The working directory in which SCRIPT will execute
    --minUptime      Minimum uptime (millis) for a script to not be considered "spinning"
    --spinSleepTime  Time to wait (millis) between launches of a spinning script.
    --colors         --no-colors will disable output coloring
    --plain          Disable command line colors
    -d, --debug      Forces forever to log debug output
    -v, --verbose    Turns on the verbose messages from Forever
    -s, --silent     Run the child script silencing stdout and stderr
    -w, --watch      Watch for file changes
    --watchDirectory Top-level directory to watch from
    --watchIgnore    To ignore pattern when watch is enabled (multiple option is allowed)
    -t, --killTree   Kills the entire child process tree on `stop`
    --killSignal     Support exit signal customization (default is SIGKILL),
                     used for restarting script gracefully e.g. --killSignal=SIGTERM
                     Any console output generated after calling `forever stop/stopall` will not appear in the logs
    -h, --help       You're staring at it

  [Long Running Process]
    The forever process will continue to run outputting log messages to the console.
    ex. forever -o out.log -e err.log my-script.js

  [Daemon]
    The forever process will run as a daemon which will make the target process start
    in the background. This is extremely useful for remote starting simple node.js scripts
    without using nohup. It is recommended to run start with -o -l, & -e.
    ex. forever start -l forever.log -o out.log -e err.log my-daemon.js
        forever stop my-daemon.js

Answer 6

永远停止0

其中0是运行的应用程序的索引，如果只有一个，则为0。