Tweet
No issues here. Build is smooth.
-
Ramon -
Hello Ramon,
It can be useful to know more details about your installation, as it looks like the DNAS update behaves differently, depending from the platform, OS, panel, etc.
Thank you.Comment
-
All I know is that I'm on a 64bit system. I pay for hosting. I got two months. I use the latest Centovacast. I had an issue with a mount not showing listeners in Centovacast. I removed and add them back, rebooted and that cleared it up. Maybe you can try that.RamonComment
-
Hello,
I believe that your mount wasn't showing the listeners because of no communication between Centova Cast and the server.... This happen sometime because you change the password fromCentova Cast without restarting the server.
After restarting the new password is enforced and listeners were again visible in Centova Cast.
...but this is issue you mentioned is something else, not related with the current DNAS issue and thread.
RegardsComment
-
same..
Same problem and logs as MRGrp.
Thanks MRGrp for the better explanation. Maybe its the bug No.6 as DrO said.Comment
-
...in the meantime I confirm that our 7 radio stations keep going offline continuously. Many times they do not restart, they simply go offline.
Centova Team doesn't know how to assist us.
We really hope to get some assistance (and a solution) from DrO and the SHOUTcast team as soon as possible. The radio stations are listed in iTunes and Windows directories, and downtime can just result in being Delisted.
Best Regards.Comment
-
the 493 errors are irrespective of the DNAS version being used and is a yp side issue which we've been trying to resolve for the last week.
so its an actual DNAS crash that happens? the log just prior to the DNAS crashing would be handy to have.
also in both cases are multiple 1.x sources being used for the streams ? as I see in the initial log provided the legacy source options are being used.Comment
-
if it will helpfull i can give you access to our server or if you dont want this i can send you the complete logfiles. Because the problems seems the same.
before last update we have as well the error 493 and stream doesnt start sometimes by themselve, but after last build this error doesnt exist. Now only restarts without this 493 error. For last build we have done manual installation.Originally Posted by MRGrpComment
-
the complete logs would be best as a starting point. though I'm wondering how many people are having such issues and not bothering to report them (as its taken what 2 weeks before we've had any reports of issues with the new build).Comment
-
Hello DrO,Originally Posted by DrO
Thank you for your reply.
If you are so kind to provide step by step guidance about what to do, I will be more than happy to pull the log/data you are looking for and provide them/it.
In the meantime I was able to download the "all logs" compressed folder using Centova Cast features. I will try to send you a private message with a download link.
Best regardsComment
-
Hi DrO,Originally Posted by DrO
Would you please check your PM inbox? You will find a link to download the complete logs (pulled utilizing Centova Cast).
Thank you.
Best regards
MRGrpComment
-
i've had a quick look and it's not showing anything obvious, though i only quickly skimmed through the files. it doesn't look like it's due to the known issue noted (as the logs for such cases show different things going on) and i'm wondering if it's related to some of the YP instability as another use has found their DNAS crashes when the YP responds with a certain HTTP header (100-continue).
really would need the DNAS to have all of it's debug logging options enabled to see what is going on. am not sure if the Centova options allow for that or it'll need the DNAS config file to be manually changed (which makes me wonder for such situations if it'd be better to have a DNAS admin page that allows for easily toggling such options on/off).Comment
-
Thank you DrO,
Is there anything that we can do in order to help with the debugging? Even if it has to be pulled from the SHOUTcast server page itself with your guidance?
We run our stations on a server with Linux 64 bit/latest CentOS.
Is it advisable to switch to the 32 bit version of the DNAS 2.4.2 (Build 167) in order to fix this issue, or would you suggest for the moment to just roll back to the old DNAS dated 2011?
What differences (let us say "limitations"?) will we will face, broadcasting 7 to 10 radio stations of our Group with a x86 version of the DNAS installed on our 64bit server?
We have our radio stations going online and offline like the lights of a Christmas tree, and we are really keen to find a solution ASAP.
Thank you for your assistance.
Best Regards.Comment
-
To enable more debug logging options in Centova Cast you would have to edit Shoutcast's configuration file. You can do this from within Centova Cast by loging into the affected station's account, Settings->Raw Configuration->Shoutcast2
Not sure what debug logging options are needed, but I guess you should probably change
yp1debug and yp2debug from 0 to 1. After that restart the station and check the logs when the problem occurs again.Comment
-
Thank you perfectlemon,
I have enabled yp1debug and yp2debug for one of the radio stations (the one stopping or restarting every about 30 minutes).
RegardsComment
Comment