|
Minimsever update won't run
|
|
12-09-2025, 17:01
(This post was last modified: 12-09-2025 17:35 by simoncn.)
Post: #39
|
|||
|
|||
RE: Minimsever update won't run
(11-09-2025 15:53)steamfan Wrote: The export-import approach did not work. i got error messages while importing. It was faster to set up a new container from scratch. I have found a possible solution for this. I have made a change to the MinimServer script launched by the container. The updated script checks for a launch error and waits for 5 minutes before exiting. This gives enough time for the user to start a terminal inside the container and either retrieve important data or make changes to fix the problem. The only problem with my current implementation is that no error message is shown to the user until the 5 minute timeout has expired. There is a message in the container log but the user needs to open the container log to see it. This means the user will think the container is hung (or very slow) unless they open the container log. Do you know of any way for a container to show a message that pops up in Synology Container Manager with no user action needed? Ideally this would work for other container managers as well. Edit: I have another idea. As the container has a mounted volume for the host MinimServer shared folder, there could be a setting in a file there to tell the container to wait for a specified time after abnormal exit. The user would see the error, then activate this setting, then restart the container with enough wait time to do whatever recovery/repair is needed. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



