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