PRPnet server bugs and barfing problem

[Lennart]

Originally Posted by mdettweiler

Hey, looky! I just noticed something! G3000 has now *really* dried (not just nominally). It now shows just one insanely huge k with 999999999 as the min-n on the server_stats.html page, which is how dried PRPnet servers are "supposed" to react. (It's just a cosmetic error, though rest assured, yes, we're working on that too. )

This means, of course, that if there's any data to be had on the client side of things, it's already sitting in one of Lennart's debug.log's and waiting for us to collect.

It is not easy for me to find that I have to check ~80 logs on 20 Computer

Do you see anything strange in server log that can nail it down to one computer

Lennart

[mdettweiler]

Originally Posted by Lennart

It is not easy for me to find that I have to check ~80 logs on 20 Computer

Do you see anything strange in server log that can nail it down to one computer

Lennart

Okay, the last time the server's barfed was around the time of these log entries:

[2009-08-03 21:14:45 GMT] 172257*6^148184+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _31 Program:   Residue:   
[2009-08-03 21:15:18 GMT] 168610*6^148352+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _206 Program:   Residue:   
[2009-08-03 21:15:51 GMT] 87800*6^147867+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _162 Program:   Residue:   
[2009-08-03 21:16:14 GMT] 124125*6^148166+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _127 Program: pfgw  Residue: 59589D7D3BD68AF3  
[2009-08-03 21:16:28 GMT] 123285*6^148356+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _206 Program:   Residue:   
[2009-08-03 21:17:01 GMT] 108527*6^148607+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _71 Program:   Residue:   
[2009-08-03 21:17:34 GMT] 33706*6^147870+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _162 Program:   Residue:   
[2009-08-03 21:18:07 GMT] 59506*6^148227+1:  Email: gbarnes017@gmail.com  User: gd_barnes  Client: humpford Program:   Residue:   
[2009-08-03 21:18:40 GMT] 124125*6^148166+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _127 Program:   Residue:   
[2009-08-03 21:19:13 GMT] 108527*6^148607+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _71 Program:   Residue:   
[2009-08-03 21:19:46 GMT] 124221*6^148285+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _31 Program:   Residue:   
[2009-08-03 21:20:19 GMT] 13215*6^148275+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _127 Program:   Residue:

Any of those with blank residuals above should do the trick.

[Lennart]

Originally Posted by mdettweiler

Okay, the last time the server's barfed was around the time of these log entries:

[2009-08-03 21:14:45 GMT] 172257*6^148184+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _31 Program:   Residue:   
[2009-08-03 21:15:18 GMT] 168610*6^148352+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _206 Program:   Residue:   
[2009-08-03 21:15:51 GMT] 87800*6^147867+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _162 Program:   Residue:   
[2009-08-03 21:16:14 GMT] 124125*6^148166+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _127 Program: pfgw  Residue: 59589D7D3BD68AF3  
[2009-08-03 21:16:28 GMT] 123285*6^148356+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _206 Program:   Residue:   
[2009-08-03 21:17:01 GMT] 108527*6^148607+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _71 Program:   Residue:   
[2009-08-03 21:17:34 GMT] 33706*6^147870+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _162 Program:   Residue:   
[2009-08-03 21:18:07 GMT] 59506*6^148227+1:  Email: gbarnes017@gmail.com  User: gd_barnes  Client: humpford Program:   Residue:   
[2009-08-03 21:18:40 GMT] 124125*6^148166+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _127 Program:   Residue:   
[2009-08-03 21:19:13 GMT] 108527*6^148607+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _71 Program:   Residue:   
[2009-08-03 21:19:46 GMT] 124221*6^148285+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _31 Program:   Residue:   
[2009-08-03 21:20:19 GMT] 13215*6^148275+1:  Email: sm5ymt@pekhult.se  User: sm5ymt  Client: _127 Program:   Residue:

Any of those with blank residuals above should do the trick.

I did start debug 2009-08-03 22:00 UTC on almost all .

Have you anything after that time.

Lennart

[mdettweiler]

Originally Posted by Lennart

I did start debug 2009-08-03 22:00 UTC on almost all .

Have you anything after that time.

Lennart

Unfortunately, no. And since the server's already been dried...hmm...

Anyone up for another run-through of 140K-150K?

[mdettweiler]

Okay, I've loaded 140K-150K into the server once again. Hopefully this time we'll get all the testing data we need and won't have to re-run this range any more.

[gd_barnes]

Rerun it as many times as you need. With Lennart's and my machines on there, it goes very quickly and if there is any anomoly with rejected or deleted results, we can try to isolate every one of them.

I'm not clear, was the patch that Mark referred to put in for this run? If not, I'm assuming we'll have some of the same issues and of course we'll have to run it again with the patch (and/or additional patches) in place.


Gary

[gd_barnes]

Oopsie...the one summary page is showing 35 k's remaining. I then went to the page with all of the k's showing "min n" and "max n" for each and it also shows 35 remaining.

With a run beginning at n=140K, there should only be 30 k's remaining.


Gary

[mdettweiler]

Originally Posted by gd_barnes

Oopsie...the one summary page is showing 35 k's remaining. I then went to the page with all of the k's showing "min n" and "max n" for each and it also shows 35 remaining.

With a run beginning at n=140K, there should only be 30 k's remaining.


Gary

Oops...sorry. This time around I forgot to remove all the k's that had been primed in n=100K-140K. Oh well, it's just a few more k's, and since the entire range is being rerun anyway, it will just give us that much more test data.

Edit: And yes, we're still NOT using the patched server version, so that we can catch the logs on both the server and client from when it barfs.

[Lennart]

Here is some files.

Lennart

[rogue]

Originally Posted by Lennart

Here is some files.

Lennart

These are large files, can you narrow down the time frame for the issue? Can you verify that the issue is in one of these files?

[mdettweiler]

Originally Posted by rogue

These are large files, can you narrow down the time frame for the issue? Can you verify that the issue is in one of these files?

Based on the server logs, it seems there was a lot of barfing between [2009-08-06 15:47:02 GMT] and [2009-08-06 16:50:34 GMT].