Locally built API ML instance does not work on Ubuntu + error ZWEAM100E at Discovery component startup #3920
Replies: 4 comments
-
Juat looking at the start scripts, when you are trying to disable the certificates, I would recommend to also remove the https profile for the discovery service as this is possibly what is a source of the failure --spring.profiles.active=https |
Beta Was this translation helpful? Give feedback.
-
Hi Jakub, Tried your suggestion with no success. I see no significant difference in log messages, components statuses in Web UI remained the same. |
Beta Was this translation helpful? Give feedback.
-
Hi Pavel, thanks for sharing, I am reaching out to internal team to help with the issue, but given the current time of year we won't get to it sooner than next week. |
Beta Was this translation helpful? Give feedback.
-
Hi Pavel, we have found arbitrary issues when building the project with recent gradle versions, could you please try to run clean build with gradle version 8.4? What is your JDK version? |
Beta Was this translation helpful? Give feedback.
-
Hello team,
I performed API ML V3 build on local Ubuntu x64 server according to the instructions from https://github.com/zowe/api-layer/tree/v3.x.x. Some test(s) failed during build process so I excluded them by adding "-x test" option then build became successful.
I turned off everything related to ssl, set apiml.security.auth.provider=dummy and run it using script including gateway/catalog/discovery components only.
The only explicit error message I got was :
[AD] 2024-11-29 11:17:45.863 <ZWEADS1:main: > root ERROR ((o.z.a.p.v.BuildInfo)) ZWEAM100E Could not read properties from: 'META-INF/git.properties'
Message explanation says it may indicate problem during build - "The jar file is not packaged correctly. Please submit an issue."
Though I am not sure whether it is really harmful regarding the fact it does not break discovery startup.
In the console I see ZWEAM000I messages indicating catalog and discovery startup completed successfully but does not see the same message for gateway.
Finally web interface is available but says no one component is active
Here is the complete execution log
APIML_log_29112024.zip
Please, advise what are the possible reasons of components unavailability and what should I do to resolve this issue.
Many thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions