Shoutcast DNAS crashing every morning

[stephen02]

hello all,

Thanks for any help you can provide on the matter. For some reason my stream crashes around the early morning hours. Its been doing it for about a month now, and i can't find the problem. What is weird is only one of our streams is crashing.

This is the last thing the sc_serv.log has for the last couple of days:

12-02-2013:

PHP Code:

2013-12-02 14:25:49    I    msg:***91;YP2***93; Connecting to yp.shoutcast.com
2013-12-02 14:26:51    I    msg:***91;DST 54.254.199.44:57312 sid=1***93; SHOUTcast 1 client connection accepted. Java/1.6.0_24
2013-12-02 14:26:51    E    msg:***91;DST 54.254.199.44:57312 sid=1***93; Socket error while waiting to send data. err=Software caused connection abort.(10053)
2013-12-02 14:26:51    I    msg:***91;DST 54.254.199.44:57312 sid=1***93; SHOUTcast 1 client connection closed (0 seconds) ***91;Bytes: 265386***93; Agent: `Java/1.6.0_24'
2013-12-02 14:26:52    I    msg:***91;DST 54.254.199.44:57321 sid=1***93; SHOUTcast 1 client connection accepted. 
2013-12-02 14:26:56    E    msg:***91;DST 54.254.199.44:57321 sid=1***93; Socket error while waiting to send data. err=Connection reset by peer.(10054)
2013-12-02 14:26:56    I    msg:***91;DST 54.254.199.44:57321 sid=1***93; SHOUTcast 1 client connection closed (4 seconds) ***91;Bytes: 302171***93; Agent: `'
2013-12-02 14:27:02    I    msg:***91;DST 54.254.199.44:57380 sid=1***93; SHOUTcast 1 client connection accepted. Lavf53.24.0
2013-12-02 14:27:06    E    msg:***91;DST 54.254.199.44:57380 sid=1***93; Socket error while waiting to send data. err=Connection reset by peer.(10054)
2013-12-02 14:27:06    I    msg:***91;DST 54.254.199.44:57380 sid=1***93; SHOUTcast 1 client connection closed (4 seconds) ***91;Bytes: 327276***93; Agent: `Lavf53.24.0'
2013-12-02 14:27:40    E    msg:***91;SRC 54.254.199.44:57418***93; Timeout waiting for data (1386023260 1386023230***91;30***93; )
2013-12-02 14:27:45    I    msg:***91;DST 54.254.199.44:57601 sid=1***93; SHOUTcast 1 client connection accepted. NSPlayer/4.1.0.3856
2013-12-02 14:27:45    E    msg:***91;DST 54.254.199.44:57601 sid=1***93; Socket error while waiting to send data. err=Connection reset by peer.(10054)
2013-12-02 14:27:45    I    msg:***91;DST 54.254.199.44:57601 sid=1***93; SHOUTcast 1 client connection closed (0 seconds) ***91;Bytes: 265402***93; Agent: `NSPlayer/4.1.0.3856'
2013-12-03 06:32:05    E    msg:***91;SRC 127.0.0.1:65313 sid=1***93; Timeout waiting for data (1386081125 1386023273***91;57852***93; )
2013-12-03 06:32:05    E    msg:***91;DST 151.151.109.21:6251 sid=1***93; Timeout waiting to send data (1386081125 1386023273***91;57852***93; ) 


12-02-2013

PHP Code:

2013-12-02 00:09:33    I    msg:***91;YP2***93; Connecting to yp.shoutcast.com
2013-12-02 00:09:46    E    msg:***91;SRC 54.254.199.44:51799***93; Timeout waiting for data (1385971786 1385971756***91;30***93; )
2013-12-02 00:10:01    I    msg:***91;DST 54.254.199.44:52062 sid=1***93; SHOUTcast 1 client connection accepted. NSPlayer/4.1.0.3856
2013-12-02 00:10:01    E    msg:***91;DST 54.254.199.44:52062 sid=1***93; Socket error while waiting to send data. err=Connection reset by peer.(10054)
2013-12-02 00:10:01    I    msg:***91;DST 54.254.199.44:52062 sid=1***93; SHOUTcast 1 client connection closed (0 seconds) ***91;Bytes: 265406***93; Agent: `NSPlayer/4.1.0.3856' 


12-01-2013

PHP Code:

2013-12-01 04:21:45    E    msg:***91;DST 88.77.129.91:49959 sid=1***93; Socket error while waiting to send data. err=Software caused connection abort.(10053)
2013-12-01 04:21:45    I    msg:***91;DST 88.77.129.91:49959 sid=1***93; SHOUTcast 1 client connection closed (7662 seconds) ***91;Bytes: 122564036***93; Agent: `iTunes/11.1.2 (Macintosh; OS X 10.6.8) AppleWebKit/534.59.10'
2013-12-01 04:21:46    I    msg:***91;DST 54.254.153.139:39761 sid=1***93; SHOUTcast 1 client connection accepted. Java/1.6.0_24
2013-12-01 04:21:46    E    msg:***91;DST 54.254.153.139:39761 sid=1***93; Socket error while waiting to send data. err=Connection reset by peer.(10054)
2013-12-01 04:21:46    I    msg:***91;DST 54.254.153.139:39761 sid=1***93; SHOUTcast 1 client connection closed (0 seconds) ***91;Bytes: 262143***93; Agent: `Java/1.6.0_24'
2013-12-01 04:21:47    I    msg:***91;DST 54.254.153.139:39772 sid=1***93; SHOUTcast 1 client connection accepted. 
2013-12-01 04:21:50    E    msg:***91;DST 54.254.153.139:39772 sid=1***93; Socket error while waiting to send data. err=Connection reset by peer.(10054)
2013-12-01 04:21:50    I    msg:***91;DST 54.254.153.139:39772 sid=1***93; SHOUTcast 1 client connection closed (3 seconds) ***91;Bytes: 300922***93; Agent: `'
2013-12-01 04:21:54    I    msg:***91;DST 54.254.153.139:39809 sid=1***93; SHOUTcast 1 client connection accepted. Lavf53.24.0
2013-12-01 04:21:58    E    msg:***91;DST 54.254.153.139:39809 sid=1***93; Socket error while waiting to send data. err=Connection reset by peer.(10054)
2013-12-01 04:21:58    I    msg:***91;DST 54.254.153.139:39809 sid=1***93; SHOUTcast 1 client connection closed (4 seconds) ***91;Bytes: 308022***93; Agent: `Lavf53.24.0'
2013-12-01 04:21:59    I    msg:***91;YP2***93; Connecting to yp.shoutcast.com
2013-12-01 04:22:35    E    msg:***91;SRC 54.254.153.139:39870***93; Timeout waiting for data (1385900555 1385900525***91;30***93; )
2013-12-01 04:22:45    I    msg:***91;DST 54.254.153.139:40088 sid=1***93; SHOUTcast 1 client connection accepted. NSPlayer/4.1.0.3856
2013-12-01 04:22:45    E    msg:***91;DST 54.254.153.139:40088 sid=1***93; Socket error while waiting to send data. err=Connection reset by peer.(10054)
2013-12-01 04:22:45    I    msg:***91;DST 54.254.153.139:40088 sid=1***93; SHOUTcast 1 client connection closed (0 seconds) ***91;Bytes: 262053***93; Agent: `NSPlayer/4.1.0.3856
2013-12-01 07:22:25    E    msg:***91;DST 91.178.224.3:50867 sid=1***93; Timeout waiting to send data (1385911345 1385900577***91;10768***93; ) 


Some of the last ip address are listed as Amazon Technologies.
any ideas as to why my stream may be shutting down.

[DrO]

i assume that's a v2 based DNAS? if so update to the v2.2.1 release (link in stick thread) and see if that improves things.

[stephen02]

Yes sir, trying to complete the process now... if i read correctly the doc files i can just place the files in the existing folder and it will overwrite what it needs?

Thanks.

[stephen02]

Originally Posted by DrO

i assume that's a v2 based DNAS? if so update to the v2.2.1 release (link in stick thread) and see if that improves things.

Yes sir, Currently working on the upgrade... If i read the upgrade instructions correctly i can just paste the new folder in the old folders place. Is that correct.

Thanks.

[stephen02]

i just had a crash and happen to see it. Now it won't let me restart it at all.
Now my stream is down completely..
The Below images are of the new DNAS v2.2.



Since those stopped working i brought up my back up of v2.0 temporaryly till i can get v2.2 fixed. Just as an FYI here is an image of the event logger on v2.0 error.

[stephen02]

I am still having issues with this.. anybody able to help me?

[DrO]

the crash details in the screenshots don't give me much to work with. i'd really need something like the actual dmp file to attempt to work out what's going on. though based on the first screenshot, that looks like it crashed on loading which is strange.

so if a dmp file can be obtained than that would be most helpful as well as a copy of the config file(s) being used without authhash and passwords in them.

[stephen02]

Originally Posted by DrO

the crash details in the screenshots don't give me much to work with. i'd really need something like the actual dmp file to attempt to work out what's going on. though based on the first screenshot, that looks like it crashed on loading which is strange.

so if a dmp file can be obtained than that would be most helpful as well as a copy of the config file(s) being used without authhash and passwords in them.

That is really the thing. It worked for about two days then crashed like v2.0 did. Then i tried to start it up and it keep crashing on load. I didn't redo the authash on this server because it was all the same info and just an update to v2.0 not a fresh install. I assume i didn't have to but maybe i am incorrect on doing so.

here is the attachments, not much to look at since it crashed and i tried to restart it several times which erases the 2 days of data.

[stephen02]

I just tried to get the v2.2 working and this time it allowed me to. I will let it run for a couple of days and see if it crashes again. But this time i will backup the sc_serv.txt files before trying to restart it.

[stephen02]

OK So my server just shut down from running for the last three days. Here are the logs that i can find and that were updating for those 3 days.

Thanks for the help.

[DrO]

sadly that doesn't give me much to work with other than it might be something around the time of a title update since that's the last thing. though as it shows you're running on an 8 core setup, it could be a threading issue, and might be an idea to try setting cpucount lower to see if that helps.

however, it'd be better to have a crash dump file to work with. you can use http://forums.winamp.com/showpost.ph...86&postcount=6 (and change the Winamp paths to those of the DNAS) which should then be able to provide me something which is a bit more helpful to be able to determine the cause of the crash.