sc_serv XML output stops after running for a while

[Cabloo]

I have an sc_serv setup using v2 Build 29 (July 31st 2011?). I also tried with various previous versions.

I'm using sc_trans to broadcast to sc_serv in a continuous loop. It seems to me like the radio fails at ~2:23 AM EST every day (but I'm not entirely sure of that). Audio continues to stream with no interruption, but the XML information on port 8000 fails pretty badly.

http://radio.gamevue.net/
(Note: it's streaming @ 320kbps MP3)

This is the system I've been working very hard on (if you couldn't tell) but I can't seem to get past this one error.

So far it logs all the songs and DJ interactions in a DB. It does this by running a cron job every 2 seconds that calls

PHP Code:

file_get_contents( 'http://username:password@127.0.0.1:8000/admin.cgi?mode=viewxml&page=5&sid=1' ) 


which should give me song info under SHOUTCASTSERVER->SONGMETADDATA. This does work for a while, until randomly it crashes. There's nothing weird at that point in the logs as far as I can tell.

The output of the XML file is

code:
<SHOUTCASTSERVER>

     <SONGMETADATA/>

</SHOUTCASTSERVER>

It works perfectly and then all song data stops being sent to XML.

logs from sc_serv are available at radio.gamevue.net/logs/sc_*.log
Logs copied:
sc_serv.log
sc_serv_1.log
sc_serv_2.log
sc_serv_3.log
sc_serv_4.log
sc_serv_5.log
sc_w3c.log

e.g. http://radio.gamevue.net/logs/sc_serv_1.log

The sc_serv configuration is available at http://radio.gamevue.net/logs/sc_serv_basic.conf (there were no other included configs)


I'm not sure what the problem is here but I've been having it for a while.
Also, I'm fairly certain that the problem is not related to sc_trans because all it takes is one reset of sc_serv to fix itself (unless sc_trans is sending it music w/ weird characters, which I doubt because I've tried removing characters).

I'll do anything within my power to get this fixed this weekend. I'm very good with PHP, fairly confident with Linux, and I understand some C/C++ (enough to compile and troubleshoot most of the time).

Hopefully I've provided all the necessary resources, and any help is much appreciated! I'd be happy to provide any extra information. I'm decently experienced with most of this stuff so feel free to talk technical.

Much thanks,
Zane "Cabloo" Hooper