Didn’t see this message when I originally replied.
My LEDs were doing the same thing before I rebooted mine after I initially lost WiFi when it auto-updated. That’s what initially made me think something had crashed, and then that maybe I’d rebooted it mid update once I realised it had updated.
Hello,
I have Turris MOX and today my WiFi suddenly disappeared. Seeing that my modem right next to MOX still blinked (I have the LED turned off on MOX), it was not a power outage. I unplugged + plugged the power cord and interestingly enough it booted up (WiFi re-appeared) but once I connected via browser only Luci interface worked, Foris was just throwing errors - half 500 and half 503.
I was like OK, that’s weird, probably some messed up update (happened to me before), let’s do btrfs rollback. Everything started working again.
I logged in to Foris, and in update tab I re-applied settings to start immediate update. After a while my WiFi was gone again. This time I waited for 15 minutes, making sure I don’t interrupt the update. No return to normal.
Once again unplugging and plugging power cord, this time no return of the WiFi. Another btrfs rollback, back to OK state.
Should I just disable the automatic update not to have broken update the third time?
As I have the MOX version with only one RJ45 connector, it’s a bit tricky to do much debugging if I cannot connect anymore.
Anybody experienced the same? Any advices?
Kind regards,
Jiri
Which version of TOS you have? Are you using SDIO or mPCI card?
| Device | CZ.NIC Turris Mox Board |
|---|---|
| Serial number | 56639904431 |
| Turris OS version | 4.0.5 |
| Turris OS branch | hbs |
| Kernel version | 4.14.162 |
Looking up the mail with the invoice receipt you sent out after the Indiegogo campaign - my device is “Turris MOX: Power Wi-Fi Set - extended (included modules A+G) 1 GB RAM”. I never looked inside 
This topic is about TOS 5. Create other thread and explain which of your two wi-fi cards not working together with attached dmesg log.
For me also the upgrade happened in plain daylight, during WFH hours. Isn’t it supposed to run at night ?
After the upgrade, I could ssh to the router, the router could ping the Internet, but machines on LAN could not ping the Internet. I just identified this is mwan3 : when I stop mwan3, I’m back to normal. When I start it, it complains with “uci: Entry not found” messages, but no more insights.
I’m still investigating how to fix the config…
Is this reply to my message? If it is I believe my issue is still related to TOS 5 update. I am pretty certain my MOX auto-updated to it, and after the first WiFi disappearance I might have unplugged/plugged the power cord too early and for the second attempt I waited long enough (about 15 minutes my WiFi was gone before I unplugged/plugged again). Only after the two btrfs rollbacks I started looking what update was supposed to happen and found out this thread that major version update was just released (TOS5). I have WiFi 1 configured as 5GHz and WiFi 2 as 2.4GHz, both networks disappeared after the update.
I have another Turris MOX - Classic in my other place and I just connected there remotely over SSH with tunnel to access the interface. Interestingly enough the Foris interface is also broken (the same 500/503 errors), Luci still works. I cannot say if the WiFi networks work there or not. And it also auto-updated (although this time I did not get any email notification):
| Firmware Version | TurrisOS 5.0.0 21454a772bd8ccf13923db37a9bf02e48abeb278 / LuCI branch (git-20.016.50400-c59a6f3) |
| Kernel Version | 4.14.180 |
| Local Time | Thu Jun 4 21:53:52 2020 |
| Uptime | 4h 24m 43s |
Are you willing to provide any logs? There’s a page of Getting help, which you can use. With LuCI and as well with SSH. If you don’t use Turris support, which is available for you as written in OP, unfortunately, we can not help you.
No, Updater checks every 4 hours if there is an update to apply.
If ever anyone comes across the same issue, my mwan3 config was missing a option family 'ipv4' in the interface sections.
This was not needed in turrisos 4, but on turrisos 5.0 it prevents mwan3 from working, further blocking all LAN to WAN traffic. Painful to debug with only uci: Entry not found appearing randomly on the console…
Would you mind please describe it a little bit more? What means it stopped working? The website is not loading for you or it is loaded, but you can not access to it? Are there any related details in system log?
Which Turris router do you have and which version of Turris OS? Also, I would like to know, which version if Nextcloud do you have installed.
In any case, there is created page in our documentation for Getting help. Can you please follow it?
1 - It means that at client side server responded with “500 Internal Server Error” for “GET https://192.168.1.1/nextcloud/status.php”
2 - /var/log/lighttpd/error.log (same line repeating over and over again):
2020-06-04 17:56:35: (mod_fastcgi.c.421) FastCGI-stderr: PHP message: PHP Fatal error: Class 'Doctrine\DBAL\Platforms\AbstractPlatform' not found in /srv/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Platforms/MySqlPlatform.php on line 553- Device info
Device Turris Omnia
Turris OS version 5.0.0
Turris OS branch hbs
Kernel version 4.14.1804 - Nextcloud version
nextcloud - 16.0.9-1.1
5 - System log (filtering mysqld service)
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] /usr/sbin/mysqld (mysqld 10.4.12-MariaDB) starting as process 6627 ...
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Warning] Could not increase number of max_open_files to more than 1024 (request: 4184)
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Warning] Changed limits: max_open_files: 1024 max_connections: 151 (was 151) table_cache: 421 (was 2000)
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] InnoDB: Using Linux native AIO
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] InnoDB: Uses event mutexes
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] InnoDB: Number of pools: 1
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] InnoDB: Using generic crc32 instructions
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [ERROR] InnoDB: Linux Native AIO interface is not supported on this platform. Please check your OS documentation and install appropriate binary of InnoDB.
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Warning] InnoDB: Linux Native AIO disabled.
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] InnoDB: Initializing buffer pool, total size = 64M, instances = 1, chunk size = 64M
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] InnoDB: Completed initialization of buffer pool
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Jun 4 19:22:05 turris mysqld[6627]: 2020-06-04 16:22:05 0 [Note] InnoDB: The log sequence number 7278155872 in the system tablespace does not match the log sequence number 7278155881 in the ib_logfiles!
Jun 4 19:22:08 turris mysqld[6627]: 2020-06-04 16:22:08 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
Jun 4 19:22:08 turris mysqld[6627]: 2020-06-04 16:22:08 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Jun 4 19:22:08 turris mysqld[6627]: 2020-06-04 16:22:08 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Jun 4 19:22:08 turris mysqld[6627]: 2020-06-04 16:22:08 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Jun 4 19:22:18 turris mysqld[6627]: 2020-06-04 16:22:18 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Jun 4 19:22:18 turris mysqld[6627]: 2020-06-04 16:22:18 0 [Note] InnoDB: Waiting for purge to start
Jun 4 19:22:18 turris mysqld[6627]: 2020-06-04 16:22:18 0 [Note] InnoDB: 10.4.12 started; log sequence number 7278155881; transaction id 1933606
Jun 4 19:22:18 turris mysqld[6627]: 2020-06-04 16:22:18 0 [Note] InnoDB: Loading buffer pool(s) from /srv/mysql/ib_buffer_pool
Jun 4 19:22:18 turris mysqld[6627]: 2020-06-04 16:22:18 0 [Note] Server socket created on IP: '127.0.0.1'.
Jun 4 19:22:19 turris mysqld[6627]: 2020-06-04 16:22:19 0 [Warning] 'user' entry 'root@turris' ignored in --skip-name-resolve mode.
Jun 4 19:22:19 turris mysqld[6627]: 2020-06-04 16:22:19 0 [Warning] 'proxies_priv' entry '@% root@turris' ignored in --skip-name-resolve mode.
Jun 4 19:22:20 turris mysqld[6627]: 2020-06-04 16:22:20 0 [Note] Reading of all Master_info entries succeeded
Jun 4 19:22:20 turris mysqld[6627]: 2020-06-04 16:22:20 0 [Note] Added new Master_info '' to hash table
Jun 4 19:22:20 turris mysqld[6627]: 2020-06-04 16:22:20 0 [Note] /usr/sbin/mysqld: ready for connections.
Jun 4 19:22:20 turris mysqld[6627]: Version: '10.4.12-MariaDB' socket: '/var/run/mysql/mysql.sock' port: 3306 Source distribution
Jun 4 19:22:32 turris mysqld[6627]: 2020-06-04 16:22:32 0 [Note] InnoDB: Buffer pool(s) load completed at 200604 16:22:32Alright, thanks for the hint. I wrote to the support email and included dmesg/network config file/installed packages as instructed in the linked page.
What’s the thing about minidlna/gerbera? I still see both packages in TOS 5.
I can not seem to get the update to 5.0 to work.
After typing in pkgupdate, I get the following
INFO:Target Turris OS: 5.0.0
line not found
line not found
line not found
line not found
line not found
line not found
ERROR:
inconsistent: Package acme requires package wget-ssl that is not available.
opkg install wget-ssl
Upgrading wget on root from 1.19.5-4.0 to 1.20.3-4.0...
Downloading https://repo.turris.cz/hbs/turris1x/packages/packages/wget_1.20.3-4_powerpc_8540.ipk
Removing obsolete file /usr/bin/wget.
Configuring wget.
pkgupdate
And then I get the same error again… 
INFO:Target Turris OS: 5.0.0
line not found
line not found
line not found
line not found
line not found
line not found
ERROR:
inconsistent: Package acme requires package wget-ssl that is not available.Some of our users reported issues in MiniDLNA. It looks like mostly as an upstream bug, which is not maintained so much. Those packages come from upstream and gerbera might seems like a good replacement opinion.
This one is working to me.
root@turris:~# opkg install wget-ssl
Installing wget (1.20.3-4.0) to root...
Downloading https://repo.turris.cz/hbk/omnia/packages/packages/wget_1.20.3-4_arm_cortex-a9_vfpv3-d16.ipk
Configuring wget.
root@turris:~# opkg install acme
Installing acme (2.8.5-2.3) to root...
Downloading https://repo.turris.cz/hbk/omnia/packages/packages/acme_2.8.5-2_all.ipk
Configuring acme.
root@turris:~# pkgupdate
INFO:Target Turris OS: 5.0.0
WARN:Package wpad is in cyclic dependency. It might fail its post-install script.
WARN:Package hostapd is in cyclic dependency. It might fail its post-install script.
WARN:Requested package foris-storage-plugin-l10n-de that is missing, ignoring as requested.However, I see it downloads a package for Turris 1.x (powerpc_8540) is that right in your case? Didn’t you have Turris Omnia or Turris MOX router?
root@turris:~# opkg install acme
Installing acme (2.8.5-2.6) to root...
Downloading https://repo.turris.cz/hbl/turris1x/packages/packages/acme_2.8.5-2_all.ipk
Installing wget (1.20.3-4.0) to root...
Downloading https://repo.turris.cz/hbl/turris1x/packages/packages/wget_1.20.3-4_powerpc_8540.ipk
Configuring wget.
Configuring acme.We will look at it more, but can you please remove acme for now until we look at it further and install it once you finished an upgrade to Turris OS 5.0?
If you have two MOXes with two broken wi-fi and inaccessible Foris, report to technical support is really best solution.
