Turris OS 3.11 is out!

release

#61

I noticed that Data Collection was uninstalled during update on both of my Omnias. Is this supposed to be due to implementation of sentinel?


#62
root@turris:~# pkgupdate
WARN:Requested package luci-i18n-ddns-en that is missing, ignoring as requested.
line not found
line not found
line not found
line not found
line not found
ERROR:
inconsistent: Requested package ddns-scripts_cloudflare that is not available.

I am using Cloudflare DNS for dynamic updates and would like to keep it working. Please help.


#65

You need to remove package ddns-scripts_cloudflare as it was using API v1, which was retired on June 4.
More details about it can be found here:


If you’d like to use ddns-scripts for cloudflare, you need to install package ddns-scripts_cloudflare.com-v4


#68

Don’t you have connected any devices, which has running DHCP server? It could be a repeater or something else. That’s might be why you experienced the issue, which you described because when the router detects any other running DHCP server, it will turn off it’s DHCP server.


#69

Ok, that helped. Thanks. I also needed to stop/disable ddns, if this is a known issue, maybe the upgrade script should do it by itself?


#70

Just to clarify regarding NTP, ntpdate is installed by default in place of ntp and ntpdate runs automatically if enabled? There is no longer a ntp setting under “system”?


#71

Nextcloud is broken after 3.11 update:

How can I debug this?


#72

Just a note: after this update I’ve to reinstall a BigClown dongle:

turris ~ # pip3 install --upgrade bcf
turris ~ # pip3 install --upgrade bcg

#73

I have implemented the suggestions for the update. DDNS turned off and undone the changes for DNS over TLS on the Knot Resolver. Update went through clean and everything works fine. Now I’m looking for the option to change the default DNS (in my case to Cloudflare).

Edit: according to Mail the foris-tls-plugin was uninstalled (some packages at the end of the mail)
Is it related to it? Everything works so far, only this thing makes me suspicious

##### Restart is needed #####
The system was updated, but some changes will take effect only after reboot. Please reboot the device.

The device will be restarted automatically on Friday, December 14 at 03:30 AM.
 • **Removed package foris-tls-plugin-l10n-de**
 • Removed package python-libatsha204
 • **Removed package foris-tls-plugin**

Where is this menu? Or was it really uninstalled? Can I reinstall it?

Best regards!


Requested package foris-tls-plugin that is not available
#74

This is another TERRIBLE update.
Updater hangs on my Onmia forever too.

First, it was not possible to even run update properly. Manual attempts of pkgupdate were ending as:

INFO:Queue install of create_notification/turris/58
line not found
line not found
line not found
ERROR:
unreachable: https://repo.turris.cz/omnia/packages/base/kernel_4.4.165-1-4a7a81f8db0ad743e54c68e1845c60b6-1_mvebu.ipk: Operation timed out after 55209 milliseconds with 491250 out of 2807478 bytes received

On each attempt it failed at different stage, not at the same file. Amazingly, pkgupdate always tried to download ALL packages again and again FROM THE START, not from the latest failed package, so it never finished.

Well, my router had uptime for about 30 days, so I rebooted it (yes, it is the approach which is usually taken on “unnamed OS known for it’s low quality”, but since several repeated attempts were unsuccessful, I saw it as pragmatic option). After reboot I started pkgupdate again, it downloaded all packages smoothly at the first shot and went with the update. I thought it’s finally going well, but then it hanged in postinstallation phase, last messages were:

Output from foris-diagnostics-plugin-l10n-sk.postinst:

  • ‘[’ -n ]
  • /etc/init.d/lighttpd restart
    Output from nuci.postinst:
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    100 65 100 65 0 0 39 0 0:00:01 0:00:01 --:–:-- 48
    Output from foris-controller-storage-module.postinst:
  • ‘[’ -z ]
  • /etc/init.d/foris-controller restart
  • /etc/init.d/srv enable
  • mkdir -p /srv
    Output from foris-storage-plugin.postinst:
  • ‘[’ -n ]
  • /etc/init.d/lighttpd restart

After it was stuck for too long time (pkgupdate process still existing), I rebooted router manually. And guess what: Boot did not finish properly, there was “forever running” process:

3094 root 1164 S /bin/sh /etc/rc.common /etc/rc.d/S85updater boot

(so for example LED colors were not set)
Storage, storage… yes, I do have mSATA SSD, /dev/sda1 is mounted on /srv, Foris shows it properly, nothing extraordinary here, I definitely do not expect any problems here.

This update is another huge disappointment, breaking things which were working (and as I see this thread, not only for me). You know what? I’m done with this sh!t, really.
Rolled back to previous snapshot of 3.10.8. Disabled automatic updates completely. It’s exactly opposite of what was advertised when Omnia campaign was running, but I already spent way too much time with these repeated breakages. While I consider myself quite patient and I understand that everything does not always go perfectly, my experience with several other OSes shows, that what happens with Omnia is really not necessary. Yeah guys, you failed in your mission. Instead of motivating users to frequent updates, your “message” to them really translates to “Don’t risk any updates, there is big chance that things will break suddenly.”


#75

This is a bug in the ddns-scripts package.
We or somebody else needs to dig this bug and look what’s happening inside the ddns-scripts and fix it. I think that we won’t update it unless we have to because of a security issue if it would be found. Hopefully not.
Updater guy (@cynerd ) did some improvements for Updater and prepared pull request for review. My rough estimate is that it can be included in Turris OS 3.12. You can see his response here about this issue.


#76

Unfortunately, from this message, we don’t see what can be wrong. Can you check system logs or Nextcloud logs, if there is anything that will tell us more?


#77

I’m keep getting notifications:

Updater selhal:

inconsistent: Requested package foris-tls-plugin that is not available.

#78

I see we have removed foris-tls-plugin for Turris OS 3.11. It was a Foris plugin, which provides a frontend for NUCI TLS plugin, by small steps, we’re trying to remove nuci as much as we can, because it is just an old project, which we deprecated and thus we don’t provide support for it. NUCI (Networked UCI) is a daemon for accessing OpenWRT configuration through a network with the netconf protocol.

Is there any reason, why would you like to have it installed? I think you might have it installed by hand. So, you can remove it with the following command. Once you do that you can run Updater again.

opkg remove foris-tls-plugin

//EDIT: @freshdax: If it was uninstalled, then everything is fine. :slight_smile: No need to worry about it.


#79
    root@turris:/tmp/log# grep -i err messages 
    2018-12-11 18:32:00 err kresd[2761]: [priming] cannot resolve '.' NS, next priming query in 10 seconds
    2018-12-11 18:32:00 err block[]: /dev/sda is already mounted
    2018-12-11 18:32:01 err block[]: /dev/sdb1 is already mounted
    2018-12-11 18:32:01 err block[]: /dev/sdc1 is already mounted
    2018-12-11 18:32:01 err block[]: /dev/sdd1 is already mounted
    2018-12-11 18:32:05 err ntpdate[4407]: name server cannot be used: Try again (-3)
    2018-12-11 18:32:47 err foris-controller[2965]: WARNING:turrishw:unsupported TOS version (on omnia): 3
    2018-12-11 18:32:54 err foris-controller[2723]: Last message 'WARNING:turrishw:uns' repeated 1 times, suppressed by syslog-ng on turris
    2018-12-11 18:33:12 err foris-controller[2965]: WARNING:turrishw:unsupported TOS version (on omnia): 3
    2018-12-11 18:33:20 err foris-controller[2723]: Last message 'WARNING:turrishw:uns' repeated 1 times, suppressed by syslog-ng on turris
    2018-12-11 18:36:18 info updater-supervisor[]: pkgupdate reported no errors
    2018-12-11 19:00:02 err server_uplink[]: Failed to download contract status
    2018-12-11 20:00:01 err server_uplink[]: Failed to download contract status
    2018-12-11 20:11:03 info updater-supervisor[]: pkgupdate reported no errors
    2018-12-11 21:00:01 err server_uplink[]: Failed to download contract status
    2018-12-11 22:00:01 err server_uplink[]: Failed to download contract status
    2018-12-11 22:01:01 err server_uplink[]: Failed to get registration code
    root@turris:/tmp/log# grep -i err /srv/www/nextcloud/data/nextcloud.log
    {"reqId":"AAn4o6h6QBYKIEco4lhu","level":3,"time":"2018-12-11T21:18:02+00:00","remoteAddr":"192.168.1.20","user":"--","app":"index","method":"GET","url":"\/nextcloud\/","message":{"Exception":"Error","Message":"Class 'OCP\\Config' not found"

Besides these error messages i haven’t found anything, yet. What should I look for?


#80

This is another TERRIBLE update.

Thanks, dude. I can understand that in your case it didn’t end up well, but please, let’s avoid words like shit.
I know that it gave you some temporary relief, but in the end, it doesn’t help anyone.

Would not be better, if together we can focus and improve things, which can push us forward? So we can make everyone happy including you.
You as a part of the community can help us to catch bugs or issues, which appears. So, we can fix them. I would lie to myself if I said there would never be an issue or bug. There might be always something, so all of us can improve the next release as we can not test all setups, which are possible. That’s something that we’d like to deal with. Most users won’t notice it.

Unfortunately, Turris OS 3.11 brings a lot of changes as it is a major release. It was in RC for a month, you can check it here: Turris OS 3.11 in RC! It looked like that we could release it. However, not many users were in RC as you can see. I see it’s something, what can be improved. Should we at least give active users, who helped us T-shirts or any other swag?

Anyway, this release was a good one except for ddns-scripts issue even there is always what can be improved as most of the issues was caused by upgrading busybox because it provides ntpd. That’s what can be solved in a few seconds or minutes. I don’t know if it helps you, but this happens in the latest snapshot of OpenWRT.

If you would like to compare some numbers here or on Support (tech.support@turris.cz), it’s really small numbers comparing it against routers, which are running. Would you provide positive feedback about things or products, which you like to manufacturer or support? I doubt it. Most of the feedback you can see here or somewhere else it’s from users, who are not satisfied or they found some issue.

Let’s talk about your issues.
The issue, which you have mentioned is related to your internet connection and I doubt that’s what we can change if you look at the error message what it says - Operation timed out. If the restart solves it, then great.

ERROR: unreachable: https://repo.turris.cz/omnia/packages/base/kernel_4.4.165-1-4a7a81f8db0ad743e54c68e1845c60b6-1_mvebu.ipk: Operation timed out after 55209 milliseconds with 491250 out of 2807478 bytes received

About Updater and its hang, I have already answered it here:

Just my two cents, I don’t recommend to disable automatic updates completely as you can use updates with approval or delayed updates, because, in almost every version of Turris OS, we’re upgrading packages, which had security issues.


#81

I don’t remember installing it, so probably I don’t needed. I’ve uninstalled it.
Thank you!


#82

Did you find out out to update the ntp servers? Or enable ntp server in router?


#83

The Wifi adapter 2.4 Ghz is slower than before. To connect 30/30 Mbps reach after the update speed between 7-15 Mbps. The 5 Ghz network is without speed reduction, previously both WiFi networks were at a speed of comparable or identical.

Both channel 2.4 and broadcast performance are the same as before update


#84

We haven’t update ath9k, it might seem for you like it is caused by the update, but we didn’t do anything with it. There are many access points on 2.4 GHz wireless, so there is a lot of interference and not many spaces for another ap in the same frequency. I’d suggest changing the channel of the radio for 2.4 GHz and see if it helps.