Bug 802132 - cups does not start properly / needs restart
Summary: cups does not start properly / needs restart
Status: RESOLVED DUPLICATE of bug 857372
Alias: None
Product: openSUSE 12.2
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: All openSUSE 12.2
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: systemd maintainers
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-05 11:55 UTC by Axel Braun
Modified: 2014-02-14 10:04 UTC (History)
2 users (show)

See Also:
Found By: Community User
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Startlog of the system.... (309.27 KB, image/svg+xml)
2013-02-05 12:00 UTC, Axel Braun
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Braun 2013-02-05 11:55:37 UTC
User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:18.0) Gecko/20100101 Firefox/18.0

New installation of openSUSE 12.2 on a desktop, eth1 configured with if-up.
After boot there is no connection on localhost:631, which means that network printing is not possible.
Manual restart (rccups restart) fixes the problem.
I assume that this is a systemd problem - any idea how to track this?

Reproducible: Always

Steps to Reproduce:
1. reboot PC
2.
3.
Actual Results:  
no connection to localhost:631 / no network printing
Comment 1 Axel Braun 2013-02-05 12:00:38 UTC
Created attachment 523364 [details]
Startlog of the system....
Comment 2 Axel Braun 2013-02-05 15:27:24 UTC
Situation after boot:
southpole:/home/axel # rccups status
redirecting to systemctl
cups.service - CUPS Printing Service
          Loaded: loaded (/lib/systemd/system/cups.service; enabled)
          Active: inactive (dead)
          CGroup: name=systemd:/system/cups.service

Feb 05 11:55:21 southpole cupsd[9140]: No SubscriptionPrivateValues defined in policy allowallforanybody - using defaults.
Feb 05 12:22:16 southpole cupsd[3961]: No limit for Validate-Job defined in policy allowallforanybody and no suitable template found.
Feb 05 12:22:17 southpole cupsd[3961]: No limit for Cancel-Jobs defined in policy allowallforanybody and no suitable template found.
Feb 05 12:22:17 southpole cupsd[3961]: No limit for Cancel-My-Jobs defined in policy allowallforanybody and no suitable template found.
Feb 05 12:22:17 southpole cupsd[3961]: No limit for Close-Job defined in policy allowallforanybody and no suitable template found.
Feb 05 12:22:17 southpole cupsd[3961]: No limit for CUPS-Get-Document defined in policy allowallforanybody and no suitable template found.
Feb 05 12:22:17 southpole cupsd[3961]: No JobPrivateAccess defined in policy allowallforanybody - using defaults.
Feb 05 12:22:17 southpole cupsd[3961]: No JobPrivateValues defined in policy allowallforanybody - using defaults.
Feb 05 12:22:17 southpole cupsd[3961]: No SubscriptionPrivateAccess defined in policy allowallforanybody - using defaults.
Feb 05 12:22:17 southpole cupsd[3961]: No SubscriptionPrivateValues defined in policy allowallforanybody - using defaults.
Comment 3 Johannes Meixner 2013-02-06 13:55:45 UTC
Only FYI (I cannot help regarding systemd issues):
You can ignore the cupsd messages regarding "policy allowallforanybody".
Those messages come from the cupsd itself while it starts.
The cupsd works o.k. - it is just too verbose here.
Those messages have nothing to do whether or not systemd starts the cupsd.
Comment 6 Frederic Crozat 2013-03-11 14:40:30 UTC
By default, cups will be started on demand (when a print job is sent or a cups client requests more information), which might explain why you don't see it started.


If you don't want this behaviour, run ;
systemctl disable cups.path cups.socket
ln -s /usr/lib/systemd/system/cups.service /etc/systemd/system/multi-user.target.wants/
Comment 7 Axel Braun 2013-03-11 15:14:43 UTC
(In reply to comment #6)
> By default, cups will be started on demand (when a print job is sent or a cups
> client requests more information), which might explain why you don't see it
> started.

That may work on a local machine, but it is not useful for a network printer. The clients get permanent timeouts until cups is started.
Anyway, I will try your a.m. commands, thanks
Comment 8 Johannes Meixner 2014-02-05 16:36:00 UTC
I think my current cups.service file as shown in
https://bugzilla.novell.com/show_bug.cgi?id=857372#c75
basically implements what Frederic Crozat wrote in comment#6:
---------------------------------------------------------------------
systemctl disable cups.path cups.socket
ln -s /usr/lib/systemd/system/cups.service /etc/systemd/system/multi-user.target.wants/
---------------------------------------------------------------------

Axel Braun,
I would appreciate it if you try out the cups package
from the OBS project "Printing" on your systems and
please provide feedback whether or not it works for you, see
https://bugzilla.novell.com/show_bug.cgi?id=857372#c75
for instructions - in particular note
-----------------------------------------------------------------------
To make systemd using only that cups.service file one may have to do
# systemctl disable cups.service
# systemctl enable cups.service
-----------------------------------------------------------------------
Comment 9 Johannes Meixner 2014-02-14 10:04:34 UTC
I think this issue here is meanwhile obsolete since
https://bugzilla.novell.com/show_bug.cgi?id=857372#c61
and subsequent comments.

*** This bug has been marked as a duplicate of bug 857372 ***