Error 'Service Entry Point daemon failed to start. Please check the host workspace log for details.'

[heymchri]

IBM i Debug extension 2.0.2

When adding the first SEP after (re)starting the Debug Service Job, it fails with error message
'Service Entry Point daemon failed to start. Please check the host workspace log for details.'

You can simply click 'Cancel' and on a second attempt the SEP will be added just fine.
Subsequent adding of SEPs works OK.
As soon as the Debug Service job is restarted, the issue reoccurs on the first SEP being set. Subsequent adds work fine.

---

Context	Version
Code for IBM i version	2.14.5
Visual Studio Code version	1.96.0
Operating System	darwin_arm64

Active extensions

.NET Install Tool (vscode-dotnet-runtime): 2.2.3
COBOL (cobol): 24.12.14
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.5.0
Configuration Editing (configuration-editing): 1.0.0
Db2 for IBM i (vscode-db2i): 1.7.0
Dev Containers (remote-containers): 0.394.0
Emmet (emmet): 1.0.0
Error Lens (errorlens): 3.21.0
Excel Viewer (gc-excelviewer): 4.2.62
Git (git): 1.0.0
Git Base (git-base): 1.0.0
GitHub (github): 0.0.1
GitHub Authentication (github-authentication): 0.0.2
IBM i Debug (ibmidebug): 2.0.2
IBM i Project Explorer (vscode-ibmi-projectexplorer): 2.12.0
JSON Language Features (json-language-features): 1.0.0
Jira and Bitbucket (Atlassian Labs) (atlascode): 3.0.15
Merge Conflict (merge-conflict): 1.0.0
Node Debug Auto-attach (debug-auto-launch): 1.0.0
Overtype (overtype): 0.5.0
Prettier - Code formatter (prettier-vscode): 11.0.0
Print (vscode-print): 0.13.3
RPGLE (vscode-rpgle): 0.28.2
Server Ready Action (debug-server-ready): 1.0.0
Source Orbit (vscode-sourceorbit): 1.0.2
TODO Highlight (vscode-todo-highlight): 1.0.5
Task Buttons (vscode-task-buttons): 1.1.3
TypeScript and JavaScript Language Features (typescript-language-features): 1.0.0
YAML (vscode-yaml): 1.15.0
vscode-icons (vscode-icons): 12.10.0

---

Remote system

Setting	Value
IBM i OS	V7R5M0
Tech Refresh	4
CCSID Origin	65535
Runtime CCSID	65535
Default CCSID	37
SSHD CCSID	?
cqsh	true
SQL	Enabled
Source dates	Disabled

Enabled features

/usr/bin	/QOpenSys/pkgs/bin	/QSYS.lib/ILEDITOR.lib	/QSYS.LIB	/QIBM/ProdData/IBMiDebugService/bin	/QOpenSys/QIBM/ProdData/JavaVM/jdk80	/QOpenSys/QIBM/ProdData/JavaVM/jdk11	/QOpenSys/QIBM/ProdData/JavaVM/jdk17
attr	bash	GETNEWLIBL.PGM	QZDFMDB2.PGM	startDebugService.sh	64bit	64bit	64bit
iconv	chsh
setccsid	ls
tar	md5sum
uname	sort
	stat

Shell env

BUILDLIB=QGPL
CURLIB=QGPL
HOME=/home/HEYMCHR
HOST=usalil02.infor.com
LIBLS=QTEMP QGPL
LOGIN=heymchr
LOGNAME=heymchr
MAIL=/var/spool/mail/heymchr
OLDPWD=/home/HEYMCHR
PATH=/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin
PWD=/home/HEYMCHR
SHELL=/QOpenSys/pkgs/bin/bash
SHLVL=1
SSH_CLIENT=10.61.0.155 62793 22
SSH_CONNECTION=10.61.0.155 62793 10.39.117.102 22
TZ=<EST>5<EDT>,M3.2.0,M11.1.0
USER=heymchr
USERNAME=heymchr
WORKDIR=/home/HEYMCHR
_=/QOpenSys/usr/bin/env

Variants

{
  "american": "#@$",
  "local": "#@$"
}

[mkwan01]

@heymchri This looks like a timing issue. Can you attach the debug service log and Eclipse instance log?

Debug service log: /QIBM/UserData/IBMiDebugService/DebugService_log.txt
Eclipse instance log: /QIBM/UserData/IBMiDebugService/startDebugService_workspace/$UserProfile/.metadata/.log

Please replace $$UserProfile by the user profile that starts the debug service.

[mkwan01]

After reviewing the code, I believe it is a timing related issue. Although we start the SEP daemon before setting the first SEP, the SEP daemon startup call is wrapped in a thread object. There is a chance that the SEP daemon startup has not been completed when we set the first SEP. The fix will require an update to the debug service PTF.

[heymchri]

Hi @mkwan01 here are both requested files. I stopped the debug service job, cleared both log files to have fresh logs, then started the debug service job and then added a SEP which resulted in the error message. I then collected the logs.

DebugService_log.txt
.log

[heymchri]

Hi @mkwan01 just a quick follow-up on this. Even if the debug service job has been started a very long time ago, the first time an SEP is set, the issue occurs. So this may not be a timing issue?

[mkwan01]

@heymchri If you can leave your email address, I can send you a test fix based on the timing assumption. You can verify whether the test fix works for you. The test fix is in the form of a new jar file, which replaces one of the existing jar files under /QIBM/ProdData/IBMiDebugService/plugins.

[heymchri]

@mkwan01 here goes: