zowe / community

Zowe Community - Sub-projects, Squads, Contribution Guidelines, Meeting Minutes, and more
53 stars 41 forks source link

USS explorer returns: Fetch children failed for <path> #63

Closed emx0r closed 5 years ago

emx0r commented 5 years ago

Describe the bug Hi,

after recycle of ZOWE server USS explorer no longer works. Whenever I try to open it it gives an error: Fetch children failed for no matter which path I want to load.

All other functions work just fine, including Editor which is able to open USS files.

Logs The only related message in log I was able to spot is: 2019-03-28 08:59:33.749 WARN 16778045 --- [0.0-7554-exec-2] o.s.web.servlet.PageNotFound : No mapping found for HTTP request with URI [/error] in DispatcherServlet with name 'dispatcherServlet' 2019-03-28 08:59:33.964 WARN 16778045 --- [0.0-7554-exec-6] o.s.web.servlet.PageNotFound : No mapping found for HTTP request with URI [/error] in DispatcherServlet with name 'dispatcherServlet' 2019-03-28 08:59:34.077 WARN 16778045 --- [0.0-7554-exec-7] o.s.web.servlet.PageNotFound : No mapping found for HTTP request with URI [/error] in DispatcherServlet with name 'dispatcherServlet' 2019-03-28 08:59:34.197 WARN 16778045 --- [0.0-7554-exec-5] o.s.web.servlet.PageNotFound : No mapping found for HTTP request with URI [/error] in DispatcherServlet with name 'dispatcherServlet'

Details version 1.0.0 #26 RACF, zOS 2.3, JES3

Web Browser Details (if the bug relates to Zowe Desktop usage): Linux, Chromium, Firefox

Joe-Winchester commented 5 years ago

@emx0r tks for reporting the issue. Do the MVS and JES explorers work it's just the USS explorer that is causing problems ? Can you also open the dev console in your browser and look at the network traffic and let us know if there are any red messages (i.e. non 200 return code) and what the request and response are on these.

emx0r commented 5 years ago

thank you for response @Joe-Winchester and pointing me how to debug this problem. MVS and JES explorer works but when I tired to see network in dev console, I found following error

{messages: [{messageType: "ERROR", messageNumber: "AML0105",…}]} messages : [{messageType: "ERROR", messageNumber: "AML0105",…}] 0 : {messageType: "ERROR", messageNumber: "AML0105",…} messageContent : "The certificate of the service accessed by HTTPS using URI '/api/v1/zosmf/restfiles/fs' is not trusted by the API Gateway: com.ibm.jsse2.util.h: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: ↵ java.security.cert.CertPathValidatorException: The certificate issued by CN=IBM INTERNAL INTERMEDIATE CA, O=International Business Machines Corporation, C=US is not trusted; internal cause is: ↵ java.security.cert.CertPathValidatorException: Certificate chaining error" messageKey : "apiml.common.tlsError" messageNumber : "AML0105" messageType : "ERROR"

So I assume I need to fix certificate problem

emx0r commented 5 years ago

@Joe-Winchester do you please know where I can set verifyCertificatesOfServices to false? It would help me to see if I have really a problem with certificate or there's something more

thanks

emx0r commented 5 years ago

I found it in the documentation, thank you