My Linux Mint 20 randomly shuts down every few weeks

Questions about other topics - please check if your question fits better in another category before posting here
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Fasterghost
Level 1
Level 1
Posts: 11
Joined: Thu Jul 04, 2013 6:55 am

My Linux Mint 20 randomly shuts down every few weeks

Post by Fasterghost »

Dear Linux Mint forum members,

I recently encountered a strange phenomenon where my NAS computer (Linux NFS 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux) where I am running Linux Mint 20 Mate would shut itself down every few weeks. I first suspected power-outages or failing hardware but by looking at the logs, I can see that this is a software shutdown.

The thing is, based on those logs, I cannot determine what is causing these shutdowns. :-(

There was nobody using the NAS at the times the shutdowns occurred and there was nothing special running there either. I am also the only one with physical access so nobody pressed the power button either. I also did some quick stress tests and there seem to be nothing wrong with the hardware.

Below, I am attaching the relevant portions of the logs and I would be very grateful for any ideas you can give me. Note that I selected portion of the logs from the point where it seem to start happening to a point where normal shutdown processes are underway.

Syslog:

Code: Select all

Apr 18 04:54:24 NFS rtkit-daemon[2202]: Supervising 2 threads of 1 processes of 1 users.
Apr 18 04:54:24 NFS rtkit-daemon[2202]: Successfully made thread 74840 of process 2121 owned by '1000' RT at priority 5.
Apr 18 04:54:24 NFS rtkit-daemon[2202]: Supervising 3 threads of 1 processes of 1 users.
Apr 18 04:54:27 NFS NetworkManager[1852]: <info>  [1618714467.5956] manager: NetworkManager state is now CONNECTED_SITE
Apr 18 04:54:27 NFS dbus-daemon[1850]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=1852 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 18 04:54:27 NFS systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 18 04:54:27 NFS dbus-daemon[1850]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 18 04:54:27 NFS systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 18 04:54:27 NFS NetworkManager[1852]: <info>  [1618714467.8640] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 18 04:54:34 NFS systemd[2112]: Stopping D-Bus User Message Bus...
Apr 18 04:54:34 NFS gvfsd[2462]: A connection to the bus can't be made
Apr 18 04:54:34 NFS systemd[2112]: gvfs-mtp-volume-monitor.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: gvfs-gphoto2-volume-monitor.service: Succeeded.
Apr 18 04:54:34 NFS xdg-desktop-por[2683]: Failed to close session implementation: The connection is closed
Apr 18 04:54:34 NFS systemd[1]: run-user-1000-gvfs.mount: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: run-user-1000-gvfs.mount: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: gvfs-goa-volume-monitor.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE
Apr 18 04:54:34 NFS systemd[2112]: xdg-permission-store.service: Failed with result 'exit-code'.
Apr 18 04:54:34 NFS systemd[2112]: obex.service: Main process exited, code=exited, status=1/FAILURE
Apr 18 04:54:34 NFS systemd[2112]: obex.service: Failed with result 'exit-code'.
Apr 18 04:54:34 NFS evolution-calen[2758]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
Apr 18 04:54:34 NFS evolution-calen[2758]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
Apr 18 04:54:34 NFS evolution-addre[2785]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
Apr 18 04:54:34 NFS systemd[1]: run-user-1000-doc.mount: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: run-user-1000-doc.mount: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: gvfs-metadata.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: xdg-document-portal.service: Main process exited, code=exited, status=20/n/a
Apr 18 04:54:34 NFS systemd[2112]: xdg-document-portal.service: Failed with result 'exit-code'.
Apr 18 04:54:34 NFS systemd[2112]: gvfs-afc-volume-monitor.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: gvfs-udisks2-volume-monitor.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: xdg-desktop-portal.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: xdg-desktop-portal-gtk.service: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopping Session c1 of user salon.
Apr 18 04:54:34 NFS systemd[1]: Removed slice system-clean\x2dmount\x2dpoint.slice.
Apr 18 04:54:34 NFS systemd[2112]: evolution-source-registry.service: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Removed slice system-modprobe.slice.
Apr 18 04:54:34 NFS pulseaudio[2121]: ICE default IO error handler doing an exit(), pid = 2121, errno = 32
Apr 18 04:54:34 NFS systemd[1]: Removed slice system-postfix.slice.
Apr 18 04:54:34 NFS systemd[1]: Stopped target Graphical Interface.
Apr 18 04:54:34 NFS systemd[1]: Stopped target Multi-User System.
Apr 18 04:54:34 NFS systemd[1]: Stopped target Login Prompts.
Apr 18 04:54:34 NFS systemd[1]: Stopped target RPC Port Mapper.
Apr 18 04:54:34 NFS systemd[1]: Stopped target Sound Card.
Apr 18 04:54:34 NFS systemd[1]: Stopped target Timers.
Apr 18 04:54:34 NFS systemd[1]: anacron.timer: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopped Trigger anacron every hour.
Apr 18 04:54:34 NFS systemd[1]: apt-daily-upgrade.timer: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: dbus.service: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopped Daily apt upgrade and clean activities.
Apr 18 04:54:34 NFS systemd[1]: apt-daily.timer: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopped Daily apt download activities.
Apr 18 04:54:34 NFS systemd[2112]: Stopped D-Bus User Message Bus.
Apr 18 04:54:34 NFS systemd[1]: e2scrub_all.timer: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopped Periodic ext4 Online Metadata Check for All Filesystems.
Apr 18 04:54:34 NFS systemd[1]: fstrim.timer: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopped Discard unused blocks once a week.
Apr 18 04:54:34 NFS systemd[2112]: evolution-calendar-factory.service: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: fwupd-refresh.timer: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopped Refresh fwupd metadata regularly.
Apr 18 04:54:34 NFS systemd[1]: logrotate.timer: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopped Daily rotation of log files.
Apr 18 04:54:34 NFS systemd[1]: man-db.timer: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopped Daily man-db regeneration.
Apr 18 04:54:34 NFS systemd[1]: motd-news.timer: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopped Message of the Day.
Apr 18 04:54:34 NFS nm-dispatcher: Caught signal 15, shutting down...
Apr 18 04:54:34 NFS systemd[2112]: evolution-addressbook-factory.service: Succeeded.
Apr 18 04:54:34 NFS ModemManager[1980]: <info>  Caught signal, shutting down...
Apr 18 04:54:34 NFS systemd[1]: systemd-tmpfiles-clean.timer: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Apr 18 04:54:34 NFS systemd[1]: lvm2-lvmpolld.socket: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Closed LVM2 poll daemon socket.
Apr 18 04:54:34 NFS systemd[1]: systemd-rfkill.socket: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Apr 18 04:54:34 NFS systemd[2112]: Started D-Bus User Message Bus.
Apr 18 04:54:34 NFS systemd[1]: Stopping Modem Manager...
Apr 18 04:54:34 NFS systemd[1]: Stopping Network Manager Script Dispatcher Service...
Apr 18 04:54:34 NFS systemd[1]: Stopping Accounts Service...
Apr 18 04:54:34 NFS systemd[1]: Stopping ACPI event daemon...
/var/log/auth:

Code: Select all

Apr 18 04:54:34 NFS polkitd(authority=local): Unregistered Authentication Agent for unix-session:c1 (system bus name :1.37, object path /org/mate/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Apr 18 04:54:34 NFS systemd-logind[1897]: System is powering down.
Apr 18 04:54:34 NFS lightdm: pam_unix(lightdm-autologin:session): session closed for user salon
journalctl:

Code: Select all

Apr 18 04:54:27 NFS NetworkManager[1852]: <info>  [1618714467.5956] manager: NetworkManager state is now CONNECTED_SITE
Apr 18 04:54:27 NFS dbus-daemon[1850]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=1852 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 18 04:54:27 NFS systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 18 04:54:27 NFS dbus-daemon[1850]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 18 04:54:27 NFS systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 18 04:54:27 NFS NetworkManager[1852]: <info>  [1618714467.8640] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 18 04:54:34 NFS polkitd(authority=local)[1876]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.37, object path /org/mate/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Apr 18 04:54:34 NFS systemd[2112]: Stopping D-Bus User Message Bus...
Apr 18 04:54:34 NFS gvfsd[2462]: A connection to the bus can't be made
Apr 18 04:54:34 NFS systemd[2112]: gvfs-mtp-volume-monitor.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: gvfs-gphoto2-volume-monitor.service: Succeeded.
Apr 18 04:54:34 NFS xdg-desktop-por[2683]: Failed to close session implementation: The connection is closed
Apr 18 04:54:34 NFS systemd[1]: run-user-1000-gvfs.mount: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: run-user-1000-gvfs.mount: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: gvfs-goa-volume-monitor.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE
Apr 18 04:54:34 NFS systemd[2112]: xdg-permission-store.service: Failed with result 'exit-code'.
Apr 18 04:54:34 NFS systemd[2112]: obex.service: Main process exited, code=exited, status=1/FAILURE
Apr 18 04:54:34 NFS systemd[2112]: obex.service: Failed with result 'exit-code'.
Apr 18 04:54:34 NFS evolution-calen[2758]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
Apr 18 04:54:34 NFS evolution-calen[2758]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
Apr 18 04:54:34 NFS evolution-addre[2785]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
Apr 18 04:54:34 NFS systemd[1]: run-user-1000-doc.mount: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: run-user-1000-doc.mount: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: gvfs-metadata.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: xdg-document-portal.service: Main process exited, code=exited, status=20/n/a
Apr 18 04:54:34 NFS systemd[2112]: xdg-document-portal.service: Failed with result 'exit-code'.
Apr 18 04:54:34 NFS systemd-logind[1897]: System is powering down.
Apr 18 04:54:34 NFS systemd[2112]: gvfs-afc-volume-monitor.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: gvfs-udisks2-volume-monitor.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: xdg-desktop-portal.service: Succeeded.
Apr 18 04:54:34 NFS systemd[2112]: xdg-desktop-portal-gtk.service: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Stopping Session c1 of user salon.
Apr 18 04:54:34 NFS systemd[1]: Removed slice system-clean\x2dmount\x2dpoint.slice.
Apr 18 04:54:34 NFS systemd[2112]: evolution-source-registry.service: Succeeded.
Apr 18 04:54:34 NFS systemd[1]: Removed slice system-modprobe.slice.
Apr 18 04:54:34 NFS pulseaudio[2121]: ICE default IO error handler doing an exit(), pid = 2121, errno = 32
Apr 18 04:54:34 NFS systemd[1]: Removed slice system-postfix.slice.
Apr 18 04:54:34 NFS systemd[1]: Stopped target Graphical Interface.
Apr 18 04:54:34 NFS systemd[1]: Stopped target Multi-User System.
Apr 18 04:54:34 NFS systemd[1]: Stopped target Login Prompts.
Apr 18 04:54:34 NFS systemd[1]: Stopped target RPC Port Mapper.
Apr 18 04:54:34 NFS systemd[1]: Stopped target Sound Card.
Apr 18 04:54:34 NFS systemd[1]: Stopped target Timers.
Thank you very much in advance!
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
SMG
Level 25
Level 25
Posts: 31304
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: My Linux Mint 20 randomly shuts down every few weeks

Post by SMG »

Fasterghost wrote: Sun Apr 18, 2021 7:36 amI recently encountered a strange phenomenon where my NAS computer (Linux NFS 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux) where I am running Linux Mint 20 Mate would shut itself down every few weeks. I first suspected power-outages or failing hardware but by looking at the logs, I can see that this is a software shutdown.

The thing is, based on those logs, I cannot determine what is causing these shutdowns. :-(
Based on the log portions you posted, I think it's possible whatever might be causing the problem happens before what you posted. You mostly posted the shutdown info with only a couple of lines of what happened in the ten seconds before systemd stopped the D-Bus User Message Bus.

Have you noticed if the shutdowns seem to happen on specific days of the week? Or might there be any other similarities (ie. days of the month) when they happen?

Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
That will let us know what hardware you have and how Mint views it.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Fasterghost
Level 1
Level 1
Posts: 11
Joined: Thu Jul 04, 2013 6:55 am

Re: My Linux Mint 20 randomly shuts down every few weeks

Post by Fasterghost »

Hi,

thank you for your answer.

Here is the output of that command, as well as some of the previous lines from the logs posted above. There does not seem to be anything relevant though, unless the shutdown was triggered way earlier and large waiting period. I do not think it happens at specific times or days.

inxi -Fxxxrz

Code: Select all

System:
  Kernel: 5.4.0-70-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Console: tty 1 dm: LightDM 1.30.0 Distro: Linux Mint 20 Ulyana 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: Micro-Star model: B450 TOMAHAWK MAX (MS-7C02) v: 1.0 
  serial: <filter> UEFI: American Megatrends v: 3.70 date: 06/09/2020 
CPU:
  Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics 
  bits: 64 type: MT MCP arch: Zen+ rev: 1 L1 cache: 384 KiB 
  L2 cache: 2048 KiB L3 cache: 4096 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 59202 
  Speed: 1263 MHz min/max: N/A Core speeds (MHz): 1: 1263 2: 1263 3: 1260 
  4: 1260 5: 1265 6: 1268 7: 1313 8: 1338 
Graphics:
  Device-1: AMD Picasso vendor: Micro-Star MSI driver: amdgpu v: kernel 
  bus ID: 29:00.0 chip ID: 1002:15d8 
  Display: server: X.org 1.20.9 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa compositor: compton v: 0.1~beta2+20150922 
  tty: 80x24 
  Message: Advanced graphics data unavailable in console for root. 
Audio:
  Device-1: Creative Labs CA0108/CA10300 [Sound Blaster Audigy Series] 
  driver: snd_emu10k1 v: kernel bus ID: 26:00.0 chip ID: 1102:0008 
  Device-2: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel 
  v: kernel bus ID: 29:00.1 chip ID: 1002:15de 
  Device-3: AMD Family 17h HD Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 29:00.6 chip ID: 1022:15e3 
  Sound Server: ALSA v: k5.4.0-70-generic 
Network:
  Device-1: Intel 82574L Gigabit Network driver: e1000e v: 3.2.6-k 
  port: b000 bus ID: 28:00.0 chip ID: 8086:10d3 
  IF: enp40s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 47.47 TiB used: 19.57 TiB (41.2%) 
  ID-1: /dev/sda vendor: Toshiba model: HDWN160 size: 5.46 TiB 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: FS1M temp: 34 C 
  ID-2: /dev/sdb vendor: Western Digital model: WD40EZRZ-00GXCB0 
  size: 3.64 TiB speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> 
  rev: 0A80 temp: 25 C scheme: GPT 
  ID-3: /dev/sdc vendor: Western Digital model: WD60EFRX-68L0BN1 
  size: 5.46 TiB speed: 6.0 Gb/s rotation: 5700 rpm serial: <filter> 
  rev: 0A82 temp: 29 C 
  ID-4: /dev/sdd vendor: Western Digital model: WD6003FZBX-00K5WB0 
  size: 5.46 TiB speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
  rev: 1A01 temp: 26 C 
  ID-5: /dev/sde vendor: Western Digital model: WD6003FZBX-00K5WB0 
  size: 5.46 TiB speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
  rev: 1A01 temp: 26 C 
  ID-6: /dev/sdf type: USB vendor: Western Digital model: WD Elements 25A3 
  size: 3.64 TiB serial: <filter> rev: 1013 scheme: GPT 
  ID-7: /dev/sdg vendor: Western Digital model: WD2003FZEX-00Z4SA0 
  size: 1.82 TiB speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
  rev: 1A01 temp: 26 C scheme: GPT 
  ID-8: /dev/sdh vendor: Western Digital model: WD40EZRZ-00GXCB0 
  size: 3.64 TiB speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> 
  rev: 0A80 temp: 24 C scheme: GPT 
  ID-9: /dev/sdi vendor: Western Digital model: WD40EFRX-68N32N0 
  size: 3.64 TiB speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> 
  rev: 0A82 temp: 25 C scheme: GPT 
  ID-10: /dev/sdj vendor: Western Digital model: WD40EZRZ-00GXCB0 
  size: 3.64 TiB speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> 
  rev: 0A80 temp: 24 C scheme: GPT 
  ID-11: /dev/sdk vendor: Intel model: SSDSC2CT180A4 size: 167.68 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 335u scheme: GPT 
  ID-12: /dev/sdl vendor: Western Digital model: WD60EZRZ-00GZ5B1 
  size: 5.46 TiB speed: 6.0 Gb/s rotation: 5700 rpm serial: <filter> 
  rev: 0A80 temp: 26 C 
RAID:
  Supported md-raid types: raid1 raid6 raid5 raid4 linear multipath raid0 
  raid10 
  Device-1: md1 type: mdraid status: active Components: 
  online: sdj1~c0 sdh1~c1 
  Info: raid: mirror blocks: 3906783232 report: 2/2 UU chunk size: N/A 
  super blocks: 1.2 
  Device-2: md451 type: mdraid status: active Components: 
  online: sdi1~c1 sdb1~c0 
  Info: raid: mirror blocks: 3906865152 report: 2/2 UU chunk size: N/A 
  super blocks: 1.2 
  Device-3: md0 type: mdraid status: active Components: 
  online: sdl~c3 sde~c0 sda~c4 sdd~c1 sdc~c5 
  Info: raid: raid-6 blocks: 17581171392 report: 5/5 UUUUU chunk size: 64k 
  super blocks: 1.2 algorithm: 2 
Partition:
  ID-1: / size: 163.59 GiB used: 14.34 GiB (8.8%) fs: ext4 dev: /dev/sdk2 
Sensors:
  System Temperatures: cpu: 26.4 C mobo: 31.0 C gpu: amdgpu temp: 26 C 
  Fan Speeds (RPM): fan-1: 0 fan-2: 1880 fan-3: 892 fan-4: 0 fan-5: 847 
  fan-6: 0 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com ulyana main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:
  Processes: 362 Uptime: 1d 10h 02m Memory: 31.06 GiB used: 1.46 GiB (4.7%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 
  Shell: bash (sudo) v: 5.0.17 running in: tty 1 (SSH) inxi: 3.0.38
/var/log/auth

Code: Select all

Apr 18 04:17:01 NFS CRON[74802]: pam_unix(cron:session): session closed for user
 root
Apr 18 04:25:01 NFS CRON[74810]: pam_unix(cron:session): session opened for user
 root by (uid=0)
Apr 18 04:25:01 NFS CRON[74810]: pam_unix(cron:session): session closed for user
 root
Apr 18 04:35:01 NFS CRON[74819]: pam_unix(cron:session): session opened for user
 root by (uid=0)
Apr 18 04:35:01 NFS CRON[74819]: pam_unix(cron:session): session closed for user root
Apr 18 04:45:01 NFS CRON[74830]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 18 04:45:01 NFS CRON[74830]: pam_unix(cron:session): session closed for user root
syslog

Code: Select all

Apr 18 03:35:01 NFS CRON[74759]: (root) CMD (command -v debian-sa1 > /dev/null && debian-s
a1 1 1)
Apr 18 03:45:01 NFS CRON[74770]: (root) CMD (command -v debian-sa1 > /dev/null && debian-s
a1 1 1)
Apr 18 03:55:01 NFS CRON[74780]: (root) CMD (command -v debian-sa1 > /dev/null &
& debian-sa1 1 1)
Apr 18 04:05:01 NFS CRON[74789]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 18 04:07:16 NFS smartd[1894]: Device: /dev/sdj [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 125 to 126
Apr 18 04:15:01 NFS CRON[74799]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 18 04:17:01 NFS CRON[74803]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 18 04:19:01 NFS ntpd[2067]: receive: Unexpected origin timestamp 0xe4261594.c87ed77f does not match aorg 0000000000.00000000 from server@5.1.56.123 xmt 0xe4261595.e324c300
Apr 18 04:25:01 NFS CRON[74811]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 18 04:35:01 NFS CRON[74820]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 18 04:45:01 NFS CRON[74831]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
journalctl

Code: Select all

Apr 18 03:45:01 NFS CRON[74769]: pam_unix(cron:session): session closed for user root
Apr 18 03:55:01 NFS CRON[74779]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 18 03:55:01 NFS CRON[74780]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 18 03:55:01 NFS CRON[74779]: pam_unix(cron:session): session closed for user root
Apr 18 04:05:01 NFS CRON[74788]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 18 04:05:01 NFS CRON[74789]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 18 04:05:01 NFS CRON[74788]: pam_unix(cron:session): session closed for user root
Apr 18 04:07:16 NFS smartd[1894]: Device: /dev/sdj [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 125 to 126
Apr 18 04:15:01 NFS CRON[74798]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 18 04:15:01 NFS CRON[74799]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 18 04:15:01 NFS CRON[74798]: pam_unix(cron:session): session closed for user root
Apr 18 04:17:01 NFS CRON[74802]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 18 04:17:01 NFS CRON[74803]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 18 04:17:01 NFS CRON[74802]: pam_unix(cron:session): session closed for user root
Apr 18 04:19:01 NFS ntpd[2067]: receive: Unexpected origin timestamp 0xe4261594.c87ed77f does not match aorg 0000000000.00000000 from server@5.1.56.123 xmt 0xe4261595.e324c300
Apr 18 04:25:01 NFS CRON[74810]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 18 04:25:01 NFS CRON[74811]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 18 04:25:01 NFS CRON[74810]: pam_unix(cron:session): session closed for user root
Apr 18 04:35:01 NFS CRON[74819]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 18 04:35:01 NFS CRON[74820]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 18 04:35:01 NFS CRON[74819]: pam_unix(cron:session): session closed for user root
Apr 18 04:45:01 NFS CRON[74830]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 18 04:45:01 NFS CRON[74831]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 18 04:45:01 NFS CRON[74830]: pam_unix(cron:session): session closed for user root
Thanks!
Fasterghost
Level 1
Level 1
Posts: 11
Joined: Thu Jul 04, 2013 6:55 am

Re: My Linux Mint 20 randomly shuts down every few weeks

Post by Fasterghost »

I just noticed that there is this series of processes happening at IRREGULAR intervals according to the journalctl. First is the situation where it does not shutdown PC and second is the one where it does.

Code: Select all

Apr 17 06:52:55 NFS NetworkManager[1852]: <info>  [1618635175.1360] manager: NetworkManager state is now CONNECTED_SITE
Apr 17 06:52:55 NFS dbus-daemon[1850]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=1852 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 17 06:52:55 NFS systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 17 06:52:55 NFS dbus-daemon[1850]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 17 06:52:55 NFS systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 17 06:52:59 NFS NetworkManager[1852]: <info>  [1618635179.8723] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 17 06:53:10 NFS systemd[1]: NetworkManager-dispatcher.service: Succeeded.

Code: Select all

Apr 18 04:54:27 NFS NetworkManager[1852]: <info>  [1618714467.5956] manager: NetworkManager state is now CONNECTED_SITE
Apr 18 04:54:27 NFS dbus-daemon[1850]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=1852 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 18 04:54:27 NFS systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 18 04:54:27 NFS dbus-daemon[1850]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 18 04:54:27 NFS systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 18 04:54:27 NFS NetworkManager[1852]: <info>  [1618714467.8640] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 18 04:54:34 NFS polkitd(authority=local)[1876]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.37, object path /org/mate/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Apr 18 04:54:34 NFS systemd[2112]: Stopping D-Bus User Message Bus...
So in typical situations, it ends with message:

systemd[1]: NetworkManager-dispatcher.service: Succeeded.

But in rare cases, it goes to error message and proceeds to shutdown the PC:

polkitd(authority=local)[1876]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.37, object path /org/mate/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Apr 18 04:54:34 NFS systemd[2112]: Stopping D-Bus User Message Bus...

Any ideas?

Thanks.
User avatar
SMG
Level 25
Level 25
Posts: 31304
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: My Linux Mint 20 randomly shuts down every few weeks

Post by SMG »

Fasterghost wrote: Mon Apr 19, 2021 5:43 pmBut in rare cases, it goes to error message and proceeds to shutdown the PC:

polkitd(authority=local)[1876]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.37, object path /org/mate/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Apr 18 04:54:34 NFS systemd[2112]: Stopping D-Bus User Message Bus...
What error message are you seeing?

Explanation of polkitd Unregistered Authentication Agent indicates, "Policykit is a system daemon and policykit authentication agent is used to verify identity of the user before executing actions. The messages logged in /var/log/secure show that an authentication agent is registered when user logs in and it gets unregistered when user logs out. These messages are harmless and can be safely ignored."

It's my understanding the 5.8 kernel has improvements which help 3rd gen Ryzens. Maybe updating to that kernel will help resolve the shutdowns. I know it helped others resolve odd freeze situations.
CPU:
Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics

If you want to give it a try, it is available in Update Manager.

Open Update Manager. Select View > Linux Kernels and click Continue. Make sure 5.8 is selected on the left panel and then click the top-most option on the right panel. An "Install" button will appear. Install the kernel and then reboot for it to become active.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Fasterghost
Level 1
Level 1
Posts: 11
Joined: Thu Jul 04, 2013 6:55 am

Re: My Linux Mint 20 randomly shuts down every few weeks

Post by Fasterghost »

Thank you for the suggestion regarding the new kernel. I'll give it a try later. I still think that key to the mystery is why these specific processes occur.

Code: Select all

Apr 17 06:52:55 NFS NetworkManager[1852]: <info>  [1618635175.1360] manager: NetworkManager state is now CONNECTED_SITE
Apr 17 06:52:55 NFS dbus-daemon[1850]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=1852 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 17 06:52:55 NFS systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 17 06:52:55 NFS dbus-daemon[1850]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 17 06:52:55 NFS systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 17 06:52:59 NFS NetworkManager[1852]: <info>  [1618635179.8723] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 17 06:53:10 NFS systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Why is NetworkManager cycling between CONNECTED_SITE and CONNECTED_GLOBAL states...

I have two other Linux PCs in the network also running Linux Mint 20 with the same NIC. In none of those is this happening and there are no weird shutdowns.
User avatar
SMG
Level 25
Level 25
Posts: 31304
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: My Linux Mint 20 randomly shuts down every few weeks

Post by SMG »

Fasterghost wrote: Thu Apr 22, 2021 6:33 amWhy is NetworkManager cycling between CONNECTED_SITE and CONNECTED_GLOBAL states...

I have two other Linux PCs in the network also running Linux Mint 20 with the same NIC. In none of those is this happening and there are no weird shutdowns.
If you see the system cycling, perhaps there is a clue in the time sequence. I do not know how your network device and its driver might be different for that computer compared to the other two PCs you have.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Fasterghost
Level 1
Level 1
Posts: 11
Joined: Thu Jul 04, 2013 6:55 am

Re: My Linux Mint 20 randomly shuts down every few weeks

Post by Fasterghost »

In all cases, the NIC is Intel Gigabit CT PCI-E and the driver is e1000e. As far as I know, I do not use any special settings with either of them, except that they are all configured for Jumbo Frames MTU (9000 bytes).

I cannot find any time pattern to the cyclings, based either on time of the day/week, the intervals, or the usage of the NAS when it occurs... it makes no sense.

I am starting to suspect it could be Data degradation in RAM after the computer is running non-stop for a very long time. I am considering purchasing new rig with ECC capability.
User avatar
SMG
Level 25
Level 25
Posts: 31304
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: My Linux Mint 20 randomly shuts down every few weeks

Post by SMG »

Fasterghost wrote: Fri Apr 23, 2021 5:54 amI am starting to suspect it could be Data degradation in RAM after the computer is running non-stop for a very long time. I am considering purchasing new rig with ECC capability.
Or you could just try the 5.8 kernel I suggested trying earlier in this thread.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
deepakdeshp
Level 20
Level 20
Posts: 12334
Joined: Sun Aug 09, 2015 10:00 am

Re: My Linux Mint 20 randomly shuts down every few weeks

Post by deepakdeshp »

Fasterghost wrote: Fri Apr 23, 2021 5:54 am In all cases, the NIC is Intel Gigabit CT PCI-E and the driver is e1000e. As far as I know, I do not use any special settings with either of them, except that they are all configured for Jumbo Frames MTU (9000 bytes).

I cannot find any time pattern to the cyclings, based either on time of the day/week, the intervals, or the usage of the NAS when it occurs... it makes no sense.

I am starting to suspect it could be Data degradation in RAM after the computer is running non-stop for a very long time. I am considering purchasing new rig with ECC capability.
I am sure there won't be data degradation. Run memtest from grub for a long time which will test memory.

For disks
https://help.ubuntu.com/community/Smartmontools
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help.
Regards,
Deepak

Mint 21.1 Cinnamon 64 bit with AMD A6 / 8GB
Mint 21.1 Cinnamon AMD Ryzen3500U/8gb
deepakdeshp
Level 20
Level 20
Posts: 12334
Joined: Sun Aug 09, 2015 10:00 am

Re: My Linux Mint 20 randomly shuts down every few weeks

Post by deepakdeshp »

If possible open the box and blow off the dust, check if all the fans are running. Change the power supply which can cause unpredictable problems.
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help.
Regards,
Deepak

Mint 21.1 Cinnamon 64 bit with AMD A6 / 8GB
Mint 21.1 Cinnamon AMD Ryzen3500U/8gb
Locked

Return to “Other topics”