Turris OS 3.10.8 released!

release

#1

Dear Turris users,

we have just pushed 3.10.8. It contains kernel update where we dropped a patch that could cause a panic in some circumstances. Apart from that just few minor updates. One of them is Nextcloud, but we are still sticking to 13 branch. Nextcloud 14 will be part of 3.11 release as it needs some tuning.

Full release notes are as follows:

  • kernel, nextcloud, btrfs-progs, php: update
  • kernel: drop blkio LED trigger as it was causing some issues from time to time
  • pakon: more robust database maintenance

In general, we don’t expect any issues, but if you encounter any regressions, let us know.


#2

#3

After the update reboot ran schnapps rollback 8 and got

Segmentation fault

Rebooted once more and ran the same command with no error but again the rollback snapshot has no description when schnapps list

Another rollback and reboot later the rollback description is showing, weird.


#4

after the update nextcloud is showing a warning about some issues with code integrity in the ui


#5

3.10.8 tag is missing in github repository.

Here openvpn (turris as openvpn server) stopped passing traffic correctly to LAN after update and reboot. No idea what could cause that because according to changelog nothing related to openvpn has changed.


#6

After the update WiFi LEDs were out and radio0 (5 GHz) was missing in Foris; in Luci it was present as enabled but didn’t broadcast. After reboot WiFi LEDs are on, both radios are present and enabled in Foris and LuCi, but radio1 (2.4 GHz) isn’t broadcasting (Bitrate: ? Mbit/s). Another reboot didn’t improve this situation. I didn’t make any changes in WiFi configuration before enabling 3.10.8 update (nor in anything else). What am I supposed to do?

Update: about one hour later I saw both radios working :wink:


#7

WiFi Guest networks stopped working. More information will come later today, once I get back to my router.


#8

I have my /var/log/messages spammed by these log records.

2018-10-16 16:45:01 info /usr/sbin/cron[6701]: (root) CMD (   /usr/bin/notifier)
2018-10-16 16:45:01 info /usr/sbin/cron[6700]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2018-10-16 16:45:18 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:45:24 warning dnsmasq-dhcp[2543]: Last message 'no address range ava' repeated 1 times, suppressed by syslog-ng on turris
2018-10-16 16:45:24 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:45:31 warning dnsmasq-dhcp[2543]: Last message 'no address range ava' repeated 1 times, suppressed by syslog-ng on turris
2018-10-16 16:45:47 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:45:53 warning dnsmasq-dhcp[2543]: Last message 'no address range ava' repeated 1 times, suppressed by syslog-ng on turris
2018-10-16 16:45:53 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:46:01 warning dnsmasq-dhcp[2543]: Last message 'no address range ava' repeated 1 times, suppressed by syslog-ng on turris
2018-10-16 16:46:01 info /usr/sbin/cron[6778]: (root) CMD (nethist_stats.lua)
2018-10-16 16:46:01 info /usr/sbin/cron[6777]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2018-10-16 16:46:17 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:46:23 warning dnsmasq-dhcp[2543]: Last message 'no address range ava' repeated 1 times, suppressed by syslog-ng on turris
2018-10-16 16:46:23 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:46:31 warning dnsmasq-dhcp[2543]: Last message 'no address range ava' repeated 1 times, suppressed by syslog-ng on turris
2018-10-16 16:46:46 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:46:52 warning dnsmasq-dhcp[2543]: Last message 'no address range ava' repeated 1 times, suppressed by syslog-ng on turris
2018-10-16 16:46:52 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:47:01 warning dnsmasq-dhcp[2543]: Last message 'no address range ava' repeated 1 times, suppressed by syslog-ng on turris
2018-10-16 16:47:01 info /usr/sbin/cron[6830]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2018-10-16 16:47:15 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:47:21 warning dnsmasq-dhcp[2543]: Last message 'no address range ava' repeated 1 times, suppressed by syslog-ng on turris
2018-10-16 16:47:21 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:47:31 warning dnsmasq-dhcp[2543]: Last message 'no address range ava' repeated 1 times, suppressed by syslog-ng on turris
2018-10-16 16:47:44 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:47:50 warning dnsmasq-dhcp[2543]: Last message 'no address range ava' repeated 1 times, suppressed by syslog-ng on turris
2018-10-16 16:47:50 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris
2018-10-16 16:47:57 warning dnsmasq-dhcp[2897]: no address range available for DHCP request via br-guest_turris

#9

So I have restarted my omnia and my problem has gone.

  • /var/log/messages is clean
  • WiFi is working again

It seems my problem was somehow connected to automatic restart scheduled by updater.


#10

Did you restart your router again?
My own configuration works directly without problems (as like my own guest network does).


#11

Dobry den,
Mám Turris v. 1 a po posledním updatu nejde Lighttpd a tudíž ani Luci.
Když spustím Lighttpd, tak se příkaz provede. V běžících procesech ho vidím, co je zajímavé že log je naprosto prázdný.


#12

3.10.8 tag is missing in github repository.

We pushed a new tag one hour ago. :slight_smile:


#13

Nextcloud now shows a notification that the webserver is not set to resolve /.well-known/caldav and /.well-known/carddav. According to docs it could cause problems to some clients which can’t find proper sync address. Although I am not using CalDAV or CardDAV clients I would like to know a resolution. I couldn’t find out how to set proper redirection in lighttpd config. Anybody experiencing the same issue?


#14

I just got notification of update from my Omnia at the top of which was:

##### Error notifications #####
Updater selhal: Failed operations:

pakon/postinst: Command failed: Not found

What’s that about?


#15

Exactly. The automatic restart just put the router in some inconsistent state. Once I restarted the router manually, problem has gone.


#16

Naprosto stejný problém pozoruji už od verze 3.10.6. Lighttpd neběží vůbec, log prázdný. Restart lighttpd nevypisuje žádnou chybu a v procesech není vidět.


#17

I have a problem with the resolution of the repos after updating

I’ll see if a reboot again fixes it

root@turris:~# pkgupdate
WARN:Couldn’t read the status file: [string “backend”]:1173: [string “backend”]:1164: Failed to lock the lock file //var/lock/opkg.lock: Resource temporarily unavailable
line not found
line not found
line not found
ERROR:
unreachable: https://repo.turris.cz/omnia/lists/base.lua: Couldn’t resolve host ‘repo.turris.cz’
line not found
line not found
line not found
ERROR:
unreachable: https://repo.turris.cz/omnia/lists/base.lua: Couldn’t resolve host ‘repo.turris.cz’
root@turris:~# pkgupdate
line not found
line not found
line not found
ERROR:
unreachable: https://repo.turris.cz/omnia/lists/base.lua: Couldn’t resolve host ‘repo.turris.cz’


#18

Nextcloud is missing 2 files in this update
.user.ini and .htaaccess and complains about Code integrity check failed in a same way as dscribed here:

My assumption is that 2 hidden files were forgotten and not inclded in the update:

Technical information

=====================
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results

  • core
    • INVALID_HASH
      • .htaccess
    • FILE_MISSING
      • .user.ini

Raw output

Array
(
[core] => Array
(
[INVALID_HASH] => Array
(
[.htaccess] => Array
(
[expected] => 60cb065543a840e650166fdb80dae8315e8d62f843947b34e080fbeb5d61780f78d1a875d0320876f6ae5ca607e192d24972a6017bcaa530dd487c7f3cf81f9c
[current] => cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e
)

            )

        [FILE_MISSING] => Array
            (
                [.user.ini] => Array
                    (
                        [expected] => 467d4f028c447895716a2b7859ed6e569f8ee34b87b51d73dab2e6a9ca4fbe63172c7be3e365ae864a60408286afcce852dd38ee544b61685ed4ee5e021fecb0
                        [current] => 
                    )

            )

    )

)


#19

Seems to be comp-lzo handling (which btw is obsolete and turris configurator should switch to using “compress” configuration option).


#20