Zowe Editor An unknown error occured: undefined

[rorrss]

Describe the bug Zowe Editor Is not working correctly

Steps to Reproduce

1.When opening editor in zowe

2. reciving message :An unknown error occured: undefined

Expected behavior Editor should work correctly without issue

Screenshots

Logs

Details In zweslstc reciving abend issue 0C4-11

Web Browser Details (if the bug relates to Zowe Desktop usage): All browsers

Additional context Hello. I would like to ask you if anyone faced this issue before. I compared settings from other customers where installation of mine went fine and last installation have this issue. Please let me know. Thank you

[1000TurquoisePogs]

This may be an issue already fixed, not sure. I've certainly seen that error before but it could have different causes. What version of Zowe are you on? What datasets are you trying to look at when you get the OC4-11?

In your browser, if you hit f12, you can get the developer tools console. In the network tab, you can see which requests were issues. There's probably an error 500 associated with the failed request, and if you can find which one, it may help us know which request failed. For example, is it a very large PDS? Or a dataset with unusual symbols?

[rorrss]

@1000TurquoisePogs Hello It actually does not matter what im trying to open by Editor.

It shows same issue all the time. As you can see USS has same issue.

I am using zowe 2.14.0, but had this issue in 2.13 too

here is a network log:

Thank you for checking

[JoeNemo]

There is most likely a logrec entry for the captured OC4-04 in the zss server address-space. If this yields no info we may need a SLIP trap on OC4 for the zss address space.

I assume the ZSS server successfully handled a user authentication request, so it probably got some internal error after that. Is the whole server log available?

Also, was an SVCDUMP taken for this failure?

[JoeNemo]

Maybe someday Zowe can have a config option for not pushing a recovery context in httpserver.c when handling a service request and let errors generate dumps and halt the server (just for debugging purposes).

[rorrss]

Hello. very sorry for a delay. I had vacation last week.

So here is what i did: I made Sliptrap for 0c4

slip set,id=ROM1,j=ZWESLSTC,c=0c4,a=svcd,end

this was not working, becouse when error occurs STC still running.

I made logrec report if is it helpful to you:

LOGREC.txt LOGREC.log

Issue still remain the same. Please let me know if you need anything else

Thank you very much

[ifakhrutdinov]

this was not working, becouse when error occurs STC still running.

An SVC dump can be taken when the STC is running. In the SYSLOG, do you see any corresponding messages about the reasons a dump was not taken?

[rorrss]

Hello Guys, an SVC Dump has been taken The limit for uploading a file here is 25MB. SVC DUMP is 375MB. Where do you want to upload it?

[JoeNemo]

Can you upload it to GitHub? If there are security questions, let's discuss?

[rorrss]

Hello Guys. This issue has been fixed.

For an information it was an issue in hour Language Enviroment.

gsk_def_malloc SSL could not allocate memory

We changed Parameters in CEEPRM member from NOSIMVRD STACK(128K,128K,BELOW,KEEP,4K,4096), to STACK(128K,128K,BELOW,KEEP,512K,128K)

And after zowe restart it start to run. Thank you very much for your attention.

[1000TurquoisePogs]

Oh, okay thank you, we should document or enforce this!