Turris OS 4.0 beta8 is released!

Community office
,
21

beta 8 is working on my MOX including Foris

22

WAN Connection test OK
LAN Connection test OK
DNS Connection test OK

Notification update received
Test notification sent, message not received
Software restart failed

23

I do have exactly same problem with Foris, I already sent a ticket to tech.support.

24

In this version, there are some additional changes under the hood of foris-controller, but right now for some reason is not running for you.

May I ask if you if there is anything in messages? What would tell me, where I should look at it as I am still not able to reproduce it.
If there isn’t anything, can you please change the value in debug from 0 to 1 in a configuration file /etc/config/foris-controller? It will enable verbose logging, so once you gathered all the details, don’t forget to set it again to 0. and restart foris-controller

Then you need to restart init script of foris-controller.
That’s can be done via command:

/etc/init.d/foris-controller restart

When it is restarted, try to go to Foris web interface and once it crashes, there will be something in messages. I will appreciate if you can save it to some file or use something like pastebin and send it to me.

Also if you can generate diagnostics CLI and send it to me should be useful to reproduce this issue.

/usr/share/diagnostics/diagnostics.sh -o /tmp/diagnostics.txt && gzip /tmp/diagnostics.txt

It takes a while, but when they are generated you will see file diagnostics.txt.gz in folder /tmp. The diagnostics file will be removed after reboot as it is stored in RAM.

25

After update to TOS 4.0beta8 on a Turris Omnia I also have no access to the Foris interface. Luci works. I already had beta8 installed, and there Foris worked. I was offered the beta8 update on my Omnia again (due to MOX issues that were solved?), after that I can’t access Foris anymore.

Update: with schnapps I rolled back to beta 7 and ran the beta 8 update again, same problem accessing Foris afterwards. Went back to beta7 and will wait with update until issue is solved…

26

Sent diagnostics to tech.support, there is IPv4 import error in messages.

Aug 11 07:20:36 Turris foris-controller[8284]: Traceback (most recent call last):
Aug 11 07:20:36 Turris foris-controller[8284]: File “/usr/bin/foris-controller”, line 11, in
Aug 11 07:20:36 Turris foris-controller[8284]: load_entry_point(‘foris-controller==1.0.2’, ‘console_scripts’, ‘foris-controller’)()
Aug 11 07:20:36 Turris foris-controller[8284]: File “/main.py”, line 193, in main
Aug 11 07:20:36 Turris foris-controller[8284]: File “/app.py”, line 114, in prepare_app_modules
Aug 11 07:20:36 Turris foris-controller[8284]: File “/utils.py”, line 218, in get_handler
Aug 11 07:20:36 Turris foris-controller[8284]: File “/init.py”, line 126, in import_module
Aug 11 07:20:36 Turris foris-controller[8284]: File “”, line 994, in _gcd_import
Aug 11 07:20:36 Turris foris-controller[8284]: File “”, line 971, in _find_and_load
Aug 11 07:20:36 Turris foris-controller[8284]: File “”, line 941, in _find_and_load_unlocked
Aug 11 07:20:36 Turris foris-controller[8284]: File “”, line 219, in _call_with_frames_removed
Aug 11 07:20:36 Turris foris-controller[8284]: File “”, line 994, in _gcd_import
Aug 11 07:20:36 Turris foris-controller[8284]: File “”, line 971, in _find_and_load
Aug 11 07:20:36 Turris foris-controller[8284]: File “”, line 955, in _find_and_load_unlocked
Aug 11 07:20:36 Turris foris-controller[8284]: File “”, line 665, in _load_unlocked
Aug 11 07:20:36 Turris foris-controller[8284]: File “”, line 678, in exec_module
Aug 11 07:20:36 Turris foris-controller[8284]: File “”, line 219, in _call_with_frames_removed
Aug 11 07:20:36 Turris foris-controller[8284]: File “/init.py”, line 21, in
Aug 11 07:20:36 Turris foris-controller[8284]: File “/openwrt.py”, line 25, in
Aug 11 07:20:36 Turris foris-controller[8284]: File “/init.py”, line 32, in
Aug 11 07:20:36 Turris foris-controller[8284]: ImportError: cannot import name ‘IPv4’

27

Thanks for confirming. It’s the same issue as reported by @ivanek.

2 Likes
28

We have been able to reproduce it. We are working on fixing this issue.

2 Likes
29

I looked into it and found the culprit. Updated package is on the way, so please be patient.

3 Likes
30

Same issue. With the schnapps command I returned to the previous version and paused the updates. And now I waiting to repair.

31

Last week I upgraded my TO from Beta7 to Beta8 (TurrisOS 4.0-beta8 35a78e6 / LuCI branch (git-19.219.84181-0ec4dcb)). To my suprise i found yesterday in Foris a new/other version of Beta8 was ready to install (TurrisOS 4.0-beta8 d040b6a / LuCI branch (git-19.220.84181-cb4ddc0)).

Does anybody know what this is about?
Is this a MOX thing?

1 Like
32

Beta refreshed apparently after the M issue been sorted

33

This is newer beta 8 version then beta 8

34

Hello Guys,
After upgrading to beta 8 (MOX), Wifi shut down after some time of inactivity. Someone has the same experience?
Now I am waiting to fix the Foris problem and I will study the wifi problem via eth and ssh connectivity.