Restore .xml 22.01 possible bug

[mcury]

Hello forum, I believe I found a bug.
Saved my config with the option Backup SSH keys, then tried to enable the RAM to disk option and started to have a lot of problems, like unrecognized Kernel and pkg info being empty.
Even disabling the RAM disk wouldn't fix..

So, tried to restore my config, and noticed a lot of errors, unfortunately I don't have those errors logs to provide.
The errors were basically saying something about the SSH keys, that only one could exist, the firewall was pretty dead at that moment, even a reboot wouldn't fix it..

So, I edited the .xml file, and removed all the ssh-keys (indeed there was two).
Left that part of the config like this:
<sshdata></sshdata>

Then, after a clean install, the restore worked..

[stephenw10]

Hmm, are you able to reproduce it?

What size RAM disk did you enable? Were you running any packages?

After a bunch of unknown errors like that seeing a problem restoring the SSH keys could be any number of things. I would guess the RAM disks filled completely and somthing that needed to write to /var or /tmp was unable to.

Steve

[mcury]

@stephenw10 Hi stephenw10, thanks for answering, packages installed:

acme
aws-wizard
ipsec-profile-wizard
nut
wireguard
pfblockerng with:

Alias table IP Counts
-----------------------------
   24913 total
   17763 /var/db/aliastables/pfB_PRI1_v4.txt
    7150 /var/db/aliastables/pfB_AllowPfb_v4.txt

pfSense Table Stats
-------------------
table-entries hard limit   400000
Table Usage Count         24939

===[ DNSBL Domain/IP Counts ] ===================================

  312698 total
  165905 /var/db/pfblockerng/dnsbl/Maltrail_BD.txt
  101874 /var/db/pfblockerng/dnsbl/StevenBlack_ADs.txt
   37146 /var/db/pfblockerng/dnsbl/SFS_Toxic_BD.txt
    6971 /var/db/pfblockerng/dnsbl/Spam404.txt
     801 /var/db/pfblockerng/dnsbl/D_Me_Malv.txt
       1 /var/db/pfblockerng/dnsbl/SWC.txt
       0 /var/db/pfblockerng/dnsbl/MVPS.txt
       0 /var/db/pfblockerng/dnsbl/D_Me_Malw.txt
       0 /var/db/pfblockerng/dnsbl/C19_CTC.txt

RAM disk set to 80 /tmp and 120 /var
As soon as I enabled, firewall rebooted and I started to see problems in the logs regarding Kernel, pkg info was empty (not showing anything)..

So I tried to restore the configuration and noticed the problem with the ssh keys..
Tried a clean install, then restore that same configuration, and the ssh-keys error showed up again.
So, edited the configuration, removed the ssh-keys from it, clean install then restore and it worked..

I think I can reproduce it.. What I don't know is how the configuration ended up with 2 ssh-keys in it..

[stephenw10]

Was this after upgrading to 22.01 or after a clean install?

Had it rebooted since then or was the reboot to create the RAM disks the first time?

I haven't seen anything like that and I did spend some time playing around with RAM disks on the 3100 specifically.

If it's reproducible though I can dig into it again.

Steve

[mcury]

@stephenw10 said in Restore .xml 22.01 possible bug:

Was this after upgrading to 22.01 or after a clean install?

It was a 22.01 clean install.

@stephenw10 said in Restore .xml 22.01 possible bug:

Had it rebooted since then or was the reboot to create the RAM disks the first time?

System was running perfectly, reboot and etc... Then , decided to enable RAM disk and the system rebooted to complete the process, and the kernel and pkg info problem happened. Thats when I decided to restore the configuration and noticed the ssh keys problem

@stephenw10 said in Restore .xml 22.01 possible bug:

I haven't seen anything like that and I did spend some time playing around with RAM disks on the 3100 specifically.

I can't tell why the RAM disk problem happened.. Also, I don't know how two ssh-keys ended up in my configuration..
But this post may be useful in case this happens to someone, the only action you need is to erase the ssh-keys from the .xml and restore it again..