Problem with UFW, problem running ufw-init. Possibly Kernel issue

[lyndog]

Hi all, I am having a problem trying to start up UFW on my installation.

I recently installed a newer Kernel version, the output of uname -r is: 5.4.62-1-MANJARO

When I run sudo ufw enbale I am met with the following output:

ERROR: problem running ufw-init
modprobe: FATAL: Module nf_conntrack_ftp not found in directory /lib/modules/5.4.62-1-MANJARO
modprobe: FATAL: Module nf_nat_ftp not found in directory /lib/modules/5.4.62-1-MANJARO
modprobe: FATAL: Module nf_conntrack_netbios_ns not found in directory /lib/modules/5.4.62-1-MANJARO
iptables-restore v1.8.5 (legacy): Couldn't load match `limit':No such file or directory

Error occurred at line: 63
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
iptables-restore v1.8.5 (legacy): Couldn't load match `limit':No such file or directory

Error occurred at line: 8
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
ip6tables-restore v1.8.5 (legacy): Couldn't load match `rt':No such file or directory

Error occurred at line: 24
Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.

Problem running '/etc/ufw/before.rules'
Problem running '/etc/ufw/user.rules'
Problem running '/etc/ufw/before6.rules

This causes all internet traffic to fail completely without disabling ufw.

Curiously when I run ls -l /lib/modules I am met with:

total 16
drwxr-xr-x 4 root root 4096 Sep 15 17:04 4.19.144-1-MANJARO
drwxr-xr-x 4 root root 4096 Sep 15 17:04 5.4.64-1-MANJARO
drwxr-xr-x 2 root root 4096 Sep 15 17:03 extramodules-4.19-MANJARO
drwxr-xr-x 2 root root 4096 Sep 15 17:03 extramodules-5.4-MANJARO

And running sudo mhwd-kernel -li I am met with:

Currently running: 5.4.62-1-MANJARO (linux54)
The following kernels are installed in your system:
   * linux419
   * linux54

So when I run a command to print out my kernel version I get 5.4.62-1-MANJARO but the modules in /lib/modules seem to be for 5.4.64-1-MANJARO. I am unsure if this is the major issue or a red herring, any ideas?

[xabbu]

Did you reboot your system after the update? This is a very important step after a kernel update.

[lyndog]

Now I feel like a fool, I swear I had done a reboot post kernel update. I have definitely power cycled my machine several times since then but after running sudo reboot it seems to work.

I blame the fact that I was running around trying to get something else working with the kernel update (docker) and had been rebooting at the time before the kernel update for my miss-remembering. Thanks xabbu!