• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SoB client stalling!

R

RemyCanad

Golden Member
Well I am having a horrible time with the client. It keeps stalling on all my machines. My rate should be 10M but its only 4!

Does anyone have any info about this?
 
There are a number of people experiencing different problems with the SOB service recently. Could you give more info about the problem? Such as the version of the client you are using, a snippet from your log file when the client dies, is it halting or just going to sleep, is it dying when trying to connect to the server, what flags are you using with the service, etc.

 
I will get this info soon. My local machines are running fine with the client... But the remote ones are not and I will have a guy get me the log files on them.

 
Actually, I just checked and most of my Linux clients that have net access had stalled as well. This client can't recover from a failed connection to the server. :disgust:

The funny this is, that I have never had a stall on clients that run no-net. I think that I may just change all my clients to not submit intermediate blocks. The server can't handle the load, and there is no reason I need to try to connect to the server every 10 minutes anyway.
 
If you run no-net do you have to go to each machine and send each day?

Also I am in the process of changing them all to no submit intermediate blocks. I hope this helps because I am getting frustrated.
 
If you change it to not submit intermediate blocks the machines will submit @ the end of the *WU*...assuming this is how it goes for the service installer as well.
 
Well, it is mostly no-net. I run on a cluster where only one node has net access, but the disks are cross mounted. So for each node that I run on (20 currently) I must

1) from the net node, download a WU, kill client
2) from the work node, start client, no intermediate blocks, terminate after one failed attempt with server
3) keep track of when WU will finish
4) from the net node, send finished WU, get new one
5) rinse, repeat

It takes a good chunk of my time, but for some reason I do it anyway. If the client worked well in SMP mode, I could add another 20 nodes and be up over 15 McEMs/sec. But it doesn't, so oh well.
 
Could this be running on the rack you posted a few weeks back? 🙂

Yeah I have about 80+ P3 800s that I could install it on but if the client will not work it is not worth the effort.
 
Woke up today and found that ALL 6 of my SB clients had been stalled for about 5 hours. :|

I'm trying the no intermittant block thing now, hopefully it will work.
 
Well I found out my friend that set the vast majority of them up did not set it to restart after stalls and such.

He is now reinstalling all of them with the new settings! This should fix our problems. 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top