snapd

Bug #1872115
Comment #1

Comment 1 for bug 1872115

Revision history for this message

Tony Espy (awe) wrote on 2020-04-10:

While I haven't reproduced the entire problem (i.e. /writable --> 100%) I did confirm that the script used to trigger a restart doesn't work on my Dell 3000.

Here's the contents of the script (/usr/lib/rsyslog/rsyslog-rotate) in question:

$ cat /usr/lib/rsyslog/rsyslog-rotate
#!/bin/sh

if [ -d /run/systemd/system ]; then
systemctl kill -s HUP rsyslog.service
else
invoke-rc.d rsyslog rotate > /dev/null
fi

Since the directory /run/systemd/system exists, the first command is run, which fails actually trigger a restart of rsyslogd. Here's my test:

admin@C2112XX:/run/systemd$ systemctl status rsyslog.service
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2020-03-25 15:45:04 UTC; 2h 31min ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
Main PID: 1948 (rsyslogd)
   CGroup: /system.slice/rsyslog.service
           └─1948 /usr/sbin/rsyslogd -n
admin@C2112XX:/run/systemd$ sudo systemctl kill -s HUP rsyslog.service
admin@C2112XX:/run/systemd$ systemctl status rsyslog.service
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2020-03-25 15:45:04 UTC; 2h 31min ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
Main PID: 1948 (rsyslogd)
   CGroup: /system.slice/rsyslog.service
           └─1948 /usr/sbin/rsyslogd -n

The snaps on this system are:

admin@C2112XX:/run/systemd$ snap list
Name Version Rev Tracking Publisher Notes
alsa-utils 1.1.2-5 68 stable canonical✓ -
bluez 5.47-3 166 edge canonical✓ -
caracalla 16.04-1.38 52 stable canonical✓ gadget
caracalla-kernel 4.4.0-176.206 127 stable canonical✓ kernel
ccm-wda 3.01.14.42204 20 stable dell-inc -
core 16-2.43.3 8689 stable canonical✓ core
core18 20200124 1668 stable canonical✓ base
dcc 4.2.0.553 5 stable dell-inc -
docker 18.09.9 423 stable canonical✓ -
locationd 4.2.1 163 stable canonical✓ -
modem-manager 1.8.0-12 426 stable canonical✓ -
network-manager 1.2.2-24 514 stable canonical✓ -
tpm2 1.0-5 42 stable canonical✓ -
udisks2 2.6.4-2 100 stable canonical✓ -
uefi-fw-tools 1.5.4-0.7.2+git 18 stable canonical✓ -
wifi-ap 30 355 stable canonical✓ -
wpa-supplicant 2.4.4 53 stable canonical✓ -

While I haven't reproduced the entire problem (i.e. /writable --> 100%) I did confirm that the script used to trigger a restart doesn't work on my Dell 3000.

Here's the contents of the script (/usr/lib/rsyslog/rsyslog-rotate) in question:

$ cat /usr/lib/rsyslog/rsyslog-rotate
#!/bin/sh

if [ -d /run/systemd/system ]; then
    systemctl kill -s HUP rsyslog.service
else
    invoke-rc.d rsyslog rotate > /dev/null
fi

Since the directory /run/systemd/system exists, the first command is run, which fails actually trigger a restart of rsyslogd. Here's my test:

admin@C2112XX:/run/systemd$ systemctl status rsyslog.service
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2020-03-25 15:45:04 UTC; 2h 31min ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
 Main PID: 1948 (rsyslogd)
   CGroup: /system.slice/rsyslog.service
           └─1948 /usr/sbin/rsyslogd -n
admin@C2112XX:/run/systemd$ sudo systemctl kill -s HUP rsyslog.service
admin@C2112XX:/run/systemd$ systemctl status rsyslog.service
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2020-03-25 15:45:04 UTC; 2h 31min ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
 Main PID: 1948 (rsyslogd)
   CGroup: /system.slice/rsyslog.service
           └─1948 /usr/sbin/rsyslogd -n

The snaps on this system are: