Closed apavelm closed 2 months ago
Hi @apavelm :wave:
It looks like you've got a disk corruption that's preventing Seq from starting. You should be able to recover your instance by following the backup and restore process.
If you're running in Azure Container Instances, we recommend using SQL Azure as your document store because it's more reliable than Azure Files. If you use a SQL Azure document store, your log data will still be stored on Azure Files, but the scope of corruptions there are smaller. Those docs for SQL Azure are based on Windows, but in Docker the instructions are the same except that the seq
command is called seqsvr
.
Hi @KodrAus ! Thank you for the link. Indeed, I'm using Azure Files. I'm trying to restore, but no luck so far. Anywaym thank you!
Hmm, what if you move/rename your entire C:\ProgramData\Seq\Documents
folder before attempting to restore the backup? If you rename it to C:\ProgramData\Seq\DocumentsBackup
then the restore should try work off a fully clean state.
Hmm, what if you move/rename your entire
C:\ProgramData\Seq\Documents
folder before attempting to restore the backup? If you rename it toC:\ProgramData\Seq\DocumentsBackup
then the restore should try work off a fully clean state.
I tried this option as well. Didn't help. So, I've just dropped everything and reconfigured all parameters manually from the scratch
I'm running seq inside docker, last night Seq unexpectedly stopped working. And refuse to restart. Exception stacktrace is below: