openSuSe 11.4 SuSefirewall2 init and setup

English Install/Boot/Login
#1

Hello,

I’ve downloaded and fresh new installed 11.4 yesterday, but I got during the installation the following errors:

Cannot enable service “SuSefirewall2_init”
Cannot enable service “SuSefirewall2_setup”

I tried after the installation was completed to go and manually enable the firewall startup at boot time with the same results.
I googled the error but I didn’t seem to find anything pertaining to my specific error.
Can you please help? If there already is a thread about this please excuse me and point me to it.

Thank you.
Calin.

#2

Not sure what you mean by manually, but services generally need to be started by a root privileged user.

Use YaST to setup and turn on your firewall. It should provide clear messages why it might be unable to start the firewall.

#3

Did you run the media check on the install media (first menu) and also prior to burn did you check the checksums? This sounds like a bad butn or download to me.

#4

On 2011-03-19 13:06, CalinJugarean wrote:
> I tried after the installation was completed to go and manually enable
> the firewall startup at boot time with the same results.

Repeat in CLI, paste the exact command and response here. As Code (# in
advanced edit).

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

#5

OK, thank you, here’s the command:

yast firewall startup atboot

Start-Up:

Enabling firewall in the boot process…

Errors:
Cannot enable service ‘SuSEfirewall2_init’.
Cannot enable service ‘SuSEfirewall2_setup’.

#6

Is your firewall configured before you try to start the firewall. I don’t think its turned on by default and maybe trying to start it before its configured is your problem.
Can you use SUSE Paste to paste the output from the last 2 days in


 grep -i firewall  /var/log/messages
#7

On 2011-03-19 18:06, CalinJugarean wrote:
>
> OK, thank you, here’s the command:
>
> # yast firewall startup atboot
>
> Start-Up:
> ---------
>
> Enabling firewall in the boot process…
>
>
> Errors:
> Cannot enable service ‘SuSEfirewall2_init’.
> Cannot enable service ‘SuSEfirewall2_setup’.

That’s not you manually enabling the service, in the command line (CLI).
That’s automatic. I want you using chkconfig, and later running the service
(rcSuSEfirewall2).

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

#8

chkconfig SuSEfirewall2_init on

insserv: FATAL: service network is missed in the runlevels 2 4 to use service ha_logd
insserv: FATAL: service syslog is missed in the runlevels 4 to use service ha_logd
insserv: exiting now!
/sbin/insserv failed, exit code 1

chkconfig SuSEfirewall2_setup on

chkconfig SuSEfirewall2_setup on
insserv: FATAL: service SuSEfirewall2_init has to be enabled to use service SuSEfirewall2_setup
insserv: FATAL: service network is missed in the runlevels 2 4 to use service ha_logd
insserv: FATAL: service syslog is missed in the runlevels 4 to use service ha_logd
insserv: exiting now!
/sbin/insserv failed, exit code 1

#9

On 2011-03-20 02:06, CalinJugarean wrote:
>
> # chkconfig SuSEfirewall2_init on

I don’t know… I run “chkconfig SuSEfirewall2_init” on mine and says off
in my 11.4 test partition, but it is on in my 11.2. I’m baffled. Ah! I see,
my firewall is down!

…]

Ok, now is up. And the command I told you shows “on”. Now, lets see about
yours.

> insserv: FATAL: service network is missed in the runlevels 2 4 to use
> service ha_logd
> insserv: FATAL: service syslog is missed in the runlevels 4 to use
> service ha_logd
> insserv: exiting now!
> /sbin/insserv failed, exit code 1

service ha_logd? What is that? High availability log daemon?

You are running some non-typical software for someone installing openSUSE
first time… You have some explaining to do.

I’m afraid I can’t help you with that setup.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

#10

Hi!
I’ve the same problem, but in my case the reason is different:

chkconfig SuSEfirewall2_init on
insserv: FATAL: service syslog is missed in the runlevels 4 to use service vboxdrv
insserv: exiting now!
/sbin/insserv failed, exit code 1

So, i’m going to try again removing at first VirtualBox.

#11

Ok, the problem was VirtualBox in my case, now it’s ok without it :wink:

@CalinJugarean
The problem seems to be ha_logd… Try without it…

#12

ha_logd is hardly non-typical software. It is part of the 11.4 cluster-glue package, and is required, for example, using ocfs2 at all. This has been reported at BugZilla as bugs 681340 and apparently 675870. So far they have NEW status and are assigned to bnc-team-screening, 675870 has been sitting in that state for 3 weeks apparently ignored.

The question is WTF is with $network being required in runlevel 2, which does not have network by definition?

#13

On 2011-03-23 23:06, normmackey wrote:
>
> robin_listas;2308499 Wrote:

> ha_logd is hardly non-typical software.

Hardly a common user will use the “high availablity log daemon”. I can’t
help with such a setup. Maybe you can, but I can’t.

> The question is WTF is with $network being required in runlevel 2,
> which does not have network by definition?

Not true. Not external network, yes, but the “lo” interface goes up.

runlevel 0 is System halt (Do not use this for initdefault!)

runlevel 1 is Single user mode

runlevel 2 is Local multiuser without remote network (e.g. NFS)

runlevel 3 is Full multiuser with network

runlevel 4 is Not used

runlevel 5 is Full multiuser with network and xdm

runlevel 6 is System reboot (Do not use this for initdefault!)

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

#14

In any case, for those not using Runlevel 2 and 4 (I.E. most users), why not just remove them from etc/init.d/logd’s

Default-Start: 2 3 4 5

and make the line

Default-Start: 3 5

?

#15

I get the same errors.
yast firewall startup atboot

Start-Up:

Enabling firewall in the boot process…

Errors:
Cannot enable service ‘SuSEfirewall2_init’.
Cannot enable service ‘SuSEfirewall2_setup’.

I am wondering now if it is a Virtual Machine Problem.
A previous poster said his was on Vbox.

My setup is in Vsphere ESX 4.1, New VM created as server basic install.

I will with a GUI, desktop model and post back if it still fails.

Back in a few

#16

Confirmed, It works if you install a GUI, I used Gnome.

If you are setting up a server like I am, you can prevent loading the GUI, by editing the /etc/inittab , change the id:5 ( GUI ) to a id:3 ( single user mode )

Rebooted and tested , Firewall still active.

Thanks all

#17

On Fri April 1 2011 10:06 am, deltamike214 wrote:

>
> Confirmed, It works if you install a GUI, I used Gnome.
>
> If you are setting up a server like I am, you can prevent loading the
> GUI, by editing the /etc/inittab , change the id:5 ( GUI ) to a id:3 (
> single user mode )
>
> Rebooted and tested , Firewall still active.
>
> Thanks all
>
deltamike214;

Run level 1 is single user. Run level 3 is multi-user with network and no
GUI.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

#18

hey, I’ve just got this issue with 11.3.

Trying to figure out whats wrong but have not idea…

This is pretty much all what /var/log/messages says:

May  9 14:37:18 lnx-server SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
May  9 14:37:18 lnx-server SuSEfirewall2: using default zone 'ext' for interface eth1
May  9 14:37:18 lnx-server SuSEfirewall2: using default zone 'ext' for interface vboxnet0
May  9 14:37:18 lnx-server SuSEfirewall2: batch committing...
May  9 14:37:18 lnx-server SuSEfirewall2: Firewall rules successfully set

And I paste my output after chkconfig which doesn’t throw any error messages but a lot other weird stuff I dont know to handle…

SUSE Paste

greets

#19

On 2012-05-09 14:56, alex4suse wrote:
>
> hey, I’ve just got this issue with 11.3.

1: Are you aware that 11.3 is out of maintenance? You should upgrade to
another version.
2: Your problem is not the same as CalinJugarean had, so you should post
your own new thread.

> Trying to figure out whats wrong but have not idea…
>
> This is pretty much all what /var/log/messages says:
>
>
> Code:
> --------------------
> May 9 14:37:18 lnx-server SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 …
> May 9 14:37:18 lnx-server SuSEfirewall2: using default zone ‘ext’ for interface eth1
> May 9 14:37:18 lnx-server SuSEfirewall2: using default zone ‘ext’ for interface vboxnet0
> May 9 14:37:18 lnx-server SuSEfirewall2: batch committing…
> May 9 14:37:18 lnx-server SuSEfirewall2: Firewall rules successfully set
> --------------------

No problem here.


> And I paste my output after chkconfig which doesn't throw any error
> messages but a lot other weird stuff I dont know to handle...
>
> 'SUSE Paste' (http://paste.opensuse.org/71641556)

> lnx-server:~# chkconfig SuSEfirewall2_init on
> insserv: warning: script 'K01vboxinit' missing LSB tags and overrides
> insserv: warning: script 'K01caagentinit' missing LSB tags and overrides
> insserv: warning: script 'S99igateway' missing LSB tags and overrides
> insserv: warning: script 'vboxold' missing LSB tags and overrides
> insserv: Default-Start undefined, assuming default start runlevel(s) for script `vboxold'
> insserv: warning: script 'igatewayd' missing LSB tags and overrides
> insserv: Default-Start undefined, assuming default start runlevel(s) for script `igatewayd'
> insserv: warning: script 'vboxinit' missing LSB tags and overrides
> insserv: warning: script 'caagentinit' missing LSB tags and overrides
> insserv: Starting S99igateway depends on stoppreload and therefore on system facility `$all' which can not be true!

Well, you have added services that did not come with the original openSUSE
system, so you either complain to the providers of those services or
correct them yourself. I would point you to the documentation for init.d,
but it was removed recently because it has been superseded by systemd; you
will have to read main init.d instead, or the pdf book that came with your
distribution.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#20

ok I solved the problem with adding the LSB Header to the concerning services…

example of the LSB Header, something similar in /etc/init.d/skeleton

### BEGIN INIT INFO
# Provides:      caagent
# Required-Start:   $network
# Required-Stop:   $network
# Default-Start:   2 3 4 5
# Default-Stop:      1
# Short-Description:   Backup Agent
### END INIT INFO

thx for pointing me in the right direction…

so long…