Replies: 3 comments
-
sincerely those logs don't tell much to me, would be curious to know if the same issue applies when using other deploy methods in order to understand if it's only snap related cc @jmgiaever |
Beta Was this translation helpful? Give feedback.
-
Seems to come from /snap/zwave-js-ui/332/bin/node causing a syscall=426. Some googling via https://gpages.juszkiewicz.com.pl/syscalls-table/syscalls.html For me that's about as comprehensible as chinese, but maybe it rings a bell for you. |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm not seeing these on official Ubuntu versions. Tested on both Server and Core. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Configuration:
(pls don't start a docker<>snap discussion, that's not the point here)
(I adhere to the principle "don't touch it if it works well" so I have not installed the latest version - yet)
Everything works well - no problems at all... although journalctl tells another story.
Every single second there are several journal entries like these, generating 100+MB of logging per day (fortunately it all runs on an SSD, not an SD card...):
ps -ef shows two lines related to "node":
After many hours of research (I'm not a linux expert at all) I finally succeeded in suppressing this flooding of the logging by installing auditd and creating an audit rule to exclude these lines (-a never,exclude -F exe=/snap/zwave-js-ui/332/bin/node), and I also stopped/masked systemd-journald-audit.socket.
But that handles the symptom, not the cause. Anybody got any ideas ?
Beta Was this translation helpful? Give feedback.
All reactions