Turris OS 3.11.3 in RC

release

#1

Dear Turris users,

We just released Turris OS 3.11.3 in RC. It mostly contains security updates, some minor updates for packages and also bug fixes. Release notes are:

• openssh, zmq, keepalived: security updates
• tvheadend, mpc, youtube-dl, czmq, wireguard and various minor packages: update
• kernel: update
• logread: fix
• foris-pakon: fix for Safari

We welcome any feedback and testing.


made this a banner . It will appear at the top of every page until it is dismissed by the user. #2

#3

No problems noticed both before restart and after restart.


#4

The TurrisOS 3.11.3 RC1 was installed on my Turris 1.x and on my Turris Omnia too and everything works well.

There is only problem with ssbackup creating process to cloud backup!

Thanks to Turris team for hard work! :slight_smile:


#5

applied the update, and rebooted the omnia, and it works for me.


#6

TurrisOS 3.11.3 RC was installed on my Omnia, everything is working well. I have no issues to report. Great Job!


#7

Again, there’s some glitch that didn’t manifest right away: ssbackups:

# /usr/libexec/ssbackups.sh
Traceback (most recent call last):
  File "/usr/bin/foris-client", line 11, in <module>
    load_entry_point('foris-client==0.9.5', 'console_scripts', 'foris-client')()
  File "/usr/lib/python3.6/site-packages/foris_client/client/__main__.py", line 116, in main
    options.module, options.action, data, controller_id=options.controller_id)
AttributeError: 'Namespace' object has no attribute 'controller_id'

#8
##### Oznámení o chybách #####
Vytvoření automatické zálohy do cloudu z vašeho zařízení se nezdařilo.

#9

Have the same problem with cloud backup.


#10

The update process itself went without a hitch.

It appears that `syslog-ng` is not working

Error opening include file; filename=’/etc/syslog-ng.d/’, depth=‘1’
Include file/directory not found; filename=’/etc/syslog-ng.d/’, include-path=’/etc:/usr/share/syslog-ng/include’, error=‘Invalid argument (22)’
Error parsing pragma, Error including /etc/syslog-ng.d/ in /etc/syslog-ng.conf:
5 # https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.16/release-notes/global-options
6
7 @version: 3.19
8 @include “scl.conf”
9 @include “/etc/syslog-ng.d/” # Put any customization files in this directory
10---->
10----> ^
11 options {
12 chain_hostnames(no); # Enable or disable the chained hostname format.
13 create_dirs(yes);
14 keep_hostname(yes); # Enable or disable hostname rewriting.
15 log_fifo_size(256); # The number of messages that the output queue can store.

Error parsing config, syntax error, unexpected LL_ERROR, expecting $end in /etc/syslog-ng.conf:
4 # More details about these settings can be found here:
5 # https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.16/release-notes/global-options
6
7 @version: 3.19
8 @include “scl.conf”
9-----> @include “/etc/syslog-ng.d/” # Put any customization files in this directory
9-----> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
10---->
11 options {
12 chain_hostnames(no); # Enable or disable the chained hostname format.
13 create_dirs(yes);
14 keep_hostname(yes); # Enable or disable hostname rewriting.


kernel log still showing

BTRFS: failed to read the system array on sda3
BTRFS: open_ctree failed


#11

Guys, thank you for bug report about Cloud backups. We’ll look into it!

Anyway, @n8v8r would you please restart your router or try to do following commands?

/etc/init.d/syslog-ng stop
/etc/init.d/syslog-ng start

#12

The update failed, and keep failing when trying to repeat it manually:

pkgupdate

INFO:Detected existing journal. Trying to recover it.
line not found
line not found
line not found
line not found
DIE:
[string “backend”]:1194: [string “backend”]:1185: Failed to lock the lock file //var/lock/opkg.lock: Resource temporarily unavailable
Aborted


#13

Done that but the outcome does not change. See the difference in outputs between 3.11.2 and 3.11.3 RC


3.11.2

ps | grep syslog-ng

2505 root 9076 S /usr/sbin/syslog-ng -F
3971 root 1112 R grep syslog-ng

ps | syslog-ng

WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.19 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file.;
WARNING: syslog-ng dropped support for POSIX regexp implementations in syslog-ng 3.14 in favour of PCRE, which should be upward compatible. All ‘posix’ regexps are automatically switched to ‘pcre’. Please ensure that your regexps work with PCRE and specify type(‘pcre’) explicitly or increase @version to remove this warning;


311.3 RC

ps | grep syslog-ng

5012 root 1112 S grep syslog-ng

ps | syslog-ng

Error opening include file; filename=’/etc/syslog-ng.d/’, depth=‘1’
Include file/directory not found; filename=’/etc/syslog-ng.d/’, include-path=’/etc:/usr/share/syslog-ng/include’, error=‘Invalid argument (22)’
Error parsing pragma, Error including /etc/syslog-ng.d/ in /etc/syslog-ng.conf:
5 # https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.16/release-notes/global-options
6
7 @version: 3.19
8 @include “scl.conf”
9 @include “/etc/syslog-ng.d/” # Put any customization files in this directory
10---->
10----> ^
11 options {
12 chain_hostnames(no); # Enable or disable the chained hostname format.
13 create_dirs(yes);
14 keep_hostname(yes); # Enable or disable hostname rewriting.
15 log_fifo_size(256); # The number of messages that the output queue can store.

Error parsing config, syntax error, unexpected LL_ERROR, expecting $end in /etc/syslog-ng.conf:
4 # More details about these settings can be found here:
5 # https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.16/release-notes/global-options
6
7 @version: 3.19
8 @include “scl.conf”
9-----> @include “/etc/syslog-ng.d/” # Put any customization files in this directory
9-----> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
10---->
11 options {
12 chain_hostnames(no); # Enable or disable the chained hostname format.
13 create_dirs(yes);
14 keep_hostname(yes); # Enable or disable hostname rewriting.


#14

Foris-Pakon: The display in the browser of IOS and macOS (Safari and Chrome) is not correct. You see a work of art …


#15

@n8v8r: My syslog works just fine…

# ll /etc/syslog-ng.d/
drwxr-xr-x    1 root     root            36 Jan 25 17:16 .
drwxr-xr-x    1 root     root          2084 Jan 27 14:56 ..
-rw-r--r--    1 root     root           274 Aug 20 21:19 ucollect-fake.conf

#16

What is the output of ps | syslog-ng?


From the error output

Include file/directory not found; filename=’/etc/syslog-ng.d/’

After the update to RC

ls /etc/syslog-ng.d/

ls: cannot access ‘/etc/syslog-ng.d/’: No such file or directory


ucollect is not present on the system, though I do not see a reason why that should make the difference.


#17

My output in 3.11.3 is the same as yours in 3.11.2… But anyways, what should this command do? It looks kinda suspicious to me…


#18

Can’t it be that /etc/syslog-ng.d isn’t created automatically, but on demand when some program (ucollect in my case) places a config file there?


#19

What do you find suspicious about it? It provides a process snapshot (ps) whilst initiating a startup of the specified process. Which is short and dirty way to assist with debugging startup issues. Alternatively and more sophisticated certainly is strace.


This commit changes the code base for syslog-ng between 3.11.2 and 3.11.3. I am sure the developer will figure out where it goes wrong.


#20

Are you sure it should be ps | and not ps && ? I still don’t get it - you take the output of ps and pipe it to the input of syslog-ng (which probably doesn’t read stdin at all)