| Author |
Message |
|---|
|
|
|
I have just posted new packages for the recently released PRPNet 5.2.2. See this post for full instructions.
Please note that there are some significant changes in 5.2, including replacing clientid with machineid and instanceid, and corresponding changes to the *-update-prpclient-ini scripts. It is recommended to do a clean install from the new packages rather than copying files into an existing install directory.
If you run into any problems, please post here and I'll do my best to look at it ASAP (between turkey and mulled wine)!
Cheers
- Iain
____________
Twitter: IainBethune
Proud member of team "Aggie The Pew". Go Aggie!
3073428256125*2^1290000-1 is Prime! |
|
|
 Crun-chi Volunteer tester
Send message
Joined: 25 Nov 09
Posts: 3250
ID: 50683
Credit: 152,646,050
RAC: 10,054
                         
|
|
Install on two win machines, without any problem, works perfect!
Merry Christmas Iain!
____________
92*10^1585996-1 NEAR-REPDIGIT PRIME :) :) :)
4 * 650^498101-1 CRUS PRIME
2022202116^131072+1 GENERALIZED FERMAT
Proud member of team Aggie The Pew. Go Aggie! |
|
|
HonzaVolunteer moderator
Volunteer tester
Project scientist
Send message
Joined: 15 Aug 05
Posts: 1963
ID: 352
Credit: 6,420,431,564
RAC: 2,590,392
                                     
|
|
I think more participants will welcome single package for Windows that includes both CPU and GPU with x86/x64 in one.
I'm running Wiferich on my home machine and so far so good...
____________
My stats |
|
|
|
|
|
Minor error in the 64bit linux install.
File wwwwcl permissions are initially set to 655 should be 755 (same as wwww).
Starting the client(s) from the start script results in the immediate exit of the client(s).
Starting the client directly results in the error "Could not determine version of wwww being used. File empty."
Starting wwwwcl directly results in the error "bash: ./wwwwcl: Permission denied"
Modifying the permissions eliminates the problem.
Other than that 5.2.2 installs/updates/runs as expected!
Tail-Wags-O-Appreciation to all who brought us V 5.2.2!!!
____________
There's someone in our head but it's not us. |
|
|
|
|
|
Is the "client.lock" file new with this version? I assume so.
Just an FYI, if you have a power outage you will need to delete the client.lock file before the prpclient will fire back up. Correct me if I'm off base on this.
Power outage is not fun when it's 18F outside.
____________
|
|
|
rogueVolunteer developer
Send message
Joined: 8 Sep 07
Posts: 1259
ID: 12001
Credit: 18,565,548
RAC: 0
 
|
Is the "client.lock" file new with this version? I assume so.
Just an FYI, if you have a power outage you will need to delete the client.lock file before the prpclient will fire back up. Correct me if I'm off base on this.
That is correct. The client.lock file is there to prevent you from accidentally starting two instances of the client from the same directory. I had someone do that and they created a number of "odd" problems with the client. |
|
|
|
|
File wwwwcl permissions are initially set to 655 should be 755 (same as wwww).
Fixed! My little Christmas pressie to you :)
____________
Twitter: IainBethune
Proud member of team "Aggie The Pew". Go Aggie!
3073428256125*2^1290000-1 is Prime! |
|
|
|
|
|
I went to the site to download the new client and I believe the server is down or not responding. 5:30 PM CDT
http://uwin.mine.nu/PRPNet/ |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 14045
ID: 53948
Credit: 482,681,090
RAC: 578,366
                       
|
I went to the site to download the new client and I believe the server is down or not responding. 5:30 PM CDT
http://uwin.mine.nu/PRPNet/
Yes, uwin is (or was) having problems. No ETA on when it will be up.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Minor error in the wwwwcl & Windows.
When the client was interrupted by Ctrl+C or Alt+Break,
next start of client results the exit after breaked task completion with message in prpclient.log:
[2013-01-04 20:25:11 Ф(] : Could not parse stats line in [wwww.log]
wwww.log contains the string:
Range not completed. Primes tested 268280076. Checksum 0000000000000000. Time 89.490118 secondsPrimes tested 268280076. Checksum 0000000000000000. Time 99.138174 seconds
Deleting wwww.log and client restart solves the problem.
____________
|
|
|
rogueVolunteer developer
Send message
Joined: 8 Sep 07
Posts: 1259
ID: 12001
Credit: 18,565,548
RAC: 0
|
Minor error in the wwwwcl & Windows.
When the client was interrupted by Ctrl+C or Alt+Break,
next start of client results the exit after breaked task completion with message in prpclient.log:
[2013-01-04 20:25:11 Ф(] : Could not parse stats line in [wwww.log]
wwww.log contains the string:
Range not completed. Primes tested 268280076. Checksum 0000000000000000. Time 89.490118 secondsPrimes tested 268280076. Checksum 0000000000000000. Time 99.138174 seconds
Deleting wwww.log and client restart solves the problem.
I'm aware of the problem. I haven't had time to fix it yet. |
|
|
|
|
|
rogue, what do you advice to break the clients?
Ctrl+C leads to you know what...
Closing console between result return and getting new leads to loss of tasks (I see how grows the list of my pending tasks)...
stopoption=6 did not solve my problem too...
____________
|
|
|
|
|
rogue, what do you advice to break the clients?
Ctrl+C leads to you know what...
Closing console between result return and getting new leads to loss of tasks (I see how grows the list of my pending tasks)...
stopoption=6 did not solve my problem too...
I use the stopoption=6 and it works fine in windows. You just need to wait for all the work in your queue before it shuts down properly. So if your grabbing 25 it could take a while for the stopoption to stop it. |
|
|
|
|
rogue, what do you advice to break the clients?
Ctrl+C leads to you know what...
Closing console between result return and getting new leads to loss of tasks (I see how grows the list of my pending tasks)...
stopoption=6 did not solve my problem too...
I use the stopoption=6 and it works fine in windows. You just need to wait for all the work in your queue before it shuts down properly. So if your grabbing 25 it could take a while for the stopoption to stop it.
Yes, they finish and shut down properly, but wwwwcl writes lo log
Range not completed. Primes tested 268280076. Checksum 0000000000000000. Time 89.490118 seconds
and the next time client exists with
Could not parse stats line in [wwww.log]
____________
|
|
|
rogueVolunteer developer
Send message
Joined: 8 Sep 07
Posts: 1259
ID: 12001
Credit: 18,565,548
RAC: 0
|
rogue, what do you advice to break the clients?
Ctrl+C leads to you know what...
Closing console between result return and getting new leads to loss of tasks (I see how grows the list of my pending tasks)...
stopoption=6 did not solve my problem too...
I use the stopoption=6 and it works fine in windows. You just need to wait for all the work in your queue before it shuts down properly. So if your grabbing 25 it could take a while for the stopoption to stop it.
Yes, they finish and shut down properly, but wwwwcl writes lo log
Range not completed. Primes tested 268280076. Checksum 0000000000000000. Time 89.490118 seconds
and the next time client exists with
Could not parse stats line in [wwww.log]
One of the problems is that wwww and wwwwcl need to delete wwww.log when they start up. |
|
|
Scott BrownVolunteer moderator
Project administrator
Volunteer tester
Project scientist
Send message
Joined: 17 Oct 05
Posts: 2420
ID: 1178
Credit: 20,183,747,281
RAC: 23,151,563
                                            
|
|
Interesting quirk on a 64-bit Windows Vista system. Using the update feature while running (in my case 8 instances of) the client does not change the behavior of those clients, though it used to update while running under previous PRPnet versions. Running updates while client is closed and then restarting works as expected. Is this expected behavior of the new client?
|
|
|
|
|
rogue, what do you advice to break the clients?
Ctrl+C leads to you know what...
Closing console between result return and getting new leads to loss of tasks (I see how grows the list of my pending tasks)...
stopoption=6 did not solve my problem too...
stopasapoption=6 works fine (finishes all, reports them and closes)
____________
676754^262144+1 is prime |
|
|
|
|
Interesting quirk on a 64-bit Windows Vista system. Using the update feature while running (in my case 8 instances of) the client does not change the behavior of those clients, though it used to update while running under previous PRPnet versions. Running updates while client is closed and then restarting works as expected. Is this expected behavior of the new client?
Your talking about the update ini batch file right? I've noticed this too but not every time I run it. Sometimes it does changes the ini file and at times it does not. I thought it was something I was doing wrong.
Right click and select open instead of double clicking on it. I might be off on this but I thought it worked every time I did that. Or it might have been "run as administrator" I forget and I'm at work and cant test that.
____________
|
|
|
