Go Back   Winamp & Shoutcast Forums > Shoutcast > Shoutcast Discussions

Closed Thread
Thread Tools Search this Thread Display Modes
Old 6th November 2013, 14:48   #81
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
Hello DrO.

Do you know when 2.2 will be uploaded to shoutcast.com?

Reason I ask is that centovacast automatically pulls from shoutcast when there is an update. Since the update is hosted on your personal server they are not able to do the update.

Thanks.
Bryon
Bryon Stout is offline  
Old 6th November 2013, 14:59   #82
DrO
 
Join Date: Sep 2003
Posts: 27,873
when it's done is the best i can answer that and it'd be a 2.2.1 going up.
DrO is offline  
Old 6th November 2013, 15:00   #83
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
Thanks DrO.
Bryon Stout is offline  
Old 8th November 2013, 08:58   #84
sdx
Junior Member
 
Join Date: Apr 2002
Location: Stockholm, Sweden
Posts: 9
Download link broken?

I'd like to try the new Linux 64-bit build, due to that the official release segfaults all the time (buffer overflow?). However, the download link provided in the first post in this thread seems to be broken.

So, is it possible to download the new build? Is it still interesting to receive a core dump when it segfaults with the old builds (happened weekly before, almost daily now)? I guess the reason for the crashes is malformed/unexpected data from certain clients?

One more thing, it would be great if the ban list is written somewhere so it persists across server/process restarts.
sdx is offline  
Old 8th November 2013, 09:14   #85
DrO
 
Join Date: Sep 2003
Posts: 27,873
will check out why the links aren't working. a core dump isn't going to be helpful as too much changed between 2.0 and 2.2 for me to want to go back to that version of the code.

the ban list is written to sc_serv.ban as long as writing it is enabled and v2.2 will save it when the ban is added/removed unlike only on exit as v2.0 did so any issues with it not persisting should be resolved with v2.2 as long as its not been disabled.
Attached Files
File Type: exe sc_serv2_win64_10_16_2013.exe (1.48 MB, 278 views)
File Type: exe sc_serv2_win32_10_16_2013.exe (1.34 MB, 291 views)
DrO is offline  
Old 8th November 2013, 09:45   #86
DrO
 
Join Date: Sep 2003
Posts: 27,873
i've updated the links in the first post so it's now hosted via the forums as someone kindly took the piss with getting things from my hosting :grr:
DrO is offline  
Old 8th November 2013, 16:11   #87
davidgenes
Junior Member
 
Join Date: Oct 2010
Posts: 4
I have a bunch of customers that I host live streams for that are using BUTT encoder and Shoutcast v1 on Windows. I currently have a separate instance of Shoucastv1 running for each customer's stream which has actually worked fairly well for quite a few years; it is just a pain to configure new ones as you have to create a new service, configure options, etc.

I see that the issues with BUTT are supposed to be fixed in this v2.2, so I loaded it up on a test server and did some testing, but can only seem to get to the first stream.

Can someone tell me: is it possible to host multiple streams on the same port with BUTT encoder?

If not, how about a single instance with a separate port for each source, but listeners could all be on port 80?

Thank you!
davidgenes is offline  
Old 8th November 2013, 16:18   #88
DrO
 
Join Date: Sep 2003
Posts: 27,873
BUTT uses the v1 protocol and so it can only connect on stream #1 as that's all that the v1 protocol allows. that means it's not possible to use multiple BUTT encoders on the same port as the v1 protocol doesn't support it, hence the v2 protocol to resolve that issue.


multiple legacy ports to allow for v1 based sources on streams other than #2 was something i'd started on though the main issue with it is that titles were not being detected (since they'd be sent to a port that was not there (since it's generally assumed that with a v1 based source, you have portbase [where titles go to] and portbase+1 [the port the source actually connects to]).


so due to all of that, the feature was not enabled with this v2.2 update (which otherwise will resolve the issue with using BUTT) as it'd generate more issues with titles not being provided when the only feasible way is to open up 2 ports to then be able to do it which seemed sub-optimal but is likely the only way to do it).
DrO is offline  
Old 8th November 2013, 16:29   #89
davidgenes
Junior Member
 
Join Date: Oct 2010
Posts: 4
Quote:
Originally Posted by DrO View Post
so due to all of that, the feature was not enabled with this v2.2 update (which otherwise will resolve the issue with using BUTT) as it'd generate more issues with titles not being provided when the only feasible way is to open up 2 ports to then be able to do it which seemed sub-optimal but is likely the only way to do it).
Personally, I would still love to see that!

It would be a vast improvement to have a single instance of the service running and handling multiple streams (even if the same number of ports are used) rather than having a separate instance running for each stream. Plus the listeners could then all be on port 80.

Any chance I could hire you to dump me out a version that could do that?

EDIT: Or do you think I am better off sticking with multiple instances of Shoutcastv1 running?
davidgenes is offline  
Old 9th November 2013, 22:12   #90
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
If I am using 2.0 and I upgrade to 2.2 will my stream be interrupted during the update?

Or will the streams run and play as if nothing happened?

Will it disconnect my listeners if I run the upgrade script?
Bryon Stout is offline  
Old 9th November 2013, 22:21   #91
DrO
 
Join Date: Sep 2003
Posts: 27,873
you have to stop the DNAS process during the update to allow the program file to be replaced so that means everyone connected at the time will get booted (which is why too many people refuse to update the DNAS as they're more concerned about uptime and listener counts than improved software).
DrO is offline  
Old 10th November 2013, 15:15   #92
e-j
Junior Member
 
Join Date: May 2011
Posts: 11
Quote:
Originally Posted by DrO View Post
well there's no reason then for the details to be changing if it is definitely just sc_trans which is connecting to the DNAS and nothing else. as there isn't support in sc_trans to relay different station titles from DJ connections provided through it and it should just be showing "Radio PlayMusic".

all i can suggest is making sure that only the sources you want to connect can connect, that there's no remote port access enabled and no duplicate / alternative configurations which might be used to run sc_trans, etc which would allow another instance to connect.

also check the DNAS's logs for anything suspicious as based on what you've said, there's no viable way for the title to do as you're seeing unless something else is connecting to the DNAS with a different title from what you're expecting to see.
Just wanted to mention that since upgrading to this build I also had to add "useicy=0" for titles to display in media player applications (foobar2000, XiiaLive, VLC).
e-j is offline  
Old 11th November 2013, 02:58   #93
kapitanluffy
Junior Member
 
Join Date: Nov 2013
Posts: 12
been experiencing this error (http://forums.centova.com/index.php?topic=2216.0)

any one has an idea why?

here's the config file

code:
adminpassword=betterpassword
maxuser=200
password=password
portbase=8080
portlegacy=0
streamadminpassword_1=betterpassword1
streamid_1=1
streampassword_1=password1
destip=127.2.2.129
srcip=any
publicport=80

kapitanluffy is offline  
Old 11th November 2013, 12:35   #94
DrO
 
Join Date: Sep 2003
Posts: 27,873
e-j: there is an issue with that setting in some cases which will be looked into (and seems to be the trigger point for the YP registration issues some are having).

kapitanluffy: this is definitely happening with v2.2 and not that you're still on something using v2.0 ?
DrO is offline  
Old 13th November 2013, 07:57   #95
sdx
Junior Member
 
Join Date: Apr 2002
Location: Stockholm, Sweden
Posts: 9
YP registration mandatory for users to connect?

The new build seems to require that the stream is registered in the directory. Since the service seems to be having some problems (because I can connect to the port from the Internet), this creates significant unavailability.

Another good question is why the server software requires the stream to be registered before it accepts clients. Can this be disabled?

FYI, I see the following error from time to time:

2013-11-13 09:56:21 ERROR [YP] Stream #1 connection attempt failed. YP2 error code is 480 [Cannot see your station/computer (URL: http://x.x.x.x:8000) from the Internet, disable Internet Sharing/NAT/firewall/ISP cache.]
sdx is offline  
Old 13th November 2013, 10:52   #96
DrO
 
Join Date: Sep 2003
Posts: 27,873
the v2 DNAS has always required an authhash to be present before it'll allow clients to connect if the stream(s) are set to be public as it uses the authhash details for what is provided to them e.g. title, genre etc.

I've explained too many times now why there is the need for an authhash and suggest reading through the docs provided with the DNAS to save me repeating it all again (plus its a pain to find and copy and paste it whilst I'm replying on the mobile).

I am aware that in some setups the automatic generation of the authhash is hindering things so it'll cause clients to be blocked for longer than is desired or that if the directory tester connection doesn't work correctly (though a complete directory failure should already allow clients to connect).


that is why there will be a number of changes made for the next build which will make it accept clients even if the authhash has not been created if set to be public or if the directory is not seeing / accepting the stream(s) as long as a decent title and genre are provided by the connected source.

I'm not too happy about allowing clients if there's directory errors e.g. the 480 error in legitimate cases but this is what people want despite it being a very obvious way to ensure that the DNAS is made available correctly.

as all too often people using the v1 DNAS don't realise there is a yp error for their stream which this was doing despite the complaints and abusive messages received via the formal feedback. though on the other hand it lessens the impact on server updates or stream changes so there's minimal effect on listeners which is the reason why the changes are going to be made.

so things will be fixed and those who have sent pms / messages will likely be targeted with pre-release builds when things are ready for testing.
DrO is offline  
Old 13th November 2013, 17:27   #97
sdx
Junior Member
 
Join Date: Apr 2002
Location: Stockholm, Sweden
Posts: 9
I think people who don't have their network/firewall under control would be helped by an informative message to stdout/logs every time it can't connect. However, to create a self-DoS system where listeners are prevented from connecting is a bit like throwing the baby out with the bathwater... I think that the above solution should improve both cases.

I saw that the YP directory tester started working 20 minutes ago. I assume you fixed it. Thank you.
sdx is offline  
Old 13th November 2013, 17:42   #98
DrO
 
Join Date: Sep 2003
Posts: 27,873
i've not done anything regarding the directory tester.

v2.2 has seen a mass of changes to make it more appropriate and to work more like a v1.x DNAS so it can be used as a direct replacement (as keeping having to support the v1.x DNAS based listings is a pain when the issues with them are resolved with the v2.x setup). the means to allow listeners to connect when there is a YP issue is one of the last remaining compatibility changes which still needs to be made to have the v2.2 DNAS be a true v1.x replacement.


and with your comment, that is already happening, it's just how things have been designed (as already explained) that means a failed YP add is deemed a critical failure (if the YP actually responded). though you'd be surprised at how many don't or cannot look at the logs (especially a lot of hosts as there's a whole batch of DNAS from one that aren't listed because they've not paid attention to the 'you must restart this DNAS' message that has been sent to the DNAS for the last year and a half).
DrO is offline  
Old 14th November 2013, 02:01   #99
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
Hello DrO.

Ok I updated to 2.2 but now my DNAS is telling me this.

"Status: Unable to connect to the Directory.
The server will behave like it is private."

Which then changed to..
"server is up and public"

which then changed again to...
"Server is currently up and unable to connect to the Directory.
Listeners are allowed and the server will act like it is private."


Seems like its bouncing in and out of being public?

Listeners: 22 of 1000
Status: Public
Directory ID: 186925
Source: v2 [ kick ]


2013-11-13 21:47:44 WARN [CONFIG] Invalid item on line 22 of ../deephouselounge/etc/server.conf -> `yp1debug'
2013-11-13 21:47:44 WARN [CONFIG] Deprecated statement found on line 88 of ../deephouselounge/etc/server.conf -> change autodumpsourcetime_1=30 to autodumptime_1=30
2013-11-13 21:47:44 WARN [CONFIG] Invalid item on line 102 of ../deephouselounge/etc/server.conf -> `yp2'
2013-11-13 21:47:44 WARN [CONFIG] Invalid item on line 164 of ../deephouselounge/etc/server.conf -> `specialfiletmpdir'
2013-11-13 21:47:44 INFO
2013-11-13 21:47:44 INFO [MAIN] SHOUTcast DNAS/posix(linux x64) v2.2.0.107 (Oct 16 2013)
2013-11-13 21:47:44 INFO [MAIN] PID: 1649
2013-11-13 21:47:44 INFO [MAIN] Loaded config from ../deephouselounge/etc/server.conf
2013-11-13 21:47:44 INFO [MAIN] Calculated CPU count is 8 -> using all available CPUs
2013-11-13 21:47:44 INFO [MAIN] Limited to 1024 file descriptors [relates to ulimit -n]
2013-11-13 21:47:44 INFO [MAIN] Starting 8 network threads
2013-11-13 21:47:44 INFO [MICROSERVER] Listening for source and client connections on port 8006
2013-11-13 21:47:44 INFO [MICROSERVER] Listening for legacy source connections on port 8007
2013-11-13 21:47:44 INFO [MICROSERVER] Flash policy file server not enabled
2013-11-13 21:47:44 ERROR [DST 202.94.144.97 sid=1] SHOUTcast 1 client connection rejected. Stream not available as there is no source connected. Agent: `Lavf52.111.0'
2013-11-13 21:47:44 ERROR [DST 92.236.215.177 sid=1] SHOUTcast 1 client connection rejected. Stream not available as there is no source connected. Agent: `Lavf52.111.0'
2013-11-13 21:47:44 ERROR [DST 82.131.66.142 sid=1] SHOUTcast 1 client connection rejected. Stream not available as there is no source connected. Agent: `Lavf52.111.0'
2013-11-13 21:47:44 INFO [SRC 198.15.94.34] SHOUTcast 2 source connection starting.
2013-11-13 21:47:44 ERROR [DST 5.71.244.189 sid=1] SHOUTcast 1 client connection rejected. Stream not available as there is no source connected. Agent: `Lavf52.111.0'
2013-11-13 21:47:44 INFO [SRC 198.15.94.34 sid=1] Title update [Tommy Hogunz - deephouselounge]
2013-11-13 21:47:44 ERROR [DST 88.83.230.139 sid=1] SHOUTcast 1 client connection rejected. Stream not available as waiting on a Directory response. Agent: `FreeAmp/2.x'
Bryon Stout is offline  
Old 14th November 2013, 02:23   #100
DrO
 
Join Date: Sep 2003
Posts: 27,873
the first part of the post is due to some maintenance on things which is why you were seeing that (and at least proves the error handling is working ok if the YP cannot be accessed).

the second part of the post is because there is a delay between a source connecting (when it finally does) and the YP being pinged (which has been covered in the prior posts that such behaviour will be altered).
DrO is offline  
Old 14th November 2013, 02:25   #101
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
So i reset my server and now I get this error

480 Cannot see your station/computer (URL: <streamurl>) from the Internet, disable Internet Sharing/NAT/firewall/ISP cache
Bryon Stout is offline  
Old 14th November 2013, 02:28   #102
DrO
 
Join Date: Sep 2003
Posts: 27,873
you may need to temporarily set useicy=0 in the config file to deal with a sporadic issue being seen by the Directory tester (which is something i was briefly working on but need to make a few more adjustments in addition to the DNAS fix that is needed as that option is being incorrectly handled in some cases).

and this is why v2.2 didn't go straight up on the downloads page to be able to catch such issues before it's fully pushed.
DrO is offline  
Old 14th November 2013, 02:29   #103
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
roger that.. Ill give that a try.
Bryon Stout is offline  
Old 14th November 2013, 02:32   #104
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
strange.. I didnt do anything and it went back to public with no error.


Should I still set useicy=0 ?
Bryon Stout is offline  
Old 14th November 2013, 02:34   #105
DrO
 
Join Date: Sep 2003
Posts: 27,873
i'd leave it alone for now as it can under normal circumstances take 2 'test' cycles before the YP can actually see the DNAS if running things behind a NAT, etc. either way, it's more likely to be the tail end of things i was working on being applied and catching up in the system. and with that, now it's gone 3:30am here, i'm off to sleep.
DrO is offline  
Old 14th November 2013, 02:36   #106
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
sounds good.

Thanks for the assistance as always.

Gnight.
Bryon Stout is offline  
Old 14th November 2013, 02:47   #107
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
Here is something for you when you wake up.

1. I have another station and I am trying to create the authhash. After I fill out all the details and click submit the DNAS admin login pop up shows and asks me to login. WHen I do it just repops up. If I click cancel then the authhas creation fails.

2. Itunes no longer shows the "Current song". Its only showing "stream title" and "website url".
Bryon Stout is offline  
Old 14th November 2013, 16:17   #108
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
It seems like one person keeps making a shit ton of connections.

13-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (6 seconds) [Bytes: 330344] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (7 seconds) [Bytes: 292868] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (11 seconds) [Bytes: 420564] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (5 seconds) [Bytes: 242900] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (1 seconds) [Bytes: 166560] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (4 seconds) [Bytes: 314892] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (9 seconds) [Bytes: 391244] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (7 seconds) [Bytes: 369550] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (12 seconds) [Bytes: 451138] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (2 seconds) [Bytes: 293214] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (10 seconds) [Bytes: 412779] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (4 seconds) [Bytes: 325972] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (14 seconds) [Bytes: 483799] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (10 seconds) [Bytes: 423777] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (3 seconds) [Bytes: 304053] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (8 seconds) [Bytes: 380405] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (9 seconds) [Bytes: 401940] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (14 seconds) [Bytes: 472817] Agent: `'
2013-11-14 12:15:44 INFO [DST 217.76.74.147 sid=1] SHOUTcast 1 client connection closed (13 seconds) [Bytes: 461978] Agent: `'


Any idea whats causing this?
Bryon Stout is offline  
Old 15th November 2013, 01:46   #109
DrO
 
Join Date: Sep 2003
Posts: 27,873
Quote:
Originally Posted by Bryon Stout View Post
Here is something for you when you wake up.

1. I have another station and I am trying to create the authhash. After I fill out all the details and click submit the DNAS admin login pop up shows and asks me to login. WHen I do it just repops up. If I click cancel then the authhas creation fails.
is that with v2.0 or v2.2 ? Either case, it'd need to be the DNAS server admin password i.e. from adminpassword being used and that you've accessed the page from the server admin pages and not hitting them directly.

Quote:
Originally Posted by Bryon Stout View Post
2. Itunes no longer shows the "Current song". Its only showing "stream title" and "website url".
that would need the useucy=0 'flipping of the option' to see if that resolves it (assuming this is with v2.2).

Quote:
Originally Posted by Bryon Stout View Post
It seems like one person keeps making a shit ton of connections.
...
Any idea whats causing this?
someone / something trying to connect. other than checking the IP address i.e. it's not coming from something you've setup and have it purposefully trying to get stats, etc from the wrong url. otherwise i'd look into banning it. though will note that empty user-agents can come from some hardware sources (as we had been looking to block such connections but found it caused issues in legitimate cases so it was rolled back).
DrO is offline  
Old 15th November 2013, 02:43   #110
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
[QUOTE=DrO;2974161]is that with v2.0 or v2.2 ? Either case, it'd need to be the DNAS server admin password i.e. from adminpassword being used and that you've accessed the page from the server admin pages and not hitting them directly.

Quote:
Its with 2.2 It popped up when I tried to create the authhash. I put in my admin password but the login box "username and password" kept popped up after I put in the password. This would loop as long as I kept putting in my password.
that would need the useucy=0 'flipping of the option' to see if that resolves it (assuming this is with v2.2).

Quote:
Yes its with 2.2 so I will give that a try.
someone / something trying to connect. other than checking the IP address i.e. it's not coming from something you've setup and have it purposefully trying to get stats, etc from the wrong url. otherwise i'd look into banning it. though will note that empty user-agents can come from some hardware sources (as we had been looking to block such connections but found it caused issues in legitimate cases so it was rolled back).


Quote:
I ended up banning the IP as it was making tons of connections. If it was a legit listener I guess there will always be wounded soldiers.

thanks for taking the time and answering me.
Bryon Stout is offline  
Old 18th November 2013, 13:06   #111
Cande
Junior Member
 
Join Date: Nov 2013
Posts: 15
sc_serv max open files

Hello,
I'm trying to change the maximum number of open files for the process sc_serv in my private Shoutcast DNAS 2.2 server running on Ubuntu 12.04.3 LTS 64 bit.

The system itself (sysctl -a) has a safe 202022 max open files limit.

I changed this value at "user level" to 65536 (both hard and soft limits) by editing the /etc/security/limits.conf (and by requiring pam_limits.so) and also run "ulimit -n 65536", but if I run this command:

cat /proc/(sc_serv's PID)/limits

... it shows "Max open files 1024 (soft limit) and 4096 (hard limit).
Accordingly, Shoutcast's log states 1024 as maximum open files limit.

It sounds like sc_serv uses a "self per process" setting when it starts up, ignoring system wide and per user settings.
Is there a way to change this? Is this a known limit or bug?

Thanks a lot in advance for your support and your great work!

Cheers!!!
Cande
Cande is offline  
Old 18th November 2013, 21:38   #112
Cande
Junior Member
 
Join Date: Nov 2013
Posts: 15
Update!

I found that after booting the server and (auto) starting sc_serv via shell script, the open files limit is 1024 despite changes done in limits.conf and PAM files, but if I manually stop sc_serv, issue the "ulimit -n 65536" and start sc_serv again, then the limit is correctly set to 65536 max open files!

So, the new question is: how can I make sc_serv to acquire the desired "ulimit -n" at system boot?

I am using Webmin to manage the server and my suspect is that this module changes the limits regardless of limits.conf/PAM...

Any hints?

Thanks again!
Cande
Cande is offline  
Old 18th November 2013, 22:35   #113
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
So I upgraded to 2.2. I run 4 stations on centovacast.

My one stations DJ login does not work.

I created a dj name and I am trying to connect with v1 source so my password is..

djnamew and using port for v1 client.

I keep getting a error that my pw is incorrect. How can I troubleshoot this?
Bryon Stout is offline  
Old 18th November 2013, 23:07   #114
DrO
 
Join Date: Sep 2003
Posts: 27,873
Cande: you'll need to consult the documentation / help for the OS you're trying to set it on. the DNAS will just use the limit which is available to it when it starts and if the OS is not preserving that option, then it's likely there's something else either resetting it or overriding it which you've not found yet. but the DNAS is not doing anything along those lines (it cannot unless it basically has root privileges and was coded to do so - which it doesn't).

Bryon:i assume you mean you're connecting directly to the DNAS and not to sc_trans? if so then remove the DJ name from the password. as i only remember adding support for doing that in v2 mode and not for the legacy mode (but i'd need to re-check it).
DrO is offline  
Old 19th November 2013, 02:12   #115
Bryon Stout
Senior Member
 
Join Date: Feb 2011
Posts: 377
maybe I didnt explain myself correctly.

1. I have centovacast 3.0
2. I upgraded to 2.2 shoutcast DNAS server
3. In order for my DJs to connect via BUTT I need to create a DJ user.
4. In order to connect with BUTT which is V1 legacy you need to use DJNAME:PASSWORD as the password inside of BUTT (lol sounds so funny).

It was saying my pw is incorrect but I think I know why. I need to restart my server in order for that dj account to be active.

Now that I restarted my server I am getting the 480 error again. (I never changed the useicy=0 so I think that is my next move.) I was avoiding changing this as I wanted to wait for 2.2.1 to be released. I dont feel like remembering to change it back once 2.2.1 is released.

So with all that said, my next step is to change useicy=0 and go from there.
Bryon Stout is offline  
Old 19th November 2013, 07:37   #116
DrO
 
Join Date: Sep 2003
Posts: 27,873
yes use the useicy=0 option as its the reason for the random 480 errors. the next update will deprecate that option for a different value name ws well as allowing the tester to work with it being disabled. so other than showing as an invalid option in the config loading it'll all work as expected.
DrO is offline  
Old 19th November 2013, 22:48   #117
Cande
Junior Member
 
Join Date: Nov 2013
Posts: 15
Thanks for your reply DrO!

By looking for a solution, I discovered that the "/sbin/init" script I was using to startup sc_serv at boot, does NOT consider limits.conf to set, for example, the maximum open files for processes run at system level.

Since I'm using Ubuntu Server and Webmin and both are configured to use the "Upstart" boot system, I used Webmin to create a simple Upstart script for sc_serv and of course I included the "limit nofile n n" stanza (parameter) to alter system's default 1024 open files limitation.

Now when my server (re)boots sc_serv is loaded with the desired limit and seems to work OK!

Thanks again!
Cande
Cande is offline  
Old 20th November 2013, 09:05   #118
milosz
Senior Member
 
Join Date: Apr 2006
Location: chicago
Posts: 123
I've limited listeners to 250 on primary and secondary servers, and I've had no problems with DNAS running out of file handles for over a week. So I don't think there's some ongoing process on the box that is eating up file handles as time goes on. It's sc-serv that somehow thinks it has run out of file handles when close to 300 users connect even though the hard and soft limits for open files is set at 65535 (which is the Linux max.)

I don't understand why, but that's the conclusion I've come to. At some point as connected listeners approach 300, sc_serv **THINKS** there are no more file handles, even though there are plenty.

I believe that sc_serv runs as root on my machine, but even if it's not running as root, I have implemented 65535 as hard and soft limits for all users via PAM, so no matter what user sc_serv thinks it is, it will have 65535 file handles to play with.
milosz is offline  
Old 20th November 2013, 09:14   #119
DrO
 
Join Date: Sep 2003
Posts: 27,873
there's no need to keep repeating the same information about your issue - i know that something is specifically messed up with your setup and the interaction with the DNAS. and i've said i will look into it but i need to finish the project i'm currently working on before i can start to work solely on the DNAS issues.
DrO is offline  
Old 20th November 2013, 09:34   #120
milosz
Senior Member
 
Join Date: Apr 2006
Location: chicago
Posts: 123
Well I thought I would indicate that I have tried to eliminate the possibility that some other process on the machine was causing the file-handle equivalent of a memory leak, and also that I have pretty high confidence that the system is, indeed, presenting sufficient file resources to any process running. I'd actually prefer that the issue NOT be DNAS and would be some system-environment related thing that I could sweep away with a setting or a script- to that end I've been trying to examine what's happening on the machine. I am still half convinced that something related to being a virtual Linux instance might actually be the culprit, though damned if I can find out WHAT, exactly.
milosz is offline  
Closed Thread
Go Back   Winamp & Shoutcast Forums > Shoutcast > Shoutcast Discussions

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