CPU usage limiting, bugfixes, stability improvements and even more in our new BitNinja versions (V3.7.0 and 3.7.1)

Most systems will automatically update, if you have specific settings or applications preventing automatic updates, you can follow our documentation on how to proceed to have the latest version installed.

The details:

• Added a config option called cpuUsageLimit in the System module, under the resources section.
  • You can set an upper CPU usage limit that BitNinja is allowed to consume, in percentage.

• Fixed an issue regarding the crash report uploading.
  • Logging is pretty important, so this fix ensures we are not missing any of them.

• Fixed an issue regarding the SslTerminating cert mining when no certs were found.
  • Another edge case issue has been squashed!

• Startup error logs are now more verbose instead of “Failed to access the API server“ log.
  • Yet another log-related fix, this makes the debugging process a lot easier!

• Extended the filesystem cache cleaning mechanism, ensuring the database size is kept within limits.
  • Under some specific circumstances, this database could consume more space than it should have. This has been fixed.

• The filesystem cache is now re-enabled if the size is below the filesystem cache size limit.
  • Previously it was kept off, but combined with the size fix, this is no longer necessary.

• Fixed an issue regarding the WAF when HEAD requests were hanging.
  • Let's make sure we are not hanging anything that should not be hung. 🙂

The newest BitNinja versions (V3.7.0 and 3.7.1) brought CPU usage limiting, stability improvements, and bugfixes.

If you'd like to read more about previous release notes, you can 🔎find them here. Alternatively, if you would like to see your feature request show up here, don't forget to cast your🙋‍♂️Vote