-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nodemon cannot run in background with nohup? #296
Comments
Is killed, as in, dies? Or does it linger, then restart? I could do with a bit more information. Perhaps some help debugging? |
I run nodemon, everything is fine as below.
But nohup not work.
Here is the log of nohup.out
On Wed, Feb 19, 2014 at 4:48 AM, Remy Sharp notifications@github.comwrote:
|
I'm also facing the same issue. I tried to run nodemon in verbose mode but it didn't help much. Here's what happens when I try to run nodemon with nohup : work: [1] + exit 1 nohup nodemon --verbose serve.js work: If appropriate, please file an error: http://github.com/remy/nodemon/issues/new 5 Mar 04:27:30 - [nodemon] exiting |
Can someone run the exact same command, but add |
|
-bash-4.1# cat nohup.out
|
I had same issue. Here is my work around
Then execute the script with nohup
|
Cheers for the tip. I've not had a chance to play with this yet (am on On Tuesday, May 6, 2014, Sriraman notifications@github.com wrote:
— Remy |
@sparkit noop, the ways produce the same error... |
this may be help: details: #98 |
I have same problem, how can make it work, please help |
@nvcken |
I has try nohup nodemon </dev/null & 8 Jul 15:00:57 - �[33m[nodemon] v1.2.0�[39m |
@sparkit 8 Jul 15:06:49 - �[33m[nodemon] v1.2.0�[39m If appropriate, please file an error with the output from: At http://github.com/remy/nodemon/issues/new |
@sparkit |
Have added permission +x for exec.sh ? |
I has added +x permission for exec.sh. |
Will look something like On Tue, Jul 8, 2014 at 1:48 PM, nvcken notifications@github.com wrote:
|
I get nohup nodemon work, now. 8 Jul 15:39:02 - �[32m[nodemon] restarting due to changes...�[39m I lookup grep node, has a node process with listening port 35729 running. |
Could you please paste here a) nohup command you are running Thanks On Tue, Jul 8, 2014 at 2:15 PM, nvcken notifications@github.com wrote:
|
I use only command below Thanks |
I added an issue to nodejs, because I was having the same issue when binding to stdin. It might be related this issue, too. @remy I bet if you remove these lines, it will work without issues using nohup :) https://github.com/remy/nodemon/blob/master/lib/nodemon.js#L106 |
nohup nodemon app.js </dev/null & |
nohup nodemon app.js </dev/null & |
i can put it to background, but after close ssh connection, nodemon stopped, because after connecet to ssh again i dont have any package on background
|
Another possible solution:
The -I switch prevents nodemon from attempting to use STDIN, which isn't allowed under nohup as there's no input stream. |
|
@barraponto please use |
This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up. |
@leoliaolei you can use nodemon with |
@remy Feel free to close this issue, the |
I've got an faq item to merge, so I'll add this to the FAQ too. 👍 |
For those trying to use it (I don't have the -I switch yet on the version I installed), you can also try with the command "screen" if your distribution has it (AWS has it), it opens a deattached shell which wont die even if your ssh dies (plus you can recover it later) |
thanks this is work for me |
I use
nohup nodemon server.js &
. It seems nodemon is killed soon.The text was updated successfully, but these errors were encountered: