Nice to see some progress, but the initial problem description and mine
is different from what has been discovered. The problem is not just the
webinterface, it is cups itself (or the scheduler) which goes inactive
and doesn't come back.

Today I was able to invest more time. On my system there was still a
client.conf in /etc/cups/ The man page says it is deprecated. I moved it
to client.conf_bak and restarted cups. The scheduler is now running for
over 3 hours. I will have an eye on this, but maybe this fixed my cups
problem.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1598300

Title:
  cups hang after a while

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—————————————————————————————————————————————————————————————————————————————————————⌍
  |root@cupsmachine :~# systemctl status cups                                   
        |
  |● cups.service - CUPS Scheduler                                              
        |
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
        |
  |     Docs: man:cupsd(8)                                                      
        |
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)        |
  | Main PID: 28686 (code=exited, status=0/SUCCESS)                             
        |
  |                                                                             
        |
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.           
        |
  
⌎—————————————————————————————————————————————————————————————————————————————————————⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to