Bug 918631

Those lines are all valid, and the only reason I can see for cupsd not to start is if the mentioned certificate/key files do not exist -- but in that case it should have failed to start before the upgrade as well.

Could you please attach /etc/cups/cupsd.conf?

Created attachment 706196 [details]
This is the cupsd.conf file on the affected desktop unit after the Feb 26 update

Here is the cupsd.conf file on the affected Desktop unit.  I have two other F17 units, and one F18 desktop that did not have this problem, but there was no RPM update at the bottom of their cups-files.conf file.

The certificate files do not exist, and they did not exist before the update

Created attachment 706214 [details]
THis is the original cupsd.conf file before the yum update on 02/26/2013

These were the log entries in the /var/log/messages file:
Mar  5 07:58:26 IrMd systemd[1]: Unit cups.service entered failed state.
Mar  5 07:58:26 IrMd cupsd: Unable to read configuration file - exiting!
Mar  5 07:58:26 IrMd systemd[1]: cups.service: main process exited, code=exited, statu

These were the log entreis in the /var/log/cups/error.log file:

C [05/Mar/2013:17:55:57 -0600] Unable to read /etc/cups/cups-files.conf
E [05/Mar/2013:18:25:18 -0600] File or directory for "ServerCertificate /etc/cups/ssl/

When I commented out the server certificate lines in cups-file.conf I was able to get cups to activate, but lpstat -a would still not give me any list of printers.  When I commented out all of the lines appened to cups-file.conf by RPM then I was able to get lpstat -a to give me a list of printers.

I never had the certificates active even when the old cupsd.conf file had the line items of the certificates active.  It looks to me like the new rev of cups is more sensitive, and less willing to run if things are not set up properly.  This would be a good thing from my point of view.

The file seems to have been migrated correctly -- what seems to have changed is how strictly cupsd handles those particular directives.

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.