⚠️ OPSWAT Central Management v7 and My OPSWAT On-Premises (My OPSWAT Central Management v8) will reach End of Sale on July 31, 2025, and End of Life on January 31, 2027. We encourage you to upgrade to My OPSWAT Central Management v10 before Janauary 31, 2027, to ensure continued support and access to the latest features.

Failed to remote install OPSWAT Products

TermDetail
ProblemFailed to remote install OPSWAT Products
CauseOPSWAT Central Management was unable to open a SSH connection. The target machine did not satisfy the system requirements of the OPSWAT Product that was being installed.
TroubleshootingCheck log in gears_product_service.log file. Look for the newest version of the message "Testing connection to <target machine>".
SolutionEnsure that the target machine has enabled OpenSSH server and can satisfy the system requirements of the OPSWAT Product.

After starting the remote installation, the new OPSWAT Product's entry in the corresponding management page shows the Disconnected status.

Please check the file gears_product_service.log in the folder "C:\Program Files\OPSWAT\Central\tomcat\logs".

Look for the section that starts with "Testing connection to <target machine>" to find the remote installation's error message. If the log includes the line "Install failed", a possible cause is that the target machine did not satisfy the OPSWAT Product's system requirements. Please ensure that the target machine does meet the system requirements and try again.

If the log has one or more error messages "ExitStatus: 1" instead of "ExitStatus: 0", it is possible that OpenSSH server has not been enabled correctly on the target machine. Please refer to Remote Install OPSWAT Products to correct its configuration.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
OPSWAT Client failed to report to OPSWAT Central Management server
On This Page
Failed to remote install OPSWAT Products