Description of problem: I am using shinken and with mageia 7, I have the following warning : [/usr/lib/tmpfiles.d/shinken.conf:1] Line references path below legacy directory /var/run/, updating /var/run/shinken → /run/shinken; please update the tmpfiles.d/ drop-in file accordingly. the path was changed from /var/run to /run in mageia 7 it is the same kind of warning as https://bugs.mageia.org/show_bug.cgi?id=25598 Version-Release number of selected component (if applicable): shinken-2.4.3-2.mga7 How reproducible: every time Steps to Reproduce: 1. 2. 3.
Assigning to QA, Advisory: ======================== Since latest systemd tmpfiles dir was moved from /var/run to /run, so this update fixes the tmpfiles location in our shinken package. ======================== Packages in 7/core/updates_testing: ======================== shinken-2.4.3-2.1.mga7.noarch.rpm shinken-arbiter-2.4.3-2.1.mga7.noarch.rpm shinken-reactionner-2.4.3-2.1.mga7.noarch.rpm shinken-scheduler-2.4.3-2.1.mga7.noarch.rpm shinken-poller-2.4.3-2.1.mga7.noarch.rpm shinken-broker-2.4.3-2.1.mga7.noarch.rpm shinken-receiver-2.4.3-2.1.mga7.noarch.rpm Source RPM: ======================== shinken-2.4.3-2.1.mga7.src.rpm
CC: (none) => geiger.david68210Assignee: bugsquad => qa-bugs
Mageia7, x86_64 See https://shinken.readthedocs.io/en/2.2/ installed the release packages and ran this to enable shinken services: $ su - # for i in arbiter poller reactionner scheduler broker receiver; do systemctl enable shinken-$i.service; done That seemed to work OK. # systemctl start shinken-scheduler # systemctl status shinken-scheduler ● shinken-scheduler.service - Shinken Scheduler Loaded: loaded (/usr/lib/systemd/system/shinken-scheduler.service; enabled; > Active: active (running) since Mon 2019-11-04 18:31:22 GMT; 10s ago Process: 23215 ExecStart=/usr/sbin/shinken-scheduler -d -c /etc/shinken/daemo> [...] # systemctl stop shinken-scheduler Not intending to learn how to run this system. It runs anyway, before the update. $ cat /usr/lib/tmpfiles.d/shinken.conf d /var/run/shinken 710 shinken shinken Ran the updates, enabled the services and ran a startup loop on all the shinken services. # for i in arbiter poller reactionner scheduler broker receiver; do systemctl start shinken-$i.service; done; # systemctl status shinken-reactionner ● shinken-reactionner.service - Shinken Reactionner Loaded: loaded (/usr/lib/systemd/system/shinken-reactionner.service; enabled> Active: active (running) since Mon 2019-11-04 18:42:41 GMT; 1min 44s ago cat /usr/lib/tmpfiles.d/shinken.conf d /var/run/shinken 710 shinken shinken Ran the updates, enabled the services and ran a startup loop on all the shinken services. # for i in arbiter poller reactionner scheduler broker receiver; do systemctl start shinken-$i.service; done; # systemctl status shinken-reactionner ● shinken-reactionner.service - Shinken Reactionner Loaded: loaded (/usr/lib/systemd/system/shinken-reactionner.service; enabled> Active: active (running) since Mon 2019-11-04 18:42:41 GMT; 1min 44s ago $ cat /usr/lib/tmpfiles.d/shinken.conf d /run/shinken 710 shinken shinken Good enough for a 64-bit OK. The services start and the repair has been effected.
Whiteboard: (none) => MGA7-64-OKCC: (none) => tarazed25
Validating. Advisory in Comment 1.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => advisoryCC: (none) => tmb
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2019-0200.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED