SUCCESS/UPDATED
In the case of SUCCESS no further operation is required as all components have been successfully updated.
UPDATE REQUIRED
The node/component must be updated to the version indicated in the Update version column.
ERROR
If the ERROR was generated by a failed update of the Web Application, all updates relating to the remaining components are canceled. At this point, it will be mandatory to restore the database backup made by the user before starting the update procedure. (Except in the event that another web application has already been successfully updated in the same update process).
It is recommended to restart the node and try the update again. If the error recurs, it is advisable to retrieve the log as specified in the LOG section and contact support during assistance hours.
If the ERROR was generated by another component, it is advisable to restart the node and try the update again. If the error recurs, it is advisable to retrieve the log as specified in the LOG section.
CRITICAL
A CRITICAL error is generated when both the update and the automatic backup restore have failed for a component.
In this case, the component remains in an indefinite state and manual intervention by the user is required to solve the problem.
It is recommended that you restore the full server from snapshots and contact boolebox support during support hours.
The “critical error” status is also reported in the main application window in the list of components / nodes:
By double clicking on the line relating to the error, a window will appear showing the cause of the error.
In the main window, the critical state remains until the user expressly requests to remove it. To remove the “critical” status, simply press the “Remove the alert” button on the previous screen.
The actions to be implemented in the event of a critical error are:
WebApp case
Retrieving the logs from the node affected by the error
Snapshot restore of affected server / node
Restore the database
Contact Boole Server support providing the logs retrieved previously
case other components
Retrieving the logs from the node affected by the error
Snapshot restore of affected server / node
Contact Boole Server support providing the logs retrieved previously
LOG
The default path of the Boolebox Updater Service logs on all nodes is:
% programdata% BooleBoxUpdater ServiceLogs
The default path for the Boolebox Updater Console logs and reports is:
% programdata% BooleBoxUpdater ConsoleLogs
% programdata% BooleBoxUpdater ConsoleReports
The last log generated by the Updater can be identified by the following file name
BooleBoxUpdaterGuest-XXXX-XX-XX.txt where with XXXX-XX-XX is indicated the date of the update attempt.
The last report generated by the Console can be identified by the following file name
Report_ XXXX-XX-XX_XXXX.txt where with XXXX-XX-XX_XXXX is indicated the date and time of the update attempt.