Panel

Table of Contents

For the UDMG Web Transfer Client, please refer to UDMG Web Transfer Client for Linux Installation.

Upgrading Universal Data Mover Gateway

Upgrading UDMG refers to the increase of a currently installed pre-2.0.x Version, Release, or Modification level of UDMG (1.5.x, 1.4.x, 1.3.x, 1.2.x) to UDMG 2.0.x.

Note

title	Note

Starting with UDMG version 2.0, a license key must be provided to enable file transfers.

Contact your Stonebranch representative or Customer Support to receive the license key prior to upgrading to version 2.0 or later.

Note

title	Note

If you are upgrading an installation of UDMG from any release prior to 2.0.0.0, the start parameters for several services have changed.

Please review them carefully, especially for a manual installation or in case the Systemd service files have been edited.
For a standard upgrade with the provided Linux packages, the service configuration is updated automatically.

The following modules now requires a 'start' command to begin in server mode.

udmg-auth-proxy start -f configuration_file

udmg-web-transfer start -f configuration_file

udmg-agent-client start -f configuration_file

udmg-agent-server start -f configuration_file

Without it, they will only display the command line usage information.

In addition, a 'test' command allows to verify the the syntax of the configuration file without starting the server.

...

title	Note

If you are upgrading an installation of UDMG from any release prior to 1.3.0.0, you must uninstall the older version before installing the new version.
The installation packages, binaries, services, and environment variables have changed, and this does not allow for a standard upgrade.

...

mft_waarp_gateway
mft_auth_proxy
nginx
mft_web_transfer_client
mft-agent-proxy-client
mft-agent-proxy-server

...

udmg-server
udmg-auth-proxy
nginx
udmg-web-transfer
udmg-agent-server
udmg-agent-client

...

WAARP_GATEWAY_ADDRESS
MFT_AUTH_PROXY_CONFIG
MFT_AGENT_PROXY_CONFIG

...

UDMG_SERVER_ADDRESS
UDMG_AUTH_PROXY_CONFIG
UDMG_AGENT_CONFIG

It may be required to modify the work and data directories ownership or access rights and to update UDMG Server transfer rules to use paths that are accessible by the 'udmg' user.

The configuration files must be reviewed and compared between the old and new locations.

Special attention is required for the AESpassphrase parameter for UDMG Server. It must be the path for the file that was used by the previous release and must be accessible by the new service user. It is recommended to set an absolute path in the configuration file.

...

Pre-Installation / Upgrade Backups

The installation process overwrites the current files (exception: the configuration files are kept), this may affect your modifications.

Backing up the configuration files optimizes the time it takes you to get up and running after installing or upgrading.

/opt/udmg/etc/udmg/nginx/udmg.conf
/opt/udmg/etc/udmg/agent/client.toml
/opt/udmg/etc/udmg/agent/server.toml
/opt/udmg/etc/udmg/auth-proxy/config.toml
/opt/udmg/etc/udmg/web-transfer/config.toml
/opt/udmg/etc/udmg-server/server.ini

After upgrading RPM or DEB packages, review the new configuration file templates (with the extension .rpmnew or .dpk-new) and edit the current configuration files to add new parameters or remove deprecated parameters.

...

Release Migration

The UDMG release version is stored in the database to ensure the data structure is compatible with the version of the UDMG components.

After upgrading the component binaries and before starting the UDMG Server it is required to perform the release migration step.

The udmg-server "migrate" command handles the necessary database updates and the setting of the internal version.

Code Block

$ /opt/udmg/bin/udmg-server migrate --help
Usage:
  udmg-server [OPTIONS] migrate [migrate-OPTIONS] [version]

Help Options:
  -h, --help         Show this help message

[migrate command options]
      -c, --config=  The configuration file to use
      -d, --dry-run  Simulate the migration but does not commit the changes
      -l, --list     List Migrations
      -f, --file=    Writes the migration commands into a file instead of sending them to the database
      -v, --verbose  Show verbose debug information. Can be repeated to increase verbosity

[migrate command arguments]
  version:           The version to which the database should be migrated

The configuration file is the one used for the server mode, with the parameter for accessing the target database.

To get the list of supported target versions, use the list parameter. The last value is the release version of the udmg-server and also the default target version. The current version of the UDMG database structure is shown with the [DATABASE] tag:

Code Block
$ /opt/udmg/bin/udmg-server migrate -c /opt/udmg/etc/udmg-server/server.ini --list \| tail -n 2 1.5.0 [DATABASE] 2.0.0 [DEFAULT]

It is recommended to set the verbose parameter (3 times) to follow the progress. If not specified on the command line, the target version is the latest release number.

Code Block
$ /opt/udmg/bin/udmg-server migrate -c /opt/udmg/etc/udmg-server/server.ini -vvv [INFO ] Migration: Starting upgrade migration... [INFO ] Migration: Applying migration 'Bump database version to 2.0.0'

After the migration, the services for UDMG components can be started.

Upgrading Universal Data Mover Gateway for Linux

Upgrading with Linux Software Packages

...

Step 1

...

Contact your Stonebranch representative or Customer Support to receive the software package for the intended operating system.

...

Step 2

...

Perform the recommended backup of configuration files.

...

Step 3

...

Stop the components services.

The exact steps depend on the system architecture and the deployed components, for example:

sudo systemctl stop nginx sudo systemctl stop udmg-server sudo systemctl stop udmg-auth-proxy sudo systemctl stop udmg-agent-clientsudo systemctl stop udmg-agent-server

...

Step 4

...

Upgrade the UDMG packages (RPM or DEB), for example:

sudo rpm -Uvh udmg-agent-2.0.0.0.build.7.x86_64.rpm
sudo rpm -Uvh udmg-admin-ui-2.0.0.0.build.4.x86_64.rpm
sudo rpm -Uvh udmg-admin-ui-nginx-2.0.0.0.build.4.x86_64.rpm
sudo rpm -Uvh udmg-auth-proxy-2.0.0.0.build.15.x86_64.rpm
sudo rpm -Uvh --force udmg-server-2.0.0.build.3.x86_64.rpm

...

Panel

Table of Contents

For the UDMG Web Transfer Client, please refer to UDMG Web Transfer Client for Linux Installation.

Upgrading Universal Data Mover Gateway

Upgrading UDMG refers to the increase of a currently installed pre-2.0.x Version, Release, or Modification level of UDMG (1.5.x, 1.4.x, 1.3.x, 1.2.x) to UDMG 2.0.x.

Note

title	Note

Starting with UDMG version 2.0, a license key must be provided to enable file transfers.

Contact your Stonebranch representative or Customer Support to receive the license key prior to upgrading to version 2.0 or later.

Note

title	Note

If you are upgrading an installation of UDMG from any release prior to 2.0.0.0, the start parameters for several services have changed.

Please review them carefully, especially for a manual installation or in case the Systemd service files have been edited.
For a standard upgrade with the provided Linux packages, the service configuration is updated automatically.

The following modules now requires a 'start' command to begin in server mode.

udmg-auth-proxy start -f configuration_file

udmg-web-transfer start -f configuration_file

udmg-agent-client start -f configuration_file

udmg-agent-server start -f configuration_file

Without it, they will only display the command line usage information.

In addition, a 'test' command allows to verify the the syntax of the configuration file without starting the server.

Note

title	Note

If you are upgrading an installation of UDMG from any release prior to 1.3.0.0, you must uninstall the older version before installing the new version.
The installation packages, binaries, services, and environment variables have changed, and this does not allow for a standard upgrade.

Category	Prior releases	Release 1.3
user and group	mft:mft	udmg:udmg
binaries	/usr/local/bin	/opt/udmg/bin
configuration files	/etc/mft	/opt/udmg/etc
log files	/var/opt/udmg/logs	/var/opt/udmg/logs
UDMG Admin UI assets	/opt/udmg/var/www/mft	/opt/udmg/var/www/udmg
Services	mft_waarp_gateway mft_auth_proxy nginx mft_web_transfer_client mft-agent-proxy-client mft-agent-proxy-server	udmg-server udmg-auth-proxy nginx udmg-web-transfer udmg-agent-server udmg-agent-client
Environment variables	WAARP_GATEWAY_ADDRESS MFT_AUTH_PROXY_CONFIG MFT_AGENT_PROXY_CONFIG	UDMG_SERVER_ADDRESS UDMG_AUTH_PROXY_CONFIG UDMG_AGENT_CONFIG

It may be required to modify the work and data directories ownership or access rights and to update UDMG Server transfer rules to use paths that are accessible by the 'udmg' user.

The configuration files must be reviewed and compared between the old and new locations.

Special attention is required for the AESpassphrase parameter for UDMG Server. It must be the path for the file that was used by the previous release and must be accessible by the new service user. It is recommended to set an absolute path in the configuration file.

Anchor

	backup
	backup

Pre-Installation / Upgrade Backups

The installation process overwrites the current files (exception: the configuration files are kept), this may affect your modifications.

Backing up the configuration files optimizes the time it takes you to get up and running after installing or upgrading.

/opt/udmg/etc/udmg/nginx/udmg.conf
/opt/udmg/etc/udmg/agent/client.toml
/opt/udmg/etc/udmg/agent/server.toml
/opt/udmg/etc/udmg/auth-proxy/config.toml
/opt/udmg/etc/udmg/web-transfer/config.toml
/opt/udmg/etc/udmg-server/server.ini

After upgrading RPM or DEB packages, review the new configuration file templates (with the extension .rpmnew or .dpk-new) and edit the current configuration files to add new parameters or remove deprecated parameters.

Anchor

	db_migration
	db_migration

Release Migration

The UDMG release version is stored in the database to ensure the data structure is compatible with the version of the UDMG components.

After upgrading the component binaries and before starting the UDMG Server it is required to perform the release migration step.

The udmg-server "migrate" command handles the necessary database updates and the setting of the internal version.

Code Block

$ /opt/udmg/bin/udmg-server migrate --help
Usage:
  udmg-server [OPTIONS] migrate [migrate-OPTIONS] [version]

Help Options:
  -h, --help         Show this help message

[migrate command options]
      -c, --config=  The configuration file to use
      -d, --dry-run  Simulate the migration but does not commit the changes
      -l, --list     List Migrations
      -f, --file=    Writes the migration commands into a file instead of sending them to the database
      -v, --verbose  Show verbose debug information. Can be repeated to increase verbosity

[migrate command arguments]
  version:           The version to which the database should be migrated

The configuration file is the one used for the server mode, with the parameter for accessing the target database.

To get the list of supported target versions, use the list parameter. The last value is the release version of the udmg-server and also the default target version. The current version of the UDMG database structure is shown with the [DATABASE] tag:

Code Block
$ /opt/udmg/bin/udmg-server migrate -c /opt/udmg/etc/udmg-server/server.ini --list \| tail -n 2 1.5.0 [DATABASE] 2.0.0 [DEFAULT]

It is recommended to set the verbose parameter (3 times) to follow the progress. If not specified on the command line, the target version is the latest release number.

Code Block
$ /opt/udmg/bin/udmg-server migrate -c /opt/udmg/etc/udmg-server/server.ini -vvv [INFO ] Migration: Starting upgrade migration... [INFO ] Migration: Applying migration 'Bump database version to 2.0.0'

After the migration, the services for UDMG components can be started.

Upgrading Universal Data Mover Gateway for Linux

Upgrading with Linux Software Packages

Step 1

Contact your Stonebranch representative or Customer Support to receive the software package for the intended operating system.

Step 2

Perform the recommended backup of configuration files.

Step 3

Stop the components services.

The exact steps depend on the system architecture and the deployed components, for example:

sudo systemctl stop nginx sudo systemctl stop udmg-server sudo systemctl stop udmg-auth-proxy sudo systemctl stop udmg-agent-clientsudo systemctl stop udmg-agent-server

Step 4

Upgrade the UDMG packages (RPM or DEB), for example:

sudo rpm -Uvh udmg-agent-2.0.0.0.build.7.x86_64.rpm
sudo rpm -Uvh udmg-admin-ui-2.0.0.0.build.4.x86_64.rpm
sudo rpm -Uvh udmg-admin-ui-nginx-2.0.0.0.build.4.x86_64.rpm
sudo rpm -Uvh udmg-auth-proxy-2.0.0.0.build.15.x86_64.rpm
sudo rpm -Uvh --force udmg-server-2.0.0.build.3.x86_64.rpm

Step 5

Review the component configuration files.
Refer to each component installation section below for the list of parameters.
/opt/udmg/etc/udmg/nginx/udmg.conf
/opt/udmg/etc/udmg/agent/client.toml
/opt/udmg/etc/udmg/agent/server.toml
/opt/udmg/etc/udmg/auth-proxy/config.toml
/opt/udmg/etc/udmg-server/server.ini

Note that new configuration file templates (with the extension .rpmnew or .dpk-new) that contain all the allowed parameters are added during the software package upgrade.

Note

title	Note

The default upstream port to reach the UDMG Authentication Proxy is set to 5775 in /opt/udmg/etc/udmg/nginx/udmg.conf starting from version 1.5.0.1.

Please review and make sure that the same port (either 5000 or 5775) is also defined in /opt/udmg/etc/udmg/auth-proxy/config.toml .

Step 6 Perform the release migration.

Step 7

Start

Review the component service configuration files.

For instance, the UDMG Authentication Proxy service file (/etc/systemd/system/udmg-auth-proxy.service) was installed with these parameter in version 1.5

Code Block

title	udmg-auth-proxy.service (Version 1.5)

[Unit]
Description=Stonebranch UDMG Authentication Proxy

[Service]
Type=simple
User=udmg
Group=udmg
WorkingDirectory=/home/udmg
Environment="UDMG_AUTH_PROXY_CONFIG=/opt/udmg/etc/udmg/auth-proxy/config.toml"
ExecStart=/bin/sh -c 'exec /opt/udmg/bin/udmg-auth-proxy'
Restart=on-failure
SyslogIdentifier=udmg-auth-proxy
SyslogFacility=local0

[Install]
WantedBy=multi-user.target

Note the addition of the start command on the ExecStart directive on the version 2.0:

Code Block

title	udmg-auth-proxy.service (Version 2.0)

[Unit]
Description=Stonebranch UDMG Authentication Proxy

[Service]
Type=simple
User=udmg
Group=udmg
WorkingDirectory=/home/udmg
Environment="UDMG_AUTH_PROXY_CONFIG=/opt/udmg/etc/udmg/auth-proxy/config.toml

"
ExecStart=/bin/sh -c 'exec /opt/udmg/

etc/udmg-server/server.ini

Note that new configuration file templates (with the extension .rpmnew or .dpk-new) that contain all the allowed parameters are added during the software package upgrade.

Note

title	Note

The default upstream port to reach the UDMG Authentication Proxy is set to 5775 in /opt/udmg/etc/udmg/nginx/udmg.conf starting from version 1.5.0.1.

Please review and make sure that the same port (either 5000 or 5775) is also defined in /opt/udmg/etc/udmg/auth-proxy/config.toml .

Step 6 Perform the release migration.

bin/udmg-auth-proxy start'
Restart=on-failure
SyslogIdentifier=udmg-auth-proxy
SyslogFacility=local0

[Install]
WantedBy=multi-user.target

The same applies for the other components:

/etc/systemd/system/udmg-auth-proxy.service

/etc/systemd/system/udmg-agent-client.service

/etc/systemd/system/udmg-agent-server.service

Step 8

Start the components services.

The exact steps depend on the system architecture and the deployed components, for example:

sudo systemctl start udmg-server sudo systemctl start udmg-auth-proxy sudo systemctl start udmg-agent-clientsudo systemctl start udmg-agent-server sudo systemctl start nginx

Step 9 Verify or apply the License, see UDMG Licensing.

Upgrading a Manual Installation

Step 1

Contact your Stonebranch representative or Customer Support to receive the software package for the intended operating system.

Step 2

Perform the recommended backup of configuration files.

Step 3

Stop the components services.

The exact steps depend on the system architecture and the deployed components, for example:

sudo systemctl

start

stop nginx sudo systemctl stop udmg-server sudo systemctl

start

stop udmg-auth-proxy sudo systemctl

start

stop udmg-agent-clientsudo systemctl

start

stop udmg-agent-server

sudo systemctl start nginxStep 8Verify or apply the License, see UDMG Licensing.

Upgrading a Manual Installation

Review the component configuration files.

Refer to each component installation section below for the list of parameters.
/opt/udmg/etc/udmg/nginx/udmg.conf

Step 1

Contact your Stonebranch representative or Customer Support to receive the software package for the intended operating system.

Step 2

Perform the recommended backup of configuration files.

Step 3

Stop the components services.

The exact steps depend on the system architecture and the deployed components, for example:

sudo systemctl stop nginx sudo systemctl stop udmg-server sudo systemctl stop udmg-auth-proxy sudo systemctl stop udmg-agent-clientsudo systemctl stop udmg-agent-server

Step 4

Replace the component binaries:

sudo cp udmg-server.bin /opt/udmg/bin/udmg-server sudo cp udmg-client.bin /opt/udmg/bin/udmg-client sudo cp udmg-auth-proxy.bin /opt/udmg/bin/udmg-auth-proxy

Change ownership/permissions on new files:

sudo chown -R root:udmg /opt/udmg/bin/ sudo chmod -R 750 /opt/udmg/bin/

Upgrade the Admin UI:

sudo mv /opt/udmg/var/www/udmg mv /opt/udmg/var/www/udmg_BACKUP
sudo unzip -d /opt/udmg/var/www/udmg 'udmg-admin-ui-2.0.0.0 build.4.zip'
sudo chown -R root:udmg /opt/udmg/var/www/udmg

Step 5

Step 4

Replace the component binaries:

sudo cp udmg-server.bin /opt/udmg/bin/udmg-server sudo cp udmg-client.bin /opt/udmg/bin/udmg-client sudo cp udmg-auth-proxy.bin /opt/udmg/bin/udmg-auth-proxy

Change ownership/permissions on new files:

sudo chown -R root:udmg /opt/udmg/bin/ sudo chmod -R 750 /opt/udmg/bin/

Upgrade the Admin UI:

sudo mv /opt/udmg/var/www/udmg mv /opt/udmg/var/www/udmg_BACKUP
sudo unzip -d /opt/udmg/var/www/udmg 'udmg-admin-ui-2.0.0.0 build.4.zip'
sudo chown -R root:udmg /opt/udmg/var/www/udmg

Step 5

Review the component configuration files.

Refer to each component installation section below for the list of parameters.
/opt/udmg/etc/udmg/nginx/udmg.conf
/opt/udmg/etc/udmg/agent/client.toml
/opt/udmg/etc/udmg/agent/server.toml
/opt/udmg/etc/udmg/auth-proxy/config.toml
/opt/udmg/etc/udmg-server/server.ini

Step 6 Perform the release migration.

Step 7

Review the component service configuration files.

For instance, the UDMG Authentication Proxy service file (/etc/systemd/system/udmg-auth-proxy.service) was installed with these parameter in version 1.5

Code Block

title	udmg-auth-proxy.service (Version 1.5)

[Unit]
Description=Stonebranch UDMG Authentication Proxy

[Service]
Type=simple
User=udmg
Group=udmg
WorkingDirectory=/home/udmg
Environment="UDMG_AUTH_PROXY_CONFIG=/opt/udmg/etc/udmg/auth-proxy/config.toml"
ExecStart=/bin/sh -c 'exec /opt/udmg/bin/udmg-auth-proxy'
Restart=on-failure
SyslogIdentifier=udmg-auth-proxy
SyslogFacility=local0

[Install]
WantedBy=multi-user.target

Note the addition of the start command on the ExecStart directive on the version 2.0:

Code Block

title	udmg-auth-proxy.service (Version 2.0)

[Unit]
Description=Stonebranch UDMG Authentication Proxy

[Service]
Type=simple
User=udmg
Group=udmg
WorkingDirectory=/home/udmg
Environment="UDMG_AUTH_PROXY_CONFIG=/opt/udmg/etc/udmg/

agent

auth-proxy/

client

config.toml

"
ExecStart=/bin/sh -c 'exec /opt/udmg/

etc/udmg/agent/server.toml
/opt/udmg/etc/udmg/auth-proxy/config.toml
/opt/udmg/etc/udmg-server/server.ini

Step 6 Perform the release migration.

bin/udmg-auth-proxy start'
Restart=on-failure
SyslogIdentifier=udmg-auth-proxy
SyslogFacility=local0

[Install]
WantedBy=multi-user.target

The same applies for the other components:

/etc/systemd/system/udmg-auth-proxy.service

/etc/systemd/system/udmg-agent-client.service

/etc/systemd/system/udmg-agent-server.service

Step 8

Start the components services.

The exact steps depend on the system architecture and the deployed components, for example:

sudo systemctl start udmg-server sudo systemctl start udmg-auth-proxy sudo systemctl start udmg-agent-clientsudo systemctl start udmg-agent-server sudo systemctl start nginx

Step 89 Verify or apply the License, see UDMG Licensing.

...

Note

title	Note

About the global section: the requested OS file and directory creation permissions are applied after the umask of the OS user that is running the UDMG Server process.

...

Panel
`# sudo vi /opt/udmg/etc/udmg/agent/client.toml`
Panel
`[client]` `# Target UDMG Agent Proxy client.toml`

Panel

[client]
# Target UDMG Agent Proxy Hostname or IP, and port
hostname = "localhost"
port = "2222"

# UDMG Agent Service User and password
username = "mft"
password = "61ee8b5601a84d5154387578466c8998848ba089"

# Default TTL to Connection Retry
ttl="5s"

[client.api]
# UDMG Agent Client Admin APIport="2280"

[gateway]
# UDMG Server Hostname or IP, and port
hostname = "localhost"
port = "222218080"
# UDMG Agent Service User and passwordServer Username/Password
username = "mftadmin"
password = "61ee8b5601a84d5154387578466c8998848ba089"

# Default TTL to Connection Retry
ttl="5s"

[client.api]
# UDMG Agent Client Admin APIport="2280"

[gateway]
# UDMG Server Hostname or IP, and port
hostname = "localhost"
port = "18080"
# UDMG Server Username/Password
username = "admin"
password = "admin_password"

The password key is used for the client authentication.

...

admin_password"

The password key is used for the client authentication.

Setup the Systemd Services

Note

title	Note

If you are upgrading an installation of UDMG from any release prior to 2.0.0.0, the start parameters for several services have changed.

Please review them carefully, especially for a manual installation or in case the Systemd service files have been edited.
For a standard upgrade with the provided Linux packages, the service configuration is updated automatically.

The following modules now requires a 'start' command to begin in server mode.

udmg-auth-proxy start -f configuration_file

udmg-web-transfer start -f configuration_file

udmg-agent-client start -f configuration_file

udmg-agent-server start -f configuration_file

Without it, they will only display the command line usage information.

In addition, a 'test' command allows to verify the the syntax of the configuration file without starting the server.

UDMG Server

Create a new service definition:

...

Panel
`# sudo vi /etc/systemd/system/udmg-auth-proxy.service`

Panel

[Unit]
Description=Stonebranch UDMG Auth Proxy server

[Service]
Type=simple
User=udmg
Group=udmg
WorkingDirectory=/home/udmg
Environment="UDMG_AUTH_PROXY_CONFIG=/opt/udmg/etc/udmg/auth_proxy/config.toml"
ExecStart=/bin/sh -c 'exec /opt/udmg/bin/udmg-auth-proxy start'
Restart=on-failure

[Install]
WantedBy=multi-user.target

...

Panel

# systemctl start udmg-auth-proxy
# systemctl status udmg-auth-proxy
● udmg-auth-proxy.service - Stonebranch UDMG Auth Proxy server
Loaded: loaded ( /etc/systemd/system/udmg-auth-proxy.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2022-06-07 16:58:48 -03; 21s ago
Main PID: 25008 (udmg-auth-proxy)
Tasks: 3 (limit: 3509)
CPU: 4ms
CGroup: /system.slice/udmg-auth-proxy.service
└─25008 /opt/udmg/bin/udmg-auth-proxy start

Make sure that the listen port and network interface is reachable by NGINX Server.

...

Panel
`# sudo vi /etc/systemd/system/udmg-agent-server.service`

Panel

[Unit]

Description=Stonebranch UDMG Agent Proxy server 
[Service] Type=simple User=udmg Group=udmg WorkingDirectory=/home/udmg Environment="UDMG_AGENT_CONFIG=/opt/udmg/etc/udmg/agent/server.toml" ExecStart=/bin/sh -c 'exec /opt/udmg/bin/udmg-agent-server start' Restart=on-failure 
[Install] WantedBy=multi-user.target

...

Panel

# systemctl start udmg-agent-server
# systemctl status udmg-agent-server
● udmg-agent-server.service - Stonebranch UDMG Agent Proxy Server
Loaded: loaded ( /etc/systemd/system/udmg-agent-server.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2022-06-07 16:26:53 -03; 2s ago
Main PID: 25444 (udmg-agent-server)
Tasks: 5 (limit: 3509)
CPU: 5ms
CGroup: /system.slice/udmg-agent-server.service
└─25444 /opt/udmg/bin/udmg-agent-server start

Jun 07 16:26:53 localhost.localdomain systemd[1]: Started UDMG Agent Proxy Server.
Jun 07 16:26:53 localhost.localdomain sh[25444]: level=info TS=2022-06-07T19:26:53.624296821Z HostKey=Ok Path=/data/agent

...

Panel
`# sudo vi /etc/systemd/system/udmg-agent-client.service`

Panel

[Unit]
Description=Stonebranch UDMG Agent Proxy Client

[Service]
Type=simple
User=udmg
Group=udmg
WorkingDirectory=/home/udmg
Environment="UDMG_AGENT_CONFIG=/opt/udmg/etc/udmg/agent/client.toml"
ExecStart=/bin/sh -c 'exec /opt/udmg/bin/udmg-agent-client start'
Restart=on-failure

[Install]
WantedBy=multi-user.target

...

Panel

# systemctl start udmg-agent-client
# systemctl status udmg-agent-client
● udmg-agent-client.service - Stonebranch UDMG Agent Proxy Client
Loaded: loaded ( /etc/systemd/system/udmg-agent-client.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2022-06-07 17:26:53 -03; 2s ago
Main PID: 25445 (udmg-agent-client)
Tasks: 5 (limit: 3509)
CPU: 6ms
CGroup: /system.slice/udmg-agent-client.service
└─25445 /opt/udmg/bin/udmg-agent-client start

Jun 07 17:26:53 localhost.localdomain systemd[1]: Started UDMG Agent Proxy Client.
Jun 07 17:26:53 localhost.localdomain sh[25445]: level=info TS=2022-06-07T20:26:53.624296821Z Servers=[]

...

Anchor
selinux
selinux
Using UDMG with SELinux

Security-Enhanced Linux (SELinux) is enabled by default on modern RHEL and CentOS servers. Each operating system object (process, file descriptor, file, etc.) is labeled with an SELinux context that defines the permissions and operations the object can perform. In RHEL 6.6/CentOS 6.6 and later, NGINX is labeled with the httpd_t context.

When SELinux is enabled, the UDMG Admin UI shows "403 access denied" and "404 page not found" errors on the landing page and permission errors are reported in the NGINX log files:

Panel
`... 2023/09/19 12:51:38 [error] 108236#108236: *1 "/opt/udmg/var/www/udmg/index.html" is forbidden (13: Permission denied), client: 127.0.0.1, server: localhost, request: "GET / HTTP/1.1", host: "localhost ...`

...

Version	Old Version 8	New Version 9
Changes made by	Olivier Michaut	Olivier Michaut
Saved on	Jun 01, 2024	Jun 01, 2024

Page Comparison

Versions Compared

Key

Upgrading Universal Data Mover Gateway

Pre-Installation / Upgrade Backups

Release Migration

Upgrading Universal Data Mover Gateway for Linux

Upgrading with Linux Software Packages

Upgrading Universal Data Mover Gateway

Pre-Installation / Upgrade Backups

Release Migration

Upgrading Universal Data Mover Gateway for Linux

Upgrading with Linux Software Packages

Upgrading a Manual Installation

Upgrading a Manual Installation

Setup the Systemd Services

UDMG Server

AnchorselinuxselinuxUsing UDMG with SELinux

Anchor
selinux
selinux
Using UDMG with SELinux