Segmentation fault VOS container

Dear all,

we have deployed VOS as docker since a couple of year now (we use tenforce/virtuoso).
Yesterday we got the following segmentation fault error by restarting the container:

2/14/2019 4:59:05 PM15:59:05 
Unknown macro: { Loading plugin 1} 
2/14/2019 4:59:05 PM15:59:05 
Unknown macro: { Loading plugin 2} 
2/14/2019 4:59:05 PM15:59:05 
Unknown macro: { Loading plugin 3} 
2/14/2019 4:59:05 PM15:59:05 OpenLink Virtuoso Universal Server
2/14/2019 4:59:05 PM15:59:05 Version 07.20.3217-pthreads for Linux as of Sep 29 2016
2/14/2019 4:59:05 PM15:59:05 uses parts of OpenSSL, PCRE, Html Tidy
2/14/2019 4:59:05 PM15:59:05 Database version 3126
2/14/2019 4:59:05 PM15:59:05 SQL Optimizer enabled (max 1000 layouts)
2/14/2019 4:59:06 PM15:59:06 Compiler unit is timed at 0.000142 msec
2/14/2019 4:59:08 PM15:59:08 Roll forward started
2/14/2019 4:59:08 PM15:59:08 3 transactions, 185 bytes replayed (100 %)
2/14/2019 4:59:08 PM15:59:08 Roll forward complete
2/14/2019 4:59:08 PM15:59:08 Checkpoint started
2/14/2019 4:59:08 PM15:59:08 Checkpoint finished, log reused
2/14/2019 4:59:10 PM15:59:10 HTTP/WebDAV server online at 8890
2/14/2019 4:59:10 PM15:59:10 Server online at 1111 (pid 11)
2/14/2019 5:11:53 PM/virtuoso.sh: line 57: 11 Segmentation fault (core dumped) virtuoso-t +wait +foreground

Don’t know is related to the specific container or to Virtuoso in general.
Could someone help on that?

Sincerely
Pasquale

The error clearly reports that Virtuoso core dumped about 12mins after starting, the question is what causes it to crash ?

Was a core file created in the database directory ?

I also note you are running an old 07.20.3217 build from 2016, and would recommend updating to use the latest Virtuoso open source 07.20.3230 docker container

You should also review the current virtuoso.log file to see if any errors are being reported there. Also, run an integrity check on the database on startup, and if the database does have any corruption, perform database recovery as detailed in the above document, or restore from backup which I would hope you have in place ?