[Pacemaker] How SuSEfirewall2 affects on openais startup?

[Aleksey Zholdak]

Hi.

>>>> All interfaces in SuSEfirewall2 is set to "Internal zone".
>>>> I start openais on one node of two configured.
>>>> Openais starts, but resources do not run.
>>>>
>>>> When the SLES boots, I see, that SuSEfirewall2 phase 1 of 2 runs
>>>> _before_ openais and phase 2 of 2 runs _after_ openais.
>>>> This is the dependencies which are set in /etc/init.d scripts.
>>>> Could this affect the openais and it can not correctly initialize
>>>> before SuSEfirewall2 starting the second phase?
>>> Don't know much about SuSEfirewall2, but can't see how when it
>>> starts should influence the cluster, as long as it lets the
>>> traffic we need through.
>> And what to do?
> 
> The firewall should let through the UDP multicast traffic on
> ports mcastport and mcastport+1.

As I wrote above: all interfaces in SuSEfirewall2 is set to "Internal 
zone". So, how can I "open" these ports if it already opened?

>>> You mention here SLES and in the subject. Which one is
>>> it?
>> I mean SUSE Linux Enterprise Server. (Where you see OpenSUSE?)
> 
> Don't no anymore, must have misread openais as opensuse. There
> are too many openthings nowadays.

I understand ;)

>>>> When I change /etc/init.d/openais script depencies to
>>>> "Required-Start: $ALL; Should-Start: $ALL" then openais started last
>>>> and resources are starts successfully.
>>>>
>>>> Someone might comment on that?
>>>>
>>>> P.S. Sorry for my English ...

--
Aleksey