Release Notes - Version 5.0

5.0.2 (2025-09-09)

  • Set client version to 5.2.2.3715

  • Fixed installation error: “Unable to move file/directory (1): /usr/bin/mv /opt/teamdrive/webportal/agent” (WEBCLIENT-490).

  • Added LaunchAgentTemplate setting which is a template for the “Launch Agent Script”: start-td-service-apache.sh. Note that as of this version, the Launch Agent Script may no longer by altered directly, and will be overwritten on update to version 5.0.2 (WEBCLIENT-494). See LaunchAgentTemplate for details.

  • Containers can now be disabled and enabled on the Admin Console (WEBCLIENT-488). If disabled, the user will get a message when attempting to login to the Web Portal.

  • Container status is now checked every 2 minutes in order to determine the number of running/active containers when enforcing the MaxActiveContainer setting (WEBCLIENT-502).

  • An update notice will no longer appear in the Admin Console and yvva console if the current Agent version is higher then the required Agent version, as specified by the RequiredAgentVersion setting (WEBCLIENT-498).

  • The External authentication settings: AuthServiceEnabled, AuthLoginPageURL and AuthTokenVerifyURL, are deprecated and will be removed in a future version (WEBCLIENT-505).

    Note: on upgrade AuthServiceEnabled will be automatically set to False. This may cause a disruption of the Web Portal service. If this is the case, set AuthServiceEnabled=True until the problems can be solved by upgrading the External Authentication Service and the TeamDrive Clients to the latest version. Also note that after upgrade, user’s of external authentication must login using their email address.

  • The Web Portal will now detect if the user of a container has been deleted or recreated (WEBCLIENT-497).

    A new auto-task, Delete Unused Containers checks all containers regularly, to determine if the user of the container is still valid. If not, the status of the container will be set to either “user-not-found” or “user-created”. Containers marked as such will be deleted after 30 days.

    If you attempt to login and the user of the container is no longer valid, the status of the container will also be set accordingly.

    In the Web Portal Admin Console, in the “Container List”, you can list all Containers with invalid user, by selecting “User not Found” from the popup in the search bar.

  • The auto-tasks: Remove Idle Containers and Delete Container Storage have been removed.

    The task performed by Remove Idle Containers is now done by Swap Containers which will swap container storage to backup when RemoveIdleContainerTime has expired.

    The task previously peformed by Delete Container Storage is now done by the new auto-task Delete Unused Containers which will deleted containers that have exceeded the ContainerStorageTimeout timeout. All container data is removed in this case, including backups.

  • In some cases, when an Agent is not reachable the Web Portal could get into an a loop in which the Agent was contantly stopped and restarted due to a race condition in parallel requests from the Web UI (WEBCLIENT-507).

  • The Web Portal now checks the teamdrive.pid file of the Agent to ensure that the Agent is not running, if the database indicates the Container is stopped. If the Agent is still running according the teamdrive.pid file the Web Portal will try to stop the process. If this is not possible, an error will be generated (WEBCLIENT-509).

    Both the process ID and the command line are now checked to verify if an Agent is running. The command line must contain the username of the Agent container.

    In general, if the Web Portal is not able to stop a Container, it will generate an error, and follow up tasks, for example backup, will be cancelled.

5.0.1 (2025-01-28)

  • Set client version to 5.2.1.3665

  • Changed $round() calls to be compatible with yvva 1.6 (WEBCLIENT-479).

  • Certain strings in the Web UI were not being displayed in the correct language (WEBCLIENT-477).

  • If a user has no Web Portal (i.e. no Web Portal is specified by the Provider of the user), then the user will now receive an appropriate error message (WEBCLIENT-466).

  • When an Agent container is swapped to cloud storage (see EnableSwapping), the entire installation is now compressed and archived before upload. This ensures that all changes are synchronised, even if this was not completed before backup (WEBCLIENT-471).

    The TempArchivePath setting which specifies a directory to be used to create and unpack archives when using container swapping.

Automatic TeamDrive Agent Update

The Web Portal is now able to update the TeamDrive Agent automatically, without a complete upgrade of the Web Portal software (WEBCLIENT-449).

Update information is downloaded from the URL stored in the AgentUpdateInfoURL setting. The default is: https://agentrelease.teamdrive.net/wpagentrelease.json.

The contents of the wpagentrelease.json file is as follows:

{
      "agent-version" : {
    "<web-portal-version>" : "<agent-version>",
    "<web-portal-version>" : "<agent-version>",
    "<web-portal-version>" : "<agent-version>",
    ...
  }
}

With this format you can specify which version of the TeamDrive Agent is the current version for a particular Web Portal version. If the Web Portal does not find its version in the file, then the next lowest version is applied. However, a version older than the default value of RequiredAgentVersion will never be installed. This is the value of CURRENT_AGENT_VERSION which is hard-coded with the release of a Web Portal version.

A new auto-task: “Check For Updates”, downloads the wpagentrelease.json file and updates the RequiredAgentVersion setting accordingly.

To perform the actual upgrade automatically, the yvva function auto_update_agent must be executed as follows:

yvva --call=auto_update_agent --config-file="/etc/yvva.conf"

The command must be executed with root privileges.

The auto_update_agent function checks and automatically installs the TeamDrive Agent version as specified by the RequiredAgentVersion setting.

However, auto_update_agent only performs this operation if the following two conditions are not met:

  1. The setting AutoUpdateAgent must be set to True, and
  2. the function is called between 2:00 and 4:00 AM.

If not, then auto_update_agent does nothing. So auto_update_agent can be called regularly (once every hour for example) and it will only do an update if automatic upgrade is enabled, and it is early in the morning.

Note that the setting RequiredAgentVersion was previously named MinimumAgentVersion. In addition, ContainerImage has been changed to CurrentAgent. Both settings are now read-only.

The Web Portal will only upgrade the Agent version automatically. If the version specified in the wpagentrelease.json file is lower than the current Agent version then it will be ignored. It is possible to force a downgrade by prefixing the version number of the Agent in the wpagentrelease.json file with ”!”.

Note that containers cannot be downgraded, and will may cease to function if they were started with a older Agent version then before. Such containers must be deleted manually or they will remain unusable until an Agent with a later version is installed.

During upgrade, all other auto-tasks will be disabled. Messages to this affect may appear in the log file as a warning. If upgrade is started and an auto-task is running, then the update process will wait for up to 40 minutes for the task to complete. If the task does not complete in time, upgrade will be aborted and retried in 24 hours.

Setting BuildBinaryName is deprecated and has been removed.

5.0.1 (2024-MM-DD)

  • Set client version to 5.2.0.3623

5.0.0 (2024-08-09)

  • 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 Web Portal is based on the last release 3.1.3 and only includes small changes (see below) and the current client version (see below).
  • HMAC-SHA1 authentication can now be selected for accessing the Registration Server API (WEBCLIENT-463).
  • When using External Authentication there some cases where the login name (usually an email address) that was entered in TeamDrive was not always pre-filled in the External Authentication login page. In addition, if the login name is not an email address, then the field will not be set to read-only.
  • If AllowedProviders is not set then the redirect to the appropriate Web Portal of the user was not always working correctly (WEBCLIENT-465).
  • Set client version to 5.2.0.3615
  • Admin Console: Added a “Restart” button to the details page (WEBCLIENT-469).