[Bug 731876] New: syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

bugzilla_noreply＠novell.com

21 Nov 2011 21 Nov '11

23:53

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c0 Summary: syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: arun@gmx.de QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 After changing all repos to 12.1/current and running "zypper dup" (Tumbleweed +packman-tumbleweed enabled), syslog-ng is not started. Running syslog-ng by hand starts it with these two error messages: Plugin module not found in 'module-path'; module-path='/lib64/syslog-ng:/usr/lib64/syslog-ng', module='afsql' Error managing capability set, cap_set_proc returned an error; caps='= cap_syslog+ep cap_chown,cap_dac_override,cap_fowner,cap_net_bind_service+p cap_dac_read_search+e', error='Operation not permitted (1)' Using systemctl works to after the reboot, here is some information from it: ape:/lib/systemd # systemctl |grep syslog syslog.service loaded failed failed System Logging Service syslog.socket loaded active running Syslog Socket syslog.target loaded active active Syslog ape:/lib/systemd # systemctl status syslog.service syslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/syslog.service; enabled) Active: failed since Mon, 21 Nov 2011 14:44:35 -0800; 1h 3min ago Process: 1099 ExecStart=/sbin/syslog-ng (code=exited, status=2) Process: 1097 ExecStartPre=/var/run/syslog-ng/addsockets (code=exited, status=0/SUCCESS) Process: 1033 ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/syslog.service ape:/lib/systemd # systemctl start syslog.service ape:/lib/systemd # systemctl status syslog.service syslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/syslog.service; enabled) Active: active (running) since Mon, 21 Nov 2011 15:48:49 -0800; 2s ago Process: 7380 ExecStart=/sbin/syslog-ng (code=exited, status=0/SUCCESS) Process: 7378 ExecStartPre=/var/run/syslog-ng/addsockets (code=exited, status=0/SUCCESS) Process: 7375 ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service (code=exited, status=0/SUCCESS) Main PID: 7382 (syslog-ng) CGroup: name=systemd:/system/syslog.service ├ 7381 supervising syslog-ng └ 7382 /sbin/syslog-ng Reproducible: Always Steps to Reproduce: 1. boot 2. syslog-ng doesn't start 3. happy to supply more information (logs, etc) if needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

4 Dec 4 Dec

13:23

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c1 Carsten Koch-Mauthe changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ckm@vienenbox.de --- Comment #1 from Carsten Koch-Mauthe 2011-12-04 13:23:32 UTC --- Same problem here. syslog-ng fails on systemstart but can be started later if systems running. Found it probably related to the source entry in syslog.ng.conf source src { # # include internal syslog-ng messages # note: the internal() soure is required! # internal(); # # read kernel messages directly (12.x) or # does klogd forward them via /dev/log? # file ("/proc/kmsg" program_override("kernel")); # # the following line will be replaced by the # socket list generated by SuSEconfig using # variables from /etc/sysconfig/syslog: # unix-dgram("/dev/log"); # # uncomment to process log messages from network: # udp(ip("192.168.0.100") port(514)); }; I've activated syslog on specific network interface. It seems systemd will start syslog-ng to early, when network is not completely ready. I've changed /lib/systemd/system/syslog.service and added network.target in Requires and After and since then it is working. Strange thing is that network.target is already included in includefile /run/systemd/syslog.core but probably systemd will not consider this entries. ==== # /lib/systemd/system/syslog.service # # This file is part of package klogd. # # Copyright (c) 2011 SuSE LINUX Products GmbH, Germany. # Author: Werner Fink # Please send feedback to http://www.suse.de/feedback # # Description: # # Used to start one of the System Logging Service daemons # depending on the configuration found in /etc/sysconfig/syslog. # [Unit] Description=System Logging Service Requires=var-run.mount syslog.target network.target After=var-run.mount network.target Before=syslog.target OnFailure=systemd-kmsg-syslogd.service Conflicts=syslog-ng.service rsyslog.service # # Now systemd include the further dependency rules and # Service section. This include will be automatically # updated depending on the configuration. # include /run/systemd/syslog.core [Install] WantedBy=multi-user.target === Other thing is the missing afsql modul. syslog-ng --version shows === syslog-ng --version syslog-ng 3.3.1 Installer-Version: 3.3.1 Revision: ssh+git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline--3.3#master#3a736e62b27f7036ab23b91cf0839a95d0185e18 Default-Modules: affile,afprog,afsocket,afuser,basicfuncs,csvparser,dbparser,syslogformat,afsql Available-Modules: afprog,afuser,csvparser,dummy,afsocket,basicfuncs,convertfuncs,syslogformat,dbparser,confgen,affile,afmongodb Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-Linux-Caps: on Enable-Pcre: on === so it is compiled with afsql as default modul but this modul is not available. :-( I've changed /etc/sysconfig/syslog and changed the syslog-ng parameters. === SYSLOG_NG_PARAMS="--default-modules=afprog,afuser,csvparser,dummy,afsocket,basicfuncs,convertfuncs,syslogformat,dbparser,affile,afmongodb" === Take care not to add the available modul confgen. This results here in a segmentation fault on starting syslog-ng. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

9 Dec 9 Dec

01:12

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c2 --- Comment #2 from Arun Persaud 2011-12-09 01:12:31 UTC --- Adding the network.target is most likely the solution for my problems too, since I'm also logging to another server. Can't reboot right now, but will give this a try and report back. Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13 Dec 13 Dec

10:19

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c zj jia changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@suse.com AssignedTo|bnc-team-screening@forge.pr |mt@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17 Dec 17 Dec

00:36

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c3 --- Comment #3 from Arun Persaud 2011-12-17 00:36:13 UTC --- I tried adding network.target to Requires and After in /lib/systemd/system/syslog.service as recommended in comment #2, but it didn't help :( I now get: ape:~ # systemctl status syslog.service syslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/syslog.service; enabled) Active: inactive (dead) CGroup: name=systemd:/system/syslog.service By mistake I only added it to Requires and not to After first, also no success. "systemctl start syslog.service" still starts the syslog service though once I'm logged into my Desktop. This works with or without the modification from comment #2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

4 Jan 4 Jan

11:26

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c4 peter czanik changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pczanik@genesi-usa.com --- Comment #4 from peter czanik 2012-01-04 11:26:01 UTC ---

...

Other thing is the missing afsql modul. syslog-ng --version shows === syslog-ng --version syslog-ng 3.3.1 Installer-Version: 3.3.1 Revision: ssh+git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline--3.3#master#3a736e62b27f7036ab23b91cf0839a95d0185e18 Default-Modules: affile,afprog,afsocket,afuser,basicfuncs,csvparser,dbparser,syslogformat,afsql Available-Modules: afprog,afuser,csvparser,dummy,afsocket,basicfuncs,convertfuncs,syslogformat,dbparser,confgen,affile,afmongodb Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-Linux-Caps: on Enable-Pcre: on === so it is compiled with afsql as default modul but this modul is not available. :-(

It is available, but in a separate package, so it does not introduce a new dependency (libdbi and database libraries), where database access is not used.

...

I've changed /etc/sysconfig/syslog and changed the syslog-ng parameters. === SYSLOG_NG_PARAMS="--default-modules=afprog,afuser,csvparser,dummy,afsocket,basicfuncs,convertfuncs,syslogformat,dbparser,affile,afmongodb" === Take care not to add the available modul confgen. This results here in a segmentation fault on starting syslog-ng.

My syslog-ng 3.3 package is available at https://build.opensuse.org/package/show?package=libevtlog&project=home%3Aczanik%3Asyslog-ng33 , now I added Tumbleweed to the list of targets. It removes the afsql warning, without needing to edit /etc/sysconfig/syslog (added a configure parameter). There was also a capability related message: it's coming from AppArmor. It's ugly, but still works fine. I try to investigate this, but audit.log does not show anything... CzP/syslog-ng upstream -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

5 Jan 5 Jan

08:54

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c5 --- Comment #5 from peter czanik 2012-01-05 08:54:22 UTC --- FYI: For the capability problem, the following line needs to be added to Apparmor ( /etc/apparmor.d/sbin.syslog-ng ): capability dac_read_search, Will open a separate bug for it... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:32

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c6 --- Comment #6 from Carsten Koch-Mauthe 2012-01-05 09:32:26 UTC --- Good to hear this afsql behavior is changed. There is another problem with syslog-ng. On reload (log_rotate) there are many internal-error entries. === Dec 31 03:00:07 master syslog-ng[2386]: Internal error, duplicate configuration elements refer to the same persistent config; name='.... . . . === This seems to be fixed in syslog-ng 3.3.3 according to the balabit changelog === 3.3.2 Sat, 12 Nov 2011 20:48:53 +0100 Bugfixes: ========= . . . * Fixed an "internal error duplicate config element" error during reload due to an invalid bugfix applied for 3.3.1. Older beta versions of 3.3 were not affected. === Is the automatically fixed also in your package or should i open a separate bug for this ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:07

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c7 --- Comment #7 from peter czanik 2012-01-05 11:07:40 UTC --- It should be fixed in 3.3.3, at least I never noticed this message in my logs :) I plan to wait for 3.3.4, and then to push it to Factory, and if possible also as an update for 12.1, as it has many bugfixes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

9 Jan 9 Jan

17:13

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c8 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse-beta@cboltz.de --- Comment #8 from Christian Boltz 2012-01-09 18:13:33 CET --- (In reply to comment #5)

...

FYI: For the capability problem, the following line needs to be added to Apparmor ( /etc/apparmor.d/sbin.syslog-ng ):

capability dac_read_search,

Will open a separate bug for it...

Too late! ;-) I already fixed it upstream, the fix will be in AppArmor 2.7.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

1 Feb 1 Feb

23:00

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c9 --- Comment #9 from Bernhard Wiedemann 2012-02-02 00:00:17 CET --- This is an autogenerated message for OBS integration: This bug (731876) was mentioned in https://build.opensuse.org/request/show/102427 Factory / apparmor -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

2 Feb 2 Feb

10:00

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c10 --- Comment #10 from Bernhard Wiedemann 2012-02-02 11:00:17 CET --- This is an autogenerated message for OBS integration: This bug (731876) was mentioned in https://build.opensuse.org/request/show/102458 Factory / apparmor -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

7 Feb 7 Feb

16:00

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c11 --- Comment #11 from Bernhard Wiedemann 2012-02-07 17:00:13 CET --- This is an autogenerated message for OBS integration: This bug (731876) was mentioned in https://build.opensuse.org/request/show/103067 12.1 / apparmor -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

22 Feb 22 Feb

10:51

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c12 Benjamin Brunner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #12 from Benjamin Brunner 2012-02-22 11:51:50 CET --- Update released for 12.1. I'll close the bug as resolved fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

5 Mar 5 Mar

03:44

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c13 --- Comment #13 from Arun Persaud 2012-03-05 03:44:55 UTC --- Hi just tried it again and the problem is still there: syslog-ng doesn't start, but I don't get any error messages now. Here are some messages after a clean reboot (running zypper ref and zypper up beforehand, with 12.1 + tumbleweed). ape:~ # systemctl status syslog.service syslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/syslog.service; enabled) Active: inactive (dead) CGroup: name=systemd:/system/syslog.service ape:~ # ps aux |grep syslog root 425 0.0 0.0 17268 696 ? Ss 19:25 0:00 /lib/systemd/systemd-kmsg-syslogd root 622 0.1 0.0 18824 912 ? Ss 19:26 0:00 /lib/systemd/systemd-stdout-syslog-bridge arun 5187 0.1 0.0 561520 6156 ? Sl 19:27 0:00 /usr/bin/pulseaudio --start --log-target=syslog root 5486 0.0 0.0 6792 868 pts/0 S+ 19:28 0:00 grep --color=auto syslog ape:~ # systemctl restart syslog.service ape:~ # systemctl status syslog.service syslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/syslog.service; enabled) Active: active (running) since Sun, 04 Mar 2012 19:28:48 -0800; 8s ago Process: 5532 ExecStart=/sbin/syslog-ng (code=exited, status=0/SUCCESS) Process: 5530 ExecStartPre=/var/run/syslog-ng/addsockets (code=exited, status=0/SUCCESS) Process: 5527 ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service (code=exited, status=0/SUCCESS) Main PID: 5534 (syslog-ng) CGroup: name=systemd:/system/syslog.service ├ 5533 supervising syslog-ng └ 5534 /sbin/syslog-ng ape:~ # ps aux |grep syslog root 622 0.1 0.0 18824 912 ? Ss 19:26 0:00 /lib/systemd/systemd-stdout-syslog-bridge arun 5187 0.1 0.0 561520 6156 ? Sl 19:27 0:00 /usr/bin/pulseaudio --start --log-target=syslog root 5533 0.0 0.0 26612 640 ? S 19:28 0:00 supervising syslog-ng root 5534 0.1 0.0 501112 4100 ? Ss 19:28 0:00 /sbin/syslog-ng root 5656 0.0 0.0 6792 864 pts/0 S+ 19:29 0:00 grep --color=auto syslog not sure if this helps, but I also got the same problem for postfix.service (i.e. I need to restart by hand). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

27 Mar 27 Mar

00:16

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c14 Arun Persaud changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #14 from Arun Persaud 2012-03-27 00:16:06 UTC --- Hi still not working for me, so I try to reopen it. Arun -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

26 Jul 26 Jul

19:42

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c15 --- Comment #15 from Arun Persaud 2012-07-26 19:42:08 UTC --- Still need to restart syslog and postfix by hand every time I reboot. Is there anything I can do/post that could help figuring out what the problem is? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

5 Sep 5 Sep

22:21

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c16 --- Comment #16 from Arun Persaud 2012-09-05 22:21:50 UTC --- Just fyi: updated to 12.2 and the problem went away. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17 Sep 17 Sep

12:22

New subject: [Bug 731876] syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

https://bugzilla.novell.com/show_bug.cgi?id=731876 https://bugzilla.novell.com/show_bug.cgi?id=731876#c17 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #17 from Marius Tomaschewski 2012-09-17 12:22:05 UTC --- There was something broken in your system / configuration / deps I think. Closing it as FIXED again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

4246

Age (days ago)

4547

Last active (days ago)

List overview

Download

18 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 731876] New: syslog-ng doesn't start automatically at boot after updating Tumbleweed base from 11.4 to 12.1

tags

participants (1)