[QUOTE=henryzz;315845]Going back to the problem case. When the server finishes loading the pairs from admin how does it go through the tests already done to check if there is a prime. I suspect it will be the same code that would be run when changing server type from non-seirp/riesel to seirp/riesel.
It seems like whatever it is checks from the larger tests down(assuming no replacement if smaller found). Would it be possible to switch the order?[/QUOTE]

When a prime is returned by a client, the server will mark all n for that k,b,c for that prime in such a way that no more candidates for higher n are sent out.

When server stats are recomputed every 20 minutes (or however you have the server configured), it selects the min(CandidateName) with a prime for that k,b,c. Obviously that code is wrong as it should choose from the candidate with the smallest decimal length.

I'm working on PRPNet 5.2.0 as I write this. It will include the following changes:
[list][*]Replace clientid with machineid and instanceid which allows for both unique identification of a machine and unique identification of an instance of the PRPNet client on the machine.[*]Modify doublechecker flag to use machineid (was using clientid).[*]Modify Sierpinski/Riesel stats collection to select the smallest n with a prime for a given k/b/c rather than the candidate with the first alphabetical name.[*]Modify code to set HasSierpinskiRieselPrime to 1 if higher n are added to a k/b/c with a found prime.[*]Remove support for clients older than 4.3.[*]Add brieftestlog flag to prpserver.ini so that output to console and testlog is shorter.[*]Fix a bug when client runs wwww helper program as it sometimes doesn't recognize it.[/list]
This should include the changes that have been requested earlier in this thread. If I'm forgetting something or if you have idea for new mods or found other bugs, please let me know. I hope to release the code early next week.

I've posted PRPNet 5.2.0. It has the following changes from 5.1.0:

[code] prpclient: Replace clientid in ini with machineid and instanceid.
prpclient: Fix bug for wwww projects where client couldn't extract program name.
prpserver: Rename column ClientID in database to MachineID. Add InstanceID.
prpserver: Modify doublechecker to use machine id instead of clientid.
prpserver: Fix bug in Sierpinski/Riesel stats to ensure prime listed in table has the smallest n.
prpserver: Modify Sierpinski/Riesel stats updater to set HasSierpinskiRieselPrime flag on new Candidates that are inserted if a prime was already found for the k, b, c.
prpserver: Removed support for clients older than 4.3.
prpserver: Added brieftestlog to prpserver.ini. This flag can be used to shorten the output on consoles.
prpserver: Added estimate of days left to Wieferich/WallSunSun server_stats.html.[/code]

If upgrading a server, please read the history.txt file to find the SQL statements you need to run to do the upgrade.

Clients as old as 4.3 compatible with the 5.2 server. 5.2 clients should be compatible with servers as old as 4.3, but I have not tested that.

I highly recommend that projects upgrade to 5.2.0 at their earliest convenience. I cannot guarantee that future releases of the server will support 4.x clients. If you need assistance in upgrading a server from 4.x to 5.x, feel free to contact me via PM or e-mail. There is little risk to make that upgrade.

You can d/l 5.2.0 from [URL="http://home.roadrunner.com/~mrodenkirch/prpnet_5.2.0.zip"]here[/URL].

I've posted PRPNet 5.2.1. This version fixes a bug with strcpy() where the source and target are within the same string buffer. Apparently this isn't a issue on most OSes, but it is a big no-no on some flavors of Linux.

You can d/l 5.2.1 from [URL="http://home.roadrunner.com/~mrodenkirch/prpnet_5.2.1.zip"]here[/URL].

I've posted PRPNet 5.2.2. In this version I changed onekperclient in the server to onekperinstance and fixed a bug I introduced in 5.2.0. I fixed a logging issue where timezone would show as '???'. I also added a 64-bit build option to the Windows solution.

You can d/l 5.2.2 from [URL="http://home.roadrunner.com/~mrodenkirch/prpnet_5.2.2.zip"]here[/URL].

[QUOTE=rogue;322195]I've posted PRPNet 5.2.2. In this version I changed onekperclient in the server to onekperinstance and fixed a bug I introduced in 5.2.0. I fixed a logging issue where timezone would show as '???'. I also added a 64-bit build option to the Windows solution.

You can d/l 5.2.2 from [URL="http://home.roadrunner.com/~mrodenkirch/prpnet_5.2.2.zip"]here[/URL].[/QUOTE]

...any hopes to have a check at DoubleMersennes?... :smile:

Luigi

[QUOTE=ET_;322219]...any hopes to have a check at DoubleMersennes?... :smile:
Luigi[/QUOTE]

It's not clear to me what you are looking for. Are you referring to me fixing gmp-fermat and the double-mersenne logic it has? If so, then I don't know when I'll get to it. If I'm lucky, next week, but I can't make any promises. If you are referring to modify PRPNet to support a search, I've never thought about it.

[QUOTE=rogue;322242]It's not clear to me what you are looking for. Are you referring to me fixing gmp-fermat and the double-mersenne logic it has? If so, then I don't know when I'll get to it. If I'm lucky, next week, but I can't make any promises. If you are referring to modify PRPNet to support a search, I've never thought about it.[/QUOTE]

I hope you will be lucky... :smile:

Luigi

Yesterday I updated from version 4.3.7 to version 5.2.2. (Windows 7 x64)
But the new version seems to be more unstable than the old one :(
I just came home and saw, the the prpserver.exe crashed (Windows message: Stopped working, application needs to be closed).
In the log file there is nothing.. last message was a correctly accepted tests.

The only thing I noticed is, I got many of the following messages on different clients, although the server was running:
[CODE][2013-01-13 01:56:22 MZ] s19: Returning work to server localhost at port 7119
[2013-01-13 01:56:32 MZ] s19: nothing was received on socket after 10 seconds
[2013-01-13 01:56:34 MZ] s19: nothing was received on socket after 2 seconds
[2013-01-13 01:56:34 MZ] Could not connect to any servers and no work is pending. Pausing 10 minutes
[2013-01-13 02:06:35 MZ] s19: Returning work to server localhost at port 7119
[2013-01-13 02:06:45 MZ] s19: nothing was received on socket after 10 seconds
[2013-01-13 02:06:47 MZ] s19: nothing was received on socket after 2 seconds
[2013-01-13 02:06:47 MZ] Could not connect to any servers and no work is pending. Pausing 10 minutes
[2013-01-13 02:16:48 MZ] s19: Returning work to server localhost at port 7119[/CODE]

Could it have something to do with the amount of tests in the database?
I am testing s19, there are about 2M tests in the mysql database.
Using MySQL server version 5.1.43.

[QUOTE=Xentar;324557]Yesterday I updated from version 4.3.7 to version 5.2.2. (Windows 7 x64)
But the new version seems to be more unstable than the old one :(
I just came home and saw, the the prpserver.exe crashed (Windows message: Stopped working, application needs to be closed).
In the log file there is nothing.. last message was a correctly accepted tests.

The only thing I noticed is, I got many of the following messages on different clients, although the server was running:
[CODE][2013-01-13 01:56:22 MZ] s19: Returning work to server localhost at port 7119
[2013-01-13 01:56:32 MZ] s19: nothing was received on socket after 10 seconds
[2013-01-13 01:56:34 MZ] s19: nothing was received on socket after 2 seconds
[2013-01-13 01:56:34 MZ] Could not connect to any servers and no work is pending. Pausing 10 minutes
[2013-01-13 02:06:35 MZ] s19: Returning work to server localhost at port 7119
[2013-01-13 02:06:45 MZ] s19: nothing was received on socket after 10 seconds
[2013-01-13 02:06:47 MZ] s19: nothing was received on socket after 2 seconds
[2013-01-13 02:06:47 MZ] Could not connect to any servers and no work is pending. Pausing 10 minutes
[2013-01-13 02:16:48 MZ] s19: Returning work to server localhost at port 7119[/CODE]

Could it have something to do with the amount of tests in the database?
I am testing s19, there are about 2M tests in the mysql database.
Using MySQL server version 5.1.43.[/QUOTE]

There are two possibilities. First, I know there is a memory leak in the Windows MySQL ODBC driver. I've reported it, but it has not been fixed. It is possible that this is causing the problem. When a 32-bit build of the server hits 2 GB it will crash. When that happens you will see various MySQL errors on the prpserver console. This is a addressed by shutting down and restarting the server every few days. Second, I have seen other intermittent crashes in the server, but they occur rarely and of course never occur with debug builds. I probably need to do a "clean" then a "build", but I can't claim that it is a compile or linkage issue.

The problem appeared after updating the prpserver only. I didnt touch the MySQL server (or ODBC driver). The old version ran for months without restarting. Maybe I just should update them? The newest MySQL version is 5.5.* :smile:

A few minutes ago, I saw this lines in the log:
[CODE][2013-01-13 16:32:03 MZ] 524: ODBC Information: SQL_ERROR: [MySQL][ODBC 5.1 Driver][mysqld-5.1.43-community]Lock wait timeout exceeded; try restarting transaction
[2013-01-13 16:32:03 MZ] 524: ODBC Information: SQL Statement: update Candidate set HasPendingTest = 1 where CandidateName = 1446*19^100146+1 and HasPendingTest = 0
[/CODE]

I will try debuglevel=1 and see if it crashes again.