I  TXN      [conn5298] transaction parameters:{ lsid: { id: UUID("d731e818-38c5-4aef-ab08-789e4586791b"), uid: BinData(0, 830872FC3F605AFFB6F640ED87DB86D55DCD03BE1E29155D54CDA151B743588A) }, txnNumber: 199, autocommit: false, readConcern: { level: "snapshot" } }, readTimestamp:Timestamp(0, 0), keysExamined:64 docsExamined:50 terminationCause:committed timeActiveMicros:15563 timeInactiveMicros:137671 numYields:0 locks:{ ReplicationStateTransition: { acquireCount: { w: 2 } }, Global: { acquireCount: { w: 1 } }, Database: { acquireCount: { w: 1 } }, Collection: { acquireCount: { w: 3 } }, Mutex: { acquireCount: { r: 3 } } } storage:{} wasPrepared:0, 153ms
                  
                  
                  2022-04-27T08:44:29.959+0000 I  CONTROL  [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
                  
                  
                  2022-04-27T08:44:29.960+0000 I  REPL     [RstlKillOpThread] Starting to kill user operations
                  
                  
                  2022-04-27T08:44:29.961+0000 I  REPL     [RstlKillOpThread] Stopped killing user operations
                  
                  
                  2022-04-27T08:44:31.107+0000 I  NETWORK  [conn5304] end connection 10.255.0.235:51446 (12 connections now open)
                  
                  
                  2022-04-27T08:44:39.961+0000 I  REPL     [RstlKillOpThread] Starting to kill user operations
                  
                  
                  2022-04-27T08:44:39.961+0000 I  REPL     [RstlKillOpThread] Stopped killing user operations
                  
                  
                  2022-04-27T08:44:39.963+0000 I  STORAGE  [signalProcessingThread] Failed to stepDown in non-command initiated shutdown path ExceededTimeLimit: No electable secondaries caught up as of 2022-04-27T08:44:39.961+0000. Please use the replSetStepDown command with the argument {force: true} to force node to step down.
                  
                  
                  2022-04-27T08:44:39.974+0000 I  NETWORK  [signalProcessingThread] shutdown: going to close listening sockets...
                  
                  
                  2022-04-27T08:44:39.974+0000 I  NETWORK  [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
                  
                  
                  2022-04-27T08:44:39.975+0000 I  -        [signalProcessingThread] Stopping further Flow Control ticket acquisitions.
                  
                  
                  2022-04-27T08:44:39.976+0000 I  REPL     [signalProcessingThread] shutting down replication subsystems
                  
                  
                  2022-04-27T08:44:39.976+0000 I  REPL     [signalProcessingThread] Stopping replication reporter thread
                  
                  
                  2022-04-27T08:44:39.976+0000 I  REPL     [signalProcessingThread] Stopping replication fetcher thread
                  
                  
                  2022-04-27T08:44:39.976+0000 I  REPL     [signalProcessingThread] Stopping replication applier thread
                  
                  
                  2022-04-27T08:44:39.979+0000 I  REPL     [rsSync-0] Finished oplog application
                  
                  
                  
                  
                  
                  что может быть не так?
                  
                  
                
ключевое CONTROL [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends гуглеж показал что тут либо проблемы с настройками https://stackoverflow.com/questions/38059330/mongodb-crash-got-signal-15-terminated либо ктото действительно прибивает монгу - тут настраивать аудит действий и отсматривать системные логи ну и на всякий раз уж итак то и дело стопается обновитесь до последний версий
Обсуждают сегодня