Troubleshooting ISSU-Related Problems Using Log Error Messages
The following problems might occur during an ISSU upgrade. You can identify the errors by using the details in the logs. You can also see the details of the error messages in the Junos OS System Log Reference.
Chassisd Process Errors
Problem
Description: There are errors related to chassisd.
Solution
Use the error messages to understand the issues related to chassisd.
When ISSU starts, a request is sent to chassisd to check whether there are any problems related to ISSU from a chassis perspective. If there is a problem, a log message is created.
Kernel State Synchronization
Problem
Description: There are errors related to ksyncd.
Solution
Use the following error messages to understand the issues related to ksyncd:
Failed to get kernel-replication error information from Standby Routing Engine.
mgd_slave_peer_has_errors() returns error at line 4414 in mgd_package_issu.
ISSU checks whether there are any ksyncd errors on the secondary node (node 1) and displays the error message if there are any problems and aborts the ISSU.
Installation Related Errors
Problem
Description: The install image file does not exist or the remote site is inaccessible.
Solution
Use the following error messages to understand the installation related problems:
error: File does not exist: /var/tmp/junos-srx5000-11.4X3.2-domest error: Couldn't retrieve package /var/tmp/junos-srx5000-11.4X3.2-domest
ISSU downloads the install image as specified in the ISSU command as an argument. The image file can be a local file or located at a remote site. If the file does not exist or the remote site is inaccessible, an error is reported.
ISSU Support Related Errors
Problem
Description: There is an installation failure because of unsupported software and unsupported feature configuration.
Solution
Use the following error messages to understand the compatibility-related problems:
WARNING: Current configuration not compatible with /var/tmp/junos-srx5000-11.4X3.2-domestic.tgz Exiting in-service-upgrade window Exiting in-service-upgrade window
RG Groups Failover Errors
Problem
Description: There is a problem with automatic redundancy group failure.
Solution
Use the following error messages to understand the problem:
failover all RG 1+ groups to node 0 error: Command failed. None of the redundancy-groupss has been failed over. Some redundancy-groups on node1 are already in manual failover mode. Please execute 'failover reset all' first..
Initial Validation Checks Fail
Problem
Description: The initial validation checks fail.
Solution
The following error messages are displayed when initial validation checks fail when the image is not present and ISSU is aborted:
When Image is Not Present
user@host> ...0120914_srx_12q1_major2.2-539764-domestic.tgz reboot Chassis ISSU Started Chassis ISSU Started ISSU: Validating Image Initiating in-service-upgrade Initiating in-service-upgrade Fetching package... error: File does not exist: /var/tmp/junos-srx1k3k-12.1I20120914_srx_12q1_major2.2-539764-domestic.tgz error: Couldn't retrieve package /var/tmp/junos-srx1k3k-12.1I20120914_srx_12q1_major2.2-539764-domestic.tgz Exiting in-service-upgrade window Exiting in-service-upgrade window Chassis ISSU Aborted Chassis ISSU Aborted Chassis ISSU Aborted ISSU: IDLE ISSU aborted; exiting ISSU window.
When Image File is Corrupted
user@host> ...junos-srx1k3k-11.4X9-domestic.tgz_1 reboot Chassis ISSU Started node1: -------------------------------------------------------------------------- Chassis ISSU Started ISSU: Validating Image Initiating in-service-upgrade node1: -------------------------------------------------------------------------- Initiating in-service-upgrade ERROR: Cannot use /var/tmp/junos-srx1k3k-11.4X9-domestic.tgz_1: gzip: stdin: invalid compressed data--format violated tar: Child returned status 1 tar: Error exit delayed from previous errors ERROR: It may have been corrupted during download. ERROR: Please try again, making sure to use a binary transfer. Exiting in-service-upgrade window node1: -------------------------------------------------------------------------- Exiting in-service-upgrade window Chassis ISSU Aborted Chassis ISSU Aborted node1: -------------------------------------------------------------------------- Chassis ISSU Aborted ISSU: IDLE ISSU aborted; exiting ISSU window. {primary:node0}
The primary node validates the device configuration to ensure that it can be committed using the new software version. If anything goes wrong, ISSU aborts and error messages are displayed.