Release Notes - Version 5.x¶
5.0.3 (2025-04-29)¶
Added a number of settings that related to outgoing connections (HOSTSERVER-968):
EnableCurlTrace
: Set toTrue
to enable tracing of outgoing network calls(which use libcurl). Output is at the lowest log level enabled.
TraceCurlContent
: Set toTrue
to include the contents of the outgoingnetwork calls (using libcurl) in the trace.
DisableAuthTokenCheck
: Set toTrue
to disable verification of userAuthentication Tokens. In this case the username sent by the TeamDrive client is assumed to be correct. Disabling verification is a security risk.
DisableIPv4
: Set toTrue
to disable the use of IP (Internet Protocol) version4 for outgoing connections.
DisableIPv6
: Set toTrue
to disable the use of IP (Internet Protocol) version6 for outgoing connections.
Fixed a bug in the proxy configuration for outgoing connections (HOSTSERVER-970) made by the Apache module (mod_pspace). The specified proxy was ignored.
The default
ConnectionTimeout
value is now 5 seconds.Fixed bug which incorrectly removed the names of Spaces after creation, even when
StoreSpaceNames
was enabled (HOSTSERVER-967). The missing Space name can now be set in the Host Server Admin Console. Missing Space names will be automatically uploaded by a future version of the client.Admin Console: fixed setting with minute, day and byte values (HOSTSERVER-969). Conversion of values using these units on input was incorrect.
Added “setspace” API call (HOSTSERVER-971).
No longer log a warning when the Host Server’s DH (1.0) Public/Private key is missing or cannot be loaded (HOSTSERVER-960).
Fixed key exchange error that occurred if a test upgrade is performed (HOSTSERVER-965).
The “Process S3 Logs” auto-task will now ignore S3 errors when downloading logs (HOSTSERVER-972). In order to prevent the accumulation of logs in the local file system, already downloaded logs are all processed before downloading further logs from the Object Store. At most 100 logs are downloaded before processing begins.
Added td-log-processing service (HOSTSERVER-973). This service performs the “Process S3 Logs” auto-task when started. The server is only required if the log processing function requires too many resource to be run by the td-hostserver service. In order to use the td-log-processing service you must disable the “Process S3 Logs” auto-task in the Host Server Admin Console. This service is only available on CentOS 9 (or later) systems.
Added setting
S3ExecUploadTimeout
, which is set to 10 GB by default. Files larger than this are uploaded to the Object Store using theaws
executable, if it is installed on the host (see HOSTSERVER-926 below).Added
S3ExecUploadTimeout
, which is set to 30 minutes by default (HOSTSERVER-974). This is the maximum time allowed for uploading a file to the Object Store.The server now logs instances where the client reads past the end of the Space log (HOSTSERVER-957).
When a snapshot fails due to lock timeout the Host Server will now report an error and continue with the next snapshot (HOSTSERVER-976). A snapshot will then only be attempted again, after the “snapshot frequency” time for the Space has past.
5.0.2 (2025-02-25)¶
Added setting
UploadCheckProgressFreq
, see UploadCheckProgressFreq for details.Added background task: “Consolidate Traffic” which consolidates the Traffic and Disk usage Log to one entry per month after one year, and to a yearly entry after 2 years (HOSTSERVER-935).
Fixed Host Server registration error: “RSA public key required” (HOSTSERVER-946).
Fixed problem with publish, unpublish and republish a file in quick succession (HOSTSERVER-868). Attributes such as password and notification user where sometimes not reset on republish.
The background task could hang (in a repeat loop) when uploading a file that is to be uploaded is marked for deletion later (HOSTSERVER-949).
Added setting
ModuleTraceOn
. When set totrue
the Host Server will write a trace path to the “CallTrace” table, for each running Apache process (HOSTSERVER-948). An Apache process must be restarted in order to change this setting.Added setting
UseXForwarded
(HOSTSERVER-947). If set toTrue
the Host Server will accept theHTTP_X_FORWARDED_FOR
andHTTP_X_FORWARDED_PROTO
headers set by a proxy or load balancer.The following setting are deprecated, and have been removed:
TSHSEnabled
,TSHSImportVolumes
,TSHSExecutable
,TSHSMyCnfFile
.Removed the setting:
ImportS3tagFiles
, which is no longer used.Fixed the cleanup of incomplete Cloud Storage uploads (HOSTSERVER-950).
The Host Server will now use the AWS CLI (aws.amazon.com/cli) to upload very large (over 20 GB) files to the Object Store (HOSTSERVER-926). This will work automatically if the
aws
executable is installed in “/usr/bin/”.If ``aws` is not installed, the IP Works library will be used to perform the uploads as usual. Note that this may result in excessive memory (more than 10 GB) usage for very large files.
Fixed upgrade error: Invalid default value for ‘DelayAction’ (HOSTSERVER-951). This error may occur when upgrading on a system that has set the default time zone to something other than UTC.
A number of the “mys3” functions have been deprecated and removed, including: “createbucket”, “activatebucketlogging”, “deactivatebucketlogging”, “getbucketinfo” and “md5check”. All remaining functions now support the options “-ipworks” (HOSTSERVER-945).
Traffic Analyzer: fixed error on empty log files (HOSTSERVER-952).
Data Retention Period and Space names: this data will now be requested from the client if required by the Host Server (HOSTSERVER-954).
Until the information is sent to the Host Server, the Host Server may not be sure whether certains spaces are using a data retention period or not. In this case an appropriate wording is used in the Admin Console: “may have” is used instead of “has a Data Retention Period”.
The storage of space names can now be enabled at the Depot level (HOSTSERVER-805). Moved
StoreSpaceNames
setting from “General Settings” to “Client Settings”.
5.0.1 (2027-07-25)¶
- Fixed error: “An unknown option was passed in to libcurl”, when sending an email by setting the libcurl dependency to version 7.50.0 or later (HOSTSERVER-927).
- Fixed duplicate security headers (X-Frame-Options , X-Content-Type-Options) returned by API (HOSTSERVER-928).
- The Host Server will automatically fetch the RSA/2.0 key from the Registration Server if it does not already have it (HOSTSERVER-929).
- Very old client installations that do not have an RSA public/private key will now receive the correct error code (HOSTSERVER-930). An update to TeamDrive client 5.2.0 is also required in order restore communication with the Host Server in this case.
- Fixed error “Locking: ... before locking: ...” error generated by the S3 Daemon when synchronising log directories with the Object Store (HOSTSERVER-933).
- Fixed a problem when exchanging the new “API Access Key” with the Registration Server (HOSTSERVER-934), see HOSTSERVER-914 below.
Note
The API call verification can no longer be disabled, the setting
APIChecksumRequired
is deprecated, and has been removed.
Note
The setting APISalt
has also be deprecated and will be
removed in a future version. HMAC hashing together with the key stored
in APIAccessKey
must be used in the future. Please contact TeamDrive
if you need support on this issue when accessing the Host Server API.
The following errors that may occur during the processing of the Object Store logs have been fixed:
[Error] [Process S3 Logs]: Data too long for column ‘StateChangeList’ at row 1 (HOSTSERVER-937)
Record: 0, cannot get space ID from Object Key: 112063%2Fsnapshot%2F0.log (HOSTSERVER-938)
Note
Previously setting S3EnableRedirect
to False
disabled the processing
of Object Store log files. This has been changes in version 5.0.1 because
security relavent analysis is now performed on the logs.
- When using the API log, if a request or reply is longer that 65000 bytes, the message is now trucnted to 64000 bytes (HOSTSERVER-939). This is done by removing data from the middle of the message and replacing it with: “[...]”.
- A regression was fixed in the TeamDrive Protocol Version 1 (aka TDP v1) (HOSTSERVER-941). This protocol is only used by TeamDrive version 3 and older client.
Note
The TDP v1 is deprecated and will be phased out in a future version of the Host Server. We recommend upgrading to the latest version of the TeamDrive Client as soon as possible.
5.0.0 (2024-05-21)¶
First release for CentOS 9. Version number 5 for all server products (TeamDrive Registration Server, TeamDrive Host Server and TeamDrive Web Portal) only stands for the common CentOS 9 release. The actual functionality of the Host Server is based on the last release 4.0.8 and only includes small changes (see below).
Meta-data handling: improved atomic update capabilities.
Certain additional security features have been implemented (HOSTSERVER-885). Host Server administrators may ask TeamDrive support for details on these changes.
The Host Server now supports email notifications for downloaded public files (HOSTSERVER-905). The email is sent to a specific TeamDrive user as specified in the TeamDrive App. The email is sent using the Registration Server and requires version 4.7.2 or later.
Added support for API access checking based on HMAC hashing and a local random generated key (HOSTSERVER-914). Switch to the new implementation is automatic as soon as it is supported by the Registration Server.
In order to access the Host Server API you must use the key stored in the
APIAccessKey
setting (without the “$” sign if present in the value). The search arg “authtoken” replaces the “checksum” arg previously used, and the authorisation value is the HMAC-SHA1 value of the request body and the key.For example if you are using PHP use the following code:
$url .= '?authtoken='.hash_hmac('sha1', $request_body, $auth_key);
where
$request_body
is the body of the HTTP request,$url
is URL of the Host Server, and$auth_key
is theAPIAccessKey
as specified above.Implemented support of user authentication tokens (HOSTSERVER-845).
The Host Server getStatistics() API call was failing when the client only sends a version 2000 public key (i.e. when a version 1000 key was not provided).
Fixed error: Operation not permitted: ‘/tmp/td-host-df.out’ (HOSTSERVER-862).
The newspace() API call now supports setting meta data (HOSTSERVER-906).
Increase the Space event log size from 2MB to 12MB (HOSTSERVER-919).
When downloading a published file which requires a password, the number of times you may enter an incorrect password is now limited (HOSTSERVER-847). The limit is specified by the
IncorrectPasswordLimit
.After exceeding this limit, the user is force to wait for a certain amount of time before they may try again. This delay is specified by the
IncorrectPasswordDelay
setting.The new HTML template: “too-many-fails.html”, is used to output an error when the incorrect password limit is exceeded.
Added new shortcut URL paths (HOSTSERVER-846):
- apia: the admin API (statistics and creating spaces)
- apic: the client API (data exchange using TDP v1 and TDP v3)
- apiy: the yvva API (general API for accessing depot and space info)
- tdhs: use ‘tdhs’ (TeamDrive Host Server) instead of ‘primespace’
Fixed recalc Space size when a file that is already on S3 is re-uploaded by the client (HOSTSERVER-850).
Moved
LogFileThreshold
setting to “Resouce Management”.Prevent the s3d from potentially not releasing the Space log lock, and added lock timeouts to s3d and mod_pspace to prevent hanging if a lock is held too long (HOSTSERVER-920).
Added setting
MaxFileUploadSize
. This is the maximum size of files that may be uploaded to the Host Server. The default is zero, which means unlimited. This setting is enforced by the TeamDrive client.Added settings
VolumeCriticalCheck
,VolumeCriticalFileSize
andVolumeCriticalFreeSize
(HOSTSERVER-900). These settings implement the “volume critical check” feature which prevents a single large upload from consuming all free disk space and thereby disrupting the operation of spaces that share the same disk volume on the Host Server. See VolumeCriticalCheck for details.Fixed potential error when adding a file to the “deleted later” list (HOSTSERVER-924).