Old 28th March 2012, 18:25   #1
mcalfin28
Junior Member
 
Join Date: Mar 2012
Posts: 3
DNAS v2 Crashes - DNAS 1.9.8 won't work with YP

I work for Computer Services at Stockton College in NJ. Recently, one of our guys who ran the SHOUTcast server left only for the machine running it to crash a few weeks later.

Long story short, I got dumped on this radio station project and have little to no knowledge about SHOUTcast itself, but I do have good general knowledge of computers/server systems.

Anyway, I need some help keeping this thing up. I had everything up and running properly on the new machine we setup for them... all seems to work well for anywhere from 24 hours to a week, only to end in multiple crashes throughout the day or over the new few days... The sc_serv application seems to randomly crash no matter what we do with it (we tried running sc_serv on a linux virtual machine on the windows box itself, as well as a machine from one of our offices outside the radio station... both would eventually just send out a segmentation fault and shutdown within that random 24hour to one week period). Apparently this was never an issue when the old server was up and running - it ran DNAS 1.9.8 with DSP 1.9.0.

I also tried downgrading to 1.9.8 with DSP 1.9.0, but I keep running into issues with "Invalid Resource Request(/listen.aac)" which appears in my logs whenever anyone tries to connect using the yellowpages. I can't seem to get it up and running using the yellowpages whatsoever with 1.9.8 with either MP3 or AAC encoding.

Any help or insight on how I could get these newer versions running smoothly, or the older version working on yp.shoutcast.com, I'd greatly appreciate it. The department that runs the radio station here at the college is starting to get very frustrated, and I don't blame them... because I am too. I just don't really know what to tell them at this point, as I can't find any solid information on this anywhere online.

If needed, I'll gladly post logs/config files/system info/etc... just ask and it shall be yours!

Thanks in advanced for any help...
mcalfin28 is offline   Reply With Quote
Old 28th March 2012, 19:04   #2
thinktink
Forum King
 
thinktink's Avatar
 
Join Date: May 2009
Location: Somewhere on this planet.
Posts: 2,586
Send a message via Skype™ to thinktink
Wow, a segfault in Windows? Ouch.

Please post your system specs and include any debug logs from the v2 DNAS. The legacy DNAS 1.9.8 isn't supported/developed anymore with the push to switch over to the new v2 DNAS.

Can you check your application logs (from the Control Panel) and see if there's any related errors/warnings?
thinktink is offline   Reply With Quote
Old 28th March 2012, 20:11   #3
mcalfin28
Junior Member
 
Join Date: Mar 2012
Posts: 3
The segfault is actually what the Linux box threw, when using the SHOUTcast DSP for WinAMP as the stream source.

We originally setup the DSP and DNAS on a single GX620 machine and stored it up in the room with the radio station broadcast equipment. This always ended in a good 48-72hour run, followed by sc_serv crashing the next day, sometimes even multiple times throughout the day.... then we'd have another stretch of a good 48hours up to 5 days... followed by more random crashing.

After that got to be far too annoying, we setup a linux virtual machine INSIDE the windows machine up at the radio station HQ using ubuntu server, but that VM threw segmentation faults. We then setup a dedicated ubuntu server box in our offices in computer services which still used the same DSP box up in the radio station to stream to the IP of the linux DNAS box in our offices....

At this point, I don't have a huge collection of logs... which I know I should, but we've been switching around boxes trying to eliminate this problem for months now.

Where we currently stand is we have a single gx620 running windows that has the DSP and DNAS apps running on it. All of our excess gx620s that we can use for this project have the following specs

Pentium D 2.8GHz
1GB RAM
SoundMAX Digital Audio (Currently using Line-In)
Intel 82945G Graphics
80GB HDD

We also have an extra LynxONE sound capture device that we had hooked up to the broadcasting equipment, but we tried removing that to switch to Line-In... which didn't help this problem at all.

I'll turn on debugging right now, and let the server run over night. As soon as it crashes again (which it will...) I will post up those debug logs.

For now... All I can find in the event viewer from sc_serv2 is the following, multiplied by hundreds.... throws these errors every few minutes while it's running.

Quote:
Event Type: Error
Event Source: sc_serv2
Event Category: None
Event ID: 1
Date: 3/22/2012
Time: 11:32:25 PM
User: N/A
Computer: WLFRSHOUTCAST
Description:
2012-03-22 23:32:25 sc_serv2 msg:[DST 24.184.90.28:4196 sid=1] Socket error while waiting to send data. err=Connection reset by peer.(10054)
Quote:
Event Type: Error
Event Source: sc_serv2
Event Category: None
Event ID: 1
Date: 3/23/2012
Time: 1:40:02 AM
User: N/A
Computer: WLFRSHOUTCAST
Description:
2012-03-23 01:40:02 sc_serv2 msg:[SRC 108.25.185.226:50041] Timeout waiting for data (1332481202 1332481172[30] )
These seem to be somewhat normal... the only other thing I can find that might be of help is this

Quote:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 3/23/2012
Time: 4:15:36 PM
User: N/A
Computer: WLFRSHOUTCAST
Description:
Faulting application sc_serv.exe, version 29.7.31.2011, faulting module msvcr90.dll, version 9.0.21022.8, fault address 0x000302fd.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 73 63 5f ure sc_
0018: 73 65 72 76 2e 65 78 65 serv.exe
0020: 20 32 39 2e 37 2e 33 31 29.7.31
0028: 2e 32 30 31 31 20 69 6e .2011 in
0030: 20 6d 73 76 63 72 39 30 msvcr90
0038: 2e 64 6c 6c 20 39 2e 30 .dll 9.0
0040: 2e 32 31 30 32 32 2e 38 .21022.8
0048: 20 61 74 20 6f 66 66 73 at offs
0050: 65 74 20 30 30 30 33 30 et 00030
0058: 32 66 64 0d 0a 2fd..
Hopefully some of this might help... If not, I'll have some debug logs ready by tomorrow.
mcalfin28 is offline   Reply With Quote
Old 29th March 2012, 11:54   #4
DrO
Winamp Team
 
DrO's Avatar
 
Join Date: Sep 2003
Posts: 26,231
if the windows version is crashing then it's most likely related to the known issue which can cause it to crash with some invalid client handling in the public build.

for the linux version, the same applies from the windows version but also some metadata can cause it to crash.


the 10054 error is normal and is usually followed by a client disconnect message - it's something that shouldn't have been enabled other than for debugging (as was changed in the internal builds).


the Timeout waiting for data error indicates a lack of input audio data from the DSP. as you seem to be trying to use the v1 Source DSP, then that would make sense since it cannot keep the connection alive if there is no input audio - this is one of the things of the supported v2 Source DSP.


as the Windows build generally has been more stable compared to the linux builds, i need to know if you want a 32-bit or 64-bit build to try out. also i will provide you with a newer build of the Source DSP but you will need to make sure that you are using the current Winamp release (v5.623 at the time of this reply).

-daz

If you have issues with Winamp or still want to get it, ensure
you get v5.666 build 3516 and the required plug-in updates
DrO is offline   Reply With Quote
Old 29th March 2012, 17:47   #5
mcalfin28
Junior Member
 
Join Date: Mar 2012
Posts: 3
If I could get a 32bit build to try and attempt to fix this problem, that would be great!

I have infact used v1 mode on the DSP as an attempt to stop this thing from going down, so that may be why those are showing up. I've got the server up and running again on v2 with debugging enabled, and it's been up since last night when I wrote the last post... Probably just asking to jynx myself by saying that though.

EDIT: And yes, I am using the latest version of winamp. Whatever you got I am willing to try.
mcalfin28 is offline   Reply With Quote
Old 29th March 2012, 19:41   #6
DrO
Winamp Team
 
DrO's Avatar
 
Join Date: Sep 2003
Posts: 26,231
check your pm.

-daz

If you have issues with Winamp or still want to get it, ensure
you get v5.666 build 3516 and the required plug-in updates
DrO is offline   Reply With Quote
Old 8th September 2013, 17:43   #7
Arsimael_
Junior Member
 
Join Date: Aug 2012
Posts: 12
Hello,
I know this thread is OLD! But I still have the same error. Only on Linux.

sc_serv is crashing randomly. I have 2 server set up and BOTH crash at the SAME TIME.

The Metadata is clean of any non ASCII Signs. No ()[]{}*:öäüß?\!"§$%&/

I am nearly done with it and pissed because I can do what I want and it still crashes.

NEED HELP PLEASE!
Arsimael_ is offline   Reply With Quote
Old 9th September 2013, 10:03   #8
DrO
Winamp Team
 
DrO's Avatar
 
Join Date: Sep 2003
Posts: 26,231
the last few lines of the log (though is generally better with all of the debug logging enabled) when the issue happens may help to determine the cause of the crash, unless it's from one of the known issues from http://forums.winamp.com/showthread.php?p=2790357#known

If you have issues with Winamp or still want to get it, ensure
you get v5.666 build 3516 and the required plug-in updates
DrO is offline   Reply With Quote
Old 19th September 2013, 05:24   #9
Arsimael_
Junior Member
 
Join Date: Aug 2012
Posts: 12
Here. Last 50 lines of the logfile I have until the crash: (debug)

2013-09-07 22:38:45 D msg:[MICROSERVER] Connection received from 87.106.215.176:38468
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 0 amt=4
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 1 amt=3
2013-09-07 22:38:45 D msg:[THREADRUNNER] Adding microConnection to thread 1
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 0 amt=4
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 1 amt=4
2013-09-07 22:38:45 D msg:[THREADRUNNER] Adding protocol_HTTPStyle to thread 0
2013-09-07 22:38:45 D msg:[THREADRUNNER] Removing microConnection from thread 1
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 0 amt=5
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 1 amt=3
2013-09-07 22:38:45 D msg:[THREADRUNNER] Adding protocol_admincgi to thread 1
2013-09-07 22:38:45 I msg:[ADMINCGI] Title update [The White Stripes - Seven nation army]
2013-09-07 22:38:45 D msg:[THREADRUNNER] Removing protocol_admincgi from thread 1
2013-09-07 22:38:45 D msg:[THREADRUNNER] Removing protocol_HTTPStyle from thread 0
2013-09-07 22:38:45 D msg:[MICROSERVER] Connection received from 178.2.145.111:1408
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 0 amt=4
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 1 amt=3
2013-09-07 22:38:45 D msg:[THREADRUNNER] Adding microConnection to thread 1
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 0 amt=4
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 1 amt=4
2013-09-07 22:38:45 D msg:[THREADRUNNER] Adding protocol_HTTPStyle to thread 0
2013-09-07 22:38:45 D msg:[THREADRUNNER] Removing microConnection from thread 1
2013-09-07 22:38:45 D msgrotocol_shoutcast2Client
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 0 amt=5
2013-09-07 22:38:45 D msg:[THREADRUNNER] thread 1 amt=3
2013-09-07 22:38:45 D msg:[THREADRUNNER] Adding protocol_shoutcast2Client to thread 1
2013-09-07 22:38:45 D msg:state_AttachToStream
2013-09-07 22:38:45 D msg:[DST 178.2.145.111:1408 sid=1] Sending [HTTP/1.1 200 OK
Server:Ultravox/2.1 SHOUTcast v2.0.0.29
Content-Type:misc/ultravox
icy-pub:1
Ultravox-SID:1
Ultravox-Bitrate:128000
Ultravox-Title:Vox Noctem - Die Stimme der Nacht
Ultravox-Genre:Goth
Ultravox-URL:http://www.voxnoctem.de
Ultravox-Max-Msg:16377
Ultravox-Class-Type:7000

]
2013-09-07 22:38:45 I msg:[DST 178.2.145.111:1408 sid=1] SHOUTcast 2 client connection accepted. WinampMPEG/5.62, Ultravox/2.1
2013-09-07 22:38:45 D msg:state_InitiateStream
2013-09-07 22:38:45 D msg:resetReadPtr readPtr=1562330955 amt=299528
2013-09-07 22:38:45 D msg:state_InitiateStream sending metadata Z9p<?xml version="1.0" encoding="UTF-8" ?>
<metadata>
<TIT2>David Bowie - Valentines Day</TIT2>
</metadata>

2013-09-07 22:38:45 D msg:state_SendCachedMetadata
2013-09-07 22:38:45 D msg:[THREADRUNNER] Removing protocol_HTTPStyle from thread 0
(CRASHED)
Arsimael_ is offline   Reply With Quote
Old 29th September 2013, 18:09   #10
Arsimael_
Junior Member
 
Join Date: Aug 2012
Posts: 12
No Idea?
Arsimael_ is offline   Reply With Quote
Old 29th September 2013, 18:20   #11
DrO
Winamp Team
 
DrO's Avatar
 
Join Date: Sep 2003
Posts: 26,231
(hadn't seen there was a post after i'd last replied). it's due to incorrect error handling related to the metadata issues as noted by point #4. only an updated DNAS can resolve the issue.

If you have issues with Winamp or still want to get it, ensure
you get v5.666 build 3516 and the required plug-in updates
DrO is offline   Reply With Quote
Old 1st October 2013, 02:17   #12
Arsimael_
Junior Member
 
Join Date: Aug 2012
Posts: 12
Ok. I removed all "spechial Caracters" ( "#`´ ' {}|<>&%$ ) from the ID3-Tags and Filenames.
I hope this helps until the new version gets released.
Arsimael_ is offline   Reply With Quote
Old 1st October 2013, 02:26   #13
DrO
Winamp Team
 
DrO's Avatar
 
Join Date: Sep 2003
Posts: 26,231
you didn't have special characters in the log posted above. the crash with that log is related to but is not specifically due to those characters (though if you've been able to clean up tags with then that would explain some of the crashes) and is due to something being expected and it not and that than cause an error handler to be incorrectly passed to a kill action.

If you have issues with Winamp or still want to get it, ensure
you get v5.666 build 3516 and the required plug-in updates
DrO is offline   Reply With Quote
Old 2nd October 2013, 01:01   #14
Arsimael_
Junior Member
 
Join Date: Aug 2012
Posts: 12
Ok, this means if I use shoutcast2 I can't be sure that the stream runns smooth and without crashes. It can happen anytime that the stream just stops, throws all listeners awy and I have to restart it.
And If I use Shoutcast One I am not listed on shoutcast.com.

Is this a suitable describtion of the situation?
Arsimael_ is offline   Reply With Quote
Old 2nd October 2013, 09:42   #15
DrO
Winamp Team
 
DrO's Avatar
 
Join Date: Sep 2003
Posts: 26,231
the new v2 DNAS is currently under going final testing at the moment. once that is completed and i've updated enough of the documentation to be useful so there's a reference to all of the new features (within the next day or two), then you will be able to replace the current DNAS program file with the new one and that should be the issue resolved (based on what i've seen and fixed over the last 2yrs of all of the metadata fixes that have been put in place since the last public release).

If you have issues with Winamp or still want to get it, ensure
you get v5.666 build 3516 and the required plug-in updates
DrO is offline   Reply With Quote
Reply
Go Back   Winamp Forums > SHOUTcast > SHOUTcast Technical Support

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump