Turris OS 4.0 alpha5 is released!

release

#21

Mine looks a little bit different

  lxc-start Debian 20190414115919.277 ERROR    lxc_conf - conf.c:run_buffer:438 - Script exited with status 127.
  lxc-start Debian 20190414115919.345 ERROR    lxc_network - network.c:lxc_create_network_priv:2402 - Failed to create network device
  lxc-start Debian 20190414115919.345 ERROR    lxc_start - start.c:lxc_spawn:1206 - Failed to create the network.
  lxc-start Debian 20190414115919.345 ERROR    lxc_start - start.c:__lxc_start:1459 - Failed to spawn container "Debian".
  lxc-start Debian 20190414115919.346 ERROR    lxc_container - lxccontainer.c:wait_on_daemonized_start:760 - Received container state "STOPPING" instead of "RUNNING"
  lxc-start Debian 20190414115919.346 ERROR    lxc_start_ui - tools/lxc_start.c:main:371 - The container failed to start.
  lxc-start Debian 20190414115919.346 ERROR    lxc_start_ui - tools/lxc_start.c:main:373 - To get more details, run the container in foreground mode.
  lxc-start Debian 20190414115919.346 ERROR    lxc_start_ui - tools/lxc_start.c:main:375 - Additional information can be obtained by setting the --logfile and --logpriority options.

Full config file

lxc.arch = armv7l
lxc.tty = 4
lxc.pts = 1024
lxc.rootfs = /srv/lxc-debian
lxc.utsname = Debian
lxc.network.type = veth
lxc.network.link = br-lan
lxc.network.flags = up
lxc.network.name = eth0
lxc.network.script.up = /usr/share/lxc/hooks/tx-off
lxc.network.hwaddr = 92:d7:d5:2f:47:e0
lxc.cgroup.devices.allow = c 188:* rwm
lxc.mount.entry = /dev/bus/usb/001 dev/bus/usb/001 none bind,optional,create=dir 0 0
lxc.mount.entry = /dev/bus/usb/002 dev/bus/usb/002 none bind,optional,create=dir 0 0
lxc.mount.entry = /dev/bus/usb/003 dev/bus/usb/003 none bind,optional,create=dir 0 0
lxc.mount.entry = /dev/bus/usb/004 dev/bus/usb/004 none bind,optional,create=dir 0 0
lxc.mount.entry = /dev/ttyUSB0 dev/ttyUSB0  none bind,optional,create=file 0 0

It’s Debian Strech, installed about 1.5 year ago.


#22

Did you run lxc-checkconfig? It seems being a kernel issue (aside from the outdated lxc packages from OpenWRT that are being polled in the TOS4.x branch).


#23

Any chance you will be looking into adding a newer version of mariadb to the 4.0-alpha series?

I’ve switched from the 3.11-series with the intent of keeping the content of my nextcloud installation, and while I am aware that such an upgrade is unsupported, it is harder than I expected as I was hoping it would only be a question of migrating configuration files and such. The 4.0-alpha series has version 10.1.37 of the mariadb-packages, but the 3.11-series is currently at 10.2.18, and version 10.1.37 apparently does not support downgrading the database files from a newer version than 10.2.2. So I sort of ran into a brick wall there.


#24

That is a bit strange since OpenWRT’s current branch (where most of the TOS 4.x branch packages are curated/maintained) is at v 10.1.38 and should logicically be matching the HBS 4.x repo.

The dev/master branch is already at v 10.2.22 and it does not seem likely it being backported to the current branch. However, you could open a request at OpenWRT.


Thus far it is not clear which package will be curated/maintained by TO in the TOS branch and which are being fed from upstream OpenWRT.

With TOS4.x there will probably a shift in the way of requesting package updates and it would be good of the TO team to clarify on the subject.


#25

Any chance you will be looking into adding a newer version of mariadb to the 4.0-alpha series?

Yes, I will update it and send the pull request to OpenWrt. We will see how it goes.


#26

It’s just a minor version of the libmariadb, but I understand what you mean. If you’re interested why we decided to maintain by us (in TOS packages) libmariadb, that’s can be found in some of pull request in OpenWrt.

Thus far it is not clear which package will be curated/maintained by TO in the TOS branch and which are being fed from upstream OpenWRT.

Our Turris OS packages feed is preferred than OpenWrt packages feed. Packages, which we maintain for Turris OS 4.x and Turris OS 5.x can be found in turris-os-packages repository in branch master. Some of the packages are already in upstream, where these days we commit there a lot than in past, but for now, they’re not removed from our feed, because new packages won’t be accepted to OpenWrt 18.xx. The best way will be to backport those packages as a patch and include them in turris-build and remove them from our turris-os-packages feed. However, we will send more packages to OpenWrt, which we maintain and they’re no in OpenWrt. That’s on my TO-DO list.

But that’s not all. We have also patches as I mention and they can be found in turris-build and there is branch master (for OpenWrt master) and v4.0 (currently for OpenWrt 18.xx).

(aside from the outdated lxc packages from OpenWRT that are being polled in the TOS4.x branch).

You need to complain about it to upstream. They should will need take care of it. However, from you, I read this message about outdated LXC packages a lot in Turris OS 4.x. We’re not maintainers of the package. We said to you 2 months ago this one:


It still same. Nothing has changed since than.


#27

Nothing has changed in my setup.
I’m getting several times a day errors like below. Once This happens, the Wifi stays connected on the iPhone but I can’t open any address.

System Log

Apr 18 18:13:31 turris hostapd: wlan0: STA 78:XX:XX:XX:XX:XX IEEE 802.11: authenticated
Apr 18 18:13:31 turris hostapd: wlan0: STA 78:XX:XX:XX:XX:XX IEEE 802.11: associated (aid 6)
Apr 18 18:13:31 turris hostapd: wlan0: AP-STA-CONNECTED 78:XX:XX:XX:XX:XX
Apr 18 18:13:31 turris hostapd: wlan0: STA 78:XX:XX:XX:XX:XX RADIUS: starting accounting session 4802D218D134FFD8
Apr 18 18:13:31 turris hostapd: wlan0: STA 78:XX:XX:XX:XX:XX WPA: pairwise key handshake completed (RSN)
Apr 18 20:13:31 turris kernel: [1115851.569738] ath10k_pci 0000:02:00.0: dropping dbg buffer due to crash since read
Apr 18 20:13:32 turris kernel: [1115852.569746] ath10k_pci 0000:02:00.0: dropping dbg buffer due to crash since read
Apr 18 18:14:01 turris /usr/sbin/cron[18196]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
Apr 18 18:14:21 turris hostapd: wlan0: AP-STA-DISCONNECTED 78:XX:XX:XX:XX:XX
Apr 18 18:14:21 turris hostapd: wlan0: STA 78:XX:XX:XX:XX:XX IEEE 802.11: disassociated
Apr 18 20:14:21 turris kernel: [1115901.570786] ath10k_pci 0000:02:00.0: dropping dbg buffer due to crash since read


#28

Today I tried 4.0a5 and I cannot pass the Foris Guide “Region and Time”.
Any region I choose, it will crash after click on save.

An unexpected error has occurred
Remote Exception: Internal error ['uci', '-c', '/etc/config/', '-P', '/tmp/.uci-foris-controller', 'set', 'system.ntp.enabled=1']: command failed (b'uci: Invalid argument\n')('<class 'foris_controller.exceptions.UciException'>')
Remote request

{"module": "time", "action": "update_settings", "kind": "request", "data": {"city": "Prague", "country": "CZ", "region": "Europe", "timezone": "CET-1CEST,M3.5.0,M10.5.0/3", "time_settings": {"how_to_set_time": "ntp"}}}

Stack trace

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/foris_controller/message_router.py", line 117, in process_message
    data = module_instance.perform_action(message["action"], message.get("data", {}))
  File "/usr/lib/python3.6/site-packages/foris_controller/module_base.py", line 59, in perform_action
    res = action_function(data)
  File "/usr/lib/python3.6/site-packages/foris_controller_modules/time/__init__.py", line 59, in action_update_settings
    time,
  File "/usr/lib/python3.6/site-packages/foris_controller/utils.py", line 112, in inner
    res = func(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/foris_controller_modules/time/handlers/openwrt.py", line 67, in update_settings
    return self.uci.update_settings(region, country, city, timezone, how_to_set_time, time)
  File "/usr/lib/python3.6/site-packages/foris_controller_backends/time/__init__.py", line 102, in update_settings
    backend.set_option("system", "ntp", "enabled", store_bool(how_to_set_time == "ntp"))
  File "/usr/lib/python3.6/site-packages/foris_controller_backends/uci/__init__.py", line 200, in set_option
    self._run_uci_command("set", "%s.%s.%s=%s" % (config, section_name, option_name, value))
  File "/usr/lib/python3.6/site-packages/foris_controller_backends/uci/__init__.py", line 173, in _run_uci_command
    raise UciException(cmdline_args, stderr)
foris_controller.exceptions.UciException: ['uci', '-c', '/etc/config/', '-P', '/tmp/.uci-foris-controller', 'set', 'system.ntp.enabled=1']: command failed (b'uci: Invalid argument\n')

Environment

{'CONTENT_LENGTH': '126',
 'CONTENT_TYPE': 'application/x-www-form-urlencoded',
 'DOCUMENT_ROOT': '/www',
 'GATEWAY_INTERFACE': 'CGI/1.1',
 'HTTP_ACCEPT': 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
 'HTTP_ACCEPT_ENCODING': 'gzip, deflate',
 'HTTP_ACCEPT_LANGUAGE': 'en-US,en;q=0.5',
 'HTTP_CONNECTION': 'keep-alive',
 'HTTP_CONTENT_LENGTH': '126',
 'HTTP_COOKIE': 'foris.session=b2acd413ced85acf2a430cc7f9cded09; '
                'foris.ws.session=3506fda0179dd94606924e8ef31b5c29',
 'HTTP_DNT': '1',
 'HTTP_HOST': '192.168.1.1',
 'HTTP_REFERER': 'http://192.168.1.1/foris/config/main/time/',
 'HTTP_UPGRADE_INSECURE_REQUESTS': '1',
 'HTTP_USER_AGENT': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) '
                    'Gecko/20100101 Firefox/66.0',
 'PATH_INFO': '/main/time/',
 'PATH_TRANSLATED': '/www/main/time/',
 'QUERY_STRING': '',
 'REDIRECT_STATUS': '200',
 'REMOTE_ADDR': '192.168.1.2',
 'REMOTE_PORT': '62450',
 'REQUEST_METHOD': 'POST',
 'REQUEST_SCHEME': 'http',
 'REQUEST_URI': '/foris/config/main/time/',
 'SCRIPT_FILENAME': '/www/foris/config',
 'SCRIPT_NAME': '/foris/config',
 'SERVER_ADDR': '192.168.1.1',
 'SERVER_NAME': '192.168.1.1',
 'SERVER_PORT': '80',
 'SERVER_PROTOCOL': 'HTTP/1.1',
 'SERVER_SOFTWARE': 'lighttpd/1.4.50',
 'bottle.app': <bottle.Bottle object at 0x1148790>,
 'bottle.raw_path': '/time/',
 'bottle.request': <LocalRequest: POST http://192.168.1.1/foris/config/main/time/>,
 'bottle.request.body': <_io.BytesIO object at 0x1363890>,
 'bottle.request.headers': <bottle.WSGIHeaderDict object at 0x12d7de0>,
 'bottle.request.post': {'country': 'CZ',
                         'csrf_token': 'LPi6xLoyJk20yj6EvNb9LKaBgteqWSJK',
                         'region': 'Europe',
                         'send': '',
                         'zonename': 'Europe/Prague'},
 'bottle.request.urlparts': SplitResult(scheme='http', netloc='192.168.1.1', path='/foris/config/main/time/', query='', fragment=''),
 'bottle.route': <POST '/<page_name:re:.+>/' <function config_page_post at 0x1160e30>>,
 'foris.backend': MqttSender('localhost:11883'),
 'foris.language': 'en',
 'foris.session': <foris.middleware.sessions.SessionForisProxy object at 0x1360aa0>,
 'foris.session.data': {'_messages': [],
                        'csrf_token': 'LPi6xLoyJk20yj6EvNb9LKaBgteqWSJK',
                        'user_authenticated': True},
 'foris.session.id': 'b2acd413ced85acf2a430cc7f9cded09',
 'foris.version': '99.7.5',
 'route.handle': <POST '/<page_name:re:.+>/' <function config_page_post at 0x1160e30>>,
 'route.url_args': {'page_name': 'time'},
 'wsgi.errors': <flup.server.fcgi_base.OutputStream object at 0x1361680>,
 'wsgi.input': <_io.BytesIO object at 0x1363890>,
 'wsgi.multiprocess': False,
 'wsgi.multithread': True,
 'wsgi.run_once': False,
 'wsgi.url_scheme': 'http',
 'wsgi.version': (1, 0)}

Another Foris bug is on “Network interfaces”. After several fast click on any lan icon the gui gets a bit broken:


And when u press exit button, it gets worse :wink:


#29

Probably I found the solution. It is stable for 2 days now. By default OpenWRT is using the package “ath10k-firmware-qca988x-ct”. This firmware is modified from vendors version. I install “ath10k-firmware-qca988x”, uninstalled “ath10k-firmware-qca988x-ct” and rebooted the router.


#30

I’m glad that you have been able to find solution in your case. In the upcoming version of Turris OS 4.0, we have decided to change the Wi-Fi driver from Candela Tech drivers to standard ath10k drivers.


#31

When do you plan to release the next alpha release?


#32

We’re preparing a new release, which we would like to release soon. Will it be OK for you when it is released this week? :wink:


#33

Perfect. Thank you :+1:


#34

Second attempt to 4.0 alpha 5.

Mysql module for looks ok (php-cli -m reports that mysqlnd is loaded).
Loading php-mysqlnd requires php-openssl and libmariadbclient.

LXC does not work at all (or I’m unable to start one).
Container copied from 3.11.4 does not start: network device issues.
So I tried to run new one with Debian Buster.
Container starts (with network not configured yet), but lxc-attach fails.

Anyone was able to run existing container, or at least new one?