Streamerp2p Forum

This morning, for some unknown reason, streamer crashed - no error message, it just locked up. Oddcast couldn't connect, and no stream was being sent at all. I had to use Task Manager to kill it.

When I restarted it, Oddcast connected immediately, and the receiver I had running on another system had audio within about a minute - with the normal 3-5 second delay between the playout and the receiver.

Radio X T Z is the station...

It's been running continuously - other than when the whole system went down during a storm - since installation.. is there something there that needs a shutdown every couple of weeks? Right now, it's running on a Win2KSP4 box along with the automation system... I'm going to move it to a dedicated box (also Win2K) to ease the load on the automation computer - and to have a backup connection, if I can manage it somehow....

If streamer crashes it dumps a error.txt to the streamer installation folder. If it freeze complete it's possible the error.txt isn't there. If there is one send it to the email address given to you in the error dialog.

Normaly not. Don't know if win2k needs some special tweeks. I don't use it anymore since two years now. Streamer is running pretty stable for me on win2k and winXP.

Nope;

No error dialog, and no error.txt file

Win2K SP4 is supposed to be the most stable of the NT platforms; I've had the other programs running for months on end... I did have the entire computer hang once when the LAN switch got disconnected by accident, but that wasn't the computer's fault...

Puzzled...

If it wasn't for the 4-5 second echo and buffer delay, I'd monitor the stream full time...

<sigh>

I'll keep an eye on it...

It locked up again this morning - no error message, and no .txt file...

I've got another system ready to go that will be dedicated to JUST the stream...

I'll switch it today, and we'll see if that fixes it.

I don't have a second ISP yet, so if the problem is bandwidth... (I have the stream BW set to 128 kb, which should be plenty for a 64 kb ogg stream....)

This sounds like the old TcpIp Stack Handle “Failure to release” problem.

Basically what happens is, that tcpip handle’s are opened
and in certain cercantance’s , never released.

This continues until the situation is reached were windows has no more free TCPIP handles

Then Windows Freeze’s

Bad news is::
This has been present in very version of MS Windows,
since Internet/TCPIP support was added ( to Windows 3.11 )


Sadly there is no fix, ( if there was Id assume Microsoft would have fixed it by now )

Sadly it is not possible to predict how frequently this problem is likely to reach critical

The best option is to reboot before it happens (either by schedule, or manual restart)


Some broadcasters will discover that they cant run continuously for many months
while others will require to reboot every week/fortnite.

PS: my system, both my broadcast feed, and remote server,
are rebooted once a week (05:45 utc Monday), for esactly this reason !

PPS: quote RTF2 "I had to use Task Manager to kill it"
if this was possible, then the TcpIp Stack Handle problem
was NOT the clause of there crash in that insance
as windows remained functional.

I have experienced streamer freezing for no apparent reason (without writing "error.txt")
I suspect it was claused by a corrupted support file !
The file being danaged when windows had previously frozen
due to the "TcpIp Stack Handle problem"