SoB error - "server busy" for the last N hours

[VirtualLarry]

Is it just my rig, or is the SoB work server semi-permanently busy?

 

[TAandy]

sorry, no

 

[SlowBones]

Yes, approximately. Under Vista, I get no message, but I'm computing and my stats aren't ticking up. Looking at the performance monitor, my down-tick is longer than usual as if there were a server issue (a network / dialup failure is actually shorter).

I *did* finish a WU today, so that may be part of it.

I think this happened briefly about 4 or 5 days ago; see the week-long stats thread.

 

[petrusbroder]

The error is probably not with SoB. It seems that the IP-addy for the default server (sb.pns.net) is not correct. However you can download the results and get new WUs from the server "www.seventeenorbust.com".
Here is a "How to":

Caution: for this fix to work you need to edit the registry. If you mess up the registry, your comp may not work properly and you may loose data and time. Therefore: if you do not know what to do and how to edit the keys in the registry, do not do it.
If you mess up, the responsibility is yours.

Read the whole How-to before doing any changes to the registry. If you are not sure how to do this don't. The addy will correct it self after some time and it is not worth the risk.

A. Before doing the following shut down sb.exe either by clicking first the stop-button and then the exit button or - if you have installed it as a service - by stopping it using the service manager.

You can not change the addy using sb.exe config option because the server addy is too long (I have tried it). therefore:

B. Change the sb.exe-keys in the registry:

1. Go to the "Run"-box and start "Regedit".
2. Search (by going to the Edit-menu and choosing "search") for the string sb.pns.net. It should be in the key "server".
3. Click on the word "server", and a editing box containing the string sb.pns.net should open.
4. Replace the string sb.pns.net with the string www.seventeenorbust.com.
5. Close "regedit".

C. Start the sb.exe or start the service (using the service manager) or restart the computer.

D. Check that the program connects to the server: click the config button and see what server is registered or wait until the program has crunched a block and sent it away ...

Read a little bit more about this here: http://www.free-dc.org/forum/s...8298f5a2b318fe&t=13309

 

[Spacehead]

Just got home & read this. No connection here either.

There is a thread on the SOB forums though with a workaround(i guess... haven't tried it)
http://www.free-dc.org/forum/showthread.php?t=13309

 

[petrusbroder]

Originally posted by: Spacehead
Just got home & read this. No connection here either.

There is a thread on the SOB forums though with a workaround(i guess... haven't tried it)
http://www.free-dc.org/forum/showthread.php?t=13309

LoL, what a few seconds can do - above is the workaround!

 

[Spacehead]

Originally posted by: petrusbroder

Originally posted by: Spacehead
Just got home & read this. No connection here either.

There is a thread on the SOB forums though with a workaround(i guess... haven't tried it)
http://www.free-dc.org/forum/showthread.php?t=13309

LoL, what a few seconds can do - above is the workaround!

I really love my dialup connection


I assume, if you're using SBQueue you can correct this by going to "Options"-->"Set Remote Server" & change it there???

 

[petrusbroder]

Yupp, you can ...

 

[biodoc]

Originally posted by: Spacehead
Just got home & read this. No connection here either.

There is a thread on the SOB forums though with a workaround(i guess... haven't tried it)
http://www.free-dc.org/forum/showthread.php?t=13309

Same problem with me too. www.seventeenorbust.com does not "fit' in the config window for the windows version so I did a tracert on it and came up with an IP address of 69.9.160.186

I plugged the IP address instead.


I rebooted and now am communicating with the server. I hope this is a "permanent" fix

 

[SlowBones]

Can I assume this problem will correct itself in a short number of days?

I don't want to mess with the registry in Vista. If I update the SoB GUI version in my admin account, somehow I doubt it will flow to the service.

<what, there's no emoticon with steam coming out of the ears?!>

 

[caferace]

Can't you just add an entry in your HOSTS file? No registry change needed...

-jim

edit:

HOSTS file change generic: http://help.hardhathosting.com/question.php/11
HOSTS (or LMHOSTS) file change Vista: http://support.microsoft.com/kb/923947

 

[IJump]

Man, I hope this get resolved in the next couple of days (or sooner). I won't be back to work until next Tuesday... ugh. Extremely low production for 4 days!!!

Hopefully I have enough work to get my crunchers through the time....

 

[Rudy Toody]

Thanks for the registry fix, Peter!

I had fixed my 2 linux .conf files and was trying to remember what to use to get the IP address from the domain name so I could fix the WinXP service. I'd forgotten about tracert.

I'm golden, now!

 

[winr]

Hey Peter...it worked for me on my single install.

On my PC, XP PRO, it shows "find" instead of "search"

The string "sb.pns.net" was in the key "serv_addr", I replaced "sb.pns.net" with "www.seventeenorbust.com, restarted SOB and it connected...yay!!!


Now I am going to try my service install on my dual core.

EDIT:
Cool, it worked on my dual core, it also worked on my single core running Windows 98 SE.

Thanks.

 

[nefariouscaine]

Thanks for the work around - i gotta edit the reg keys of a few comps on monday

boy do I feel bad for IJump - I couldn't imagine having to edit the keys for a few labs

 

[petrusbroder]

It is supposed to fix itself - but that can sometimes take a few days.
If there is an error on one of the DNS servers, that that error is propagated to other servers (when updating their whois-databases). When the error is corrected it takes a few days before all DNS-servers have the new IP-numbers in their caches ...

 

[Insidious]

Will we need to re-edit our registry when it does get corrected on their end?

-Sid

 

[PeterN]

Originally posted by: nefariouscaine
Thanks for the work around - i gotta edit the reg keys of a few comps on monday

boy do I feel bad for IJump - I couldn't imagine having to edit the keys for a few labs

Luckily he is using the SBQueue for all his clients. With that you can get new work units by using www.seventeenorbust.com as server. That way he only needs to get them with two queues, but it requires him to be physically there unless he has remote access to his SBQueue servers.

 

[PeterN]

Originally posted by: Insidious
Will we need to re-edit our registry when it does get corrected on their end?

-Sid

Nah, the sb.pns.net normally also refers to the same servers, so it is allright to leave all the changed settings. They all point to the same location.

 

[Insidious]

Originally posted by: PeterN

Originally posted by: Insidious
Will we need to re-edit our registry when it does get corrected on their end?

-Sid

Nah, the sb.pns.net normally also refers to the same servers, so it is allright to leave all the changed settings. They all point to the same location.

Thanks Peter

Chuggin' along here good now thanks to the help on this.

Now, does anyone have a workaround for a retarded little kitten that seems to feel it is her responsibility to pull on every wire comming out of the back of these interesting warm boxes?

:laugh:

 

[SlowBones]

Thanks caferace for reminding me about the hosts file, and that link for Vista sure was handy. I only use it every few years.

Life is good!

 

[NicColt]

Here's what I think happened.

sb.pns.net was doing the double checking and ran out of WU to check, (in other words there are no more double checking WU to be done) but your client's are/were able to send the completed WU back to sb.pns.net. Once the clients completed the WU however it was simply unable to retrieve new WU

If/when you change over to www.seventeenorbust.com it's now doing the normal WU without the double checking. my cEMs/sec are back to what they were before the double checking.

I'm sure they are going to fix as soon as they can.

Also this is where the Queue comes in handy. If you have a queue all you need to do is change the remote server to seventeenorbust.com and restart the process by Start - Programs - Administrative Tools - Component Services - Services(Local) and right click on the Seventeen or bust process and Restart. Or reboot the computer

Originally posted by: Insidious
Will we need to re-edit our registry when it does get corrected on their end?
-Sid

No you don't need to, they request you to use the sb.pns.net but you don't have to.
But the thing is that if in the future we goto double checking again the reverse will happen, seventeenorbust.com will run out of WU and sb.pns.net will be the main one.

 

[RaySun2Be]

Man, I wish I had seen this a lot earlier!

Thanks for the info though. 1 more PC to update and I'm back in business.

 

[NicColt]

I may have been wrong, it now seems that there is a DNS issue. Even with a dns issue the queue is able to complete the WU and hold it until it can connect. I thought for sure that it was submitting the work to sb.pns.net block by block. Oh well.

BTW if we are back to normal sob crunching we should be able to see some pretty high numbers. Once the double checking WU's complete.

 

[RaySun2Be]

Originally posted by: IJump
Man, I hope this get resolved in the next couple of days (or sooner). I won't be back to work until next Tuesday... ugh. Extremely low production for 4 days!!!

Hopefully I have enough work to get my crunchers through the time....

What, no remote administration setup? :Q

We can VPN into the network, then RDP to the server. Domain admins cannot use RDP, we have to use our own user id for tracking/security purposes.

Comes in very handy, except when a server locks up and no remote tools will work, like today. :|

Oh well, we can let the TSO get a bit ahead.