Search found 4 matches
- Wed Apr 22, 2009 8:22 pm
- Forum: Issues with a specific server
- Topic: 171.64.122.139
- Replies: 64
- Views: 15332
Re: 171.64.122.139
Just to update again. Of the remaining 4 uniprocessor clients which were unable to connect I stopped the processes, reconfig'd them to not use advanced methods, small packet size and 800mb memory available and they were all able to pull work (for now). Instead of the IP in question they pulled from ...
- Wed Apr 22, 2009 1:59 pm
- Forum: Issues with a specific server
- Topic: 171.64.122.139
- Replies: 64
- Views: 15332
Re: 171.64.122.139
Hey bruce and toTOW, Came in this morning and had 6 of my uniprocessor clients waiting for work. I can provide snippets of the FAH logs but they all look identical to the one I posted before. 2 of the clients were windows, the other 4 were Linux. The advanced methods work around managed to get me wo...
- Wed Apr 22, 2009 12:49 am
- Forum: Issues with a specific server
- Topic: 171.64.122.139
- Replies: 64
- Views: 15332
Re: 171.64.122.139
I don't suppose there's some switch I can use at the command line to manually specify a working server is there? No. The Pande Group assigns various work server based on scientific need. In this case, server 171.64.122.139 has an exceptionally high net load, but it's successfully distributing a lot...
- Tue Apr 21, 2009 7:41 pm
- Forum: Issues with a specific server
- Topic: 171.64.122.139
- Replies: 64
- Views: 15332
Re: 171.64.122.139
Still getting a ton of the following from at least 3 different workstations. I have tried every combination of work unit size and advanced methods flags possible as well as upping the ram limit to 1gb for the client without success. I don't suppose there's some switch I can use at the command line t...