Error when starting shoutcast after rebooting

[csc2ya]

After I rebooted my server earlier, I noticed that shoutcast did not appear to be working.

The way I run shoutcast is via a scheduled task that runs it on boot.

On stopping the task, and attempting to run it manually, I got a message that there was already something listening on port 8000.

I looked in task manager, and noticed sc_serv.exe listed. I ended this, and attempted to run sc_serv.exe manually again. On doing this I got an error prompt referencing sc_serv_basic.conf. http://csc2ya.co.uk/shoutcast.png

On looking into what could be wrong with my files, i've come up blank. Both files have always worked fine up until now. Ideally, I want shoutcast to run as a scheduled task on boot, as it's always done before, but as I can't continue past the error unless I can see it, it appears this way will no longer work.

My configuration files (with any sensitive info removed), are pasted below:

Originally Posted by sc_serv.conf

; NOTE: for any relative paths specified are relative to
; sc_serv and not to where the conf file is being stored


; we use the sc_serv_basic.conf configuration file as the
; base configuration to work from for a public server
include=sc_serv_basic.conf

; due to the way configuration files work we can replace an
; existing value like 'publicserver' with a newer value so
; the following will force any sources to be public which
; allows us to then connect and be listed on the YP
publicserver=always
streamid_1=1
streamauthhash_1=
MaxUser=1000

Originally Posted by sc_serv_basic.conf

; NOTE: for any relative paths specified are relative to
; sc_serv and not to where the conf file is being stored

; here we will setup where the log and other related files
; will be stored. make sure that these folders exist else
; sc_serv will throw an error and will close itself down.
; we will make the logs save to the sc_serv2 directory
logfile=logs\sc_serv.log
w3clog=logs\sc_w3c.log
banfile=control\sc_serv.ban
ripfile=control\sc_serv.rip


; for testing we will make the server only work locally
; (i.e. localhost / 127.0.0.1) though if this is left out
; or set to publicserver=always then we attempt to make a
; connection to the YP for listing - do not forget to add
; in a 'streamauthhash' value for any public streams made
;publicserver=always


; if you're wanting to use a different port to use for any
; connections then you can use this option e.g. to use 80
; otherwise port 8000 is used as the default to listen on.
;portbase=80


; password used by sc_trans or the Winamp dsp plug-in
; NOTE: remember to change this to something else
password=


; password used for accessing the administation pages
; NOTE: remember to change this to something else
adminpassword=

[DrO]

what is the version reported by the DNAS ?

as for that messagebox, that's possibly some debugging incorrectly left in an earlier build (it shouldn't be in the current build - hence the question above).

if it is happening with the current release, we'll have to follow-up with something to try out.

[csc2ya]

2.4.2.167

I just redownloaded and reinstalled to ensure I was using the latest version, and the same error still occurs.

I have noticed that if I rename sc_serv.conf so that it's inaccessible to shoutcast, it will ask me which config file to use on startup, with the only option being sc_serv_basic.conf. After pressing enter to confirm, it will then run with no issues.

[DrO]

ok, i found the reason for the messagebox..

the work around is to have all of the settings just in sc_serv.conf (passwords, authhash, anything else you've specifically set) and ensure there is no 'include' line in the sc_serv.conf i.e. copy + paste the contents of sc_serv_basic.conf to the end of your current sc_serv.conf and ensure that include=sc_serv_basic.conf is removed.

that should sort out the issue of the debug message being shown (which is already removed for the next build, just the public build was incorrectly built with it still enabled).

[csc2ya]

Thanks....Have done that, and it now runs with no errors, as well as the scheduled task working to start it now.

[DrO]

thanks for the confirmation it's ok now for you.