Summary
This article describes procedures for troubleshooting the DPX auto-update management console if it hangs. To resolve this issue, perform the procedures below and send the relevant information to Catalogic Software Data Protection Technical Support.
Symptoms
In the DPX management console, perform an auto-update by selecting Help > Autoupdate DPX. If you see the following symptoms, the auto-update process is hung:
During an auto-update, the progress bar remains static for an unusual length of time. In addition, one or more table rows displaying patch package information does not display either of the following values in the status column:
- (file is local)
- %100 (file is local)
The lower table represents nodes being updated. The status column in the table does not display any of the following values:
- Installation: passed
- Installation: passed_rebootrequired
- Installation: passed rebootinit
- Installation: failed
- Installation: failed_noderolledback
Resolution
Important: Although the images in this article depict a specific version of the DPX management console, their functionality is applicable to all currently supported versions.
Typically, during the last phase of an auto-update, a monitor window displays the progress of the installation. When the installation is completed, the progress bar moves to 100% and the label on the button changes from Abort to Done.
However, under certain conditions the monitor window freezes or fails to indicate that the process completed.
To resolve this issue:
- Review the master agent log to determine if the update process completed successfully.
- Check Java Virtual Machine (JVM).
Perform these steps using the information below:
To review the master log:
- Look in the <SSPRODIR>\updates\logs folder on the master server for the latest master agent logs. The master agent log names include a timestamp, so ensure that you are looking at the most current log. The line at the end of the log indicates that the update process is completed:
DPX Update Complete...
Note: Typically, a DPX management console freeze has no impact on the actual
update process. Therefore, thoroughly review the master agent log file to determine the update
state of each node. The update process may still be running in the background. To check this,
reopen the log file several times until the auto-update process is complete.
Refer to the following image:
In the image above, the monitor window is frozen. Although the master agent logs indicate that the
update process is complete, the monitor window is never updated. There are runtime exceptions,
which cause the monitor window updates to freeze.
To check the Java Virtual Machine (JVM):
- All the Runtime Exceptions are logged in the Java console; under Internet Explorer select Tools > SUN Java Console. For both Internet Explorer 6 and Internet Explorer 7, the procedure to display the Sun Java console is the same. Through the JVM console, obtain the stack trace for the current thread running within the JVM.
- Click v. The current thread dump displays and includes all the runtime exceptions thrown during the
application runtime. Copy and paste the current thread dump into a text editor.Note: If you see runtime exceptions, attach the master, client, and management console logs as
well as the thread dump stack trace, which will help us to understand the failure. Send this
information to Catalogic Software Data Protection Technical Support. - Open the Java console and check for any exceptions. If the message that displays in the Java Console is similar to the following, it confirms that the management console is hung.
Exception in thread "AWT-EventQueue-0" java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
at java.util.AbstractList$Itr.next(Unknown Source)
at com.syncsort.bex.autoupdate.core.elements.JobDef.clone(JobDef.java:318)
at com.syncsort.bex.autoupdate.gui.MonitorWindow.updateTableData(MonitorWindow.java:527)
at com.syncsort.bex.autoupdate.gui.MonitorWindow$2.actionPerformed(MonitorWindow.java:253)
at javax.swing.Timer.fireActionPerformed(Unknown Source)
at javax.swing.Timer$DoPostEvent.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Dump thread stack ...