CUPS sudden refuses to print after previously working fine

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

CUPS sudden refuses to print after previously working fine

acampbell
 I have a networked Brother-HL5350DN printer which has worked fine
 with CUPS for over a year. Two days ago it suddenly refused to
 print on my desktop running -current I reconfigured the printer
 several times without effect.

I then set up CUPS on a laptop running -release. It also failed. In
both cases the printer appears on screen and I can queue jobs for
printing as normal but they don't print. The printer itself is
working normally from my wife's computer. I cam ping the printer
without difficulty.

I turned on debug and found this:
[Job 30] Unable to locate printer \"BRN001BA92DB44A\"

I'm mystified. Whenever I've set up the printer in CUPS previously
it has always worked. The only clue I found was on Arch Linux where
they talk about needing to set up avahi jn such cases, but I don't
know if that is relevant here.

Any ideas gratefully received.


Anthony

--
Anthony Campbell https://www.acampbell.uk

Reply | Threaded
Open this post in threaded view
|

Re: CUPS sudden refuses to print after previously working fine

Antoine Jacoutot-7
On Fri, Feb 28, 2020 at 08:28:52AM +0000, Anthony Campbell wrote:

>  I have a networked Brother-HL5350DN printer which has worked fine
>  with CUPS for over a year. Two days ago it suddenly refused to
>  print on my desktop running -current I reconfigured the printer
>  several times without effect.
>
> I then set up CUPS on a laptop running -release. It also failed. In
> both cases the printer appears on screen and I can queue jobs for
> printing as normal but they don't print. The printer itself is
> working normally from my wife's computer. I cam ping the printer
> without difficulty.
>
> I turned on debug and found this:
> [Job 30] Unable to locate printer \"BRN001BA92DB44A\"
>
> I'm mystified. Whenever I've set up the printer in CUPS previously
> it has always worked. The only clue I found was on Arch Linux where
> they talk about needing to set up avahi jn such cases, but I don't
> know if that is relevant here.
>
> Any ideas gratefully received.

Can you share your configuration?
If it's a network printer, it could be that cups is trying to connect to your
printer using avahi which doesn't work on OpenBSD.  You must make sure you
configure your printer using hostname or IP.

--
Antoine

Reply | Threaded
Open this post in threaded view
|

Re: CUPS sudden refuses to print after previously working fine

acampbell
On 28 Feb 2020, Antoine Jacoutot wrote:

> On Fri, Feb 28, 2020 at 08:28:52AM +0000, Anthony Campbell wrote:
> >  I have a networked Brother-HL5350DN printer which has worked fine
> >  with CUPS for over a year. Two days ago it suddenly refused to
> >  print on my desktop running -current I reconfigured the printer
> >  several times without effect.
> >
> > I then set up CUPS on a laptop running -release. It also failed. In
> > both cases the printer appears on screen and I can queue jobs for
> > printing as normal but they don't print. The printer itself is
> > working normally from my wife's computer. I cam ping the printer
> > without difficulty.
> >
> > I turned on debug and found this:
> > [Job 30] Unable to locate printer \"BRN001BA92DB44A\"
> >
> > I'm mystified. Whenever I've set up the printer in CUPS previously
> > it has always worked. The only clue I found was on Arch Linux where
> > they talk about needing to set up avahi jn such cases, but I don't
> > know if that is relevant here.
> >
> > Any ideas gratefully received.
>
> Can you share your configuration?
> If it's a network printer, it could be that cups is trying to connect to your
> printer using avahi which doesn't work on OpenBSD.  You must make sure you
> configure your printer using hostname or IP.
>
> --
> Antoine
>
>

Thanks Antoine. I've now got Cups working on my laptop, by setting
socket://<printer-ip>. This is not yet working on my Desktop (-current)
although the "printer not found" error no longer appears.

I'm not sure which configuration I should post here - some of the
files in /etc/cups?

It's occurred to me that the problem on the desktop may have
happened because on a couple of occasions recently after an upgrade
I was unable to make the requested deletions (they disappared from
the screen before I could do it). Tomorrow I'll try reinstalling
Cups from scratch in case that fixes it.

Anthony

--
Anthony Campbell https://www.acampbell.uk

Reply | Threaded
Open this post in threaded view
|

Re: CUPS sudden refuses to print after previously working fine

acampbell
In reply to this post by Antoine Jacoutot-7
On 28 Feb 2020, Antoine Jacoutot wrote:

> On Fri, Feb 28, 2020 at 08:28:52AM +0000, Anthony Campbell wrote:
> >  I have a networked Brother-HL5350DN printer which has worked fine
> >  with CUPS for over a year. Two days ago it suddenly refused to
> >  print on my desktop running -current I reconfigured the printer
> >  several times without effect.
> >
> > I then set up CUPS on a laptop running -release. It also failed. In
> > both cases the printer appears on screen and I can queue jobs for
> > printing as normal but they don't print. The printer itself is
> > working normally from my wife's computer. I cam ping the printer
> > without difficulty.
> >
> > I turned on debug and found this:
> > [Job 30] Unable to locate printer \"BRN001BA92DB44A\"
> >
> > I'm mystified. Whenever I've set up the printer in CUPS previously
> > it has always worked. The only clue I found was on Arch Linux where
> > they talk about needing to set up avahi jn such cases, but I don't
> > know if that is relevant here.
> >
> > Any ideas gratefully received.
>
> Can you share your configuration?
> If it's a network printer, it could be that cups is trying to connect to your
> printer using avahi which doesn't work on OpenBSD.  You must make sure you
> configure your printer using hostname or IP.

I don't have any avahi daemon running. I have a static address for
the printer.

Here is my latest config file:


# Printer configuration file for CUPS v2.3.1
# Written by cupsd on 2020-03-01 10:32
# DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING
NextPrinterId 2
<DefaultPrinter Brother_HL-5350DN_series>
PrinterId 1
UUID urn:uuid:a7dada8a-a537-3188-7c98-35ec7bf5bccf
Info Brother_HL-5350DN_series
Location
MakeModel Brother HL-5350DN Foomatic/Postscript
DeviceURI socket://192.168.1.83
State Idle
StateTime 1583058733
ConfigTime 1583058632
Type 8433684
Accepting Yes
Shared No
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
Attribute marker-colors \#000000,#000000,#000000
Attribute marker-levels -1,-1,54
Attribute marker-names Black Toner Cartridge,Black Toner Cartridge,Drum Unit
Attribute marker-types toner,toner,opc
Attribute marker-change-time 1583058733
</DefaultPrinter>


--
Anthony Campbell https://www.acampbell.uk

Reply | Threaded
Open this post in threaded view
|

Re: CUPS sudden refuses to print after previously working fine - SOLVED

acampbell
On 01 Mar 2020, Anthony Campbell wrote:
> On 28 Feb 2020, Antoine Jacoutot wrote:
> > On Fri, Feb 28, 2020 at 08:28:52AM +0000, Anthony Campbell wrote:
> > >  I have a networked Brother-HL5350DN printer which has worked fine
> > >  with CUPS for over a year. Two days ago it suddenly refused to
> > >  print on my desktop running -current I reconfigured the printer
> > >  several times without effect.


Well, I finally "solved" the problem by the simple expedient of just
deleting the printer in Cups and reinstalling it from scratch. It
then worked perfectly without doing anything else.  Here is the
resulting /etc/cups/printers.conf:

# Printer configuration file for CUPS v2.3.1
# Written by cupsd on 2020-03-02 09:54
# DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING
NextPrinterId 3
<DefaultPrinter Brother_HL-5350DN_series>
PrinterId 2
UUID urn:uuid:795e4424-0458-3f6d-413a-1669af7e997e
Info Brother HL-5350DN series
Location
MakeModel Brother HL-5350DN BR-Script3
DeviceURI lpd://brother/BINARY_P1
State Idle
StateTime 1583142812
ConfigTime 1583142501
Type 8433748
Accepting Yes
Shared No
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
Attribute marker-colors \#000000,#000000,#000000
Attribute marker-levels -1,-1,54
Attribute marker-names Black Toner Cartridge,Black Toner Cartridge,Drum Unit
Attribute marker-types toner,toner,opc
Attribute marker-change-time 1583142812
</DefaultPrinter>
~





--
--
Anthony Campbell https://www.acampbell.uk

Reply | Threaded
Open this post in threaded view
|

Re: CUPS sudden refuses to print after previously working fine - SOLVED

Vincenzo Nicosia
On Mon, Mar 02, 2020 at 10:50:53AM +0000, Anthony Campbell wrote:

[cut]

>
>
> Well, I finally "solved" the problem by the simple expedient of just
> deleting the printer in Cups and reinstalling it from scratch. It
> then worked perfectly without doing anything else.  Here is the
> resulting /etc/cups/printers.conf:
>
> # Printer configuration file for CUPS v2.3.1
> # Written by cupsd on 2020-03-02 09:54
> # DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING
> NextPrinterId 3
> <DefaultPrinter Brother_HL-5350DN_series>
> PrinterId 2
> UUID urn:uuid:795e4424-0458-3f6d-413a-1669af7e997e
> Info Brother HL-5350DN series
> Location
> MakeModel Brother HL-5350DN BR-Script3
> DeviceURI lpd://brother/BINARY_P1

It was not just about "turn it off and on again" :) In your previous
configuration file you had the printer on "socket://" without a port
specified. Now it's configured as an lpd spooler. So there is an
important difference there ;)

(just to reaffirm that re-staring, re-booting, re-configuring,
re-whatevering do no magic on their own :P).

HTH

Reply | Threaded
Open this post in threaded view
|

Re: CUPS sudden refuses to print after previously working fine - SOLVED

acampbell
On 02 Mar 2020, Vincenzo Nicosia wrote:

> On Mon, Mar 02, 2020 at 10:50:53AM +0000, Anthony Campbell wrote:
>
> [cut]
>
> >
> >
> > Well, I finally "solved" the problem by the simple expedient of just
> > deleting the printer in Cups and reinstalling it from scratch. It
> > then worked perfectly without doing anything else.  Here is the
> > resulting /etc/cups/printers.conf:
> >
> > # Printer configuration file for CUPS v2.3.1
> > # Written by cupsd on 2020-03-02 09:54
> > # DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING
> > NextPrinterId 3
> > <DefaultPrinter Brother_HL-5350DN_series>
> > PrinterId 2
> > UUID urn:uuid:795e4424-0458-3f6d-413a-1669af7e997e
> > Info Brother HL-5350DN series
> > Location
> > MakeModel Brother HL-5350DN BR-Script3
> > DeviceURI lpd://brother/BINARY_P1
>
> It was not just about "turn it off and on again" :) In your previous
> configuration file you had the printer on "socket://" without a port
> specified. Now it's configured as an lpd spooler. So there is an
> important difference there ;)
>
> (just to reaffirm that re-staring, re-booting, re-configuring,
> re-whatevering do no magic on their own :P).
>
> HTH
>

Yes, I'd earlier deleted and reinstalled cups, which I'd assumed
would automatically involve reinstalling the printer, but evidently
not.

The reason for the "socket://" stuff in the previous configuration
file was that this seemed to be necssary in my two laptops (running
-release) so I tried it in the desktop (-current) as well.

After successfully deleting/reinstallin the printer on the desktop
this morning I did the same on the laptops and in both cases the
printer now works perfectly with lpd on those as well.

The only explanation I can think of is that last night I'd
changed the printer's IP address from dhcpd to fixed, as suggested by
someone on another list.

Anthony

--
Anthony Campbell https://www.acampbell.uk