[opensuse] Can't enable SuSEFirewall2 SystemD service
If I finish the YaST firewall setup I get: Attempt to `enable` service 'SuSEfirewall2' failed. ERROR: I am also unable to enable the SuSEfirewall2 service manually: systemctl enable SuSEfirewall2.service Failed to execute operation: Invalid argument Manual start works: # systemctl start SuSEfirewall2.service # systemctl status SuSEfirewall2.service SuSEfirewall2.service - SuSEfirewall2 phase 2 Loaded: loaded (/usr/lib/systemd/system/SuSEfirewall2.service; enabled) Active: active (exited) since Wed 2015-08-19 00:21:21 CEST; 5s ago Process: 23344 ExecStop=/usr/sbin/SuSEfirewall2 systemd_stop (code=exited, status=0/SUCCESS) Process: 23371 ExecStart=/usr/sbin/SuSEfirewall2 boot_setup (code=exited, status=0/SUCCESS) Main PID: 23371 (code=exited, status=0/SUCCESS) How can I get more details? "journalctl -n" shows nothing about the failed commands. Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
19.08.2015 01:24, Bjoern Voigt пишет:
If I finish the YaST firewall setup I get:
Attempt to `enable` service 'SuSEfirewall2' failed. ERROR:
I am also unable to enable the SuSEfirewall2 service manually:
systemctl enable SuSEfirewall2.service Failed to execute operation: Invalid argument
Manual start works:
# systemctl start SuSEfirewall2.service # systemctl status SuSEfirewall2.service SuSEfirewall2.service - SuSEfirewall2 phase 2 Loaded: loaded (/usr/lib/systemd/system/SuSEfirewall2.service; enabled) Active: active (exited) since Wed 2015-08-19 00:21:21 CEST; 5s ago Process: 23344 ExecStop=/usr/sbin/SuSEfirewall2 systemd_stop (code=exited, status=0/SUCCESS) Process: 23371 ExecStart=/usr/sbin/SuSEfirewall2 boot_setup (code=exited, status=0/SUCCESS) Main PID: 23371 (code=exited, status=0/SUCCESS)
How can I get more details? "journalctl -n" shows nothing about the failed commands.
According to output it is already enabled. I do not get this error in TW; you do not say which version you are running, may be older systemctl failed to enable already enabled unit. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
19.08.2015 01:24, Bjoern Voigt пишет:
If I finish the YaST firewall setup I get:
Attempt to `enable` service 'SuSEfirewall2' failed. ERROR:
I am also unable to enable the SuSEfirewall2 service manually:
systemctl enable SuSEfirewall2.service Failed to execute operation: Invalid argument
Manual start works:
# systemctl start SuSEfirewall2.service # systemctl status SuSEfirewall2.service SuSEfirewall2.service - SuSEfirewall2 phase 2 Loaded: loaded (/usr/lib/systemd/system/SuSEfirewall2.service; enabled) Active: active (exited) since Wed 2015-08-19 00:21:21 CEST; 5s ago Process: 23344 ExecStop=/usr/sbin/SuSEfirewall2 systemd_stop (code=exited, status=0/SUCCESS) Process: 23371 ExecStart=/usr/sbin/SuSEfirewall2 boot_setup (code=exited, status=0/SUCCESS) Main PID: 23371 (code=exited, status=0/SUCCESS)
How can I get more details? "journalctl -n" shows nothing about the failed commands.
According to output it is already enabled. I do not get this error in TW; you do not say which version you are running, may be older systemctl failed to enable already enabled unit.
Sorry, it's openSUSE 13.2 with all online updates. # systemctl --version systemd 210 +PAM -LIBWRAP +AUDIT +SELINUX -IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP +APPARMOR # rpm -qf /bin/systemctl systemd-210-25.16.1.x86_64 Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-08-19 00:24, Bjoern Voigt wrote:
systemctl enable SuSEfirewall2.service Failed to execute operation: Invalid argument
Do it with chkconfig. It will also fail, but it will tell you the syntax to attempt with insserv, and this one you can correct. It is a bug somewhere, I think chkconfig is using the wrong syntax. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXVLqMACgkQja8UbcUWM1z6KgD8D2xHDme5MQ1QFDEI4L2ZX77+ ZdcHED0L1BPNlorPBBYA/33va8cXa708NNy7XeZMUf1cDkdStdj6rab3/c5c2byo =Ahqt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-08-19 00:24, Bjoern Voigt wrote:
systemctl enable SuSEfirewall2.service Failed to execute operation: Invalid argument
Do it with chkconfig. It will also fail, but it will tell you the syntax to attempt with insserv, and this one you can correct. It is a bug somewhere, I think chkconfig is using the wrong syntax. Thanks for the hint. I still can't enable SuSEfirewall2. I also
Carlos E. R. wrote: tried to deactivate SuSEfirewall2.service first. # systemctl enable SuSEfirewall2.service Failed to execute operation: Invalid argument # chkconfig --add SuSEfirewall2 SuSEfirewall2: unknown service Note: This output shows SysV services only and does not include native systemd services. SysV configuration data might be overridden by native systemd configuration. If you want to list systemd services use 'systemctl list-unit-files'. To see services enabled on particular target use 'systemctl list-dependencies [target]'. # insserv SuSEfirewall2 Warning: /etc/init.d/SuSEfirewall2 is masked by /usr/lib/systemd/system/SuSEfirewall2.service. Try 'chkconfig SuSEfirewall2 on' instead can't open SuSEfirewall2: No such file or directory at /usr/sbin/insserv line 80. # chkconfig SuSEfirewall2 on Failed to execute operation: Invalid argument # systemctl disable SuSEfirewall2 # systemctl status SuSEfirewall2 SuSEfirewall2.service - SuSEfirewall2 phase 2 Loaded: loaded (/usr/lib/systemd/system/SuSEfirewall2.service; disabled) Active: active (exited) since Thu 2015-08-20 00:02:40 CEST; 1 day 12h ago Main PID: 9298 (code=exited, status=0/SUCCESS) CGroup: /system.slice/SuSEfirewall2.service # systemctl enable SuSEfirewall2 Failed to execute operation: Invalid argument Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-08-21 12:59, Bjoern Voigt wrote:
# insserv SuSEfirewall2
I'm unsure, but maybe you have to change directory to /etc/init.d Wait. There is no firewall script there. That's the problem. Must be another name. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
21.08.2015 15:53, Carlos E. R. пишет:
On 2015-08-21 12:59, Bjoern Voigt wrote:
# insserv SuSEfirewall2
I'm unsure, but maybe you have to change directory to /etc/init.d
Wait. There is no firewall script there. That's the problem. Must be another name.
in 13.2 SuSEfirewall2 is native systemd service, it does not have initscript. I just tested and systemctl enable SuSEfirewall2 works just fine, enabled or disabled previously. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-08-21 20:31, Andrei Borzenkov wrote:
21.08.2015 15:53, Carlos E. R. пишет:
On 2015-08-21 12:59, Bjoern Voigt wrote:
# insserv SuSEfirewall2
I'm unsure, but maybe you have to change directory to /etc/init.d
Wait. There is no firewall script there. That's the problem. Must be another name.
in 13.2 SuSEfirewall2 is native systemd service, it does not have initscript. I just tested and systemctl enable SuSEfirewall2 works just fine, enabled or disabled previously.
Yes, the same in 13.1. I noticed that later. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXa7DYACgkQja8UbcUWM1xxKAD9EtyRpTVSWvcT1Cqrm5/G8g+A TY8bQPBn0Mfd3Pvfd0sA/AiEll+5C30LWPl4iFO27OBZZ32nHBPy9410k7HldTb5 =juLQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Please change the subject line so that it doesn't say "systemd", or the automatic mail filters vetoes the post :-( On 2015-08-21 12:59, Bjoern Voigt wrote:
Carlos E. R. wrote:
# insserv SuSEfirewall2 Warning: /etc/init.d/SuSEfirewall2 is masked by /usr/lib/systemd/system/SuSEfirewall2.service. Try 'chkconfig SuSEfirewall2 on' instead can't open SuSEfirewall2: No such file or directory at /usr/sbin/insserv line 80.
I'm unsure, but maybe you have to change directory to /etc/init.d Wait. There is no firewall script there. That's the problem. Must be another name. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
Please change the subject line so that it doesn't say "systemd", or the automatic mail filters vetoes the post :-(
On 2015-08-21 12:59, Bjoern Voigt wrote:
Carlos E. R. wrote: # insserv SuSEfirewall2 Warning: /etc/init.d/SuSEfirewall2 is masked by /usr/lib/systemd/system/SuSEfirewall2.service. Try 'chkconfig SuSEfirewall2 on' instead can't open SuSEfirewall2: No such file or directory at /usr/sbin/insserv line 80.
I'm unsure, but maybe you have to change directory to /etc/init.d
Wait. There is no firewall script there. That's the problem. Must be another name. No, there isn't any SuSEfirewall2 script in /etc/init.d. systemctl seems to search /etc/init.d first and continues with /usr/lib/systemd/system. /usr/local/lib/systemd/system/SuSEfirewall2.service exists.
Here is an ltrace-excerpt: # ltrace -s 1000 -A 1000 systemctl enable SuSEfirewall2 [...] strlen("/etc/init.d") = 11 malloc(12) = 0x2249400 stpcpy(0x2249400, "/etc/init.d") = 0x224940b free(0x2249400) = <void> strlen("\n\t") = 2 strlen("/etc/init.d") = 11 malloc(12) = 0x2249400 stpcpy(0x2249400, "/etc/init.d") = 0x224940b free(0x2249400) = <void> strlen("SuSEfirewall2.service") = 21 strlen(".service") = 8 memcmp(0x22436dd, 0x4699ea, 8, 2538) = 0 __asprintf_chk(0x7ffcbbcb0408, 1, 0x468228, 0x2245300) = 41 access("/etc/systemd/system/SuSEfirewall2.service", 0) = -1 free(0x22452a0) = <void> __asprintf_chk(0x7ffcbbcb0408, 1, 0x468228, 0x2247320) = 41 access("/run/systemd/system/SuSEfirewall2.service", 0) = -1 free(0x22452a0) = <void> __asprintf_chk(0x7ffcbbcb0408, 1, 0x468228, 0x2245270) = 51 access("/usr/local/lib/systemd/system/SuSEfirewall2.service", 0) = -1 free(0x2249340) = <void> __asprintf_chk(0x7ffcbbcb0408, 1, 0x468228, 0x2248330) = 45 access("/usr/lib/systemd/system/SuSEfirewall2.service", 0) = 0 [...] memchr("ybnqiuxtdsogh", 's', 13) = 0x47952a memchr("org.freedesktop.DBus.Error.InvalidArgs", '\0', 38) = nil [...] memchr("ybnqiuxtdsogh", 's', 13) = 0x47952a memchr("Invalid argument", '\0', 16) = nil memmove(0x2245530, "", 0) = 0x2245530 __strdup("org.freedesktop.DBus.Error.InvalidArgs") = 0x2245580 __strdup("Invalid argument") = 0x2245c00 strlen("org.freedesktop.DBus.Error.InvalidArgs") = 38 strcmp("rg.freedesktop.DBus.Error.InvalidArgs", "rg.freedesktop.DBus.Error.InvalidArgs") = 0 Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 23 Aug 2015 00:28, Bjoern Voigt
Carlos E. R. wrote:
Please change the subject line so that it doesn't say "systemd", or the automatic mail filters vetoes the post :-(
On 2015-08-21 12:59, Bjoern Voigt wrote:
Carlos E. R. wrote: # insserv SuSEfirewall2 Warning: /etc/init.d/SuSEfirewall2 is masked by /usr/lib/systemd/system/SuSEfirewall2.service. Try 'chkconfig SuSEfirewall2 on' instead can't open SuSEfirewall2: No such file or directory at /usr/sbin/insserv line 80.
I'm unsure, but maybe you have to change directory to /etc/init.d
Wait. There is no firewall script there. That's the problem. Must be another name. No, there isn't any SuSEfirewall2 script in /etc/init.d. systemctl seems to search /etc/init.d first and continues with /usr/lib/systemd/system. /usr/local/lib/systemd/system/SuSEfirewall2.service exists.
Here is an ltrace-excerpt: ...
Just to make sure it is not a'trivial' error, what is the output of "rpm --verify SuSEfirewall2" ? Only one line is OK, and that is for the '/etc/sysconfig/SuSEfirewall2' file, e.g.: [output] S.5....T. c /etc/sysconfig/SuSEfirewall2 [/output] the service files should be in '/usr/lib/systemd/system/': /usr/lib/systemd/system/SuSEfirewall2.service /usr/lib/systemd/system/SuSEfirewall2_init.service when 'enabled', there are links to these files in '/etc/systemd/' /etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service /etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service and the called executeable resides in '/usr/sbin/': /usr/sbin/SuSEfirewall2 The 'helper scripts' are in '/etc/sysconfig/scripts/' /etc/sysconfig/scripts/SuSEfirewall2-* - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Yamaban wrote:
Just to make sure it is not a'trivial' error, what is the output of "rpm --verify SuSEfirewall2" ? Only one line is OK, and that is for the '/etc/sysconfig/SuSEfirewall2' file, e.g.: [output] S.5....T. c /etc/sysconfig/SuSEfirewall2 [/output] Same for me:
# rpm --verify SuSEfirewall2 S.5....T. c /etc/sysconfig/SuSEfirewall2
the service files should be in '/usr/lib/systemd/system/': /usr/lib/systemd/system/SuSEfirewall2.service /usr/lib/systemd/system/SuSEfirewall2_init.service Yes, files are correct.
when 'enabled', there are links to these files in '/etc/systemd/' /etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service /etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service
Good point. These files are zero length files on my system, not links: # ls -l /etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service /etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service ---------- 1 root root 0 Aug 16 23:57 /etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service ---------- 1 root root 0 Aug 16 23:57 /etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service After deleting the files, I can enable SuSEfirewall2 again: # rm /etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service /etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service ---------- 1 root root 0 Aug 16 23:57 /etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service ---------- 1 root root 0 Aug 16 23:57 /etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service # systemctl disable SuSEfirewall2 # systemctl enable SuSEfirewall2 # ls -l /etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service /etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service lrwxrwxrwx 1 root root 45 Aug 24 09:20 /etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service -> /usr/lib/systemd/system/SuSEfirewall2.service lrwxrwxrwx 1 root root 50 Aug 24 09:20 /etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service -> /usr/lib/systemd/system/SuSEfirewall2_init.service Thanks for the hint. The problem with the zero length files was probably caused by a failed restore from tar-backup operation. Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-08-24 09:28, Bjoern Voigt wrote:
Thanks for the hint. The problem with the zero length files was probably caused by a failed restore from tar-backup operation.
Oh! :-o - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXa7JIACgkQja8UbcUWM1yyXgD/VKYGLwoXYvBtAawR7GLCanTP MzWR9Q+6UEv6idvavgQA/2AkJl41vXEzYVHCPgcQO95S7GNzo5CcXgjF/g6LSauT =Qpg2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-08-23 00:28, Bjoern Voigt wrote:
No, there isn't any SuSEfirewall2 script in /etc/init.d. systemctl seems to search /etc/init.d first and continues with /usr/lib/systemd/system. /usr/local/lib/systemd/system/SuSEfirewall2.service exists.
I just tried in my 13.1: minas-tirith:~ # systemctl enable SuSEfirewall2 minas-tirith:~ # systemctl disable SuSEfirewall2 rm '/etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service' rm '/etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service' rm '/etc/systemd/system/SuSEfirewall2_setup.service' minas-tirith:~ # systemctl enable SuSEfirewall2 ln -s '/usr/lib/systemd/system/SuSEfirewall2.service' '/etc/systemd/system/SuSEfirewall2_setup.service' ln -s '/usr/lib/systemd/system/SuSEfirewall2.service' '/etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service' ln -s '/usr/lib/systemd/system/SuSEfirewall2_init.service' '/etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service' minas-tirith:~ # systemctl enable SuSEfirewall2 minas-tirith:~ # It is set as a native systemd service, which is why there is no script in /etc/init.d/ You should have /usr/lib/systemd/system/SuSEfirewall2*.service files. Are they missing? - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXY/oAACgkQja8UbcUWM1xEsQD+JVytw8tslVNp3FSgJNj34E+H 7F0oXsTtp7FQDF3zWIcA/3fZxmgd3tyiN6O7m1Po8o2DDsQjAmGixobyh4/M24c+ =OOdG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
23.08.2015 01:28, Bjoern Voigt пишет:
Carlos E. R. wrote:
Please change the subject line so that it doesn't say "systemd", or the automatic mail filters vetoes the post :-(
On 2015-08-21 12:59, Bjoern Voigt wrote:
Carlos E. R. wrote: # insserv SuSEfirewall2 Warning: /etc/init.d/SuSEfirewall2 is masked by /usr/lib/systemd/system/SuSEfirewall2.service. Try 'chkconfig SuSEfirewall2 on' instead can't open SuSEfirewall2: No such file or directory at /usr/sbin/insserv line 80.
I'm unsure, but maybe you have to change directory to /etc/init.d
Wait. There is no firewall script there. That's the problem. Must be another name. No, there isn't any SuSEfirewall2 script in /etc/init.d. systemctl seems to search /etc/init.d first and continues with /usr/lib/systemd/system. /usr/local/lib/systemd/system/SuSEfirewall2.service exists.
Here is an ltrace-excerpt:
Please make full trace available.
# ltrace -s 1000 -A 1000 systemctl enable SuSEfirewall2 [...] strlen("/etc/init.d") = 11 malloc(12) = 0x2249400 stpcpy(0x2249400, "/etc/init.d") = 0x224940b free(0x2249400) = <void> strlen("\n\t") = 2 strlen("/etc/init.d") = 11 malloc(12) = 0x2249400 stpcpy(0x2249400, "/etc/init.d") = 0x224940b free(0x2249400) = <void> strlen("SuSEfirewall2.service") = 21 strlen(".service") = 8 memcmp(0x22436dd, 0x4699ea, 8, 2538) = 0 __asprintf_chk(0x7ffcbbcb0408, 1, 0x468228, 0x2245300) = 41 access("/etc/systemd/system/SuSEfirewall2.service", 0) = -1 free(0x22452a0) = <void> __asprintf_chk(0x7ffcbbcb0408, 1, 0x468228, 0x2247320) = 41 access("/run/systemd/system/SuSEfirewall2.service", 0) = -1 free(0x22452a0) = <void> __asprintf_chk(0x7ffcbbcb0408, 1, 0x468228, 0x2245270) = 51 access("/usr/local/lib/systemd/system/SuSEfirewall2.service", 0) = -1 free(0x2249340) = <void> __asprintf_chk(0x7ffcbbcb0408, 1, 0x468228, 0x2248330) = 45 access("/usr/lib/systemd/system/SuSEfirewall2.service", 0) = 0 [...] memchr("ybnqiuxtdsogh", 's', 13) = 0x47952a memchr("org.freedesktop.DBus.Error.InvalidArgs", '\0', 38) = nil [...] memchr("ybnqiuxtdsogh", 's', 13) = 0x47952a memchr("Invalid argument", '\0', 16) = nil memmove(0x2245530, "", 0) = 0x2245530 __strdup("org.freedesktop.DBus.Error.InvalidArgs") = 0x2245580 __strdup("Invalid argument") = 0x2245c00 strlen("org.freedesktop.DBus.Error.InvalidArgs") = 38 strcmp("rg.freedesktop.DBus.Error.InvalidArgs", "rg.freedesktop.DBus.Error.InvalidArgs") = 0
Greetings, Björn
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-08-19 00:24, Bjoern Voigt wrote:
I am also unable to enable the SuSEfirewall2 service manually:
systemctl enable SuSEfirewall2.service Failed to execute operation: Invalid argument
Do it with chkconfig. It will also fail, but it will tell you the syntax to attempt with insserv, and this one you can correct. It is a bug somewhere, I think chkconfig is using the wrong syntax. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXVL0EACgkQja8UbcUWM1xyWAD/RAFeYUPtwqFGH6jDxpNTHFUn kN4KOfgUdN4WxOA7mH4A/2nZ3k2pZj9BtJKDlXShV8HIzSG3MKvRdyPOijXUAsev =E3wZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrei Borzenkov -
Bjoern Voigt -
Carlos E. R. -
Carlos E. R. -
Yamaban