Backup errors starting/stopping container manager

007revad / Synology_app_mover

Easily move Synology packages from 1 volume to another volume

MIT License

416 stars 26 forks source link

Backup errors starting/stopping container manager #140

Open enieuwy opened 2 days ago

enieuwy commented 2 days ago

I've tried to backup Container Manager (only). Reports size as 276GB. Containers are successfully exported, but then I receive the error:

Removing dangling docker images
Line 569: ERROR Stopping Container Manager failed!
progstatus called from package_stop line 647 (v4.2.75)

In the Synology GUI, the container manager package hung at "stopping". After rebooting the NAS, container manager was stopped so I tried the backup task again. This time it failed to start:

Ready to Backup Container Manager to /volume1/backups? [y/n]
y

Line 569: ERROR Starting Container Manager failed!
progstatus called from package_start line 670 (v4.2.75)

Perhaps it just didn't wait long enough, because container manager successfully started after this error.

007revad commented 2 days ago

The script has a 5 minute timeout when stopping and starting packages. I added the timeout in case a package hangs so it won't prevent other packages from being backup or restored if "all" packages were selected.

I could change it to only use the timeout if more than 1 package is selected.

I'm curious how long Container Manager takes to start for you. Can you stop Container Manager then start it and time how long it takes?

enieuwy commented 2 days ago

I have about 71 containers. System resources aren't being taxed during the start/stop (much headroom remains). Watching the logs shows each container is stopped sequentially, taking 3-10 seconds each.

In total, it took 11m35s to stop Container Manager via the UI.

enieuwy commented 2 days ago

Restarting from the UI took 14m45s

007revad commented 2 days ago

That's a lot longer than I expected.

Do you want to try this new version. https://github.com/007revad/Synology_app_mover/releases/tag/v4.2.76

007revad commented 2 days ago

According to my math

Stopping 71 containers took an avg of 9.79 seconds each.
Starting 71 containers took an avg 12.46 seconds each.

I could get the number of containers and multiply it 15 seconds then warn the user how many minutes starting or stopping could take.

Then set the timeout to that number plus 5 minutes.

007revad commented 9 hours ago

Fixed in https://github.com/007revad/Synology_app_mover/releases/tag/v4.2.77

Changed timeout for starting and stopping apps from 5 minutes to 30 minutes.
- Container Manager with lots of containers takes longer than 5 minutes to stop or start.
Changed to only use the timeout when there is more than 1 app to backup or restore.