[opensuse-factory] rsyslogd is not stopped on package uninstall
Using openSUSE 12.3 here. When I replace rsyslog with systemd's journal $ sudo zypper -v in systemd-logger -rsyslog -syslog-service the rsyslogd daemon keeps running after the package uninstall. Is this right? Should not RPM %service_del_preun macro run "systemctl stop" on it? Zypper output: Verbosity: 1 Non-option program arguments: 'systemd-logger' '-rsyslog' '-syslog-service' Initializing Target Checking whether to refresh metadata for openSUSE-12.3-Non-Oss Checking whether to refresh metadata for openSUSE-12.3-Oss Checking whether to refresh metadata for openSUSE-12.3-Update Checking whether to refresh metadata for openSUSE-12.3-Update-Non-Oss Loading repository data... Reading installed packages... Force resolution: No Selecting 'systemd-logger-195-13.18.1.x86_64' from repository 'openSUSE-12.3-Update' for installation. Selecting 'rsyslog-7.2.5-2.2.1.x86_64' for removal. Selecting 'syslog-service-2.0-768.2.1.noarch' for removal. Resolving package dependencies... Force resolution: No The following NEW package is going to be installed: systemd-logger 195-13.18.1 The following packages are going to be REMOVED: rsyslog 7.2.5-2.2.1 syslog-service 2.0-768.2.1 1 new package to install, 2 to remove. Overall download size: 90.7 KiB. After the operation, 1.8 MiB will be freed. Continue? [y/n/?] (y): committing Retrieving package systemd-logger-195-13.18.1.x86_64 (1/1), 90.7 KiB ( 1.6 KiB unpacked) Retrieving: systemd-logger-195-13.18.1.x86_64.rpm [.done] (1/3) Installing: systemd-logger-195-13.18.1 [......done] (2/3) Removing rsyslog-7.2.5-2.2.1 [....done] (3/3) Removing syslog-service-2.0-768.2.1 [....done] committingCommitResult (total 3, done 3, error 0, skipped 0, updateMessages 0) Checking for running processes using deleted libraries... There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs. $ sudo zypper ps The following running processes use deleted files: PID | PPID | UID | Login | Command | Service | Files -----+------+-----+-------+---------+---------+------------------------------- 1522 | 0 | 0 | root | rs:main | | /usr/lib64/rsyslog/lmnet.so | | | | | | /usr/lib64/rsyslog/immark.so | | | | | | /usr/lib64/rsyslog/imuxsock.so | | | | | | /usr/lib64/rsyslog/imklog.so | | | | | | /usr/sbin/rsyslogd (deleted) You may wish to restart these processes. See 'man zypper' for information about the meaning of values in the above table. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 15/04/13 09:52, Marcos Felipe Rasia de Mello escribió:
Using openSUSE 12.3 here. When I replace rsyslog with systemd's journal
$ sudo zypper -v in systemd-logger -rsyslog -syslog-service
the rsyslogd daemon keeps running after the package uninstall. Is this right? Should not RPM %service_del_preun macro run "systemctl stop" on it?
The spec file says it does..(at least the current one in factory) preuninstall scriptlet (using /bin/sh): # # stop the rsyslogd daemon when it is running # test -n "$FIRST_ARG" || FIRST_ARG=$1 if [ $FIRST_ARG -eq 0 ]; then # Package removal, not upgrade /usr/bin/systemctl --no-reload disable rsyslog.service > /dev/null 2>&1 || : /usr/bin/systemctl stop rsyslog.service > /dev/null 2>&1 || : fi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2013/4/16 Cristian Rodríguez <crrodriguez@opensuse.org>:
El 15/04/13 09:52, Marcos Felipe Rasia de Mello escribió:
Using openSUSE 12.3 here. When I replace rsyslog with systemd's journal
$ sudo zypper -v in systemd-logger -rsyslog -syslog-service
the rsyslogd daemon keeps running after the package uninstall. Is this right? Should not RPM %service_del_preun macro run "systemctl stop" on it?
The spec file says it does..(at least the current one in factory)
preuninstall scriptlet (using /bin/sh): # # stop the rsyslogd daemon when it is running #
test -n "$FIRST_ARG" || FIRST_ARG=$1 if [ $FIRST_ARG -eq 0 ]; then # Package removal, not upgrade /usr/bin/systemctl --no-reload disable rsyslog.service > /dev/null 2>&1 || : /usr/bin/systemctl stop rsyslog.service > /dev/null 2>&1 || : fi
Did some testing with "systemd.debug_level=debug". systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.RestartUnit() on /org/freedesktop/systemd1 systemd[1]: Trying to enqueue job systemd-journal-flush.service/restart/replace systemd[1]: Installed new job systemd-journal-flush.service/restart as 404 systemd[1]: Enqueued job systemd-journal-flush.service/restart as 404 systemd[1]: Job systemd-journal-flush.service/restart finished, result=done systemd[1]: Converting job systemd-journal-flush.service/restart -> systemd-journal-flush.service/start systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... systemd[1]: About to execute /usr/bin/systemctl kill --kill-who=main --signal=SIGUSR1 systemd-journald.service systemd[1]: Forked /usr/bin/systemctl as 1394 systemd[1]: systemd-journal-flush.service changed dead -> start systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.GetUnit() on /org/freedesktop/systemd1 systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.KillUnit() on /org/freedesktop/systemd1 systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Received SIGCHLD from PID 1394 (systemctl). systemd[1]: Got SIGCHLD for process 1394 (systemctl) systemd[1]: Child 1394 died (code=exited, status=0/SUCCESS) systemd[1]: Child 1394 belongs to systemd-journal-flush.service systemd[1]: systemd-journal-flush.service: main process exited, code=exited, status=0/SUCCESS systemd[1]: systemd-journal-flush.service changed start -> dead systemd[1]: Job systemd-journal-flush.service/start finished, result=done systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.Get() on /org/freedesktop/systemd1/unit/systemd_2djournal_2dflush_2eservice systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent systemd[1]: systemd-journal-flush.service: cgroup is empty systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd-journal[245]: Allowing system journal files to grow to 4.0G. systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.DisableUnitFiles() on /org/freedesktop/systemd1 systemd[1]: Looking for unit files in: systemd[1]: /etc/systemd/system systemd[1]: /usr/lib/systemd/system systemd[1]: Looking for SysV init scripts in: systemd[1]: /etc/init.d systemd[1]: Looking for SysV rcN.d links in: systemd[1]: /etc/init.d systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.StopUnit() on /org/freedesktop/systemd1 systemd[1]: Trying to enqueue job rsyslog.service/stop/replace systemd[1]: Installed new job rsyslog.service/stop as 408 systemd[1]: Enqueued job rsyslog.service/stop as 408 systemd[1]: Stopping System Logging Service... systemd[1]: syslog.socket got notified about service death (failed permanently: no) systemd[1]: syslog.socket changed running -> listening systemd[1]: rsyslog.service changed running -> stop-sigterm systemd[1]: Incoming traffic on syslog.socket systemd[1]: Trying to enqueue job rsyslog.service/start/replace systemd[1]: Job rsyslog.service/stop finished, result=canceled systemd[1]: Installed new job rsyslog.service/start as 409 systemd[1]: Enqueued job rsyslog.service/start as 409 systemd[1]: Received SIGCHLD from PID 418 (rsyslogd). systemd[1]: syslog.socket got notified about service death (failed permanently: no) systemd[1]: Starting System Logging Service... systemd[1]: About to execute /usr/sbin/rsyslog-service-prepare systemd[1]: Forked /usr/sbin/rsyslog-service-prepare as 1402 systemd[1]: rsyslog.service changed dead -> start-pre systemd[1]: Incoming traffic on syslog.socket systemd[1]: syslog.socket changed listening -> running systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.Get() on /org/freedesktop/systemd1/unit/rsyslog_2eservice systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Received SIGCHLD from PID 1402 (rsyslog-service). systemd[1]: Got SIGCHLD for process 1402 (rsyslog-service) systemd[1]: Child 1402 died (code=exited, status=0/SUCCESS) systemd[1]: Child 1402 belongs to rsyslog.service systemd[1]: rsyslog.service: control process exited, code=exited status=0 systemd-journal[245]: Forwarding to syslog missed 19 messages. systemd[1]: syslog.socket changed listening -> running systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.GetUnit() on /org/freedesktop/systemd1 systemd[1]: Got SIGCHLD for process 418 (rsyslogd) systemd[1]: Child 418 died (code=exited, status=0/SUCCESS) systemd[1]: Child 418 belongs to rsyslog.service systemd[1]: syslog.socket changed running -> listening systemd[1]: rsyslog.service got final SIGCHLD for state start-pre systemd[1]: About to execute /usr/sbin/rsyslogd -n $RSYSLOGD_PARAMS systemd[1]: Forked /usr/sbin/rsyslogd as 1407 systemd[1]: rsyslog.service changed start-pre -> running systemd[1]: Job rsyslog.service/start finished, result=done systemd[1]: Started System Logging Service. systemd[1]: Accepted connection on private bus. systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.Reload() on /org/freedesktop/systemd1 systemd[1]: Reloading. systemd[1]: Serializing state to /run/systemd/dump-1-Z9psIk systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-rc-local-generator as 1416 systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-system-update-generator as 1417 systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-getty-generator as 1418 systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-fstab-generator as 1419 systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-cryptsetup-generator as 1420 systemd[1]: /usr/lib/systemd/system-generators/systemd-rc-local-generator exited successfully. systemd[1]: /usr/lib/systemd/system-generators/systemd-system-update-generator exited successfully. systemd[1]: /usr/lib/systemd/system-generators/systemd-getty-generator exited successfully. systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited successfully. systemd[1]: /usr/lib/systemd/system-generators/systemd-cryptsetup-generator exited successfully. systemd[1]: Looking for unit files in: systemd[1]: /etc/systemd/system systemd[1]: /run/systemd/generator systemd[1]: /usr/lib/systemd/system systemd[1]: Looking for SysV init scripts in: systemd[1]: /etc/init.d systemd[1]: Looking for SysV rcN.d links in: systemd[1]: /etc/init.d systemd[1]: Failed to load configuration for nfsserver.service: No such file or directory systemd[1]: Failed to load configuration for ypserv.service: No such file or directory systemd[1]: Failed to load configuration for basic.service: No such file or directory systemd[1]: Failed to load configuration for auditd.service: No such file or directory systemd[1]: Failed to load configuration for scsidev.service: No such file or directory systemd[1]: Failed to load configuration for multipath.service: No such file or directory systemd[1]: Failed to load configuration for udev-trigger.service: No such file or directory systemd[1]: Failed to load configuration for apparmor.service: No such file or directory systemd[1]: Failed to load configuration for syslog.service: No such file or directory systemd[1]: Failed to load configuration for network-remotefs.service: No such file or directory systemd[1]: Failed to load configuration for acpid.service: No such file or directory systemd[1]: Failed to load configuration for winbind.service: No such file or directory systemd[1]: Failed to load configuration for resmgr.service: No such file or directory systemd[1]: Failed to load configuration for firstboot.service: No such file or directory systemd[1]: Failed to load configuration for local_fs.target: No such file or directory systemd[1]: Failed to load configuration for exim.service: No such file or directory systemd[1]: Failed to load configuration for sendmail.service: No such file or directory systemd[1]: Failed to load configuration for openslp.service: No such file or directory systemd[1]: Failed to load configuration for ldap.service: No such file or directory systemd[1]: Failed to load configuration for cyrus.service: No such file or directory systemd[1]: Failed to load configuration for amavis.service: No such file or directory systemd[1]: Failed to load configuration for lwresd.service: No such file or directory systemd[1]: Deserializing state... systemd[1]: Failed to load configuration for rsyslog.service: No such file or directory systemd[1]: Failed to load configuration for syslog-ng.service: No such file or directory systemd[1]: Failed to load configuration for syslogd.service: No such file or directory And now pid 1407 is a ghost... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 16/04/13 19:08, Marcos Felipe Rasia de Mello escribió:
systemd[1]: Trying to enqueue job rsyslog.service/stop/replace systemd[1]: Installed new job rsyslog.service/stop as 408 systemd[1]: Enqueued job rsyslog.service/stop as 408 systemd[1]: Stopping System Logging Service... systemd[1]: syslog.socket got notified about service death (failed permanently: no) systemd[1]: syslog.socket changed running -> listening systemd[1]: rsyslog.service changed running -> stop-sigterm systemd[1]: Incoming traffic on syslog.socket systemd[1]: Trying to enqueue job rsyslog.service/start/replace systemd[1]: Job rsyslog.service/stop finished, result=canceled systemd[1]: Installed new job rsyslog.service/start as 409 systemd[1]: Enqueued job rsyslog.service/start as 409 systemd[1]: Received SIGCHLD from PID 418 (rsyslogd). systemd[1]: syslog.socket got notified about service death (failed permanently: no) systemd[1]: Starting System Logging Service... systemd[1]: About to execute /usr/sbin/rsyslog-service-prepare systemd[1]: Forked /usr/sbin/rsyslog-service-prepare as 1402 systemd[1]: rsyslog.service changed dead -> start-pre systemd[1]: Incoming traffic on syslog.socket systemd[1]: syslog.socket changed listening -> running systemd[1]: Accepted connection on private bus. systemd[1]: Received SIGCHLD from PID 1402 (rsyslog-service). systemd[1]: Got SIGCHLD for process 1402 (rsyslog-service) systemd[1]: Child 1402 died (code=exited, status=0/SUCCESS) systemd[1]: Child 1402 belongs to rsyslog.service systemd[1]: rsyslog.service: control process exited, code=exited status=0 systemd-journal[245]: Forwarding to syslog missed 19 messages. systemd[1]: syslog.socket changed listening -> running systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.GetUnit() on /org/freedesktop/systemd1 systemd[1]: Got SIGCHLD for process 418 (rsyslogd) systemd[1]: Child 418 died (code=exited, status=0/SUCCESS) systemd[1]: Child 418 belongs to rsyslog.service systemd[1]: syslog.socket changed running -> listening systemd[1]: rsyslog.service got final SIGCHLD for state start-pre systemd[1]: About to execute /usr/sbin/rsyslogd -n $RSYSLOGD_PARAMS systemd[1]: Forked /usr/sbin/rsyslogd as 1407 systemd[1]: rsyslog.service changed start-pre -> running systemd[1]: Job rsyslog.service/start finished, result=done
And now pid 1407 is a ghost...
Can you reproduce this behaviour with *current* rsyslog from Base:System ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2013/4/16 Cristian Rodríguez <crrodriguez@opensuse.org>:
El 16/04/13 19:08, Marcos Felipe Rasia de Mello escribió: <snip>
And now pid 1407 is a ghost...
Can you reproduce this behaviour with *current* rsyslog from Base:System ?
I can try. But will it make a difference? The only change is related to SELinux: https://build.opensuse.org/package/revisions?package=rsyslog&project=openSUSE%3AFactory -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El mar 16 abr 2013 20:15:16 CLST, Marcos Felipe Rasia de Mello escribió:
2013/4/16 Cristian Rodríguez <crrodriguez@opensuse.org>:
El 16/04/13 19:08, Marcos Felipe Rasia de Mello escribió: <snip>
And now pid 1407 is a ghost...
Can you reproduce this behaviour with *current* rsyslog from Base:System ?
I can try. But will it make a difference?
The only change is related to SELinux: https://build.opensuse.org/package/revisions?package=rsyslog&project=openSUSE%3AFactory
You are looking at openSUSE:Factory but I told you to look at Base:System ;) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2013/4/16 Cristian Rodríguez <crrodriguez@opensuse.org>:
El mar 16 abr 2013 20:15:16 CLST, Marcos Felipe Rasia de Mello escribió:
2013/4/16 Cristian Rodríguez <crrodriguez@opensuse.org>:
El 16/04/13 19:08, Marcos Felipe Rasia de Mello escribió:
<snip>
And now pid 1407 is a ghost...
Can you reproduce this behaviour with *current* rsyslog from Base:System ?
I can try. But will it make a difference?
The only change is related to SELinux:
https://build.opensuse.org/package/revisions?package=rsyslog&project=openSUSE%3AFactory
You are looking at openSUSE:Factory but I told you to look at Base:System ;)
Sorry. I'm an openSUSE newbie. :) Yes, same issue with rsyslog-7.2.5-138.1.x86_64. systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.RestartUnit() on /org/freedesktop/systemd1 systemd[1]: Trying to enqueue job systemd-journal-flush.service/restart/replace systemd[1]: Installed new job systemd-journal-flush.service/restart as 404 systemd[1]: Enqueued job systemd-journal-flush.service/restart as 404 systemd[1]: Job systemd-journal-flush.service/restart finished, result=done systemd[1]: Converting job systemd-journal-flush.service/restart -> systemd-journal-flush.service/start systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... systemd[1]: About to execute /usr/bin/systemctl kill --kill-who=main --signal=SIGUSR1 systemd-journald.service systemd[1]: Forked /usr/bin/systemctl as 1387 systemd[1]: systemd-journal-flush.service changed dead -> start systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.GetUnit() on /org/freedesktop/systemd1 systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.KillUnit() on /org/freedesktop/systemd1 systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.Get() on /org/freedesktop/systemd1/unit/systemd_2djournal_2dflush_2eservice systemd[1]: Received SIGCHLD from PID 1387 (systemctl). systemd[1]: Got SIGCHLD for process 1387 (systemctl) systemd[1]: systemd-journal-flush.service changed start -> dead systemd-journal[253]: Allowing system journal files to grow to 4.0G. systemd[1]: Child 1387 died (code=exited, status=0/SUCCESS) systemd[1]: Job systemd-journal-flush.service/start finished, result=done systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent systemd[1]: systemd-journal-flush.service: cgroup is empty systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Child 1387 belongs to systemd-journal-flush.service systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.DisableUnitFiles() on /org/freedesktop/systemd1 systemd[1]: Looking for unit files in: systemd[1]: /etc/systemd/system systemd[1]: /usr/lib/systemd/system systemd[1]: Looking for SysV init scripts in: systemd[1]: /etc/init.d systemd[1]: Looking for SysV rcN.d links in: systemd[1]: /etc/init.d systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.StopUnit() on /org/freedesktop/systemd1 systemd[1]: Trying to enqueue job rsyslog.service/stop/replace systemd[1]: Installed new job rsyslog.service/stop as 408 systemd[1]: Enqueued job rsyslog.service/stop as 408 systemd[1]: Stopping System Logging Service... systemd[1]: syslog.socket got notified about service death (failed permanently: no) systemd[1]: syslog.socket changed running -> listening systemd[1]: rsyslog.service changed running -> stop-sigterm systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.GetUnit() on /org/freedesktop/systemd1 systemd[1]: Incoming traffic on syslog.socket systemd[1]: Trying to enqueue job rsyslog.service/start/replace systemd[1]: syslog.socket got notified about service death (failed permanently: no) systemd[1]: Starting System Logging Service... systemd[1]: About to execute /usr/sbin/rsyslog-service-prepare systemd[1]: Forked /usr/sbin/rsyslog-service-prepare as 1394 systemd[1]: rsyslog.service changed dead -> start-pre systemd[1]: Incoming traffic on syslog.socket systemd[1]: syslog.socket changed listening -> running systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Received SIGCHLD from PID 1394 (rsyslog-service). systemd[1]: Got SIGCHLD for process 1394 (rsyslog-service) systemd[1]: Child 1394 died (code=exited, status=0/SUCCESS) systemd[1]: Child 1394 belongs to rsyslog.service systemd[1]: rsyslog.service: control process exited, code=exited status=0 systemd[1]: rsyslog.service got final SIGCHLD for state start-pre systemd[1]: About to execute /usr/sbin/rsyslogd -n $RSYSLOGD_PARAMS systemd[1]: Forked /usr/sbin/rsyslogd as 1398 systemd[1]: rsyslog.service changed start-pre -> running systemd[1]: Job rsyslog.service/start finished, result=done systemd[1]: Started System Logging Service. systemd[1]: Accepted connection on private bus. systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd-journal[253]: Forwarding to syslog missed 17 messages. systemd[1]: Job rsyslog.service/stop finished, result=canceled systemd[1]: Installed new job rsyslog.service/start as 409 systemd[1]: Enqueued job rsyslog.service/start as 409 systemd[1]: syslog.socket changed listening -> running systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.Get() on /org/freedesktop/systemd1/unit/rsyslog_2eservice systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Received SIGCHLD from PID 465 (rsyslogd). systemd[1]: Got SIGCHLD for process 465 (rsyslogd) systemd[1]: Child 465 died (code=exited, status=0/SUCCESS) systemd[1]: Child 465 belongs to rsyslog.service systemd[1]: syslog.socket changed running -> listening systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local systemd[1]: Accepted connection on private bus. systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.Reload() on /org/freedesktop/systemd1 systemd[1]: Reloading. Btw, the correct option is "systemd.log_level=debug". -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 16/04/13 21:11, Marcos Felipe Rasia de Mello escribió:
systemd[1]: Trying to enqueue job rsyslog.service/stop/replace systemd[1]: Installed new job rsyslog.service/stop as 408 systemd[1]: Enqueued job rsyslog.service/stop as 408 systemd[1]: Stopping System Logging Service...
OK, trying to stop... # Package removal, not upgrade /usr/bin/systemctl --no-reload disable rsyslog.service > /dev/null 2>&1 || : /usr/bin/systemctl stop rsyslog.service > /dev/null 2>&1 || : --> here...
systemd[1]: syslog.socket got notified about service death (failed permanently: no) systemd[1]: syslog.socket changed running -> listening
waiting for requests on the socket, as expected..
systemd[1]: rsyslog.service changed running -> stop-sigterm
stop signal sent..(most deamons catch signals to do house keeping before going away..) buuuuut units still there, systemd has been told by rpm post scriptlets not to reload its configuration on disable.. hahah! <evil grin> (drum roll)
systemd[1]: Incoming traffic on syslog.socket
Still sending data...nothing wrong with that but...
systemd[1]: Trying to enqueue job rsyslog.service/start/replace systemd[1]: syslog.socket got notified about service death (failed permanently: no)
As --no-reload was passed, systemd assumes that "you know what are you doing" you decided not to provide it "fresh" information about the fact there is no syslog implementation anymore..it tries to do what it should.. ta dah! FAIL. :D For this particular case --no-reload is not adequate.. but rpm scriptlets are generic ;) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04/16/2013 09:11 PM, Marcos Felipe Rasia de Mello wrote:
Btw, the correct option is "systemd.log_level=debug".
btw, what you sent to me was part of the output of journalctl right ? if not, there is no warranty of messages showing up in order the order they were emitted... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2013/4/16 Cristian Rodríguez <crrodriguez@opensuse.org>:
On 04/16/2013 09:11 PM, Marcos Felipe Rasia de Mello wrote:
Btw, the correct option is "systemd.log_level=debug".
btw, what you sent to me was part of the output of journalctl right ? if not, there is no warranty of messages showing up in order the order they were emitted...
Yes, I just removed an unrelated kernel message that got interleaved. Thanks for the analysis! Should I report a bug? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04/16/2013 11:25 PM, Marcos Felipe Rasia de Mello wrote:
Thanks for the analysis! Should I report a bug?
This is certainly a misbehaviour, what I am not convinced is what to do about it if anything. In this case systemd is just doing what it is told to do by the rpm macros.. there are a few alternatives to address this: - make systemctl to ignore --no-reload on case disable when the service or alias to service to be disabled is bound to a socket unit, the ramifications of doing this are not clear to me at the moment. - add a new macro service_del_preun_with_reload just for the few packages that use socket activation. - do nothing unless it causes a permanent functionality loss, other system component to go crazy or breaks update/upgrade even after reboot. Also consider that this happends in the time window between rpm %preun where /usr/bin/systemctl --no-reload disable .. is called,,, and %postun (where systemctl daemon-reload is executed and therefore knows the system configuration has changed) Frederic ..what you think about this? none of the options sound appealing to me at this stage.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mercredi 17 avril 2013 à 00:52 -0300, Cristian Rodríguez a écrit :
On 04/16/2013 11:25 PM, Marcos Felipe Rasia de Mello wrote:
Thanks for the analysis! Should I report a bug?
This is certainly a misbehaviour, what I am not convinced is what to do about it if anything.
In this case systemd is just doing what it is told to do by the rpm macros.. there are a few alternatives to address this:
- make systemctl to ignore --no-reload on case disable when the service or alias to service to be disabled is bound to a socket unit, the ramifications of doing this are not clear to me at the moment.
- add a new macro service_del_preun_with_reload just for the few packages that use socket activation.
- do nothing unless it causes a permanent functionality loss, other system component to go crazy or breaks update/upgrade even after reboot.
Also consider that this happends in the time window between rpm %preun where /usr/bin/systemctl --no-reload disable .. is called,,, and %postun (where systemctl daemon-reload is executed and therefore knows the system configuration has changed)
Frederic ..what you think about this? none of the options sound appealing to me at this stage..
Well, on the RPM macro front, I'd like us to merge our macros with upstream RPM systemd macros (unfortunately, they didn't use exactly the same implementation and names but we can probably handle a transition and still ship both our and upstream macros and make sure they do the same thing). Once we merged them, it would be a matter to be discussed with upstream to see how to handle this particular topic (I don't think it is handled properly by upstream RPM macros either but I might be wrong) by opening a bug to them. In any case, I would suggest to open a bug report so it isn't lost.. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2013/4/18 Frederic Crozat <fcrozat@suse.com>:
Le mercredi 17 avril 2013 à 00:52 -0300, Cristian Rodríguez a écrit :
On 04/16/2013 11:25 PM, Marcos Felipe Rasia de Mello wrote:
Thanks for the analysis! Should I report a bug?
This is certainly a misbehaviour, what I am not convinced is what to do about it if anything.
In this case systemd is just doing what it is told to do by the rpm macros.. there are a few alternatives to address this:
- make systemctl to ignore --no-reload on case disable when the service or alias to service to be disabled is bound to a socket unit, the ramifications of doing this are not clear to me at the moment.
- add a new macro service_del_preun_with_reload just for the few packages that use socket activation.
- do nothing unless it causes a permanent functionality loss, other system component to go crazy or breaks update/upgrade even after reboot.
Also consider that this happends in the time window between rpm %preun where /usr/bin/systemctl --no-reload disable .. is called,,, and %postun (where systemctl daemon-reload is executed and therefore knows the system configuration has changed)
Frederic ..what you think about this? none of the options sound appealing to me at this stage..
Well, on the RPM macro front, I'd like us to merge our macros with upstream RPM systemd macros (unfortunately, they didn't use exactly the same implementation and names but we can probably handle a transition and still ship both our and upstream macros and make sure they do the same thing).
Once we merged them, it would be a matter to be discussed with upstream to see how to handle this particular topic (I don't think it is handled properly by upstream RPM macros either but I might be wrong) by opening a bug to them.
In any case, I would suggest to open a bug report so it isn't lost..
Upstream macros have other names, but systemctl invocations are the same. Here's the bug report: https://bugs.freedesktop.org/show_bug.cgi?id=63735 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le vendredi 19 avril 2013 à 14:43 -0300, Marcos Felipe Rasia de Mello a écrit :
2013/4/18 Frederic Crozat <fcrozat@suse.com>:
Le mercredi 17 avril 2013 à 00:52 -0300, Cristian Rodríguez a écrit :
On 04/16/2013 11:25 PM, Marcos Felipe Rasia de Mello wrote:
Thanks for the analysis! Should I report a bug?
This is certainly a misbehaviour, what I am not convinced is what to do about it if anything.
In this case systemd is just doing what it is told to do by the rpm macros.. there are a few alternatives to address this:
- make systemctl to ignore --no-reload on case disable when the service or alias to service to be disabled is bound to a socket unit, the ramifications of doing this are not clear to me at the moment.
- add a new macro service_del_preun_with_reload just for the few packages that use socket activation.
- do nothing unless it causes a permanent functionality loss, other system component to go crazy or breaks update/upgrade even after reboot.
Also consider that this happends in the time window between rpm %preun where /usr/bin/systemctl --no-reload disable .. is called,,, and %postun (where systemctl daemon-reload is executed and therefore knows the system configuration has changed)
Frederic ..what you think about this? none of the options sound appealing to me at this stage..
Well, on the RPM macro front, I'd like us to merge our macros with upstream RPM systemd macros (unfortunately, they didn't use exactly the same implementation and names but we can probably handle a transition and still ship both our and upstream macros and make sure they do the same thing).
Once we merged them, it would be a matter to be discussed with upstream to see how to handle this particular topic (I don't think it is handled properly by upstream RPM macros either but I might be wrong) by opening a bug to them.
In any case, I would suggest to open a bug report so it isn't lost..
Upstream macros have other names, but systemctl invocations are the same.
The order is slightly different..
Here's the bug report: https://bugs.freedesktop.org/show_bug.cgi?id=63735
Thanks. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Cristian Rodríguez -
Frederic Crozat -
Marcos Felipe Rasia de Mello