Can't connect to i - database permissions denied

[rjtaylor1]

Has anyone applied CUM 25100750 and been able to connect afterwards? We were not having any issues Friday but over the weekend, had PTFs applied and an IPL. We are at Java 15 and V7R5. VSC is now just coming back with Not connected to server. If I run ssh in a terminal window with db2 "values current_server" I get permission denied. Any and all suggestions appreciated!

[worksofliam]

Weird. So are you able to connect with Code for IBM i? Do you get an error when connecting?

Please share the contents of your Code for IBM i output channel after you see a warning, or after you connect.

[rjtaylor1]

Here is the output from Code for IBM I:
Code for IBM i, version 2.16.3

.: echo "This should be the only text!"
{
"code": 0,
"signal": null,
"stdout": "This should be the only text!",
"stderr": ""
}

.: echo $HOME && cd && test -w $HOME
{
"code": 0,
"signal": null,
"stdout": "/home/RJTAYLO1",
"stderr": ""
}

/home/RJTAYLO1: /usr/bin/uname -rv
{
"code": 0,
"signal": null,
"stdout": "5 7",
"stderr": ""
}

/home/RJTAYLO1: echo "$HOME/.vscode/"
{
"code": 0,
"signal": null,
"stdout": "/home/RJTAYLO1/.vscode/",
"stderr": ""
}

/home/RJTAYLO1: echo "$HOME/.vscode/"
{
"code": 0,
"signal": null,
"stdout": "/home/RJTAYLO1/.vscode/",
"stderr": ""
}

/home/RJTAYLO1: echo "$HOME/.vscode/"
{
"code": 0,
"signal": null,
"stdout": "/home/RJTAYLO1/.vscode/",
"stderr": ""
}

/home/RJTAYLO1: echo "$HOME/.vscode/"
{
"code": 0,
"signal": null,
"stdout": "/home/RJTAYLO1/.vscode/",
"stderr": ""
}

/home/RJTAYLO1: echo "$HOME/.vscode/"
{
"code": 0,
"signal": null,
"stdout": "/home/RJTAYLO1/.vscode/",
"stderr": ""
}

Code for IBM i components:
cqsh (1): Installed
GetNewLibl (1): Installed
GetMemberInfo (3): Installed
CopyToImport (1): Installed
SQLStatementChecker (5): Installed

/home/RJTAYLO1: test -r /etc/vscode/settings.json
{
"code": 1,
"signal": null,
"stdout": "",
"stderr": ""
}

settings config state: {"server":"no_exist"}
/home/RJTAYLO1: LC_ALL=EN_US.UTF-8 /home/RJTAYLO1/.vscode/cqsh_1
liblist
{
"code": 0,
"signal": null,
"stdout": "",
"stderr": ""
}

/home/RJTAYLO1: LC_ALL=EN_US.UTF-8 /home/RJTAYLO1/.vscode/cqsh_1
system "CRTLIB LIB(ILEDITOR) TEXT('Code for i temporary objects. May be cleared.')"
/home/RJTAYLO1: [ -d "/tmp" ]
{
"code": 0,
"signal": null,
"stdout": "",
"stderr": ""
}

{
"code": 0,
"signal": null,
"stdout": "",
"stderr": ""
}

/home/RJTAYLO1: echo $SHELL
{
"code": 0,
"signal": null,
"stdout": "/QOpenSys/pkgs/bin/bash",
"stderr": ""
}

/home/RJTAYLO1: LC_ALL=EN_US.UTF-8 /home/RJTAYLO1/.vscode/cqsh_1 -c "system "call QSYS/QZDFMDB2 PARM('-d' '-i' '-t')""
values current_server
{
"code": 0,
"signal": null,
"stdout": "",
"stderr": ""
}

[worksofliam]

Looks like it could be the issue under 'No results from SQL execution'?

https://codefori.github.io/docs/tips/setup/#no-results-from-sql-execution

[rjtaylor1]

Our admin opened a case with IBM and after commenting out a UsePrivilegeSeparation line in the SSHD config and restarting, we were able to connect. Now, however, the debugger in VSC says we are at 2.0.1 but the i says we are at 3.0. I have completely uninstalled all plug ins, uninstalled VSC, deleted the code folder and reinstalled everything - still 2.0.1. WHY???

[rjtaylor1]

Liam - What exactly do you mean by "reloading the settings"?

[rjtaylor1]

Also - looking through my output, I went and looked at the QIBM/ProdData/IBMiDebugService/package.json - funny enough, it lists "version": "2.0.1"

[sebjulliand]

Liam - What exactly do you mean by "reloading the settings"?

Also - looking through my output, I went and looked at the QIBM/ProdData/IBMiDebugService/package.json - funny enough, it lists "version": "2.0.1"

Do you have other folders starting with IBMiDebugService under /QIBM/ProdData ? If so, what's their version in their package.json file?

[rjtaylor1]

I've done the connect and reload before. We have 2 other folders. One has 2.0.1 and the other has 2.0.0

[rjtaylor1]

Our admin has verified that the 3.0 PTFs are installed

[rjtaylor1]

We ended up uninstalling and re-installing the Debugger 3.0 PTFs and regenerating the key.

[worksofliam]

cc @mkwan01

[mkwan01]

Please check the contents of the following IFS file to see the debug service version number:
/QIBM/ProdData/IBMiDebugService/package.json

If it is version 3.0, it should have the following contents:

{
"version": "3.0.0",
"java": "11"
}

[mkwan01]

Please note that the user need to stop the debug service before applying the PTF update. If the debug service is running, some files may be locked and not updated correctly. This information is included in the PTF cover letter.