We are proud to inform you that we released a new version of Turris OS into the stable branch, so the update will be downloaded and applied automatically unless you are using delayed updates or approvals.
Turris OS 6.0.3 release notes:
New Features
• Added SFP and OpenVPN modules for diagnostics
Updates
• rainbow updated to version 0.1.3
• syncthing updated to version 1.19.2
• golang updated to version 1.18.8
• Linux kernel updated to 5.15.78 and 5.10.154
Other Changes
• Switch to performance governor by default
If you find any bugs in this release, please let us know through official channels.
Oi, very interesting, the MOX classic here had to be rebooted, and it is breathing after it ! No need to pull the plug!
Is this a kernel ( it says 5.15.78 ) thingie, or am i lust lucky
Thxs!
Probably yes and no. The kernel config will apply to both Omnia and MOX. However, on Omnia, I don’t see cpufreq being used, so it probably will not have any effect.
I have a problem with Nextcloud after installation new OS release. It doesn’t seem to work, or it has such a slow response that it won’t load. Floccus keeps trying to sync, the windows app gives up because of the response. If I reboot the router, nextcloud loads, although the slow response is still noticeable. It only lasts a moment, and then it’s unavailable again. Any idea how to check?
Otherwise, update ok, no unwanted network/wifi interruption (except the approved reboot): Turris Omnia 2017, 1 GB RAM, dead eMMC, system running from mSATA SSD, original wifi cards. Storage plugin enabled, LXC containers, tor relay, USB HDD shared over samba4 and minidlna, SQM, Hardwario gateway + MQTT IoT bridge, OpenVPN, PPtP VPN, Dynamic firewall, minipots, HaaS, Pakon.
Turis 1.1
still has broken LEDs.
After boot all leds blinks green, then blue and stay blue for ever. Nov activity blinking, nothing. Just full brightness blue on all leds.
rainbow commands are stil failing
$ rainbow led1 enable blue
reader_loop: bad jump: 8388608
Aborting...
Turris Omnia
rainbow command still throws errors, but at least it actually do change LEDs
$ rainbow led1 enable blue
Command failed: Not found
Command failed: Not found
OK, I take it back. This is a windows client issue. For some reason, it overwhelms the server when it syncs and it goes silent. Apparently after I added a network drive as external storage, which I didn’t even expect to sync automatically. I’ve added an exception to the rules, so we’ll see.
The update was strange.
I now relized that Reforris updated from 5.4.4 to 6.03
After the update my router took quit long until I got network. The first working network was my W-Lan. The wired connection need some minutes more. The longest time needed the Guest W-Lan.
Now Internet works but the Webserver for reforis and Luci seems down. A reboot does not help.
Did you check /var/log/lighttpd/error.log In there you might find the reason. In my case it was a config file in /etc/lighttpd/conf.d/ lacking the number prefix a simple renaming of the file solved the problem. This change for lighttpd was mentioned in TOS 6.0 release notes. In another case (Webapps icons missing) there was no error to be found in the error.log but there were double config files with different number prefixes found in /etc/lighttpd/conf.d/ which caused the problem.
...
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 3: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 4: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 5: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 6: from: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 7: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 8: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 9: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 10: from: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 13: syntax error: unexpected "("
Nov 18 15:34:31 turris dnsmasq[5923]: script process exited with status 2
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 3: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 4: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 5: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 6: from: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 7: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 8: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 9: import: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 10: from: not found
Nov 18 15:34:31 turris dnsmasq-script[5923]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 13: syntax error: unexpected "("
Nov 18 15:34:31 turris dnsmasq[5923]: script process exited with status 2
...
It seems to me lighttpd is not even started. As I remember from last days /var/log/lighttpd/error.log collects errors if lighttpd fails to start and while running AND it produces as first entry at start or at least trying to start it creates the file var/log/lighttpd/error.log
2022-11-16 15:32:23: (../src/server.c.1588) server started (lighttpd/1.4.67)
or similar.
So there should be any entry in var/log/lighttpd/error.log
Entering /etc/init.d/lighttpd status in shell should show you whether it is running or not. In case not /etc/init.d/lighttpd start should start it and eventually produce error information AND /etc/init.d/lighttpd enable takes care lighttpd will be started after each reboot.
After rolling back - every thing works now - I checked updates with opkg update. There I get one Error: *** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/sidn/Packages.gz