server 2008 R2 64bit & shoutcast2

[yanivs]

hi,

trying to run sc_serv...

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

c:\SHOUTcast2>sc_serv
The application has failed to start because its side-by-side configuration is in
correct. Please see the application event log or use the command-line sxstrace.e
xe tool for more detail.

c:\SHOUTcast2>

what happend?

[DrO]

you didn't read the documentation it seems... http://wiki.winamp.com/wiki/SHOUTcas...rver_2#Windows

-daz

[yanivs]

you right. because SC2 working on my other mashine, i didnt think about it...

you think that the SC2 can work with the "Microsoft Visual C++ 2010 Redistributable Package (x64)" ? or i need to install the 2008 version of it?

[DrO]

it needs to be the one which is specified in the documentation (which is why it is explicitly mentioned in the documentation) as 2008 relates to the version of the compiler which is used to build the DNAS and has nothing to do with the date things are built - installing the 2010 package will have no effect on getting the DNAS to run.

-daz

[yanivs]

working....

now it's the stage of the authhash.

"Creating an authhash locks it to the IP of the machine used for registration. If this changes then you will need to contact support to be able to make any changes."

but why IP only? :-( There is no way to do this with domain that associated to
the IP server?

[DrO]

because that was the best way to work universally irrespective of people having weird domain setups, etc and since it's information that is simple to get from the connection made from the DNAS to the YP.

and generally, there shouldn't be much need to keep changing the details of the authhash - if that is the case then i'd suggest you might need to re-assess what you're doing as continuously changing the details will move the listing around and won't make it easy for people to re-find your station in the listing.


also, make sure there is a streamid_1=1 line in your config file - if not then you need to add it and restart the DNAS otherwise it won't always recognise the authhash which causes too many people to incorrectly re-create the authhash over and over again.

-daz

[yanivs]

my server is permanent, i asked about the domain because I have a backup server with different IP on stand by. In the case of a problem, i just need to change the A record of the domain to the backup server IP.

OK.

i have hash:

streamid_1=1
streampath_1=/stream1
streamid_2=2
streampath_2=/stream2
streamauthhash_1= **my hash**
streamauthhash_2= **my hash**

[yanivs]

no YP connection.

what i did wrong?

password=1234
adminpassword=5678
portbase=80
requirestreamconfigs=1
yp2=1
log=1
screenlog=1
logclients=1
logfile=sc_serv.log
w3cenable=1
w3clog=sc_w3c.log
publicserver=default
banfile=sc_serv.ban
ripfile=sc_serv.rip
;riponly=0
savebanlistonexit=1
saveriplistonexit=1
maxuser=250
;listenertime=0
streamid_1=1
streampath_1=/stream1
streamauthhash_1=1111
streamid_2=2
streampath_2=/stream2
streamauthhash_2=1111
;configrewrite=0
;songhistory=10
;namelookups=1
;ypaddr=yp.shoutcast.com
;ypport=80
;ypPath=/yp2
;ypTimeout=60
;autodumpusers=0
hidestats=1

the number 1111 represents the hash that i got...

[DrO]

i've no idea and don't really want to guess at what it might be (especially as i'm now stopping for the night seeing as it's gone midnight my time).

all i can do is suggest you look at the DNAS's logs to see what error is being reported and try to do as it suggests (if applicable), as there is nothing i can work from with what you've posted above.

-daz

[yanivs]

ok, i will do that...

[yanivs]

I performed a test, to change the port to "portbase=8000" (from 80)

and now the YP2 is connected.

i can't to broadcast the audio on port 80 and sill work with YP2??

[DrO]

port 80 is supported by the DNAS but it depends on your network setup as to whether it'll work ok or not (as other people use the v2 DNAS on port 80 without issues).

however, without any details from the log when you were trying to run it on port 80, there's not much i can do / suggest as to why it is not wanting to work.

-daz

[yanivs]

how can i collect the right details about the YP error?

the log is not giving me any data about it, except from (no YP connection)
at the html interface...

i already did:

yp1debug=1
yp2debug=1

....

[yanivs]

i'm looking for YP on the log. nothing.

[DrO]

i might be easier to just paste the contents of the log file (make sure to remove any authhash, passwords) though i'm about to finish looking at things until the 29th so you will likely have to wait for a reply from me (unless anyone else has a look at it in the meantime).

-daz

[yanivs]

no problem, tell me what to do to make the log helpfull..

the issue is, that i can't leave the shoutcast at public mode because no budy
can to connect to the stream...and we can't to collect the data about the
YP error when i'm in private mode...(i think so)

now it's night, i can "play" with the stream.
tell me what to put in the config file to make the log more helpfull,
and how meny time you ned m to be at "public" mode.

thnx...

[yanivs]

Solved!

i don't know why,
but at "default" public mode at the server, with "public" mode on SAM, it's not working.
but with the mode "always" on the server it's working now on port 80.

[DrO]

i'd have to guess that SAM isn't sending the correct details to the DNAS since 'default' in the DNAS config makes it use what the source says the public/private mode is meant to be. depending on the SAM version you're using, it could be a current issue or something which is fixed in a newer version than you're using, but that is likely to be something to direct at them.

with the log, just attaching things as you'd already configured them would have been enough since that also in the version being used provides details about the source connection (which might be able to work out the SAM issue). if not then don't worry about it as long as you're able to broadcast as you want to do.

-daz

[yanivs]

I attached the "new" log, after the YP problem solved.
(i deleted the old one and restarted the server)

i see there a lot of Errors...if you can look at it...

[DrO]

all of the 10053 / 10054 error lines can bascially be ignored - that's just the DNAS reporting information which shouldn't be unless when debugging client connections (and is normal when a client disconnects) and is something that will be hidden in the next release.


the initial blocking of the clients is correct as there is no source connected until a bit later and the DNAS cannot provide the stream if there is no source.


what does seem strange is the number of client connections which only last up to a few seconds though i'm not too sure about that and might be an issue with the stream coming from the source or could just be the clients not liking the stream itself (why though i don't know).

-daz

[yanivs]

maybe thay didnt like...maybe because i "played" a lot with the stream for two hours :-)

i will let the new shoutcast to run for this week.

p.s: i see that another SRC want to connect

1-12-24 23:04:21 I msg:[SRC 115.168.33.141:17485 sid=1] SHOUTcast 1 source connection.
2011-12-24 23:04:21 E msg:[SRC 115.168.33.141:17485 sid=1] connection denied. Bad password.
2011-12-24 23:04:21 I msg:[SRC 41.74.166.48:59296 sid=1] SHOUTcast 1 source connection.
2011-12-24 23:04:21 E msg:[SRC 41.74.166.48:59296 sid=1] connection denied. Bad password.

is that so?

i can to open the SRC connection just to my DYNDNS domain?

[yanivs]

i try to use the SRCIP

srcip=radio111.dyndns.tv

the domain is for my studio IP to prevent another SRC to connect...

the SC2 not accept it...

[DrO]

Originally Posted by yanivs

p.s: i see that another SRC want to connect

1-12-24 23:04:21 I msg:[SRC 115.168.33.141:17485 sid=1] SHOUTcast 1 source connection.
2011-12-24 23:04:21 E msg:[SRC 115.168.33.141:17485 sid=1] connection denied. Bad password.
2011-12-24 23:04:21 I msg:[SRC 41.74.166.48:59296 sid=1] SHOUTcast 1 source connection.
2011-12-24 23:04:21 E msg:[SRC 41.74.166.48:59296 sid=1] connection denied. Bad password.

is that so?

depending on how / what is trying to access the pages of the DNAS, if it's not matched to anything then the DNAS will attempt to treat it as a potential source connection and then handle it that way. not ideal but there's not too much which can be done as banning only applies to clients and is done at a later stage in the source / client connection process due to needing to be able to do it on a per-stream basis.

Originally Posted by yanivs

i try to use the SRCIP

srcip=radio111.dyndns.tv

the domain is for my studio IP to prevent another SRC to connect...

the SC2 not accept it...

if the DNAS cannot resolve it then that is the most likely reason for it not being liked. you could try entering the raw IP address it relates to and see if that works.

-daz