search

zowe / zlux

The top-level superproject for zLUX. zLUX includes the Zowe Desktop framework in addition to several built-in apps and an example server implementation.
Eclipse Public License 2.0
38 stars 42 forks source link

Issue: Sporadically issue with Zowe editor (An unknown error occured: undefined) #981

Closed lv198 closed 2 weeks ago

lv198 commented 7 months ago

Describe the bug Sporadically after stopping/starting Zowe, I get the following error message in the Zowe editor: "An unknown error occured: undefined" as seen in the screenshot . The issue can only be resolved with restarting Zowe (sometimes several times). In the Zowe log, I get the following message: failed to verify signature with status 53817348 - Signature is not correct

Steps to Reproduce Still not really sure as it only occurs sporadically.

Expected behavior Editor should work as expected.

Screenshots (if needed) grafik

Logs

I can get Logs if needed...

Describe your environment

Additional context

1000TurquoisePogs commented 7 months ago

Please open the developer console of the browser (usually, f12) and check the network tab. Whenever this issue occurs, see if there is a failed network request associated with the failure. This looks like a failure to reach ZSS, for some reason, but the screenshot does not say why.

lv198 commented 7 months ago

Here is a censored screenshot after the issue occured: grafik

lv198 commented 6 months ago

@1000TurquoisePogs is the screenshot helpful? Do you have any idea how to solve the problem?

1000TurquoisePogs commented 6 months ago

Hi yes it is helpful. You are getting HTTP 401 on calls to the ZSS server. That happens when ZSS cannot verify your login session - such as an expired cookie or no cookie in the browser, or maybe some new issue. Try clicking the user icon at the bottom right of the desktop to do a logout, then log back in. Does it change the behavior?

lv198 commented 6 months ago

Hi @1000TurquoisePogs performing a logout and logging in again does not change the behaviour - even deleting all Browser Data (cookies etc.) is not helpful. The only possibility to solve this is restating Zowe and even that does not solve the problem with a probability of 100% - sometimes it takes more than one restart until it works again.

What else can I check?

Sam-Explorer commented 4 months ago

Hi, Did your issue with Zowe editor got fixed? Was it working initially, any thing need to be checked in zowe.yaml for Zowe Editor to work ?

1000TurquoisePogs commented 4 months ago

Hi apologies for the long wait on this one but, are either of you using a high-availability configuration in which there might be more than one copy of ZSS or app-server running at the same time? We had bugs in the past where cookies would not be usable between multiple servers, causing one to be okay with a request, and the other to think of it as unauthenticated. That particular bug is to be fixed in v2.15.0 releasing shortly.

Sam-Explorer commented 4 months ago

Hi, thank you for replying, we are not using high-availability configuration. however when I check the logs I see the below messages

BPXTLS failed: rc=-1, return code=139, reason code=0x0be802af for this I found update in - https://github.com/zowe/docs-site/issues/705 - Was thinking to try

also, I see ZWED0070I - User=undefined (org.zowe.zlux.auth.trivial): Session authenticate successful

MVS-Explorer and USS-Explorer works, its just MVS-Editor which has issue ' An unknown error occurred: undefined '.

In Developer console of the browser, I see Http failure response for https://zowetest.com: 403 OK Refused to apply style from 'https://zowetest.com' because its MIME type ('application/json') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

Any advice on this issue?

Thanks

1000TurquoisePogs commented 4 months ago

Okay that's a very interesting error you get. reason code according to IBM documentation is:

02AF JREnvDirty

The specified function is not supported in an address space where a load was done that is not program controlled.

Action: Make sure that programs being loaded into this address space are defined as program controlled.

And, ZSS, the server that's being used, is a program-controlled server. So, why did it lose program control status? Not sure but, I'm going to open an issue there to research further. https://github.com/zowe/zss/issues/692

1000TurquoisePogs commented 4 months ago

By chance, is the file zowe/components/zss/bin/zssServer NOT program controlled ( https://www.ibm.com/docs/en/zos/2.1.0?topic=authorizations-program-control ) ZSS must be, and as the doc recommends the way to add it would be extattr +p zowe/components/zss/bin/zssServer but, it is distributed in that form so I normally would expect it already has that set.

Sam-Explorer commented 4 months ago

Exactly, we did refer to the below link and checked it seems to be ok https://www.ibm.com/docs/en/zos/2.2.0?topic=installation-establishing-program-control

1000TurquoisePogs commented 4 months ago

Not sure if this is whats happening to you, but I learned that some programs can interfere with the program control state of another running program such as Zowe. Do you see any ICH or BPX messages in the logs / syslog about program control? For example, ICH422I THE ENVIRONMENT CANNOT BECOME UNCONTROLLED.
BPXP014I ENVIRONMENT MUST REMAIN CONTROLLED FOR SERVER (BPX.SERVER) PROCESSING.

Sam-Explorer commented 4 months ago

Hi, thank you very much for helping on the issue and sorry for the delay in reply. After we updated the file owner of Zowe to Zowe ID and recycle the Zowe STC issue got fixed. Now we are able to access the Zowe Editor.

JoeNemo commented 3 months ago

So is this resolved as a config/privilege issue?

@lv198 - is this resolution satisfactory??

JoeNemo commented 3 months ago

@1000TurquoisePogs can you elaborate on the program trying to "uncontrol" zowe?

lv198 commented 3 weeks ago

So is this resolved as a config/privilege issue?

@lv198 - is this resolution satisfactory??

Hello @1000TurquoisePogs

Yes solution is satisfactory, was a privilege problem. Thank you for your help.

rudatp commented 1 week ago

Hi, thank you very much for helping on the issue and sorry for the delay in reply. After we updated the file owner of Zowe to Zowe ID and recycle the Zowe STC issue got fixed. Now we are able to access the Zowe Editor.

What file owner? I'm getting the same issue every time in Editor, both for USS and MVS files

rudatp commented 1 week ago

I just switched the configuration to ATTLS and Editor is working. What could be the reason, that it fails with TLS, but not with ATTLS?