Turris OS 5.1 is out

any idea what may be the way and who can to connect in such way?

Hello,

After updating from 5.0.4 to 5.1 I get
once a day this mail, it is always the same:

Error notifications

Updater failed:

runtime: [string “requests”]:417: [string “utils”]:422: Unable to finish URI (https://repo.turris.cz/hbs/omnia/lists/pkglists/netdata.lua): Download failed

There seems to be something wrong with Netdata in the repository, or not available. Everything else works fine.
Netdata itself also works.

Best Regards

apparently it’s when someone tries to port forward/tunnel. the haas-proxy does not support this. https://gitlab.nic.cz/haas/proxy/-/issues/2

also interesting might be, if you installed haas HP, and after that you install PAKON, the HP stops working, at least here… Solution is to re install the HP, and all is working.

At least once a day this is happening and kicks me off the network. I have to disconnect and reconnect to be able to access it again.

Sep 1 20:07:10 turris hostapd: wlan0: AP-STA-DISCONNECTED d0:c6:37:bd:cd:bf
Sep 1 20:07:21 turris hostapd: wlan0: STA d0:c6:37:bd:cd:bf IEEE 802.11: authenticated
Sep 1 20:07:21 turris hostapd: wlan0: STA d0:c6:37:bd:cd:bf IEEE 802.11: associated (aid 1)
Sep 1 20:07:21 turris hostapd: wlan0: STA-OPMODE-SMPS-MODE-CHANGED d0:c6:37:bd:cd:bf off
Sep 1 20:07:21 turris hostapd: wlan0: AP-STA-CONNECTED d0:c6:37:bd:cd:bf
Sep 1 20:07:21 turris hostapd: wlan0: STA d0:c6:37:bd:cd:bf RADIUS: starting accounting session 82778C05581626C8
Sep 1 20:07:21 turris hostapd: wlan0: STA d0:c6:37:bd:cd:bf WPA: pairwise key handshake completed (RSN)
Sep 1 13:07:22 turris dnsmasq-dhcp[15074]: read /etc/ethers - 0 addresses
Sep 1 20:07:22 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:22 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:22 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:22 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:22 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:22 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 13:07:23 turris dnsmasq-dhcp[15074]: read /etc/ethers - 0 addresses
Sep 1 20:07:23 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:23 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:23 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:23 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:23 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:23 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:23 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:24 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:24 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:24 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:24 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:24 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:24 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:24 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:25 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:25 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:25 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:25 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:25 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:25 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:25 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:25 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:26 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:26 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:26 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:26 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:26 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:26 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:27 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:27 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:27 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:27 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:27 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:27 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:27 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:27 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:28 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:28 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:28 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:28 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:28 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:28 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:29 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:29 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:29 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:29 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:29 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:29 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:29 turris /dhcp_host_domain_ng.py: DHCP unknown update operation
Sep 1 20:07:29 turris /dhcp_host_domain_ng.py: Refresh kresd leases
Sep 1 20:07:33 turris sshd[29526]: Accepted password for root from 10.0.0.16 port 51510 ssh2

I found a same. A lot of previously enabled services become disabled by default. By enabling them again solved all issues. Fortunately configurations remained untouched. In my case mdadm, samba, minidlna and some others…

Yes, seeing the same.
Update to 5.1 is somehow divided into 2 steps. In first step, it remove all packages related to samba. (and few more)
And as second step requires approval from (re)foris in order to finish updates and install samba back I ended up with no samba installed at all…
Same thing already happened during 4->5.0 migration.

Also during 5.0.x updates, SATA HDD issues re-appeared again (workaround doesn’t work)
This is really shame and I gave up with Turris as NAS :frowning:

1 Like

Same here, upgrade botched my services, I don’t have approval set up, but still took 2 reboots to finish.
Also, sata errors in syslog are also there on startup, but don’t appear when the system is running (don’t have raid, just one ssd and one hdd).

Hi Pavel, there are several similar issues that were probably caused by WebSockets.
Have you changed the Lighttpd ports? Please check https://gitlab.nic.cz/turris/reforis/foris-js/-/issues/17 & ReForis port issue.
Otherwise, it is fixed and will be available in further updates.
Thanks, Aleksandr

I recently upgrade from TurrisOS 3 to TurrisOS 5 and it seems that Ludus is no longer compatible. I am getting errors on both GUI and CLI that:

root@turris:~# pkgupdate
INFO:Target Turris OS: 5.1.0
WARN:Requested package luci-i18n-rainbow-en that is missing, ignoring as requested.

I’ve tried opkg remove ludus-guibut that doesn’t seem to work, does anyone know how to fix this issue?

A post was merged into an existing topic: microSD card and corrupted FS

Hmmm - well I thought all was well after the update, but not so. Adblock disabled by default and something strange is going on with the wifi (very slow, reduced signal) if I attempt the same with ethernet, no problems. Only started since the update.

Issue with LUCI and LXC config screen still present (LUCI overlays I think was the issue last time?)

I managed to create a LXC with the command line but still the Luci page is unusable (keeps asking for login then throws up error of main not being found.)

Two things are standing out after updating:

  1. When opening ReForis, I get an 403, but will be redirected to the login page after a second or so. Not a big thing.

  2. When using a non-English or non-German browser profile, after logging in, the page keeps refreshing a few times while showing this error, then will stop eventually after a few reloads:

reForis version 0.9.3
An Error Occurred
TypeError: langsList.map is not a function

More detailed information is available in the console of your web browser - on most browsers accessible after pressing Ctrl+Shift+J or F12.

Please report this error to our support team via e-mail: tech.support@turris.cz.

I’m seeing this too. A momentary 403 before a redirect.

1 Like

My samba4 and minidlna also got disabled by the update from 5.0 to 5.1 (HBS with update approvals, Omnia 1GB).

Try upgrade to gerbera instead.

That’s unrelated. Minidlna works for me when I enable it manually.

1 Like

Minidlna is abandoned in TOS.

I was curious about this too. I hadn’t noticed that samba4 was disabled, so I tried installing it.

#### Executing package manager

Installing samba4-server (4.11.11-3.7-1.2) to root...

##### Errors

Collected errors: 
* opkg_download_pkg: Package samba4-server is not available from any configured src. 
* opkg_install_pkg: Failed to download samba4-server. Perhaps you need to run 'opkg update'? 
* opkg_install_cmd: Cannot install package samba4-server.

I made sure “NAS” and “Samba” were selected. Here’s my distfeeds.conf:

src/gz turrisos_core https://repo.turris.cz/hbs/omnia/packages/core
src/gz turrisos_base https://repo.turris.cz/hbs/omnia/packages/base
src/gz turrisos_cesnet https://repo.turris.cz/hbs/omnia/packages/cesnet
src/gz turrisos_luci https://repo.turris.cz/hbs/omnia/packages/luci
src/gz turrisos_node https://repo.turris.cz/hbs/omnia/packages/node
src/gz turrisos_openwisp https://repo.turris.cz/hbs/omnia/packages/openwisp
src/gz turrisos_packages https://repo.turris.cz/hbs/omnia/packages/packages
src/gz turrisos_routing https://repo.turris.cz/hbs/omnia/packages/routing
src/gz turrisos_sidn https://repo.turris.cz/hbs/omnia/packages/sidn
src/gz turrisos_telephony https://repo.turris.cz/hbs/omnia/packages/telephony
src/gz turrisos_turrispackages https://repo.turris.cz/hbs/omnia/packages/turrispackages

That looks like all of them. I feel like I missed an announcement about it not being available in 5.1, but I’m not sure.

[edit]
I found samba4-server_4.11.11-3.7-1_arm_cortex-a9_vfpv3-d16.ipk in /omnia/packages/packages where samba36 is in /omnia/packages/core

So, I"m not sure why it’s asking for 4.11.11-3.7-1.2 when only 4.11.11-3.7-1 is available.

Same happened to me… I was not able to install it manually.
I have 1 additional update to be approved in foris. After that, upgrade to 5.1 was finalized and samba4 installed again (of-course disabled)