|
|
|
|
#1 |
|
Junior Member
Join Date: Feb 2014
Posts: 5
|
Unable to connect to directory
Hi there,
this is my first post in bad english (sorry).. I managed many Shoutcastservers with a lot of listeners.. Some of them running without problems, some put this message: Status: Unable to connect to the Directory. The server will behave like it is private. What should I do?!? Greetings, MaxBahr (GTARadio) |
|
|
|
|
|
#2 |
|
Forum King
Join Date: Jun 2007
Location: Under the bridge
Posts: 2,290
|
Step 1: Provide more details, especially, what version of DNAS are you running
Step 2: ??? Step 3: Profit "If you don't like DNAS, write your own damn system" So I did |
|
|
|
|
|
#3 |
|
Join Date: Sep 2003
Posts: 27,873
|
have you tried restating the ones having the issue? are they all using v2.2.1?
if it persists after a restart (as I hope you've looked at the stickies about the sale and migration of the directory last week) then you'll need to provide at least some links to the DNAS which are affected so we can try to check our logs to find out what is going on. plus you'll need to check the DNAS logs and provide the error messages being reported. |
|
|
|
|
|
#4 | |
|
Junior Member
Join Date: Feb 2014
Posts: 5
|
Thanks for reply..
Since last week all shoutcastserver use v2.2.1.109 on Linux (Debian 7, 64Bit), the transcoder we use is v2.0.0 Build 54. I note on five streams something like this: Quote:
Now, some streams (server) are public... for 2-3 hours.. |
|
|
|
|
|
|
#5 |
|
Join Date: Sep 2003
Posts: 27,873
|
that isn't a DNAS issue (and should not be an issue with running multiple streams) and is something on our end relating to the new YP server setup (based on the error message). would still be helpful to know the address of the DNAS server (if needed you can send me a pm with it in it instead of posting it publically).
|
|
|
|
|
|
#6 |
|
Junior Member
Join Date: Feb 2014
Posts: 5
|
I will send you a pm..
|
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|