WebUI: mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented #2649
-
Describe the issue you are experiencingI had a working docker installation (on Linux mint, Intel based, with Image ID 4362ba0e95ba and others before). I upgraded the image to the most recent version (image ID fcd18820f085) using install-docker.sh. The upgrade works, the container starts fine and shows no errors (using "docker logs ccu"). But the WebUI doesn't work:
In the container I can see in /var/log/lighttpd-error.log lots of message like this
I already cleared browser cache, no difference Describe the behavior you expectedWebUI should work as usual. Steps to reproduce the issue
What is the version this bug report is based on?3.73.9.20240130 Which base platform are you running?intelnuc (intel NUC) Which HomeMatic/homematicIP radio module are you using?HmIP-RFUSB Anything in the logs that might be useful for us?Error log of lighthttpd
2024-02-09 17:45:55: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 17:45:55: (../src/gw_backend.c.281) establishing connection failed: socket: tcp:127.0.0.1:8183: Connection refused
2024-02-09 17:45:55: (../src/gw_backend.c.1007) all handlers for /esp/system.htm?sid=@Zwstoa2Xfw@&action=UpdateUI on are down.
2024-02-09 17:45:55: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 17:45:56: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 17:45:56: (../src/gw_backend.c.358) gw-server re-enabled: tcp:127.0.0.1:8183 127.0.0.1 8183
2024-02-09 17:45:59: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 17:46:02: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 17:46:06: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 17:46:09: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 17:46:10: (../src/server.c.1224) [note] graceful shutdown started
2024-02-09 17:46:10: (../src/server.c.1175) [note] pid 1393 continuing to handle 3 connection(s) in progress
2024-02-09 17:46:10: (../src/server.c.1933) server started (lighttpd/1.4.73)
2024-02-09 17:46:10: (../src/server.c.1224) [note] graceful shutdown started
2024-02-09 17:46:12: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 17:46:14: (../src/server.c.2332) server stopped by UID = 0 PID = 1068
2024-02-09 17:46:15: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 17:46:19: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 17:46:23: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
...
2024-02-09 18:05:51: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 18:05:56: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 18:06:02: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 18:06:06: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented
2024-02-09 18:06:12: (../src/mod_cgi.c.1048) fork/spawn /bin/tclsh: Function not implemented In the browser's web-console I can see "http 500 server error": Additional informationNo response |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 6 replies
-
Reverting back to image-id 4362ba0e95ba was OK, there I don't have error messages like |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
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: Is there a minimum kernel version requirement? I'll check the tclsh and version as soon as possible. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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). |
Beta Was this translation helpful? Give feedback.
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).