Bug 1437065
Summary: | CUPS does not recognize changes to /etc/resolv.conf until CUPS restart | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Zdenek Dohnal <zdohnal> |
Component: | cups | Assignee: | Zdenek Dohnal <zdohnal> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 25 | CC: | ashankar, codonell, fweimer, jean-luc.richier, jeischma, jpopelka, mdshaikh, mnewsome, pfrankli, psklenar, qe-baseos-daemons, redhat-bugzilla, thozza, twaugh, zdohnal |
Target Milestone: | --- | Keywords: | Patch, Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | cups-2.2.0-6.fc25 cups-2.2.2-3.fc26 cups-2.2.0-8.fc25 cups-2.2.2-5.fc26 cups-2.1.4-6.fc24 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1325692 | Environment: | |
Last Closed: | 2017-04-09 02:54:32 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Comment 1
Fedora Update System
2017-03-30 11:51:57 UTC
cups-2.2.0-6.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-aaa2f5c814 cups-2.2.2-3.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cb1c7c3146 cups-2.2.2-3.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cb1c7c3146 cups-2.1.4-4.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-af9f3f0102 cups-2.2.0-6.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-aaa2f5c814 cups-2.2.0-6.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. cups-2.2.2-3.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. cups-2.1.4-4.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-af9f3f0102 cups-2.1.4-4.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-af9f3f0102 (In reply to Fedora Update System from comment #7) > cups-2.2.0-6.fc25 has been pushed to the Fedora 25 stable repository. If > problems still persist, please make note of it in this bug report. On my Fedora 25 x86_64 system, I have cups-2.2.0-6.fc25.x86_64 and can confirm the bug is still there. In fact, I only encountered this bug report because I was Googling the problem, which only came to my attention on this machine yesterday. It is strange, because I had no problem previously and I have not run a system update since Saturday afternoon Australian time. (In reply to Doug Hutcheson from comment #11) > (In reply to Fedora Update System from comment #7) > > cups-2.2.0-6.fc25 has been pushed to the Fedora 25 stable repository. If > > problems still persist, please make note of it in this bug report. > > On my Fedora 25 x86_64 system, I have cups-2.2.0-6.fc25.x86_64 and can > confirm the bug is still there. In fact, I only encountered this bug report > because I was Googling the problem, which only came to my attention on this > machine yesterday. > > It is strange, because I had no problem previously and I have not run a > system update since Saturday afternoon Australian time. Ignore me - I replied to the wrong bug report. Humble apologies. I can also confirm there is still a problem. CUPS fails to start at boot, but it's somehow started and running when I check it afterwards. Nevertheless cups-browsed fails to start at boot because cups as its dependency failed to start and it stays that way until you manually restart it. Thanks Jirka and Doug, I will look into it. cups-2.1.4-5.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-19ab04c1b9 (In reply to Jiri Eischmann from comment #13) > I can also confirm there is still a problem. CUPS fails to start at boot, > but it's somehow started and running when I check it afterwards. > Nevertheless cups-browsed fails to start at boot because cups as its > dependency failed to start and it stays that way until you manually restart > it. I have the same problem using cups-2.2.0-6.fc25.x86_64 : cups fails at boot time, withe message cupsd[991]: cupsd: Cannot get a status of /etc/resolv.conf and therefore the dependency cups-browsed fails to start at boot To solve the problem, I modified /lib/systemd/system/cups.service to wait for the activation of NetworkManager diff /lib/systemd/system/cups.service.DIST /lib/systemd/system/cups.service 4c4 < After=network.target --- > After=network-online.target NetworkManager-wait-online.service (In reply to Need Real Name from comment #16) > I have the same problem using cups-2.2.0-6.fc25.x86_64 : cups fails at boot > time, > with message > cupsd[991]: cupsd: Cannot get a status of /etc/resolv.conf I installed cups-2.2.0-7.fc25.x86_64 and it solves the problem Yes, it solves problem, but I removed that patch only temporarily until I fix this issue. Your solution will delay boot process for 90s if network-online.target fails. IMHO it is not the way it should be solved. Issue is with cups.service, which tries to start when network.target is completed, but network.target completion doesn't guarantee that /etc/resolv.conf exists. I'll try to do stat call later in daemon, when /etc/resolv.conf could exist. Ad comment #18: After some time CUPS restarts, but cups-browsed, which depends on CUPS, will not restart and stays dead from boot time. cups-2.1.4-5.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-19ab04c1b9 *** Bug 1439124 has been marked as a duplicate of this bug. *** cups-2.1.4-6.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-61498b10c5 cups-2.2.0-8.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-37931b24eb cups-2.2.2-5.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-81ec2a7046 Issue should be fixed with 2.1.4-6.fc24, 2.2.0-8.fc25, 2.2.2-5.fc26 and 2.2.3-4.fc27 releases. It contains again cups-resolv_reload.patch, which now does following: - when /etc/resolv.conf doesn't exist, it tries to reload resolver with local nameserver (more info in 'man resolv.conf'). - when even reloading resolver with local nameserver fails, function httpCheckResolv returns error, which is checked in cupsd main function - it only prints message to stderr about "Cannot reload resolver - using old configuration" - and no hard exit I tested it in my F25, no error mesages for CUPS and cups-browsed service is still running. Purpose of cups-resolv_reload.patch is to make CUPS recognize changes of nameserver IP's configuration without CUPS restart. This patch is only temporary workaround until glibc doesn't fix issue with dynamically changing nameservers IP configuration. Please check if this feature works too (it should be, I tested it too). cups-2.1.4-6.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-61498b10c5 cups-2.2.0-8.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-37931b24eb cups-2.2.2-5.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-81ec2a7046 cups-2.2.0-8.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. cups-2.2.2-5.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. cups-2.1.4-6.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report. |