Seq container instance - seq container terminating and restarting #2198
Replies: 4 comments 1 reply
-
|
Hi @rodneytamblyn, thanks for you message. Does There's also a |
Beta Was this translation helpful? Give feedback.
-
|
I think the relevant error is as follows. As I needed to restore service I resorted to resetting seq to default (as I have exported/backed up critical log events using JSON exporter). |
Beta Was this translation helpful? Give feedback.
-
|
It is premium storage. I think the issue might have been that a second container instance that I was trying to deploy started before the first one fully exited. That's my guess. Is it safe to use container stop for a safe shutdown or is there some command I can execute against the container for a safe orderly shutdown: e.g. using AZ commands something similar to |
Beta Was this translation helpful? Give feedback.
-
|
FYI Our Azure Container INstance deployment of Seq has been going well over the last two months. I wanted to redeploy it to add the seq-input-syslog sidecar container, and the only way I can do this is to stop and delete the current instance and replace it with a new instance. This was when the corruption happened. Makes me nervous about upgrading the container. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have seq running in a Azure container instances. Tonight the seq container is terminating and restarting (resulting in logging down).
What is the best way to investigate and resolve these issues?
Is there a trouble shooting guide to investigating and restoring service. I would be OK with starting from scratch if necessary, the main thing is to get service restored.
Beta Was this translation helpful? Give feedback.
All reactions