coolify: [Bug]: Backup large postgres database stuck
Description
The in-dashboard backup solution for a postgres large database is not working.
Minimal Reproduction (if possible, example repository)
On a large 40GB database, when I try to save, it doesn’t display anything.
However, the backup was working at the beginning of July.
Exception or Error
INFO Nothing to migrate.
[05-Sep-2024 18:02:21] NOTICE: fpm is running, pid 99
[05-Sep-2024 18:02:21] NOTICE: ready to handle connections
[05-Sep-2024 18:02:21] NOTICE: systemd monitor interval set to 10000ms
INFO Seeding database.
Running in self-hosted mode.
Checking localhost key.
Refreshing public ips!
Skipping alive as do_not_track is enabled
Refreshing public ips!
Cleaning up unused networks from coolify proxy
Running queue cleanup...
Running cleanup stucked resources.
Scheduler is enabled. Starting.
Horizon is enabled. Starting.
INFO Horizon started successfully.
2024-09-05 18:02:29 App\Actions\Server\StopSentinel ................ RUNNING
2024-09-05 18:02:29 App\Actions\Server\StopSentinel ................ RUNNING
2024-09-05 18:02:29 App\Actions\Server\StopSentinel .......... 178.03ms DONE
2024-09-05 18:02:29 App\Actions\Server\StopSentinel ................ RUNNING
2024-09-05 18:02:29 App\Actions\Server\StopSentinel .......... 115.47ms DONE
2024-09-05 18:02:29 App\Actions\Server\StopSentinel ................ RUNNING
2024-09-05 18:02:29 App\Actions\Server\StopSentinel .......... 101.16ms DONE
2024-09-05 18:02:29 App\Actions\Server\StopSentinel ................ RUNNING
2024-09-05 18:02:29 App\Actions\Server\StopSentinel .......... 109.87ms DONE
2024-09-05 18:02:29 App\Actions\Server\StopSentinel ................ RUNNING
2024-09-05 18:02:29 App\Actions\Server\StopSentinel ................ RUNNING
2024-09-05 18:02:29 App\Actions\Server\StopSentinel ................ RUNNING
2024-09-05 18:02:30 App\Actions\Server\StopSentinel .......... 795.50ms DONE
2024-09-05 18:02:30 App\Actions\Server\StopSentinel ................ RUNNING
2024-09-05 18:02:30 App\Actions\Server\StopSentinel .......... 373.49ms DONE
2024-09-05 18:02:30 App\Actions\Server\StopSentinel .......... 552.07ms DONE
2024-09-05 18:02:30 App\Jobs\CleanupHelperContainersJob ............ RUNNING
2024-09-05 18:02:30 App\Jobs\CleanupHelperContainersJob ...... 136.84ms DONE
2024-09-05 18:02:30 App\Actions\Server\StopSentinel .......... 850.23ms DONE
2024-09-05 18:02:30 App\Jobs\CoolifyTask ........................... RUNNING
2024-09-05 18:02:30 App\Jobs\CoolifyTask ..................... 224.56ms DONE
2024-09-05 18:02:30 App\Actions\Server\StopSentinel ................ 1s DONE
2024-09-05 18:02:38 App\Jobs\DatabaseBackupJob ..................... RUNNING
2024-09-05 18:02:38 App\Jobs\DatabaseBackupJob ................ 55.43ms DONE
2024-09-05 18:02:38 App\Jobs\DatabaseBackupJob ..................... RUNNING
2024-09-05 18:02:38 App\Jobs\DatabaseBackupJob ................ 14.55ms FAIL
2024-09-05 18:02:46 App\Jobs\DatabaseBackupJob ..................... RUNNING
2024-09-05 18:02:46 App\Jobs\DatabaseBackupJob ................ 46.55ms DONE
2024-09-05 18:02:46 App\Jobs\DatabaseBackupJob ..................... RUNNING
2024-09-05 18:02:46 App\Jobs\DatabaseBackupJob ................ 10.32ms FAIL
In Kernel.php line 142:
Attempt to read property "settings" on null
Version
v4.0.0-beta.329
Cloud?
- Yes
- No
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 19 (3 by maintainers)
Didn’t realize you’re the core team 😃 I subbed to the PR so should get a notification when it’s released.
I’ll be checking:
The latter two were failing I believe due to the status getting stuck
In ProgressYes that is fine.
Awesome news @peaklabs-dev thanks for your work!
Since I use coolify on the cloud only - is it alright if I test once the next version is deployed? Since the team is rolling out updates quite often should not be that long I suppose. Let me know if that’s alright please.
@AkashDPA I added a bounty on the parent issue as well as one here if you like to take a look at this. Cheers!