Joachim Bauch
Joachim Bauch
> My previous update was 2 months ago, and the old bin still starts up if I use that instead of the newly compiled one, which make me think there...
Do you have SELinux or something similar enabled? The "kernel: audit ..." log entries seem to indicate that something was blocked and the signaling server was killed because of that....
Another guess: the syscall from the audit log is 160 (`syscall=160`), which according to https://filippo.io/linux-syscall-table/ is `setrlimit`. The service seems to run with uid/gid 997/997 which might not be allowed...
This looks like a potential cause for the `setrlimit` call during startup with newer builds: https://github.com/golang/go/issues/46279 Could you please provide your `.service` file? Maybe you need to apply the changes...
@hanserasmus did you get a chance to look at your `.service` file yet?
Perfect, thanks for confirming. So this is fixed already in the repository then. No worries about the response delay, I'm not quick in answering in some cases, too :-)
Please check if the solution from #180 (run `make clean` before building) resolves the issue for you.
Sorry for the late response. This indeed looks incomplete: > Aug 09 11:39:51 amd signaling[905]: capabilities.go:192: Incomplete OCS response {"ocs":{"meta":{"status":"ok","statuscode":200,"message":"OK"},"data":{"version":{"major":27,"minor":0,"micro":1,"string":"27.> Or was this clipped while copying the output to the...
If this is still happening with the latest version, please reopen the issue and provide the full logs.