My Application can't be stopped #251

Closed
solisoft opened this Issue Dec 19, 2011 · 8 comments

Comments

Projects
None yet
3 participants
@solisoft

I'm trying to stop and restart my application but it don't work.

$ nodester app info
The "sys" module is now called "util". It should have a similar interface.
nodester info Gathering information about: solicms
nodester info solicms on port 13031 running: false (pid: unknown)
nodester info gitrepo: git@nodester.com:/node/git/obonnaure/4878-b1bcb4416136cd2e7e0158db7f4283ba.git
nodester info appfile: server.js

but http://solicms.nodester.com is up.

If I commit and push my code : no change.

Thank you for your help.

@chrismatthieu

This comment has been minimized.

Show comment
Hide comment
@chrismatthieu

chrismatthieu Dec 19, 2011

Collaborator

That's strange. Git push should automatically restart your application. Have you tried nodester app restart or nodester app stop and nodester app start CLI commands?

Collaborator

chrismatthieu commented Dec 19, 2011

That's strange. Git push should automatically restart your application. Have you tried nodester app restart or nodester app stop and nodester app start CLI commands?

@solisoft

This comment has been minimized.

Show comment
Hide comment
@solisoft

solisoft Dec 19, 2011

$ nodester app stop
The "sys" module is now called "util". It should have a similar interface.
nodester info Attemping to stop app: solicms
nodester info app stopped.

In fact the app is still running ...

olivier@iMac:~/workspace/solicms (master)$ nodester app start
The "sys" module is now called "util". It should have a similar interface.
nodester info Attemping to start app: solicms
nodester info app started.

$ nodester app stop
The "sys" module is now called "util". It should have a similar interface.
nodester info Attemping to stop app: solicms
nodester info app stopped.

In fact the app is still running ...

olivier@iMac:~/workspace/solicms (master)$ nodester app start
The "sys" module is now called "util". It should have a similar interface.
nodester info Attemping to start app: solicms
nodester info app started.

@contra

This comment has been minimized.

Show comment
Hide comment
@contra

contra Dec 19, 2011

Contributor

Have you tried a restart?

Contributor

contra commented Dec 19, 2011

Have you tried a restart?

@solisoft

This comment has been minimized.

Show comment
Hide comment
@solisoft

solisoft Dec 20, 2011

$ nodester app restart didn't work neither ...
I just stopped the application using : $ nodester app stop

then I do :
$ nodester app info
The "sys" module is now called "util". It should have a similar interface.
nodester info Gathering information about: solicms
nodester info solicms on port 13031 running: false (pid: unknown)
nodester info gitrepo: git@nodester.com:/node/git/obonnaure/4878-b1bcb4416136cd2e7e0158db7f4283ba.git
nodester info appfile: server.js

The app seems down ... but actually the app is up (http://solicms.nodester.com) I think that there is a problem with processes running in the background.

$ nodester app restart didn't work neither ...
I just stopped the application using : $ nodester app stop

then I do :
$ nodester app info
The "sys" module is now called "util". It should have a similar interface.
nodester info Gathering information about: solicms
nodester info solicms on port 13031 running: false (pid: unknown)
nodester info gitrepo: git@nodester.com:/node/git/obonnaure/4878-b1bcb4416136cd2e7e0158db7f4283ba.git
nodester info appfile: server.js

The app seems down ... but actually the app is up (http://solicms.nodester.com) I think that there is a problem with processes running in the background.

@chrismatthieu

This comment has been minimized.

Show comment
Hide comment
@chrismatthieu

chrismatthieu Dec 21, 2011

Collaborator

Sounds like this issue could be related to nodester running node.js 0.4.x and solisoft running 0.6.x. It looks like this error (The "sys" module is now called "util") is related to a difference in the versions of node.
http://groups.google.com/group/nodejs/browse_thread/thread/44ccefc8d9f4a5ac

Collaborator

chrismatthieu commented Dec 21, 2011

Sounds like this issue could be related to nodester running node.js 0.4.x and solisoft running 0.6.x. It looks like this error (The "sys" module is now called "util") is related to a difference in the versions of node.
http://groups.google.com/group/nodejs/browse_thread/thread/44ccefc8d9f4a5ac

@contra

This comment has been minimized.

Show comment
Hide comment
@contra

contra Dec 21, 2011

Contributor

@chrismatthieu - That's unrelated. That error is just a nuisance, the sys module is linked to util so the functionality still works as expected. The CLI needs to be updated for that to go away

Contributor

contra commented Dec 21, 2011

@chrismatthieu - That's unrelated. That error is just a nuisance, the sys module is linked to util so the functionality still works as expected. The CLI needs to be updated for that to go away

@solisoft

This comment has been minimized.

Show comment
Hide comment
@solisoft

solisoft Dec 22, 2011

For information :
$ nodester app info
The "sys" module is now called "util". It should have a similar interface.
nodester info Gathering information about: solicms
nodester info solicms on port 13031 running: false (pid: unknown)
nodester info gitrepo: git@nodester.com:/node/git/obonnaure/4878-b1bcb4416136cd2e7e0158db7f4283ba.git
nodester info appfile: server.js

but http://solicms.nodester.com/ is UP

Maybe there is a ghost process running?

For information :
$ nodester app info
The "sys" module is now called "util". It should have a similar interface.
nodester info Gathering information about: solicms
nodester info solicms on port 13031 running: false (pid: unknown)
nodester info gitrepo: git@nodester.com:/node/git/obonnaure/4878-b1bcb4416136cd2e7e0158db7f4283ba.git
nodester info appfile: server.js

but http://solicms.nodester.com/ is UP

Maybe there is a ghost process running?

@chrismatthieu

This comment has been minimized.

Show comment
Hide comment
@chrismatthieu

chrismatthieu Feb 10, 2012

Collaborator

This ticket is really old and a lot has changed on our platform. Please open a new ticket if you are still having an issue.

Collaborator

chrismatthieu commented Feb 10, 2012

This ticket is really old and a lot has changed on our platform. Please open a new ticket if you are still having an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment