Good afternoon! :]
Digging through my y2log file I see many commands to disable the firewall bot not a single one to stop it. ... 2017-09-05 19:01:58 <1> server1(3030) [Ruby] yast2/systemd_unit.rb:122 `systemctl disable SuSEfirewall2.service ` To the contrary - close to the end of the log (there are only some more 50 lines) the firewall gets started explicitly
What I see in y2log is this:
2017-09-05 11:47:22 <1> bla-srv(3041) [Ruby] network/susefirewall.rb:197 Firewall service is not enabled
2017-09-05 11:47:22 <1> bla-srv (3041) [Ruby] network/susefirewall.rb:211 Checking firewall status...
2017-09-05 11:47:22 <2> bla-srv (3041) [Ruby] modules/Service.rb:448 [DEPRECATION] `Status' in "/usr/share/YaST2/lib/network/susefirewall.rb:212:in `IsStarted'" is deprecated; use `active?` instead
2017-09-05 11:47:22 <1> bla-srv (3041) [Ruby] yast2/systemd_unit.rb:122 `systemctl show SuSEfirewall2.service --property=Id --property=MainPID --property=Description --property=LoadState --property=ActiveState --property=SubState --property=UnitFileState --property=FragmentPath `
2017-09-05 11:47:22 <1> bla-srv (3041) [Ruby] network/susefirewall.rb:216 Firewall service is stopped
So I think I have to correct myself, looks like the FW isn't even started in the first place (instead of being stopped).
Another thought: despite being disabled our firewall is configured by several
I am really wondering what is causing this ...
To be honest, I don't have a clue... :/ Maybe it's got something to do with "clients/inst_oes_postconfig.rb" . Since we are not using OES I can't tell, but I don't find any calls to this module in our logs. Perhaps some step during the installation of OES requires the FW to be started even though you disabled it. BTW Our installation basis is the SLES12 SP 2 DVD-image. Regards, Zimo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org