Zowe V3 API ML does not start as expected #3924
Unanswered
PavelKondratiev
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi team,
I installed and configured Zowe V3 on zPDT z/OS V2.5 system. Enabled to start 3 API ML components only : API catalog, discovery and gateway. Created and configured z/OS keyring, CA and server certificates for the product.
Started with almost no errors but cannot get API Catalog and authentication services online in UI :
The only explicit error I see in the log is the same one I already reported in ticket #3920
2024-12-05 21:41:23.042 ZWEAGW1:main:50397782 �[35mZWESVUSR�[0;39m �[36mERROR�[0;39m ((o.z.a.p.v.BuildInfo)) ZWEAM100E Could not read properties from: 'META-INF/git.properties'
Another issue is I do not see ZWEAM000I message for gateway service, though other messages seems to indicate it was started successfully :
2024-12-06 20:08:22.586 ZWEAGW1:main:50397909 �[35mZWESVUSR�[0;39m �[36mINFO �[0;39m ((o.s.c.n.e.s.EurekaServiceRegistry)) Registering application GATEWAY with eureka with status UP
2024-12-06 20:08:31.206 ZWEAGW1:main:50397909 �[35mZWESVUSR�[0;39m �[36mINFO �[0;39m ((o.a.c.h.Http11NioProtocol)) Starting ProtocolHandler ["https-jsse-nio-0.0.0.0-7554"]
2024-12-06 20:08:34.420 ZWEAGW1:main:50397909 �[35mZWESVUSR�[0;39m �[36mDEBUG�[0;39m ((o.a.t.u.n.j.JSSEUtil)) The [protocols] that are active are : [[TLSv1.3, TLSv1.2]]
2024-12-06 20:08:34.472 ZWEAGW1:main:50397909 �[35mZWESVUSR�[0;39m �[36mDEBUG�[0;39m ((o.a.t.u.n.o.c.OpenSSLCipherConfigurationParser)) Ciphers used: [TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,,TLS_AES_128_GCM_SHA256,,TLS_AES_256_GCM_SHA384,]
2024-12-06 20:08:34.517 ZWEAGW1:main:50397909 �[35mZWESVUSR�[0;39m �[36mDEBUG�[0;39m ((o.a.t.u.n.j.JSSEUtil)) The [ciphers] that are active are : [[TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384]]
2024-12-06 20:08:34.848 ZWEAGW1:main:50397909 �[35mZWESVUSR�[0;39m �[36mINFO �[0;39m ((o.a.t.u.n.N.certificate)) Connector [https-jsse-nio-0.0.0.0-7554], TLS virtual host [default], certificate type [UNDEFINED] configured from keystore [/tmp/.keystore] using alias [ZOWE_server_Z25C] with trust store [null]
2024-12-06 20:08:35.423 ZWEAGW1:main:50397909 �[35mZWESVUSR�[0;39m �[36mDEBUG�[0;39m ((o.a.t.u.n.N.certificate))
[
SHA-256 fingerprint: 8b6cd2e7a671975c4869db7698221386b296ab6b43959d0f43e1edc190bfa5d7
SHA-1 fingerprint: 678fdba2c4fb055e67379e9d04185978351641c6
[
[
Version: V3
Subject: CN=zPDT_ZOWE_Z25C, OU=Mainframe department, O=IBA Group, C=CZ
Signature Algorithm: SHA256withRSA, OID = 1.2.840.113549.1.1.11
Key: algorithm = RSA, unparsed keybits =
0000: 30 82 01 0a 02 82 01 01 00 b0 00 3e 41 d2 57 64 0...........A.Wd
0010: ea 0b de 54 42 fa ed 35 ad 77 f3 f6 97 7f ea 17 ...TB..5.w......
0020: 23 52 a7 04 c4 45 67 84 b6 cc c4 89 a0 5d 3e 94 .R...Eg.........
0030: b6 37 f0 99 86 7a b7 09 fb 9d d7 07 44 d9 a4 16 .7...z......D...
0040: 45 f0 8e 30 a2 82 59 25 aa dc 7d 1a 49 32 a0 08 E..0..Y.....I2..
0050: 3a b1 f7 f5 f9 45 7e 7d a5 bb ca 38 ab 34 72 d0 .....E.....8.4r.
0060: 82 c1 70 aa 0d 0a 6b 29 74 2e 1b 02 38 ae fe 89 ..p...k.t...8...
0070: a2 db 31 9c c2 b7 81 34 fa 01 ee a7 1d fc 18 68 ..1....4.......h
0080: 54 34 fe 78 00 10 b4 48 5b ca f1 79 5b 58 3f e6 T4.x...H...y.X..
0090: 88 c8 92 34 39 b4 19 2d eb 6c 9c b6 0c f9 7e 4a ...49....l.....J
00a0: d5 d8 65 9c ed f1 a1 5c fe 87 cc 62 fc 39 0f f3 ..e........b.9..
00b0: a8 d3 81 3c bd e4 0e 20 7e ae 90 2b 1b 61 c7 71 .............a.q
00c0: de c5 b3 ba 8b 7f 95 6e 06 97 a8 e6 3b 22 7b f8 .......n........
00d0: f0 ce c9 30 ba 91 a2 fe a6 37 6f 4b 2f f8 f8 9c ...0.....7oK....
00e0: 43 c3 e7 12 b6 2d 5a ab 85 c8 4d 41 25 5a 47 d6 C.....Z...MA.ZG.
00f0: e6 07 ab 6f 67 91 61 fb aa 57 f5 62 19 3f ce b4 ...og.a..W.b....
0100: c7 a2 5c 82 4b 9d fb 1f a5 02 03 01 00 01 ....K.........
Validity: [From: Mon Dec 02 21:00:00 GMT 2024,
To: Mon Aug 28 20:59:59 GMT 2034]
Issuer: CN=Zowe Service CA, OU=API Mediation Layer, O=Zowe Sample, L=Prague, ST=Prague, C=CZ
SerialNumber: [ 01]
Certificate Extensions: 5
[1]: ObjectId: 2.16.840.1.113730.1.13 Criticality=false
Extension unknown: DER encoded OCTET string =
0000: 04 32 16 30 47 65 6E 65 72 61 74 65 64 20 62 79 .2.0Generated by
0010: 20 74 68 65 20 53 65 63 75 72 69 74 79 20 53 65 the Security Se
0020: 72 76 65 72 20 66 6F 72 20 7A 2F 4F 53 20 28 52 rver for z/OS (R
0030: 41 43 46 29 ACF)
[2]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: 49 DD D8 7F EA 41 97 84 FC 62 B0 E0 40 45 0D 94 I....�...?..??..
0010: 34 D0 1D F7 4...
]
]
[3]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
DigitalSignature
Non_repudiation
Key_Encipherment
Data_Encipherment
]
[4]: ObjectId: 2.5.29.17 Criticality=false
SubjectAlternativeName [
IPAddress: 10.25.2.118
]
[5]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: A5 E2 AD 55 07 10 83 21 86 45 AE B8 72 21 B9 1C ...?...�.?..Г..
0010: 8F 92 DB AC ....
]
]
]
Algorithm: [SHA256withRSA]
Signature:
0000: 5B 93 E8 F4 5E 3A 21 0F A0 44 7C 8F 8F 68 64 4A [...?“..!...D|?
0010: 91 A2 F3 A0 09 5E B6 A2 89 5C 68 5F 32 28 C3 3D .....?...^фЅ.?
0020: BB F3 D3 7F 2E B7 78 75 C4 FC D0 0D 59 F3 A1 92 ....?.�.....?...
0030: 9B B1 41 BD 64 69 AF ED 3C 5F 8B ED FB E4 5D 27 ..?.A?..i?...._?
0040: F4 DC 64 EB 79 64 C6 3A B4 12 D0 C6 5A 89 E3 0C ..?.d?.y....?...
0050: F6 D3 9E 68 06 77 54 96 B4 10 EB D6 7A CC D4 C2 ...?.?h.....?...
0060: DE 20 EF B1 3E 81 1B 23 E1 C2 66 94 F2 E4 B7 72 .?..?..>..�....?
0070: C0 F2 51 E9 14 7E F6 C0 D3 64 CA 02 DC B4 05 80 ..?......?......
0080: 6C F9 8B BB 9C D9 BC BB 3C CC CE A5 49 61 7B 1E l.......?...??..
0090: 32 84 68 F3 39 4E FA 35 5F 67 D4 A0 94 BA C9 A0 2.?.
ў.NЈ......
00A0: E3 21 EA E3 EF AA 92 34 20 BD 75 A3 A0 0C 41 04 .?.....‹.?... .
00B0: C2 92 A2 AE 1E 6A B4 BF F2 CF 1E E3 E4 98 50 70 .....?........•
00C0: 6D DB 8F 8E EE E5 5B 8B C1 EE 80 86 D5 46 E9 2F m.....?......?.?
00D0: 95 2D 26 62 36 00 6A 5B 97 84 A4 50 9C 6F DA FA .?-&b.
2024-12-06 20:08:40.069 ZWEAGW1:main:50397909 �[35mZWESVUSR�[0;39m �[36mINFO �[0;39m ((o.s.b.w.e.t.TomcatWebServer)) Tomcat started on port 7554 (https)
2024-12-06 20:08:40.183 ZWEAGW1:main:50397909 �[35mZWESVUSR�[0;39m �[36mINFO �[0;39m ((o.s.c.n.e.s.EurekaAutoServiceRegistration)) Updating port to 7554
...
2024-12-06 20:08:50.954 ZWEAGW1:main:50397909 �[35mZWESVUSR�[0;39m �[36mINFO �[0;39m ((o.z.a.g.GatewayServiceApplication)) Started GatewayServiceApplication in 1665.013 seconds (process running for 2120.849)
Tried to run with both values "gateway.apiml.security.auth.provider = saf/zosmf" with same result.
Attched some logs and config file, looking forward for your advice - thanks!
docs_10122024.zip
Beta Was this translation helpful? Give feedback.
All reactions