-
Notifications
You must be signed in to change notification settings - Fork 98
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
Error starting Debug Service job after 2.0.2 update - "Environment variable DEBUG_SERVICE_KEYSTORE_PASSWORD is not set." #2412
Comments
It's quite possible Code for IBM i needs some additional changes to work with debug-2.0.2. I need to look into this more. |
I guess this is expected behaviour. I suspect that the PTF being installed reset that file back to the default. |
@heymchri You need to regenerate the SSL certificates using Code for IBM i. Code for IBM i saves the certificate settings in the DebugService.env file. These settings are gone after installing an updated debug service PTF. If you rerun the certification generation wizard, Code for IBM i will save the settings to DebugService.env again. Please note that there is no automatic way to regenerate the certificate right now. You can remove the folder "/QIBM/UserData/IBMiDebugService/certs" from the host machine. And Code for IBM i will allow you to generate the certificate again. |
Thanks @sebjulliand. The "Regenerate Service Certificate" could be a newer feature. I am not seeing this action in an older Code for IBM i driver. |
As a workaround, I just save the 4 lines from the DebugService.env file before the PTF apply and then put them back into the replaced DebugService.env file after the PTF apply. Seems to work just fine. |
How odd, it's been here for a few months 🤔 (the related commit is from July). |
Updated Debug extension from 2.0.1 to 2.0.2.
Stopped Debug Service.
Installed prereq server PTF SJ03030 on server (V7R5M0).
Restarted Debug Service.
Error: Environment variable DEBUG_SERVICE_KEYSTORE_PASSWORD is not set.
It looks like the at some point during the update process (not sure whether it's the extension or the server PTF), the DebugService.env is updated, removing the 4 lines at the end:
Is this expected behavior? This would mean that the cert needs to be regenerated which will add these 4 entries back, but that affects all users who have downloaded the client cert before?
Active extensions
Remote system
Enabled features
Shell env
Variants
The text was updated successfully, but these errors were encountered: