Zowe errors ZWEAM100E, ZWEAM500W , ZWEAG713E, ZWEAG108E, ZWEAC705W, ZWEAG181W, ZWES1606W

Products

Zowe

Issue/Introduction

Installed Zowe 3.0 and after running the started task ZWESLSTC seeing some errors/warnings per below:

<ZWEAZS1:main: > Ã35mMXZWE1 Ã0;39m Ã36mERROR Ã0;39m ((o.z.a.p.v.BuildInfo)) ZWEAM100E Could not read properties from: 'META-INF/git.properties'
ZWEAG713E Configuration error when trying to establish JWT producer.
ZWEAG108E z/OSMF instance 'ibmzosmf' not found or incorrectly configured. ZAAS is shutting down.
ZWEAC705W The home page url for service IBMZOSMF was not transformed. Not able to select route for url https://##.##.#.#:443/ of the service ibmzosmf. Original url used.

z/OSMF is in the same system connecting with https://##.##.#.#:443/zosmf.
Not sure why its showing the error "ZWEAG181W z/OSMF service 'ibmzosmf' is either not registered or not online yet."

Also provided the full STC log.

Environment

Zowe 3.0

Resolution

The STC log shows ZWEAM100E, ZWEAM500W, ZWEAG181W, ZWEAC705W, ZWES1606W and repeated certificate related errors "Fatal (CERTIFICATE_UNKNOWN): No subject alternative names matching IP address ##.##.#.# found"

*****
...
2025-06-23 07:20:38.091 <ZWEAZS1:main: > Ý35mMXZWE1Ý0;39m Ý36mERRORÝ0;39m ((o.z.a.p.v.BuildInfo)) ZWEAM100E Could not read properties from: 'META-INF/git.properties'
...
2025-06-23 07:20:48.308 <ZWEAGW1:main:50401805> Ý35mMXZWE1Ý0;39m Ý36mWARN Ý0;39m ((o.z.a.s.HttpsFactory)) ZWEAM500W The service is not verifying the TLS/SSL certificates of the services
... error parsing JSON response
2025-06-23 07:21:43.356 <ZWEAZS1:Timer-1:50401817> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((o.z.a.z.s.l.Providers)) ZWEAG181W z/OSMF service 'ibmzosmf' is either not registered or not online yet.
2025-06-23 07:21:43.450 <ZWED:33624605> MXZWE1 INFO (_zsf.install,webapp.js:2068) ZWED0068I - Creating composite swagger endpoint for org.zowe.zlux
2025-06-23 07:21:43.451 <ZWED:33624605> MXZWE1 INFO (_zsf.install,webapp.js:2075) ZWED0069I - Creating swagger endpoint for org.zowe.zlux:server-plugins-api
2025-06-23 07:21:43.690 <ZWEAGW1:parallel-5:50401805> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((o.s.c.l.c.RoundRobinLoadBalancer)) No servers available for service: zaas
2025-06-23 07:21:43.690 <ZWEAGW1:parallel-5:50401805> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((o.s.c.c.l.r.ReactorLoadBalancerExchangeFilterFunction)) LoadBalancer does not contain an instance for the service zaas
error parsing JSON response
2025-06-23 07:21:53.704 <ZWEAGW1:parallel-1:50401805> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((o.s.c.l.c.RoundRobinLoadBalancer)) No servers available for service: zaas
2025-06-23 07:21:53.704 <ZWEAGW1:parallel-1:50401805> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((o.s.c.c.l.r.ReactorLoadBalancerExchangeFilterFunction)) LoadBalancer does not contain an instance for the service zaas
2025-06-23 07:21:56.501 <ZWEAAC1:scheduling-1:16847386> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((o.z.a.a.s.c.CachedProductFamilyService)) ZWEAC705W The home page url for service ZSS was not transformed. Not able to select route for url h
2025-06-23 07:21:56.503 <ZWEAAC1:scheduling-1:16847386> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((o.z.a.a.s.c.CachedProductFamilyService)) ZWEAC705W The home page url for service IBMZOSMF was not transformed. Not able to select route for
2025-06-23 07:21:58.372 <ZWEAZS1:Timer-1:50401817> Ã35mMXZWE1Ã0;39m Ã36mINFO Ã0;39m ((o.z.a.p.s.ServiceStartupEventHandler)) ZWEAM000I ZAAS started in 84.52 seconds
error parsing JSON response
2025-06-23 07:22:03.719 <ZWEAGW1:parallel-3:50401805> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((o.s.c.l.c.RoundRobinLoadBalancer)) No servers available for service: zaas
2025-06-23 07:22:03.719 <ZWEAGW1:parallel-3:50401805> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((o.s.c.c.l.r.ReactorLoadBalancerExchangeFilterFunction)) LoadBalancer does not contain an instance for the service zaas
error parsing JSON response
ZWES1606W Failed to get JWK. rc=HTTP response error - invalid JSON (3), rsn=Invalid port (3). Retry in 10 seconds
2025-06-23 07:22:13.733 <ZWEAGW1:parallel-5:50401805> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((o.s.c.l.c.RoundRobinLoadBalancer)) No servers available for service: zaas
2025-06-23 07:22:13.733 <ZWEAGW1:parallel-5:50401805> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((o.s.c.c.l.r.ReactorLoadBalancerExchangeFilterFunction)) LoadBalancer does not contain an instance for the service zaas
2025-06-23 07:22:20.757 <ZWEAGW1:DiscoveryClient-InstanceInfoReplicator-%d:50401805> Ã35mMXZWE1Ã0;39m Ã36mINFO Ã0;39m ((o.z.a.g.c.GatewayHealthIndicator)) ZWEAM001I API Mediation Layer started
error parsing JSON response
2025-06-23 07:22:24.252 <ZWEAZS1:https-jsse-nio-0.0.0.0-7558-exec-2:50401817> Ã35mMXZWE1Ã0;39m Ã36mERRORÃ0;39m ((javax.net.ssl)) Fatal (CERTIFICATE_UNKNOWN): Received fatal alert: certificate_unknown
2025-06-23 07:22:23.761 <ZWEAGW1:parallel-1:50401805> Ã35mMXZWE1Ã0;39m Ã36mWARN Ã0;39m ((i.n.u.NetUtilInitializations)) Failed to find the loopback interface
2025-06-23 07:22:24.231 <ZWEAGW1:reactor-http-nio-2:50401805> Ã35mMXZWE1Ã0;39m Ã36mERRORÃ0;39m ((javax.net.ssl)) Fatal (CERTIFICATE_UNKNOWN): No subject alternative names matching IP address ##.##.#.# found
...
*****

There are multiple issues:

The yaml file had "verifyCertificates: DISABLED".
After changing to "verifyCertificates: NONSTRICT" the ZWEAM500W message was removed.
Error "ZWES1606W Failed to get JWK" has been observed before with Zowe 3.0 per GitHub - z/OSMF JWT regression #4092
Change the yaml file line:
jwtAutoconfiguration: jwt
TO:
jwtAutoconfiguration: ltpa
There was a certificate issue and using the correct certificate removed the CERTIFICATE_UNKNOWN messages. As part of that change yaml file parameter externalDomains was also changed to add a valid FQDN as the first entry (IP address ##.##.#.# kept as 2nd entry).
For the remaining messages Zowe Engineering advised:
These messages can happen during startup because Zowe components don't start in order and at startup time they try to talk to one another before they are available.
ZWEAC705W - not all services have home page configured, this is just warning that can be ignored.
ZWEAG181W - most likely z/OSMF will get registered eventually, repeated messages are repeated attempts until success. If login to API Catalog works, z/OSMF registered as it is used as authentication service. So if these messages don't repeat after start up everything should be OK.

The best way to confirm success is to login to API Catalog web UI, this will use all APIML components.

- Go to APIML landing page: https://gatewayHostname:7554
- Confirm three green checks
- Click on "The API Catalog Service is running"
- Login using MF credentials

If all these steps work and login is successful then the Zowe start up has been successful.

NOTE: Subsequently there was also a firewall access issue which was resolved by the network team.