Announcement

Collapse
No announcement yet.

SHOUTcast DNAS 2.4.2 (Build 167) 30th October 2014

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • SHOUTcast DNAS 2.4.2 (Build 167) 30th October 2014

    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 2.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 167 (30th October 2014):
    • Fixed issues with not finding cacert.pem in the same location as the DNAS program file which was preventing YP connectivity working (2.4.1 build 164 specific)
    • Fixed broken relative config file handling not working correctly with init scripts and 3rd party control panels (2.4.1 build 165 specific)
    • Changed some of the log and admin page output to better show the actual filepath being used for log and configuration files (helpful for determining path loading issues)
    • Changed handling incase the cacert.pem file cannot be found to be more forgiving for the time being (futher changes will follow in later builds)
    • Removed 'Error writing to console' log messages when screenlog=1 (default) and the shell the DNAS was started in is closed whilst the DNAS is still running e.g. due to OS defined timeouts - always use screenlog=0 if running the DNAS and you do not need it sending log output to the console



    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 1.x 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 build 29 release (this will be updated by the end of October-ish).


    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 probable 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.
    9. The banning actions may not work correctly in some cases (primarily dependent upon details provided by the listener connection details).



    Discussion about the previous version of the server including changelogs can be found in the following threads
    WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

  • #2
    *new version bump*

    note: the main site is showing 2.4 as the version but the download is 2.4.2 (will be fixed)

    this build resolves the issues which affected both of the 2.4.1 builds, including loading via init scripts and 3rd party control panels (which has been confirmed as ok prior to releasing with Centova).
    WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

    Comment


    • #3
      Smylink removed, new version installed, error gone
      It seems all working well.
      Deep Radio - We are Dance! - 24x7 dance, house, techno and chill music - https://deep.radio

      Comment


      • #4
        Big thanks for FreeBSD version! On my FreeBSD 9.1 amd64 works fine.

        Comment


        • #5
          well that's good it seems to run ok, just a shame there's no trace of it in our listings...
          WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

          Comment


          • #6
            So I talked with my host and they say they ran the update script but still 147. They say it pulls whatever is on Centova servers. So I'm stuck waiting with no eta on when they'll update their side. Centova can be a pain at times.
            Ramon

            Comment


            • #7
              the Linux 32 bit version contains 64 bit binaries...:


              sc_serv: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, BuildID[sha1]=0x1a33bb5b81dc5b6214063497c453744c230dc8f1, stripped

              Comment


              • #8
                Yes, Sir. This is true.

                Comment


                • #9
                  Hi ram130,

                  Even though Centovacast doesn't always update Shoutcast2 at the same time, you can download the binaries from shoutcast.com, stop your stream, replace the binaries with the ones you downloaded from shoutcast.com and then start your stream again.

                  Be sure to back up your existing binaries first, in case something goes wrong ;-)

                  I always backup sc_trans2 and sc_serv2 before running any Centova updates. Good thing I did this time, as bashelst has noted, the update from Centova pulls down a 64bit version of the sc_serv binary, that didn't work for me on on my 32bit Centovacast server. I suspect Centova just grabbed and 32bit and 64bit binaries from shoutcast.com without checking...

                  Comment


                  • #10
                    there was a caching issue with the official linux 32-bit link providing the earlier incorrect copy despite the correct version having been uploaded. it should now be working correctly - the downloaded archive size should be 2,898,219 bytes.

                    as for Centova updates, there is information on their forum on how to force a manual update of the DNAS. additionally updating to Centova 3.1.1 will also correct what it is going to attempt to download (as we've changed our download links - though that won't help the badly cached linux 32-bit version) which would explain why it's not pulling down the new versions.
                    WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

                    Comment


                    • #11
                      solved indeed:
                      sc_serv: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, BuildID[sha1]=0xb6d8ed0c0443c4ba732871858340032c1bf28997, stripped

                      Comment


                      • #12
                        a new Mac build has been uploaded and is marked as build 168 - this is purely to resolve issues with the Mac build not finding files correctly relative to the DNAS program file. no other changes have been made and all other builds are not affected by this issue.
                        WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

                        Comment


                        • #13
                          Stream Restarts

                          Hello,

                          since updating to Build 167, we have from time to time restarts of our streams. The log files give no clear entry. The stream starts then just new and it does not come to the interupt of listeners.

                          But if restart not will work, we receive serious problems.

                          We are using DNAS 2.4.2 Build 167, Centova 3.1.1

                          Shoutcast simply crashing without leaving any log message behind about it. Centova is looking as well.

                          Maybe a Bug? I cant find something in forum about it.

                          Thanks in advance

                          Comment


                          • #14
                            sorry but i'm really struggling to understand your message. when is it crashing ? what are you doing to make it crash (that is not at all clear from your message). unless you're trying to describe point #6 from the known issues (http://forums.winamp.com/showthread.php?t=373139#known)
                            WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog

                            Comment


                            • #15
                              Hello everybody,

                              Same case as McLemmi, Linux 64bit server running Centova Cast 3.1.1 and we also upgraded yesterday to the latest version of DNAS 2.4.2 b.167 (coming from the year 2011 DNAS version).
                              We have 7 radio stations of our group are currently "trying" to broadcast. I say "try" because since we installed the latest version of DNAS some stations are restarting even every 30 minutes.
                              Centova Cast is dispatching the alert email informing us about it: "This message is to inform you that your streaming server went down in the past few minutes, but has been restarted successfully".
                              In fact, sometime it doesn't even restart successfully!

                              Some of the 7 radio stations are suffering more restarts (even every 30 minutes), and some "just" a couple in the last 12 hours.

                              Also banning IPs seems not to be effective. The IPs are being banned and kicked out, but allowed to connect again right after.

                              Finally, for few hours (then this error red line stopped appearing) also the below error lines were appearing repeatedly in the logs of ll the radio stations:
                              "2014-11-12 08:51:59 ERROR [YP] Stream #2 connection attempt failed. YP2 error code is 493 [Internal error - unable to acquire data source]
                              2014-11-12 08:52:00 ERROR [YP] Stream #1 connection attempt failed. YP2 error code is 493 [Internal error - unable to acquire data source]
                              2014-11-12 08:52:02 ERROR [YP] Stream #3 connection attempt failed. YP2 error code is 493 [Internal error - unable to acquire data source]
                              2014-11-12 08:52:02 ERROR [YP] Stream #4 connection attempt failed. YP2 error code is 493 [Internal error - unable to acquire data source]".


                              Seeing the severity of the issue, we will now roll back to the old version dated 2011, which we were using until yesterday.

                              Hopefully rolling back won't be an issue???

                              Thank you and have a good day.

                              Best Regards

                              EDIT:
                              In order to provide more complete info, please find below the first lines of the Log, when WE restart from Centova Cast any of the streams:

                              =============
                              2014-11-13 10:01:12 WARN [CONFIG] Invalid item on line 22 of ../xxradioxx/etc/server.conf -> `yp1debug'
                              2014-11-13 10:01:12 WARN [CONFIG] Deprecated statement found on line 88 of ../xxradioxx/etc/server.conf -> change autodumpsourcetime_1=30 to autodumptime_1=30
                              2014-11-13 10:01:12 WARN [CONFIG] Invalid item on line 102 of ../xxradioxx/etc/server.conf -> `yp2'
                              2014-11-13 10:01:12 WARN [CONFIG] Invalid item on line 164 of ../xxradioxx/etc/server.conf -> `specialfiletmpdir'
                              2014-11-13 10:01:12 INFO
                              2014-11-13 10:01:12 INFO [MAIN] SHOUTcast DNAS/posix(linux x64) v2.4.2.167 (Oct 30 2014)
                              2014-11-13 10:01:12 INFO [MAIN] PID: 15810
                              2014-11-13 10:01:12 INFO [MAIN] Saving log output to `/usr/local/centovacast/var/vhosts/xxradioxx/var/log/error.log'
                              2014-11-13 10:01:12 INFO [MAIN] Automatic log rotation interval: 1 day
                              2014-11-13 10:01:12 INFO [MAIN] Loaded config from `/usr/local/centovacast/var/vhosts/xxradioxx/etc/server.conf'
                              2014-11-13 10:01:12 INFO [MAIN] Calculated CPU count is 4 -> using all available CPUs
                              2014-11-13 10:01:12 INFO [MAIN] Limited to 10240 file descriptors [relates to ulimit -n]
                              2014-11-13 10:01:12 INFO [MAIN] Starting 4 network threads
                              2014-11-13 10:01:12 INFO [BAN] Banned 9 IP's from global ban file
                              2014-11-13 10:01:12 INFO [MICROSERVER] Listening for source and client connections on port 8800
                              2014-11-13 10:01:12 INFO [MICROSERVER] Listening for legacy source connections on port 8801
                              2014-11-13 10:01:12 INFO [MICROSERVER] Listening for legacy source connections on port 8019
                              2014-11-13 10:01:12 INFO [MICROSERVER] Listening for legacy source connections on port 8020
                              2014-11-13 10:01:12 INFO [MICROSERVER] Listening for legacy source connections on port 8021
                              2014-11-13 10:01:12 INFO [MICROSERVER] Flash policy file server not enabled

                              Comment

                              Working...
                              X
                              😀
                              🥰
                              🤢
                              😎
                              😡
                              👍
                              👎