I'll also pause my individual k's search and move the quad-core to C443.

IB,

To quickly help the drying process of port 7500 could you reduce the "maximum allowed time for a user to complete a job" to 4 hours?

Carlos

Port 7500 has now dried out. No more work is available for the 4th drive other than a manual range that I am working on.

I'm shifting all my machines to the manual range, which should be complete in ~3 days.

This is all I have running now for official llrnet servers hosted here
crus 6
nplb 400
nplb 5000

Max needs to clean up these and we will be good to go :smile:
10000
10001

Is it just me, or are all of IronBits' servers down? I can connect to his web pages just fine (so it definitely isn't a problem with his internet connection), but for whatever reason none of my clients can connect to his LLRnet servers. Can anyone else connect to them? (I noticed that the web pages showed "no results.txt for today" on all servers--surely if anyone else was able to connect, there would be something there?)

[quote=mdettweiler;145861]Is it just me, or are all of IronBits' servers down? I can connect to his web pages just fine (so it definitely isn't a problem with his internet connection), but for whatever reason none of my clients can connect to his LLRnet servers. Can anyone else connect to them? (I noticed that the web pages showed "no results.txt for today" on all servers--surely if anyone else was able to connect, there would be something there?)[/quote]

Port 400 is definitely down, although port 5000 seems to be working fine but the latter must have been down earlier since there are no results for the day for it. I just now moved 2 slow cores to port 5000 and will shortly move 2 even slower :-) cores to it.

So if anyone sees this, go ahead and use port 5000 for the 3rd drive and port 443 for the 1st drive until we find out what's up.


Gary

[quote=IronBits;145816]This is all I have running now for official llrnet servers hosted here
crus 6
nplb 400
nplb 5000

Max needs to clean up these and we will be good to go :smile:
10000
10001[/quote]

David,

Per the Email that I sent you, I can't tell if all straggling k/n pairs have been 100% processed on port 7500 since the stats are not showing on the web page. I know it was dried out but as of late last night, there were still a few remaining to be processed.

Can you verify that all port 7500 k/n pairs were processed?


Thanks,
Gary

[quote=gd_barnes;145862]Port 400 is definitely down, although port 5000 seems to be working fine but the latter must have been down earlier since there are no results for the day for it. I just now moved 2 slow cores to port 5000 and will shortly move 2 even slower :-) cores to it.

So if anyone sees this, go ahead and use port 5000 for the 3rd drive and port 443 for the 1st drive until we find out what's up.


Gary[/quote]
Hmm...actually, it seems that they're all back on now. The only remaining problem is that port 400 seems to have dried out (!). When I tried to connect to it as a test my client said that there was no work from the server and it would try again later.

Regardless, all the rest of the servers seem to be on (except for the odd issue on port 400), so thanks David, whatever you did! :grin:

Edit: Ah, I just checked my email and saw a reply to an earlier message I sent to David regarding the servers being down--he said that it was due to a little error on his local network, and that that's fixed now. I mentioned the strange issue with port 400 in my reply.

[quote=mdettweiler;145864]Hmm...actually, it seems that they're all back on now. The only remaining problem is that port 400 seems to have dried out (!). When I tried to connect to it as a test my client said that there was no work from the server and it would try again later.

Regardless, all the rest of the servers seem to be on (except for the odd issue on port 400), so thanks David, whatever you did! :grin:

Edit: Ah, I just checked my email and saw a reply to an earlier message I sent to David regarding the servers being down--he said that it was due to a little error on his local network, and that that's fixed now. I mentioned the strange issue with port 400 in my reply.[/quote]


I don't know what you mean that port 400 has dried out. That has never been the case. It has plenty of pairs for several weeks. It was 'sleeping' due to the issue that David described.

Anyway, port 400 as well as all other ports are working fine now. Thanks, David, for taking care of that.


Gary

[quote=gd_barnes;145879]I don't know what you mean that port 400 has dried out. That has never been the case. It has plenty of pairs for several weeks. It was 'sleeping' due to the issue that David described.

Anyway, port 400 as well as all other ports are working fine now. Thanks, David, for taking care of that.


Gary[/quote]
What I meant is that for whatever reason, it seemed to appear to my client as if it was dried out...but, since that's all fixed now, no biggie. :smile:

David,

I don't seem to access to view the Oct. 23rd results files. Can you check on that?


Thanks,
Gary