View Single Post
Old 2004-05-03, 01:36   #8
nevillednz
 
May 2004

32 Posts
Default

I created the file, and even put UseFullURL=1 into primenet.ini and prime.ini, saddly no luck.
$ ls -lt *.ini
-rw-rw-r-- 1 nevilled nevilled 215 May 3 09:06 local.ini
-rw-rw-r-- 1 nevilled nevilled 230 May 3 08:32 prime.ini
-rw-rw-r-- 1 nevilled nevilled 13 May 3 08:32 primenet.ini
-rw-rw-r-- 1 nevilled nevilled 0 May 1 10:50 worktodo.ini
$ grep UseFullURL=1 *.ini
prime.ini:UseFullURL=1
primenet.ini:UseFullURL=1
$ ./mprime -d
Mersenne number primality test program version 23.5
Sending result to server for exponent 18080627
ERROR: Primenet error 2252
The FAQ at http://www.entropia.com/ips/faq.html may have more information.
Will try contacting server again in 60 minutes.
^C
$ strings mprime | egrep -i "primenet.ini|url"
primenet.ini
UseFullURL
$ -- so it seems that the executable does know about primenet.ini & UseFullURL

I note that once a month, near the estimated end date the system manages to communicate a different message with the primenet server. i.e.
[Fri Mar 12 16:40:24 2004 - ver 23.5]
Updating computer information on the server
Sending expected completion date for M18080627: Apr 19 2004
[Sat Apr 10 09:56:27 2004 - ver 23.5]
Updating computer information on the server
Sending expected completion date for M18080627: May 9 2004

Maybe I should just leave it running for a few more day waiting for the next "end date check in"?? (Or I could change LastEndDatesSent=1081562188 to a smaller number to speed this up?)

I also note that the problem only started on the 12th or March. Prior to this the "client" mprime program did not log any server connection problems/messages (even after several months of running). It is possible that something was changed on the server that triggered this problem? Possibly the mprime "server side" communication service was changed, or maybe you installed a WindowsNT service pack that was patching one of Microsofts famous virus/worm holes? (Which works so well that NO relative URLs work anymore...)

Here is a log when the FIRST problem happened:

Updating computer information on the server
Sending expected completion date for M18080627: Mar 15 2004
[Fri Mar 12 14:25:11 2004 - ver 23.5]
ERROR: Primenet error 2252
[Fri Mar 12 14:25:40 2004 - ver 23.5]
ERROR: Primenet error 2252
[Fri Mar 12 16:40:24 2004 - ver 23.5]
Updating computer information on the server
Sending expected completion date for M18080627: Apr 19 2004
[Fri Apr 2 11:26:33 2004 - ver 23.5]
Updating computer information on the server
ERROR: Primenet error 2252
[Fri Apr 2 11:29:44 2004 - ver 23.5]
Updating computer information on the server
ERROR: Primenet error 2252

(FYI: mprime not been running 100% of the time on this machine)

Any more ideas? (I am leaning towards downloading & compiling the new version for linux)

NevilleD
nevillednz is offline