Hello!

I've seen that the NoCeM processing doesn't work as intended currently.

It didn't match all in the first run, something seems to be wrong.

root@pi-dach:~# tail -f /var/spool/rslight/log/nocem.log
Nov 20 06:53:12 spoolnews Good signature in: nocem@eternal-september.org[2024.11.20.06.48.49]7UJV71
Nov 20 06:55:27 spoolnews Good Issuer and Type for: i2pn2-nocem@i2pn2.org[2024.11.20.06.53.16]8DpQdd
Nov 20 06:55:27 spoolnews Good signature in: i2pn2-nocem@i2pn2.org[2024.11.20.06.53.16]8DpQdd
Nov 20 06:55:27 spoolnews TRYING: <86d12f8f-4@6dc-4bee-92b6-1c0ad35c9998> IN: de.soc.misc
Nov 20 06:55:27 spoolnews TRYING: <376cdb09-3@ae3-4b39-aae4-68efe0c15e40> IN: de.soc.misc
Nov 20 06:55:27 rocksolid DELETING: <376cdb09-3@ae3-4b39-aae4-68efe0c15e40> IN: de.soc.misc
Nov 20 06:55:29 spoolnews TRYING: <4ce8313e-2@73a-464c-b249-790665a2eb16> IN: de.talk.tagesgeschehen
Nov 20 06:55:29 Group not found: de.talk.tagesgeschehen
Nov 20 06:55:29 spoolnews Good Issuer and Type for: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
Nov 20 06:55:29 spoolnews Good signature in: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U^C
root@pi-dach:~# mv /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U /var/spool/rslight/nocem/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
root@pi-dach:~# systemctl restart rslight
root@pi-dach:~# tail -f /var/spool/rslight/log/nocem.log
Nov 20 06:55:29 spoolnews TRYING: <4ce8313e-2@73a-464c-b249-790665a2eb16> IN: de.talk.tagesgeschehen
Nov 20 06:55:29 Group not found: de.talk.tagesgeschehen
Nov 20 06:55:29 spoolnews Good Issuer and Type for: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
Nov 20 06:55:29 spoolnews Good signature in: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
Nov 20 06:56:56 spoolnews Good Issuer and Type for: i2pn2-nocem@i2pn2.org[2024.11.20.06.55.34]IOAs8g
Nov 20 06:56:56 spoolnews Good signature in: i2pn2-nocem@i2pn2.org[2024.11.20.06.55.34]IOAs8g
Nov 20 06:56:56 spoolnews TRYING: <e0de2718-8@c36-4ff0-bc4e-259e4b35649e> IN: de.talk.tagesgeschehen
Nov 20 06:56:56 Group not found: de.talk.tagesgeschehen
Nov 20 06:56:56 spoolnews TRYING: <ff42bd54-1@ac6-47b5-ba9d-3bac61e47c40> IN: de.soc.misc
Nov 20 06:56:56 rocksolid DELETING: <ff42bd54-1@ac6-47b5-ba9d-3bac61e47c40> IN: de.soc.misc
Nov 20 06:57:00 spoolnews Good Issuer and Type for: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
Nov 20 06:57:00 spoolnews Good signature in: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
Nov 20 06:57:00 spoolnews Good Issuer and Type for: nocem@eternal-september.org[2024.11.20.06.55.34]nzViBL
Nov 20 06:57:00 spoolnews Good signature in: nocem@eternal-september.org[2024.11.20.06.55.34]nzViBL^C
root@pi-dach:~#
m@ryz:~$

--
kind regards
Marco

Send spam to 1732120676muell@stinkedores.dorfdsl.de

Marco Moock wrote:

> Hello!
>
> I've seen that the NoCeM processing doesn't work as intended currently.
>
> It didn't match all in the first run, something seems to be wrong.
>
> root@pi-dach:~# tail -f /var/spool/rslight/log/nocem.log
> Nov 20 06:53:12 spoolnews Good signature in: nocem@eternal-september.org[2024.11.20.06.48.49]7UJV71
> Nov 20 06:55:27 spoolnews Good Issuer and Type for: i2pn2-nocem@i2pn2.org[2024.11.20.06.53.16]8DpQdd
> Nov 20 06:55:27 spoolnews Good signature in: i2pn2-nocem@i2pn2.org[2024.11.20.06.53.16]8DpQdd
> Nov 20 06:55:27 spoolnews TRYING: <86d12f8f-4@6dc-4bee-92b6-1c0ad35c9998> IN: de.soc.misc
> Nov 20 06:55:27 spoolnews TRYING: <376cdb09-3@ae3-4b39-aae4-68efe0c15e40> IN: de.soc.misc
> Nov 20 06:55:27 rocksolid DELETING: <376cdb09-3@ae3-4b39-aae4-68efe0c15e40> IN: de.soc.misc
> Nov 20 06:55:29 spoolnews TRYING: <4ce8313e-2@73a-464c-b249-790665a2eb16> IN: de.talk.tagesgeschehen
> Nov 20 06:55:29 Group not found: de.talk.tagesgeschehen
> Nov 20 06:55:29 spoolnews Good Issuer and Type for: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> Nov 20 06:55:29 spoolnews Good signature in: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U^C
> root@pi-dach:~# mv /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U /var/spool/rslight/nocem/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> root@pi-dach:~# systemctl restart rslight
> root@pi-dach:~# tail -f /var/spool/rslight/log/nocem.log
> Nov 20 06:55:29 spoolnews TRYING: <4ce8313e-2@73a-464c-b249-790665a2eb16> IN: de.talk.tagesgeschehen
> Nov 20 06:55:29 Group not found: de.talk.tagesgeschehen
> Nov 20 06:55:29 spoolnews Good Issuer and Type for: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> Nov 20 06:55:29 spoolnews Good signature in: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> Nov 20 06:56:56 spoolnews Good Issuer and Type for: i2pn2-nocem@i2pn2.org[2024.11.20.06.55.34]IOAs8g
> Nov 20 06:56:56 spoolnews Good signature in: i2pn2-nocem@i2pn2.org[2024.11.20.06.55.34]IOAs8g
> Nov 20 06:56:56 spoolnews TRYING: <e0de2718-8@c36-4ff0-bc4e-259e4b35649e> IN: de.talk.tagesgeschehen
> Nov 20 06:56:56 Group not found: de.talk.tagesgeschehen
> Nov 20 06:56:56 spoolnews TRYING: <ff42bd54-1@ac6-47b5-ba9d-3bac61e47c40> IN: de.soc.misc
> Nov 20 06:56:56 rocksolid DELETING: <ff42bd54-1@ac6-47b5-ba9d-3bac61e47c40> IN: de.soc.misc
> Nov 20 06:57:00 spoolnews Good Issuer and Type for: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> Nov 20 06:57:00 spoolnews Good signature in: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> Nov 20 06:57:00 spoolnews Good Issuer and Type for: nocem@eternal-september.org[2024.11.20.06.55.34]nzViBL
> Nov 20 06:57:00 spoolnews Good signature in: nocem@eternal-september.org[2024.11.20.06.55.34]nzViBL^C
> root@pi-dach:~#
> m@ryz:~$
>

I'm not certain I see what you are seeing. I checked the MIDs on your
site and they seem to not exist. Are you referring to where it says
'TRYING' but not followed by 'DELETING'? Those are the ones I checked
and I don't see them on your site.

Of course I may not understand what you're seeing.

Since these are bot messages in de.*, and you are applying e-s and i2pn
NoCeM, maybe one NoCeM is deleting them, then when you read the next
NoCeM it is listed there but already deleted, so no 'DELETING' line.

Both e-s and i2pn2 most likely have almost the same de.* bot articles
listed.

Maybe I can add more logging like, 'Article not found'?

Please let me know if I'm missing what you're saying, so we can fix the
problem if there is one.

--
Retro Guy

On 20.11.2024 um 17:01 Uhr Retro Guy wrote:

> Both e-s and i2pn2 most likely have almost the same de.* bot articles
> listed.
>
> Maybe I can add more logging like, 'Article not found'?
>
> Please let me know if I'm missing what you're saying, so we can fix
> the problem if there is one.

Maybe it got deleted after that because I copied all nocems from
processes to the parent and rerun the script.

Now a new example. The article exists, the NoCeM will be processed
again, but the article won't be deleted.

root@pi-dach:~# fgrep -r '<e150a205-b@abb-4dae-9d27-b65c06ec2682>' /var/spool/rslight/nocem/*
/var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U:<e150a205-b@abb-4dae-9d27-b65c06ec2682> de.soc.wirtschaft
root@pi-dach:~# mv /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U /var/spool/rslight/nocem/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
root@pi-dach:~# systemctl restart rslight
root@pi-dach:~# tail -f /var/spool/rslight/log/nocem.log
Nov 20 17:16:51 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.17.04.51]rjz1ag
Nov 20 17:53:09 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.17.41.05]jbecPq
Nov 20 18:05:12 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.17.53.12]V15j6u
Nov 20 18:05:12 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.17.53.13]aOe5Ce
Nov 20 18:17:25 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.18.05.15]1qnkiG
Nov 20 18:41:42 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.18.29.39]UNqeKA
Nov 20 18:41:42 spoolnews Bad Issuer or Type for: robot@pasdenom.info[2024.11.20.18.29.39]rV3AEk
Nov 20 19:05:02 spoolnews Good Issuer and Type for: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
Nov 20 19:05:02 spoolnews Good signature in: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
Nov 20 19:05:02 spoolnews Bad Issuer or Type for: robot@pasdenom.info[2024.11.20.18.53.52]iyJ4pc

^C
root@pi-dach:~# fgrep -r '<e150a205-b@abb-4dae-9d27-b65c06ec2682>' /var/spool/rslight/nocem/*
/var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U:<e150a205-b@abb-4dae-9d27-b65c06ec2682> de.soc.wirtschaft
root@pi-dach:~#

--
kind regards
Marco

Send spam to 1732118503muell@cartoonies.org

Marco Moock wrote:

> On 20.11.2024 um 17:01 Uhr Retro Guy wrote:
>
>> Both e-s and i2pn2 most likely have almost the same de.* bot articles
>> listed.
>>
>> Maybe I can add more logging like, 'Article not found'?
>>
>> Please let me know if I'm missing what you're saying, so we can fix
>> the problem if there is one.
>
> Maybe it got deleted after that because I copied all nocems from
> processes to the parent and rerun the script.
>
> Now a new example. The article exists, the NoCeM will be processed
> again, but the article won't be deleted.
>
> root@pi-dach:~# fgrep -r '<e150a205-b@abb-4dae-9d27-b65c06ec2682>' /var/spool/rslight/nocem/*
> /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U:<e150a205-b@abb-4dae-9d27-b65c06ec2682> de.soc.wirtschaft
> root@pi-dach:~# mv /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U /var/spool/rslight/nocem/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> root@pi-dach:~# systemctl restart rslight
> root@pi-dach:~# tail -f /var/spool/rslight/log/nocem.log
> Nov 20 17:16:51 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.17.04.51]rjz1ag
> Nov 20 17:53:09 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.17.41.05]jbecPq
> Nov 20 18:05:12 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.17.53.12]V15j6u
> Nov 20 18:05:12 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.17.53.13]aOe5Ce
> Nov 20 18:17:25 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.18.05.15]1qnkiG
> Nov 20 18:41:42 spoolnews Bad Issuer or Type for: i2pn2-nocem@i2pn2.org[2024.11.20.18.29.39]UNqeKA
> Nov 20 18:41:42 spoolnews Bad Issuer or Type for: robot@pasdenom.info[2024.11.20.18.29.39]rV3AEk
> Nov 20 19:05:02 spoolnews Good Issuer and Type for: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> Nov 20 19:05:02 spoolnews Good signature in: nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> Nov 20 19:05:02 spoolnews Bad Issuer or Type for: robot@pasdenom.info[2024.11.20.18.53.52]iyJ4pc
>
>
> ^C
> root@pi-dach:~# fgrep -r '<e150a205-b@abb-4dae-9d27-b65c06ec2682>' /var/spool/rslight/nocem/*
> /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U:<e150a205-b@abb-4dae-9d27-b65c06ec2682> de.soc.wirtschaft
> root@pi-dach:~#
>
Ok, I see it here. I will need to add some more logging to track it
down. I'll get on that asap. I'll let you know when I have any changes
to the script.

--
Retro Guy

On Wed, 20 Nov 2024 19:06:40 +0000, Marco Moock wrote:

> On 20.11.2024 um 17:01 Uhr Retro Guy wrote:
>
>> Both e-s and i2pn2 most likely have almost the same de.* bot articles
>> listed.
>>
>> Maybe I can add more logging like, 'Article not found'?
>>
>> Please let me know if I'm missing what you're saying, so we can fix
>> the problem if there is one.
>
> Maybe it got deleted after that because I copied all nocems from
> processes to the parent and rerun the script.
>
> Now a new example. The article exists, the NoCeM will be processed
> again, but the article won't be deleted.
>
> root@pi-dach:~# fgrep -r '<e150a205-b@abb-4dae-9d27-b65c06ec2682>'
> /var/spool/rslight/nocem/*
> /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U:<e150a205-b@abb-4dae-9d27-b65c06ec2682>
> de.soc.wirtschaft
> root@pi-dach:~# mv
> /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> /var/spool/rslight/nocem/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> root@pi-dach:~# systemctl restart rslight
> root@pi-dach:~# tail -f /var/spool/rslight/log/nocem.log
> Nov 20 17:16:51 spoolnews Bad Issuer or Type for:
> i2pn2-nocem@i2pn2.org[2024.11.20.17.04.51]rjz1ag
> Nov 20 17:53:09 spoolnews Bad Issuer or Type for:
> i2pn2-nocem@i2pn2.org[2024.11.20.17.41.05]jbecPq
> Nov 20 18:05:12 spoolnews Bad Issuer or Type for:
> i2pn2-nocem@i2pn2.org[2024.11.20.17.53.12]V15j6u
> Nov 20 18:05:12 spoolnews Bad Issuer or Type for:
> i2pn2-nocem@i2pn2.org[2024.11.20.17.53.13]aOe5Ce
> Nov 20 18:17:25 spoolnews Bad Issuer or Type for:
> i2pn2-nocem@i2pn2.org[2024.11.20.18.05.15]1qnkiG
> Nov 20 18:41:42 spoolnews Bad Issuer or Type for:
> i2pn2-nocem@i2pn2.org[2024.11.20.18.29.39]UNqeKA
> Nov 20 18:41:42 spoolnews Bad Issuer or Type for:
> robot@pasdenom.info[2024.11.20.18.29.39]rV3AEk
> Nov 20 19:05:02 spoolnews Good Issuer and Type for:
> nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> Nov 20 19:05:02 spoolnews Good signature in:
> nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> Nov 20 19:05:02 spoolnews Bad Issuer or Type for:
> robot@pasdenom.info[2024.11.20.18.53.52]iyJ4pc

Does the log file ever show 'TRYING' for the message?

Could you please provide the MID of the nocem message itself please?

--
Retro Guy

On Wed, 20 Nov 2024 20:28:46 +0000, Retro Guy wrote:

> On Wed, 20 Nov 2024 19:06:40 +0000, Marco Moock wrote:
>
>> On 20.11.2024 um 17:01 Uhr Retro Guy wrote:
>>
>>> Both e-s and i2pn2 most likely have almost the same de.* bot articles
>>> listed.
>>>
>>> Maybe I can add more logging like, 'Article not found'?
>>>
>>> Please let me know if I'm missing what you're saying, so we can fix
>>> the problem if there is one.
>>
>> Maybe it got deleted after that because I copied all nocems from
>> processes to the parent and rerun the script.
>>
>> Now a new example. The article exists, the NoCeM will be processed
>> again, but the article won't be deleted.
>>
>> root@pi-dach:~# fgrep -r '<e150a205-b@abb-4dae-9d27-b65c06ec2682>'
>> /var/spool/rslight/nocem/*
>> /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U:<e150a205-b@abb-4dae-9d27-b65c06ec2682>
>> de.soc.wirtschaft
>> root@pi-dach:~# mv
>> /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
>> /var/spool/rslight/nocem/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
>> root@pi-dach:~# systemctl restart rslight
>> root@pi-dach:~# tail -f /var/spool/rslight/log/nocem.log
>> Nov 20 17:16:51 spoolnews Bad Issuer or Type for:
>> i2pn2-nocem@i2pn2.org[2024.11.20.17.04.51]rjz1ag
>> Nov 20 17:53:09 spoolnews Bad Issuer or Type for:
>> i2pn2-nocem@i2pn2.org[2024.11.20.17.41.05]jbecPq
>> Nov 20 18:05:12 spoolnews Bad Issuer or Type for:
>> i2pn2-nocem@i2pn2.org[2024.11.20.17.53.12]V15j6u
>> Nov 20 18:05:12 spoolnews Bad Issuer or Type for:
>> i2pn2-nocem@i2pn2.org[2024.11.20.17.53.13]aOe5Ce
>> Nov 20 18:17:25 spoolnews Bad Issuer or Type for:
>> i2pn2-nocem@i2pn2.org[2024.11.20.18.05.15]1qnkiG
>> Nov 20 18:41:42 spoolnews Bad Issuer or Type for:
>> i2pn2-nocem@i2pn2.org[2024.11.20.18.29.39]UNqeKA
>> Nov 20 18:41:42 spoolnews Bad Issuer or Type for:
>> robot@pasdenom.info[2024.11.20.18.29.39]rV3AEk
>> Nov 20 19:05:02 spoolnews Good Issuer and Type for:
>> nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
>> Nov 20 19:05:02 spoolnews Good signature in:
>> nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
>> Nov 20 19:05:02 spoolnews Bad Issuer or Type for:
>> robot@pasdenom.info[2024.11.20.18.53.52]iyJ4pc
>
> Does the log file ever show 'TRYING' for the message?
>
> Could you please provide the MID of the nocem message itself please?

Ok, I found the MID.

Do any articles listed in that nocem get 'TRYING' at all? Or just some
of them? I'll try it myself here also.

--
Retro Guy

On Wed, 20 Nov 2024 20:32:10 +0000, Retro Guy wrote:

> On Wed, 20 Nov 2024 20:28:46 +0000, Retro Guy wrote:
>
>> On Wed, 20 Nov 2024 19:06:40 +0000, Marco Moock wrote:
>>
>>> On 20.11.2024 um 17:01 Uhr Retro Guy wrote:
>>>
>>>> Both e-s and i2pn2 most likely have almost the same de.* bot articles
>>>> listed.
>>>>
>>>> Maybe I can add more logging like, 'Article not found'?
>>>>
>>>> Please let me know if I'm missing what you're saying, so we can fix
>>>> the problem if there is one.
>>>
>>> Maybe it got deleted after that because I copied all nocems from
>>> processes to the parent and rerun the script.
>>>
>>> Now a new example. The article exists, the NoCeM will be processed
>>> again, but the article won't be deleted.
>>>
<snip>
>>
>> Does the log file ever show 'TRYING' for the message?
>>
>> Could you please provide the MID of the nocem message itself please?
>
> Ok, I found the MID.
>
> Do any articles listed in that nocem get 'TRYING' at all? Or just some
> of them? I'll try it myself here also.

Please give the attached 'nocem.php' a test. No changes to logging, but
some changes to reading the nocem.

--
Retro Guy

On Wed, 20 Nov 2024 21:04:40 +0000, Retro Guy wrote:

> On Wed, 20 Nov 2024 20:32:10 +0000, Retro Guy wrote:
>
>> On Wed, 20 Nov 2024 20:28:46 +0000, Retro Guy wrote:
>>
>>> On Wed, 20 Nov 2024 19:06:40 +0000, Marco Moock wrote:
>>>
>>>> On 20.11.2024 um 17:01 Uhr Retro Guy wrote:
>>>>
>>>>> Both e-s and i2pn2 most likely have almost the same de.* bot articles
>>>>> listed.
>>>>>
>>>>> Maybe I can add more logging like, 'Article not found'?
>>>>>
>>>>> Please let me know if I'm missing what you're saying, so we can fix
>>>>> the problem if there is one.
>>>>
>>>> Maybe it got deleted after that because I copied all nocems from
>>>> processes to the parent and rerun the script.
>>>>
>>>> Now a new example. The article exists, the NoCeM will be processed
>>>> again, but the article won't be deleted.
>>>>
> <snip>
>>>
>>> Does the log file ever show 'TRYING' for the message?
>>>
>>> Could you please provide the MID of the nocem message itself please?
>>
>> Ok, I found the MID.
>>
>> Do any articles listed in that nocem get 'TRYING' at all? Or just some
>> of them? I'll try it myself here also.
>
> Please give the attached 'nocem.php' a test. No changes to logging, but
> some changes to reading the nocem.

Ignore me, ignore that attached nocem.php. I'll have something later
today.

--
Retro Guy

On Thu, 21 Nov 2024 9:42:33 +0000, Retro Guy wrote:

> On Wed, 20 Nov 2024 21:04:40 +0000, Retro Guy wrote:
>
>> On Wed, 20 Nov 2024 20:32:10 +0000, Retro Guy wrote:
>>
>>> On Wed, 20 Nov 2024 20:28:46 +0000, Retro Guy wrote:
>>>
>>>> On Wed, 20 Nov 2024 19:06:40 +0000, Marco Moock wrote:
>>>>
>>>>> On 20.11.2024 um 17:01 Uhr Retro Guy wrote:
>>>>>
>>>>>> Both e-s and i2pn2 most likely have almost the same de.* bot articles
>>>>>> listed.
>>>>>>
>>>>>> Maybe I can add more logging like, 'Article not found'?
>>>>>>
>>>>>> Please let me know if I'm missing what you're saying, so we can fix
>>>>>> the problem if there is one.
>>>>>
>>>>> Maybe it got deleted after that because I copied all nocems from
>>>>> processes to the parent and rerun the script.
>>>>>
>>>>> Now a new example. The article exists, the NoCeM will be processed
>>>>> again, but the article won't be deleted.
>>>>>
>> <snip>
>>>>
>>>> Does the log file ever show 'TRYING' for the message?
>>>>
>>>> Could you please provide the MID of the nocem message itself please?
>>>
>>> Ok, I found the MID.
>>>
>>> Do any articles listed in that nocem get 'TRYING' at all? Or just some
>>> of them? I'll try it myself here also.
>>
>> Please give the attached 'nocem.php' a test. No changes to logging, but
>> some changes to reading the nocem.
>
> Ignore me, ignore that attached nocem.php. I'll have something later
> today.

I've added quite a bit of logging. This is some, but there is more for
other things that could occur:

-----
Nov 21 15:15:02 spoolnews <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not
found in history database (this is not an error)
Nov 21 15:15:02 spoolnews TRYING:
<01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> IN: de.rec.sport.misc
Nov 21 15:15:02 other <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not found
in: de.rec.sport.misc
-----
Nov 21 15:15:02 spoolnews <9425f3f5-0@192-418d-bd4d-a8c5641eb1ad> not
found in history database (this is not an error)
Nov 21 15:15:02 spoolnews TRYING:
<9425f3f5-0@192-418d-bd4d-a8c5641eb1ad> IN: de.soc.misc
Nov 21 15:15:02 Group not found: de.soc.misc
-----

I've also cleaned up identifying the mid and group names from the NoCeM,
allowing for tabs or spaces, and spaces or commas, depending on how each
admin is producing their scripts.

What we need to do is let it run, and see what is logged, or what part
of the logging is never reached. I've been letting it run for hours now
and it seems ok, but can never be sure until it's in production.

I'll be moving it into 'devel' soon. I'll let you know.

--
Retro Guy

On Thu, 21 Nov 2024 15:20:54 +0000, Retro Guy wrote:

> On Thu, 21 Nov 2024 9:42:33 +0000, Retro Guy wrote:
>
>> On Wed, 20 Nov 2024 21:04:40 +0000, Retro Guy wrote:
>>
>>> On Wed, 20 Nov 2024 20:32:10 +0000, Retro Guy wrote:
>>>
>>>> On Wed, 20 Nov 2024 20:28:46 +0000, Retro Guy wrote:
>>>>
>>>>> On Wed, 20 Nov 2024 19:06:40 +0000, Marco Moock wrote:
>>>>>
>>>>>> On 20.11.2024 um 17:01 Uhr Retro Guy wrote:
>>>>>>
>>>>>>> Both e-s and i2pn2 most likely have almost the same de.* bot articles
>>>>>>> listed.
>>>>>>>
>>>>>>> Maybe I can add more logging like, 'Article not found'?
>>>>>>>
>>>>>>> Please let me know if I'm missing what you're saying, so we can fix
>>>>>>> the problem if there is one.
>>>>>>
>>>>>> Maybe it got deleted after that because I copied all nocems from
>>>>>> processes to the parent and rerun the script.
>>>>>>
>>>>>> Now a new example. The article exists, the NoCeM will be processed
>>>>>> again, but the article won't be deleted.
>>>>>>
>>> <snip>
>>>>>
>>>>> Does the log file ever show 'TRYING' for the message?
>>>>>
>>>>> Could you please provide the MID of the nocem message itself please?
>>>>
>>>> Ok, I found the MID.
>>>>
>>>> Do any articles listed in that nocem get 'TRYING' at all? Or just some
>>>> of them? I'll try it myself here also.
>>>
>>> Please give the attached 'nocem.php' a test. No changes to logging, but
>>> some changes to reading the nocem.
>>
>> Ignore me, ignore that attached nocem.php. I'll have something later
>> today.
>
> I've added quite a bit of logging. This is some, but there is more for
> other things that could occur:
>
> -----
> Nov 21 15:15:02 spoolnews <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not
> found in history database (this is not an error)
> Nov 21 15:15:02 spoolnews TRYING:
> <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> IN: de.rec.sport.misc
> Nov 21 15:15:02 other <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not found
> in: de.rec.sport.misc
> -----
> Nov 21 15:15:02 spoolnews <9425f3f5-0@192-418d-bd4d-a8c5641eb1ad> not
> found in history database (this is not an error)
> Nov 21 15:15:02 spoolnews TRYING:
> <9425f3f5-0@192-418d-bd4d-a8c5641eb1ad> IN: de.soc.misc
> Nov 21 15:15:02 Group not found: de.soc.misc
> -----
>
> I've also cleaned up identifying the mid and group names from the NoCeM,
> allowing for tabs or spaces, and spaces or commas, depending on how each
> admin is producing their scripts.
>
> What we need to do is let it run, and see what is logged, or what part
> of the logging is never reached. I've been letting it run for hours now
> and it seems ok, but can never be sure until it's in production.
>
> I'll be moving it into 'devel' soon. I'll let you know.

This is now in devel on gitlab:
https://gitlab.com/rslight-public/rocksolid-light/-/tree/devel?ref_type=heads

nocem.php and newsportal.php have changes for the described changes.
Since it has been applied to the latest code, it's best to apply as an
upgrade, not just the files as I'm sure newsportal.php most likely has
other changes.

I will continue running this and watch for any issues, which of course
relies on NoCeM being posted. I've done all I can with copying nocem
back into the dir over and over as I tested.

Anyway, it's in devel now.

--
Retro Guy

On 21.11.2024 um 16:16 Uhr Retro Guy wrote:

> I will continue running this and watch for any issues, which of course
> relies on NoCeM being posted.

Is there a reason not to apply the spam articles and try the old NoCeMs
for testing?

If you think it is production-ready, I will install it on my machine.

Currently, the issue is no a big problem, so I will wait some days.

--
kind regards
Marco

Send spam to 1732202174muell@cartoonies.org

On Thu, 21 Nov 2024 16:34:57 +0000, Marco Moock wrote:

> On 21.11.2024 um 16:16 Uhr Retro Guy wrote:
>
>> I will continue running this and watch for any issues, which of course
>> relies on NoCeM being posted.
>
> Is there a reason not to apply the spam articles and try the old NoCeMs
> for testing?

I had no nocem that wasn't already applied, but I just generated some
and tested:

-----
Nov 21 17:00:07 spoolnews Good Issuer and Type for:
i2pn2-nocem@i2pn2.org[2024.11.21.16.55.09]y3bxMC
Nov 21 17:00:07 spoolnews Good signature in:
i2pn2-nocem@i2pn2.org[2024.11.21.16.55.09]y3bxMC
Nov 21 17:00:07 spoolnews
<eb5cf887978d8c226f3a3e562a66f2fc@www.rocksolidbbs.com> appears as
spooled:imported in history. Trying anyway...
Nov 21 17:00:07 spoolnews TRYING:
<eb5cf887978d8c226f3a3e562a66f2fc@www.rocksolidbbs.com> IN:
rocksolid.shared.test
Nov 21 17:00:07 rocksolid DELETING:
<eb5cf887978d8c226f3a3e562a66f2fc@www.rocksolidbbs.com> IN:
rocksolid.shared.test
Nov 21 17:00:07 rocksolid DELETED:
<eb5cf887978d8c226f3a3e562a66f2fc@www.rocksolidbbs.com> IN:
rocksolid.shared.test
Nov 21 17:00:08 spoolnews
<595a9d309f8bf262690d98c36bf39232@www.rocksolidbbs.com> appears as
spooled:imported in history. Trying anyway...
Nov 21 17:00:08 spoolnews TRYING:
<595a9d309f8bf262690d98c36bf39232@www.rocksolidbbs.com> IN:
rocksolid.shared.test
Nov 21 17:00:08 rocksolid DELETING:
<595a9d309f8bf262690d98c36bf39232@www.rocksolidbbs.com> IN:
rocksolid.shared.test
Nov 21 17:00:08 rocksolid DELETED:
<595a9d309f8bf262690d98c36bf39232@www.rocksolidbbs.com> IN:
rocksolid.shared.test
-----

That appears to have worked fine, and shows more of the logging in the
process.

Where it says, 'spooled:imported' or similar is for info only (useful
info for me), so 'Trying anyway' might look odd but it just means it is
continuing the process.

>
> If you think it is production-ready, I will install it on my machine.

I'm running it live now on my sites, feel free to upgrade. If it's not
fixed yet, at least the logging may help in the process.

As always, backup first.

--
Retro Guy

On 21.11.2024 17:08 Uhr Retro Guy wrote:

> That appears to have worked fine, and shows more of the logging in the
> process.

I've now upgraded to the current devel.

root@pi-dach:~/rocksolid-light/Rocksolid_Light# grep '<e150a205-b@abb-4dae-9d27-b65c06ec2682>' /var/spool/rslight/nocem/processed/*
/var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U:<e150a205-b@abb-4dae-9d27-b65c06ec2682> de.soc.wirtschaft
root@pi-dach:~/rocksolid-light/Rocksolid_Light# mv /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U /var/spool/rslight/nocem/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
root@pi-dach:~/rocksolid-light/Rocksolid_Light# systemctl restart rslight
root@pi-dach:~/rocksolid-light/Rocksolid_Light# tail -f /var/spool/rslight/log/nocem.log |grep -i 'found\|dele'
Nov 21 19:13:58 rocksolid <d02aaed0-3@484-492a-8a1c-3b8d12816766> not found in: de.sci.misc
Nov 21 19:13:58 spoolnews <d3a0319b-1@b9b-4792-a0a6-63ff2a2c734f> appears as deleted:nocem in history. Trying anyway...
Nov 21 19:13:58 rocksolid <d3a0319b-1@b9b-4792-a0a6-63ff2a2c734f> not found in: de.soc.wirtschaft
Nov 21 19:13:58 spoolnews <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not found in history database (this is not an error)
Nov 21 19:13:58 rocksolid <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not found in: de.rec.sport.misc
Nov 21 19:13:58 spoolnews <669d497d-d@64b-48c5-9c1f-062a5a6cf63d> not found in history database (this is not an error)

It stops after that, no more lines. File moved to processed.

--
kind regards
Marco

Send spam to 1732205326muell@stinkedores.dorfdsl.de

Marco Moock wrote:

> On 21.11.2024 17:08 Uhr Retro Guy wrote:
>
>> That appears to have worked fine, and shows more of the logging in the
>> process.
>
> I've now upgraded to the current devel.
>
>
> root@pi-dach:~/rocksolid-light/Rocksolid_Light# grep '<e150a205-b@abb-4dae-9d27-b65c06ec2682>' /var/spool/rslight/nocem/processed/*
> /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U:<e150a205-b@abb-4dae-9d27-b65c06ec2682> de.soc.wirtschaft
> root@pi-dach:~/rocksolid-light/Rocksolid_Light# mv /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U /var/spool/rslight/nocem/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
> root@pi-dach:~/rocksolid-light/Rocksolid_Light# systemctl restart rslight
> root@pi-dach:~/rocksolid-light/Rocksolid_Light# tail -f /var/spool/rslight/log/nocem.log |grep -i 'found\|dele'
> Nov 21 19:13:58 rocksolid <d02aaed0-3@484-492a-8a1c-3b8d12816766> not found in: de.sci.misc
> Nov 21 19:13:58 spoolnews <d3a0319b-1@b9b-4792-a0a6-63ff2a2c734f> appears as deleted:nocem in history. Trying anyway...
> Nov 21 19:13:58 rocksolid <d3a0319b-1@b9b-4792-a0a6-63ff2a2c734f> not found in: de.soc.wirtschaft
> Nov 21 19:13:58 spoolnews <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not found in history database (this is not an error)
> Nov 21 19:13:58 rocksolid <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not found in: de.rec.sport.misc
> Nov 21 19:13:58 spoolnews <669d497d-d@64b-48c5-9c1f-062a5a6cf63d> not found in history database (this is not an error)
>
> It stops after that, no more lines. File moved to processed.
>

I assume there are more than three mids listed to remove in the nocem.

Can you send the MID of the nocem itself so I can run the exact same one
please?

--
Retro Guy

On Thu, 21 Nov 2024 20:34:09 +0000, Retro Guy wrote:

> Marco Moock wrote:
>
>> On 21.11.2024 17:08 Uhr Retro Guy wrote:
>>
>>> That appears to have worked fine, and shows more of the logging in the
>>> process.
>>
>> I've now upgraded to the current devel.
>>
>>
>> root@pi-dach:~/rocksolid-light/Rocksolid_Light# grep
>> '<e150a205-b@abb-4dae-9d27-b65c06ec2682>'
>> /var/spool/rslight/nocem/processed/*
>> /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U:<e150a205-b@abb-4dae-9d27-b65c06ec2682>
>> de.soc.wirtschaft
>> root@pi-dach:~/rocksolid-light/Rocksolid_Light# mv
>> /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
>> /var/spool/rslight/nocem/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
>> root@pi-dach:~/rocksolid-light/Rocksolid_Light# systemctl restart
>> rslight
>> root@pi-dach:~/rocksolid-light/Rocksolid_Light# tail -f
>> /var/spool/rslight/log/nocem.log |grep -i 'found\|dele'
>> Nov 21 19:13:58 rocksolid <d02aaed0-3@484-492a-8a1c-3b8d12816766> not
>> found in: de.sci.misc
>> Nov 21 19:13:58 spoolnews <d3a0319b-1@b9b-4792-a0a6-63ff2a2c734f>
>> appears as deleted:nocem in history. Trying anyway...
>> Nov 21 19:13:58 rocksolid <d3a0319b-1@b9b-4792-a0a6-63ff2a2c734f> not
>> found in: de.soc.wirtschaft
>> Nov 21 19:13:58 spoolnews <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not
>> found in history database (this is not an error)
>> Nov 21 19:13:58 rocksolid <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not
>> found in: de.rec.sport.misc
>> Nov 21 19:13:58 spoolnews <669d497d-d@64b-48c5-9c1f-062a5a6cf63d> not
>> found in history database (this is not an error)
>>
>> It stops after that, no more lines. File moved to processed.
>>
>
> I assume there are more than three mids listed to remove in the nocem.
>
> Can you send the MID of the nocem itself so I can run the exact same one
> please?

What do you see in nocem log without the grep (grep -i 'found\|dele')?

I just ran a different e-s nocem and got this:

Nov 21 20:45:02 spoolnews Good Issuer and Type for:
nocem@eternal-september.org[2024.11.18.16.55.08]O0sZYT
Nov 21 20:45:02 spoolnews Good signature in:
nocem@eternal-september.org[2024.11.18.16.55.08]O0sZYT
Nov 21 20:45:02 spoolnews <e1fc05dc-4@ce5-4bdc-a883-b2bf9b2c18c5> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<e1fc05dc-4@ce5-4bdc-a883-b2bf9b2c18c5> IN: de.talk.tagesgeschehen
Nov 21 20:45:02 Group not found: de.talk.tagesgeschehen
Nov 21 20:45:02 spoolnews <31ea0906-3@4ab-4399-a3f9-5466b9052c47> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<31ea0906-3@4ab-4399-a3f9-5466b9052c47> IN: de.sci.announce
Nov 21 20:45:02 Group not found: de.sci.announce
Nov 21 20:45:02 spoolnews <b6765b30-9@262-4132-86cb-094ec6a2d072> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<b6765b30-9@262-4132-86cb-094ec6a2d072> IN: de.rec.sport.misc
Nov 21 20:45:02 other <b6765b30-9@262-4132-86cb-094ec6a2d072> not found
in: de.rec.sport.misc
Nov 21 20:45:02 spoolnews <1b840aa0-d@809-40a9-a086-5a1423ade768> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<1b840aa0-d@809-40a9-a086-5a1423ade768> IN: de.soc.misc
Nov 21 20:45:02 Group not found: de.soc.misc
Nov 21 20:45:02 spoolnews <9be14a23-f@214-4b5e-a6e1-1e56eec827c4> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<9be14a23-f@214-4b5e-a6e1-1e56eec827c4> IN: de.soc.wirtschaft
Nov 21 20:45:02 Group not found: de.soc.wirtschaft
Nov 21 20:45:02 spoolnews <8a0b2cf5-5@348-4dd7-8920-148697b9ed6a> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<8a0b2cf5-5@348-4dd7-8920-148697b9ed6a> IN: de.soc.misc
Nov 21 20:45:02 Group not found: de.soc.misc
Nov 21 20:45:02 spoolnews <66b663d1-3@5e2-455b-9676-b9441a47710b> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<66b663d1-3@5e2-455b-9676-b9441a47710b> IN: de.sci.announce
Nov 21 20:45:02 Group not found: de.sci.announce
Nov 21 20:45:02 spoolnews <8c0d9dea-4@0ad-4501-9adb-56c990d31dd7> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<8c0d9dea-4@0ad-4501-9adb-56c990d31dd7> IN: de.soc.misc
Nov 21 20:45:02 Group not found: de.soc.misc
Nov 21 20:45:02 spoolnews <fc2a2f37-5@b4f-4f8d-bbd2-ff5dfc85745a> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<fc2a2f37-5@b4f-4f8d-bbd2-ff5dfc85745a> IN: de.sci.misc
Nov 21 20:45:02 Group not found: de.sci.misc
Nov 21 20:45:02 spoolnews <a3e1be17-2@6a5-4e58-8659-8ffa71c77e07> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<a3e1be17-2@6a5-4e58-8659-8ffa71c77e07> IN: de.sci.announce
Nov 21 20:45:02 Group not found: de.sci.announce
Nov 21 20:45:02 spoolnews <745dbd4d-8@a0c-4a53-a8d9-7a927fe8c348> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<745dbd4d-8@a0c-4a53-a8d9-7a927fe8c348> IN: de.talk.tagesgeschehen
Nov 21 20:45:02 Group not found: de.talk.tagesgeschehen
Nov 21 20:45:02 spoolnews <265d270e-7@3f3-42a1-bf7b-e19b9867ef15> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<265d270e-7@3f3-42a1-bf7b-e19b9867ef15> IN: de.soc.wirtschaft
Nov 21 20:45:02 Group not found: de.soc.wirtschaft
Nov 21 20:45:02 spoolnews <20d44a97-7@370-428a-b0a5-03ab81e7f919> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<20d44a97-7@370-428a-b0a5-03ab81e7f919> IN: de.talk.tagesgeschehen
Nov 21 20:45:02 Group not found: de.talk.tagesgeschehen
Nov 21 20:45:02 spoolnews <45c97afe-a@9d5-4b9c-8bc6-8f839fb0f199> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<45c97afe-a@9d5-4b9c-8bc6-8f839fb0f199> IN: de.soc.misc
Nov 21 20:45:02 Group not found: de.soc.misc
Nov 21 20:45:02 spoolnews <8efe5e61-d@c52-4c9e-b67b-cd79cb77bdf6> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<8efe5e61-d@c52-4c9e-b67b-cd79cb77bdf6> IN: de.sci.misc
Nov 21 20:45:02 Group not found: de.sci.misc
Nov 21 20:45:02 spoolnews <e150a205-b@abb-4dae-9d27-b65c06ec2682> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<e150a205-b@abb-4dae-9d27-b65c06ec2682> IN: de.soc.wirtschaft
Nov 21 20:45:02 Group not found: de.soc.wirtschaft
Nov 21 20:45:02 spoolnews <46035c0c-8@c7f-4ba5-9295-f682ca63fca4> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<46035c0c-8@c7f-4ba5-9295-f682ca63fca4> IN: de.talk.tagesgeschehen
Nov 21 20:45:02 Group not found: de.talk.tagesgeschehen
Nov 21 20:45:02 spoolnews <1f5424fc-7@559-491a-aafa-e59394da51b6> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<1f5424fc-7@559-491a-aafa-e59394da51b6> IN: de.soc.wirtschaft
Nov 21 20:45:02 Group not found: de.soc.wirtschaft
Nov 21 20:45:02 spoolnews <1e21fd1d-9@40a-4a5d-882d-d743260ea927> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<1e21fd1d-9@40a-4a5d-882d-d743260ea927> IN: de.sci.announce
Nov 21 20:45:02 Group not found: de.sci.announce
Nov 21 20:45:02 spoolnews <45220d4e-c@4cb-4e36-9a59-910b8d147eec> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<45220d4e-c@4cb-4e36-9a59-910b8d147eec> IN: de.rec.sport.misc
Nov 21 20:45:02 other <45220d4e-c@4cb-4e36-9a59-910b8d147eec> not found
in: de.rec.sport.misc
Nov 21 20:45:02 spoolnews <bbdb2996-2@99f-41e3-8a94-76f3e87e4f9c> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<bbdb2996-2@99f-41e3-8a94-76f3e87e4f9c> IN: de.soc.misc
Nov 21 20:45:02 Group not found: de.soc.misc
Nov 21 20:45:02 spoolnews <9425f3f5-0@192-418d-bd4d-a8c5641eb1ad> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<9425f3f5-0@192-418d-bd4d-a8c5641eb1ad> IN: de.soc.misc
Nov 21 20:45:02 Group not found: de.soc.misc
Nov 21 20:45:02 spoolnews <f0d7a124-0@57b-4719-b84e-f19192c0c3e3> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<f0d7a124-0@57b-4719-b84e-f19192c0c3e3> IN: de.rec.sport.misc
Nov 21 20:45:02 other <f0d7a124-0@57b-4719-b84e-f19192c0c3e3> not found
in: de.rec.sport.misc
Nov 21 20:45:02 spoolnews <d02aaed0-3@484-492a-8a1c-3b8d12816766> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<d02aaed0-3@484-492a-8a1c-3b8d12816766> IN: de.sci.misc
Nov 21 20:45:02 Group not found: de.sci.misc
Nov 21 20:45:02 spoolnews <d3a0319b-1@b9b-4792-a0a6-63ff2a2c734f> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<d3a0319b-1@b9b-4792-a0a6-63ff2a2c734f> IN: de.soc.wirtschaft
Nov 21 20:45:02 Group not found: de.soc.wirtschaft
Nov 21 20:45:02 spoolnews <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> IN: de.rec.sport.misc
Nov 21 20:45:02 other <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not found
in: de.rec.sport.misc
Nov 21 20:45:02 spoolnews <669d497d-d@64b-48c5-9c1f-062a5a6cf63d> not
found in history database (this is not an error)
Nov 21 20:45:02 spoolnews TRYING:
<669d497d-d@64b-48c5-9c1f-062a5a6cf63d> IN: de.talk.tagesgeschehen
Nov 21 20:45:02 Group not found: de.talk.tagesgeschehen

On Thu, 21 Nov 2024 20:51:25 +0000, Retro Guy wrote:

> On Thu, 21 Nov 2024 20:34:09 +0000, Retro Guy wrote:
>
>> Marco Moock wrote:
>>
>>> On 21.11.2024 17:08 Uhr Retro Guy wrote:
>>>
>>>> That appears to have worked fine, and shows more of the logging in the
>>>> process.
>>>
>>> I've now upgraded to the current devel.
>>>
>>>
>>> root@pi-dach:~/rocksolid-light/Rocksolid_Light# grep
>>> '<e150a205-b@abb-4dae-9d27-b65c06ec2682>'
>>> /var/spool/rslight/nocem/processed/*
>>> /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U:<e150a205-b@abb-4dae-9d27-b65c06ec2682>
>>> de.soc.wirtschaft
>>> root@pi-dach:~/rocksolid-light/Rocksolid_Light# mv
>>> /var/spool/rslight/nocem/processed/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
>>> /var/spool/rslight/nocem/nocem@eternal-september.org[2024.11.18.16.55.49]9vE37U
>>> root@pi-dach:~/rocksolid-light/Rocksolid_Light# systemctl restart
>>> rslight
>>> root@pi-dach:~/rocksolid-light/Rocksolid_Light# tail -f
>>> /var/spool/rslight/log/nocem.log |grep -i 'found\|dele'
>>> Nov 21 19:13:58 rocksolid <d02aaed0-3@484-492a-8a1c-3b8d12816766> not
>>> found in: de.sci.misc
>>> Nov 21 19:13:58 spoolnews <d3a0319b-1@b9b-4792-a0a6-63ff2a2c734f>
>>> appears as deleted:nocem in history. Trying anyway...
>>> Nov 21 19:13:58 rocksolid <d3a0319b-1@b9b-4792-a0a6-63ff2a2c734f> not
>>> found in: de.soc.wirtschaft
>>> Nov 21 19:13:58 spoolnews <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not
>>> found in history database (this is not an error)
>>> Nov 21 19:13:58 rocksolid <01b9780d-0@301-4f1a-b64d-f8de69a2c3d9> not
>>> found in: de.rec.sport.misc
>>> Nov 21 19:13:58 spoolnews <669d497d-d@64b-48c5-9c1f-062a5a6cf63d> not
>>> found in history database (this is not an error)
>>>
>>> It stops after that, no more lines. File moved to processed.
>>>
>>
>> I assume there are more than three mids listed to remove in the nocem.
>>
>> Can you send the MID of the nocem itself so I can run the exact same one
>> please?
>
> What do you see in nocem log without the grep (grep -i 'found\|dele')?
>
> I just ran a different e-s nocem and got this:
>
<snip>

Also, could you please run nocem.php manually and watch for any errors
(php errors, memory errors, etc.)?

As www user:
cd <webdir>/spoolnews
php /etc/rslight/scripts/nocem.php

--
Retro Guy

On 21.11.2024 20:34 Uhr Retro Guy wrote:

> Can you send the MID of the nocem itself so I can run the exact same
> one please?

Message-ID: <17319486020.Eea5eBcFA.3860024@feeder.eternal-september.org>

--
kind regards
Marco

Send spam to 1732217649muell@stinkedores.dorfdsl.de

On 21.11.2024 20:51 Uhr Retro Guy wrote:

> What do you see in nocem log without the grep (grep -i 'found\|dele')?

As I see the message got deleted yesterday.
I still see some spam, but not covered by the processed messages.

There are older NoCeMs from E-S, but they don't seem to be in the
processed folder. Is there an easy way to let it poll them or is the
easier way that I get them from a newsserver and copy them to the nocem
dir?

--
kind regards
Marco

Send spam to 1732218685muell@stinkedores.dorfdsl.de

On Fri, 22 Nov 2024 15:34:50 +0000, Marco Moock wrote:

> On 21.11.2024 20:51 Uhr Retro Guy wrote:
>
>> What do you see in nocem log without the grep (grep -i 'found\|dele')?
>
> As I see the message got deleted yesterday.
> I still see some spam, but not covered by the processed messages.
>
> There are older NoCeMs from E-S, but they don't seem to be in the
> processed folder. Is there an easy way to let it poll them or is the
> easier way that I get them from a newsserver and copy them to the nocem
> dir?

The processed folder gets cleaned (old files removed) regularly, so they
eventually disappear.

I think the easiest is to get them from a server and drop them into the
folder. I don't think (don't remember) that the filenames are important.
They are named the way they are so as to not overwrite eachother, and
using MID for filename was causing issues.

--
Retro Guy