[Server] 2.1.7 released

NOTE:  Database changes are required for this upgrade.  During the upgrade process you will be prompted for your root mysql password.  If you don’t remember this password you may have set it as the same as the bluecherry password during installation.  You can run ‘sudo cat /etc/bluecherry.conf’ to see what the bluecherry database password is.  It is highly recommend that you test the connection to mysql by running this command:

 mysql -u bluecherry bluecherry –execute=”select value from GlobalSettings where parameter=’G_LAST_CURRENT_VERSION’;” -p

You will be prompted for your root mysql password.  If you successfully enter it you should see something that looks like this:

| value       |
| 1:2.0.2-1 |

Once you have the root mysql password, follow the instructions below to upgrade.

This release focuses on problems where events weren’t deleted properly causing the filesystem to become full.  This release also works on improving IP camera connectivity problems that have been causing problems for the past few releases.

Information on how to upgrade to this release can be found on our Knowledge Base.

Questions or Comments?  Visit our new community page community.bluecherrydvr.com

The following bugs were fixed in this release:

* Installation fixes
* Upgraded toolchains
* Fixed MySQL-related crashed
* Moved from libav to latest ffmpeg
* Fixed motion detection and streaming errors
* Improved motion detection performance
* Default back to UDP now that it works better
* Filtered some bogus error messages
* Fixed locking problems
* Various cleanups
* Fixed double call-trace on SIGABRT

* New call-tracing implementation
* Improved media cleanup speed
* Fixed cleanup of events
* Implemented available recording time estimation
* Fixed motion threshold ranges
* Changed username used by bluecherry services to “bc-services”
* Fixed logging issues and implemented message de-duplication
* Fixed keep-alive request for ACTi cameras
* Fixed upgrading and downgrading from 2.1.5
* Added safeguard against reserved username reuse
* Improved logging implementation
* Add DB cleanup at startup
* Misc. bugfixes
* Fail gracefully on event start if DB connection is lost
* Bug #127: Fixed pre and post-recording duration
* Updated build environments
* Internal syslog wrapper API fixes
* Do not log to /var/log/syslog
* Available recording time estimation now done on-the-fly
* Fixes to license checking code

 The following features were added in this release:

* None