Page 5 of 5 FirstFirst ... 345
Results 41 to 50 of 50

Thread: Cannot access CUPS server after update

  1. #41
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,378
    Blog Entries
    1

    Default Re: Cannot access CUPS server after update

    BTW, if you still have problems with accessing the CUPS server after disabling CUPS socket-activation, can you please confirm that cupsd.conf has

    Code:
    # Show shared printers on the local network.
    Browsing On
    BrowseOrder allow,deny
    BrowseAllow all
    BrowseLocalProtocols CUPS

  2. #42

    Default Re: Cannot access CUPS server after update

    Quote Originally Posted by deano_ferrari View Post
    @Addanc: If CUPS socket-activation has been enabled previously, the sockets may still not be closed properly. In fact, I found even a reboot prevented CUPS listening to port 631, until I did the following
    Code:
    systemctl disable cups.socket
    systemctl stopcups.socket
    Check the status
    Code:
    # systemctl status cups.socket
    cups.socket - CUPS Printing Service Sockets
       Loaded: loaded (/usr/lib/systemd/system/cups.socket; disabled)
       Active: inactive (dead)
       Listen: /var/run/cups/cups.sock (Stream)
               127.0.0.1:631 (Stream)
               127.0.0.1:631 (Datagram)
    
    Jan 27 09:47:55 linux-bbgi.site systemd[1]: Stopping CUPS Printing Service Sockets.
    Jan 27 09:47:55 linux-bbgi.site systemd[1]: Closed CUPS Printing Service Sockets.
    Note the CUPS sockets are now confirmed as closed. Without that, CUPS will still not be able to listen on port 631.

    Now restart the CUPS daemon
    Code:
    systemctl restart cups.service
    Confirm that the print server printers are now shown
    Code:
    lpstat -t
    Tried the above sequence and it does restore the printers; but does not survive a re-boot.

  3. #43

    Default Re: Cannot access CUPS server after update

    Quote Originally Posted by wolfi323 View Post
    Code:
    [Unit]
    Description=CUPS Printing Service Sockets
    
    [Socket]
    ListenStream=/var/run/cups/cups.sock
    ListenStream=631
    ListenDatagram=0.0.0.0:631
    BindIPv6Only=ipv6-only
    
    [Install]
    WantedBy=sockets.target
    Then call "sudo systemctl enable cups.socket" and everything should be like before the Update.
    And the change in /etc won't be lost on updates either.
    Created the above file and performed the "systemctl enable cups.socket", this restores the printer and also survives a re-boot as advertised.

    Thanks folks, help much appreciated!

  4. #44

    Default Re: Cannot access CUPS server after update

    Do this, I have confirmation from somebody in the german forum that it does indeed work:
    Quote Originally Posted by wolfi323 View Post
    But edit the file /etc/systemd/system/cups.socket, with "kdesu kwrite /etc/systemd/system/cupsd.socket" f.e., and insert the following content: (if the file already exists, just change it accordingly so it looks exactly like this)
    Code:
    [Unit]
    Description=CUPS Printing Service Sockets
    
    [Socket]
    ListenStream=/var/run/cups/cups.sock
    ListenStream=631
    ListenDatagram=0.0.0.0:631
    BindIPv6Only=ipv6-only
    
    [Install]
    WantedBy=sockets.target
    Then call "sudo systemctl enable cups.socket" and everything should be like before the Update.
    And the change in /etc won't be lost on updates either.
    Edit: Sorry, just saw you did that already. The reply wasn't there yet when I wrote my post...

    Glad to hear it works now!

  5. #45

    Default Re: Cannot access CUPS server after update

    Quote Originally Posted by deano_ferrari View Post
    BTW, if you still have problems with accessing the CUPS server after disabling CUPS socket-activation, can you please confirm that cupsd.conf has

    Code:
    # Show shared printers on the local network.
    Browsing On
    BrowseOrder allow,deny
    BrowseAllow all
    BrowseLocalProtocols CUPS
    My cups.conf file looks a little different, one machine looks like this:
    Code:
    # Show shared printers on the local network.
    Browsing On
    BrowseLocalProtocols CUPS
    BrowseAllow @LOCAL
    BrowseOrder allow,deny
    BrowsePoll yggdrasil
    Another machine looks like this:
    Code:
    # Show shared printers on the local network.
    Browsing On
    BrowseOrder allow,deny
    BrowseAllow all
    BrowseRemoteProtocols CUPS
    BrowseLocalProtocols
    BrowsePoll yggdrasil
    These file have not been edited manually; both setup through YAST:
    Accept Printer Announcements from CUPS Servers => accept from all hosts in the local network.
    Request Printer Information from CUPS Servers => yggdrasil

  6. #46

    Default Re: Cannot access CUPS server after update

    On 01/27/2014 04:06 PM, Addanc pecked at the keyboard and wrote:
    > wolfi323;2619507 Wrote:
    > Code:
    > --------------------
    > > > [Unit]

    > > Description=CUPS Printing Service Sockets
    > >
    > > [Socket]
    > > ListenStream=/var/run/cups/cups.sock
    > > ListenStream=631
    > > ListenDatagram=0.0.0.0:631
    > > BindIPv6Only=ipv6-only
    > >
    > > [Install]
    > > WantedBy=sockets.target
    > >

    > --------------------
    >> Then call "sudo systemctl enable cups.socket" and everything should be
    >> like before the Update.
    >> And the change in /etc won't be lost on updates either.

    > Created the above file and performed the "systemctl enable cups.socket",
    > this restores the printer and also survives a re-boot as advertised.
    >
    > Thanks folks, help much appreciated!
    >
    >


    I can confirm this as I ad the same issue.

    Ken

  7. #47
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,378
    Blog Entries
    1

    Default Re: Cannot access CUPS server after update

    I've found that the following works for me

    Code:
    [Unit]
    Description=CUPS Printing Service Sockets
    
    [Socket]
    ListenStream=/var/run/cups/cups.sock
    ListenStream=0.0.0.0:631
    ListenDatagram=0.0.0.0:631
    BindIPv6Only=ipv6-only
    
    [Install]
    WantedBy=sockets.target
    In particular, the following entry
    Code:
    ListenStream=0.0.0.0:631
    is required so that the web interface is available. (Alternatively, cupsd.conf will listen if provided with 'Port 631' entry.)

    It is described here

    https://wiki.archlinux.org/index.php...it.27s_enabled

  8. #48
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,378
    Blog Entries
    1

    Default Re: Cannot access CUPS server after update

    I encourage others experiencing problems described in this thread to try the update suggested in this bug report. Socket-activation has been disabled, and cups.service is enabled with
    Code:
    [Unit]
    Description=CUPS Printing Service
    After=network.target
    
    [Service]
    ExecStart=/usr/sbin/cupsd -f
    
    [Install]
    WantedBy=multi-user.target
    (so cupsd is loaded at boot). The configuration directives in cupsd.conf will again determine the network/ports being listened to. (I can confirm that the update is working for me including communication with a CUPS print server on my LAN.)

    Code:
    # rpm -q --changelog cups | head
    * Thu Jan 30 2014 jsmeix@suse.de
    - cups-0003-systemd-secure-cups.service-unit-file.patch changes
      the cups.service systemd unit file to be more secure and
      to let the cupsd again work as it did all the time for printing
      in a network (bnc#857372 in particular comment #61 therein).
    - cups-1.5-additional_policies.patch was updated to avoid
      cupsd warning messages of the form "No limit for ... defined
      in policy allowallforanybody and no suitable template found"
      (bnc#857372 in particular comment #48 therein).

  9. #49
    Join Date
    Mar 2014
    Location
    Westervoort, NL
    Posts
    4

    Default Re: Cannot access CUPS server after update

    Thanks to all who worked on this problem. For me it was in vain and I gave up after two day (intermittently) working on the issue.
    So I solved it quick and dirty in /etc/init.d/after.local
    Code:
    #! /bin/sh
    #
    # Copyright (c) 2010 SuSE LINUX Products GmbH, Germany. All rights reserved.
    #
    # Author: Werner Fink, 2010
    #
    # /etc/init.d/after.local
    #
    # script with local commands to be executed from init after all scripts
    # of a runlevel have been executed.
    #
    # Here you should add things, that should happen directly after
    # runlevel has been reached. Common environment
    # variables for this are:
    # RUNLEVEL -- The current system runlevel.
    # PREVLEVEL -- The previous runlevel (useful after a runlevel switch).
    #
    /etc/init.d/cups restart

    When time allows I'll refine it with test before invoking...
    regards,
    Johan

  10. #50
    Join Date
    Mar 2014
    Location
    Westervoort, NL
    Posts
    4

    Default Re: Cannot access CUPS server after update

    Quote Originally Posted by pa0hwn View Post
    Thanks to all who worked on this problem. For me it was in vain and I gave up after two day (intermittently) working on the issue.
    So I solved it quick and dirty in /etc/init.d/after.local
    Code:
    ----------------------cut----------------------
    When time allows I'll refine it with test before invoking...
    regards,
    Johan
    Looking further I took the advice from:

    https://forums.opensuse.org/showthre...-inaktiv/page2

    and now it is working again...
    that is: after reboot cups is available on this OSS 13.1.
    regards,
    Johan

Page 5 of 5 FirstFirst ... 345

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •