Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #257755 > unrolled thread
| Started by | gene heskett <gheskett@shentel.net> |
|---|---|
| First post | 2023-05-01 01:10 +0200 |
| Last post | 2023-05-08 07:10 +0200 |
| Articles | 20 on this page of 89 — 15 participants |
Back to article view | Back to linux.debian.user
repeat of previous question that has gone unanswered several times. gene heskett <gheskett@shentel.net> - 2023-05-01 01:10 +0200
Re: repeat of previous question that has gone unanswered several times. Lee <ler762@gmail.com> - 2023-05-01 02:20 +0200
Re: repeat of previous question that has gone unanswered several times. gene heskett <gheskett@shentel.net> - 2023-05-01 09:40 +0200
Re: repeat of previous question that has gone unanswered several times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 15:50 +0200
Re: repeat of previous question that has gone unanswered severaltimes. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 16:10 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:40 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 18:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 19:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-02 01:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 20:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-01 22:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 23:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:30 +0200
Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Jeffrey Walton <noloader@gmail.com> - 2023-05-01 16:20 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
Re: repeat of previous question that has gone unanswered several times. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 06:30 +0200
Re: repeat of previous question that has gone unanswered several times. john doe <johndoe65534@mail.com> - 2023-05-01 09:40 +0200
Re: repeat of previous question that has gone unanswered several times. <tomas@tuxteam.de> - 2023-05-01 13:50 +0200
Re: repeat of previous question that has gone unanswered several times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
Re: repeat of previous question that has gone unanswered several times. zithro <slack@rabbit.lu> - 2023-05-04 21:50 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-04 22:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 16:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 17:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 19:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 22:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-06 01:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-06 03:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Alex King <alex@king.net.nz> - 2023-05-07 01:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. David <curmudgeon@telaman.net.au> - 2023-05-07 02:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Byung-Hee HWANG <soyeomul@doraji.xyz> - 2023-05-07 03:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 13:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-07 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-07 18:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 06:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-08 13:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 19:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 00:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 10:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-09 13:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 22:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 14:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 16:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. <tomas@tuxteam.de> - 2023-05-10 16:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 19:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 20:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-10 22:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:10 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 21:20 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 00:00 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 00:30 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 01:50 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:40 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 11:20 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 13:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:20 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:10 +0200
Re: :Re: repeat of previous question thathasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 23:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-12 20:50 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 21:30 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-13 13:20 +0200
Re: SOLVED:Re: repeat of previous questionthathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-13 17:10 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:30 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 19:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 07:10 +0200
Page 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-10 22:00 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GtY8F-7YFy-1@gated-at.bofh.it> |
| In reply to | #258129 |
On 5/10/23 14:22, Brian wrote: > On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote: > >> On 5/10/23 11:29, Brian wrote: >>> On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote: >>> >>>> On 5/10/23 08:17, Brian wrote: >> >>> [...] > >>> Is /etc/cups/client,conf really, really needed? >>> >> That is the first thing cups docs tell you to do, see "printer sharing" > > A link would be ever so useful. > >>>> Also on the bpi's, running armbian, libnss-ldap is installed, which >>>> conflicts with installing libnss-*, but did install libnss-my*, and now the >>>> printers have disappeared again. That does not hold water. What the heck is >>>> going on now? >>> >>> I haven't any idea and do not claim the know anything about armbian and how >>> it should deal with NSS\ >> >> Since that comes from a debian arm64 repo. my first assumption is that its >> identical. > > After appreciating that bpi51 has libnss-mdns installed, you might discard any > assumption that nsswitch.conf on bpi54 has the same contents. > I don't believe any of these 4 bpi's have libnss-mdns installed, locate after a sudo updatedb, cannot find it on either of the 2 that are live on this net ATM. Now. I modified /etc/cups/cupsd.conf to change loglevel to debug2, and add Listen 192.168.xx.yy:631, then restarted cups, getting this notice in /var/log/cups/error_log: E [10/May/2023:14:32:16 -0500] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [10/May/2023:14:32:16 -0500] Unable to open listen socket for address 192.168.xx.yy:631 - Cannot assign requested address. There's no ipv6 here, none within 100 miles so the first is expected but what is the second one telling us? Permissions, bad path, wrong time of the month? IDK... This above is on bpi51. Take care & stay well Brian. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-11 13:10 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <Guclj-87xI-9@gated-at.bofh.it> |
| In reply to | #258130 |
On Wed 10 May 2023 at 15:51:53 -0400, gene heskett wrote: > On 5/10/23 14:22, Brian wrote: [...] > > After appreciating that bpi51 has libnss-mdns installed, you might discard any > > assumption that nsswitch.conf on bpi54 has the same contents. > > > I don't believe any of these 4 bpi's have libnss-mdns installed, locate > after a sudo updatedb, cannot find it on either of the 2 that are live on > this net ATM. bpi51 has avahi-browse. avahi-browse depends on avahi-daemon. avahi-daemon recommends libnss-mdns. > Now. I modified /etc/cups/cupsd.conf to change loglevel to debug2, and add > Listen 192.168.xx.yy:631, then restarted cups, getting this notice in > /var/log/cups/error_log: This is on bpi54? I do not believe a change to /etc/cups/cupsd.conf is necessary. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-11 18:30 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GuhkZ-8aJ7-11@gated-at.bofh.it> |
| In reply to | #258136 |
On 5/11/23 07:09, Brian wrote: > On Wed 10 May 2023 at 15:51:53 -0400, gene heskett wrote: > >> On 5/10/23 14:22, Brian wrote: > > [...] > >>> After appreciating that bpi51 has libnss-mdns installed, you might discard any >>> assumption that nsswitch.conf on bpi54 has the same contents. >>> >> I don't believe any of these 4 bpi's have libnss-mdns installed, locate >> after a sudo updatedb, cannot find it on either of the 2 that are live on >> this net ATM. > > bpi51 has avahi-browse. avahi-browse depends on avahi-daemon. avahi-daemon > recommends libnss-mdns. > >> Now. I modified /etc/cups/cupsd.conf to change loglevel to debug2, and add >> Listen 192.168.xx.yy:631, then restarted cups, getting this notice in >> /var/log/cups/error_log: > > This is on bpi54? I do not believe a change to /etc/cups/cupsd.conf is > necessary. > Yes, it was necessary, see my previous post. Not determined is the need for a client.conf file with its contents, I rather suspect it might still be required as its the only "Server" specification in the whole shebang. Take care & stay well. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-10 22:10 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GtYil-7YY6-1@gated-at.bofh.it> |
| In reply to | #258129 |
On 5/10/23 14:22, Brian wrote: > On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote: > >> On 5/10/23 11:29, Brian wrote: >>> On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote: >>> >>>> On 5/10/23 08:17, Brian wrote: >> >>> [...] > >>> Is /etc/cups/client,conf really, really needed? >>> >> That is the first thing cups docs tell you to do, see "printer sharing" > > A link would be ever so useful. send browser to cups.org, click help, in right pane, click "printer sharing", scroll down about a screenfull to Automatic using IPP > >>>> Also on the bpi's, running armbian, libnss-ldap is installed, which >>>> conflicts with installing libnss-*, but did install libnss-my*, and now the >>>> printers have disappeared again. That does not hold water. What the heck is >>>> going on now? >>> >>> I haven't any idea and do not claim the know anything about armbian and how >>> it should deal with NSS\ >> >> Since that comes from a debian arm64 repo. my first assumption is that its >> identical. > > After appreciating that bpi51 has libnss-mdns installed, you might discard any > assumption that nsswitch.conf on bpi54 has the same contents. > Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | debian-user@howorth.org.uk |
|---|---|
| Date | 2023-05-10 22:20 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GtYs1-7Z19-5@gated-at.bofh.it> |
| In reply to | #258131 |
gene heskett <gheskett@shentel.net> wrote:
> On 5/10/23 14:22, Brian wrote:
> > A link would be ever so useful.
>
> send browser to cups.org, click help, in right pane, click "printer
> sharing", scroll down about a screenfull to Automatic using IPP
So the answer to Brian's question is
https://www.cups.org/doc/sharing.html and scroll down about a screenful
to Automatic Configuration using IPP
I think :)
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-11 13:10 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <Guclj-87xI-7@gated-at.bofh.it> |
| In reply to | #258131 |
On Wed 10 May 2023 at 16:02:43 -0400, gene heskett wrote: > On 5/10/23 14:22, Brian wrote: > > On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote: > > > > > On 5/10/23 11:29, Brian wrote: > > > > On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote: > > > > > > > > > On 5/10/23 08:17, Brian wrote: > > > > > > > [...] > > > > > > Is /etc/cups/client,conf really, really needed? > > > > > > > That is the first thing cups docs tell you to do, see "printer sharing" > > > > A link would be ever so useful. > > send browser to cups.org, click help, in right pane, click "printer > sharing", scroll down about a screenfull to Automatic using IPP Thanks to you and debian-user@howorth.org.uk. Note that this page is for Apple CUPS. The one for Deian CUPS is at https://openprinting.github.io/cups/doc/sharing.html Havong said that, it should also be noted that the /etc/cups/client.conf is used when a local spooler is not required and is presented as to be used only as absolutely necessary. Hardly "the first thing cups docs tell you to do". Why is it absolutely necessary in your situation? Additionally, a client.conf overrides the default local server. All the analysis in this thread has been carried out assuming a functional local server, so I do not know where that leaves us now if a client.conf has been in the mix all the time.. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-11 18:10 +0200 |
| Subject | SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <Guh1D-8aCB-1@gated-at.bofh.it> |
| In reply to | #258135 |
On 5/11/23 07:07, Brian wrote: > On Wed 10 May 2023 at 16:02:43 -0400, gene heskett wrote: > >> On 5/10/23 14:22, Brian wrote: >>> On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote: >>> >>>> On 5/10/23 11:29, Brian wrote: >>>>> On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote: >>>>> >>>>>> On 5/10/23 08:17, Brian wrote: >>>> >>>>> [...] >>> >>>>> Is /etc/cups/client,conf really, really needed? >>>>> >>>> That is the first thing cups docs tell you to do, see "printer sharing" >>> >>> A link would be ever so useful. >> >> send browser to cups.org, click help, in right pane, click "printer >> sharing", scroll down about a screenfull to Automatic using IPP > > Thanks to you and debian-user@howorth.org.uk. Note that this page is for Apple > CUPS. The one for Debian CUPS is at > > https://openprinting.github.io/cups/doc/sharing.html > Thank you for that link, the other Apple Cups link is first in a google search, and probably close in DDG too since the search was for cups, not openprinting as I was not then aware that Mike had moved. Apple should be ashamed of themselves hanging onto the cups links when they are no longer writing the authors paychecks. > Havong said that, it should also be noted that the /etc/cups/client.conf is used > when a local spooler is not required and is presented as to be used only as > absolutely necessary. Hardly "the first thing cups docs tell you to do". Why is > it absolutely necessary in your situation? > > Additionally, a client.conf overrides the default local server. All the analysis > in this thread has been carried out assuming a functional local server, so I do > not know where that leaves us now if a client.conf has been in the mix all the time.. > I am wondering now if I shouldn't remove the other Listen directives from cupsd.conf, isolating their influence when there are no locally connected printers. Aha!!!! Got it, geany evince okular etc can now print from bpi54! Removing the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a Listen 192.168.xx.yy:631 made the localhost:631/printers on this machine show up in FF on bpi54, all 5 choices from this machine. All that as root of course, and the acid test was me as 1st user, calling up geany to edit that file, which complained it was not writable but to print it on the B&W laser, which it just did. I did have to leave active the "Listen /run/cups/cups.sock" line, it did not work w/o that. I changed the LogLevel back to warn before it fills up a 64BG card, and it seems its all Just Working. That warning in the paragraph above s/not be a show stopper when there is only one machine as the Server on this local network. IMO, it should be speced as applying to any machine that does NOT have any locally connected printers. Your help, and some comments from Greg, have been very helpful. Thank you both for bearing with me, most appreciated. Take care & stay well. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-11 21:20 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GujZv-8crL-1@gated-at.bofh.it> |
| In reply to | #258137 |
On Thu 11 May 2023 at 12:08:01 -0400, gene heskett wrote: > On 5/11/23 07:07, Brian wrote: > > On Wed 10 May 2023 at 16:02:43 -0400, gene heskett wrote: > > > > > On 5/10/23 14:22, Brian wrote: > > > > On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote: > > > > > > > > > On 5/10/23 11:29, Brian wrote: > > > > > > On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote: > > > > > > > > > > > > > On 5/10/23 08:17, Brian wrote: > > > > > > > > > > > [...] > > > > > > > > > > Is /etc/cups/client,conf really, really needed? > > > > > > > > > > > That is the first thing cups docs tell you to do, see "printer sharing" > > > > > > > > A link would be ever so useful. > > > > > > send browser to cups.org, click help, in right pane, click "printer > > > sharing", scroll down about a screenfull to Automatic using IPP > > > > Thanks to you and debian-user@howorth.org.uk. Note that this page is for Apple > > CUPS. The one for Debian CUPS is at > > > > https://openprinting.github.io/cups/doc/sharing.html > > > Thank you for that link, the other Apple Cups link is first in a google > search, and probably close in DDG too since the search was for cups, not > openprinting as I was not then aware that Mike had moved. Apple should be > ashamed of themselves hanging onto the cups links when they are no longer > writing the authors paychecks. > > > Havong said that, it should also be noted that the /etc/cups/client.conf is used > > when a local spooler is not required and is presented as to be used only as > > absolutely necessary. Hardly "the first thing cups docs tell you to do". Why is > > it absolutely necessary in your situation? > > > > Additionally, a client.conf overrides the default local server. All the analysis > > in this thread has been carried out assuming a functional local server, so I do > > not know where that leaves us now if a client.conf has been in the mix all the time.. > > > I am wondering now if I shouldn't remove the other Listen directives from > cupsd.conf, isolating their influence when there are no locally connected > printers. > > Aha!!!! Got it, geany evince okular etc can now print from bpi54! Removing > the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a > > Listen 192.168.xx.yy:631 > > made the localhost:631/printers on this machine show up in FF on bpi54, all > 5 choices from this machine. All that as root of course, and the acid test > was me as 1st user, calling up geany to edit that file, which complained it > was not writable but to print it on the B&W laser, which it just did. I did > have to leave active the "Listen /run/cups/cups.sock" line, it did not work > w/o that. > > I changed the LogLevel back to warn before it fills up a 64BG card, and it > seems its all Just Working. > > That warning in the paragraph above s/not be a show stopper when there is > only one machine as the Server on this local network. IMO, it should be > speced as applying to any machine that does NOT have any locally connected > printers. > > Your help, and some comments from Greg, have been very helpful. Thank you > both for bearing with me, most appreciated. You are, as uaual, treading your own path. Sometimes, it touches on mine or crosses it. Let's leave it there. The acknowledgement is gracious and appreciated. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Vincent Lefevre <vincent@vinc17.net> |
|---|---|
| Date | 2023-05-12 00:00 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <Gumul-8dLC-1@gated-at.bofh.it> |
| In reply to | #258137 |
On 2023-05-11 12:08:01 -0400, gene heskett wrote: > Aha!!!! Got it, geany evince okular etc can now print from bpi54! Removing > the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a > > Listen 192.168.xx.yy:631 > > made the localhost:631/printers on this machine show up in FF on bpi54, all > 5 choices from this machine. Any explanation? -- Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-05-12 00:30 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GumXn-8eaM-1@gated-at.bofh.it> |
| In reply to | #258141 |
On Thu, May 11, 2023 at 11:58:56PM +0200, Vincent Lefevre wrote: > On 2023-05-11 12:08:01 -0400, gene heskett wrote: > > Aha!!!! Got it, geany evince okular etc can now print from bpi54! Removing > > the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a > > > > Listen 192.168.xx.yy:631 > > > > made the localhost:631/printers on this machine show up in FF on bpi54, all > > 5 choices from this machine. > > Any explanation? Seems obvious enough to me. CUPS on bpi54 was only listening to loopback (localhost), but Gene wanted to print through it remotely. So he had to make it listen to the network instead. My questions would be: 1) Can you put *both* Listen lines in, to keep loopback working? 2) Failing that, can you use 0.0.0.0 as the Listen address, to listen on all interfaces? That's the normal convention.
[toc] | [prev] | [next] | [standalone]
| From | Vincent Lefevre <vincent@vinc17.net> |
|---|---|
| Date | 2023-05-12 01:50 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GuocN-8ePR-1@gated-at.bofh.it> |
| In reply to | #258142 |
On 2023-05-11 18:24:39 -0400, Greg Wooledge wrote: > On Thu, May 11, 2023 at 11:58:56PM +0200, Vincent Lefevre wrote: > > On 2023-05-11 12:08:01 -0400, gene heskett wrote: > > > Aha!!!! Got it, geany evince okular etc can now print from bpi54! Removing > > > the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a > > > > > > Listen 192.168.xx.yy:631 > > > > > > made the localhost:631/printers on this machine show up in FF on bpi54, all > > > 5 choices from this machine. > > > > Any explanation? > > Seems obvious enough to me. CUPS on bpi54 was only listening to > loopback (localhost), but Gene wanted to print through it remotely. > So he had to make it listen to the network instead. My question was more on why does this affect localhost:631/printers? > My questions would be: > > 1) Can you put *both* Listen lines in, to keep loopback working? The cupsd.conf(5) man page says: "Multiple Listen directives can be provided to listen on multiple addresses." > 2) Failing that, can you use 0.0.0.0 as the Listen address, to listen on > all interfaces? That's the normal convention. According to the cupsd.conf(5) man page, you can use "Listen *:631". -- Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-12 03:40 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. |
| Message-ID | <GupVf-8fT9-1@gated-at.bofh.it> |
| In reply to | #258144 |
On 5/11/23 19:41, Vincent Lefevre wrote: > On 2023-05-11 18:24:39 -0400, Greg Wooledge wrote: >> On Thu, May 11, 2023 at 11:58:56PM +0200, Vincent Lefevre wrote: >>> On 2023-05-11 12:08:01 -0400, gene heskett wrote: >>>> Aha!!!! Got it, geany evince okular etc can now print from bpi54! Removing >>>> the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a >>>> >>>> Listen 192.168.xx.yy:631 >>>> >>>> made the localhost:631/printers on this machine show up in FF on bpi54, all >>>> 5 choices from this machine. >>> >>> Any explanation? >> >> Seems obvious enough to me. CUPS on bpi54 was only listening to >> loopback (localhost), but Gene wanted to print through it remotely. >> So he had to make it listen to the network instead. > > My question was more on why does this affect localhost:631/printers? > >> My questions would be: >> >> 1) Can you put *both* Listen lines in, to keep loopback working? > > The cupsd.conf(5) man page says: "Multiple Listen directives can be > provided to listen on multiple addresses." > My results seem to indicate otherwise. >> 2) Failing that, can you use 0.0.0.0 as the Listen address, to listen on >> all interfaces? That's the normal convention. > > According to the cupsd.conf(5) man page, you can use "Listen *:631". The possibility exists that the star goes thru a different path, which works. untested here. But folks, that isn't a SWAG, its a plain old WAG. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | Vincent Lefevre <vincent@vinc17.net> |
|---|---|
| Date | 2023-05-12 11:20 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. |
| Message-ID | <Gux6p-8kH1-9@gated-at.bofh.it> |
| In reply to | #258147 |
On 2023-05-11 21:34:11 -0400, gene heskett wrote: > On 5/11/23 19:41, Vincent Lefevre wrote: > > On 2023-05-11 18:24:39 -0400, Greg Wooledge wrote: > > > My questions would be: > > > > > > 1) Can you put *both* Listen lines in, to keep loopback working? > > > > The cupsd.conf(5) man page says: "Multiple Listen directives can be > > provided to listen on multiple addresses." > > > My results seem to indicate otherwise. I don't think that you even showed anything. The only test you should do about that is to try to connect to the port, e.g. with telnet (or nmap can probably tell you). If the connection isn't immediately refused, then the Listen directive is OK. For instance: zira:~> telnet localhost 631 Trying ::1... flushoutput character is 'off'. Connected to localhost. Escape character is '^]'. Fine. And you can try the same thing from a different machine on the network, replacing "localhost" by the IP address of the server, e.g. from another machine on my network: $ telnet 192.168.1.3 631 Trying 192.168.1.3... telnet: Unable to connect to remote host: Connection refused because my CUPS server just has Listen localhost:631 Listen /var/run/cups/cups.sock If the connection is accepted with telnet by using multiple Listen directives, then the Listen configuration is correct. If you can see any other issue related to the printers, then the problem is due to something else. -- Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-12 12:30 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. |
| Message-ID | <Guyca-8ljm-13@gated-at.bofh.it> |
| In reply to | #258156 |
On 5/12/23 05:18, Vincent Lefevre wrote: > On 2023-05-11 21:34:11 -0400, gene heskett wrote: >> On 5/11/23 19:41, Vincent Lefevre wrote: >>> On 2023-05-11 18:24:39 -0400, Greg Wooledge wrote: >>>> My questions would be: >>>> >>>> 1) Can you put *both* Listen lines in, to keep loopback working? >>> >>> The cupsd.conf(5) man page says: "Multiple Listen directives can be >>> provided to listen on multiple addresses." >>> >> My results seem to indicate otherwise. > > I don't think that you even showed anything. The only test you > should do about that is to try to connect to the port, e.g. with > telnet (or nmap can probably tell you). If the connection isn't > immediately refused, then the Listen directive is OK. > > For instance: > > zira:~> telnet localhost 631 > Trying ::1... > flushoutput character is 'off'. > Connected to localhost. > Escape character is '^]'. > > Fine. And you can try the same thing from a different machine on > the network, replacing "localhost" by the IP address of the server, > e.g. from another machine on my network: > > $ telnet 192.168.1.3 631 > Trying 192.168.1.3... > telnet: Unable to connect to remote host: Connection refused > I'm not able to test that on the bpi's, telnet is not installed. > because my CUPS server just has > > Listen localhost:631 > Listen /var/run/cups/cups.sock > > If the connection is accepted with telnet by using multiple Listen > directives, then the Listen configuration is correct. If you can > see any other issue related to the printers, then the problem is > due to something else. > Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-05-12 13:30 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. |
| Message-ID | <Guz8d-8lSa-3@gated-at.bofh.it> |
| In reply to | #258158 |
On Fri, May 12, 2023 at 06:26:00AM -0400, gene heskett wrote: > On 5/12/23 05:18, Vincent Lefevre wrote: > > Fine. And you can try the same thing from a different machine on > > the network, replacing "localhost" by the IP address of the server, > > e.g. from another machine on my network: > > > > $ telnet 192.168.1.3 631 > > Trying 192.168.1.3... > > telnet: Unable to connect to remote host: Connection refused > > > I'm not able to test that on the bpi's, telnet is not installed. Then install it, or use an EQUIVALENT command.
[toc] | [prev] | [next] | [standalone]
| From | Vincent Lefevre <vincent@vinc17.net> |
|---|---|
| Date | 2023-05-12 13:50 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. |
| Message-ID | <Guzrz-8lYM-3@gated-at.bofh.it> |
| In reply to | #258158 |
On 2023-05-12 06:26:00 -0400, gene heskett wrote: > I'm not able to test that on the bpi's, telnet is not installed. You can try with nmap: $ nmap -p 631 localhost $ nmap -p 631 <server_IP> PORT STATE SERVICE 631/tcp open ipp means that you can connect. PORT STATE SERVICE 631/tcp closed ipp means that you can't. -- Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-12 18:20 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. |
| Message-ID | <GuDER-8oDT-7@gated-at.bofh.it> |
| In reply to | #258163 |
On 5/12/23 07:49, Vincent Lefevre wrote: > nmap -p 631 localhost had to install 5 pkgs to get it, but: gene@bpi51:~/src/cups-master$ nmap -p 631 localhost Starting Nmap 7.80 ( https://nmap.org ) at 2023-05-12 11:10 -05 Nmap scan report for localhost (127.0.0.1) Host is up (0.00030s latency). PORT STATE SERVICE 631/tcp open ipp Nmap done: 1 IP address (1 host up) scanned in 0.12 seconds gene@bpi51:~/src/cups-master$ nmap -p 631 192.168.nn.y Starting Nmap 7.80 ( https://nmap.org ) at 2023-05-12 11:11 -05 Nmap scan report for coyote.coyote.den (192.168.nn.y) Host is up (0.00073s latency). PORT STATE SERVICE 631/tcp open ipp Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds ditto for machines name, so the host file is working. Next? Cheers, Geneh Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-12 12:30 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. |
| Message-ID | <Guyca-8ljm-9@gated-at.bofh.it> |
| In reply to | #258156 |
On 5/12/23 05:18, Vincent Lefevre wrote: > On 2023-05-11 21:34:11 -0400, gene heskett wrote: >> On 5/11/23 19:41, Vincent Lefevre wrote: >>> On 2023-05-11 18:24:39 -0400, Greg Wooledge wrote: >>>> My questions would be: >>>> >>>> 1) Can you put *both* Listen lines in, to keep loopback working? >>> >>> The cupsd.conf(5) man page says: "Multiple Listen directives can be >>> provided to listen on multiple addresses." >>> >> My results seem to indicate otherwise. > > I don't think that you even showed anything. The only test you > should do about that is to try to connect to the port, e.g. with > telnet (or nmap can probably tell you). If the connection isn't > immediately refused, then the Listen directive is OK. > > For instance: > > zira:~> telnet localhost 631 > Trying ::1... > flushoutput character is 'off'. > Connected to localhost. > Escape character is '^]'. > > Fine. And you can try the same thing from a different machine on > the network, replacing "localhost" by the IP address of the server, > e.g. from another machine on my network: > > $ telnet 192.168.1.3 631 > Trying 192.168.1.3... > telnet: Unable to connect to remote host: Connection refused > > because my CUPS server just has > > Listen localhost:631 > Listen /var/run/cups/cups.sock > > If the connection is accepted with telnet by using multiple Listen > directives, then the Listen configuration is correct. If you can > see any other issue related to the printers, then the problem is > due to something else. > I'm confused. There is not anything wrong with this machine as a Server. ALL of this muttering and bitching has been because bookworm clients did NOT work. buster clients work great. How many times do I have to say it is/was a CLIENT problem that only exists for BOOKWORM clients. The elephant in the room that most have ignored. What I have done, on the BOOKWORM CLIENT works, but we still don't have a clue why that is so. That said i've dl'd the src from cups, which is broken by not being in a state that will even autogen. So I dl'd the obviously much later src.zip from Mikes new openprinting site. The zip is about 250% the size of the apple tar.gz. Its complete and only needs one argument to configure, with-tls=no. Then it builds and passes a make test, but I've not installed it on this machine. The debian code appears to be the Apple src. What I intend to do is move the openprinting version 2.4.5 to one of the bpi's, see if it will build there, and install it on the bpi to see if that works. But I'm just one, and there is only so much I can do in a day. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | Vincent Lefevre <vincent@vinc17.net> |
|---|---|
| Date | 2023-05-12 13:50 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. |
| Message-ID | <Guzrz-8lYM-1@gated-at.bofh.it> |
| In reply to | #258159 |
On 2023-05-12 06:23:56 -0400, gene heskett wrote: > I'm confused. There is not anything wrong with this machine as a Server. > ALL of this muttering and bitching has been because bookworm clients did NOT > work. buster clients work great. > > How many times do I have to say it is/was a CLIENT problem that only exists > for BOOKWORM clients. The elephant in the room that most have ignored. But you said that the problem was "solved" by modifying a setting corresponding to the Listen directives (in /etc/cups/cupsd.conf). These directives concern the *server* only. I suspect that your problem was solved for another reason (e.g. something else occurred on the network in the mean time, or some config was reloaded at the right time, possibly as a consequence of your testing). Or perhaps it is not solved at all and could reappear in the future (that's why it would be interesting to know the real cause of the problem). -- Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-12 18:10 +0200 |
| Subject | :Re: repeat of previous question thathasgoneunansweredseveraltimes. |
| Message-ID | <GuDve-8oAr-7@gated-at.bofh.it> |
| In reply to | #258162 |
On 5/12/23 07:41, Vincent Lefevre wrote:
> On 2023-05-12 06:23:56 -0400, gene heskett wrote:
>> I'm confused. There is not anything wrong with this machine as a Server.
>> ALL of this muttering and bitching has been because bookworm clients did NOT
>> work. buster clients work great.
>>
>> How many times do I have to say it is/was a CLIENT problem that only exists
>> for BOOKWORM clients. The elephant in the room that most have ignored.
>
> But you said that the problem was "solved" by modifying a setting
> corresponding to the Listen directives (in /etc/cups/cupsd.conf).
> These directives concern the *server* only.
>
Oh, then how does one tell the CLIENT to even use the SERVER? That
statement, added to a created CLIENT.CONF, is not sufficient, Been tried
many times. It does log a lack of auth, also reported here. Is that the
real problem? The lack of any tracing info in the log, even at debug2
level reporting is a huge hindrance to intelligent trouble shooting.
> I suspect that your problem was solved for another reason (e.g.
> something else occurred on the network in the mean time, or some
> config was reloaded at the right time, possibly as a consequence
> of your testing). Or perhaps it is not solved at all and could
> reappear in the future (that's why it would be interesting to
> know the real cause of the problem).
>
copied new cup-master.zip to the bpi51
unpacked it to cups-master in ~/gene/src
./configure --with-tls=no, no show-stoppers.
make no-show stoppers
make test, failed for 2 functions
the report said at one place it got 34 errors but only expected 33
I didn't install
Back to the apple version installed, what fixed the bpi54 ddoes not fix
the bpi51, so Vincent was right to be concerned
It is 100% a "cannot assign requested address error" on the bpi51 as
logged in/var/log/cups/error_log:
E [12/May/2023:10:32:20 -0500] Unable to open listen socket for address
192.168.71.3:631 - Cannot assign requested address.
E [12/May/2023:10:34:45 -0500] Unable to open listen socket for address
[v1.::1]:631 - Cannot assign requested address.
Where its getting the ipv6 addy is a mystery
ip a:
gene@bpi51:~/src/cups-master$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
link/ether ae:c8:46:2e:6b:6b brd ff:ff:ff:ff:ff:ff permaddr
da:0e:c7:cf:52:52
inet 192.168.nn.y/24 brd 192.168.nn.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
ip r:
gene@bpi51:~/src/cups-master$ ip r
default via 192.168.nn.y dev eth0 proto static metric 100
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.nn.y/24 dev eth0 proto kernel scope link src 192.168.nn.y metric
100
So, how can we proceed?
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
Page 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
Back to top | Article view | linux.debian.user
csiph-web