Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZWEAM400E Error initializing SSL Context #4038

Closed
2 tasks
jimmschlo89 opened this issue Dec 11, 2023 · 6 comments
Closed
2 tasks

ZWEAM400E Error initializing SSL Context #4038

jimmschlo89 opened this issue Dec 11, 2023 · 6 comments

Comments

@jimmschlo89
Copy link

jimmschlo89 commented Dec 11, 2023

Hello! I have installed a fresh new Zowe version. I'm trying to start it but I'm running into these errors:

image

The errors are accurate, in that those files don't exist, but they should need to. I have an existing Zowe keyring/cert/certauth that was setup for the previous version of Zowe. I used "Option 4" in the zowe.yaml file. So why would Zowe need these files?
Also isn't Zowe supposed to create them upon startup?

This seems to be preventing Zowe from starting and I'm not sure why. Any advice on what to try would be great!

Looking forward to a response! Thank you.

Tasks

Preview Give feedback
@1000TurquoisePogs
Copy link
Member

Hi,
When you want to use keyrings in which you bring your own cert, 2 things could be done

  1. You don't have a keyring, but you do have a cert to CONNECT: edit the zowe yaml for option 4, and then run zwe init certificate, which either creates the keyring & updates the yaml, or in dry-run mode, prints out which JCL you should execute and what to update your yaml with when done. (see https://docs.zowe.org/stable/user-guide/import-certificates#importing-an-existing-jceracfks-certificate)
  2. You already have a keyring: skip all options, and edit the zowe yaml directly, after ensuring the keyring is valid for use with zowe
    see the sort of values you'd specify in the yaml as in the bottom of this example image
    image

by the way, if you do run zwe init certificate, we'd need to see that output for if there were an error that led to your current output.

@jimmschlo89
Copy link
Author

jimmschlo89 commented Dec 13, 2023

Ok I have done that. Seemed to fix the problem. However the server still won't start.

Seems like TomCat can't start properly. I'm also seeing a constant cycle of the Caching Service starting/failing with these errors following the initial startup attempt:

image

image

@jimmschlo89
Copy link
Author

Also is "Server Internal SSL Enabled: false" the default? Does that take additional config for internal SSL comms?

@1000TurquoisePogs 1000TurquoisePogs transferred this issue from zowe/zowe-install-packaging Dec 14, 2023
@1000TurquoisePogs
Copy link
Member

Hi, to understand more about what's going wrong now, someone would need to see the logs.
You can post them here but this is a public place so you may also prefer to email me at [email protected] for discretion

@jimmschlo89
Copy link
Author

Will do. Thank you!

@balhar-jakub balhar-jakub transferred this issue from zowe/community Oct 3, 2024
@JoeNemo JoeNemo closed this as completed Oct 16, 2024
@JoeNemo
Copy link
Contributor

JoeNemo commented Oct 16, 2024

Closed under the believe that this was resolved in another bug report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants