When changing server settings cups stops and is never restarted

Bug #37986 reported by casualprogrammer
16
Affects Status Importance Assigned to Milestone
cupsys (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

This is for Dapper Drake 6.06, updates as of 2006-04-04

When setting up the cups server via localhost:631 setting the server parameters under administration is accepted, but the server stops and has to be restarted manually.

Note: the original reporter indicated the bug was in package 'cups'; however, that package was not published in Ubuntu.

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

Please provide configuration files before and after your modification. Before, when it's working, and after modifications via :631.
Please see also logs of cups in /var/log when you try to apply your modifications.

Changed in cupsys:
status: Unconfirmed → Needs Info
Revision history for this message
casualprogrammer (casualprogrammer) wrote :
Download full text (4.7 KiB)

Hi Patrice,

not sure what configuration files exactly you need, please specify.

The process again is:

1. Start Firefox
2. Enter http://localhost:631
3. In the page titled "Common UNIX Printing System 1.2svn" click on the tab "Administration"
4. Select / Deselect from "Basic Server Settings"
5. Press "Change Settings"
6. A page titled "Change Settings" appears, asking to "stand by..."
7. A page titled "Unable to connect" appears.

Starting cups with "$ sudo cupsd" is required to get on.

The configuration file(from the admin interface ) shows:

# Show troubleshooting information in error_log.
LogLevel debug
SystemGroup lpadmin
RunAsUser Yes
# Enable printer sharing and shared printers.
Browsing On
BrowseOrder allow,deny
BrowseAllow @LOCAL
BrowseAddress @LOCAL
DefaultAuthType Basic
<Location />
  # Allow shared printing and remote administration...
  Order allow,deny
  Allow @LOCAL
</Location>
<Location /admin>
  # Allow remote administration...
  Order allow,deny
  Allow @LOCAL
</Location>
<Location /admin/conf>
  AuthType Basic
  Require user @SYSTEM
  # Allow remote access to the configuration files...
  Order allow,deny
  Allow @LOCAL
</Location>
<Policy default>
  <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>
  <Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default>
    AuthType Basic
    Require user @SYSTEM
    Order deny,allow
  </Limit>
  <Limit CUPS-Authenticate-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>
  # Only the owner or an administrator can cancel a job...
  <Limit Cancel-Job>
    Order deny,allow
    Require user @OWNER @SYSTEM
  </Limit>
  <Limit All>
    Order deny,allow
  </Limit>
</Policy>
Include /etc/cups/cups.d/ports.conf
Include /etc/cups/cups.d/browse.conf
# Allow remote access
Listen *:631
Listen /var/run/cups/cups.sock

The access log (from the administration page) shows:

localhost - - [04/Apr/2006:11:55:01 +0200] "PUT /admin/conf/cupsd.conf HTTP/1.1" 401 0 - -
localhost - - [04/Apr/2006:11:55:01 +0200] "PUT /admin/conf/cupsd.conf HTTP/1.1" 401 0 - -
localhost - - [04/Apr/2006:11:55:02 +0200] "PUT /admin/conf/cupsd.conf HTTP/1.1" 401 0 - -
localhost - root [04/Apr/2006:11:55:02 +0200] "PUT /admin/conf/cupsd.conf HTTP/1.1" 201 1862 - -
localhost - - [04/Apr/2006:11:54:46 +0200] "POST /admin HTTP/1.1" 200 3449 - -
localhost - - [04/Apr/2006:11:55:58 +0200] "GET /admin HTTP/1.1" 200 0 - -
localhost - - [04/Apr/2006:11:55:59 +0200] "POST / HTTP/1.1" 200 1382 CUPS-Get-Devices -
localhost - - [04/Apr/2006:11:55:5...

Read more...

Revision history for this message
Matthias Klose (doko) wrote :

please could you recheck after upgrading to 20060414, or check out https://lists.ubuntu.com/archives/ubuntu-devel/2006-April/017211.html

Revision history for this message
casualprogrammer (casualprogrammer) wrote :

After upgrading on 20060414 nothing really changed (probably, because the configuration file will not be overwritten), I got rid of it by accident though:

While trying to set up Dapper as print server for some WindowsXP workstations I came to edit the CUPS config file via http://localhost:631/admin?op=config-server and, while being dissatisfied with my results, I chose the option "Use Default Configuration File".

The generated file looks distinctly different from what is delivered with the distribution and the reported problem is gone with it.

I have a Canon iP4000 as well as the PDF-Printer working now also from the WindowsXP workstations over SAMBA. In fact, I am using the CUPS supplied Default Configuration File without changes.

Revision history for this message
Martin Pitt (pitti) wrote :

Do you still have the older cupsd.conf around? Usually cups makes a backup like cupsd.conf.O. Can you attach both your old and new file? (They are in /etc/cups)

Revision history for this message
casualprogrammer (casualprogrammer) wrote :

Alas not, but you may be able to extract the file from the flight 6 iso. The file installed by apt fails, the file generated by cups works. ( localhost:631 ) administration / view configuration file / create default

Revision history for this message
casualprogrammer (casualprogrammer) wrote :

After the most recent upgrade ( 20060426 06:30 GMT+1 ) cupsys isn't restarting at all ( neither with old nor new config. )

In addition, when the default config file is selected and saved cupsys won't even start manually.

Revision history for this message
Ante Karamatić (ivoks) wrote :

You have multiple Listen directive that point to the same interface. Remove all 'Listen' and 'Port' dircetives from cupsd.conf and manage them inside /etc/cups/cups.d/ports.conf.

So, in ports.conf should be:

Listen 631

Also remove 'Browsing On' and 'RunAsUser' directives. Browsing is managed trough /etc/cups/cups.d/browse.conf.

Revision history for this message
Ante Karamatić (ivoks) wrote :

CUPS won't start if multiple Listen|Port directives are inserted for same interface; including:

Listen 631
Port 192.168.0.1:631

- this will result in broken CUPS.

Closing this bug as misconfigured service. Please reopen if these instructions didn't help you.

Thank you.

Changed in cupsys:
status: Needs Info → Rejected
Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Marking this bug as a duplicate of bug #59266, since that bug has more detailed information for this issue.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.