EQAVS1007E self signed certificate debugger IBM i

[buzzia2001]

Hello,
A few weeks ago I set up the debugger for IBM i following the documentation there, and it worked like a charm.
As of today it started giving errors. The first setup involved using a self signed certificate generated directly from VSCode and there it returned me error EQAVS1007E saying the certificate was self signed. At this point I loaded again from code the pfx I use with the certificate for the HTTP part of my IBM i system and I have the same MSGID but the error now talks about a self signed certificate in my chain.
I can tell you that I am using an IBM i system at V7R5M0, version 2.14.5 for Code for IBM i, 2.0.2 for the debugger and on my pc I have macOS 15.3

[mkwan01]

For the self signed certificate message, the most likely cause is that the client side .crt file does not match the host side .crt file.

First, please let us know whether your host side .pfx and .crt files (located under /QIBM/UserData/IBMiDebugService/certs) are generated from Code for IBM i, or you manually copied the .pfx file from another service. If the .pfx file is not generated by Code for i, then you also need to manually generate the .crt file and copy it to the client machine.

If the certificate is generated from Code for i, please compare the content of the host side .crt file (/QIBM/UserData/IBMiDebugService/certs/debug_service.crt) and the client side .crt file. We prepend the host name to the client .crt file. The full path should be available from the debugger tab of IBM i: Connection Settings. The host and client .crt files should have the same content.

[heymchri]

@buzzia2001 @mkwan01 This sounds very familiar - I have been struggling with this for a while - see issue #10. I still cannot consistently reproduce this, but it appears to happen mostly when I'm switching between partitions. What seems to work most of the time is disconnecting from the partition, fully exit VSCode, relaunch, and then reconnect to the partition but use the reload option.

[buzzia2001]

Hello,
even in my case the issue started with adding new systems in the client.
I've tried to stop debug server, generate a new cert and import that certificate on my client, nothing changes.

[sebjulliand]

Hi @buzzia2001 ,
debug service v3 is out, along with an update for iNav to manage it. Check out the documentation, update, and try again: https://codefori.github.io/docs/developing/debug/#required-ptfs

[buzzia2001]

Ciao @sebjulliand!
now on 7.5 partition works fine, on 7.6 it doesn't start because it tells me that there are some java classes missing.
I have all ptfs required:

1.log

startDebugServiceNavigator.log

I've also uploaded all logs
Have a nice Day

[sebjulliand]

@buzzia2001 can you check what this returns?

ls /QIBM/ProdData | grep IBMiDebug

And also this:

ls /QIBM/ProdData/IBMiDebugService/plugins

Also, I don't know how your startDebugServiceNavigator.log was retrieved, but it is unreadable (maybe it was encoded with CCSID 37).

[buzzia2001]

cioa @sebjulliand, here the output:

-bash-5.2$ ls /QIBM/ProdData | grep IBMiDebug
IBMiDebugService
IBMiDebugService.v2.0.1upd.src
IBMiDebugService.v2upd.src
-bash-5.2$ ls /QIBM/ProdData/IBMiDebugService/plugins
com.google.gson_2.8.9.v20220111-1409.jar org.apache.felix.gogo.shell_1.1.4.v20210111-1007.jar org.eclipse.equinox.console_1.4.500.v20211021-1418.jar
com.ibm.debug.daemon.core.jar org.apache.felix.scr_2.1.24.v20200924-1939.jar org.eclipse.equinox.event_1.6.100.v20211021-1418.jar
com.ibm.debug.pdt.core.jar org.eclipse.core.contenttype_3.8.100.v20210910-0640.jar org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar
com.ibm.debug.pdt.daas.application.jar org.eclipse.core.expressions_3.8.100.v20210910-0640.jar org.eclipse.equinox.preferences_3.9.100.v20211021-1418.jar
com.ibm.etools.iseries.daas.application.jar org.eclipse.core.filesystem_1.9.301.v20220725-0748.jar org.eclipse.equinox.registry_3.11.100.v20211021-1418.jar
com.ibm.etools.iseries.debug.core.jar org.eclipse.core.jobs_3.12.100.v20220120-1329.jar org.eclipse.equinox.security_1.3.900.v20220108-1321.jar
com.ibm.etools.iseries.services.ifs.jar org.eclipse.core.net_1.3.1100.v20210424-0724.jar org.eclipse.equinox.simpleconfigurator_1.4.1.v20230216-0904.jar
com.ibm.etools.iseries.services.jar org.eclipse.core.resources_3.16.100.v20220214-1012.jar org.eclipse.jsch.core_1.3.900.v20200422-1935.jar
com.ibm.etools.iseries.services.qsys.jar org.eclipse.core.runtime_3.24.100.v20220211-2001.jar org.eclipse.osgi.compatibility.state_1.2.600.v20220207-1403.jar
com.ibm.etools.iseries.toolbox.jar org.eclipse.core.variables_3.5.100.v20210721-1355.jar org.eclipse.osgi.services_3.10.200.v20210723-0643.jar
com.jcraft.jsch_0.1.55.v20190404-1902.jar org.eclipse.debug.core_3.19.0.v20220125-2302.jar org.eclipse.osgi.util_3.6.100.v20210723-1119.jar
org.apache.felix.gogo.command_1.1.2.v20210111-1007.jar org.eclipse.equinox.app_1.6.100.v20211021-1418.jar org.eclipse.osgi_3.17.201.v20220323-0814.jar
org.apache.felix.gogo.runtime_1.1.4.v20210111-1007.jar org.eclipse.equinox.common_3.16.0.v20220211-2322.jar
-bash-5.2$

log file:
Beginning of data**
file: 001-2103 Error found getting information for file or directory is. No suc
file: 001-2103 Error found getting information for file or directory deprecated
file: 001-2103 Error found getting information for file or directory and. No su
file: 001-2103 Error found getting information for file or directory will. No s
file: 001-2103 Error found getting information for file or directory be. No suc
file: 001-2103 Error found getting information for file or directory removed. N
file: 001-2103 Error found getting information for file or directory in. No suc
file: 001-2103 Error found getting information for file or directory the. No su
file: 001-2103 Error found getting information for file or directory future.. N
java version "17.0.11" 2024-04-16
IBM Semeru Runtime Certified Edition (build 17.0.11+9)
Eclipse OpenJ9 VM (build openj9-0.44.0, JRE 17 OS/400 ppc64-64-Bit Compressed R
OpenJ9 - b0699311c7
OMR - 254af5a04
OMR - 254af5a04
JCL - ffaf9b8a650 based on jdk-17.0.11+9)
An error has occurred. See the log file
/QDBGSRV/.metadata/.log.

[sebjulliand]

I compared with my own plugins folder and we have the exact same content.
Can you put here the content of the /QIBM/ProdData/IBMiDebugService/bin/startDebugService.sh?
Thanks!