Turris 1.1 under contract - repeating error message
root@turris1:~# cat /var/log/messages | grep 'err foris'
2017-12-21T13:15:31+01:00 err foris-controller[]: Failed to parse content of '/usr/share/server-uplink/contract_valid'.
2017-12-21T13:15:36+01:00 err foris-controller[6018]: Last message 'Failed to parse cont' repeated 20 times, suppressed by syslog-ng on turris1
2017-12-21T13:15:38+01:00 err foris-controller[]: Failed to parse content of '/usr/share/server-uplink/contract_valid'.
2017-12-21T13:15:39+01:00 err foris-controller[6018]: Last message 'Failed to parse cont' repeated 8 times, suppressed by syslog-ng on turris1
2017-12-21T13:15:39+01:00 err foris-controller[]: Failed to parse content of '/usr/share/server-uplink/contract_valid'.
2017-12-21T13:15:44+01:00 err foris-controller[6018]: Last message 'Failed to parse cont' repeated 8 times, suppressed by syslog-ng on turris1
OK, I donāt know if this has been asked before, butā¦ When are you guys going to stop messing around with user configuration? /etc/config/* should be sacred, and every single time thereās an update the dhcp configuration is changed and the resolver script reenabled. I personally only use dnsmasq (no unbound or knot) and Iām really getting annoyed at this whole deal. Really, no excuses, just stop it.
I cannot create LXC container from Luci too, even with 3.9.1. lxc-create -t download -n test works for Debian but not for ArchLinux (tar: Ignoring unknown extended header keyword 'SCHILY.fflags' error).
Unfortunately these topics are duplicate and honestly I donāt know why the creator create another same thread, but ok and Iām going to close one of it or merge it.
Letās take it one by one
Installing containers via LuCI doesnāt work. We know it and working on it and I already confirmed in some thread.
Workaround: Use SSH. In past we thought that api should work, but please donāt use it and stay with repo.
What was fixed?
Starting/stopping/restarting containers via LuCI.
It is mentioned in the kernel news, so the second issue Not the LuCI one. SHILY.flags should be harmless, but Iāll check whether Archlinux didnāt changed something in their tarballs.
EDIT: Yep, regardless of SHILY.flags warnings container is installed fine.
root@turris:~# updater.sh
WARN:Script file:///usr/share/updater/localrepo/localrepo.lua not found, but ignoring its absence as requested
WARN:Requested package luci-i18n-ddns-en that is missing, ignoring as requested.
WARN:Requested package foris-netmetr-plugin-l10n-cs that is missing, ignoring as requested.
WARN:Requested package foris-netmetr-plugin-l10n-de that is missing, ignoring as requested.
WARN:Requested package https-cert that is missing, ignoring as requested.
INFO:Queue install of updater-ng/turris/60.0.5-2
Press return to continue, CTRL+C to abort
Hi thereā¦ can someone explain me how the new Haas honeywagon works? I see my unit there, but no data. And it is sending dataā¦should i remove the p22 FW rule that used to work?
Ok, thanks @miska and @Pepe for the info. Of course I could check the kernel news but I didnāt know where to find it. I would consider to put a link to a commit/release in those announcements (if there is more info for those who want to know more details).
@miska I re-tested ArchLinux container and you are right, it works despite warnings. I can also confirm that Start/Stop/Reboot works correctly now with containers.
My Turris Omnia successfully upgraded to 3.9.1. All services seem to be fine, except I still cannot login to Foris. I get a ā500 - Internal Server Errorā when trying to connect to the router. The Foris interface entered this state since the 3.8 update, and worked fine before that. The LuCI entry works, though. Any ideas how to solve Foris are appreciated.
Thanks, tried that, did not help. I also tried from different systems (Windows10, Mac High Sierra) and different browsers (Firefox 57.0.2 64-bit, Chrome 63.0 64-bit). This makes me believe that it is an issue on the Turris Omnia side and not on the browser side.
Not the LuCI one. 
Being more verbose is in todo.