This package and a few others from xtables-addons will be available in Turris OS 6.0.2. It requires updating them in the OpenWrt packages repository, otherwise, these packages were not compiled as they did not support Linux kernel 5.15, which we are using, and that’s difference from the OpenWrt.
2 Likes
How to share you my diagnostics ?
I have no way to upgrade. it’s like a bug, and don’ tknow where to share it as they close my issue I’m got too
In reForis: Administration → Diagnostics. More information on contacting Turris Support can be found here.
Actually, as a developer of lighttpd (a portmanteau of “light” and “httpd”), I can tell you that it is intentional that is an error. When changing the lighttpd configuration, it is strongly recommended to test the config using lighttpd -f /etc/lighttpd/lighttpd.conf -tt. If there is an error, fix the problem before continuing (before restarting lighttpd or before rebooting). If someone else with admin privileges – e.g. the automated package updater – makes config changes, it too should test the config and should rollback the changes if there is an error, and alert an admin for intervention. The lighttpd config changes made by the Turris Team in Turris OS 6 (treewide: use number prefixes for lighttpd configuration files (!913) · Merge requests · Turris / Turris OS / Turris OS packages · GitLab) unfortunately did not play nicely with /bandwidthd/ or rrdtool or possibly other custom configs. Breaking a working config is an error, and lighttpd flagged it as such.
Lesson learned: as @miska noted in Turris OS 6.0 aftermath - Community office - Turris forum the Turris Team renaming and reconfiguration of lighttpd include files could have been rolled out seperately and earlier than Turris OS 6.
OK, but a message that explicitly says that it’s fatal and not a crash would be nice.
@fantomas. I am not sure you are distinguishing between a crash and a non-zero exit value following the error message: Configuration of plugins failed. Going down. lighttpd did the latter; lighttpd did not crash. Are you suggesting that I change the phrase “failed. Going down.” to “fatal error”? I think you are splitting hairs here. In any case, this is off-topic. If you’d like to suggest different phrasing, please join the lighttpd forums
This topic was automatically closed after 18 days. New replies are no longer allowed.