The following topics contain information that can help you troubleshoot problems when you encounter unexpected behavior installing Zowe z/OS components or starting Zowe's
ZWESVSTC started task.
When you start
ZWESVSTC started task, either by running the
zowe-start.sh script or by launching the started task directly, you encounter the following error in the log:
You will also encounter the following messages in the SYSLOG:
This problem occurs when the maximum number of
BPXAS instances have been reached.
This may be because when the Zowe instance directory was created, it was generated in the same location as the Zowe root directory. The Zowe instance directory is created by using the script
<RUNTIME_DIR>/bin/zowe-configure-instance.sh -c <PATH_TO_INSTANCE_DIR>. See Creating an instance directory. The Zowe runtime directory is replaced when new PTFs are applied and should be considered as a read-only set of files. Zowe instance directories are designed to live outside the directory structure and are used to start a Zowe runtime.
This problem will only occur with Zowe drivers prior to v1.10 and has been resolved in v1.10 where the
zowe-configure-instance.sh script will report error if it detects the
-c argument because the installation directory location is an existing Zowe runtime directory.
When you start the
ZWESVSTC started task, you encounter the following error messages:
This problem occurs when you use Node.js v8.16.1 which is not supported on Zowe. There is a known issue with node.js v8.16.1 and Zowe desktop encoding. Use a supported version of Node.js instead. For more information, see Supported Node.js versions.
When you start the ZWESVSTC started task, you might encounter the following error message:
Check that /bin is part on your PATH. Do
echo $PATH to check. If it is missing, make sure that it is appended to PATH in your profile, for example, in
When you configure the Zowe environment variable
instance.env with a domain (for example,
domain-a.com), and access Zowe with another domain (for example,
domain-b.com), you may see the following errors:
Certificate warnings similar to the following one:domain-b.com:8544 uses an invalid security certificate.The certificate is only valid for the following names: domain-a.com, <ip-of-domain-a>, localhost.localdomain, localhost, 127.0.0.1
No pinned applications show in Zowe Desktop.
JES Explorer, MVS Explorer, USS Explorer may show errors similar to the following one if you ignore the certificate error.Blocked by Content Security PolicyAn error occurred during a connection to domain-a.com:7554.Firefox prevented this page from loading in this way because the page has a content security policy that disallows it.
The above warnings and errors will also show when you plan to use Zowe with multiple domain names.
You can take the following steps:
When you prepare the
bin/zowe-setup-certificates.envfile, specify the
IPADDRESS=parameters to accept multiple domains separated by comma (from Zowe v1.14.0). The following configuration is an example:HOSTNAME=domain-a.com,domain-b.comIPADDRESS=<ip-of-domain-a>,<ip-of-domain-b>
Then you can proceed to run the
After you run the
bin/zowe-configure-instance.shscript, modify the
instance.envfile located in the instance directory in the following ways to reflect the multiple domains you plan to use.
- Add a line of
ZWE_EXTERNAL_HOSTS. For example,
- Add a line of
ZWE_REFERRER_HOSTS. For example,
- Find the line that starts with
ZOWE_EXPLORER_FRAME_ANCESTORSand modify its values to
- Add a line of
With this change, you must use the API Mediation Layer Gateway port (default is 7554) to access Zowe Desktop, for example,
https://domain-b.com:7554/ui/v1/zlux. Using Desktop port (default is 8544) like
https://domain-b.com:8544/ is not supported.