155.247.166.219 rejecting
Moderators: Site Moderators, FAHC Science Team
155.247.166.219 rejecting
155.247.166.219 has been rejecting connections since earlier today. All but two of my nodes configured with >24 cpus have stopped folding. Somehow those two got assigned to 134.139.52.2 and 134.139.52.3 which I don't even see on the server status list. Do I just have to reconfigure my big nodes to use be cpus=24 every time this occurs now or is there another solution?
Re: 155.247.166.219 rejecting
I'll notify those who can fix 155.247.166.219
FAH's projects vary in size and some cannot fully utilize 24 CPUs without crashing. If you're using th released FAHClient v7.4.4, it will ONLY accept projects that meet your request for using 24 cores. If you're using the beta v7.4.15 or .16 it will negotiate with the servers and find the largest project that's available that uses <=24 rather than remaining idle.
Both servers 134.139.52.2 and 134.139.52.3 are on-line at csulb.edu. They're shown in the beta version of serverstat.html ... which hopefully will soon replace the public version.
If you posted your log, we could probably help you better.
FAH's projects vary in size and some cannot fully utilize 24 CPUs without crashing. If you're using th released FAHClient v7.4.4, it will ONLY accept projects that meet your request for using 24 cores. If you're using the beta v7.4.15 or .16 it will negotiate with the servers and find the largest project that's available that uses <=24 rather than remaining idle.
Both servers 134.139.52.2 and 134.139.52.3 are on-line at csulb.edu. They're shown in the beta version of serverstat.html ... which hopefully will soon replace the public version.
If you posted your log, we could probably help you better.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: 155.247.166.219 rejecting
Thanks for the tip about the beta version, Bruce. I'll give that a try.
Re: 155.247.166.219 rejecting
Looks like 155.247.166.219 started accepting requests yesterday afternoon. I am able to get work units and upload them without errors. However, it appears that am not getting credit for those completed work units. It looks like I have completed about 17 WUs since the server came back online, but have not received any credit for them.
Should I create a new post for this, or is this related to the server rejecting from yesterday?
Thanks!
Should I create a new post for this, or is this related to the server rejecting from yesterday?
Thanks!
Re: 155.247.166.219 rejecting
I've notified the stats team of the problem.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: 155.247.166.219 rejecting
Thanks Bruce!bruce wrote:I've notified the stats team of the problem.
Re: 155.247.166.219 rejecting
I completed one to this server and the points had been posted when I checked at 1PM (EST) today (about 6 hours ago). Anyone having a problem getting credit since then?
========
DrBB1
DrBB1
Re: 155.247.166.219 rejecting
I just went through my logs and I have not received credit for 21 WUs that were uploaded between 12/19/17 @ 21:36:05 and 12/21/17 @ 00:26:19.DrBB1 wrote:I completed one to this server and the points had been posted when I checked at 1PM (EST) today (about 6 hours ago). Anyone having a problem getting credit since then?
And I just realized what happened. Someone had commented above about trying out the Beta client, which ended up crashing on my computer. So I uninstalled it and re-installed the stable client. When I reinstalled, I forgot to put my username in. STUPID me!!
Re: 155.247.166.219 rejecting
Join the crowd....fluke76 wrote:And I just realized what happened. Someone had commented above about trying out the Beta client, which ended up crashing on my computer. So I uninstalled it and re-installed the stable client. When I reinstalled, I forgot to put my username in. STUPID me!!
========
DrBB1
DrBB1