Retro Guy wrote:

> Retro Guy wrote:

>> Interesting... I may have found a bug.

>> Checking it out...

> Found a problem specific to r.s.programming, which is weird. Making a minor change to spoolnews.php to see what's going on.

Added some logging before and after pulling a message. Let's see...

--
Posted on def2
z5bqfv5v75kxy7pj.onion

Retro Guy wrote:

> Retro Guy wrote:

>> Retro Guy wrote:

>>> Interesting... I may have found a bug.

>>> Checking it out...

>> Found a problem specific to r.s.programming, which is weird. Making a minor change to spoolnews.php to see what's going on.

> Added some logging before and after pulling a message. Let's see...

Jun 02 00:29:26 rocksolid Trying to get: 192.xxx rocksolid.nodes.announce:224
Jun 02 00:29:28 rocksolid Wrote to spool: 192.xxx rocksolid.nodes.announce:224

--
Posted on def2
z5bqfv5v75kxy7pj.onion

Retro Guy wrote:

> Retro Guy wrote:

>> Retro Guy wrote:

>>> Retro Guy wrote:

>>>> Interesting... I may have found a bug.

>>>> Checking it out...

>>> Found a problem specific to r.s.programming, which is weird. Making a minor change to spoolnews.php to see what's going on.

>> Added some logging before and after pulling a message. Let's see...

> Jun 02 00:29:26 rocksolid Trying to get: 192.xxx rocksolid.nodes.announce:224
> Jun 02 00:29:28 rocksolid Wrote to spool: 192.xxx rocksolid.nodes.announce:224

Added one more line (Unexpected response to ARTICLE command: ...)

--
Posted on: Rocksolid Light
www.novabbs.com

Retro Guy wrote:

> Retro Guy wrote:

>> Retro Guy wrote:

>>> Retro Guy wrote:

>>>> Retro Guy wrote:

>>>>> Interesting... I may have found a bug.

>>>>> Checking it out...

>>>> Found a problem specific to r.s.programming, which is weird. Making a minor change to spoolnews.php to see what's going on.

>>> Added some logging before and after pulling a message. Let's see...

>> Jun 02 00:29:26 rocksolid Trying to get: 192.xxx rocksolid.nodes.announce:224
>> Jun 02 00:29:28 rocksolid Wrote to spool: 192.xxx rocksolid.nodes.announce:224

> Added one more line (Unexpected response to ARTICLE command: ...)

The modified spoolnews.php now checks for problems in maintaing last article retrieved in config, plus adds above logging.

Could you please pull spoolnews.php.txt from the download directory and give it a try if you get a chance? Obviously, remove '.txt'.

Thanks!

Retro Guy

--
Posted on: Rocksolid Light
www.novabbs.com

Retro Guy wrote:

> Could you please pull spoolnews.php.txt from the download directory and give it a try if you get a chance? Obviously, remove '.txt'.

Hold off on that. Digging for bugs found me another bug :)

Working on it...

Retro Guy

--
Posted on: Rocksolid Light
www.novabbs.com

Retro Guy wrote:

> Retro Guy wrote:

>> Could you please pull spoolnews.php.txt from the download directory and give it a try if you get a chance? Obviously, remove '.txt'.

> Hold off on that. Digging for bugs found me another bug :)

> Working on it...

Ok, the script is back on the download site. If you install it, please back up your spoolnews.php first. This is really just a messy test.

Retro Guy

--
Posted on: Rocksolid Light
www.novabbs.com

rocksolid.nodes:336
rocksolid.nodes.help:75
rocksolid.nodes.announce:229
rocksolid.shared.encryption:40
rocksolid.shared.entertainment:91
rocksolid.shared.freenet:15
rocksolid.shared.general:166
rocksolid.shared.hacking:159
rocksolid.shared.helpdesk:101
rocksolid.shared.i2p:199
rocksolid.shared.linux:69
rocksolid.shared.news:172
rocksolid.shared.offtopic:199
rocksolid.programming:180
rocksolid.shared.rocksolid:259
rocksolid.shared.security:126
rocksolid.social:159
rocksolid.shared.test:1101
rocksolid.shared.tor:112

That seems a little off vs the expectations.

Will try the new script soon.

cheers

trw

--
Posted on def2.i2p

Anonymous wrote:

> rocksolid.nodes:336
> rocksolid.nodes.help:75
> rocksolid.nodes.announce:229
> rocksolid.shared.encryption:40
> rocksolid.shared.entertainment:91
> rocksolid.shared.freenet:15
> rocksolid.shared.general:166
> rocksolid.shared.hacking:159
> rocksolid.shared.helpdesk:101
> rocksolid.shared.i2p:199
> rocksolid.shared.linux:69
> rocksolid.shared.news:172
> rocksolid.shared.offtopic:199
> rocksolid.programming:180
> rocksolid.shared.rocksolid:259
> rocksolid.shared.security:126
> rocksolid.social:159
> rocksolid.shared.test:1101
> rocksolid.shared.tor:112

> That seems a little off vs the expectations.

> Will try the new script soon.

Yes, it is off. I found the same problem on my test server. But here is the file now:

rocksolid.nodes:336
rocksolid.nodes.help:75
rocksolid.nodes.announce:230
rocksolid.shared.encryption:40
rocksolid.shared.entertainment:91
rocksolid.shared.freenet:15
rocksolid.shared.general:166
rocksolid.shared.hacking:159
rocksolid.shared.helpdesk:101
rocksolid.shared.i2p:199
rocksolid.shared.linux:69
rocksolid.shared.news:172
rocksolid.shared.offtopic:180
rocksolid.programming:64
rocksolid.shared.rocksolid:259
rocksolid.shared.security:126
rocksolid.social:11
rocksolid.shared.test:1101
rocksolid.shared.tor:112

Notice how both programming and social are incorrect in your file. I've made a temporary mod to see if I can correct this problem. If it does, then I will clean up the mod, test again, and send it to you.

Note: You do NOT need to restart the nntp server to replace spoolnews.php

Retro Guy

--
Posted on: Rocksolid Light
www.novabbs.com

is on my server (def2).

--
Posted on def2.i2p

Anonymous wrote:

> is on my server (def2).

Great! After it runs once, take a look at the group file again and it should have correct numbers.

--
Posted on: Rocksolid Light
www.novabbs.com

rocksolid.nodes:336
rocksolid.nodes.help:75
rocksolid.nodes.announce:233
rocksolid.shared.encryption:40
rocksolid.shared.entertainment:91
rocksolid.shared.freenet:15
rocksolid.shared.general:166
rocksolid.shared.hacking:159
rocksolid.shared.helpdesk:101
rocksolid.shared.i2p:199
rocksolid.shared.linux:69
rocksolid.shared.news:172
rocksolid.shared.offtopic:180
rocksolid.programming:64
rocksolid.shared.rocksolid:259
rocksolid.shared.security:126
rocksolid.social:11
rocksolid.shared.test:1101
rocksolid.shared.tor:112

--
Posted on def2.i2p

were different for different groups ? what was special about social ?

--
Posted on def2.i2p

Anonymous wrote:

> were different for different groups ? what was special about social ?

In 0.6.5c there was a bug that allowed the watermark for a group to keep climbing if there was any error, or whatever. I'm guessing programming and social had something in a message causing the loop to continued past a message, but then kept incrementing the counter (which was the bug).

I fixed this bug in 0.6.5d, but the watermarks would still be in the file after an upgrade. Loading backward 20 messages was fine, but if the watermark was more than 20 ahead, it had no effect.

This version of spoolnews.php checks the upstream server each run, and makes sure the watermark does not exceed the highest post on the server. If it does, it corrects it.

I've added some logging to hopefully show if a message has an error, so if one doesn't show up, I'm hoping the error will be logged. This info will help me see why a message might fail.

It's possible that if you use the semaphore file again, you may pull the missing message in social. From a previous post:
"Then, in /var/spool/rslight, please create a file named 'rocksolid.reload' and give this file permissions that allow the web server user to delete it. This is a semaphore file to tell spoolnews to go back (currently 20) articles and retry to pull them."

Of course if the message-id of the message is in the overview file, it won't download it again. Since I don't know if the message is a problem, I don't know what will happen. </end useless info :)>

Retro Guy

--
Posted on: Rocksolid Light
www.novabbs.com

> don't know what will happen.

to reget the messages fixed many threads, including social.

--
Posted on def2.i2p

I'm wondereing if vichan is running message_read on an article before rslight tries to display the article, then rslight is just trying to pull it from the spool because it already exists (rslight does that for speed purposes).

Then rslight is never creating the correct cache files and ends up getting lost on those articles (the cache files are incorrect).

If that's the case, we can fix it, but I'd like to see if message_read being run separately from rslight running it is causing a problem.

Retro Guy

--
Posted on: Rocksolid Light
www.novabbs.com