Mongo docker error

Kobo On Your Own Server
, ,
1

Hi! i’m having some trouble with the kobo-docker implementation, basically from time to time the server dies and with a restart works again, this happened from time to time but know it’s almost daily
i tracked down the error to the docker container that shows this message:

2022-03-08T14:04:44.399+0000 I CONTROL  [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
2022-03-08T14:04:44.399+0000 I NETWORK  [signalProcessingThread] shutdown: going to close listening sockets...
2022-03-08T14:04:44.399+0000 I NETWORK  [signalProcessingThread] closing listening socket: 7
2022-03-08T14:04:44.399+0000 I NETWORK  [signalProcessingThread] closing listening socket: 8
2022-03-08T14:04:44.399+0000 I NETWORK  [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
2022-03-08T14:04:44.399+0000 I NETWORK  [signalProcessingThread] shutdown: going to flush diaglog...
2022-03-08T14:04:44.399+0000 I FTDC     [signalProcessingThread] Shutting down full-time diagnostic data capture
2022-03-08T14:04:44.402+0000 I STORAGE  [signalProcessingThread] WiredTigerKVEngine shutting down
2022-03-08T14:04:44.580+0000 I STORAGE  [signalProcessingThread] shutdown: removing fs lock...
2022-03-08T14:04:44.580+0000 I CONTROL  [signalProcessingThread] now exiting
2022-03-08T14:04:44.580+0000 I CONTROL  [signalProcessingThread] shutting down with code:0

so the mongo container seems to be killing himself for some reason
any help is appreciated
thanks!

2

It could be running out of RAM; what are your machine specs?

3

Hi! thanks for replying! the server has 4gib of ram and from what i’m seeing it’s not all being used (it’s at 50%) and didn’t notice any spikes

and this is the usage for the container

MEM USAGE / LIMIT MEM %
33.65MiB / 3.845GiB 0.85%

thanks in advance