Version: 3.7.1.17
Date: January 22, 2018
New Features
JetPatch 3.7.1 is a minor version that includes 5 elements to address agents that can become to an as package state
- Cleanup of false As-Package alerts - ensures that the consoles show only real As-Package situations.
- Fixing known cases that causes agent to As-Package status.
- Enabling manual restore of As-Package agents
- Automatic Reporting and log collection
- Secure email notification
Cleanup of false positive alerts
Some of all the agents reported as As Package were agents that are working properly. The false reporting is because older version agent leftovers alongside the current working, healthy agent. JetPatch 3.7.1 cleanup these leftovers.
This feature requires deployment of new connector version 3.7.1 and above .
Fixing known cases leading agent to As Package
Root cause analysis of every As-Package agent helps understand to the exact use case that caused this. Patch 3.7.1 is fixing all known use cases that were causing agents to be stuck in As Package state.
Enabling User restore / remove of As Package agents
In case that for some unknown reason an agent in As Package state found, the user will be able to restore (Windows only) / remove it from the Server's tab.
Automatic Reporting and log collection
Once the system detects an agent that is left in As Package state, it will send an email alert and the required logs to JetPatch so we will be able to proactively investigate and fix potential issues.
Secure email notification
In case an agent is reported as As package JetPatch will send email notification to a specified address. The email is TLS encrypted and invoke the STARTTLS command.
The email notification now supports strong encryption for the attached data to email via AES 256/128 encryption.
Relevant logs are attached in Zip format.
The user can turn the reporting feature and set the encryption password under Setting page
Notes
Zip encryption password should be shared between all recipients in order to be able to open the zip files. Any changes in password should be conveyed to all recipients.
Some of the features parameters could be modified using the Intigua property file -
Intigua Properties Configuration file - new parameters
Property Name |
Description |
Default Value |
|
as-package.fix-attempts.max-number |
Number of retries to fix agent in as package state |
3 |
|
as-package.fix-attempt.next.hours |
Interval between fix attempts |
24 |
|
as-package.mail.alert.delay |
Frequency for sending email alerts in ms (the time the system will wait before sending the next email in the queue) |
60000 |
|
as-package.mail.alert.initial-delay |
Delay for email notification feature after Manager server restart in ms (the system will wait before starting to send alerts - so that the automatic fix can complete its work) |
3600000 |
|
as-package.mail.alert.send.to.list |
JetPatch automatically sends alerts to:aspack@intigua.com. If this list exist it will send emails to this list so make sure the list include the default email address - aspack@intigua.com |
aspack@intigua.com |
|
as-package.report.next.days |
Interval for re-sending email alert |
14 |
|
as-package.report.max-number |
Max number of resending email alerts |
5 |
|
mail.smtp.starttls.required |
|
false |
|
mail.smtp.ssl.protocols |
space separated list of allowed ciphers. If not defined uses the java VM default list |
|
|
zip.encoding.AES.strength |
AES strength (allowed values 128 or 256) |
256 |
Known Issues
Restore for As Package agents works on windows machines only
Comments
0 comments
Please sign in to leave a comment.