From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.7.8-1.1.3.1 Description of problem: When I configure the printer options of printer through the cups admin http://localhost:631, I get the error message server-error-service-unavailable instead of a nice configured printer. Version-Release number of selected component (if applicable): cups-1.1.17-13.3.27 How reproducible: Always Steps to Reproduce: 1. download the PPD-file NRG-DSm645-PS.ppd 2. copy the file to the directory /usr/share/cups/model/ 3. restart cups (service cups restart) 4. start http://localhost:631 5. add a printer with the new PPD-file 6. configure some printer options (NOT modify) 7. click continue button Actual Results: Admin Error: server-error-service-unavailable Copyright 1993-2002 Easy Software Products, All Rights Reserved. The Common UNIX Printing System, CUPS, and the CUPS logo are the trademark property of Easy Software Products. All other trademarks are the property of their respective owners. Expected Results: The new printer options should be saved to the PPD-file in the directory /etc/cups/ppd. Additional info: When I try to reproduce this error on a Fedora Core 2 box everythings turns out fine and the configuration is saved correct. So I don't think it is a problem with the specific PPD-file.
What does /var/log/cups/error_log contain at that point?
Created attachment 116048 [details] cups error log
Could you attach the PPD file please?
Created attachment 116049 [details] ppd file
It is possible that this has the same cause as bug #138123. Could you try the test packages I made to address that? They are referenced in bug #138123 comment #69.
1. I stopped cups (service cups stop) 2. I installed the following test packages: ftp://people.redhat.com/twaugh/tmp/cups-rhel3/i386/cups-1.1.17-13.3.27.0.0.6.i386.rpm ftp://people.redhat.com/twaugh/tmp/cups-rhel3/i386/cups-libs-1.1.17-13.3.27.0.0.6.i386.rpm 3. I started cups (service cups start) 4. I deleted my printer definition. 5. I created a new printer Unfortunately my problem still exists.
Same error_log messages? What you can do in that case is the following (as root): mkdir /tmp/cups chmod a+x /tmp/cups touch /tmp/cups/err_output chmod a+w /tmp/cups/err_output service cups restart Please delete the printer definition and re-create it, and then attach /tmp/cups/err_output. Thanks.
Created attachment 116054 [details] err_output
Confirmed -- I see this here with that PPD file too.
This has the same root cause as bug #161952. *** This bug has been marked as a duplicate of 161952 ***
****** ****** ****** See bug #161952 comment #17. Ignore attachments prior to this comment #15. ****** ****** ******
Corne, please provide this information: Version-Release number of selected component Steps to Reproduce (if different from original report above) Actual results Expected results
Cups-1.1.17-13.3.32 For all other information see original bug comments. Can we change the priority to high ? I have to edit all the ppd-files in the organisation by hand which is taking a lot of time.
With 13.3.27 I could reproduce the problem here as you described. With 13.3.32 I cannot. I have built a package with debugging support enabled, 1.1.17-13.3.32.0.0.2: ftp://people.redhat.com/twaugh/tmp/cups-rhel3/i386/ Please try it out and follow the instructions in comment #7. Please be sure to clear out the error_log file first, like this: service cups stop >/var/log/cups/error_log When you have reproduced the problem with this package, please attach: 1. /var/log/cups/error_log 2. /tmp/cups/err_output Thanks.
Created attachment 119458 [details] cups error log with patch 1.1.17-13.3.32.0.0.2
Created attachment 119459 [details] cups error log with patch 1.1.17-13.3.32.0.0.2
Created attachment 119460 [details] err_output with patch 1.1.17-13.3.32.0.0.2
It looks very much like the IPP client is getting an error due to the fact that the server has (for some reason) closed its socket. Can you confirm that the message you get is 'server-error-service-unavailable' and not 'client-error-not-authorized'? I have built a new test package with a patch that I am hopeful will fix this problem. Please fetch 1.1.17-13.3.32.0.0.3: ftp://people.redhat.com/twaugh/tmp/cups-rhel3/i386/
Created attachment 119523 [details] Screenshot error message
Created attachment 119524 [details] cups error log with patch cups-1.1.17-13.3.32.0.0.3
Created attachment 119525 [details] err_output with patch 1.1.17-13.3.32.0.0.3
Even with cups-1.1.17-13.3.32.0.0.3 I am still experiencing the same problem.
1. Curiously enough the err_output file only has output from the cupsd process (the scheduler), and not the admin.cgi process that it spawns. I think the /etc/cups/err_output file (and directory) probably does not have the right permissions. Please use the chmod commands in comment #7 to fix this. 2. Could you please change the LogLevel line in /etc/cups/cupsd.conf to read like this?: LogLevel debug2 Then please run: service cups stop >/var/log/cups/error_log >/tmp/cups/err_output Sorry to ask, but could you please try again and attach the new logs?
Created attachment 119541 [details] err_output with patch 1.1.17-13.3.32.0.0.3
Created attachment 119542 [details] cups error log with patch cups-1.1.17-13.3.32.0.0.3
I have built a new test package with another patch in addition to the last one. Please fetch 1.1.17-13.3.32.0.0.4: ftp://people.redhat.com/twaugh/tmp/cups-rhel3/i386/ and try again. Thanks!
Created attachment 119543 [details] cups error log with patch cups-1.1.17-13.3.32.0.0.4
Created attachment 119544 [details] err_output with patch cups-1.1.17-13.3.32.0.0.4
Dear Tim, Everything is now working as expected. Thank you very much for your efforts. I attached the output files for you. Maybe you want to check them out. Can I keep using these packages or is it better for me to wait for the official release ?
Thank you for testing. Those packages are experimental and still contain some debugging code (which could slow the scheduler down or fill up disk space). It would be better to wait for the official update packages if possible.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0034.html