Turris OS 6.0 is released

[Patryk]

My MOX keeps trying to upgrade to 6.0, despite the fact it has SDIO card. Luckily, it fails on wireguard package.

Why? It was supposed not to upgrade to 6.x.

[Pepe]

Could you send diagnostics through the support channel, please? We will look into it.

[Leonardo]

I got the same problem, did you fix that?

[pschonmann]

In [CZ] im trying to describe this situation. Seems mox cant detect right branch and switch to hbs-sdio

MOX - HBS@5.4.4 s SDIO se chce updatovat na TOS 6.0 i když by neměl

[maurer]

added logs for my upgrade boot loop issue here

Omnia 2016 boot loop after upgrade to 6.0

[JardaB]

Thanks for solving the problem with lighttpd, (reForis ??) and Luci. It was really enough to edit /etc/lighttpd/conf.d/30-rrdtool.conf by deactivating the line

## rrdtool.db-name = home_dir + "lighttpd.rrd … and then restart … /etc/init.d/lighttpd restart

(Confirming the CPU temperature drop from 62 to 52 degrees Celsius in Statistics … but i think it must be a function of the sensor, because the CPU has the same load)

In my case Luci is working and reForis reports an error even after another router restart

A problem occurred in a Python script. Here is the sequence of function calls leading up to the error, in the order they occurred.

 /usr/lib/python3.9/site-packages/flup/server/fcgi_base.py in run(self=<flup.server.fcgi_base.Request object>)
 /usr/lib/python3.9/site-packages/flup/server/fcgi_base.py in handler(self=<flup.server.fcgi.WSGIServer object>, req=<flup.server.fcgi_base.Request object>)
 /usr/lib/python3.9/site-packages/reforis/__main__.py in __call__(self=

Souhrn

<reforis.main.AppWrapper object>, environ={‘CONTENT_LENGTH’: ‘0’, ‘DOCUMENT_ROOT’: ‘/www/turris-webapps/’, ‘GATEWAY_INTERFACE’: ‘CGI/1.1’, ‘HTTPS’: ‘on’, ‘HTTP_ACCEPT’: ‘text/html,application/xhtml+xml,application/xml;…,/;q=0.8,application/signed-exchange;v=b3;q=0.9’, ‘HTTP_ACCEPT_ENCODING’: ‘gzip, deflate, br’, ‘HTTP_ACCEPT_LANGUAGE’: ‘cs,en-GB;q=0.9,en;q=0.8’, ‘HTTP_CACHE_CONTROL’: ‘max-age=0’, ‘HTTP_COOKIE’: ‘_csrf_token=21dacf1f36a94a281f14f6623bd4a17014f2…qpoyzkp; sysauth=c7fbc69260906ebe035e41349b4e59da’, ‘HTTP_DNT’: ‘1’, …}, start_response=<function BaseFCGIServer.handler..start_response>)
/usr/lib/python3.9/site-packages/flask/app.py in call(self=<Flask ‘reforis’>, environ={‘CONTENT_LENGTH’: ‘0’, ‘DOCUMENT_ROOT’: ‘/www/turris-webapps/’, ‘GATEWAY_INTERFACE’: ‘CGI/1.1’, ‘HTTPS’: ‘on’, ‘HTTP_ACCEPT’: ‘text/html,application/xhtml+xml,application/xml;…,/;q=0.8,application/signed-exchange;v=b3;q=0.9’, ‘HTTP_ACCEPT_ENCODING’: ‘gzip, deflate, br’, ‘HTTP_ACCEPT_LANGUAGE’: ‘cs,en-GB;q=0.9,en;q=0.8’, ‘HTTP_CACHE_CONTROL’: ‘max-age=0’, ‘HTTP_COOKIE’: ‘_csrf_token=21dacf1f36a94a281f14f6623bd4a17014f2…qpoyzkp; sysauth=c7fbc69260906ebe035e41349b4e59da’, ‘HTTP_DNT’: ‘1’, …}, start_response=<function BaseFCGIServer.handler..start_response>)
/usr/lib/python3.9/site-packages/flask/app.py in wsgi_app(self=<Flask ‘reforis’>, environ={‘CONTENT_LENGTH’: ‘0’, ‘DOCUMENT_ROOT’: ‘/www/turris-webapps/’, ‘GATEWAY_INTERFACE’: ‘CGI/1.1’, ‘HTTPS’: ‘on’, ‘HTTP_ACCEPT’: ‘text/html,application/xhtml+xml,application/xml;…,/;q=0.8,application/signed-exchange;v=b3;q=0.9’, ‘HTTP_ACCEPT_ENCODING’: ‘gzip, deflate, br’, ‘HTTP_ACCEPT_LANGUAGE’: ‘cs,en-GB;q=0.9,en;q=0.8’, ‘HTTP_CACHE_CONTROL’: ‘max-age=0’, ‘HTTP_COOKIE’: ‘_csrf_token=21dacf1f36a94a281f14f6623bd4a17014f2…qpoyzkp; sysauth=c7fbc69260906ebe035e41349b4e59da’, ‘HTTP_DNT’: ‘1’, …}, start_response=<function BaseFCGIServer.handler..start_response>)
/usr/lib/python3.9/site-packages/flask/app.py in handle_exception(self=<Flask ‘reforis’>, e=ControllerMissing(‘Connection to controller 0000000B00006219 is lost.’))
/usr/lib/python3.9/site-packages/reforis/init.py in internal_error(error=<InternalServerError ‘500: Internal Server Error’>)
/usr/lib/python3.9/site-packages/flask/templating.py in render_template(template_name_or_list=‘errors/500.html’, **context={‘error’: <InternalServerError ‘500: Internal Server Error’>, ‘g’: <flask.ctx._AppCtxGlobals object>, ‘request’: <Request ‘https://192.168.2.1/reforis/’ [GET]>, ‘session’: <FileSystemSession {’_permanent’: True}>})
/usr/lib/python3.9/site-packages/flask/app.py in update_template_context(self=<Flask ‘reforis’>, context={‘error’: <InternalServerError ‘500: Internal Server Error’>, ‘g’: <flask.ctx._AppCtxGlobals object>, ‘request’: <Request ‘https://192.168.2.1/reforis/’ [GET]>, ‘session’: <FileSystemSession {’_permanent’: True}>})
/usr/lib/python3.9/site-packages/reforis/init.py in add_translations_catalog_to_ctx()
/usr/lib/python3.9/site-packages/flask_babel/init.py in get_locale()
/usr/lib/python3.9/site-packages/reforis/init.py in get_locale()
/usr/lib/python3.9/site-packages/reforis/init.py in _get_locale_from_backend(app=<Flask ‘reforis’>)
/usr/lib/python3.9/site-packages/reforis/backend.py in perform(self=MqttSender, module=‘web’, action=‘get_data’, data=None, raise_exception_on_failure=True, controller_id=None)
/usr/lib/python3.9/site-packages/reforis/backend.py in perform(self=MqttSender, module=‘web’, action=‘get_data’, data=None, raise_exception_on_failure=True, controller_id=None)
/usr/lib/python3.9/site-packages/reforis/backend.py in _send(self=MqttSender, module=‘web’, action=‘get_data’, data=None, controller_id=None)
/usr/lib/python3.9/site-packages/foris_client/buses/mqtt.py in send(self=<foris_client.buses.mqtt.MqttSender object>, module=‘web’, action=‘get_data’, data=None, timeout=30.0, controller_id=‘0000000B00006219’)
/usr/lib/python3.9/site-packages/foris_client/buses/mqtt.py in check_controllers()
ControllerMissing: Connection to controller 0000000B00006219 is lost.
args = (‘Connection to controller 0000000B00006219 is lost.’,)
device_id = ‘0000000B00006219’
with_traceback =

[fantomas]

@Hopper

Ssh is accessible (but the key was changed, so here is another issue to handle).

I have just asked about this, can you check if this caused the problem?

Ssh host mismatch - ecdsa key disabled after 6.0 upgrade

[iron-maiden]

“Next time, when we will be releasing Turris OS 7.0, it will contain just a migration to a newer OpenWrt and no other new features.”

Quoted from the thread:

Turris OS 6.0 aftermath

I fully agree with that first release pure major upgrade and then release new Turris OS specific features.

Major release with such specific changes is a big challenge.

[michal]

“PaKon moved to a separate page” - to which page? Where can I find more details?

[mvasilek]

It’s now a separate webapp, so if you install it, it will show up in the overview where you can choose between reForis, LuCI, Nextcloud, etc.

[bamf]

Since upgrade this happens:

Every 60 seconds. Is this normal? Should I worry? Never seen this behavior before the upgrade.

[tonyquan]

@Pepe saw this also, failed sentinel firewall logs in reForis. will file a support report

[fantomas]

@robinb

In the log file this was mentioned:
turris procd: Instance lighttpd::instance1 s in a crash loop 6 crashes, 0 seconds since last crash

I’ve had the same problem, but no rrdtool config anywhere I could comment out.

luckily error message in /var/log/lighttpd/error.log was at least a bit helpful:

2022-10-21 07:31:31: (../src/server.c.1588) server started (lighttpd/1.4.67)
2022-10-21 07:31:31: (../src/mod_alias.c.70) url.alias: `/bandwidthd/' will never match as `/' matched first
2022-10-21 07:31:31: (../src/server.c.1592) Configuration of plugins failed. Going down.

so I renamed /etc/lighttpd/conf.d/bandwidthd.conf to 00-bandwidthd.conf
and lighthttpd started correctly.
this kind of error should not cause lighthttpd to crash but this is not problem of turris I guess

[0W0]

Yes. I replied to origin comment with link.

Turris OS 6.0 is released

[Mossroy]

Like @dadall , I had to do a rollback of my Mox to 5.4.4 for now.

Here is how I did it (please tell me if I did something wrong, that other should not reproduce):

• As an extra precaution, I made a backup of the SD-card of the Mox. It was probably not necessary but, one never knows. For that, I’ve shut down the Mox, opened module A, extracted the microSD card, plugged it on a computer, and copied its content byte-to-byte (I did it with “Disk” app on Ubuntu, but “dd” command-line would do the same). Then I’ve put the SD-card back in module A
• I restarted the Mox and opened a web browser on /reforis/administration/snapshots. There, I found the latest pre-6.0 snapshot (called “Automatic pre-update snapshot (TurrisOS 5.4.4)” on mine), and clicked on “rollback” on its line
• I waited a while (because no obvious feedback of when the rollback is over), then asked the Mox to reboot
• I browsed to /reforis/login (if you just go to /reforis, there’s a kind of infinite browser loop, probably due to some browser cache), then to /reforis/package-management/update-settings to change automatic update settings: I’ve set it to require manual approval for updates

The Mox seems to be stable. USB works.

[tommyq]

Yeah, last week I’m just rolling back. But the last update in HBT looks OK, except the ethernet on MOX C - the br-lan is empty on my MOX, the lan1-4 unassinged after upgrade - the /etc/config/network looks kind of OK, had no time to compare it yet, when I tried to add it using reforis, the status of lan1-4 is DOWN. In Luci I noticed the empty br-lan, so tried to set it up again, but the lan1-4 still claims no connection. So when I set it up, I lost wi-fi lan as well. Will try to look deeper once I’ll have more time and the will to suffer

[Hopper]

I did not check this at the time when the issue appeared (just added the new key).
I can see now that /etc/ssh/sshd_config was modified at the time of the OS update (the first one).
But the line referencing HostKey is not commented.

[KreMic]

I did the update on my blue Turris Omnia 1GB with internal SSD. It was impossible to do the update via WIFI so I had to do it via ethernet and I chose ssh login and pkgupdate to do so I could see some feedback on how it advances.
As mentioned before by 0W0 in post #96 I manually had to interfere to get mysqld working angain for Nextcloud.

lighttpd was or better is not working properly. I have to say I use letsencrypt and when I tried to start lighttpd it refused to start and I found the following in `/var/log/lighttpd/error.log:

xxxx-xx-xx xx:xx:xx: (…/src/server.c.1588) server started (lighttpd/1.4.67)
xxxx-xx-xx xx:xx:xx: (…/src/mod_alias.c.70) url.alias: /.well-known/acme-challenge/' will never match as /’ matched first
xxxx-xx-xx xx:xx:xx: (…/src/server.c.1592) Configuration of plugins failed. Going down.

After renaming /etc/lighttpd/conf.d/letsencrypt.conf to /etc/lighttpd/conf.d/letsencrypt.conf.bak I was able to start lighttpd and access ReForis, Luci and Nextcloud therefore I got new log entries in /var/log/lighttpd/error.log:

xxxx-xx-xx xx:xx:xx: (…/src/server.c.1588) server started (lighttpd/1.4.67)
xxxx-xx-xx xx:xx:xx: (…/src/mod_openssl.c.3281) SSL: 1 error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol (192.241.210.200)

Content of /etc/lighttpd/conf.d/letsencrypt.conf is

alias.url += ( “/.well-known/acme-challenge/” => “/www/letsencrypt/.well-known/acme-challenge/”)

I was not able to check any further despite lxcworks as well as my DDNS and openvpn server

As I think lighttpd and especially it’s configuration needs some overdoing.

Edit:I just realized Firewall logs in section Sentinel in ReForis failed. Disabling and enabling in ReForis again solved the fail.

Anyway thank you for 6.0 and now is the time to show community can also contribute – hopefully constructive input – to maintainers.

[JardaB]

@michal

“PaKon moved to a separate page” - to which page?

Is Pakon installed on your machine ? ?

[peci1]

@KreMic

Edit:I just realized Firewall logs in section Sentinel in ReForis failed. Disabling and enabling in ReForis again solved the fail.

Rather double-check this. If you restart the firewall logs collector, it has a green check for a few seconds, but then goes red again. At least for me.