Turris OS 5.3.7 released

Community office
, , , ,
1

Dear Turris users,

We are pleased to inform you that Turris OS 5.3.7 has been released from the testing branch.

Notable changes include improvements of Turris Sentinel and fixes of multiple security vulnerabilities and various bugs. Several packages were updated as well.

5.3.7 release changelog:

  • Updated kernel to version 4.14.274
  • Sentinel improvements
  • Updated syslog-ng
  • Fixed switch-branch and listing versions
  • Security fixes

The update will be applied automatically unless you opted for update approvals or disabled automatic updates entirely (check your reForis Update Settings or Updates section in the latter cases).

If you come across any problems regarding this release don’t hesitate to contact us to get help.

4 Likes
2

Turris MOX, reboot still not working, power disconnected, twice because the wifi was not working.
Now hopefully working.

3

MOX: reboot unfortunately stil not working (applied v4 patch)

2 Likes
4

TO-2020, Smooth upgrade, no issues so far.

1 Like
5

TO 2016 all fine, Mox classic needed power plug hand patch to breath again.

1 Like
6

The error is repeated (possible to replicate) even in version 5.3.7 after uninstalling Statistics -

image
image786×267 18.3 KB

9

Turris Mox Board: hang after reboot again.
I just can’t rely on automatic rebooting. It reboots and then the router became unresponsive. LED keeps faintly constantly shining and the web interface is not reachable. I have to cut the power. Then it boots normally with updates installed.

1 Like
11

I was looking over your post from before. I have a few suggestions that might help.

  1. Go back through and uninstall the packages.

  2. I would recommend removing the luci_statistics and collectd (if it exists) config files in /etc/config. Move them somewhere so you can go through them later to replicate your environment if you want.

  3. If you have no errors in the interface, then you would want to reinstall the packages.

  4. If that looks OK (no errors in the interface), then start to reconfigure things.

I’ve found that some of the collect-mod-* packages are kind of flakey and have caused issues form me in the past. I would install those one at a time, making sure each one isn’t causing an issue.

I know it could be time consuming to do this, but it’s really the only sane way to do troubleshooting of this sort of issue.

1 Like
12

I regularly uninstalled Statistics, then manually deleted the luci_statistics and collectd config files.

These are modules are installed: collectd-mod-conntrack modules, collectd-mod-cpu, collectd-mod-df, collectd-mod-disk, collectd-mod-exec, collectd-mod-interface, collectd-mod-iwinfo, collectd-mod-load, collectd-mod-memory, collectd-mod-network, collectd-mod-ping, collectd-mod-rrdtool, collectd-mod-sensors, collectd-mod-thermal, collectd-mod-unixsock, foris-controller-collectd-module, foris-controller-collectd-module-src

After reinstalling and rebooting, I stopped follectd in startup and kill it. It was needed to manually enable luci_statistics in auto-start

I placed RRD in /srv/rrd

This tabs are displayed in Statistics: collectd-mod-conntrack, collectd-mod-cpu, collectd-mod-df
collectd-mod-disk, collectd-mod-exec, collectd-mod-interface, collectd-mod-iwinfo, collectd-mod-load, collectd-mod-memory, collectd-mod-network, collectd-mod-ping, collectd-mod-rrdtool, collectd-mod-sensors, collectd-mod-thermal, collectd-mod-unixsock, follectd, foris-controller-collectd-module, foris-controller-collectd-module-src

and Interfaces, Wireless, Conntrack, Ping

Graph data in /srv/rrd/ Turris_JB is not created Graphs are not displayed (it not see graph coordinates)

These errors are newly found in syslog

Apr 7 16:34:48 Turris_JB collectd [16850]: Error: Parsing the config file failed!
Apr 7 16:34:53 Turris_JB collectd [16860]: configfile: stat (/tmp/collectd.conf) failed: No such file or directory
Apr 7 16:34:53 Turris_JB collectd [16860]: Configuration file /tmp/collectd.conf is empty.

Therefore, collectd is not running now

In the past, I unsuccessfully solved the problem the easiest way - by returning to the older functional version using schnapps

13

Similarly

root @ Turris_JB: ~ # opkg install collectd --force-reinstall
Removing package collectd from root ...
Not deleting modified conffile /etc/config/collectd.
Installing collectd (5.12.0-1) to root ...
Downloading https://repo.turris.cz/hbs/omnia/packages/packages/collectd_5.12.0-1_arm_cortex-a9_vfpv3-d16.ipk
Configuring collectd.
Collected errors:
  * file_sha256sum_alloc: Failed to open file / etc / config / collectd: No such file or directory.
root @ Turris_JB: ~ #

The It lists the error though file /etc/config/collectd existed

image

After deleting this /etc/config/collectd file again, colletcd will run and I will watch what happens.

=================================
*** Ex auctoritae Dei omnipotentis, Patris, et Filii, et Spiritus Sacti, et sanctorum canonum, sanctaeque et intemeratae Virginis Dei genetricis Mariae. Atque omnium coelestium virtutum, angelorum, archangelorum, … anathema sit … Good God, righteous, omnipotent, merciful … it works.

I like that so much when I don’t know where the problem was?

14

It is then installed + reboot.

• Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ledtrig-heartbeat
Souhrn 
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-libphy
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-swconfig
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-switch-mvsw61xx
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ikconfig
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-nls-base
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-usb-core
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-scsi-core
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-usb-storage
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-usb-storage-extras
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-usb-serial
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-usb-serial-wwan
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-usb-serial-qualcomm
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-i2c-core
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-i2c-mux
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-i2c-mux-pca954x
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-gpio-pca953x
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-nvmem
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-eeprom-at24
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ledtrig-default-on
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-usb-storage-uas
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-usb-ehci
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-usb2
 • Installed version 4.14.274+4.19.221-1-1-473c1393009fbc6bdc1f54511245c742 of package kmod-cfg80211
 • Installed version 4.14.274+4.19.221-1-1-473c1393009fbc6bdc1f54511245c742 of package kmod-mac80211
 • Installed version 4.14.274+4.19.221-1-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ath
 • Installed version 4.14.274+4.19.221-1-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ath10k
 • Installed version 4.14.274+4.19.221-1-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ath9k-common
 • Installed version 4.14.274+4.19.221-1-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ath9k
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-nf-conntrack
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-nf-flow
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-nf-ipt
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-nf-reject
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ipt-core
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-br-netfilter
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-nf-nat
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-nf-nathelper
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ledtrig-gpio
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ledtrig-oneshot
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ipt-nat
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-nf-conntrack6
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ipt-conntrack
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ledtrig-netdev
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ledtrig-transient
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ledtrig-timer
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ipt-offload
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ipt-raw
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ipt-conntrack-extra
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ipt-ipopt
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-ifb
 • Installed version 4.14.274+2019-03-12-057c7388-1-473c1393009fbc6bdc1f54511245c742 of package kmod-sched-cake
 • Installed version 4.14.274-1-473c1393009fbc6bdc1f54511245c742 of package kmod-sched-core
 • Installed version 5.12.0-1 of package collectd-mod-exec
 • Installed version 5-2

Only the annoying syslog bug persists

foris-controller [6088]: WARNING: foris_controller_backends.collectd: Socket error occured '[Errno 2] No such file or directory'

=======================
What this error means ?

Collected errors:
  * file_sha256sum_alloc: Failed to open file / etc / config / collectd: No such file or directory.
1 Like
15

Both of my MOXes hangs (v4 applied).

16

OS update 5.3.7 cannot install apps from Google Play on your phone :(.

17

TOS 5 are able to install apps from the Google Play?

18

Is it unrelated to AdBlock? I had similar issues when setting up an AdBlock blacklist.

19

I do not have AdBlock activated (installed).

20

How do you set up reForis DNS Settings (forward) ?

21

There is no such thing that update will affect it.