IBM Support

Cause of SRC_TRYX error in PowerVM VIOS

Troubleshooting


Problem

SRC_TRYX can be seen after a VIOS reboot after updating VIOS to 3.1.3.21

Symptom

Error logged on VIOS error log during VIOS reboot, e.g.
Jan  8 04:00:16 SRC        P SRC_TRYX            aso
Jan  8 04:00:16 SRC        I SRC_RSTRT           aso
Jan  8 04:00:16 SRC        I SRC_RSTRT           aso
Jan  8 03:59:51 sys0       I PARTID_BOOT_REASON  Partition boot reason.
Dec 31 20:19:31 SRC        P SRC_TRYX            aso
Dec 31 20:19:31 SRC        I SRC_RSTRT           aso
Dec 31 20:19:31 SRC        I SRC_RSTRT           aso
Dec 31 20:19:07 sys0       I PARTID_BOOT_REASON  Partition boot reason.
Dec 31 18:01:18 SRC        P SRC_TRYX            aso
Dec 31 18:01:18 SRC        I SRC_RSTRT           aso
Dec 31 18:01:18 SRC        I SRC_RSTRT           aso
Dec 31 18:00:54 sys0       I PARTID_BOOT_REASON  Partition boot reason.
LABEL:		SRC_TRYX
IDENTIFIER:	1BA7DF4E

Date/Time:       Wed Jan  8 04:00:16 2025
Sequence Number: 6678
Machine Id:      00FXXXXXXB00
Node Id:         vios2
Class:           S
Type:            PERM
WPAR:            Global
Resource Name:   SRC

Description
SOFTWARE PROGRAM ERROR

Probable Causes
APPLICATION PROGRAM

Failure Causes
SOFTWARE PROGRAM

	Recommended Actions
	DETERMINE WHY SUBSYSTEM CANNOT RESTART

Detail Data
SYMPTOM CODE
           0
SOFTWARE ERROR CODE
       -9020
ERROR CODE
           0
DETECTING MODULE
'srchevn.c'@line:'394'
FAILING MODULE
aso

Cause

The SRC_TRYX error indicates the Active System Optimizer (ASO) subsystem failed to start. 
There is a known Issue in VIOS 3.1.3 fixed with
IJ40943 SRC_TRYX, SRC_RSTRT ERRLOG ENTRIES WITH ASO IN VIOS ENVIRONMENT
See APAR details for workaround.
This also applies to VIOS 3.1.4 and it is fixed with IJ41746.

Environment

VIOS 3.1

Diagnosing The Problem

Determine whether aso exits in inittab.  As padmin, run:
$ oem_setup_env
$ lsitab -a|grep -i aso
aso:23456789:once:/usr/bin/startsrc -s aso

Resolving The Problem

ASO subsystem is mainly designed for AIX and not for VIOS.  It will be disabled in future VIOS releases.
The APAR is a packaging fix to permanently remove the entries where aso is not applicable.
It does not fix the issue with respect to ASO failing to start in VIOS during VIOS reboot.
To prevent future errors, remove aso from inittab.  As padmin user, run:
$ oem_setup_env
# rmitab aso

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"ARM Category":[{"code":"a8mKe000000TN3UIAW","label":"ERRPT"}],"ARM Case Number":"TS018210745","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
05 February 2025

UID

ibm17181372

Page Feedback