Shorewall doesn't start after reboot - urgent!

NethServer Version: 7.2.2009
Module: firewall

Hi friends,

I updated my proxmoxserver this morning and rebooted it. Before I installed some updates on Nethserver.
Since then, shorewall doesn’t start automatically with systemboot.
When starting shorewall manually, it shows running, but I can’t get the users and groups in cockpit.

Nethupdates this morning:

Nov 18 07:56:49 Updated: clamav-filesystem-0.103.4-1.el7.noarch
Nov 18 07:56:50 Updated: clamav-lib-0.103.4-1.el7.x86_64
Nov 18 07:56:50 Updated: clamav-update-0.103.4-1.el7.x86_64
Nov 18 07:56:50 Updated: httpd-tools-2.4.6-97.el7.centos.2.x86_64
Nov 18 07:56:51 Updated: httpd-2.4.6-97.el7.centos.2.x86_64
Nov 18 07:56:51 Updated: 1:mod_ssl-2.4.6-97.el7.centos.2.x86_64
Nov 18 07:56:52 Updated: clamav-0.103.4-1.el7.x86_64
Nov 18 07:56:52 Updated: clamd-0.103.4-1.el7.x86_64

Shorewall status:

[root@nethserver ~]# systemctl status shorewall -l
● shorewall.service - Shorewall IPv4 firewall
   Loaded: loaded (/usr/lib/systemd/system/shorewall.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/shorewall.service.d
   Active: failed (Result: exit-code) since Thu 2021-11-18 11:44:03 CET; 3min 16s ago
  Process: 1530 ExecStart=/usr/sbin/shorewall $OPTIONS start $STARTOPTIONS (code=exited, status=143)
  Process: 1360 ExecStartPre=/usr/share/nethserver-blacklist/load-ipsets (code=exited, status=0/SUCCESS)
 Main PID: 1530 (code=exited, status=143)

Nov 18 11:44:02 nethserver.jeckel.local shorewall[1530]: bye...
Nov 18 11:44:02 nethserver.jeckel.local shorewall[1530]: IPv4 Forwarding Enabled
Nov 18 11:44:02 nethserver.jeckel.local shorewall[1530]: Processing /etc/shorewall/restored ...
Nov 18 11:44:02 nethserver.jeckel.local shorewall[1530]: done.
Nov 18 11:44:02 nethserver.jeckel.local shorewall[1530]: Shorewall restored from /var/lib/shorewall/restore
Nov 18 11:44:03 nethserver.jeckel.local shorewall[1530]: /usr/share/shorewall/lib.common: line 93:  2883 Terminated                                                                                    $SHOREWALL_SHELL $script $options $@
Nov 18 11:44:03 nethserver.jeckel.local systemd[1]: shorewall.service: main process exited, code=exited, status=143/n/a
Nov 18 11:44:03 nethserver.jeckel.local systemd[1]: Failed to start Shorewall IPv4 firewall.
Nov 18 11:44:03 nethserver.jeckel.local systemd[1]: Unit shorewall.service entered failed state.
Nov 18 11:44:03 nethserver.jeckel.local systemd[1]: shorewall.service failed.

I need help, because sogo is our central calendar and we need it and it cant authenticate without users and groups.

Any thoughts about this??

TIA Ralf



Are you using LDAP or AD?
Is the account provider running?

The list of users is NOT dependent on Shorewall running, it depends on your Account Provider.
SoGo needs the Account Provider, otherwise it doesn’t have any users for mail / calendar or adressbooks…
SoGo will need Shorewall to get or send mail, but first see that you have users and groups!

BTW, I also had updates on my Proxmox at home - including a new kernel and a reboot.
Also for about half of my clients, I’ve done the Proxmox update. My clients had no issues so far.

My 2 cents

Hi Andy,

thanks for reply. Yes SSSD is running.

Does the /var/log/shorewall-init.log* has more details on the failed start?

or journalctl -u shorewall

That was a great hint!! Thanks!

I found iptables-restore v1.4.21: Set geo-whitelist doesn't exist.

I disabled geoip in threat shield and restarted shorewall.
Now all users are back in cockpit and sogo authentication works again.

@stephdl and @filippo_carletti is there a bug in geoip?

1 Like

created without condition by the load-geoips, you have to dive better or during the update to understand why

o.k. I did the create command manually and the enabled deoip again.
Now everything works again. So no bug.

But what could have happend, that it lost the entries (geo-whitelist,geo-cn and geo-ru)?

/var/log/messages could maybe explain us better, search before and after the update, when you trigger the shorewall restart it drops normally all ipset before to build them again IIRC

Sorry I have to crawl back. After reboot same problem again.
So the set are not saved. Should I have done ipset save after create?
I’ll disable geoip for the moment until I’ve some time to dive in it.

Thanks for your help Stephan! :+1:

good new I can reproduce :smiley:

add to /etc/systemd/system/shorewall.service.d/blacklist.conf

this is the example

# /etc/systemd/system/shorewall.service.d/blacklist.conf

then systemctl daemon-reload

try the reboot then, the ipset will be created after the reboot, think to enable again the geoip before to reboot

1 Like

Good morning Stephane,

tried your solution and I confirm that it works. :clap: :clap: :clap: :smiley:
After reboot geoips are loaded and shorewall works as expected.

I marked this one now as solution, as my one was only a workaround. :wink:

Thanks a lot!!