SHOUTcast DNAS 2.4.1 (Build 165) 29th October 2014

[DrO]

This build is our new update and introduces new features as listed in the “Changes” section below, as well as addresses bugs reported in the previous build. It is recommended where possible to update to this build over any previous v2.x builds due to the stability and other compatibility improvements it provides.

This release is now available for the following platforms:

• Windows 32-bit (Windows 2000 and up)
• Windows 64-bit (Windows XP64 and up)
• Linux
• Linux 64-bit
• BSD (8.x)
• Raspbian (Raspberry Pi)
• Mac OS X (Intel)

Downloads

You can download the updated version of the DNAS from the main download page here for all of the supported versions.


Changes

Build 165 (29th October 2014):

• Fixed the DNAS not finding cacert.pem which breaks all DNAS-YP connectivity due to issues processing relative filepaths

Build 164 (27th October 2014):

• Added features relating to the 'DNAS+ for CDN' streaming solution
• Added ability to preserve the peak listener numbers for a stream between DNAS sessions e.g. when updating the DNAS (subject to conditions) - this requires the stream being publically listed and will be disabled if found to be abused!
• Added experimental support to allow streams using 1.x source clients to be able to provide stream branding artwork via 'artworkfile' and 'streamartworkfile' configuration options (this enables basic stream branding artwork support for legacy 1.x based streams subject to client support [as below] - for 2.x based streams, the source should already have the ability to provide the stream branding and now playing artwork)
• Added ability to provide artwork to 1.x clients via the legacy in-stream metadata system when provided from a 2.x source or when using the experimental support mentioned above (subject to clients supporting this feature - see the wiki for more information)
• Added 'email' configuration option so hosts can provide a generic contact address (which is used during authhash creation / updates if not manually specified)
• Changed YP connections to use HTTPS - this means a valid cacert.pem must be present in the same folder as the DNAS program file otherwise the DNAS cannot list streams
• Changed file permission defaults on non-Windows builds to be more consistent between the different APIs internally used for files created by the DNAS
• Changed the update notifications to provide extra information where possible about the update
• Fixed YP connectivity issues introduced during the change over to using libcurl in the 2.2.2 / 2.4 releases e.g. randomly stops updating or prevents the DNAS from being able to close correctly or does not correctly handle cases when the YP is not contactable
• Fixed handling of custom streampaths with parameters (starting with /; or ; ) always providing stream #1 (using /stream/x/ did not experience this issue)
• Fixed rare issue leading to high CPU usage when using a single core non-Windows system
• Fixed rare crash when accessing some of the admin pages on non-Windows builds
• Fixed some IP formatting issues on the admin pages
• Removed remaining ICY support so all client connections are now via standard HTTP requets as 2.4 did (ICY was a HTTP-like protocol)
• Removed the 'disableicy' configuration option for controlling this support (not needed due to the prior change)
• Updated to support newer YP requirements for authhash handling and listing modes as well as related tweaks to the authhash management pages
• Updated to OpenSSL v1.0.1j
• Return of the BSD 8.x build (if people don't use this, then it will be dropped permanently)
• Other miscellaneous code changes, improvments and related documentation updates (including handling immediate segfaults on start-up)

Getting Started

If you already have a running instance of the 2.x DNAS then there should not be any issues with replacing your current version with this new version.

If this is a new install then make sure to read through the information in 'Readme_DNAS_Server.html' and the related documentation as well as considering using the setup mode which should make it easier to get started over all prior 2.x builds (and v1 based releases).

Finally, all current copies of the documentation are included with the installer / archive and is the recommended point of reference for this release. The information found online at http://wiki.shoutcast.com/wiki/SHOUTcast_Broadcaster for the DNAS server only relates to the v2.0 (build 29) release (this will be updated by the end of October).


Reporting Issues

If you do come across an issue with the DNAS, then please do post in this thread with as much information as possible about what you're doing at the time, the system you are using and anything else which will make it easier to understand what is or isn't going on with your install.

Posts relating to authhash management issues will be ignored as this is not the thread for posting such issues.


Known Issues

The following are known issues with the current 2.x DNAS release that are not currently fixed / fully confirmed as needing to be fixed (i.e. intended behaviour):

1. The configuration builder has not been fully updated for this release i.e. not all new options are available. This will be resolved in a later update and does not affect most configuration aspects if this mode is used.
2. Under sustained high numbers (1000's) of concurrent client connections, the DNAS server may in rare scenarios crash / segfault. This is primarily due to the networking methods currently used not scaling as well to the 1000s of concurrent client connections as desired compared to the need for more portable code between the platform builds. This requires completion of a networking stack re-write (no eta) and should not generally happen under most expected usage (most stations never break a few 100 concurrent listeners let alone 1000s at the same time).
3. The change of 'disableicy' from 0 to 1 may cause some clients not to show the current title anymore. Setting disableicy=0 will allow the prior behaviour at the expense of breaking default compatibility with Flash and HTML5 audio players. See http://forums.shoutcast.com/showpost...08&postcount=7 for more on what you can do currently and what will be done in the 2.4.0 build.
4. Some Centova setups experience a crash when the logs are rotated. For some using the Linux 32-bit version helps as the issue has only been seen with the Linux 64-bit release. This is due to incorrectly handling invalid log / w3c files and if you have any 0-byte files in your log folder, this issue is now fixed as of the 2.4.0 DNAS release.
5. When attempting to update / remove an authhash, some installs will experience a 462 error (which is due to an issue with the integration of libcurl into the DNAS). Contact support with the authhash and the details you require to be changed. Additionally this may cause a failure to be listed or you will see generic 400 error messages.
6. In some setups, disconnecting a source may cause the DNAS to crash - the probably cause of this has been identified but a fix still needs to be implemented.
7. The advert and metrics code (when enabled) is new so there may be some minor issues so keep a look out for updated DNAS versions!
8. In some setups, the YP connectivity may either fail to start or will randomly fail after an unspecified time. This is an implementation issue related to changing over to libcurl in 2.2.2. A fix will hopefully be available for the 2.4.1 update.

Discussion about the previous version of the server including changelogs can be found in the following threads

• GM (Build 147)
• GM (Build 123)
• GM (Build 109)
• GM (Build 107)
• GM (Build 29)
• RC2 (Build 28)
• RC (Build 27)
• Beta (Build 18 + 19)
• Beta (Build 17)
• Beta (Build 13 + 14)
• Beta (Build 10)
• Beta (Build 7)

[DrO]

*new version bump*
note: the main site is showing 2.4 as the version but the download is 2.4.1 (will be fixed)

this build should resolve the remaining YP connectivity issues that were unfortunately introduced with the change over to using libcurl in the 2.2.2 and 2.4 releases e.g. if there is a YP issue, 2.4.1 will not lock up like has been seen with 2.2.2 and 2.4.

otherwise it's the general tweaks and improvements, including the start of support for 1.x clients to be able to receive artwork and for 2.x clients to receive stream branding artwork when you're limited to using a 1.x source client (the wiki will be updated over the coming week to detail how that all works).

enjoy!

[WizardX]

We will upgrade later on this night. Thanks!

[milosz]

By "main site" I assume you mean http://www.shoutcast.com/broadcastnow ...?

[WizardX]

I have the cacert.pem that came with the install file in the running directory, but it gives me errors:

2014-10-28 00:05:18 ERROR [YP] Request [https://yp.shoutcast.com/yp2] failed, code: 77 [error setting certificate verify locations:
CAfile: /cacert.pem
CApath: none]

Could it be possible that it looks from the running dir? On my systems shoutcast is being started from initscripts. Maybe it can't find it because of that? Is it possible to set it with a variable in the config?

[edit]
a symlink in the / dir worked perfectly

[DrO]

milosz: yes that's what i mean by the "main site".

WizardX: ok, will need to check that out as that's not at all expected. there isn't any option to override the location of the file as it's only meant to be there as a fall back for the in-memory approach we were hoping to have done for this release but it wasn't stable to use in time for this release.

btw, did you get any warning message appear on loading relating to the file not being able to be found ?

[WizardX]

@DrO: Not when loading just that error during operations.

[DrO]

ok, that's a bit strange as the checks use the same code. will follow-this up with you over the next few days once i've had a chance to try things out a bit more.

[WizardX]

All right, untill now everything seems to be running smoothly so no stress

[DrO]

i believe we'll be providing an updated DNAS build tomorrow as the search for the cacert.pem local to the sc_serv program file doesn't work at all well on non-Windows builds when running it via commands from other locations than where the DNAS is installed (which i think is an issue which was seen with sc_trans when run as a daemon due to how the current directory was different).

[DrO]

the patched build is now queued for upload so it hopefully will be uploaded in a few hours time. sorry about any inconvenience this has caused people with the update (is something else that has now been added to the pre-release tests - running the DNAS from a different path from where it's stored to ensure it's loading things correctly which was a fix already in place when running in daemon mode).

[DrO]

*new version bump*
build 165 is now available to resolve the issue seen with build 164 where it cannot correctly find the cacert.pem file which breaks DNAS-YP connections. there are no other changes in this new build.

[max055]

Hi,
I have the same problem, but after updating to 165 version, server not starting anymore, im reciving this error.
My OS is Centos 6.5


2014-10-29 20:27:19 WARN [CONFIG] Could not find `../server.conf' - looking for config file to load...2014-10-29 20:27:19 INFO2014-10-29 20:27:19 INFO *********************************************************************2014-10-29 20:27:19 INFO ** SHOUTcast Distributed Network Audio Server (DNAS) **2014-10-29 20:27:19 INFO ** Copyright (C) 2014 Radionomy SA, All Rights Reserved. **2014-10-29 20:27:19 INFO ** Use "sc_serv filename.conf" to specify a config file. **2014-10-29 20:27:19 INFO *********************************************************************2014-10-29 20:27:19 INFO [MAIN] SHOUTcast DNAS/posix(linux x64) v2.4.1.165 (Oct 29 2014)2014-10-29 20:27:19 INFO [MAIN] PID: 47812014-10-29 20:27:19 ERROR [MAIN] Aborting as no valid config files could be found.2014-10-29 20:27:19 ERROR [MAIN] Try running setup mode to create a valid config file.2014-10-29 20:27:19 ERROR [BAN] Could not open global ban file `sc_serv.ban' for writing2014-10-29 20:27:19 ERROR [RIP] Could not open global rip file `sc_serv.rip' for writing2014-10-29 20:27:19 ERROR [AGENT] Could not open global agent file `sc_serv.agent' for writing2014-10-29 20:27:19 INFO [MAIN] Shutdown

Can you check this

Regards

[DrO]

i'd need to know where sc_serv is on the machine and the command used to start it (including if it's from a different folder from where sc_serv is located).

though you will most likely need to change the relative path being used or specify the full path to the server.conf file.

[edit]
ignore the above, we're going to re-work the changes made in build 165 so relative paths will work again like in build 164 as it's breaking too many init scripts and usage via 3rd party control panels like from Centova.

[ram130]

Thanks. Good update, I'm hoping this finally fixes no title showing in the Roku shoutcast app finally(showed multiple IE connects in admin page). Also, I suppose no ETA on the rework version for 165? I know, it will come when ready.

Anyway will get to test 165 as soon as my host updates to it. Just pinged them.

[DrO]

is best to go with the 166 build (once released later today) than 165 as per my post above.

[DrO]

v2.4.2 released which fixes the starting issues which were experienced with the previous 2.4.1 release.