auto config backups not showing in 2.60 dev

4o4rh

Manual backups say they are successfully with 2.60dev but they do not show in the restore window. I always download the config from these backups, because i found they include everything whereas the diagnostics - backup/restore does not

Steve_B

Tested this morning with 2.6 snapshot from last night and ACB appears to be working as expected.

There was a brief server outage a couple of days ago. Possibly you were unlucky and tested during that event.

4o4rh

@steve_b nope. Still happening right now.
I am using below because of the multiwan issue with 2.5.1

2.6.0-DEVELOPMENT (amd64)
built on Fri May 28 01:04:03 EDT 2021
FreeBSD 12.2-STABLE

Steve_B

I am unable to reproduce an issue with that version either. Can you ping acb.netgate.com ?

4o4rh

@steve_b said in auto config backups not showing in 2.60 dev:

acb.netgate.com

I can of course ping. I can see both manual and automated backups from 2.5.0 and manual and automated backups from 2.5.1. The last backup was before I upgraded to 2.60dev
Sun, 06 Jun 2021 00:01:59 +0200 (system): Scheduled backup

if i do a manual backup
Backup completed successfully.

Just can't see any backups after 6th of June

4o4rh

@gwaitsi fyi - the weekly schedule just run and the backup shows in the restore list. so it is only the manual backup that does not show. Also, i just upgraded to the June release, but hasn't made any difference

Steve_B

Just completed another round of tests, including "Backup now", and again all works as expected. This is mysterious as whether manual or scheduled, the same code is executed.

I tested "Backup now" while configured for ACB on config change, and again for ACB on on a regular schedule.

I'll try to think of another way to test.

4o4rh

@steve_b it is the maximum length that appears to have changed

Core_Build_2_60_dev_LAGG_Setup_DNS_Forwader_pfBlockerNG_UPS_Suricata_v2_LoadBalance = bad
Core_Build_2_60_dev_LAGG_Setup_DNS_Forwader_pfBlockerNG = bad
Core_Build_2_60_dev_LAGG_Setup_DNS_Forwader_pfBlocker = Bad
Core_Build_2_60_dev_LAGG_Setup_DNS_Forwader_pfBlocke = good

so the Revision size has been substantially reduced in 2.60 compared to <= 2.5x

Steve_B

Thanks for the more detailed explanation. Now I see what the problem is.

pfBlocker and Snort both beat the crap out of the configuration system writing to it on such a frequent basis that ACB becomes pretty much useless. I discussed ways to address this with the package maintainers some time ago but so far the problem still exists.

For this reason there is a filter in the ACB system that rejects backups if the "Reason" parameter contains "pfblocker", "snort" or "minicron".

pfSense is supposed to display an error message stating that the backup was rejected, but this seems to be broken. I'll try to get that fixed ASAP.

For now, please ensure you backup "Reason" does not include those terms.