Advanced Recovery sync is stuck

Following my issue last week with Adv Rec (user error with the FPBX firewall) I’ve got a stuck sync that I can’t get rid of. Stopping and starting Adv Rec operations work fine, but once restarted the same sync ID number is presented and has been that way for 3 days now. If I click the sync button I get told there is a sync a progress and I need to wait. I’m pretty sure 3 days is long enough to have waited.
Is there a way I can clear this sync and launch a new one without scheduling a restart (assuming that would bluntly do the trick)?


Thank you
Nathan.

Hi @urbanpeasant

May be check your db for “adv_recovery_backuprestore_log” DB table like
select * from adv_recovery_backuprestore_log where type='BackupRun'
and delete the entry and try again.

Regards
Kapil

Thanks Kapil.

I didn’t find a log by the name you quoted.

The advrecovery_err.log contains no data.

The adv_recovery.log does show the stuck transaction ID

And the advrecovery-out.log show the following errors repeatedly.

2025-05-11 18:37 +01:00: Stack trace:
2025-05-11 18:37 +01:00: 1. Whoops\Exception\ErrorException->() /var/www/html/admin/modules/adv_recovery/functions.inc/functions.inc.php:92
2025-05-11 18:37 +01:00: 2. Whoops\Run->handleError() /var/www/html/admin/modules/adv_recovery/functions.inc/functions.inc.php:92
2025-05-11 18:37 +01:00: 3. advr_service_daemon() /var/www/html/admin/modules/adv_recovery/adv_recovery_service.php:19
2025-05-12 00:39 +01:00: Whoops\Exception\ErrorException: Illegal string offset ‘restorestatus’ in file /var/www/html/admin/modules/adv_recovery/functions.inc/functions.inc.php on line 92
2025-05-12 00:39 +01:00: Stack trace:
2025-05-12 00:39 +01:00: 1. Whoops\Exception\ErrorException->() /var/www/html/admin/modules/adv_recovery/functions.inc/functions.inc.php:92
2025-05-12 00:39 +01:00: 2. Whoops\Run->handleError() /var/www/html/admin/modules/adv_recovery/functions.inc/functions.inc.php:92
2025-05-12 00:39 +01:00: 3. advr_service_daemon() /var/www/html/admin/modules/adv_recovery/adv_recovery_service.php:19

I’m not spotting anything here that I can remove to help things out and ensure a successful sync. Other thoughts?

Thanks
Nathan.

I was talking about the DB table to delete the entry so you can start the sync again.

As this is commercial module so may be you can raise support ticket as well. If raising support ticket then please DM me the ticket number so I can check internally with the team. Thanks

Best Regards,
Kapil

Where do I find that DB table Kapil? I can’t see it in the asterisk folder. We have some Linux admins here that should be able to help out once I know where to ask them to look.
I’m not sure Sangoma will offer support. The licenses for AR are valid (renew in December each year) but we don’t have a support contract. I am seeking management approval to change this however, now that the business is using FPBX as a BAU application.
Thanks.

Sorted!

Someone helped me out with the databases.
We ran ‘systemctl status’ to find out what database was running and saw it was mariadb.service using mysql.

We connected to mysql and then ran show databases; to see the list

mysql

Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 1108233
Server version: 5.5.65-MariaDB MariaDB Server

MariaDB [(none)]> show databases;
±-------------------+
| Database |
±-------------------+
| information_schema |
| asterisk |
| asteriskcdrdb |
| mysql |
| performance_schema |
| test |
±-------------------+

We connected to askerisk and then looked at the tables

MariaDB [(none)]> connect asterisk;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Connection id: 1108353
Current database: asterisk

MariaDB [asterisk]> show tables
→ ;
±-------------------------------------------+
| Tables_in_asterisk |
±-------------------------------------------+
| admin |
| adv_recovery_backuprestore_log

We could see the table you mentioned Kapil, so we ran the command you gave

MariaDB [asterisk]> select * from adv_recovery_backuprestore_log where type=‘BackupRun’;

Then we deleted both of those entries from the table

MariaDB [asterisk]> delete from adv_recovery_backuprestore_log where type=‘BackupRun’;
Query OK, 2 rows affected (0.01 sec)

MariaDB [asterisk]> commit;
Query OK, 0 rows affected (0.00 sec)

MariaDB [asterisk]> select * from adv_recovery_backuprestore_log where type=‘BackupRun’;
Empty set (0.00 sec)

MariaDB [asterisk]>

At this point a Refresh of the Adv Rec web page showed that there was no longer a sync in progress, and a new sync worked correctly.

Thanks for the assist.
Nathan.

Great :+1:

Best Regards
Kapil

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.