BUG: auto backup jobs not available in restore menu

4o4rh

i have two systems, prod and test. but restore lists stopped after the same change

Test system - last restore option
Thu, 22 Aug 2019 17:45:12 +0200 admin@192.168.0.09 (Local Database): Firewall: Rules - deleted a firewall rule.

Production system - last restore option
Thu, 22 Aug 2019 17:43:25 +0200 admin@192.168.0.09 (Local Database): Firewall: Rules - deleted a firewall rule.

The other common factor is, both units had reached 99.

I can resolve and traceroute from localhost and client via WAN directly
acb.netgate.com
portal.pfsense.org

i can also access both sites via HTTPS
I note that it is possible to do a restore of an early backup too.

I am wondering if there is a bug on the netgate server side.
Although you delete the backup from restore (i deleted all), it is not being deleted from the server, or the 100 backup count on the server is not subtracking the deleted backups

Pretty shoddy backup system, particularly as the diagnostics backup doesn't actually backup the whole system. I found restoring from the diagnostics backup/restore does not result is a full restore, where as the autoconf backup does.......at least for the restores that are listed.

stephenw10

Hmm, also seeing this. Digging....

stephenw10

Please re-test it should be good now.

Steve

KOM

OK, now I see my two Test runs from yesterday. New Test3 backup works and appears in the list.

What was the resolution?

stephenw10

I don't have the details but it was a backend change.

If anyone sees an issue like that in future opening a ticket is the fastest way to alert us: https://go.netgate.com

Steve

4o4rh

@stephenw10
on my test machine, where i deleted all 99 backups, it is working.
on my production machine, where i still have 48 backups, it is not working

p.s. on the test machine, i do not see any of the backups i created yesterday.

++ deleted all backups on the production machine, and it still doesn't work

stephenw10

You won't see any backups created whilst this issue was in effect. Whilst to connection to the server was good and it was able to write out entries there was an error meaning they are not found for that device. Deleting entries will make no difference here.

Was the production box successfully creating backups until yesterday?

If you PM me the device key we can check if new backups are being received.

Steve

4o4rh

@stephenw10 last working entries

Test system - last restore option
Thu, 22 Aug 2019 17:45:12 +0200 admin@192.168.0.09 (Local Database): Firewall: Rules - deleted a firewall rule.

Production system - last restore option
Thu, 22 Aug 2019 17:43:25 +0200 admin@192.168.0.09 (Local Database): Firewall: Rules - deleted a firewall rule.

Now test works, but production doesn't.
Have just run some manual backups with "test"
both report success

of course....stupid me, disabled on the production while i was investigating.....it's working.

p.s. there seems to be some limitation/s on the size / characters of the "Revision Reason"
e.g. 20180822BaseBuildSnortBlockerNGNoSquidEnabled
this reports has being successful, but doesn't show in the restore list. I have already removed the +/- characters, so must be a size limitation

stephenw10

So I think you're all good now yes?

Steve

4o4rh

@stephenw10 would be good to know exactly what the limitations are on the "Revision Reason" - thanks

KOM

@stephenw10 said in BUG: auto backup jobs not available in restore menu:

You won't see any backups created whilst this issue was in effect.

Strange. The two test backups I did yesterday to confirm the problem showed up today. I haven't tried to restore them but they were in the list.

4o4rh

it's down again

stephenw10

Seems good here. No problem on any system I tested.

It looks like the key words that are rejected if used in the Revision Reason field are: snort pfblocker minicron and merged in config.

Steve

RonpfS

@stephenw10 said in BUG: auto backup jobs not available in restore menu:

Seems good here. No problem on any system I tested.

It looks like the key words that are rejected if used in the Revision Reason field are: snort pfblocker minicron and merged in config.

Steve

That would explain why saving PfblockerNG settings doesn't end up in Services / Auto Configuration Backup / Restore :

Sat, 24 Aug 2019 11:39:23 -0400 	(system): Suricata pkg v4.1.4_8: post-install configuration saved. 	
Sat, 24 Aug 2019 11:39:31 -0400 	(system): Overwrote previous installation of suricata. 	
Thu, 29 Aug 2019 17:49:43 -0400 	admin@172.24.48.84 (Local Database): Test

Diagnostics / Backup & Restore / Config History :

 		8/29/19 17:49:37 	19.1 	262 KiB 	admin@172.24.48.84 (Local Database): Test 	Current configuration
		8/29/19 17:40:36 	19.1 	263 KiB 	(system): Installed cron job for /usr/local/bin/php /usr/local/www/pfblockerng/pfblockerng.php cron >> /var/log/pfblockerng/pfblockerng.log 2>&1 	
		8/29/19 17:40:34 	19.1 	262 KiB 	(system): pfBlockerNG: save settings 	
		8/29/19 17:36:12 	19.1 	262 KiB 	admin@172.24.48.84 (Local Database): Removed cron job for pfblockerng.php cron 	
		8/29/19 17:36:11 	19.1 	263 KiB 	admin@172.24.48.84 (Local Database): pfBlockerNG: Running Force Reload 	
		8/29/19 17:36:00 	19.1 	263 KiB 	admin@172.24.48.84 (Local Database): [pfBlockerNG] save DNSBL settings 	
		8/29/19 17:32:22 	19.1 	263 KiB 	admin@172.24.48.84 (Local Database): pfBlockerNG: Added [ gstatic.com ] to DNSBL Whitelist 	
		8/24/19 11:39:24 	19.1 	262 KiB 	(system): Overwrote previous installation of suricata. 	
		8/24/19 11:39:14 	19.1 	262 KiB 	(system): Suricata pkg v4.1.4_8: post-install configuration saved.

stephenw10

Yes, probably. The new system will be much better in that respect. https://redmine.pfsense.org/issues/9693

Steve