search

zowe / zlux

The top-level superproject for zLUX. zLUX includes the Zowe Desktop framework in addition to several built-in apps and an example server implementation.
Eclipse Public License 2.0
39 stars 42 forks source link

ZOWE1EJ, ZOWE1EF, ZOWE1DT ABEND=SEC6 #634

Closed John-A-Davies closed 3 weeks ago

John-A-Davies commented 5 years ago

Describe the bug ZOWESVR starts but ends prematurely because 3 STCs terminate with SIGHUP.

In order to do internal testing with ZOWE, I have installed ZOWE 1.5.0 on a z/OS 02.03.00 - FMID HBB77B0 (SP7.2.3), but I cannot get it to run normally. When I start ZOWE, it starts bringing the different ZOWE tasks up until some (ZOWE1EJ, ZOWE1EF & ZOWE1DT) ABEND=SEC6 U0000 REASON=0000FF01 then ZOWESVR ends with a message $HASP395 ZOWESVR ENDED - RC=0000I have attached the ZOWESVR STD.err, the STD.out, two logs created in /usr/lpp/zowe/1.5.0/zlux-app-server/log/, ZOWESVR syslog messages, zowe-check-prereqs.sh and zowe-verify.sh execution. The last message I receive in the different files is: CEE5210S The signal SIGHUP was received.

Steps to Reproduce

  1. S ZOWESVR from the operator cmd line via SDSF.

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Logs

IEA989I SLIP TRAP ID=XEC6 MATCHED.  JOBNAME=ZOWE1EF , ASID=009D.      
BPXP023I THREAD 0EE4A00000000001, IN PROCESS 50331656, WAS 902        
TERMINATED BY SIGNAL SIGHUP, SENT FROM THREAD                         
0EE4B80000000000, IN PROCESS 83886233, UID 10, IN JOB ZOWESVR.        
IEA989I SLIP TRAP ID=XEC6 MATCHED.  JOBNAME=ZOWE1EJ , ASID=00B7.      
BPXP023I THREAD 0EEDF80000000001, IN PROCESS 67108875, WAS 904        
TERMINATED BY SIGNAL SIGHUP, SENT FROM THREAD                         
0EE4B80000000000, IN PROCESS 83886233, UID 10, IN JOB ZOWESVR.        
IEF450I ZOWE1EJ STEP1 - ABEND=SEC6 U0000 REASON=0000FF01 905          
        TIME=11.31.28                                                 
IEA989I SLIP TRAP ID=XEC6 MATCHED.  JOBNAME=ZOWE1DT , ASID=00B1.      
PAGEAOOPER |AUTCRIT IEF450I ZOWE1EJ STEP1 - ABEND=SEC6 U0000          
REASON=0000FF01                                                       
IEF450I ZOWE1EF STEP1 - ABEND=SEC6 U0000 REASON=0000FF01 910          
        TIME=11.31.28                                                 
PAGEAOOPER |AUTCRIT IEF450I ZOWE1EF STEP1 - ABEND=SEC6 U0000          
REASON=0000FF01                                                       
BPXP023I THREAD 0EEBE00000000000, IN PROCESS 189, WAS 914             
TERMINATED BY SIGNAL SIGHUP, SENT FROM THREAD                         
0EE4B80000000000, IN PROCESS 83886233, UID 10, IN JOB ZOWESVR.        
IEF450I ZOWE1DT STEP1 - ABEND=SEC6 U0000 REASON=0000FF01 915          
        TIME=11.31.28                                                 
PAGEAOOPER |AUTCRIT IEF450I ZOWE1DT STEP1 - ABEND=SEC6 U0000          
REASON=0000FF01                                                       
IEF404I ZOWESVR - ENDED - TIME=11.31.29                               
$HASP395 ZOWESVR  ENDED - RC=0000                                     
$HASP250 ZOWESVR PURGED -- (JOB KEY WAS D6E91A66)

Details node v8.16.0 Customer: CGI, Toronto. ZOWE 1.5.0 on a z/OS 02.03.00 - FMID HBB77B0 (SP7.2.3)

Web Browser Details (if the bug relates to Zowe Desktop usage): n/a

REST API client (in case of REST API issue):

Shell Environment Details (if the bug relates to CLI):

Additional context There is a non-EBCDIC line in the middle of ZOWESVR STDOUT, which when I convert it reads:

[explorer-jes] config file /usr/lpp/zowe/1.5.0/jes_explorer/server/configs/config.json:
[explorer-jes] paths will be served:
[explorer-jes]   - /ui/v1/explorer-jes => /usr/lpp/zowe/1.5.0/jes_explorer/app
[explorer-uss] config file /usr/lpp/zowe/1.5.0/uss_explorer/server/configs/config.json:
[explorer-uss] paths will be served:
[explorer-uss]   - /ui/v1/explorer-uss => /usr/lpp/zowe/1.5.0/uss_explorer/app
[explorer-mvs] config file /usr/lpp/zowe/1.5.0/mvs_explorer/server/configs/config.json:
[explorer-mvs] paths will be served:
[explorer-mvs]   - /ui/v1/explorer-mvs => /usr/lpp/zowe/1.5.0/mvs_explorer/app
[explorer-jes] is started and listening on 8546...

[explorer-uss] is started and listening on 8550...

[explorer-mvs] is started and listening on 8548...
John-A-Davies commented 5 years ago

Here is the SYSLOG for that system during the execution of ZOWESVR.
ZOWESVR.SYSLOG.SEC6.TXT

John-A-Davies commented 5 years ago

SEC6 is an ABEND due to a USS process being terminated. The tasks that got SEC6 were

ZOWE1EF - java in support of Explorer API (Files?)
ZOWE1EJ - java in support of Explorer API (jobs)
ZOWE1DT - nodeCluster, zlux-app-server, Desktop App server

The customer system has a SLIP trap enabled on SEC6 (this is standard), which means that any abrupt termination e.g. by SIGxxxx will be logged.

John-A-Davies commented 5 years ago

We're looking at

John-A-Davies commented 5 years ago

SFavreau 4:24 PM Doing a GOOGLE search on this error message (Failed to start component [Connector[HTTP/1.1-9545]org.apache.catalina.LifecycleException: Protocol handler start failed ) tell me that the Tomcat connector is configured to listen on port 8545 failed to start. The port may already be in use or the connector may be misconfigured. (edited) The port 8545 is not used. Just to make sure, I redo the test using another port (9545). I have the same problem; the applicatioon loop about 10 times getting this error message everytime before it end: 2019-11-29 15:58:56.307 Z6003Q ERROR (o.a.c.u.LifecycleBase,DirectJDKLog.java:175) Failed to start component [Con nector[HTTP/1.1-9545]org.apache.catalina.LifecycleException: Protocol handler start failed

1000TurquoisePogs commented 3 weeks ago

Closing as v1, oudated