Background process gets killed in ubuntu 16.04 server

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












0















I have a spring boot application and i'm running it as ROOT through this command:



mvn spring-boot:run -Drun.jvmArguments="-Xms512m -Xmx1024m" > lms_logs.log 2>&1 &


After a few hours it shutsdown with these logs statements:



011 11-01-2019 03:50:00.010 [pool-1-thread-1] INFO com.app.jobs.ScheduledJobsConfiguration.uploadScoreReports - Started uploadScoreReports job...
011 11-01-2019 03:50:37.701 [Thread-3] INFO org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext.doClose - Closing org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext@3a85bcaa: startup date [Fri Jan 11 03:27:13 UTC 2019]; root of context hierarchy
011 11-01-2019 03:50:37.704 [Thread-3] INFO org.springframework.jmx.export.annotation.AnnotationMBeanExporter.destroy - Unregistering JMX-exposed beans on shutdown
011 11-01-2019 03:50:37.705 [Thread-3] INFO org.springframework.jmx.export.annotation.AnnotationMBeanExporter.unregisterBeans - Unregistering JMX-exposed beans
011 11-01-2019 03:50:37.718 [Thread-3] INFO org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.destroy - Closing JPA EntityManagerFactory for persistence unit 'default'
011 11-01-2019 03:50:37.719 [Thread-3] INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown initiated...
011 11-01-2019 03:50:37.731 [Thread-3] INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown completed.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 23:34 min
[INFO] Finished at: 2019-01-11T03:50:37+00:00
[INFO] Final Memory: 76M/451M
[INFO] ------------------------------------------------------------------------


Why could this happen ?










share|improve this question






















  • I believe ApplicationContext.doClose indicates a controlled shutdown. Can you check if this is happening when the user who runs the mvn command logs out?

    – Haxiel
    Jan 11 at 7:30











  • Sorry, you 'started the user as root'? Can you edit the question and add the details on how you started the program? The problem might be caused by a SIGHUP being sent to the process when the user logs out.

    – Haxiel
    Jan 12 at 4:33











  • Apologies for the typo. This shouldn't have happened since i started the application as the root user and logged in as a different user. Something like this: ssh ubuntu & sudo su & start app & exit & exit

    – CodeShadow
    Jan 15 at 9:09
















0















I have a spring boot application and i'm running it as ROOT through this command:



mvn spring-boot:run -Drun.jvmArguments="-Xms512m -Xmx1024m" > lms_logs.log 2>&1 &


After a few hours it shutsdown with these logs statements:



011 11-01-2019 03:50:00.010 [pool-1-thread-1] INFO com.app.jobs.ScheduledJobsConfiguration.uploadScoreReports - Started uploadScoreReports job...
011 11-01-2019 03:50:37.701 [Thread-3] INFO org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext.doClose - Closing org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext@3a85bcaa: startup date [Fri Jan 11 03:27:13 UTC 2019]; root of context hierarchy
011 11-01-2019 03:50:37.704 [Thread-3] INFO org.springframework.jmx.export.annotation.AnnotationMBeanExporter.destroy - Unregistering JMX-exposed beans on shutdown
011 11-01-2019 03:50:37.705 [Thread-3] INFO org.springframework.jmx.export.annotation.AnnotationMBeanExporter.unregisterBeans - Unregistering JMX-exposed beans
011 11-01-2019 03:50:37.718 [Thread-3] INFO org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.destroy - Closing JPA EntityManagerFactory for persistence unit 'default'
011 11-01-2019 03:50:37.719 [Thread-3] INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown initiated...
011 11-01-2019 03:50:37.731 [Thread-3] INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown completed.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 23:34 min
[INFO] Finished at: 2019-01-11T03:50:37+00:00
[INFO] Final Memory: 76M/451M
[INFO] ------------------------------------------------------------------------


Why could this happen ?










share|improve this question






















  • I believe ApplicationContext.doClose indicates a controlled shutdown. Can you check if this is happening when the user who runs the mvn command logs out?

    – Haxiel
    Jan 11 at 7:30











  • Sorry, you 'started the user as root'? Can you edit the question and add the details on how you started the program? The problem might be caused by a SIGHUP being sent to the process when the user logs out.

    – Haxiel
    Jan 12 at 4:33











  • Apologies for the typo. This shouldn't have happened since i started the application as the root user and logged in as a different user. Something like this: ssh ubuntu & sudo su & start app & exit & exit

    – CodeShadow
    Jan 15 at 9:09














0












0








0








I have a spring boot application and i'm running it as ROOT through this command:



mvn spring-boot:run -Drun.jvmArguments="-Xms512m -Xmx1024m" > lms_logs.log 2>&1 &


After a few hours it shutsdown with these logs statements:



011 11-01-2019 03:50:00.010 [pool-1-thread-1] INFO com.app.jobs.ScheduledJobsConfiguration.uploadScoreReports - Started uploadScoreReports job...
011 11-01-2019 03:50:37.701 [Thread-3] INFO org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext.doClose - Closing org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext@3a85bcaa: startup date [Fri Jan 11 03:27:13 UTC 2019]; root of context hierarchy
011 11-01-2019 03:50:37.704 [Thread-3] INFO org.springframework.jmx.export.annotation.AnnotationMBeanExporter.destroy - Unregistering JMX-exposed beans on shutdown
011 11-01-2019 03:50:37.705 [Thread-3] INFO org.springframework.jmx.export.annotation.AnnotationMBeanExporter.unregisterBeans - Unregistering JMX-exposed beans
011 11-01-2019 03:50:37.718 [Thread-3] INFO org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.destroy - Closing JPA EntityManagerFactory for persistence unit 'default'
011 11-01-2019 03:50:37.719 [Thread-3] INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown initiated...
011 11-01-2019 03:50:37.731 [Thread-3] INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown completed.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 23:34 min
[INFO] Finished at: 2019-01-11T03:50:37+00:00
[INFO] Final Memory: 76M/451M
[INFO] ------------------------------------------------------------------------


Why could this happen ?










share|improve this question














I have a spring boot application and i'm running it as ROOT through this command:



mvn spring-boot:run -Drun.jvmArguments="-Xms512m -Xmx1024m" > lms_logs.log 2>&1 &


After a few hours it shutsdown with these logs statements:



011 11-01-2019 03:50:00.010 [pool-1-thread-1] INFO com.app.jobs.ScheduledJobsConfiguration.uploadScoreReports - Started uploadScoreReports job...
011 11-01-2019 03:50:37.701 [Thread-3] INFO org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext.doClose - Closing org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext@3a85bcaa: startup date [Fri Jan 11 03:27:13 UTC 2019]; root of context hierarchy
011 11-01-2019 03:50:37.704 [Thread-3] INFO org.springframework.jmx.export.annotation.AnnotationMBeanExporter.destroy - Unregistering JMX-exposed beans on shutdown
011 11-01-2019 03:50:37.705 [Thread-3] INFO org.springframework.jmx.export.annotation.AnnotationMBeanExporter.unregisterBeans - Unregistering JMX-exposed beans
011 11-01-2019 03:50:37.718 [Thread-3] INFO org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.destroy - Closing JPA EntityManagerFactory for persistence unit 'default'
011 11-01-2019 03:50:37.719 [Thread-3] INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown initiated...
011 11-01-2019 03:50:37.731 [Thread-3] INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown completed.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 23:34 min
[INFO] Finished at: 2019-01-11T03:50:37+00:00
[INFO] Final Memory: 76M/451M
[INFO] ------------------------------------------------------------------------


Why could this happen ?







ubuntu process kill webserver






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 11 at 4:52









CodeShadowCodeShadow

1012




1012












  • I believe ApplicationContext.doClose indicates a controlled shutdown. Can you check if this is happening when the user who runs the mvn command logs out?

    – Haxiel
    Jan 11 at 7:30











  • Sorry, you 'started the user as root'? Can you edit the question and add the details on how you started the program? The problem might be caused by a SIGHUP being sent to the process when the user logs out.

    – Haxiel
    Jan 12 at 4:33











  • Apologies for the typo. This shouldn't have happened since i started the application as the root user and logged in as a different user. Something like this: ssh ubuntu & sudo su & start app & exit & exit

    – CodeShadow
    Jan 15 at 9:09


















  • I believe ApplicationContext.doClose indicates a controlled shutdown. Can you check if this is happening when the user who runs the mvn command logs out?

    – Haxiel
    Jan 11 at 7:30











  • Sorry, you 'started the user as root'? Can you edit the question and add the details on how you started the program? The problem might be caused by a SIGHUP being sent to the process when the user logs out.

    – Haxiel
    Jan 12 at 4:33











  • Apologies for the typo. This shouldn't have happened since i started the application as the root user and logged in as a different user. Something like this: ssh ubuntu & sudo su & start app & exit & exit

    – CodeShadow
    Jan 15 at 9:09

















I believe ApplicationContext.doClose indicates a controlled shutdown. Can you check if this is happening when the user who runs the mvn command logs out?

– Haxiel
Jan 11 at 7:30





I believe ApplicationContext.doClose indicates a controlled shutdown. Can you check if this is happening when the user who runs the mvn command logs out?

– Haxiel
Jan 11 at 7:30













Sorry, you 'started the user as root'? Can you edit the question and add the details on how you started the program? The problem might be caused by a SIGHUP being sent to the process when the user logs out.

– Haxiel
Jan 12 at 4:33





Sorry, you 'started the user as root'? Can you edit the question and add the details on how you started the program? The problem might be caused by a SIGHUP being sent to the process when the user logs out.

– Haxiel
Jan 12 at 4:33













Apologies for the typo. This shouldn't have happened since i started the application as the root user and logged in as a different user. Something like this: ssh ubuntu & sudo su & start app & exit & exit

– CodeShadow
Jan 15 at 9:09






Apologies for the typo. This shouldn't have happened since i started the application as the root user and logged in as a different user. Something like this: ssh ubuntu & sudo su & start app & exit & exit

– CodeShadow
Jan 15 at 9:09











0






active

oldest

votes











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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
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%2f493865%2fbackground-process-gets-killed-in-ubuntu-16-04-server%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493865%2fbackground-process-gets-killed-in-ubuntu-16-04-server%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

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

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay