Why nohup background process is getting killed?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
8
down vote

favorite
2












I tried starting a shell script via a remote session, which starts a process in the background using the command.



nohup python3 run.py > nohup.out &


When the remote session is closed, the process is getting killed with the message:




Caught signal SIGHUP



SIGHUP caught but not daemonized. Exiting.




I don't understand; why is the process getting killed when it was started in background using nohup &?




background-process nohup




share|improve this question

















  • 1




    I used to be confused by all the unexpected behavior of shell job control. Now I just use tmux and ignore nohup or disown or background task completely.
    – Siyuan Ren
    May 29 at 13:30














up vote
8
down vote

favorite
2












I tried starting a shell script via a remote session, which starts a process in the background using the command.



nohup python3 run.py > nohup.out &


When the remote session is closed, the process is getting killed with the message:




Caught signal SIGHUP



SIGHUP caught but not daemonized. Exiting.




I don't understand; why is the process getting killed when it was started in background using nohup &?




background-process nohup




share|improve this question

















  • 1




    I used to be confused by all the unexpected behavior of shell job control. Now I just use tmux and ignore nohup or disown or background task completely.
    – Siyuan Ren
    May 29 at 13:30












up vote
8
down vote

favorite
2









up vote
8
down vote

favorite
2






2





I tried starting a shell script via a remote session, which starts a process in the background using the command.



nohup python3 run.py > nohup.out &


When the remote session is closed, the process is getting killed with the message:




Caught signal SIGHUP



SIGHUP caught but not daemonized. Exiting.




I don't understand; why is the process getting killed when it was started in background using nohup &?




background-process nohup




share|improve this question













I tried starting a shell script via a remote session, which starts a process in the background using the command.



nohup python3 run.py > nohup.out &


When the remote session is closed, the process is getting killed with the message:




Caught signal SIGHUP



SIGHUP caught but not daemonized. Exiting.




I don't understand; why is the process getting killed when it was started in background using nohup &?





background-process nohup





share|improve this question












share|improve this question




share|improve this question








edited Jun 3 at 11:14









Jeff Schaller

31k846105




31k846105









asked May 29 at 7:25









Mostwanted Mani

1456




1456







  • 1




    I used to be confused by all the unexpected behavior of shell job control. Now I just use tmux and ignore nohup or disown or background task completely.
    – Siyuan Ren
    May 29 at 13:30












  • 1




    I used to be confused by all the unexpected behavior of shell job control. Now I just use tmux and ignore nohup or disown or background task completely.
    – Siyuan Ren
    May 29 at 13:30







1




1




I used to be confused by all the unexpected behavior of shell job control. Now I just use tmux and ignore nohup or disown or background task completely.
– Siyuan Ren
May 29 at 13:30




I used to be confused by all the unexpected behavior of shell job control. Now I just use tmux and ignore nohup or disown or background task completely.
– Siyuan Ren
May 29 at 13:30










1 Answer
1






active

oldest

votes

















up vote
10
down vote



accepted










Your Python program undoes nohup.



nohup ignores the hangup signal with SIG_IGN and then chain loads your program in the same process.



Your Python program promptly resets the signal handling for the hangup signal, installing its own signal handler. That handler checks an internal function (that is not designed very well, being based upon some flawed assumptions, if it is the one that I have seen) and decides that the appropriate course of action on receipt of a hangup signal is to print that message and exit.



Your Python program by design is not nohup-able. On a system with a job control shell and POSIX session/job semantics, you need to be disowning the job so that the shell never knows about it to send a hangup signal to it in the first place.



(Even that is not enough on systemd operating systems. Because the systemd people have made a bit of a pig's ear of their user-space login session mechanism, you also need to ensure that systemd's mechanism that signals system shutdown, rather than hangup, to login sessions at every logout is also not kicking in.)



Further reading



  • https://docs.cherrypy.org/en/latest/_modules/cherrypy/process/plugins.html

  • Does nohup try to arrange for the program not to have a controlling terminal?

  • Difference between nohup, disown and &

  • When tmux exits (closes pty master), background processes from startup scripts die — why?

  • https://unix.stackexchange.com/a/310775/5132

  • https://unix.stackexchange.com/a/379264/5132





share|improve this answer



















  • 3




    Is it their Python program that does it, or is it the Python interpreter (/run-time environment) that does it silently behind their back?
    – ilkkachu
    May 29 at 8:29










  • Also, on Mac OS, logging out from an ssh session kills you shell jobs, even when started using nohup; haven't found a remedy for it
    – imhotap
    May 29 at 9:47










  • Well, if the problem is the signal handler the OP could simply change the signal handler to an handler that does not kill the process. This should work independently of who installs such signal handler. I'd like to add regarding ssh: sometimes, even if the process is kept alive, it might have troubles. A couple years ago I lost quite some time trying to understand some permission errors and, in the end, the culprit was Kerberos: when the ssh session was closed the tokens were expired, so I had to create new tokens to be used instead of those of the ssh session.
    – Bakuriu
    May 29 at 12:14










  • @JdeBP I tried setsid nohup python3 run.py > nohup.out &, setsid has resolved this issue. Is this a proper approach?
    – Mostwanted Mani
    Jun 1 at 13:45










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446625%2fwhy-nohup-background-process-is-getting-killed%23new-answer', 'question_page');

);

Post as a guest

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
10
down vote



accepted










Your Python program undoes nohup.



nohup ignores the hangup signal with SIG_IGN and then chain loads your program in the same process.



Your Python program promptly resets the signal handling for the hangup signal, installing its own signal handler. That handler checks an internal function (that is not designed very well, being based upon some flawed assumptions, if it is the one that I have seen) and decides that the appropriate course of action on receipt of a hangup signal is to print that message and exit.



Your Python program by design is not nohup-able. On a system with a job control shell and POSIX session/job semantics, you need to be disowning the job so that the shell never knows about it to send a hangup signal to it in the first place.



(Even that is not enough on systemd operating systems. Because the systemd people have made a bit of a pig's ear of their user-space login session mechanism, you also need to ensure that systemd's mechanism that signals system shutdown, rather than hangup, to login sessions at every logout is also not kicking in.)



Further reading



  • https://docs.cherrypy.org/en/latest/_modules/cherrypy/process/plugins.html

  • Does nohup try to arrange for the program not to have a controlling terminal?

  • Difference between nohup, disown and &

  • When tmux exits (closes pty master), background processes from startup scripts die — why?

  • https://unix.stackexchange.com/a/310775/5132

  • https://unix.stackexchange.com/a/379264/5132





share|improve this answer



















  • 3




    Is it their Python program that does it, or is it the Python interpreter (/run-time environment) that does it silently behind their back?
    – ilkkachu
    May 29 at 8:29










  • Also, on Mac OS, logging out from an ssh session kills you shell jobs, even when started using nohup; haven't found a remedy for it
    – imhotap
    May 29 at 9:47










  • Well, if the problem is the signal handler the OP could simply change the signal handler to an handler that does not kill the process. This should work independently of who installs such signal handler. I'd like to add regarding ssh: sometimes, even if the process is kept alive, it might have troubles. A couple years ago I lost quite some time trying to understand some permission errors and, in the end, the culprit was Kerberos: when the ssh session was closed the tokens were expired, so I had to create new tokens to be used instead of those of the ssh session.
    – Bakuriu
    May 29 at 12:14










  • @JdeBP I tried setsid nohup python3 run.py > nohup.out &, setsid has resolved this issue. Is this a proper approach?
    – Mostwanted Mani
    Jun 1 at 13:45














up vote
10
down vote



accepted










Your Python program undoes nohup.



nohup ignores the hangup signal with SIG_IGN and then chain loads your program in the same process.



Your Python program promptly resets the signal handling for the hangup signal, installing its own signal handler. That handler checks an internal function (that is not designed very well, being based upon some flawed assumptions, if it is the one that I have seen) and decides that the appropriate course of action on receipt of a hangup signal is to print that message and exit.



Your Python program by design is not nohup-able. On a system with a job control shell and POSIX session/job semantics, you need to be disowning the job so that the shell never knows about it to send a hangup signal to it in the first place.



(Even that is not enough on systemd operating systems. Because the systemd people have made a bit of a pig's ear of their user-space login session mechanism, you also need to ensure that systemd's mechanism that signals system shutdown, rather than hangup, to login sessions at every logout is also not kicking in.)



Further reading



  • https://docs.cherrypy.org/en/latest/_modules/cherrypy/process/plugins.html

  • Does nohup try to arrange for the program not to have a controlling terminal?

  • Difference between nohup, disown and &

  • When tmux exits (closes pty master), background processes from startup scripts die — why?

  • https://unix.stackexchange.com/a/310775/5132

  • https://unix.stackexchange.com/a/379264/5132





share|improve this answer



















  • 3




    Is it their Python program that does it, or is it the Python interpreter (/run-time environment) that does it silently behind their back?
    – ilkkachu
    May 29 at 8:29










  • Also, on Mac OS, logging out from an ssh session kills you shell jobs, even when started using nohup; haven't found a remedy for it
    – imhotap
    May 29 at 9:47










  • Well, if the problem is the signal handler the OP could simply change the signal handler to an handler that does not kill the process. This should work independently of who installs such signal handler. I'd like to add regarding ssh: sometimes, even if the process is kept alive, it might have troubles. A couple years ago I lost quite some time trying to understand some permission errors and, in the end, the culprit was Kerberos: when the ssh session was closed the tokens were expired, so I had to create new tokens to be used instead of those of the ssh session.
    – Bakuriu
    May 29 at 12:14










  • @JdeBP I tried setsid nohup python3 run.py > nohup.out &, setsid has resolved this issue. Is this a proper approach?
    – Mostwanted Mani
    Jun 1 at 13:45












up vote
10
down vote



accepted







up vote
10
down vote



accepted






Your Python program undoes nohup.



nohup ignores the hangup signal with SIG_IGN and then chain loads your program in the same process.



Your Python program promptly resets the signal handling for the hangup signal, installing its own signal handler. That handler checks an internal function (that is not designed very well, being based upon some flawed assumptions, if it is the one that I have seen) and decides that the appropriate course of action on receipt of a hangup signal is to print that message and exit.



Your Python program by design is not nohup-able. On a system with a job control shell and POSIX session/job semantics, you need to be disowning the job so that the shell never knows about it to send a hangup signal to it in the first place.



(Even that is not enough on systemd operating systems. Because the systemd people have made a bit of a pig's ear of their user-space login session mechanism, you also need to ensure that systemd's mechanism that signals system shutdown, rather than hangup, to login sessions at every logout is also not kicking in.)



Further reading



  • https://docs.cherrypy.org/en/latest/_modules/cherrypy/process/plugins.html

  • Does nohup try to arrange for the program not to have a controlling terminal?

  • Difference between nohup, disown and &

  • When tmux exits (closes pty master), background processes from startup scripts die — why?

  • https://unix.stackexchange.com/a/310775/5132

  • https://unix.stackexchange.com/a/379264/5132





share|improve this answer















Your Python program undoes nohup.



nohup ignores the hangup signal with SIG_IGN and then chain loads your program in the same process.



Your Python program promptly resets the signal handling for the hangup signal, installing its own signal handler. That handler checks an internal function (that is not designed very well, being based upon some flawed assumptions, if it is the one that I have seen) and decides that the appropriate course of action on receipt of a hangup signal is to print that message and exit.



Your Python program by design is not nohup-able. On a system with a job control shell and POSIX session/job semantics, you need to be disowning the job so that the shell never knows about it to send a hangup signal to it in the first place.



(Even that is not enough on systemd operating systems. Because the systemd people have made a bit of a pig's ear of their user-space login session mechanism, you also need to ensure that systemd's mechanism that signals system shutdown, rather than hangup, to login sessions at every logout is also not kicking in.)



Further reading



  • https://docs.cherrypy.org/en/latest/_modules/cherrypy/process/plugins.html

  • Does nohup try to arrange for the program not to have a controlling terminal?

  • Difference between nohup, disown and &

  • When tmux exits (closes pty master), background processes from startup scripts die — why?

  • https://unix.stackexchange.com/a/310775/5132

  • https://unix.stackexchange.com/a/379264/5132






share|improve this answer















share|improve this answer



share|improve this answer








edited May 29 at 8:35


























answered May 29 at 8:21









JdeBP

28k459133




28k459133







  • 3




    Is it their Python program that does it, or is it the Python interpreter (/run-time environment) that does it silently behind their back?
    – ilkkachu
    May 29 at 8:29










  • Also, on Mac OS, logging out from an ssh session kills you shell jobs, even when started using nohup; haven't found a remedy for it
    – imhotap
    May 29 at 9:47










  • Well, if the problem is the signal handler the OP could simply change the signal handler to an handler that does not kill the process. This should work independently of who installs such signal handler. I'd like to add regarding ssh: sometimes, even if the process is kept alive, it might have troubles. A couple years ago I lost quite some time trying to understand some permission errors and, in the end, the culprit was Kerberos: when the ssh session was closed the tokens were expired, so I had to create new tokens to be used instead of those of the ssh session.
    – Bakuriu
    May 29 at 12:14










  • @JdeBP I tried setsid nohup python3 run.py > nohup.out &, setsid has resolved this issue. Is this a proper approach?
    – Mostwanted Mani
    Jun 1 at 13:45












  • 3




    Is it their Python program that does it, or is it the Python interpreter (/run-time environment) that does it silently behind their back?
    – ilkkachu
    May 29 at 8:29










  • Also, on Mac OS, logging out from an ssh session kills you shell jobs, even when started using nohup; haven't found a remedy for it
    – imhotap
    May 29 at 9:47










  • Well, if the problem is the signal handler the OP could simply change the signal handler to an handler that does not kill the process. This should work independently of who installs such signal handler. I'd like to add regarding ssh: sometimes, even if the process is kept alive, it might have troubles. A couple years ago I lost quite some time trying to understand some permission errors and, in the end, the culprit was Kerberos: when the ssh session was closed the tokens were expired, so I had to create new tokens to be used instead of those of the ssh session.
    – Bakuriu
    May 29 at 12:14










  • @JdeBP I tried setsid nohup python3 run.py > nohup.out &, setsid has resolved this issue. Is this a proper approach?
    – Mostwanted Mani
    Jun 1 at 13:45







3




3




Is it their Python program that does it, or is it the Python interpreter (/run-time environment) that does it silently behind their back?
– ilkkachu
May 29 at 8:29




Is it their Python program that does it, or is it the Python interpreter (/run-time environment) that does it silently behind their back?
– ilkkachu
May 29 at 8:29












Also, on Mac OS, logging out from an ssh session kills you shell jobs, even when started using nohup; haven't found a remedy for it
– imhotap
May 29 at 9:47




Also, on Mac OS, logging out from an ssh session kills you shell jobs, even when started using nohup; haven't found a remedy for it
– imhotap
May 29 at 9:47












Well, if the problem is the signal handler the OP could simply change the signal handler to an handler that does not kill the process. This should work independently of who installs such signal handler. I'd like to add regarding ssh: sometimes, even if the process is kept alive, it might have troubles. A couple years ago I lost quite some time trying to understand some permission errors and, in the end, the culprit was Kerberos: when the ssh session was closed the tokens were expired, so I had to create new tokens to be used instead of those of the ssh session.
– Bakuriu
May 29 at 12:14




Well, if the problem is the signal handler the OP could simply change the signal handler to an handler that does not kill the process. This should work independently of who installs such signal handler. I'd like to add regarding ssh: sometimes, even if the process is kept alive, it might have troubles. A couple years ago I lost quite some time trying to understand some permission errors and, in the end, the culprit was Kerberos: when the ssh session was closed the tokens were expired, so I had to create new tokens to be used instead of those of the ssh session.
– Bakuriu
May 29 at 12:14












@JdeBP I tried setsid nohup python3 run.py > nohup.out &, setsid has resolved this issue. Is this a proper approach?
– Mostwanted Mani
Jun 1 at 13:45




@JdeBP I tried setsid nohup python3 run.py > nohup.out &, setsid has resolved this issue. Is this a proper approach?
– Mostwanted Mani
Jun 1 at 13:45












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446625%2fwhy-nohup-background-process-is-getting-killed%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more