Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • It might be worth posting excerpts from /var/log/messages and your bash history from the time that the reboots were happening. Is this a desktop or a server? Commented Dec 9, 2014 at 21:21
  • It is a desktop, but I have like 11 bash scripts running simultaneously on misc tasks, but they are like that for about a year or so. I will check that messages. Commented Dec 9, 2014 at 21:29
  • Nobody calls or activates the user. It's just how a reboot is logged in the records that last uses, no matter what triggered the reboot. Commented Dec 9, 2014 at 21:46
  • @Dayvo the reboot happened around 18:33, may be 18:32:30 (I got stunned), on log there was this: "Dec 9 18:30:39 hostid wpa_supplicant[1226]: wlan0: CTRL-EVENT-SCAN-STARTED", and this "Dec 9 18:31:35 hostid postfix/sendmail[3555097]: fatal: open /etc/postfix/main.cf: No such file or directory", but these last ones happen very often and they were much before the reboot time. Commented Dec 9, 2014 at 21:48
  • @muru, any tip on how to catch what triggered the reboot? Commented Dec 9, 2014 at 21:49