Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. 2.6.x "cxnsleep transfer permission denied"? (Nix)
2. Re: 2.6.x "cxnsleep transfer permission denied"? (Nix)
3. Re: 2.6.x "cxnsleep transfer permission denied"? (Russ Allbery)
4. Re: 2.6.x "cxnsleep transfer permission denied"? (Russ Allbery)
----------------------------------------------------------------------
Message: 1
Date: Wed, 24 Jan 2018 22:05:29 +0000
From: Nix <[email protected]>
To: [email protected]
Subject: 2.6.x "cxnsleep transfer permission denied"?
Message-ID: <[email protected]>
Content-Type: text/plain
So I just upgraded to 2.6.x latest (from 2.5 as of mid-2015), and now
every single one of my feeds is saying this:
Jan 24 21:49:45 loom warning: kzdoos.xs4all.nl:0 cxnsleep transfer permission
denied
Jan 24 21:49:45 loom notice: kzdoos.xs4all.nl checkpoint seconds 0 offered 1
accepted 0 refused 0 rejected 0 missing 0 accsize 0 rejsize 0 spooled 0
on_close 0 unspooled 1 deferred 0/0.0 requeued 1 queue 0.0/200:100,0,0,0,0,0
Jan 24 21:49:45 loom notice: kzdoos.xs4all.nl final seconds 0 offered 1
accepted 0 refused 0 rejected 0 missing 0 accsize 0 rejsize 0 spooled 0
on_close 0 unspooled 1 deferred 0/0.0 requeued 1 queue 0.0/200:100,0,0,0,0,0
Jan 24 21:50:15 loom notice: kzdoos.xs4all.nl:0 connected
Jan 24 21:50:15 loom notice: kzdoos.xs4all.nl remote MODE STREAM failed
Jan 24 21:50:15 loom notice: kzdoos.xs4all.nl checkpoint seconds 30 spooled 1
on_close 1 sleeping 0
Jan 24 21:50:15 loom notice: kzdoos.xs4all.nl final seconds 30 spooled 1
on_close 1 sleeping 0
It is... less than clear what "cxnsleep transfer permission denied"
means, or even whether it comes from my end or the other end: from the
source, it appears to be in response to a "480 Transfer permission
denied", but who is emitting this response and why is less than clear.
Incoming news seems to be flowing, and though I'm not sure yet about
outgoing innfeed's statistics suggest that things are fine.
(It is also less than clear why this has suddenly started happening in
2.6 when I left the config files utterly unchanged from 2.5 specifically
to stop anything like this from happening. Maybe it's just a new
message, and the condition is old?)
------------------------------
Message: 2
Date: Thu, 25 Jan 2018 01:18:28 +0000
From: Nix <[email protected]>
To: [email protected]
Subject: Re: 2.6.x "cxnsleep transfer permission denied"?
Message-ID: <[email protected]>
Content-Type: text/plain
On 24 Jan 2018, Nix spake thusly:
> So I just upgraded to 2.6.x latest (from 2.5 as of mid-2015), and now
> every single one of my feeds is saying this:
>
> Jan 24 21:49:45 loom warning: kzdoos.xs4all.nl:0 cxnsleep transfer permission
> denied
> Jan 24 21:49:45 loom notice: kzdoos.xs4all.nl checkpoint seconds 0 offered 1
> accepted 0 refused 0 rejected 0 missing 0 accsize 0 rejsize 0 spooled 0
> on_close 0 unspooled 1 deferred 0/0.0 requeued 1 queue 0.0/200:100,0,0,0,0,0
> Jan 24 21:49:45 loom notice: kzdoos.xs4all.nl final seconds 0 offered 1
> accepted 0 refused 0 rejected 0 missing 0 accsize 0 rejsize 0 spooled 0
> on_close 0 unspooled 1 deferred 0/0.0 requeued 1 queue 0.0/200:100,0,0,0,0,0
> Jan 24 21:50:15 loom notice: kzdoos.xs4all.nl:0 connected
> Jan 24 21:50:15 loom notice: kzdoos.xs4all.nl remote MODE STREAM failed
> Jan 24 21:50:15 loom notice: kzdoos.xs4all.nl checkpoint seconds 30 spooled 1
> on_close 1 sleeping 0
> Jan 24 21:50:15 loom notice: kzdoos.xs4all.nl final seconds 30 spooled 1
> on_close 1 sleeping 0
>
> It is... less than clear what "cxnsleep transfer permission denied"
> means, or even whether it comes from my end or the other end: from the
> source, it appears to be in response to a "480 Transfer permission
> denied", but who is emitting this response and why is less than clear.
> Incoming news seems to be flowing, and though I'm not sure yet about
> outgoing innfeed's statistics suggest that things are fine.
Speculation: is this because I'm suddenly connecting to/from all my
peers via their IPv6 addresses, but they only know to grant me
permission to read/post over IPv4? If so, it's *really annoying* that I
can't turn IPv6 off temporarily until my peers have been informed of my
IPv6 address :(
------------------------------
Message: 3
Date: Wed, 24 Jan 2018 17:55:03 -0800
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: 2.6.x "cxnsleep transfer permission denied"?
Message-ID: <[email protected]>
Content-Type: text/plain
Nix <[email protected]> writes:
> It is... less than clear what "cxnsleep transfer permission denied"
> means, or even whether it comes from my end or the other end: from the
> source, it appears to be in response to a "480 Transfer permission
> denied", but who is emitting this response and why is less than clear.
> Incoming news seems to be flowing, and though I'm not sure yet about
> outgoing innfeed's statistics suggest that things are fine.
It's coming from the remote side and generally means that your connecting
IP address is not in their incoming.conf (and its latest cached DNS
entries).
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Message: 4
Date: Wed, 24 Jan 2018 17:56:29 -0800
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: 2.6.x "cxnsleep transfer permission denied"?
Message-ID: <[email protected]>
Content-Type: text/plain
Nix <[email protected]> writes:
> Speculation: is this because I'm suddenly connecting to/from all my
> peers via their IPv6 addresses, but they only know to grant me
> permission to read/post over IPv4? If so, it's *really annoying* that I
> can't turn IPv6 off temporarily until my peers have been informed of my
> IPv6 address :(
The log messages are from innfeed, so just set force-ipv4 in innfeed.conf?
force-ipv4
This key requires a boolean value. By default, it is set to false.
Setting it to true is the same as setting bindaddress6 to "none" and
removing bindaddress from "none" if it was set.
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 102, Issue 3
*******************************************
