Turris OS 3.11.5 is released!

Can you please run a following command opkg search /usr/bin/suricata? You will see which package provides a binary file of suricata and then you can remove it.

You can send us also diagnostics, which you can generate in Foris to tech.support@turris.cz, where we will help you.

It will be for a new mobile app and also for something else, which we are preparing.

1 Like

Nothing was found:

root@turris:~# opkg search /usr/bin/suricata
root@turris:~#

E-mail to tech.support@turris.cz sent.

Sending of the testing message failed, your configuration is possibly wrong.

I test in my turris omnia in home and failed when update
I test in my work after udpate and also failed to send email notifications from different server/smtp config that before updating if it worked.
I use ssl and 465 port as usal.
Thanks

If we do not see your configuration and server, it is not possible to advise:-). Use the server Turris-it is also safer.

Had exactly the same issue! Left him 30 min to recover but still only white leds but no WAN nor LAN / WLAN. Did the 2 LEDs Reset and it was up again running 3.11.5.
This is not called a smooth update :frowning:

This is my config at home but in work i have other turris omnia updated with other domain and also now failed to send email notifications.

Oh, yes … new version of TurrisOS is coming :slight_smile:

1 Like

Thanks for the reporting, we were able to found what’s wrong and it should be fixed in Turris OS 3.11.6.

It is time to release something new. Right? :stuck_out_tongue:

1 Like

“Managed devices” section in Foris is not translated to Czech. I can´t click to “Device list” icons in Chrome. Internet Explorer 11 is not able to show the list, hanging “Loading manged devices…”.

1 Like

Omnia “Wi-Fi” tab in “Managed devices” still not working with MOX (Turris OS 4.0beta8).

State: exclamation mark, Devices and Channels: hang.

ID corresponds to token name in MOX.

Tested with Chrome and Firefox.

May I ask you if you can try Turris OS 3.11.6 to see if the issue persists? As there were some fixes for netboot.

I am not so happy to switch production router to RC, but I want to help.

switch-branch rc

INFO:Running postinst of turris-netboot-tools
udhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: no lease, failing
udhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: no lease, failing
udhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: no lease, failing
chown: /srv/turris-netboot: Read-only file system
chown: /srv/turris-netboot: Read-only file system
mkdir: can’t create directory ‘/srv/tftp/pxelinux.cfg’: I/O error
touch: /srv/tftp/pxelinux.cfg/default-arm-mvebu-turris_mox: I/O error
chown: /srv/tftp/pxelinux.cfg/default-arm-mvebu-turris_mox: I/O error
mkdir: can’t create directory ‘/srv/tftp/turris-netboot’: I/O error
chown: /srv/tftp/turris-netboot: I/O error
chown: /srv/turris-netboot/clients/accepted: Read-only file system
chown: /srv/turris-netboot/clients/incoming: Read-only file system
chown: /srv/turris-netboot/clients/transfering: Read-only file system
chown: /srv/turris-netboot/clients/accepted: Read-only file system
chown: /srv/turris-netboot/clients/incoming: Read-only file system
chown: /srv/turris-netboot/clients/transfering: Read-only file system
Generating public/private ed25519 key pair.
Regenerating configuration…
Could not stat /srv/turris-netboot/.ssh: I/O error
Saving key “/srv/turris-netboot/.ssh/reg_key” failed: I/O error
/usr/bin/netboot-manager: line 120: can’t create /srv/tftp/pxelinux.cfg/default-arm-mvebu-turris_mox: I/O error
/usr/bin/netboot-manager: line 130: can’t create /srv/turris-netboot/.ssh/authorized_keys: I/O error
chmod: /srv/turris-netboot/.ssh/authorized_keys: I/O error
Getting new rootfs…
/srv/turris-netboot/rootfs/rootfs-new.tar.gz: Read-only file system
Can’t download tarball
Output from turris-netboot-tools.postinst:
udhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: no lease, failing
udhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: no lease, failing
udhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: no lease, failing
chown: /srv/turris-netboot: Read-only file system
chown: /srv/turris-netboot: Read-only file system
mkdir: can’t create directory ‘/srv/tftp/pxelinux.cfg’: I/O error
touch: /srv/tftp/pxelinux.cfg/default-arm-mvebu-turris_mox: I/O error
chown: /srv/tftp/pxelinux.cfg/default-arm-mvebu-turris_mox: I/O error
mkdir: can’t create directory ‘/srv/tftp/turris-netboot’: I/O error
chown: /srv/tftp/turris-netboot: I/O error
chown: /srv/turris-netboot/clients/accepted: Read-only file system
chown: /srv/turris-netboot/clients/incoming: Read-only file system
chown: /srv/turris-netboot/clients/transfering: Read-only file system
chown: /srv/turris-netboot/clients/accepted: Read-only file system
chown: /srv/turris-netboot/clients/incoming: Read-only file system
chown: /srv/turris-netboot/clients/transfering: Read-only file system
Generating public/private ed25519 key pair.
Regenerating configuration…
Could not stat /srv/turris-netboot/.ssh: I/O error
Saving key “/srv/turris-netboot/.ssh/reg_key” failed: I/O error
/usr/bin/netboot-manager: line 120: can’t create /srv/tftp/pxelinux.cfg/default-arm-mvebu-turris_mox: I/O error
/usr/bin/netboot-manager: line 130: can’t create /srv/turris-netboot/.ssh/authorized_keys: I/O error
chmod: /srv/turris-netboot/.ssh/authorized_keys: I/O error
Getting new rootfs…
/srv/turris-netboot/rootfs/rootfs-new.tar.gz: Read-only file system
Can’t download tarball

Next, I disconnected USB flash, checked it, reformat in computer and put flash back to the router. Restart via “Format & Set” in “Storage” tab.

After restart, “/srv/turris-netboot/” directory stucture was empty.

Further, reinstalled “Turris MOX network boot” in “Updater” tab, directories now contains images.

Finally, situation are same, except: Chrome are working (I can push the buttons in “Set Up”) and exclamation mark icon blinking strange.

Deleting some old btrfs snapshots and balancing seems to help with this issue.

I believe this is something TurrisOS developers need to consider (@Pepe): schedule btrfs balance automatically and reduce the number of snapshots to keep (I think I had more than 10 of them, several were for the same date)

I think running btrfs balance on emmc is a very bad idea, as it leads to heavy write load that damages emmc, especially if it is called periodically…

schnapps has a cleanup algorithm (see schnapps help -> cleanup) that is called every 12 hours by /etc/cron.d/schnapps.

1 Like

Yes, I agree it might be not a good idea, but what I experienced was a really bad performance on any disk operation, and the lack of free space (as in “Total 7 Gb, Used 2 Gb, Free 0 Gb”)

1 Like