Mageia forum

As the title says, my reboot process hangs for around 2 minutes and then in ctrl+alt+f2 the last message before system shutdown is "watchdog did not stop!". Any ideas?

Best add the output as root of

Code: Select all

journalctl -ab-1 | tail -2500

and add a hint at what time you triggered the shutdown.
That command will show the journal from last boot (-b-1) and only the 2500 last lines. If your shutdown is not included you might want to replace that with more lines (5000 or more or so)

I went to Windows (I have dual boot) while awaiting a reply and when I came back to Mageia to try rebooting it, it did reboot almost instantly, so it seems that the issue has resolved itself.

By the way, while running "journalctl -ab-1 | tail -2500" I get reply "Specifying boot ID or boot offset has no effect, no persistent journal was found." so that's also a thing.

MagicD3VIL wrote:By the way, while running "journalctl -ab-1 | tail -2500" I get reply "Specifying boot ID or boot offset has no effect, no persistent journal was found." so that's also a thing.

That means you only have access to the journal logs from the current boot. Can you check whether the folder /var/log/journal exists and what do you have in /etc/systemd/journald.conf ?

/var/log/journals does not exist.

/etc/systemd/journald.conf:

Code: Select all

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See journald.conf(5) for details.

[Journal]
#Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=1000
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=no
#ForwardToKMsg=no
ForwardToConsole=yes
#ForwardToWall=yes
TTYPath=/dev/tty12
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg

MagicD3VIL wrote:/var/log/journals does not exist.

It's /var/log/journal not /var/log/journals - and that would be surprising as that directory belongs to the systemd package.
Can you show the output of

Code: Select all

ls -ald /var/log/journal

Sorry for the typo

Code: Select all

[root@localhost magicd3vil]# ls -ald /var/log/journal
drwxr-sr-x+ 3 root systemd-journal 4096 srp 14 12:00 /var/log/journal/

Hmmm looks fine.

Can you show the output as root of

Code: Select all

systemctl status systemd-journald -al -n150

Code: Select all

[root@localhost pam.d]# systemctl status systemd-journald -al -n150
● systemd-journald.service - Journal Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static; vendor preset: disabled)
   Active: active (running) since Wed 2019-10-02 10:47:58 CEST; 16min ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
 Main PID: 540 (systemd-journal)
   Status: "Processing requests..."
   Memory: 41.8M
   CGroup: /system.slice/systemd-journald.service
           └─540 /usr/lib/systemd/systemd-journald

říj 02 10:47:58 localhost.localdomain systemd-journald[540]: Journal started
říj 02 10:47:58 localhost.localdomain systemd-journald[540]: Runtime journal (/run/log/journal/cdde6703ceec485fbb52da88887d7e41) is 8.0M, max 377.3M, 369.3M free.
říj 02 10:47:58 localhost.localdomain systemd-journald[540]: Time spent on flushing to /var is 51.506ms for 724 entries.
říj 02 10:47:58 localhost.localdomain systemd-journald[540]: System journal (/var/log/journal/cdde6703ceec485fbb52da88887d7e41) is 448.1M, max 1.9G, 1.4G free.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.


But as I said, the issue self-resolved while ago