So mine rebooted every two minutes for about an hour and has since been stable. I donāt know what magic spells they use in this device but itās quite an achievement to produce such inconsistencies and randomness.
I can confirm that my Turris 1.0 also reboots randomly since the update. Several times today already. I just went to this forum for the first time in months just to see if this is a known issue.
I have a problem with the operation of LEDs for pci-e 1,2,3 Omnia Turris after restart, does not shine - just as I go to the āSystemā -> āLED Configurationā> āSave & Applyā LEDs are beginning to work.
Same for me. /etc/rc.d/S99rainbow and S99setup_led are probably too close in time. So I added sleep 3 into start() section of S99setup_led to give more time for rainbow and now itās working for me.
The System Log on my TO with 3.8 firmware is full of following error mesagges
2017-09-18T17:15:04+02:00 err nikola: (v42) Exception thrown: failed to get serial number - Communication crashed due to bad status code from ATSHA204 device. Please, use verbose mode for more information.
2017-09-18T17:15:04+02:00 err nikola: (v42) Exception traceback: [(ā/usr/bin/nikolaā, 181, āā, 'server = WrappedServer(server_address, ssl_context=ssl_
This is some error with atsha. We are using it to verify router (so that is why data collection fails). In this case error is not too descriptive and basically means that something went wrong during communication with atsha. I would suggest reboot or even reset (reset button or short power disconnect) to try to erase state of chip and i2c bus.
I had the exact same problem and I didnāt touch any DHCP/DNS settings. Had to do full reset, no IP changes in wizard, disabled updates in wizard. Then I enabled updates manually and patched the DHCP config file manually.
Since 3.8 DDNS was missing (could be reinstalled) and my router is available from the Internet, regarding ssh and the normal interfaces for foris and Luciā¦ Why is that?
Well, for now I just want to say Thank You to Omnia Turris team for the big update. For anything else I rather look whether there is a different thread matching to topic or open a new one.
This is fine. For some reason Luci-ddns developers decided that they will do languages little bit differently and integrated English to their primary package. So our code for localization selection for luci in updater is also requesting this non-existent package. And I really canāt be bothered to add exception because one developed did it differently. Just ignore that warning. You have two you have already ignored.
I choose not to do a manual install, as you proposed, as I expected the 3.8.1 update to arrive fairly soon.
Now 3.8.1 was installed on my Turris yesterday and I can see the transmission-web was part of that update (at least it was listed in the mail).
However, when I now attempt to access the transmission web page, Iām now greeted with this 404 error:
Couldn't find Transmission's web interface files!
Users: to tell Transmission where to look, set the TRANSMISSION_WEB_HOME environment variable to the folder where the web interface's index.html is located.
Package Builders: to set a custom default at compile time, #define PACKAGE_DATA_DIR in libtransmission/platform.c or tweak tr_getClutchDir () by hand.
I had expected this would be working out of the box, as I didnāt have to deal with it the first time I installed transmission-web.
If I have to set the path manually, then whatās the path?
