[QUOTE=Bundu;116148]Answer to post #97: Were you trying to perform an LL Test on the new server? If so you should probably note that you are choosing the wrong kind of work for the beta test....

4) Run version 25.5. Follow the link in the dialog box to create a userid. [B]Choose a work preference of either "Trial factoring to low limits" or "ECM on small Mersenne numbers".[/B]

Answer to post #98: If you check through the posts the "anonymous bug" seems to have popped up a few times for various users and a number of different fixes have been tried. perhaps try a couple and let us know how you get on?

Also... the "PHP Fatal error: Maximum execution time of 60 seconds exceeded in.." messages do crop up (pretty much on the hour every hour). I've let scott kurowski know by email as directed in post #76. I also notice that the timestamp you posted is almost on the hour and since the server updates at that time you're probably going to have to wait a few minutes before it picks up communication again[/QUOTE]

To #97 - yes I forgot to change to ECM in the first time, but I did so approx. half an hour later.

Anonymous bug: I think I will have access to this computer again at the end of next week, then I will try the workarounds.

I got another comm bug in mprime on Linux 32-bit. Last night my copy of mprime just stopped communicating and kept saying no work to do. There was nothing irregular in the prime.log except for a PHP error when the last exponent was retrieved and it's completion date communicated.

I interrupted (Ctrl-C) the process and ran mprime -c but to no avail. Then I did mprime -m and it immediately started communicating with the server without my having chosen any option. This is definitely not expected behaviour.

libssl.so.6 missing
 

Hello,

I'm trying to install mprime255a-linux64.tar.gz on a fresh Ubuntu 64bit install. When I kick off mprime I get:

./mprime: error while loading shared libraries: libssl.so.6: cannot open shared object file: No such file or directory

When I check the ubuntu repos I can't see to find it. Any ideas where I can get this?

Thanks,
Rich

[quote=RichJacot;116222]Hello,

I'm trying to install mprime255a-linux64.tar.gz on a fresh Ubuntu 64bit install. When I kick off mprime I get:

./mprime: error while loading shared libraries: libssl.so.6: cannot open shared object file: No such file or directory

When I check the ubuntu repos I can't see to find it. Any ideas where I can get this?

Thanks,
Rich[/quote]


I got it. I needed to:
sudo ln -s libssl.so.0.9.8 libssl.so.6
sudo ln -s libcrypto.so.0.9.8 libcrypto.so.6

and its now working. Sorry!

[QUOTE=garo;116192]I got another comm bug in mprime on Linux 32-bit. Last night my copy of mprime just stopped communicating and kept saying no work to do. There was nothing irregular in the prime.log except for a PHP error when the last exponent was retrieved and it's completion date communicated.

I interrupted (Ctrl-C) the process and ran mprime -c but to no avail. Then I did mprime -m and it immediately started communicating with the server without my having chosen any option. This is definitely not expected behaviour.[/QUOTE]

I wonder what time? I only ask because my 3 instances did the same on vista last night:

[CODE][Oct 12 01:55] <= Recv header: X-Powered-By: PHP/5.2.0
[Oct 12 01:55] <= Recv header: Content-type: text/html
[Oct 12 01:55] <= Recv data: pnErrorResult=0
[Oct 12 01:55] pnErrorDetail=SUCCESS
[Oct 12 01:55] ==END==
[Oct 12 01:55]
[Oct 12 01:55] == Info: Closing connection #0
[Oct 12 01:55] RESPONSE:
[Oct 12 01:55] pnErrorResult=0
[Oct 12 01:55] pnErrorDetail=SUCCESS
[Oct 12 01:55] ==END==
[Oct 12 01:55]
[Oct 12 01:55] Getting assignment from server
[Oct 12 01:55] URL: http://v5.mersenne.org/v5server/?v=0.95&px=GIMPS&t=ga&g=7b710aa7fa646abf34e28576ac88969b&c=0&ss=31163&sh=FF12BDE500FF6AEA44E33B66DAC6F668
[Oct 12 01:55] == Info: About to connect() to v5.mersenne.org port 80
[Oct 12 01:55] == Info: Trying 70.167.121.136...
[Oct 12 01:55] == Info: connected
[Oct 12 01:55] == Info: Connected to v5.mersenne.org (70.167.121.136) port 80
[Oct 12 01:55] => Send header: GET /v5server/?v=0.95&px=GIMPS&t=ga&g=7b710aa7fa646abf34e28576ac88969b&c=0&ss=31163&sh=FF12BDE500FF6AEA44E33B66DAC6F668 HTTP/1.1
[Oct 12 01:55] Host: v5.mersenne.org
[Oct 12 01:55] Accept: */*
[Oct 12 01:55]
[Oct 12 01:55] <= Recv header: HTTP/1.1 200 OK
[Oct 12 01:55] <= Recv header: Server: Microsoft-IIS/5.0
[Oct 12 01:55] <= Recv header: Date: Fri, 12 Oct 2007 00:56:52 GMT
[Oct 12 01:55] <= Recv header: X-Powered-By: ASP.NET
[Oct 12 01:55] <= Recv header: MicrosoftOfficeWebServer: 5.0_Pub
[Oct 12 01:55] <= Recv header: Connection: close
[Oct 12 01:55] <= Recv header: X-Powered-By: PHP/5.2.0
[Oct 12 01:55] <= Recv header: Content-type: text/html
[Oct 12 01:55] <= Recv data: pnErrorResult=0
[Oct 12 01:55] pnErrorDetail=Server assigned trial factoring work
[Oct 12 01:55] g=7b710aa7fa646abf34e28576ac88969b
[Oct 12 01:55] k=9E36825D7791379EC6A3CCA895AF7495
[Oct 12 01:55] A=1
[Oct 12 01:55] b=2
[Oct 12 01:55] n=130359389
[Oct 12 01:55] c=-1
[Oct 12 01:55] w=2
[Oct 12 01:55] sf=0
[Oct 12 01:55] ef=57
[Oct 12 01:55] ==END==
[Oct 12 01:55]
[Oct 12 01:55] == Info: Closing connection #0
[Oct 12 01:55] RESPONSE:
[Oct 12 01:55] pnErrorResult=0
[Oct 12 01:55] pnErrorDetail=Server assigned trial factoring work
[Oct 12 01:55] g=7b710aa7fa646abf34e28576ac88969b
[Oct 12 01:55] k=9E36825D7791379EC6A3CCA895AF7495
[Oct 12 01:55] A=1
[Oct 12 01:55] b=2
[Oct 12 01:55] n=130359389
[Oct 12 01:55] c=-1
[Oct 12 01:55] w=2
[Oct 12 01:55] sf=0
[Oct 12 01:55] ef=57
[Oct 12 01:55] ==END==
[Oct 12 01:55]
[Oct 12 01:55] PrimeNet success code with additional info:
[Oct 12 01:55] Server assigned trial factoring work
[Oct 12 01:55] Got assignment 9E36825D7791379EC6A3CCA895AF7495: Trial factor M130359389
[Oct 12 01:55] Sending expected completion date for M130359389: Oct 12 2007
[Oct 12 01:55] URL: http://v5.mersenne.org/v5server/?v=0.95&px=GIMPS&t=ap&g=7b710aa7fa646abf34e28576ac88969b&k=9E36825D7791379EC6A3CCA895AF7495&c=0&p=0.000000&
[Oct 12 01:55] == Info: About to connect() to v5.mersenne.org port 80
[Oct 12 01:55] == Info: Trying 70.167.121.136...
[Oct 12 01:55] == Info: connected
[Oct 12 01:55] == Info: Connected to v5.mersenne.org (70.167.121.136) port 80
[Oct 12 01:55] => Send header: GET /v5server/?v=0.95&px=GIMPS&t=ap&g=7b710aa7fa646abf34e28576ac88969b&k=9E36825D7791379EC6A3CCA895AF7495&c=0&p=0.000000&d=86400
[Oct 12 01:55] Host: v5.mersenne.org
[Oct 12 01:55] Accept: */*
[Oct 12 01:55]
[Oct 12 01:55] <= Recv header: HTTP/1.1 200 OK
[Oct 12 01:55] <= Recv header: Server: Microsoft-IIS/5.0
[Oct 12 01:55] <= Recv header: Date: Fri, 12 Oct 2007 00:56:53 GMT
[Oct 12 01:55] <= Recv header: X-Powered-By: ASP.NET
[Oct 12 01:55] <= Recv header: MicrosoftOfficeWebServer: 5.0_Pub
[Oct 12 01:55] <= Recv header: Connection: close
[Oct 12 01:55] <= Recv header: X-Powered-By: PHP/5.2.0
[Oct 12 01:55] <= Recv header: Content-type: text/html
[Oct 12 01:55] <= Recv data: pnErrorResult=0
[Oct 12 01:55] pnErrorDetail=SUCCESS
[Oct 12 01:55] ==END==
[Oct 12 01:55]
[Oct 12 01:55] == Info: Closing connection #0
[Oct 12 01:55] RESPONSE:
[Oct 12 01:55] pnErrorResult=0
[Oct 12 01:55] pnErrorDetail=SUCCESS
[Oct 12 01:55] ==END==
[Oct 12 01:55]
[Oct 12 01:55] Getting assignment from server
[Oct 12 01:55] URL: http://v5.mersenne.org/v5server/?v=0.95&px=GIMPS&t=ga&g=7b710aa7fa646abf34e28576ac88969b&c=0&ss=13716&sh=3D89C2C8C7D9F4F3E8489C2F232AB8D5
[Oct 12 01:55] == Info: About to connect() to v5.mersenne.org port 80
[Oct 12 01:55] == Info: Trying 70.167.121.136...
[Oct 12 01:55] == Info: connected
[Oct 12 01:55] == Info: Connected to v5.mersenne.org (70.167.121.136) port 80
[Oct 12 01:55] => Send header: GET /v5server/?v=0.95&px=GIMPS&t=ga&g=7b710aa7fa646abf34e28576ac88969b&c=0&ss=13716&sh=3D89C2C8C7D9F4F3E8489C2F232AB8D5 HTTP/1.1
[Oct 12 01:55] Host: v5.mersenne.org
[Oct 12 01:55] Accept: */*
[Oct 12 01:55]
[/CODE]

From the comm window while the thread just sat there..

[CODE][Oct 12 01:54] Trial factoring of M130358707 to 2^57 is 0.17% complete.
[Oct 12 01:54] M130358707 no factor to 2^57, Wd1: E33E6382
[Oct 12 01:54] Starting trial factoring of M130358773 to 2^57
[Oct 12 01:54] Trial factoring of M130358773 to 2^50 is 0.00% complete.
[Oct 12 01:54] M130358773 has a factor: 340583412583727
[Oct 12 01:54] No work to do at the present time. Waiting.
[Oct 12 01:55] Resuming.
[Oct 12 01:55] Starting trial factoring of M130358863 to 2^57
[Oct 12 01:55] Trial factoring of M130358863 to 2^50 is 0.00% complete.
[Oct 12 01:55] M130358863 has a factor: 15643063561
[Oct 12 01:55] M130358863 has a factor: 12514450849
[Oct 12 01:55] No work to do at the present time. Waiting.
[Oct 12 01:55] Resuming.
[Oct 12 01:55] Starting trial factoring of M130358951 to 2^57
[Oct 12 01:55] Trial factoring of M130358951 to 2^50 is 0.00% complete.
[Oct 12 01:55] Trial factoring of M130358951 to 2^51 is 6.25% complete.
[Oct 12 01:55] Trial factoring of M130358951 to 2^52 is 5.69% complete.
[Oct 12 01:55] M130358951 has a factor: 3271060917654623
[Oct 12 01:55] No work to do at the present time. Waiting.
[Oct 12 01:55] Resuming.
[Oct 12 01:55] Starting trial factoring of M130359007 to 2^57
[Oct 12 01:55] Trial factoring of M130359007 to 2^50 is 0.00% complete.
[Oct 12 01:55] M130359007 has a factor: 24246775303
[Oct 12 01:55] No work to do at the present time. Waiting.
[Oct 12 01:55] Resuming.
[Oct 12 01:55] Starting trial factoring of M130359083 to 2^57
[Oct 12 01:55] Trial factoring of M130359083 to 2^50 is 0.00% complete.
[Oct 12 01:55] Trial factoring of M130359083 to 2^51 is 6.25% complete.
[Oct 12 01:55] Trial factoring of M130359083 to 2^52 is 5.69% complete.
[Oct 12 01:55] Trial factoring of M130359083 to 2^53 is 2.84% complete.
[Oct 12 01:55] Trial factoring of M130359083 to 2^54 is 1.42% complete.
[Oct 12 01:55] Trial factoring of M130359083 to 2^55 is 0.71% complete.
[Oct 12 01:55] Trial factoring of M130359083 to 2^56 is 0.35% complete.
[Oct 12 01:55] Trial factoring of M130359083 to 2^57 is 0.17% complete.
[Oct 12 01:55] M130359083 no factor to 2^57, Wd1: E33E6384
[Oct 12 01:55] No work to do at the present time. Waiting.
[Oct 12 01:55] Resuming.
[Oct 12 01:55] Starting trial factoring of M130359157 to 2^57
[Oct 12 01:55] Trial factoring of M130359157 to 2^50 is 0.00% complete.
[Oct 12 01:55] M130359157 has a factor: 110426720458073
[Oct 12 01:55] No work to do at the present time. Waiting.
[Oct 12 01:55] Resuming.
[Oct 12 01:55] Starting trial factoring of M130359181 to 2^57
[Oct 12 01:55] Trial factoring of M130359181 to 2^50 is 0.00% complete.
[Oct 12 01:55] Trial factoring of M130359181 to 2^51 is 6.25% complete.
[Oct 12 01:55] Trial factoring of M130359181 to 2^52 is 5.69% complete.
[Oct 12 01:55] Trial factoring of M130359181 to 2^53 is 2.84% complete.
[Oct 12 01:55] Trial factoring of M130359181 to 2^54 is 1.42% complete.
[Oct 12 01:55] Trial factoring of M130359181 to 2^55 is 0.71% complete.
[Oct 12 01:55] Trial factoring of M130359181 to 2^56 is 0.35% complete.
[Oct 12 01:55] Trial factoring of M130359181 to 2^57 is 0.17% complete.
[Oct 12 01:55] M130359181 no factor to 2^57, Wd1: E32C6383
[Oct 12 01:55] Starting trial factoring of M130359211 to 2^57
[Oct 12 01:55] Trial factoring of M130359211 to 2^50 is 0.00% complete.
[Oct 12 01:55] Trial factoring of M130359211 to 2^51 is 6.25% complete.
[Oct 12 01:55] Trial factoring of M130359211 to 2^52 is 5.69% complete.
[Oct 12 01:55] Trial factoring of M130359211 to 2^53 is 2.84% complete.
[Oct 12 01:55] Trial factoring of M130359211 to 2^54 is 1.42% complete.
[Oct 12 01:55] Trial factoring of M130359211 to 2^55 is 0.71% complete.
[Oct 12 01:55] Trial factoring of M130359211 to 2^56 is 0.35% complete.
[Oct 12 01:55] Trial factoring of M130359211 to 2^57 is 0.17% complete.
[Oct 12 01:55] M130359211 no factor to 2^57, Wd1: E32D6381
[Oct 12 01:55] Starting trial factoring of M130359241 to 2^57
[Oct 12 01:55] Trial factoring of M130359241 to 2^50 is 0.00% complete.
[Oct 12 01:55] M130359241 has a factor: 965701257329
[Oct 12 01:55] No work to do at the present time. Waiting.
[Oct 12 01:55] Resuming.
[Oct 12 01:55] Starting trial factoring of M130359311 to 2^57
[Oct 12 01:55] Trial factoring of M130359311 to 2^50 is 0.00% complete.
[Oct 12 01:55] Trial factoring of M130359311 to 2^51 is 6.25% complete.
[Oct 12 01:55] Trial factoring of M130359311 to 2^52 is 5.69% complete.
[Oct 12 01:55] Trial factoring of M130359311 to 2^53 is 2.84% complete.
[Oct 12 01:55] Trial factoring of M130359311 to 2^54 is 1.42% complete.
[Oct 12 01:55] Trial factoring of M130359311 to 2^55 is 0.71% complete.
[Oct 12 01:55] Trial factoring of M130359311 to 2^56 is 0.35% complete.
[Oct 12 01:55] Trial factoring of M130359311 to 2^57 is 0.17% complete.
[Oct 12 01:55] M130359311 no factor to 2^57, Wd1: E33B6382
[Oct 12 01:55] No work to do at the present time. Waiting.
[Oct 12 01:55] Resuming.
[Oct 12 01:55] Starting trial factoring of M130359389 to 2^57
[Oct 12 01:55] Trial factoring of M130359389 to 2^50 is 0.00% complete.
[Oct 12 01:55] M130359389 has a factor: 449302927378073
[Oct 12 01:55] No work to do at the present time. Waiting.
[Oct 12 02:55] Resuming.
[Oct 12 02:55] No work to do at the present time. Waiting.
[Oct 12 03:55] Resuming.
[Oct 12 03:55] No work to do at the present time. Waiting.
[Oct 12 04:55] Resuming.
[Oct 12 04:55] No work to do at the present time. Waiting.
[Oct 12 05:55] Resuming.
[Oct 12 05:55] No work to do at the present time. Waiting.
[Oct 12 06:55] Resuming.
[Oct 12 06:55] No work to do at the present time. Waiting.
[Oct 12 07:55] Resuming.
[Oct 12 07:55] No work to do at the present time. Waiting.
[Oct 12 08:55] Resuming.
[Oct 12 08:55] No work to do at the present time. Waiting.
[Oct 12 09:55] Resuming.
[Oct 12 09:55] No work to do at the present time. Waiting.
[/CODE]

Manual communication doesn't fix it only an exit and restart

Another feature request:[list][*]Have a worktype of "TF up to ___ bits" -- this would be basically a modification of the "TF to low limits", perhaps if you restrict the range of values entered (to something between 2^56 and 2^64?, perhaps defaulted to a sensible value based on general machine speed (e.g. 2^64 on a modern CPU but 2^56 for a 486, etc)) it would replace both the "TF to low limits" worktype, and the manual TF work that LMH does.[/list]

[QUOTE=Bundu;116235]I wonder what time? I only ask because my 3 instances did the same on vista last night:

Manual communication doesn't fix it only an exit and restart[/QUOTE]I came home today to find my Prime64 just sitting there with no work. Manual communication kicked it back into gear for a while, but as soon as 2000h rolled around it got stuck waiting for the server to respond with more work (PHP 60-second timeout on line 82).

Happened at about 2100 UTC Oct 11th at my end.

RollingAverage et al
 

Did some testing of mprime v25.5 under Linux specifically for the RollingAverage. Conclusions:
(1) RollingAverage does not work when v25.5 runs for fewer hours per day than given in the CPUHours setting.
(2) Another possible bug noticed: no torture test was performed before starting to test a new assigned exponent (double check in the M19000000 series) even though I started with a completely new user account.
(3) Another possible bug noticed: when I unreserved the exponent from the menu at the end of the testing, the client software immediately contacted the server for more work and was given the same exponent again. (Succeeded in unreserving this afterwards using v24.14.)
See also [URL]http://www.mersenneforum.org/showpost.php?p=116261#post116261[/URL]

[QUOTE=Brian-E;116262](2) Another possible bug noticed: no torture test was performed before starting to test a new assigned exponent (double check in the M19000000 series) even though I started with a completely new user account.[/QUOTE]Possible explanation : the fact that the test has been done for a given FFT size is stored in the .ini (or .txt for version 25) files. Starting with a new user account does not reset all the data ...

Jacob

[quote=S485122;116265]Possible explanation : the fact that the test has been done for a given FFT size is stored in the .ini (or .txt for version 25) files. Starting with a new user account does not reset all the data ...

Jacob[/quote]

The test was conducted in a separate directory. The local.txt file was newly created. So the software could not know that the torture test had already been done in a different environment.

One observation: the server was down at the time the new testing environment was created. The test could then not start until the following day when the exponent was able to be assigned. Perhaps the bug only occurs under these unusual circumstances.