-
Notifications
You must be signed in to change notification settings - Fork 92
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
Debug Service Continues to Fail (Refer to issue #2110) #2114
Comments
Two questions for you:
With JAVA_PTF_GROUP as (
SELECT PTF_GROUP_TARGET_RELEASE OS,
Case PTF_GROUP_TARGET_RELEASE
When 'V7R4M0' Then 'SF99665'
When 'V7R3M0' Then 'SF99725'
When 'V7R2M0' Then 'SF99716'
When 'V7R1M0' Then 'SF99572' End PTF_GROUP
FROM QSYS2.GROUP_PTF_INFO
WHERE PTF_GROUP_DESCRIPTION = 'TECHNOLOGY REFRESH'
AND PTF_GROUP_STATUS = 'INSTALLED'
LIMIT 1)
Select Max(OS) OS,
PTF_GROUP_NAME,
Max(PTF_GROUP_LEVEL) "CURRENT LEVEL"
From QSYS2.GROUP_PTF_INFO
Inner Join JAVA_PTF_GROUP On PTF_GROUP = PTF_GROUP_NAME
Group by PTF_GROUP_NAME;
|
This links seems like it may be useful https://www.ibm.com/support/pages/support-hmacpbesha256-algorithm-app-connect-enterprise. Will investigate this to see if it will assist. |
I looked into this a bit and every time, it boils down to "Java doesn't support this algorithm". I would understand if the keystore was generated by Java, but we use What's the output of these commands for you?
|
Our test system is down for the next 3 days. Will check this out when it is back up. |
IBM i Debug v2.0.1 was just released. Debug v2 uses Java 11 instead of Java 8. This Java 8 specific error is unlikely to happen in Java 11. |
Nice, when the system is back up I will give this a go! Updates to come. |
Noted, I will look into getting the new PTF next week, and will also change the debugger config. Updates to come. |
@sebjulliand to answer your question:
Openssl version: OpenSSL 3.0.10 1 Aug 2023 (Library: OpenSSL 3.0.10 1 Aug 2023) which openssl: /QOpenSys/usr/bin/openssl Our system hardware was upgraded and there has been some issues, so for the time being I am not able to apply the new PTF to allow me to use the new debugger (2.0). Would be nice if I could get version 1.0 working while I wait. |
Maybe the output from Can you check your PATH variable?
I assume that Then re-open a shell session and check that If it still doesn't work, I'll have one more trick up my sleeve (or maybe two...). |
echo $PATH ouput: /usr/bin:.:/QOpenSys/usr/bin And when I check my .bashrc in the following directory /home/myProfileName it has the current contents: Generated by Code for IBM i So it seems like it is already setup how it should be? |
Try this now:
I tried it on my system and it worked (with or without the |
After having a close look, it turns out your Here is another vsix generated from this PR: #2151 It will force the use of Let me know how it goes! |
I'll need to check two thing related to your environment:
Also, while we're at it, from a PASE terminal, run this: /QOpenSys/usr/bin/openssl genrsa -out test_cert.key 2048 && /QOpenSys/usr/bin/openssl req -new -key test_cert.key -out test_cert.csr -subj '/CN=localhost' && /QOpenSys/usr/bin/openssl x509 -req -in test_cert.csr -signkey test_cert.key -out test_cert.crt -days 1095 -sha256 -req && /QOpenSys/usr/bin/openssl pkcs12 -export -out test_keystore.pfx -inkey test_cert.key -in test_cert.crt -password pass:password && rm test_cert.* This will create a test_keystore.pfx file in the current directory on the IFS. Please retrieve it, put it in a zip file and attach it in a reply. Thanks! |
Env Command: (blacked out company/personal info) |
Any updates on this @sebjulliand? |
Also, if you can, attach these files if they exist. Debug service log: Debug service Eclipse instance log: Thanks! |
I will look into upgrading the version you mentioned. I did not see anything for the Debug Service Log but here is the other .log file: .log |
Yeah our team can't really apply any PTFs right now, so upgrading the version won't be possible currently. When we are able to apply PTFs I will get the ones that allow me to use V2 of the debugger. |
Type: Bug
Connect to IBM i system > Start the debug server > Attempt to start the debug service in which the issue occurs at this step. It is affecting my entire team who use this tool, we all receive the same error message as well.
Opened new issue as I did not see any option to re-open the old one. The first suggestion in #2110 was to wipe the certs and generate new ones and that did not fix the problem. The second troubleshooting step had an unrelated error message to mine. Seeing if anyone has any other suggestions.
Extension version: 2.10.1
VS Code version: Code 1.90.0 (89de5a8d4d6205e5b11647eb6a74844ca23d2573, 2024-06-04T19:33:54.889Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: