So I had this error some days ago - and resolved it by removing the server from the cluster (after a few attempts). Then I re-added it and thought all was good. But yesterday it started again - and over the night it just filled up the disk (log files I guess - but the server is not very communicative at the moment).
The issues started after I restored a backup of the data into our test environment. Before restoring I flushed the database and stopped the Sync.Gateway. One observation was that it took for ages to get it back up and running - I suppose that could be a symptom of the issues we see.
This is the error. What does that mean? And how do I find out what causes this so I can fix it?
Service 'memcached' exited with status 134. Restarting. Messages: 2021-03-27T19:12:02.003070+01:00 CRITICAL /lib64/libc.so.6(abort+0x148) [0x7f4fe15f5000+0x37ac8] 2021-03-27T19:12:02.003076+01:00 CRITICAL /opt/couchbase/bin/../lib/libplatform_so.so.0.1.0() [0x7f4fe41a7000+0xb786] 2021-03-27T19:12:02.003085+01:00 CRITICAL /opt/couchbase/bin/memcached() [0x400000+0x99824] 2021-03-27T19:12:02.003092+01:00 CRITICAL /opt/couchbase/bin/memcached() [0x400000+0x6d96c] 2021-03-27T19:12:02.003098+01:00 CRITICAL /opt/couchbase/bin/../lib/libevent_core.so.2.1.8() [0x7f4fe326f000+0x17107] 2021-03-27T19:12:02.003102+01:00 CRITICAL /opt/couchbase/bin/../lib/libevent_core.so.2.1.8(event_base_loop+0x39f) [0x7f4fe326f000+0x1767f] 2021-03-27T19:12:02.003109+01:00 CRITICAL /opt/couchbase/bin/memcached() [0x400000+0x6baa9] 2021-03-27T19:12:02.003113+01:00 CRITICAL /opt/couchbase/bin/../lib/libplatform_so.so.0.1.0() [0x7f4fe41a7000+0x8f17] 2021-03-27T19:12:02.003119+01:00 CRITICAL /lib64/libpthread.so.0() [0x7f4fe19c3000+0x7ea5] 2021-03-27T19:12:02.003147+01:00 CRITICAL /lib64/libc.so.6(clone+0x6d) [0x7f4fe15f5000+0xfe9fd]
Using Couchbase Community Edition server 6.6.0 build 7909 on CentOS 7