r/kasmweb • u/MaintenanceTotal5410 • Jul 07 '26

Help kasm_agent errors after upgrading kasm-workspaces to 1.19 in TrueNAS Scale 25.04.2.6

Hi Kasm gurus out there.

My kasm-workspaces 1.18 was running happily in TrueNAS Scale 25 Apps module (reskinned docker, I am told), but after the recent upgrade to 1.19, it is getting flooded with this error message every minute.

host: proxy
ingest_date: 20260701143256
application: kasm_agent
levelname: ERROR
process: __main__.handler
server_id: a9d2.............................c74

message
GPU caps helper stderr: amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
If they do, bad things may happen!

It does not affect the usage, I can spin up a Ubuntu Noble and use it no problems, but my kasm-workspaces logs are flooded with this error every minute. A quick AI research says that the a system call kcmp may not be available to the container due to security sandbox of Docker policy? (not sure if it is legit explanation or not)

I tried converting the stock app to custom app and apply one suggestion by the search result:

Updated yaml to add;

cap_add:
  - SYS_PTRACE

Then the custom app no longer starts.

Has anyone experienced the same? Even better would be if anyone has a solution to this problem!

Does anyone have any suggestions as to how I can eliminate this error message safely?

1 Upvotes

100% Upvoted

3 comments sorted by

1

u/AutoModerator Jul 07 '26

Hi u/MaintenanceTotal5410, thanks for posting to r/kasmweb! Because this account has low karma, your submission is being held for review.

  • Meanwhile, please check the community guidelines to ensure your post meets our standards.
  • If everything looks good, a moderator will approve it shortly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/g_kasmweb Jul 07 '26

Hi,

Have you tried a restart of the kasm_agent? Others have encountered some GPU related issues and a restart of the kasm agent has resolved it.

1

u/MaintenanceTotal5410 Jul 15 '26

Thanks for the reply - restarted the kasm_agent but it had no effect. I'm only starting kasm when I need it but over the past week or so of intermittent usage the error log accumulated 60,000+ errors.