Skip to content

Process doesn't know whether it's running or not: reports inconsistent results #40

Open
@danwdart

Description

@danwdart

$ grunt start
Running "forever:server:start" (forever) task
Attempting to start app/server.js as daemon.
Warning: app/server.js is already running. Use --force to continue.

$ grunt restart
Running "forever:server:stop" (forever) task
Attempting to stop app/server.js...
uid command script forever pid id logfile uptime
[0] 6jyh /usr/bin/nodejs app/server.js 26268 26397 /home/kvd/www/code/pcomm/logs/forever.out STOPPED

Error stopping app/server.js. [REASON] :: Error: Cannot stop process that is not running.
ERROR
Warning: Task "forever:server:stop" failed. Use --force to continue.

Can it please make up its mind?

Activity

changed the title State conflicts Process doesn't know whether it's running or not: reports inconsistent results on Mar 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Process doesn't know whether it's running or not: reports inconsistent results · Issue #40 · bustardcelly/grunt-forever