Red Hat Bugzilla – Bug 833595
ez-ipupdate missing tmpfiles.d config for PIDs
Last modified: 2013-12-24 21:38:29 EST
Description of problem:
The ez-ipupdate package is missing a tmpfiles.d config file to create it's required /var/run/ez-ipupdate/ directory owned by it's runtime user. Upon reboot the daemon will fail to start since it cannot create it's pidfile which is the name of the conf files (dynamic).
The RPM creates the directory upon install, so the daemon will work initially when first installed, configured and run but fail with the system is rebooted.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install F17
2. Install ez-ipupdate, configure, chkconfig on
ez-ipupdate fails to launch, from syslog:
ez-ipupdate: version 3.0.11b8, interface em1, host XXXXX.dyndns.org, server members.dyndns.org, service dyndns
ez-ipupdate: could not create pid file /var/run/ez-ipupdate/XXXXX.pid (Bad file descriptor), exiting
ez-ipupdate launches and stays running.
Per the guidelines:
$ cat /etc/tmpfiles.d/ez-ipupdate.conf
D /var/run/ez-ipupdate 0755 ez-ipupd ez-ipupd -
Created attachment 597421 [details]
Recreate run dir using tmpfiles.
I have not tested this. Note that this is for the F18 version which has a systemd service file. It probably would work for the older releases too, but it's probably easier to add an mkdir in the init script in those branches.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
ez-ipupdate-3.0.11-0.29.b8.fc20 has been submitted as an update for Fedora 20.
ez-ipupdate-3.0.11-0.29.b8.fc19 has been submitted as an update for Fedora 19.
ez-ipupdate-3.0.11-0.29.b8.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ez-ipupdate-3.0.11-0.29.b8.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
ez-ipupdate-3.0.11-0.29.b8.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
ez-ipupdate-3.0.11-0.29.b8.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
ez-ipupdate-3.0.11-0.29.b8.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.