Syncplify Developers Blog

Release notes and blog by the developers at Syncplify

Tag ram

Syncplify Devs
July 31, 2023

Syncplify Server! v6.2.6 released

Importance of this update: NORMAL
What’s changed?
  • The Status/History tab of the Dashboard page in the Admin UI now shows each node’s status and CPU/RAM usage in a clearer and more pleasant way
  • When logging detail is configured to TRACE level, each LIST command received by the client software now also logs the number of directory items returned to the client in the response
  • Fixed an inconsistency in the way variables were processed in banners, titles, etc…
What’s new?
  • The backup verb has been added to the ss6-webrest executable, to export full configuration backups via command line
  • All virtual file system (VFS) types can now automatically identify file paths and names sent by buggy client software in encodings other than UTF8, and automatically convert them to standard UTF8

IMPORTANT NOTE: those who are running the “worker” system service under a different account (not System or LocalSystem) will need to re-configure the service to run under such account after upgrading from any version number <= 6.1.12)

Upgrading from v6.x.y is a simple and fairly automatic process: simply download the latest version from the official download page, and install it over the existing version, all of your settings and license will be kept.

If, instead, you’re upgrading from an older (v4/v5) version, you find the upgrade instructions in our knowledge base.

Thank you all for trusting our software with your secure file transfers!

Leave a comment InRelease Notes Syncplify Server! WebClient!
Syncplify Devs
July 19, 2023

Syncplify Server! v6.2.5 released

Importance of this update: MEDIUM
Fixed
  • A glitch in the Admin UI could occasionally give the impression that updates to the HTTPS/WebClient! weren’t persisted in the database (they were but without visual feedback)
  • Counter of cleaned up items in the block-list (only in log files) was wrong
Added
  • System-wide used RAM (memory) percentage indicator, per node, has been added to the dashboard
  • A few additional variables have been added to those you can use to customize the various protocol handler banners

IMPORTANT NOTE: those who are running the “worker” system service under a different account (not System or LocalSystem) will need to re-configure the service to run under such account after upgrading from any version number <= 6.1.12)

Upgrading from v6.x.y is a simple and fairly automatic process: simply download the latest version from the official download page, and install it over the existing version, all of your settings and license will be kept.

If, instead, you’re upgrading from an older (v4/v5) version, you find the upgrade instructions in our knowledge base.

Thank you all for trusting our software with your secure file transfers!

Leave a comment InRelease Notes Syncplify Server! WebClient!
Syncplify Devs
March 21, 2023

Syncplify Server! v6.0.24 released 🚨

Importance of this update: CRITICAL HOT-FIX
Fixed
  • Fixed vulnerability in the SSH2/SFTP protocol handler that could cause memory leaks and, under certain circumstances, even a DoS situation
  • Fixed several minor/cosmetic bugs in the HTTPS protocol handler (WebClient! UI)

Upgrading from v6.0.x is a simple and fairly automatic process: simply download the latest version from the official download page, and install it over the existing version, all of your settings and license will be kept.

If, instead, you’re upgrading from an older (v4/v5) version, you find the upgrade instructions in our knowledge base.

Thank you all for trusting our software with your secure file transfers!

Leave a comment InRelease Notes Syncplify Server! WebClient!
Syncplify Devs
March 13, 2023

Syncplify Server! v6.0.22 released 🔔

Today we released Syncplify Server! v6.0.22; here’s what’s new and improved in this version.

Importance of this update: IMPORTANT
Fixed
  • PUT/GET operations are now logged correctly, even when the client issues a STAT command on the open file handle before the file-transfer is finished
  • Fixed a memory leak in the session manager that only affected the ARM build of the software (x86-64 Windows and Linux versions were not affected)
  • Fixed a small memory leak in the scripting and event-handling subsystem that affected all builds on all platforms and could cause memory exhaustion over time if this subsystem was actively used
  • Fixed importing LDAP server profiles from old V5 backups
Improved
  • Optimized global server configuration loads/reloads for speed and reduced memory footprint
  • General code cleanup, removed unused/old libraries and all references to MongoDB (even in the comments)
  • Usernames are no longer treated as case-sensitive, as POSIX compliance does not require case-sensitivity for usernames (only for passwords)
Added

Upgrading from v6.0.x is a simple and fairly automatic process: simply download the latest version from the official download page, and install it over the existing version, all of your settings and license will be kept.

If, instead, you’re upgrading from an older (v4/v5) version, you find the upgrade instructions in our knowledge base.

Thank you all for trusting our software with your secure file transfers!

Leave a comment InRelease Notes Syncplify Server! WebClient!
Syncplify Devs
March 12, 2023

Tackling memory leaks… the Go way

We recently discovered two small memory leaks in our worker process, one that affected only the ARM architecture build, and one that affected all builds regardless of the CPU architecture (but only if you use scripting and event-handling). Although both of them were very small and limited in scope, over long periods of time they could lead to the unwanted allocation of a significant part of your system memory.

As many of you know, Go has a pretty nifty garbage-collector, but that doesn’t mean that all memory issues are magically prevented. Programmers still have to be clever with allocations and references.

Long story short, we spent the last week delving in pprof to hunt down, identify, and resolve these two memory leaks, and here’s the result:

As you can see, after our fixes now the worker process uses a stable amount of memory (~120 MB) and CPU (~0.7%) under constant load (~750 Mbps sustained transfer rate from 3 concurrent clients). The chart above was acquired over an observation period of 24 hours under stress-test conditions.

These fixes will be incorporated into version 6.0.22.

Leave a comment InGeneral Syncplify Server!