From: unruh@invalid.ca
On 2021-08-08, Sidney_Kotic wrote:
> On 8/8/21 12:40 AM, Carlos E. R. wrote:
>
>> Yours will probably say different, so copy it here. If not, issue:
>
> crab:~ # systemctl status firewalld
> ● firewalld.service - firewalld - dynamic firewall daemon
> Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
vendor
> preset: disabled)
Note that the vendor (SUSE) set up the system so that the firewall was
disabled.
> Active: inactive (dead)
> Docs: man:firewalld(1)
>
>> systemctl --now enable firewalld
>
> This did bring it up.
>
>> and then ask for status. If it fails, then you need to find out why:
>>
>> journalctl
>
> I went through that, as best as I could. Here are all of the entries dealing
> with the firewalld from a reboot up to the time I logged back in and issued
the
> enable command above:
>
> Aug 08 08:28:34 crab systemd[1]: Starting SuSEfirewall2 phase 1...
> Aug 08 08:28:34 crab systemd[1]: Condition check resulted in YaST2 Second
Stage
> being skipped.
> Aug 08 08:28:34 crab systemd[1]: Condition check resulted in YaST2 Firstboot
> being skipped.
>
> Aug 08 08:28:36 crab SuSEfirewall2[1024]: Firewall rules set to CLOSE.
> Aug 08 08:28:36 crab systemd[1]: Finished SuSEfirewall2 phase 1.
>
> Aug 08 08:28:38 crab systemd[1]: Starting SuSEfirewall2 phase 2...
>
> Aug 08 08:28:44 crab SuSEfirewall2[1365]: Firewall rules successfully set
> Aug 08 08:28:44 crab systemd[1]: Finished SuSEfirewall2 phase 2.
>
> Not much to see there. Nothing that tells me why it wasn't started. Where,
in
> the filesystem, would I look to see how systemd should do that?
The above just says it started, presumably because you told it to start
(systemctl --now enable firewall)
Presumably it was not enabled for startup. and thus nothing was enetered
into the logs because it never tried to start it up then.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
