mersenneforum.org Testing....
 Register FAQ Search Today's Posts Mark Forums Read

2010-03-05, 02:06   #199
mdettweiler
A Sunny Moo

Aug 2007
USA

187716 Posts

Quote:
 Originally Posted by kar_bon ok, here is the WIN-version of the local server/client with the above changes in the do.bat and a knpair-file in the server for testing. how to: - start the server by calling 'llrserver' (in folder LLRnet_server) - start 'do.bat' (in folder LLRnet_client) - let cllr do 5 pairs first and another 2 - stop the client with CTRL-C - call 'do -c' - stop server - call 'simplify.bat' (in folder LLRnet_server) check all files (server-result, job/knpair-files, client results) for completeness!
Quick question: how is one supposed to check to see if a pair's been canceled when running simplify.bat at the end triggers a prune? That pretty much always removes any "canceled" records from joblist.txt--after all, there's no reason for the server to keep those around since there's no reservation whatsoever on the pair. I suppose one could just verify that no active reservation is still in place, but wouldn't it be easier to just search for all instances of the pair in question in joblist.txt and see what it's latest state is (reserved, canceled, or done)?

 2010-03-05, 06:20 #200 kar_bon     Mar 2006 Germany 2×3×5×101 Posts the simplify.bat is only for persons running a server, not for 'normal' users doing work for NPLB. so how it works now? if a pair is cancelled by a user, will the server instantly submit it to the next user requesting new pairs? could you determine this, please. all submitted results in the result-file of the server (nothing lost), all not-done pairs are still in the knpairs.txt of the server (nothing lost, too) and the CANCEL-pairs in the joblist should be eliminated when jobMaxTime is over. or not? i'll try this by setting the jobMaxTime to a small value and try to connect with another user, do work and submit pairs. Last fiddled with by kar_bon on 2010-03-05 at 06:22
2010-03-05, 07:19   #201
mdettweiler
A Sunny Moo

Aug 2007
USA

6,263 Posts

Quote:
 Originally Posted by kar_bon the simplify.bat is only for persons running a server, not for 'normal' users doing work for NPLB. so how it works now? if a pair is cancelled by a user, will the server instantly submit it to the next user requesting new pairs? could you determine this, please. all submitted results in the result-file of the server (nothing lost), all not-done pairs are still in the knpairs.txt of the server (nothing lost, too) and the CANCEL-pairs in the joblist should be eliminated when jobMaxTime is over. or not? i'll try this by setting the jobMaxTime to a small value and try to connect with another user, do work and submit pairs.
Here's what happens:

-A pair is reserved and a notation of such is made in joblist.txt
-The same pair is canceled, and an additional notation is made in joblist.txt recording that. Note that both the reservation and cancellation joblist entries coexist, but the cancellation takes precedence since it has a newer timestamp.
-The pair is now considered immediately available for assignment just as if it was brand new.
-When the server does its next prune, it will remove both the reservation and cancellation records from joblist, since the latter negates the former and the pair is "good as new".

 2010-03-05, 12:44 #202 kar_bon     Mar 2006 Germany 303010 Posts i've tested more with that new version: - all pairs done without stopping the script with CTRL-C - script stopped and continued later - script stopped, some pairs cancelled and continued - script stopped, some pairs cancelled and continued with other user all is ok as i can say now. the only thing, that should be done on the server-side when dried is, calling 2 times "llrserver -s" to clear knpairs and joblist files! so this is it! (only speak for WIN) without processing a workfile (which pairs done and which to cancel) and without any 'empty' line! i've uploaded the latest V7-Version to the former link (small change in do.bat)
2010-03-05, 17:11   #203
mdettweiler
A Sunny Moo

Aug 2007
USA

11000011101112 Posts

Quote:
 Originally Posted by kar_bon i've tested more with that new version: - all pairs done without stopping the script with CTRL-C - script stopped and continued later - script stopped, some pairs cancelled and continued - script stopped, some pairs cancelled and continued with other user all is ok as i can say now. the only thing, that should be done on the server-side when dried is, calling 2 times "llrserver -s" to clear knpairs and joblist files! so this is it! (only speak for WIN) without processing a workfile (which pairs done and which to cancel) and without any 'empty' line! i've uploaded the latest V7-Version to the former link (small change in do.bat)
Karsten, could you possibly re-post the link? I can't find it; I tried the one in the first post of this thread but got version 0.63.

 2010-03-05, 17:12 #204 kar_bon     Mar 2006 Germany 1011110101102 Posts see post #198!
2010-03-05, 17:42   #205
mdettweiler
A Sunny Moo

Aug 2007
USA

6,263 Posts

Quote:
 Originally Posted by kar_bon see post #198!
Ah, thanks, got it now.

 2010-03-05, 18:10 #206 mdettweiler A Sunny Moo     Aug 2007 USA 6,263 Posts Okay, I tried testing the latest do.bat to cancel pairs, and it seems to have messed up somewhat. I tried it with 4 completed results and one incomplete test in queue, and it produced this output: Code: +-------------------------------------+ | LLRnet client V0.9b7 with cLLR V3.8 | | K.Bonath, 2010-02-10, Version 0.7 | +-------------------------------------+ Current configuration: server = "nplb-gb1.no-ip.org" port = 1764 username = "mdettweiler" WUCacheSize = 5 [2010-03-05 12:58:24] The server refused your new result : either someone else computed it already, either the server is now configured to work on other numbers. The server refused your new result : either someone else computed it already, either the server is now configured to work on other numbers. The server refused your new result : either someone else computed it already, either the server is now configured to work on other numbers. The server refused your new result : either someone else computed it already, either the server is now configured to work on other numbers. The server refused your new result : either someone else computed it already, either the server is now configured to work on other numbers. The server refused your new result : either someone else computed it already, either the server is now configured to work on other numbers. The server refused your new result : either someone else computed it already, either the server is now configured to work on other numbers. The server refused your new result : either someone else computed it already, either the server is now configured to work on other numbers. Cancelling : 197/118072 (600000000000:M:1:2:258) Could Not Find C:\Documents and Settings\All Users\Documents\prime\NPLB-llrnetnew\workfile .res [2010-03-05 12:58:26] Fetching WU #5/5: 197 118072 Cancelling : 197/118094 (600000000000:M:1:2:258) [2010-03-05 12:58:28] Cancelling : 197/118102 (600000000000:M:1:2:258) [2010-03-05 12:58:28] Cancelling : 197/118142 (600000000000:M:1:2:258) [2010-03-05 12:58:28] Cancelling : 197/118154 (600000000000:M:1:2:258) [2010-03-05 12:58:29] Cancelling : 197/118072 (600000000000:M:1:2:258) [2010-03-05 12:58:29] No more job to cancel ! All jobs canceled! First of all, all four completed results are apparently sent but rejected. (I see that there's 8 rejected messages, but that's to be expected since LLRnet's duplicated those messages on the console for as long as I can remember; also as expected, only 4 rejected messages were shown in lresults_hist.txt.) After that, all five jobs were canceled, which I verified on the server was done correctly. The program beeped a few times then exited. So it seems the cancellation part itself is working all right; the only problem is in sending the completed results before canceling the rest. Any idea why this isn't working? I looked in do.bat but couldn't find anything that could be a culprit, since it appeared that it was doing it in a pretty straightforward way: convert the results, add them to lresults_hist.txt, then run LLRnet to send them.
 2010-03-05, 18:41 #207 kar_bon     Mar 2006 Germany 2·3·5·101 Posts ok, forgot to copy/create the workfile.bak in the cancel-routine! update do.bat with one line: Code: :jobcancel if not exist lresults.txt goto jobcancel1 copy workfile.txt workfile.bak gawk -f do_tosend.awk lresults.txt i'll upload the corrected zip immediately! don't forget to call twice 'llrserver -s' after cancelling with 'do -c'! Last fiddled with by kar_bon on 2010-03-05 at 18:43
2010-03-05, 18:52   #208
mdettweiler
A Sunny Moo

Aug 2007
USA

626310 Posts

Quote:
 Originally Posted by kar_bon ok, forgot to copy/create the workfile.bak in the cancel-routine! update do.bat with one line: Code: :jobcancel if not exist lresults.txt goto jobcancel1 copy workfile.txt workfile.bak gawk -f do_tosend.awk lresults.txt i'll upload the corrected zip immediately! don't forget to call twice 'llrserver -s' after cancelling with 'do -c'!
Thanks! I'll give it a whirl.

 2010-03-05, 19:02 #209 mdettweiler A Sunny Moo     Aug 2007 USA 6,263 Posts Okay, I tried it in the exact same situation as before (4 pairs done, 1 pair in progress) and it seems to have worked correctly: Code: +-------------------------------------+ | LLRnet client V0.9b7 with cLLR V3.8 | | K.Bonath, 2010-02-10, Version 0.7 | +-------------------------------------+ Current configuration: server = "nplb-gb1.no-ip.org" port = 1764 username = "mdettweiler" WUCacheSize = 5 1 file(s) copied. [2010-03-05 13:53:57] Cancelling : 197/121718 (600000000000:M:1:2:258) [2010-03-05 13:53:58] Cancelling : 197/121768 (600000000000:M:1:2:258) [2010-03-05 13:53:58] Cancelling : 197/121772 (600000000000:M:1:2:258) [2010-03-05 13:53:59] Cancelling : 197/121784 (600000000000:M:1:2:258) [2010-03-05 13:53:59] Cancelling : 197/121846 (600000000000:M:1:2:258) [2010-03-05 13:53:59] No more job to cancel ! All jobs canceled! The only possible issue I found is a cosmetic one: after the four completed pairs are submitted, all five are then canceled despite there only being one left that's incomplete. Of course the server ignores the cancel requests on the first four since it already has results for them, but still, it might prove rather confusing for users. The tricky part is how to have the batch file "know" how many WUs were completed and sent in. In do.pl that's done by incrementing a \$numResults variable as each result is processed, but that would be impossible for do.bat since it doesn't actually do the processing but rather has gawk do it. Oh, I know! What if you had do.bat count the number of lines in tosend.txt before that's sent? If you take that number minus one (the newline at the end) it should give you the number of completed results done, and from there you can have it remove those from workfile.txt before beginning the actual cancellation process. Edit: scratch that, looks like it didn't work. I just started up the client again and it grabbed exactly the same 5 pairs that it did before--including the ones that were already done. It seems the server didn't ignore the cancellation requests on the completed ones as I thought; somehow they were thrown back into the pool to be reassigned. The fix would be the same as the one I presented above: the only difference being that it's no longer just a cosmetic issue but a real one. Last fiddled with by mdettweiler on 2010-03-05 at 19:04

 Similar Threads Thread Thread Starter Forum Replies Last Post kladner Soap Box 3 2016-10-14 18:43 GARYP166 Information & Answers 9 2009-02-18 22:41 gd_barnes Riesel Prime Search 20 2007-11-08 21:13 grobie Marin's Mersenne-aries 1 2006-05-15 12:26 eepiccolo Math 6 2006-03-28 20:53

All times are UTC. The time now is 17:17.

Tue Mar 28 17:17:15 UTC 2023 up 222 days, 14:45, 0 users, load averages: 0.64, 0.71, 0.79

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.

≠ ± ∓ ÷ × · − √ ‰ ⊗ ⊕ ⊖ ⊘ ⊙ ≤ ≥ ≦ ≧ ≨ ≩ ≺ ≻ ≼ ≽ ⊏ ⊐ ⊑ ⊒ ² ³ °
∠ ∟ ° ≅ ~ ‖ ⟂ ⫛
≡ ≜ ≈ ∝ ∞ ≪ ≫ ⌊⌋ ⌈⌉ ∘ ∏ ∐ ∑ ∧ ∨ ∩ ∪ ⨀ ⊕ ⊗ 𝖕 𝖖 𝖗 ⊲ ⊳
∅ ∖ ∁ ↦ ↣ ∩ ∪ ⊆ ⊂ ⊄ ⊊ ⊇ ⊃ ⊅ ⊋ ⊖ ∈ ∉ ∋ ∌ ℕ ℤ ℚ ℝ ℂ ℵ ℶ ℷ ℸ 𝓟
¬ ∨ ∧ ⊕ → ← ⇒ ⇐ ⇔ ∀ ∃ ∄ ∴ ∵ ⊤ ⊥ ⊢ ⊨ ⫤ ⊣ … ⋯ ⋮ ⋰ ⋱
∫ ∬ ∭ ∮ ∯ ∰ ∇ ∆ δ ∂ ℱ ℒ ℓ
𝛢𝛼 𝛣𝛽 𝛤𝛾 𝛥𝛿 𝛦𝜀𝜖 𝛧𝜁 𝛨𝜂 𝛩𝜃𝜗 𝛪𝜄 𝛫𝜅 𝛬𝜆 𝛭𝜇 𝛮𝜈 𝛯𝜉 𝛰𝜊 𝛱𝜋 𝛲𝜌 𝛴𝜎𝜍 𝛵𝜏 𝛶𝜐 𝛷𝜙𝜑 𝛸𝜒 𝛹𝜓 𝛺𝜔