I’ve now upgraded RockyLinux to v8.7 and installed the latest VSCode update (v1.75.0, just released today) and continue to see the same issue.
When this issue occurs, ALL connectivity is lost for a period ranging from a few minutes to much longer. The system sometimes restores itself and sometimes needs a manual restart.
Here is the RockyLinux status of the affected system:
# cat /etc/os-release
VERSION="8.7 (Green Obsidian)"
ID_LIKE="rhel centos fedora"
PRETTY_NAME="Rocky Linux 8.7 (Green Obsidian)"
Here is the version info for VSCode:
Version: 1.75.0 (system setup)
OS: Windows_NT x64 10.0.18363
I found RHBA-2020:4569 - Bug Fix Advisory that appears to be relevant. I don’t have access to the redhat portal, and I don’t know enough RL to know if or how this relates to RL v8.7.
I just now had a hang from around 23:00 UTC to 23:04 UTC.
Here is the relevant excerpt from
Feb 3 23:00:01 byron systemd: Started system activity accounting tool.
Feb 3 23:02:46 byron sssd: Child  ('nss':'nss') was terminated by own WATCHDOG. Consult corresponding logs to figure out the reason.
Feb 3 23:02:47 byron systemd: session-55.scope: Succeeded.
Feb 3 23:02:47 byron systemd-logind: Session 55 logged out. Waiting for processes to exit.
Feb 3 23:02:47 byron systemd-logind: Removed session 55.
Feb 3 23:02:47 byron sssd_nss: Starting up
Feb 3 23:02:48 byron systemd: Started Process Core Dump (PID 22647/UID 0).
Feb 3 23:02:48 byron systemd-coredump: Resource limits disable core dumping for process 22068 (node).
Feb 3 23:02:48 byron systemd-coredump: Process 22068 (node) of user 1001 dumped core.
Feb 3 23:02:48 byron systemd: firstname.lastname@example.org: Succeeded.
Feb 3 23:04:35 byron systemd: Started Session 61 of user root.
Feb 3 23:04:35 byron systemd-logind: New session 61 of user root.
I lost connectivity at 23:00. It appears to me that the “WATCHDOG” shut down sssd_nss after several failed heartbeats – I think that’s what the second entry (Feb 3 23:02:46) is telling us.
The successful signin (“Session 61”) of user “root” exactly corresponds to when my SSH client was able to reconnect.
Can someone confirm that the bug fixes and updates mentioned in the above redhat advisory are in RL v8.7?
I made one attempt to copy
/etc/default/sysconfig/sssd.con – the place where an earlier log said that
sssd was looking for the file. I made the change suggested upthread. With that change in place,
systemctl was unable to successfully launch
I did see a complaint in a VSCode log earlier this week – just once – with the following:
2023-02-02 17:40:22.918 [error] Error: spawn ENOMEM
at ChildProcess.spawn (node:internal/child_process:413:11)
at Object.spawn (node:child_process:700:9)
at t.Git.spawn (/home/tms/.vscode-server/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/extensions/git/dist/main.js:2:2017628)
at t.Git.stream (/home/tms/.vscode-server/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/extensions/git/dist/main.js:2:2016385)
at P.stream (/home/tms/.vscode-server/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/extensions/git/dist/main.js:2:2020758)
at P.getStatus (/home/tms/.vscode-server/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/extensions/git/dist/main.js:2:2034051)
at j.db (/home/tms/.vscode-server/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/extensions/git/dist/main.js:2:2101461)
at j.bb (/home/tms/.vscode-server/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/extensions/git/dist/main.js:2:2100726)
at async j.ab (/home/tms/.vscode-server/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/extensions/git/dist/main.js:2:2100238)
at async j.W (/home/tms/.vscode-server/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/extensions/git/dist/main.js:2:2099522)
at async j.status (/home/tms/.vscode-server/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/extensions/git/dist/main.js:2:208574
This complaint suggests that
vscode-server (the nodejs process that runs VSCode on the remote machine) used all the memory on the server.
I’ve had multiple hangs per day (at least a dozen), and this is the only log entry contains “ENOMEM”.
That timestamp (
2023-02-02 17:40:22) corresponded to a hang I experienced yesterday.
I’m seeing this multiple times a day, it’s a real hassle.
I invite the guidance of this community about how best to proceed.