I have exactly the same thing on 16.04 LTS with the minimal virtual machine 
install. I run the whole thing on ESXi 5.5 something. 
Status:


root@printserver:/var/log/cups# service cups status
● cups.service - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: ena
   Active: inactive (dead) since Wed 2016-08-24 22:44:57 EEST; 12min ago
     Docs: man:cupsd(8)
  Process: 2177 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)
 Main PID: 2177 (code=exited, status=0/SUCCESS)

Aug 24 22:38:23 printserver systemd[1]: Started CUPS Scheduler.


No mention of any abnormalities in any logs whatsoever. I'm afraid I need to go 
back to 14.04 LTS for this virtual machine.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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:
  Incomplete

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/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to