![]() |
News from da outaworlds |
mail files register groups login |
Message-ID: |
Subject | Author |
![]() | Marco Moock |
![]() ![]() | Retro Guy |
![]() ![]() ![]() | Marco |
![]() ![]() ![]() ![]() | Retro Guy |
![]() ![]() ![]() ![]() | Retro Guy |
![]() ![]() ![]() ![]() ![]() | Marco Moock |
![]() ![]() ![]() ![]() ![]() ![]() | Retro Guy |
![]() ![]() ![]() ![]() ![]() ![]() ![]() | Marco Moock |
![]() ![]() ![]() ![]() ![]() ![]() ![]() | Marco Moock |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | Marco Moock |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | Ulf_Kutzner |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | Marco Moock |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | Ulf_Kutzner |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | Marco Moock |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | Stefan Schmitz |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | Ulf_Kutzner |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | Marco Moock |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | Stefan Schmitz |
1 |
Hello!
I noticed that most groups (all except rocksolid) don't receive new
messages.
The logs looks like that:
Mar 03 15:50:36 rocksolid Updating threads for: rocksolid.shared.security...
Mar 03 15:50:36 rocksolid Threads updated for: rocksolid.shared.security
Mar 03 15:50:36 rocksolid CLOSING Local server: Resource id #258
Mar 03 15:50:36 rocksolid Retrieving articles for: rocksolid.shared.test...
Mar 03 15:50:37 rocksolid news.i2pn2.org: rocksolid.shared.test: 211 278 1974 2356 rocksolid.shared.test
Mar 03 15:50:37 rocksolid news.i2pn2.org: for rocksolid.shared.test We are up to date
Mar 03 15:50:37 rocksolid OPENING Local server: Resource id #271
Mar 03 15:50:37 rocksolid Updating threads for: rocksolid.shared.test...
Mar 03 15:50:37 rocksolid Threads updated for: rocksolid.shared.test
Mar 03 15:50:37 rocksolid CLOSING Local server: Resource id #271
I've restarted the job multiple times, same result here.
How can I further diagnose that?
--
kind regards
Marco
Send spam to 1741017077muell@stinkedores.dorfdsl.de
On Mon, 3 Mar 2025 16:53:46 +0100, Marco Moock wrote:
> Hello!
>
> I noticed that most groups (all except rocksolid) don't receive new
> messages.
>
> The logs looks like that:
>
> Mar 03 15:50:36 rocksolid Updating threads for: rocksolid.shared.security...
> Mar 03 15:50:36 rocksolid Threads updated for: rocksolid.shared.security
> Mar 03 15:50:36 rocksolid CLOSING Local server: Resource id #258
> Mar 03 15:50:36 rocksolid Retrieving articles for: rocksolid.shared.test...
> Mar 03 15:50:37 rocksolid news.i2pn2.org: rocksolid.shared.test: 211 278 1974 2356 rocksolid.shared.test
> Mar 03 15:50:37 rocksolid news.i2pn2.org: for rocksolid.shared.test We are up to date
> Mar 03 15:50:37 rocksolid OPENING Local server: Resource id #271
> Mar 03 15:50:37 rocksolid Updating threads for: rocksolid.shared.test...
> Mar 03 15:50:37 rocksolid Threads updated for: rocksolid.shared.test
> Mar 03 15:50:37 rocksolid CLOSING Local server: Resource id #271
>
> I've restarted the job multiple times, same result here.
>
> How can I further diagnose that?
I'm seeing a lot of:
i2pn2 nnrpd[2284778]: <your domain> can't read: Connection reset by peer
Have you changed anything?
On 03.03.2025 13:30 Retro Guy wrote:
> I'm seeing a lot of:
> i2pn2 nnrpd[2284778]: <your domain> can't read: Connection reset by
> peer
>
> Have you changed anything?
No, and sending posts works, so I don't assume a network error. Polling
for certain groups works too.
Where can I find the upstream NNTP logs?
On Tue, 4 Mar 2025 12:30:36 +0000, Marco wrote:
> On 03.03.2025 13:30 Retro Guy wrote:
>
>> I'm seeing a lot of:
>> i2pn2 nnrpd[2284778]: <your domain> can't read: Connection reset by
>> peer
>>
>> Have you changed anything?
>
> No, and sending posts works, so I don't assume a network error. Polling
> for certain groups works too.
>
> Where can I find the upstream NNTP logs?
I'll need to look into it tomorrow maybe. I'm traveling right now.
What I do see is it seems to stop right after the rocksolid groups.
--
Retro Guy
On Tue, 4 Mar 2025 13:30:36 +0100, Marco wrote:
> On 03.03.2025 13:30 Retro Guy wrote:
>
>> I'm seeing a lot of:
>> i2pn2 nnrpd[2284778]: <your domain> can't read: Connection reset by
>> peer
>>
>> Have you changed anything?
>
> No, and sending posts works, so I don't assume a network error. Polling
> for certain groups works too.
>
> Where can I find the upstream NNTP logs?
Please try deleting (renaming):
<spooldir>/rocksolid/<remote_server>:<remote_port>-remote_groups.dat
Then run cron again and see if it works.
i2pn2 is available on port (non-SSL) 119 and 8991
and 563 for SSL.
You "may" wish to try a different port than you are using.
If this removing the file above does not help, I'll try to get you some
server logs.
On 09.03.2025 11:27 Uhr Retro Guy wrote:
> Please try deleting (renaming):
> <spooldir>/rocksolid/<remote_server>:<remote_port>-remote_groups.dat
That seems to have worked.
--
kind regards
Marco
Send spam to 1741516074muell@stinkedores.dorfdsl.de
On Sun, 9 Mar 2025 20:47:44 +0100, Marco Moock wrote:
> On 09.03.2025 11:27 Uhr Retro Guy wrote:
>
>> Please try deleting (renaming):
>> <spooldir>/rocksolid/<remote_server>:<remote_port>-remote_groups.dat
>
> That seems to have worked.
I'm glad it worked. Now I have to consider why it may have broken (the
file)
On 10.03.2025 09:48 Uhr Retro Guy wrote:
> On Sun, 9 Mar 2025 20:47:44 +0100, Marco Moock wrote:
>
> > On 09.03.2025 11:27 Uhr Retro Guy wrote:
> >
> >> Please try deleting (renaming):
> >> <spooldir>/rocksolid/<remote_server>:<remote_port>-remote_groups.dat
> >>
> >
> > That seems to have worked.
>
> I'm glad it worked. Now I have to consider why it may have broken (the
> file)
I was stupid enough to delete it, so I can't really assist here.
--
kind regards
Marco
Send spam to 1741596486muell@stinkedores.dorfdsl.de
On 10.03.2025 09:48 Uhr Retro Guy wrote:
> On Sun, 9 Mar 2025 20:47:44 +0100, Marco Moock wrote:
>
> > On 09.03.2025 11:27 Uhr Retro Guy wrote:
> >
> >> Please try deleting (renaming):
> >> <spooldir>/rocksolid/<remote_server>:<remote_port>-remote_groups.dat
> >>
> >
> > That seems to have worked.
>
> I'm glad it worked. Now I have to consider why it may have broken (the
> file)
It happened again - I've now removed the file again and see what is
going on. Did you find anything that caused it?
--
kind regards
Marco
Send spam to 1741596486muell@stinkedores.dorfdsl.de
On 05.04.2025 15:43 Uhr Marco Moock wrote:
> On 10.03.2025 09:48 Uhr Retro Guy wrote:
>
> > On Sun, 9 Mar 2025 20:47:44 +0100, Marco Moock wrote:
> >
> > > On 09.03.2025 11:27 Uhr Retro Guy wrote:
> > >
> > >> Please try deleting (renaming):
> > >> <spooldir>/rocksolid/<remote_server>:<remote_port>-remote_groups.dat
> > >>
> > >
> > > That seems to have worked.
> >
> > I'm glad it worked. Now I have to consider why it may have broken
> > (the file)
>
> It happened again - I've now removed the file again and see what is
> going on. Did you find anything that caused it?
Not all groups now work fine. Is there anything I can do to track that
down?
Apr 06 08:11:10 rocksolid Preparing to spool de.comp.os.unix.linux.misc:42318
Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10488 <vfr38l$4nr$1@news2.informatik.uni-stuttgart.de>
Apr 06 08:11:10 rocksolid Preparing to spool de.comp.os.unix.linux.misc:42319
Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10489 <slrnvi2aoq.312s4.hjp-usenet4@trintignant.hjp.at>
Apr 06 08:11:10 rocksolid Updating threads for: de.comp.os.unix.linux.misc...
Apr 06 08:11:10 rocksolid Threads updated for:
de.comp.os.unix.linux.misc
Those are old articles, new ones like
<vss203$p8cb$1@yggdrasil.dn.cgarbs.de> are not in the spoolnews log at
all.
--
kind regards
Marco
Send spam to 1743860601muell@stinkedores.dorfdsl.de
On Sun, 6 Apr 2025 8:27:06 +0000, Marco Moock wrote:
> On 05.04.2025 15:43 Uhr Marco Moock wrote:
>
>> On 10.03.2025 09:48 Uhr Retro Guy wrote:
>>
>>> On Sun, 9 Mar 2025 20:47:44 +0100, Marco Moock wrote:
>>>
>>> > On 09.03.2025 11:27 Uhr Retro Guy wrote:
>>> >
>>> >> Please try deleting (renaming):
>>> >> <spooldir>/rocksolid/<remote_server>:<remote_port>-remote_groups.dat
>>> >>
>>> >
>>> > That seems to have worked.
>>>
>>> I'm glad it worked. Now I have to consider why it may have broken
>>> (the file)
>>
>> It happened again - I've now removed the file again and see what is
>> going on. Did you find anything that caused it?
>
> Not all groups now work fine. Is there anything I can do to track that
> down?
>
> Apr 06 08:11:10 rocksolid Preparing to spool
> de.comp.os.unix.linux.misc:42318
> Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10488
> <vfr38l$4nr$1@news2.informatik.uni-stuttgart.de>
> Apr 06 08:11:10 rocksolid Preparing to spool
> de.comp.os.unix.linux.misc:42319
> Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10489
> <slrnvi2aoq.312s4.hjp-usenet4@trintignant.hjp.at>
> Apr 06 08:11:10 rocksolid Updating threads for:
> de.comp.os.unix.linux.misc...
> Apr 06 08:11:10 rocksolid Threads updated for:
> de.comp.os.unix.linux.misc
>
> Those are old articles, new ones like
> <vss203$p8cb$1@yggdrasil.dn.cgarbs.de> are not in the spoolnews log at
> all.
But <vst9p1$dkpp$2@dont-email.me> (other NG) was seen here...
On 06.04.2025 08:52 Uhr Ulf_Kutzner wrote:
> On Sun, 6 Apr 2025 8:27:06 +0000, Marco Moock wrote:
>
> > On 05.04.2025 15:43 Uhr Marco Moock wrote:
> >
> >> On 10.03.2025 09:48 Uhr Retro Guy wrote:
> >>
> >>> On Sun, 9 Mar 2025 20:47:44 +0100, Marco Moock wrote:
> >>>
> >>> > On 09.03.2025 11:27 Uhr Retro Guy wrote:
> >>> >
> >>> >> Please try deleting (renaming):
> >>> >> <spooldir>/rocksolid/<remote_server>:<remote_port>-remote_groups.dat
> >>> >>
> >>> >
> >>> > That seems to have worked.
> >>>
> >>> I'm glad it worked. Now I have to consider why it may have broken
> >>> (the file)
> >>
> >> It happened again - I've now removed the file again and see what is
> >> going on. Did you find anything that caused it?
> >
> > Not all groups now work fine. Is there anything I can do to track
> > that down?
> >
> > Apr 06 08:11:10 rocksolid Preparing to spool
> > de.comp.os.unix.linux.misc:42318
> > Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10488
> > <vfr38l$4nr$1@news2.informatik.uni-stuttgart.de>
> > Apr 06 08:11:10 rocksolid Preparing to spool
> > de.comp.os.unix.linux.misc:42319
> > Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10489
> > <slrnvi2aoq.312s4.hjp-usenet4@trintignant.hjp.at>
> > Apr 06 08:11:10 rocksolid Updating threads for:
> > de.comp.os.unix.linux.misc...
> > Apr 06 08:11:10 rocksolid Threads updated for:
> > de.comp.os.unix.linux.misc
> >
> > Those are old articles, new ones like
> > <vss203$p8cb$1@yggdrasil.dn.cgarbs.de> are not in the spoolnews log
> > at all.
>
> But <vst9p1$dkpp$2@dont-email.me> (other NG) was seen here...
Only after I deleted the remote_groups.dat.
So, the original error is still present and the temporary fix didn't
work in case of this group.
--
kind regards
Marco
Send spam to 1743922362muell@stinkedores.dorfdsl.de
On Sun, 6 Apr 2025 8:27:06 +0000, Marco Moock wrote:
> On 05.04.2025 15:43 Uhr Marco Moock wrote:
>
>> On 10.03.2025 09:48 Uhr Retro Guy wrote:
>>
>>> On Sun, 9 Mar 2025 20:47:44 +0100, Marco Moock wrote:
>>>
>>> > On 09.03.2025 11:27 Uhr Retro Guy wrote:
>>> >
>>> >> Please try deleting (renaming):
>>> >> <spooldir>/rocksolid/<remote_server>:<remote_port>-remote_groups.dat
>>> >>
>>> >
>>> > That seems to have worked.
>>>
>>> I'm glad it worked. Now I have to consider why it may have broken
>>> (the file)
>>
>> It happened again - I've now removed the file again and see what is
>> going on. Did you find anything that caused it?
>
> Not all groups now work fine. Is there anything I can do to track that
> down?
>
> Apr 06 08:11:10 rocksolid Preparing to spool
> de.comp.os.unix.linux.misc:42318
> Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10488
> <vfr38l$4nr$1@news2.informatik.uni-stuttgart.de>
> Apr 06 08:11:10 rocksolid Preparing to spool
> de.comp.os.unix.linux.misc:42319
> Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10489
> <slrnvi2aoq.312s4.hjp-usenet4@trintignant.hjp.at>
> Apr 06 08:11:10 rocksolid Updating threads for:
> de.comp.os.unix.linux.misc...
> Apr 06 08:11:10 rocksolid Threads updated for:
> de.comp.os.unix.linux.misc
>
> Those are old articles, new ones like
> <vss203$p8cb$1@yggdrasil.dn.cgarbs.de> are not in the spoolnews log at
> all.
BTW, since your system started showing (some) half-new and
new messages about the day before yesterday, it takes more
than 20 minutes to show me my fresh postings, which wasn't
the case before.
This is not exactly a complaint because I guess the system
is quite busy with polling messages it did not get for a
period of maybe 12 days. To me it lokks like it polls
complete threads, maybe starting with the older postings.
So, when the content is up to date, the delay in showing
new messages delivered directly to the system might disappear
again.
Regards, ULF
Am 06.04.2025 um 10:27 schrieb Marco Moock:
> On 05.04.2025 15:43 Uhr Marco Moock wrote:
>
>> On 10.03.2025 09:48 Uhr Retro Guy wrote:
>>
>>> On Sun, 9 Mar 2025 20:47:44 +0100, Marco Moock wrote:
>>>
>>>> On 09.03.2025 11:27 Uhr Retro Guy wrote:
>>>>
>>>>> Please try deleting (renaming):
>>>>> <spooldir>/rocksolid/<remote_server>:<remote_port>-remote_groups.dat
>>>>>
>>>>
>>>> That seems to have worked.
>>>
>>> I'm glad it worked. Now I have to consider why it may have broken
>>> (the file)
>>
>> It happened again - I've now removed the file again and see what is
>> going on. Did you find anything that caused it?
>
> Not all groups now work fine. Is there anything I can do to track that
> down?
>
> Apr 06 08:11:10 rocksolid Preparing to spool de.comp.os.unix.linux.misc:42318
> Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10488 <vfr38l$4nr$1@news2.informatik.uni-stuttgart.de>
> Apr 06 08:11:10 rocksolid Preparing to spool de.comp.os.unix.linux.misc:42319
> Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10489 <slrnvi2aoq.312s4.hjp-usenet4@trintignant.hjp.at>
> Apr 06 08:11:10 rocksolid Updating threads for: de.comp.os.unix.linux.misc...
> Apr 06 08:11:10 rocksolid Threads updated for:
> de.comp.os.unix.linux.misc
>
> Those are old articles, new ones like
> <vss203$p8cb$1@yggdrasil.dn.cgarbs.de> are not in the spoolnews log at
> all.
de.etc.sprache.deutsch and de.soc.recht.misc are missing the latest
articles for 18 days.
In several other groups the last message is even much older, but there I
don't know if newer ones have been posted.
On 06.04.2025 09:46 Uhr Ulf_Kutzner wrote:
> BTW, since your system started showing (some) half-new and
> new messages about the day before yesterday, it takes more
> than 20 minutes to show me my fresh postings, which wasn't
> the case before.
I assume the posts will only show up if they are polled again from the
NNTP source. This happens with a systemd timer, and doesn't happen
immediately.
> This is not exactly a complaint because I guess the system
> is quite busy with polling messages it did not get for a
> period of maybe 12 days. To me it lokks like it polls
> complete threads, maybe starting with the older postings.
>
> So, when the content is up to date, the delay in showing
> new messages delivered directly to the system might disappear
> again.
I hope so, but I see there is a bug in general which needs to be fixed.
--
kind regards
Marco
Send spam to 1743925597muell@stinkedores.dorfdsl.de
On Sun, 6 Apr 2025 10:06:52 +0000, Stefan Schmitz wrote:
> Am 06.04.2025 um 10:27 schrieb Marco Moock:
>> On 05.04.2025 15:43 Uhr Marco Moock wrote:
>>
>>> On 10.03.2025 09:48 Uhr Retro Guy wrote:
>>>
>>>> On Sun, 9 Mar 2025 20:47:44 +0100, Marco Moock wrote:
>>>>
>>>>> On 09.03.2025 11:27 Uhr Retro Guy wrote:
>>>>>
>>>>>> Please try deleting (renaming):
>>>>>> <spooldir>/rocksolid/<remote_server>:<remote_port>-remote_groups.dat
>>>>>>
>>>>>
>>>>> That seems to have worked.
>>>>
>>>> I'm glad it worked. Now I have to consider why it may have broken
>>>> (the file)
>>>
>>> It happened again - I've now removed the file again and see what is
>>> going on. Did you find anything that caused it?
>>
>> Not all groups now work fine. Is there anything I can do to track that
>> down?
>>
>> Apr 06 08:11:10 rocksolid Preparing to spool
>> de.comp.os.unix.linux.misc:42318
>> Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10488
>> <vfr38l$4nr$1@news2.informatik.uni-stuttgart.de>
>> Apr 06 08:11:10 rocksolid Preparing to spool
>> de.comp.os.unix.linux.misc:42319
>> Apr 06 08:11:10 rocksolid Spooling: de.comp.os.unix.linux.misc:10489
>> <slrnvi2aoq.312s4.hjp-usenet4@trintignant.hjp.at>
>> Apr 06 08:11:10 rocksolid Updating threads for:
>> de.comp.os.unix.linux.misc...
>> Apr 06 08:11:10 rocksolid Threads updated for:
>> de.comp.os.unix.linux.misc
>>
>> Those are old articles, new ones like
>> <vss203$p8cb$1@yggdrasil.dn.cgarbs.de> are not in the spoolnews log at
>> all.
>
> de.etc.sprache.deutsch and de.soc.recht.misc are missing the latest
> articles for 18 days.
>
> In several other groups the last message is even much older, but there I
> don't know if newer ones have been posted.
The thread you started 4 hours ago can be found with
3 messages.
On 06.04.2025 13:52 Uhr Ulf_Kutzner wrote:
> The thread you started 4 hours ago can be found with
> 3 messages.
I did another reset of the .dat file, maybe that causes that.
--
kind regards
Marco
Send spam to 1743940375muell@stinkedores.dorfdsl.de
Am 06.04.2025 um 16:43 schrieb Marco Moock:
> On 06.04.2025 13:52 Uhr Ulf_Kutzner wrote:
>
>> The thread you started 4 hours ago can be found with
>> 3 messages.
>
> I did another reset of the .dat file, maybe that causes that.
That is interesting. This new thread shows up, but not Ulfs reply to an
old thread some minutes before.
1 |