cups: no remote printing

English Network/Internet
#1

I have the problem that i can not print via cups to a remote cups server.

the cups server is running on 15.1 for a long time without the configuration having been changed lately.
local printing on the server is working.

from a client running 15.1 printing to the server worked well.
after installation of 15.3 on this client, printing to the server is no longer working.

on client:
in yast I selected “Print via network” -> the printers of the cups server are show in printer configuration.
printing a test page results in the follwoing error message in /var/log/cups/error_log

    No destination host name supplied by cups-browsed for printer <printer name>, is cups-browsed running?

after this unsuccessful try, in the printer configuration the status of the printer is shown as dectivated

systemctl list-unit-files | grep cups


[FONT=monospace]**cups**.path                                                                 enabled         enabled       
**cups**-browsed.service                                                      enabled         disabled      
**cups**-lpd@.service                                                         static          -             
**cups**.service                                                              enabled         enabled       
**cups**-lpd.socket                                                           disabled        disabled      
**cups**.socket                                                               enabled         enabled    
[/FONT]

any hints on how I can solve this problem?

#2

The question I read i “is cups-browsed running?”
Then you show:

cups-browsed.service                                                      enabled         disabled

So indeed it isn’t.

Next logical step I assume is :

systemctl status cups-browsed
#3

[FONT=monospace]systemctl start cups-browsed.service
systemctl status cups-browsed
[/FONT]


[FONT=monospace]**●** cups-browsed.service - Make remote CUPS printers available locally 
     Loaded: loaded (/usr/lib/systemd/system/cups-browsed.service; enabled; vendor preset: disabled) 
     Active: **active (running)** since Wed 2021-12-01 11:24:43 CET; 1s ago 
   Main PID: 1928 (cups-browsed) 
      Tasks: 1 (limit: 4915) 
     CGroup: /system.slice/cups-browsed.service 
             └─1928 /usr/sbin/cups-browsed 

Dec 01 11:24:43 lu939 systemd[1]: Started Make remote CUPS printers available locally.
[/FONT]

lpq:

<printer name>[FONT=monospace] is ready
[/FONT]

yast → print test page
cat /var/log/cups/error_log:

[FONT=monospace]No destination host name supplied by cups-browsed for printer \<printer name>\", is cups-browsed running?
[/FONT]

systemctl status cups-browsed

[FONT=monospace]**●** cups-browsed.service - Make remote CUPS printers available locally 
     Loaded: loaded (/usr/lib/systemd/system/cups-browsed.service; enabled; vendor preset: disabled) 
     Active: **failed** (Result: exit-code) since Wed 2021-12-01 11:24:48 CET; 4min 11s ago 
    Process: 1928 ExecStart=/usr/sbin/cups-browsed **(code=exited, status=1/FAILURE)**
   Main PID: 1928 (code=exited, status=1/FAILURE) 

Dec 01 11:24:43 lu939 systemd[1]: Started Make remote CUPS printers available locally. 
Dec 01 11:24:48 lu939 systemd[1]: **cups-browsed.service: Main process exited, code=exited, status=1/FAILURE**
Dec 01 11:24:48 lu939 systemd[1]: **cups-browsed.service: Failed with result 'exit-code'.**
[/FONT]
#4

Please, please. Why do you separate the command from the output? Just copy/paste the line with the prompt command, then whatever lines result of that up to and including the next prompt line. In my opinion easier to do for you and certainly easier to read and understand for us.

Example:

henk@boven:~> uname -r
5.3.18-lp152.106-default
henk@boven:~>

No explanation needed. It is all there for those who want to see what you saw.

#5

Hm, my impression is that it starts correct and then after 5 secs breaks down “with exit code 1” (which does not tell us too much). :frowning:

Did you try that test page within those 5 secs? When yes, then that print trial could make it abort. When no, it aborted already before you tried to print anything.

#6

I checked, it dies before I do anything.

#7

As background. I run 15.2 here. I have only one USB printer on one system, that thus acts as CUPS server. I have one client that I configured to use that server. So that is different from your situation.

Until now I tried with you to get the most obvious information. And we found out that cups-browsed on 15.3 starts, but dies after ~5 secs. I am unsure if this has anything to do with the fact that the server still runs 15.1, which is an unsupported version already for some time.

Only thing I found in the (15.2)

man cups-brosed

is

The standard method to broadcast for shared/network printers to broadcast their presence is Bonjour. The CUPS broadcasting/browsing protocol is deprecated.
(it is rather at the top in the DESCRIPTION).
I am not sure of it’s implication in your case.

#8

I can. CUPS server runs (and prints;)) on host erlangen.

CUPS is disabled on client i3-4130. I selected “yast2 printer > Do All Printing Directly via One Single CUPS Server” and entered “erlangen” in field “One single CUPS server name or IP Address”.

**i3-4130:~ #** systemctl list-unit-files cups* 
UNIT FILE            STATE    VENDOR PRESET
cups.path            disabled enabled      
cups-browsed.service **disabled disabled     **
cups-lpd@.service    static   -            
cups.service         disabled enabled      
cups-lpd.socket      **disabled disabled     **
cups.socket          **disabled ****enabled      **

6 unit files listed. 
**i3-4130:~ #** systemctl list-units cups*      
  UNIT LOAD ACTIVE SUB DESCRIPTION
**0 loaded units listed.** Pass --all to see loaded but inactive units, too. 
To show all installed unit files use 'systemctl list-unit-files'. 
**i3-4130:~ #**
#9

I can not set this configuration.
when trying to set it via yast, it tells me that it can not set the configuration because there is still a locally running cups service reachable.
(I remember that the configuration had never worked for me in the past)

#10

it worked when I disabled the locally running cups service.
I may need it, so I have to investigate further …

#11

If you attempt to configure using the CUPS web interface (rather than YaST) do you still get the same issue occurring?

FWIW, the YaST printer module is considered deprecated…
https://bugzilla.suse.com/show_bug.cgi?id=1175341#c1