Turris OS 7.1 is out!

Community office
, , ,
104

it seems like my turris 1.1 successfully survived the upgrade, but I use the knot / kresd as the resolver

105

Soā€¦

Omnia from Indiegogo. No internet for any of devices on the network, but connection test in reForis is fully OK, including test in DNS section.

Update went on 26 november according to snapshots page (no notifications about that in reForis) and today 29. november, no internet. I have tried to change DNS provider and turn on/off DNSSEC, but nothing helped. Only rollback to 7.03 helped.

Very strange. Please fix it.

1 Like
106

I have some error during the updating process from 7.0.3 to 7.1.

Thank you for your Support.

Luca,

Updater execution failed:


Stack Traceback

===============

(1) Lua function '?' at line 57 of chunk '"logging"]'

	Local variables:

	 err = string: "[string \"transaction\"]:334: [string \"transaction\"]:142: Collisions:\

ā€¢ /sbin/logread: syslog-ng (existing-file), logd (new-file)"

	 err2string = Lua function '?' (defined at line 38 of chunk "logging"])

	 msg = string: "\

[string \"transaction\"]:334: [string \"transaction\"]:142: Collisions:\

ā€¢ /sbin/logread: syslog-ng (existing-file), logd (new-file)"

	 (*temporary) = table: 0xb14de6b0  {msg:

[string "transaction"]:334: [string "transaction"]:142: Collisions:

ā€¢ /sbin/logread: syslog-ng (existing-file), logd (new-file) (more...)}

(2)  C function 'function: 0xb1899ec0'

(3) upvalue C function 'error'

(4) Lua function '?' at line 334 of chunk '"transaction"]'

	Local variables:

	 operations = nil

	 journal_status = table: 0xb1e55390  {}

	 run_state = table: 0xb67055a0  {initialized:true, init:function: 0xb6705660, lfile:userdata: 0xb6663fa8 (more...)}

	 step = Lua function '?' (defined at line 276 of chunk "transaction"])

	 dir_cleanups = table: 0xb1e55660  {1:/usr/share/updater/unpacked//updater-fefMDk, 2:/usr/share/updater/unpacked//updater-HAAaFJ (more...)}

	 status = table: 0xb6663ff0  {shadow-groupmod:table: 0xb63db2c0, nsenter:table: 0xb6647850, rainbow-animator:table: 0xb6148770 (more...)}

	 errors_collected = table: 0xb1e554e0  {}

	 ok = boolean: false

	 err = string: "[string \"transaction\"]:142: Collisions:\

ā€¢ /sbin/logread: syslog-ng (existing-file), logd (new-file)"

(5) tail call

	Local variables:

	 (*temporary) = C function: 0xb1899ec0

(6) Lua function '?' at line 425 of chunk '"transaction"]'

	Local variables:

	 queue_cp = table: 0xb66f52c0  {1:table: 0xb1672110, 2:table: 0xb1672290, 3:table: 0xb1d7a700, 4:table: 0xb1672980 (more...)}

	 (*temporary) = Lua function '?' (defined at line 402 of chunk "transaction"])
Unknown error (Exit code: -6)
107

I have exactly the same problem.

Also rolled back to 7.0.3 and waiting for a working solution.

108

I succesfully updated my Turris v1.1 to new version with following steps:

  1. switch unbound resolver to knot by this manual
  2. rename file /sbin/logread
  3. manually install logd package
  4. run update TOS7.1.0 in reforis

and after install everything works fine.

1 Like
109

Could you try something like:

/etc/init.d/network restart

or

/etc/init.d/firewall restart

when ever one of the hotplug scripts wedges itself the rest of the bunch is not processed anymore, and sometimes manually runniing these can help.

PLEAS NOTE, I am typing from memory, so the actual commands to restart the firewall might be different.

110

I have tried several reboots, nothing helped. Even unplugging the power cord for some time didnā€™t helped.

111

Well, if the root cause is a wedged hotplug script you will run into this every time, so the test is intended to see whether running the firewall start/restart script gives you LAN internet connectivity, if that works the next step would be to figure out what goes pear shaped on the normal way to start upā€¦

IIRC I had problems with one of the NTP hotplug scriptsā€¦ that started and never returned so hotplug (which is/was in series) basically waited forever in the NTP script and never got around to execute the firewall scriptā€¦

112

Well, the root cause is that during the update were broken default settings (DNSSEC enabled, use DNS by provider), which should work every-time.

I donā€™t have time to debug such basic things. According to the forum, I am not alone and the only solution is rollback to 7.0.3

PS:
I have tried network and firewall restart - didnā€™t helped either.

114

Iā€™ve tried the update again with same unbound issue and this reinstall of libevent2 indeed fixed it.

opkg info libevent2 (before update)

Package: libevent2
Version: 2.1.12-1
Depends: libc
Status: install user installed
Architecture: powerpc_8548
Installed-Time: 1667688983

# ls -la /usr/lib/libevent-2.1.so.7.0.1
-rw-r--r--    1 root     root        262356 Feb 14  2021 /usr/lib/libevent-2.1.so.7.0.1

(also saved the file to /root)

after the force reinstall:

# ls -la /usr/lib/libevent-2.1.so.7.0.1
-rw-r--r--    1 root     root        262356 Feb 14  2021 /usr/lib/libevent-2.1.so.7.0.1

same size and time, butā€¦

diff /usr/lib/libevent-2.1.so.7.0.1 ./libevent-2.1.so.7.0.1 
Binary files /usr/lib/libevent-2.1.so.7.0.1 and ./libevent-2.1.so.7.0.1 differ

that should mean 7.1.1 is on the right trackā€¦

115

Also had DNS issues (Omnia 2020), but maybe different ones. Iā€™m using pihole between devices and the turris. The following caused all devices to time out on many websites (or they took about a minute to resolve) because they couldnā€™t get DNS answers.

The update added faulty dhcp.lan.dhcp_option entries (In LuCi > network interfaces > edit on each of them > DHCP > advanced).
In addition to my existing DHCP option entries for NTP and DNS
42,192.168.0.1 (thatā€™s the turris)
6,192.168.0.2,192.168.0.2 (thatā€™s the pihole)
the update added
6,192.168.0/24
which does not make any sense. The option even doesnā€™t get parsed correctly when passed to my PC (whether on turris or PC side I cannot tell), so that the PC ended up trying to contact a DNS server at 24.192.168.0 ā€¦which obviously didnā€™t work.
I removed the faulty DHCP option entries from all affected interfaces, and after the DHCP leases of the devices were renewed, everything was back to normal :slight_smile:

PS. Disliked this hickup and the broken banIP, but the taking over of all my firewall rules so flawlessly is very appreciated!

1 Like
116

Thatā€™s really strange. I use openwrt adblock and the upgrade worked fine. I donā€™t have any new entry in the dhcp config on any of the interfaces.