Since some days i have stream dropouts and today shoutcast server has retarded. In Centova server log i got the message: +++ dump failed
From streaming server log: 2015-06-01 12:05:59   WARN   [ADMINCGI sid=1] Title update rejected - value not allowed
Auto dj log:
"2015-06-01 12:15:25   I   msg:[DECODE] Next file is /usr/local/centovacast/var/vhosts/soundstorm/var/spool/media/=Jingle/Moni/moni7-best-tracks-2-2012.mp3
2015-06-01 12:15:25   W   msg:Could not load metadata because could not open file #!/usr/local/centovacast/bin/nextsong soundstorm 5a29a7ea5fdd58f2ab349fe3d2b4eaa2 sctrans2next
2015-06-01 12:15:25   E   msg:Failure converting filename to metadata Premature end of data (*/%TIT2.) 2015-06-01 12:15:25   E   msg:Failure converting filename to metadata Premature end of data (*/%TIT2.) 2015-06-01 12:15:25   E   msg:Failure converting filename to metadata Premature end of data (*/%TIT2.) 2015-06-01 12:15:25   E   msg:Failure converting filename to metadata Premature end of data (*/%TIT2.) 2015-06-01 12:15:40   I   msg:[DECODE] Next file is /usr/local/centovacast/var/vhosts/soundstorm/var/spool/media/=Sender - Songs/x01/Normandie - You Are Here.mp3
2015-06-01 12:15:41   W   msg:Could not load metadata because could not open file #!/usr/local/centovacast/bin/nextsong soundstorm 5a29a7ea5fdd58f2ab349fe3d2b4eaa2 sctrans2next
2015-06-01 12:15:41   E   msg:Failure converting filename to metadata Premature end of data (*/%TIT2.) 2015-06-01 12:15:41   E   msg:Failure converting filename to metadata Premature end of data (*/%TIT2.) 2015-06-01 12:15:41   E   msg:Failure converting filename to metadata Premature end of data (*/%TIT2.) 2015-06-01 12:15:41   E   msg:Failure converting filename to metadata Premature end of data (*/%TIT2.) 2015-06-01 12:15:46   I   msg:[UVOX2] 17512644 Sending metadata 3902 [654 bytes] content="

I don´t know if this is the reason.

Using the newest Centova and Shoutcast v2
Before i used Shoutcast v1, this runs around 8 month without any problems.

Have any one this errors too?

Me once more,

here a screenshot. Listeners count drops without any reason for me. Server works fine.

sc_trans is known to act up if there's issues with it sending titles which may be contributing to the issue you're having. as sc_trans is no longer supported by SHOUTcast since it was sold, there's basically no solution for any issues relating to it and you're probably better off looking at changing to use the Liquidsoap based auto-dj solution.


the other thing that I think you're describing is where the 2.x DNAS just appears to randomly stop responding but is still actually running, not that you'd be able to know the difference when it's run under Centova. though in one case of that issue being reported, it was seemingly being triggered by issues with using sc_trans as the source, but that was a one off to my knowledge.

if that is what is happening, then there is no fix for the issue as it's not been able to be replicated and I'm only officially aware of 3 people having seen the issue with official release builds. whether or not any of the changes that will be present in the next DNAS release help to resolve the issue or not I do not know as for such an issue, unless I can reliably reproduce it or get some idea of what is causing it, it cannot be fixed.

and to my knowledge, you might be the 4th person to possibly be seeing the issue that's made some attempt to report it, though a DNAS issue should generally be reported to SHOUTcast or you host (and they then contact us [SHOUTcast]) to be able to look into it (as I don't often check on these forums apart from around the time of a newer DNAS being released.

Thanks for your helpful answer! Now i get back to v1, works perfect for me.

that doesn't help in determining what the issue is so it can be fixed. so going back to 1.x is just not a 'solution' and I cannot stop you doing that but going back and using 1.x is as bad as still using IE6 to browser the internet. as 1.x over 10 years old, there are number of open security issues present with using it as well as it just not being compatible with modern HTML5 players, so if that's something you're happy with then so be it but from my view point, I now have even less chance of determining the cause of the issue let alone trying to fix it for the few that are experiencing it.