Score:0

Ubuntu 18.04 crashes abruptly

gb flag

From last few days, my ubuntu installation shuts down abruptly. I have no clue on what is causing this.

I tried few steps which I could gather and am attaching the log output as well. Can someone steer me in the right direction please?

reboot   system boot  5.4.0-74-generic Thu Jan  1 05:30 - 17:08 (4541+11:38)
runlevel (to lvl 5)   5.4.0-74-generic Tue Jun  8 16:15 - 17:08  (00:52)
myubuntu    :0           :0               Tue Jun  8 16:16 - 17:08  (00:52)
shutdown system down  5.4.0-74-generic Tue Jun  8 17:08 - 18:04  (00:56)
reboot   system boot  5.4.0-74-generic Tue Jun  8 18:04   still running
runlevel (to lvl 5)   5.4.0-74-generic Tue Jun  8 18:05 - 18:17  (00:12)
myubuntu    :0           :0               Tue Jun  8 18:05 - crash (-4541+12:34)
reboot   system boot  5.4.0-74-generic Thu Jan  1 05:30   still running
runlevel (to lvl 5)   5.4.0-74-generic Tue Jun  8 18:17   still running
myubuntu    :0           :0               Tue Jun  8 18:17    gone - no logout

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$


myubuntu:~ grep -iv ': starting\|kernel: .*: Power Button\|watching system buttons\|Stopped Cleaning Up\|Started Crash recovery kernel' \
>   /var/log/messages /var/log/syslog /var/log/apcupsd* \
>   | grep -iw 'recover[a-z]*\|power[a-z]*\|shut[a-z ]*down\|rsyslogd\|ups'
grep: /var/log/messages: No such file or directory
/var/log/syslog:Jun  8 08:27:48 myubuntu rsyslogd:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="1092" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
/var/log/syslog:Jun  8 10:05:44 myubuntu kernel: [   16.148709] systemd-journald[435]: File /var/log/journal/876825fc89af4e0a835b842317a84125/system.journal corrupted or uncleanly shut down, renaming and replacing.
/var/log/syslog:Jun  8 10:05:44 myubuntu systemd-fsck[789]: /dev/sda1: recovering journal
/var/log/syslog:Jun  8 10:05:44 myubuntu apparmor[854]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
/var/log/syslog:Jun  8 10:05:44 myubuntu systemd[1]: Started Update UTMP about System Boot/Shutdown.
/var/log/syslog:Jun  8 10:05:44 myubuntu dbus-daemon[1109]: dbus[1109]: Unknown group "power" in message bus configuration file
/var/log/syslog:Jun  8 10:05:44 myubuntu systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
/var/log/syslog:Jun  8 10:05:44 myubuntu rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.32.0]
/var/log/syslog:Jun  8 10:05:44 myubuntu rsyslogd: rsyslogd's groupid changed to 106
/var/log/syslog:Jun  8 10:05:44 myubuntu rsyslogd: rsyslogd's userid changed to 102
/var/log/syslog:Jun  8 10:05:44 myubuntu rsyslogd:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="1174" x-info="http://www.rsyslog.com"] start
/var/log/syslog:Jun  8 10:05:44 myubuntu thermald[1153]: sysfs write failed /sys/devices/virtual/powercap/intel-rapl/intel-rapl:0/enabled
grep: /var/log/apcupsd*: No such file or directory
/var/log/syslog:Jun  8 10:05:45 myubuntu NetworkManager[1154]: <info>  [1623126945.0979] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: 10-ubuntu-fan.conf, default-wifi-powersave-on.conf)
/var/log/syslog:Jun  8 10:05:46 myubuntu systemd[1]: Started Daemon for power management.
/var/log/syslog:Jun  8 10:05:48 myubuntu boltd[1711]: power: force power support: no
/var/log/syslog:Jun  8 10:05:49 myubuntu set-cpufreq[1160]: Setting powersave scheduler for all CPUs
myubuntu:~ 

Please do suggest if any other logs might help.

If nothing helps then I think my last option is to wipe down the installation altogether :(

Thanks Vick

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.