Sonata Stats Server Error after upgrade to Vital V4

VitalPBX: 4.1.0-3
Installed a new Debian 11 server installed all the basic addons and reinstalled from a backup as I have been doing with other system. During the restore process the following errors showed up:

As the image shows, there was a Permission error when recovering the queue-stats backup and trying to run artisan.

Now when try to log into stats, I keep getting a Server Error. I orginally installed the addon and setup the connection settings before restoring the backup.

I have removed the addon and reinstalled, but now no wizard appears as the backup is already there I guess.

The console is showing the sonata stats service is not actually running properly either.

● sonata-stats.service - Sonata Stats
Loaded: loaded (/lib/systemd/system/sonata-stats.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2024-05-11 22:36:34 PDT; 7min ago
Process: 12085 ExecStart=/usr/bin/php artisan queue:work --tries=3 --backoff=3 --sleep=300 --timeout=3600 (code>
Process: 12086 ExecStartPost=/usr/bin/php artisan crontab:update (code=exited, status=0/SUCCESS)
Main PID: 12085 (code=exited, status=1/FAILURE)
CPU: 282ms

May 11 22:36:33 pbx systemd[1]: sonata-stats.service: Main process exited, code=exited, stat>
May 11 22:36:33 pbx systemd[1]: sonata-stats.service: Failed with result ‘exit-code’.
May 11 22:36:34 pbx systemd[1]: sonata-stats.service: Scheduled restart job, restart counter>
May 11 22:36:34 pbx systemd[1]: Stopped Sonata Stats.
May 11 22:36:34 pbx systemd[1]: sonata-stats.service: Start request repeated too quickly.
May 11 22:36:34 pbx systemd[1]: sonata-stats.service: Failed with result ‘exit-code’.
May 11 22:36:34 pbx systemd[1]: Failed to start Sonata Stats.

Any idea to get this working again.

I was able to reinstall the addond and I deleted the wizard file and ran php artisan:cache and got to fille out the wizard again. Something failed during the backup recovery, certainly.

1 Like