Report Primes from the 1st Drive K=3401-3999 Port 7771 {Closed}

3575*2^433894-1
3711*2^417325-1
3579*2^472965-1
3839*2^415832-1
3733*2^405267-1
3429*2^410421-1
3937*2^411697-1
3741*2^413701-1
3891*2^413969-1
3897*2^415329-1
3451*2^415093-1
3963*2^416908-1
3783*2^417178-1
3705*2^418519-1
3889*2^418653-1
3553*2^418791-1
3429*2^419073-1
3783*2^419556-1
3945*2^420335-1
3481*2^422731-1
3785*2^423984-1
3927*2^424228-1
3431*2^425222-1
3801*2^426542-1
3521*2^426574-1
3483*2^426684-1
3711*2^427166-1
3441*2^433298-1
3851*2^434606-1
3661*2^436175-1
3873*2^436675-1
3489*2^439008-1
3699*2^440363-1
3789*2^463153-1
3741*2^415666-1
3491*2^406442-1
3805*2^407271-1
3493*2^407383-1
3747*2^411301-1
3449*2^411696-1
3647*2^414666-1
3827*2^415196-1
3807*2^417456-1
3563*2^417904-1
3601*2^418593-1
3787*2^419341-1
3963*2^418808-1
3525*2^419312-1
3665*2^419744-1
3951*2^422314-1
3947*2^422368-1
3609*2^423416-1
3429*2^424883-1
3867*2^426300-1
3471*2^428214-1
3735*2^428222-1
3567*2^430065-1
3599*2^430684-1
3895*2^432483-1
3905*2^433162-1
3801*2^433197-1
3875*2^435158-1
3773*2^435322-1
3563*2^435762-1
3923*2^435972-1
3959*2^436460-1
3535*2^436831-1
3689*2^437616-1
3569*2^438344-1
3447*2^438740-1
3777*2^438837-1
3765*2^440024-1
3533*2^444620-1
3755*2^444922-1
3649*2^445431-1
3591*2^446169-1
3965*2^446324-1
3841*2^447195-1
3495*2^447334-1
3713*2^447768-1
3861*2^448050-1
3819*2^448455-1
3777*2^449702-1
3485*2^449996-1
3451*2^451511-1
3597*2^456409-1
3947*2^452830-1
3657*2^457261-1
3569*2^458000-1
3789*2^453697-1
3909*2^454037-1
3549*2^459936-1
3601*2^455551-1
3665*2^461580-1
3935*2^461978-1
3531*2^462307-1
3789*2^462517-1
3741*2^463819-1
3939*2^463897-1
3879*2^464311-1
3549*2^465568-1
3725*2^466592-1
3871*2^467103-1
3783*2^467492-1
3623*2^468132-1
3921*2^468634-1
3575*2^469368-1
3493*2^469759-1
3771*2^469979-1
3519*2^470108-1
3771*2^470558-1
3703*2^470687-1
3461*2^470698-1
3617*2^471448-1
3641*2^474226-1
3575*2^474486-1
3489*2^474583-1
3647*2^476840-1
3837*2^477338-1
3631*2^477461-1
3747*2^477510-1
3513*2^478187-1
3723*2^478372-1
3445*2^482257-1
3707*2^482636-1
3967*2^482777-1
3851*2^483502-1
3489*2^488265-1
3875*2^467870-1
3661*2^485423-1
3845*2^476982-1
3811*2^481221-1
3631*2^482379-1
3423*2^489336-1
3591*2^491002-1
3423*2^491415-1
3503*2^492142-1
3523*2^492687-1

3489*2^493411-1 (148536 digits)

3759*2^493805-1 (148654 digits)

3495*2^494116-1 (148748 digits)

3577*2^494277-1

3893*2^494308-1 (148806 digits)

3403*2^495511-1

Also - This prime is showing in my client logs with a server error:

Code:

---

3403*2^495511-1 is prime!  Time : 315.400 sec.
The server refused your new result :
either someone else computed it already,
either the server is now configured to
work on other numbers.

---

,

and I'm not showing in the stats for port 7771 http://primesearch.free-dc.org/stats...ntent=progress

It appears from the log that none of my work since I switched to port 7771 has been accepted by the server, but it's happily handing it out to me.

Angus
Enter the prime you found at the top 5000 site.

We will try to work out why your client is behaving strangely.

PS
In the mean time please check the time and date on the PC.

The server handed out that test to you today and still thinks it is in progress.
Recognized Angus when you get work but not when you return it most odd.

There is a 24hr deadline but you didn't exceed that
Gut feeling at the moment is a corrupt client.

That's real odd. I stopped one of the clients, edited the config file from port 7773 to 7771, saved the file and restarted the client sometime over the weekend.

It's the same client that was working up to that point on the other port. I'll try a different port when I get near the box again in a few hours.

I have two copies of the client running on a dual core box, each client from it's own folder.

Edit: I changed the offending client to 7772 and it's working fine.

Quote:

---

Originally Posted by PCZ

Angus
Enter the prime you found at the top 5000 site.

We will try to work out why your client is behaving strangely.

PS
In the mean time please check the time and date on the PC.

The server handed out that test to you today and still thinks it is in progress.
Recognized Angus when you get work but not when you return it most odd.

There is a 24hr deadline but you didn't exceed that
Gut feeling at the moment is a corrupt client.

---

Angus

I see you in the stats on port 7771 is it working now ?

Yes, it's working now.

I think I figured out it's some weird interaction with the llrnet-remote GUI window. I didn't close the window when I originally switched to 7771, just killed and restarted the client. It must have some sort of cached connection settings for the upload (downloads worked OK).

3481*2^495859-1

Quote:

---

Originally Posted by Angus

Yes, it's working now.

I think I figured out it's some weird interaction with the llrnet-remote GUI window. I didn't close the window when I originally switched to 7771, just killed and restarted the client. It must have some sort of cached connection settings for the upload (downloads worked OK).

---

I think Shish has a similar problem, he has a boatload of rejected results coming in on the 7773 server.

3743*2^495958-1

You cannot simply switch between ports without 'running down' the cache.

If you have work from port-A in the cache and switch to port-B then port-B will reject the port-A work.

To switch from 1 port to another you should run down the cache first.

WUCacheSize in the client config file will set how many workunits the client will download at a time.

When you want to empty the cache, edit the cache size to 1.
Stop and restart the client so that it registers the new setting.
Keep tabs on the number of lines in the file workfile.txt.
When it gets down to 2 lines, remove the '-- ' comment mark from in front of the 'once=1'
then stop and restart the client and it will complete the last workunit and shut down.
Then re-insert the '--' comment mark in front of the 'once=1' (or it will only do 1 wu when you restart)
Then change your port number and restart the client.

This will avoid errors and ensure that you get all the credit for your hard work.

I only have a cache of 4. I expected it to reject those (soimetimes I don't remember to empty the cache), but then the ones it pulled from the new port were all being rejected - a couple of days worth.

I expect it was still trying to send them to the old port for some reason.

Quote:

---

Originally Posted by AMDave

You cannot simply switch between ports without 'running down' the cache.

If you have work from port-A in the cache and switch to port-B then port-B will reject the port-A work.

To switch from 1 port to another you should run down the cache first.

WUCacheSize in the client config file will set how many workunits the client will download at a time.

When you want to empty the cache, edit the cache size to 1.
Stop and restart the client so that it registers the new setting.
Keep tabs on the number of lines in the file workfile.txt.
When it gets down to 2 lines, remove the '-- ' comment mark from in front of the 'once=1'
then stop and restart the client and it will complete the last workunit and shut down.
Then re-insert the '--' comment mark in front of the 'once=1' (or it will only do 1 wu when you restart)
Then change your port number and restart the client.

This will avoid errors and ensure that you get all the credit for your hard work.

---

3897*2^496170-1

Right you are Angus.

I suspect that changing between port 7771 and 7772 is ok at the moment because they both have the same search parameter in the first line of the file "10000000000:M:1:2:258"

Where you would have a problem is with switching to or from port 7773 bacause the search parameter is different "10000000000000:M:1:2:258", having 3 additional zeros in the depth.

That difference could cause a number of rejections until the client sorts itself out.

If you want to be completely sure about the switch between ports, stop the client, then delete the "workfile.txt" file and any "zXXXXXXX" files in the client folder (those are work-in-progress files which the client can pick up again and cause the same issue). Any pairs left in those files will get handed out to another participant as soon as they expire (currently all 3 ports have a jobMaxTime of 1 day - that is the expiry time). Change your port number and fire up the client. It will automatically create a new work file from the new port with the search parameter from that port.

You can observe the jobMaxTime and other parameters on the port report page:
http://primesearch.free-dc.org/stats...p?content=port
which now includes the server status report:
http://primesearch.free-dc.org/stats...rver_status_ib

3771*2^496225-1

3727*2^496601-1 (149496 digits)

3751*2^497655-1

3945*2^497940-1 (149899 digits)

3531*2^498715-1

3499*2^499039-1 (150230 digits)

3597*2^500166-1 (150569 digits)

3563*2^500598-1
3573*2^501019-1
3405*2^501382-1

3921*2^502039-1 (151133 digits)

3639*2^502247-1
3501*2^504127-1
3709*2^504777-1
3805*2^505317-1
3921*2^506471-1
3773*2^506618-1
3741*2^507929-1
3751*2^516083-1
3495*2^516334-1
3923*2^516904-1
3543*2^517192-1
3573*2^517463-1
3915*2^517581-1
3703*2^518735-1

3927*2^517817-1 is prime!
3633*2^518088-1 is Prime!

3723*2^519082-1 is Prime!

3741*2^519231-1 is Prime!
3873*2^519288-1 is Prime!

Added 91191 : 3721*2^520263-1 (156619 digits)

3485*2^520390-1

3423*2^520902-1

3407*2^521130-1
Already in database!

Shish
Looks like Beyond tested a few pairs above 521K.
I will remove the pairs he tested.

FInding a prime already in the database is no fun.

Thought I was getting a few too many or very lucky. No probs. Cheers and beers.
Kind regards,
Shish

3429*2^523109-1 is Prime!

3597*2^524124-1

3879*2^524864-1 is Prime!