If you have faced one of the errors shown below when trying to deploy the JetPatch connector on your endpoints, please try to apply the instruction in the solution column, to resolve the issue
In order to see what was the connector error when deploying:
- Go to platform configuration
- Navigate to the servers tab
- Search for the endpoint with issues and click on it
- Navigate to the logs tab and see details.
|
Error message |
When the issue appears |
Solution |
|
N/A |
Status stays as pending for a very long-time (no error message generated) |
1. If Linux, verify the account is able to run passwordless sudo commands |
|
Invalid credentials |
|
Check this article Invalid Credentials Errors |
|
No IP Found |
Windows endpoints behind a NAT |
Verify the WSUS endpoint configuration is pointing to the private IP of the WSUS server |
|
Insufficient permissions |
when trying to deploy the connector on your Linux endpoints |
See this article.
|
| SMB Operation Failed | Deploying the connector
|
1. Check SMB2/445 Connection 2. Check if the account has read/write/execute permissions on Windows/Temp |
| Intigua deployment failed, ip: [ | Deploying the connector |
Likely /usr/share/intigua/certs permission issue. You can verify by looking at worker.log via manager logs |
If there still is an issue while deploying a connector on an endpoint, please follow the next steps which will help you resolve the issue.
- From the JetPatch server, try to telnet or netcat to the endpoint over port 22 (Linux/Unix) or 445 (Windows) port. If that doesn’t work it means you have a network issue that should be resolved.
- You can also try traceroute with port specified
- Linux Only:
- Check the post_install_log file in /tmp
- Verify the account has appropriate permissions (likely to be an issue if the activity is not timing out after a few minutes)
- Check SElinux configuration (it may limit the connection). More information can be found here.
- Deploy the connector from the endpoint itself
Look at manager logs, specifically the worker.log file in the logs folder
For any other issue, please contact the JetPatch support team with the logs attached.
Comments
0 comments
Please sign in to leave a comment.