Trouble getting Debugging Setup

[thomprl]

I'm having trouble getting debugging setup from Code For i. I go through the walkthrough. I have the debug extension installed, I made sure the PTF's are installed. I go to the Setup Certificates and click Generate Certificates. I get a pop-up

I click continue.

A few seconds later I get this message.

I look in this folder /QIBM/ProdData/IBMiDebugService/bin/cert and it does not exist.

[sebjulliand]

Hi @thomprl ,
the debug service configuration management is going to be improved in the next release. You can check out what's coming here: #1990

With the element you gave here, I can only assume the certificates were generated by someone else than you, who used a different host name to connect to this system (i.e. the letters case was different). Since the password is based on this information, what was generated would not work for you.
The Debug Service Certificate is also supposed to be generated under /QIBM/UserData/IBMiDebugService/certs.

Long story short: if you can wait for the next release to re-configure the debug service, that would be great. Otherwise, you can at least delete any existing certificate under /QIBM/UserData/IBMiDebugService/certs, then switch to Code for IBM i pre-release version (as it contains some enhancement for the debug service already). From here, you can access the IBM i debugger view that can guide you through the certificate generation:

[thomprl]

Ok, I was just trying it out. Might want to update the walkthrough as it has a different folder for the certs than the one you listed. The walkthrough has /QIBM/ProdData/IBMiDebugService/bin/certs.

[sebjulliand]

This walkthrough is going away very soon, in favor of the IBM i debugger view 😅

[petterjohansson]

@sebjulliand . I have used the debug walktrough to start debug server, but that was as you mentioned removed in favor of the IBM i debugger view. When I try to start the debug server in this view:


it fails.

I currently start it manually through a ssh terminal when I need to debug:

Any suggestions?

[sebjulliand]

At least the configuration process did its job since you can start the service using the shell script as it is (even though I'd rather start it using SBMJOB as described here: https://codefori.github.io/docs/developing/debug/#starting-the-debug-service-outside-of-code-for-ibm-i).

Can you share you Code for IBM i output after you try to start the service from VSCode? Let's see if there is something relevant in there.