ZZZZZZZTTTTTTTTT!!!!!!...... steamcast.

webranger · Post by **webranger** » Wed May 04, 2005 12:33 am

I get normal operation until steamcast dies with this error.

It seems to happen at random, anywhere between an hour and 8.

---c---
[date]<69.64.36.158> Request:/admin.cgi <UA: Mozilla/4.0<compatible; Shoutcast nsv Source v1.0.0/posix>>
[date]<Status>Nodes:20 Unique:20 Sources:1
---c---

Pfft!.....

. The IP above is the IP of the linux box running sc_nsv. Steamcast is running on a windows (2003 server) box you see in your steamcast YP, if it hasn't crashed again

.

Any ideas?.
Kevin

Post by **Jay** » Wed May 04, 2005 9:45 am

are you running it in any particular compatibility modes? Do you get alot of rejected traffic when the crash occurs (lots of people hitting a full server etc)?

The event displayed should not be a crash causing event, something you might also try is disabling all logging and see if it no longer crashes. Unfortunately I don't have access to a 2k3 machine yet. Once I get access to one I will see if I can duplicate these issues.

webranger · Post by **webranger** » Wed May 04, 2005 1:18 pm

Nope, it's not getting hammered. When it crashes next time, I'll try your suggestion.

I found out something interesting. Running 64 slots uses less monthly throughput than running 40. If you think about it, you'd know why.

Maybe I could get you access to a 2003 box, if you are interested in messing around with this.

Kevin

Post by **Jay** » Wed May 04, 2005 10:00 pm

sure, if you want to help us getting these problems worked out, access to a win 2k3 server would be a quick way to get that done.

webranger · Post by **webranger** » Wed May 04, 2005 11:37 pm

Well, here's a clue to the problem. This has been up 24 hours and no crash.

I redirected the standard output of steamcast to a file, mainly by accident. No explosions.

It looks like logging to the desktop is what is causing the problem for some reason.

Maybe something with rdp is something that it doesn't like. But it's cool, it works. Some software does blow when you run it on the remote desktop.

Cool.

Post by **Jay** » Thu May 05, 2005 1:01 am

hmm, interesting, well keep me informed of the situation.

webranger · Post by **webranger** » Fri May 06, 2005 1:50 pm

It is a problem with console logging. I think just too heavy under Windows.

Post by **Jay** » Fri May 06, 2005 2:37 pm

yes, I need to go through and do some heavier tests of the logging capabilities under multiple platforms. I think that once I get the GUI admin interface going this may become less of an issue as console logging won't be neccessary.

Limedrink · Post by **Limedrink** » Fri Oct 14, 2005 9:44 pm

I am experiencing a similar problem under Fedora Core 1:

http://forums.radiotoolbox.com/viewtopi ... =4455#4455

Limedrink.