Re: solution to / full
On 3/2/23 15:19, Felix Miata wrote:
David Christensen composed on 2023-03-02 14:41 (UTC-0800):
How do I make the settings live (other than rebooting, which might hang
if there is a syntax error)?
I think this is one of those things that systemctl daemon-reload does.
[quote]
So, it's a "soft" reload, essentially; taking changed configurations from filesystem and regenerating dependency trees.
[/quote]
https://unix.stackexchange.com/questions/364782/what-does-systemctl-daemon-reload-do
I know there's a way to confirm syntax, but I never remember what to search for to rediscover.
STFW "reload journald.conf" I see:
https://unix.stackexchange.com/questions/253203/how-to-tell-journald-to-re-read-its-configuration
Try a reload:
2023-03-02 15:50:15 root@laalaa ~
# systemctl reload systemd-journald
Failed to reload systemd-journald.service: Job type reload is not
applicable for unit systemd-journald.service.
Reading the above further, I see that the first answer, third comment,
shows the same result. The fourth comment links to:
https://unix.stackexchange.com/questions/379288/reloading-systemd-journald-config
Reading that answer is not encouraging.
Oh, well. I guess I'll try a restart:
2023-03-02 15:52:49 root@laalaa ~
# systemctl restart systemd-journald
2023-03-02 16:05:08 root@laalaa ~
#
Looks okay (?).
Reboot.
Now I am wondering where to look for systemd errors (?). STFW "systemd
error message":
https://unix.stackexchange.com/questions/332886/how-to-see-error-message-in-journald
2023-03-02 16:15:14 root@laalaa ~
# journalctl -p 3 -xb --no-pager
-- Journal begins at Fri 2023-02-24 11:38:23 PST, ends at Thu 2023-03-02
16:17:01 PST. --
Mar 02 16:06:25 laalaa kernel: iwlwifi 0000:03:00.0: firmware: failed to
load iwl-debug-yoyo.bin (-2)
Mar 02 16:06:25 laalaa kernel: firmware_class: See
https://wiki.debian.org/Firmware for information about missing firmware
Mar 02 16:06:30 laalaa pipewire[1165]: Failed to receive portal pid:
org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name
'org.freedesktop.portal.Desktop': no such name
Mar 02 16:06:36 laalaa lightdm[1227]: gkr-pam: unable to locate daemon
control file
Mar 02 16:06:36 laalaa pipewire[1247]: Failed to receive portal pid:
org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name
'org.freedesktop.portal.Desktop': no such name
Mar 02 16:06:38 laalaa kernel: nouveau 0000:01:00.0: firmware: failed to
load nouveau/nvd9_fuc084 (-2)
Mar 02 16:06:38 laalaa kernel: nouveau 0000:01:00.0: firmware: failed to
load nouveau/nvd9_fuc084d (-2)
Mar 02 16:06:38 laalaa kernel: nouveau 0000:01:00.0: msvld: unable to
load firmware data
Mar 02 16:06:38 laalaa kernel: nouveau 0000:01:00.0: msvld: init failed, -19
Nothing about /etc/systemd/journald.conf.d/local.conf.
Check disk usage of /var/log:
2023-03-02 16:13:39 root@laalaa ~
# du -mx -d 1 /var/log | sort -rn
94 /var/log
65 /var/log/journal
15 /var/log/installer
1 /var/log/speech-dispatcher
1 /var/log/samba
1 /var/log/runit
1 /var/log/private
1 /var/log/lightdm
1 /var/log/cups
1 /var/log/apt
Check disk free of root:
2023-03-02 16:15:04 root@laalaa ~
# df /
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/mapper/sdb3_crypt 12084M 6876M 4573M 61% /
It appears my /etc/systemd/journald.conf.d/local.conf is working. :-)
David
Reply to: