You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
just discovered, as I moved my simpexmq instance to a new server: With clean install via docker, the smp server container immediately stops. Unfortunately without leaving any error in the logs.
Tried some earlier releases and finally drilled it down to the following solution:
Clean install v6.06 and after that upgrading (while keeping the files in their folders) to the more recent releases keeps everything up and running.
Unfortunately (as mentioned above) there is nothing in the logs that could give even the smallest hint, why the container crashes.
We were able to reproduce this beaviour on two machines (both Synology NAS, running DSM 7.2).
Unfortunately I'm far from being tech savy enough to find out, what changed after v6.06 that causese this issue. I'm happy to have the server up and running (with the help of a friend of mine).
But I guess, for the developers it would be relatively easy to check this and find the reason.
The text was updated successfully, but these errors were encountered:
Hi there,
just discovered, as I moved my simpexmq instance to a new server: With clean install via docker, the smp server container immediately stops. Unfortunately without leaving any error in the logs.
Tried some earlier releases and finally drilled it down to the following solution:
Clean install v6.06 and after that upgrading (while keeping the files in their folders) to the more recent releases keeps everything up and running.
Unfortunately (as mentioned above) there is nothing in the logs that could give even the smallest hint, why the container crashes.
We were able to reproduce this beaviour on two machines (both Synology NAS, running DSM 7.2).
Maybe it helps, here is the compose file content:
Unfortunately I'm far from being tech savy enough to find out, what changed after v6.06 that causese this issue. I'm happy to have the server up and running (with the help of a friend of mine).
But I guess, for the developers it would be relatively easy to check this and find the reason.
The text was updated successfully, but these errors were encountered: