Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZWESLSTC failed to start #2315

Closed
connorpekovic opened this issue Jul 27, 2022 · 21 comments
Closed

ZWESLSTC failed to start #2315

connorpekovic opened this issue Jul 27, 2022 · 21 comments
Assignees
Labels
area: zos-install-upgrade Issues related to Zowe z/OS components installation, mostly using convenience build. type: troubleshoot Troubleshooting tips and questions

Comments

@connorpekovic
Copy link

connorpekovic commented Jul 27, 2022

Description

Hi Zowe Team!

At our shop we have ZWESISTC started 🎉. We ran zwe start --config path/to/zowe.yaml to start ZWESLSTC and got this output in the console.

$ export PATH=${PATH}:/usr_lpp/zowe/bin                                         
                                    
$ zwe start --config /path/to/zowe.yaml                             
=============================================================================== 
>> STARTING ZOWE                                                                
                                                                                
  * Output:                                                                     
    node: read_yaml 10: /usr_lpp/zowe/bin/commands/start/index.sh 21: .: zwecli_
process_command 4: /usr_lpp/zowe/bin/zwe 96: FSUM7351 not found                 
  * Output:                                                                     
    node: read_yaml 10: /usr_lpp/zowe/bin/commands/start/index.sh 22: .: zwecli_
process_command 4: /usr_lpp/zowe/bin/zwe 96: FSUM7351 not found                 
  * Output:                                                                     
    node: read_yaml 10: /usr_lpp/zowe/bin/commands/start/index.sh 29: .: zwecli_
process_command 4: /usr_lpp/zowe/bin/zwe 96: FSUM7351 not found                 
------------------------------------------------------------------------------- 
>> Job security_stcs_zowe is started successfully.                              
                                                                                
$                                                                               

We got this output in the SYSPRINT.

2022-07-27 12:57:59 <ZWELNCH:50398258> ZWESLSTC INFO ZWEL0021I Zowe Launcher starting
2022-07-27 12:57:59 <ZWELNCH:50398258> ZWESLSTC INFO ZWEL0023I Zowe YAML config  file is '/path/to/zowe.yaml'
2022-07-27 12:57:59 <ZWELNCH:50398258> ZWESLSTC INFO ZWEL0024I HA_INSTANCE_ID is 'lpar1'
2022-07-27 12:57:59 <ZWELNCH:50398258> ZWESLSTC INFO ZWEL0020I loading '/path/to/zowe.yaml'
2022-07-27 12:57:59 <ZWELNCH:50398258> ZWESLSTC INFO ZWEL0017I ROOT_DIR is '/usr_lpp/zowe/bin'
2022-07-27 12:57:59 <ZWELNCH:50398258> ZWESLSTC INFO ZWEL0058I WORKSPACE_DIR is '/path/to/workspace'
2022-07-27 12:57:59 <ZWELNCH:50398258> ZWESLSTC ERROR ZWEL0030E failed to prepare Zowe instance

This isn't a documentation issue as much as it is my mainframe shop looking for support. Our shop completed every step in the documentation leading up to this step. I can supply more info as needed.

Pages to Update

Screenshots

Expected behavior

Expected the ZWESLSTC to start and stay up.

Additional context

Big thank you!

@nannanli
Copy link
Member

@Joe-Winchester @jackjia-ibm @1000TurquoisePogs Hi all, do you have any suggestions or insights about the issue described above? Thank you!

@nannanli nannanli added area: zos-install-upgrade Issues related to Zowe z/OS components installation, mostly using convenience build. type: troubleshoot Troubleshooting tips and questions labels Jul 28, 2022
@nannanli nannanli changed the title Issue with docs.zowe.org/stable/user-guide/start-zowe-zos ZWESLSTC failed to start Jul 28, 2022
@jackjia-ibm
Copy link
Member

@connorpekovic I saw potentially 2 issues from the info you provided:

  1. ZWEL0017I ROOT_DIR is '/usr_lpp/zowe/bin', usually ROOT_DIR shouldn't point to the bin folder but the zowe root directory. Normally, this value should be /usr_lpp/zowe. You may double check the value of zowe.runtimeDirectory.
  2. node: read_yaml 10: /usr_lpp/zowe/bin/commands/start/index.sh 21: .: zwecli_process_command 4: /usr_lpp/zowe/bin/zwe 96: FSUM7351 not found error is usually caused by cannot find node. Please double check if node.home is properly defined in zowe.yaml, including indentation format.

Please let us know if this solves the issues you have.

@connorpekovic
Copy link
Author

@jackjia-ibm

Thank you! The team made a change and this is the new output in ZWESLSTC's SYSPRINT: The output in the Unix console was the same:

2022-07-28 13:28:52 <ZWELNCH:50398198> ZWESLSTC INFO ZWEL0021I Zowe Launcher starting 
2022-07-28 13:28:52 <ZWELNCH:50398198> ZWESLSTC INFO ZWEL0023I Zowe YAML config file is '/global/zowe/zowe200/zowe.yaml' 
2022-07-28 13:28:52 <ZWELNCH:50398198> ZWESLSTC INFO ZWEL0024I HA_INSTANCE_ID is 'lpar1' 
2022-07-28 13:28:52 <ZWELNCH:50398198> ZWESLSTC INFO ZWEL0020I loading '/global/zowe/zowe200/zowe.yaml' 
2022-07-28 13:28:52 <ZWELNCH:50398198> ZWESLSTC INFO ZWEL0017I ROOT_DIR is '/usr_lpp/zowe' 
2022-07-28 13:28:52 <ZWELNCH:50398198> ZWESLSTC INFO ZWEL0058I WORKSPACE_DIR is '/global/zowe/workspace' 
2022-07-28 13:28:54 <ZWELS:67175123> ZWESLSTC INFO (zwe-internal-start-prepare:337) Zowe version: v2.0.0 
2022-07-28 13:28:57 <ZWELS:67175123> ZWESLSTC INFO (zwe-internal-start-prepare:338) build and hash: v2.x/master#995 (0d8d5bf395041167f07bb047f34708e3ba261405) 
  * Output:       
    node: read_yaml 10: /usr_lpp/zowe/bin/commands/internal/start/prepare/index.sh 350: .: zwecli_process_command 4: /usr_lpp/zowe/bin/zwe 96: FSUM7351 not found 
2022-07-28 13:28:58 <ZWELS:67175123> ZWESLSTC INFO (zwe-internal-start-prepare:354) starting Zowe instance lpar1 with /global/zowe/zowe200/zowe.yaml ... 
2022-07-28 13:28:58 <ZWELS:67175123> ZWESLSTC ERROR (zwe-internal-start-prepare,prepare_workspace_directory:19) WARNING: Failed to set permission of some existing files or directories in /global/zowe/workspace: 
2022-07-28 13:28:58 <ZWELS:67175123> ZWESLSTC ERROR (zwe-internal-start-prepare,prepare_workspace_directory:20) chmod: FSUM6180 file "/global/zowe/workspace": EDC5139I Operation not permitted. (errno2=0x00000004) 
node: generate_instance_env_from_yaml_config 15: prepare_workspace_directory 37: /usr_lpp/zowe/bin/commands/internal/start/prepare/index.sh 366: .: zwecli_process_command 4: /usr_lpp/zowe/bin/zwe 96: FSUM7351 not found 
2022-07-28 13:28:58 <ZWELS:67175123> ZWESLSTC ERROR (bin/libs/config.sh,generate_instance_env_from_yaml_config:19) ZWEL0140E: Failed to translate Zowe configuration (/global/zowe/zowe200/zowe.yaml). 
2022-07-28 13:28:58 <ZWELNCH:50398198> ZWESLSTC ERROR ZWEL0030E failed to prepare Zowe instance 

Thank you so much!
Connor

@jackjia-ibm
Copy link
Member

@connorpekovic there are 2 issues from this log:

  1. node is still not found. There are few things to double check:
    • if node.home is defined in zowe.yaml, and if the format/indentation is good.
    • whether there is bin/node executable under the directory of node.home.
    • if node.home section is too complicated. Reading this value is using shell script. Sometimes if this section is too complicated, like multiple home: lines, etc, may confused the parser.
  2. ZWEL0140E: Failed to translate Zowe configuration is caused by permission failure on workspace directory. Will need to make sure that Zowe run time user (by default ZWESVUSR) has write permission on it.

@connorpekovic
Copy link
Author

@jackjia-ibm @nannanli The ZWESLSTC has now started and stayed up!!

There's still work to done at our shop. We're at version 2.0 and the caching service is not starting because it's HLQ is in our SMPE zone, presumably because that's we set our zowe.setup.dataset.prefix to. We'll tackle that tomorrow morning.

We hope the Zowe Desktop comes up after the caching service is fixed, then we can begin validating our Zowe installation and then begin standing up UMS for z/OS to get IBM DB2 Admin Foundations.

@Knamasiv
Copy link

Knamasiv commented May 6, 2024

/u/users/zowe/usr/lpp/zowrtm/bin/commands/start/index.sh 21: .: zwecli_process_command 4: ./zwe 96: FSUM7351 not found
Exit code: 255

14.40.36 STC32143 IFA104I REGISTRATION HAS BEEN DENIED FOR 072
072 PRODUCT WITH OWNER=IBM CORP NAME=z/OS
072 FEATURE=SDSF VERSION=.. ID=5650-ZOS

I received above error while starting zowe from USS, please suggest steps to fix this issue

I have node pointed to path /u/users/zowe/usr/lpp/IBM/cnj/v20r0/IBM/node-v20.11.0-os390-s390x-202402131732 in YAML file

@Joe-Winchester
Copy link
Member

@joepun76 , do you have anything quick you can spot from the above log extract.

@Knamasiv
Copy link

Knamasiv commented May 9, 2024

Hi Joe,
We received below error in the log.

2024-05-08 16:30:34 ZWELNCH:84476275 ZWESVUSR INFO ZWEL0021I Zowe Launcher starting
2024-05-08 16:30:34 ZWELNCH:84476275 ZWESVUSR INFO ZWEL0023I Zowe YAML config file is '/309C/u/users/zowe/zowe.yaml'
2024-05-08 16:30:34 ZWELNCH:84476275 ZWESVUSR INFO ZWEL0024I HA_INSTANCE_ID is '309c'
2024-05-08 16:30:34 ZWELNCH:84476275 ZWESVUSR INFO ZWEL0020I loading '/309C/u/users/zowe/zowe.yaml'
2024-05-08 16:30:34 ZWELNCH:84476275 ZWESVUSR INFO ZWEL0017I ROOT_DIR is '/309C/u/users/zowe/usr/lpp/zowrtm'
2024-05-08 16:30:34 ZWELNCH:84476275 ZWESVUSR INFO ZWEL0058I WORKSPACE_DIR is '/309C/u/users/zowe/workspace'
2024-05-08 16:31:58 ZWELS:34144821 ZWESVUSR INFO (zwe-internal-start-prepare:337) Zowe version: v2.0.0
2024-05-08 16:32:06 ZWELS:34144821 ZWESVUSR INFO (zwe-internal-start-prepare:338) build and hash: v2.x/master#995 (0d8d5bf395041167f07bb047f34708e3ba261405)

  • Output:
    node: read_yaml 10: /309C/u/users/zowe/usr/lpp/zowrtm/bin/commands/internal/start/prepare/index.sh 350: .: zwecli_process_command 4: /309C/u/users/zowe/usr/lpp/zowrtm/bin/zwe 96: FSUM7351 not found
    2024-05-08 16:32:15 ZWELS:34144821 ZWESVUSR INFO (zwe-internal-start-prepare:354) starting Zowe instance 309c with /309C/u/users/zowe/zowe.yaml ...
    node: generate_instance_env_from_yaml_config 15: prepare_workspace_directory 37: /309C/u/users/zowe/usr/lpp/zowrtm/bin/commands/internal/start/prepare/index.sh 366: .: zwecli_process_command 4: /309C/u/users/zowe/usr/lpp/zowrtm/bin/zwe 96: FSUM7351 n
    2024-05-08 16:32:25 ZWELS:34144821 ZWESVUSR ERROR (bin/libs/config.sh,generate_instance_env_from_yaml_config:19) ZWEL0140E: Failed to translate Zowe configuration (/309C/u/users/zowe/zowe.yaml).
    2024-05-08 16:32:26 ZWELNCH:84476275 ZWESVUSR ERROR ZWEL0030E failed to prepare Zowe instance

ZWESVUSR id have been given superuser authority UID(0)

@joepun76
Copy link

joepun76 commented May 11, 2024 via email

@joepun76
Copy link

joepun76 commented May 13, 2024 via email

@Knamasiv
Copy link

Yes its new zowe install. I did through SMPE. Now I can start ZWESLSTC task but receiving error
IEF403I ZWESLSTC - STARTED - TIME=12.59.34
+ZWEL0021I Zowe Launcher starting
$HASP708 ZWESLSTC CEEOPTS OPEN FAILED
RC=03 DATA SET ALREADY OPENED
DSNAME=ZWESVUSR.ZWESLSTC.STC00296.D0000101.?
IEC141I 013-C0,IGG0199G,ZWESLSTC,ZWESLSTC,CEEOPTS 927
ERROR DESCRIPTION: IEC141I
An open failure occurred for a subsystem data set.Possible failures
follow:

  • A SYSIN or SYSOUT data set opened by JES.
  • A SYSIN or SYSOUT data set opened under the master subystem.
  • A subsystem data set(such as an HFS data set) that uses the same
    interface as JES.
  • For JES2, a SYSOUT data set incurred a subsystem JCL failure(SJF),
    and JES2 might issue a $HASP708 message to further describe the error.
    For JES3, a reserved DD name, such as JOURNAL, might have been
    specified in a DD statement. In either case, the failing DCB was not
    opened; processing for other DCBs opened in parallel continues
    normally.

ZWESLSTC JCL:
//ZWESLSTC PROC RGN=0M
//ZWELNCH EXEC PGM=ZWELNCH,REGION=&RGN,TIME=NOLIMIT,
// PARM='ENVAR(_CEE_ENVFILE=DD:STDENV)/&HAINST.'
//STEPLIB DD DSNAME=SYSP.GT.ZOWE.SZWEAUTH,DISP=SHR
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=,LRECL=1600
//SYSERR DD SYSOUT=

//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//CEEOPTS DD *
POSIX(ON)
//STDENV DD *
CONFIG=/309C/u/users/zowe/zowe.yaml
/*

@joepun76
Copy link

joepun76 commented May 13, 2024 via email

@Knamasiv
Copy link

Thanks Joe. Yes we applied latest PTF and current version of Zowe is 2.15. I made change to the Started task JCL and didn't get any error related to CEEOPTS.

@joepun76
Copy link

joepun76 commented May 14, 2024 via email

@Knamasiv
Copy link

Thanks Joe.
I am getting below error in ZSS appserver log

ZWES1060W Failed to init TLS environment, rc=1(Handle is not valid)
ZWES1065E Failed to configure https server, check agent https settings

@Knamasiv
Copy link

In Appserver log, I could see below error

ZWED0159E - Could not read zowe manifest, version unknown

@joepun76
Copy link

joepun76 commented May 15, 2024 via email

@joepun76
Copy link

joepun76 commented May 15, 2024 via email

@Knamasiv
Copy link

ZWESLSTC task is up with errors related to HTTPS
Could you please provide your email-id to send YAML file

@joepun76
Copy link

joepun76 commented May 15, 2024 via email

@Knamasiv
Copy link

Hi Joe,
Please share your email-id

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: zos-install-upgrade Issues related to Zowe z/OS components installation, mostly using convenience build. type: troubleshoot Troubleshooting tips and questions
Projects
None yet
Development

No branches or pull requests

6 participants