WebUI: mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented about raspberrymatic

[PlayWithIt]

I now upgraded the kernel to 5.15.0 and this solves the problem.

CCU is now running with the latest docker image and CCU version 3.73.9.20240130 (the version before was 3.73.9.20231130).

[PlayWithIt]

Web-Console error:

Reverting back to image-id 4362ba0e95ba was OK, there I don't have error messages like
(../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
in the containers lighthttpd log file.

[jens-maus]

Please tell more about your host system. Which HW, which CPU, etc.

And also please try to enter the container and try to manually execute tclsh to see if the same error appears. And please state which exact Versionstring this RaspberryMatic version has please check /VERSION

[PlayWithIt]

This is an Intel based mini computer with Intel Celeron CPU J3455, 4 Cores, Linux Mint, Kernel version 5.4.0-171.

I guess this might be a kernel problem / kernel too old:
just from the error message I think "fork/spawn" fails with the error message "function not implemented".

Is there a minimum kernel version requirement?

I'll check the tclsh and version as soon as possible.

[jens-maus]

Thanks for the additional info. This really seems to be related to your hardware and changes that were performed to the docker platform compilation in RaspberryMatic.

In addition to manually trying to call tclsh, please provide details on the specific RaspberryMatic version that actually worked and the one where it started to break. Just stating the docker ID numbers is not enough. I really need the RaspberryMatic docker version numbers and the tags the containers have. In fact to me this sounds like you are using the "snapshot" tag rather than the "latest". Thus, with some nightly snapshot version it started to break. So please tell me the detailed version / commit SHA or RM Version string where it started to break.

[github-actions]

@PlayWithIt, the issue ticket you created does not seem to report a general issue/problem/bug in RaspberryMatic itself, but rather seems to point at a local usage issue that rather requires some support using a discussion or support fora. It will therefore be moved to the discussion area where you can continue for identifying solutions to your issue.