Ubuntu machine randomly reboots [closed]

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












3















I have a Ubuntu machine which randomly reboots itself:



last reboot
reboot system boot 2.6.32-042stab12 Sat Mar 25 23:48 - 12:42 (11:53)
reboot system boot 2.6.32-042stab12 Wed Mar 22 18:28 - 12:42 (3+17:14)
reboot system boot 2.6.32-042stab12 Sat Mar 18 05:10 - 12:42 (8+06:32)
reboot system boot 2.6.32-042stab12 Thu Mar 16 13:52 - 12:42 (9+21:49)
reboot system boot 2.6.32-042stab12 Thu Mar 16 09:50 - 13:52 (04:02)


I am trying to figure out why and stop it. I pasted the logs to pastebin here.



I am not doing these reboots. Also, it seems like there is nothing going on (like a crash, etc.) which would cause the server to reboot.










share|improve this question















closed as too broad by RalfFriedl, nwildner, msp9011, Fabby, Shadur Jan 10 at 12:35


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.















  • @Vlastimil No I don't have physical access, just SSH. And I have no idea what -- MARK -- is.

    – thesys
    Mar 26 '17 at 11:01











  • I just read somewhere else: "The --MARK-- messages are added at regular intervals just to indicate that syslogd is still working, even when no other messages are added. "

    – thesys
    Mar 26 '17 at 11:04











  • @Vlastimil I created a pastebin. If you require more logs just tell me which.

    – thesys
    Mar 26 '17 at 11:14






  • 1





    There's nothing in the logs. Is it a multiuser system and someone else reboots it?

    – Jan
    Mar 26 '17 at 11:28











  • did you deploy the unattended-updates service and allow it to reboot after updates if it was required by an update?

    – Phillip -Zyan K Lee- Stockmann
    Mar 26 '17 at 11:29















3















I have a Ubuntu machine which randomly reboots itself:



last reboot
reboot system boot 2.6.32-042stab12 Sat Mar 25 23:48 - 12:42 (11:53)
reboot system boot 2.6.32-042stab12 Wed Mar 22 18:28 - 12:42 (3+17:14)
reboot system boot 2.6.32-042stab12 Sat Mar 18 05:10 - 12:42 (8+06:32)
reboot system boot 2.6.32-042stab12 Thu Mar 16 13:52 - 12:42 (9+21:49)
reboot system boot 2.6.32-042stab12 Thu Mar 16 09:50 - 13:52 (04:02)


I am trying to figure out why and stop it. I pasted the logs to pastebin here.



I am not doing these reboots. Also, it seems like there is nothing going on (like a crash, etc.) which would cause the server to reboot.










share|improve this question















closed as too broad by RalfFriedl, nwildner, msp9011, Fabby, Shadur Jan 10 at 12:35


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.















  • @Vlastimil No I don't have physical access, just SSH. And I have no idea what -- MARK -- is.

    – thesys
    Mar 26 '17 at 11:01











  • I just read somewhere else: "The --MARK-- messages are added at regular intervals just to indicate that syslogd is still working, even when no other messages are added. "

    – thesys
    Mar 26 '17 at 11:04











  • @Vlastimil I created a pastebin. If you require more logs just tell me which.

    – thesys
    Mar 26 '17 at 11:14






  • 1





    There's nothing in the logs. Is it a multiuser system and someone else reboots it?

    – Jan
    Mar 26 '17 at 11:28











  • did you deploy the unattended-updates service and allow it to reboot after updates if it was required by an update?

    – Phillip -Zyan K Lee- Stockmann
    Mar 26 '17 at 11:29













3












3








3








I have a Ubuntu machine which randomly reboots itself:



last reboot
reboot system boot 2.6.32-042stab12 Sat Mar 25 23:48 - 12:42 (11:53)
reboot system boot 2.6.32-042stab12 Wed Mar 22 18:28 - 12:42 (3+17:14)
reboot system boot 2.6.32-042stab12 Sat Mar 18 05:10 - 12:42 (8+06:32)
reboot system boot 2.6.32-042stab12 Thu Mar 16 13:52 - 12:42 (9+21:49)
reboot system boot 2.6.32-042stab12 Thu Mar 16 09:50 - 13:52 (04:02)


I am trying to figure out why and stop it. I pasted the logs to pastebin here.



I am not doing these reboots. Also, it seems like there is nothing going on (like a crash, etc.) which would cause the server to reboot.










share|improve this question
















I have a Ubuntu machine which randomly reboots itself:



last reboot
reboot system boot 2.6.32-042stab12 Sat Mar 25 23:48 - 12:42 (11:53)
reboot system boot 2.6.32-042stab12 Wed Mar 22 18:28 - 12:42 (3+17:14)
reboot system boot 2.6.32-042stab12 Sat Mar 18 05:10 - 12:42 (8+06:32)
reboot system boot 2.6.32-042stab12 Thu Mar 16 13:52 - 12:42 (9+21:49)
reboot system boot 2.6.32-042stab12 Thu Mar 16 09:50 - 13:52 (04:02)


I am trying to figure out why and stop it. I pasted the logs to pastebin here.



I am not doing these reboots. Also, it seems like there is nothing going on (like a crash, etc.) which would cause the server to reboot.







ubuntu reboot






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 26 '17 at 11:10







thesys

















asked Mar 26 '17 at 10:48









thesysthesys

1193




1193




closed as too broad by RalfFriedl, nwildner, msp9011, Fabby, Shadur Jan 10 at 12:35


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.






closed as too broad by RalfFriedl, nwildner, msp9011, Fabby, Shadur Jan 10 at 12:35


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.














  • @Vlastimil No I don't have physical access, just SSH. And I have no idea what -- MARK -- is.

    – thesys
    Mar 26 '17 at 11:01











  • I just read somewhere else: "The --MARK-- messages are added at regular intervals just to indicate that syslogd is still working, even when no other messages are added. "

    – thesys
    Mar 26 '17 at 11:04











  • @Vlastimil I created a pastebin. If you require more logs just tell me which.

    – thesys
    Mar 26 '17 at 11:14






  • 1





    There's nothing in the logs. Is it a multiuser system and someone else reboots it?

    – Jan
    Mar 26 '17 at 11:28











  • did you deploy the unattended-updates service and allow it to reboot after updates if it was required by an update?

    – Phillip -Zyan K Lee- Stockmann
    Mar 26 '17 at 11:29

















  • @Vlastimil No I don't have physical access, just SSH. And I have no idea what -- MARK -- is.

    – thesys
    Mar 26 '17 at 11:01











  • I just read somewhere else: "The --MARK-- messages are added at regular intervals just to indicate that syslogd is still working, even when no other messages are added. "

    – thesys
    Mar 26 '17 at 11:04











  • @Vlastimil I created a pastebin. If you require more logs just tell me which.

    – thesys
    Mar 26 '17 at 11:14






  • 1





    There's nothing in the logs. Is it a multiuser system and someone else reboots it?

    – Jan
    Mar 26 '17 at 11:28











  • did you deploy the unattended-updates service and allow it to reboot after updates if it was required by an update?

    – Phillip -Zyan K Lee- Stockmann
    Mar 26 '17 at 11:29
















@Vlastimil No I don't have physical access, just SSH. And I have no idea what -- MARK -- is.

– thesys
Mar 26 '17 at 11:01





@Vlastimil No I don't have physical access, just SSH. And I have no idea what -- MARK -- is.

– thesys
Mar 26 '17 at 11:01













I just read somewhere else: "The --MARK-- messages are added at regular intervals just to indicate that syslogd is still working, even when no other messages are added. "

– thesys
Mar 26 '17 at 11:04





I just read somewhere else: "The --MARK-- messages are added at regular intervals just to indicate that syslogd is still working, even when no other messages are added. "

– thesys
Mar 26 '17 at 11:04













@Vlastimil I created a pastebin. If you require more logs just tell me which.

– thesys
Mar 26 '17 at 11:14





@Vlastimil I created a pastebin. If you require more logs just tell me which.

– thesys
Mar 26 '17 at 11:14




1




1





There's nothing in the logs. Is it a multiuser system and someone else reboots it?

– Jan
Mar 26 '17 at 11:28





There's nothing in the logs. Is it a multiuser system and someone else reboots it?

– Jan
Mar 26 '17 at 11:28













did you deploy the unattended-updates service and allow it to reboot after updates if it was required by an update?

– Phillip -Zyan K Lee- Stockmann
Mar 26 '17 at 11:29





did you deploy the unattended-updates service and allow it to reboot after updates if it was required by an update?

– Phillip -Zyan K Lee- Stockmann
Mar 26 '17 at 11:29










1 Answer
1






active

oldest

votes


















0














Have you checked /proc/sys/kernel/panic? If it's value is 1 then server will immediately reboot on panic. Bad drivers can cause kernel panic.



If it's not panic, check last issue of reboot, maybe overheating is the issue.



last reboot






share|improve this answer





























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Have you checked /proc/sys/kernel/panic? If it's value is 1 then server will immediately reboot on panic. Bad drivers can cause kernel panic.



    If it's not panic, check last issue of reboot, maybe overheating is the issue.



    last reboot






    share|improve this answer



























      0














      Have you checked /proc/sys/kernel/panic? If it's value is 1 then server will immediately reboot on panic. Bad drivers can cause kernel panic.



      If it's not panic, check last issue of reboot, maybe overheating is the issue.



      last reboot






      share|improve this answer

























        0












        0








        0







        Have you checked /proc/sys/kernel/panic? If it's value is 1 then server will immediately reboot on panic. Bad drivers can cause kernel panic.



        If it's not panic, check last issue of reboot, maybe overheating is the issue.



        last reboot






        share|improve this answer













        Have you checked /proc/sys/kernel/panic? If it's value is 1 then server will immediately reboot on panic. Bad drivers can cause kernel panic.



        If it's not panic, check last issue of reboot, maybe overheating is the issue.



        last reboot







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Sep 4 '17 at 19:40









        JBoy AdvanceJBoy Advance

        100112




        100112












            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