Re: SIGSEGV on mdb_txn_begin / __pthread_mutex_lock_full

2017-06-19 Thread Howard Chu
opensou...@gmx-topmail.de wrote: Are you running multiple Docker instances on the same database? AFAIK that won't work because of Docker's munging with POSIX namespaces. No, it is a Single Docker instance. Actually, I saw the same thing happening on a Ubuntu box, so it should not be related to

RE: SIGSEGV on mdb_txn_begin / __pthread_mutex_lock_full

2017-06-19 Thread opensource
> Are you running multiple Docker instances on the same database? AFAIK that > won't work because of Docker's munging with POSIX namespaces. No, it is a Single Docker instance. Actually, I saw the same thing happening on a Ubuntu box, so it should not be related to Docker. I restructured the CI

Re: SIGSEGV on mdb_txn_begin / __pthread_mutex_lock_full

2017-06-18 Thread Howard Chu
opensou...@gmx-topmail.de wrote: We are using LMDB and are running a big number of tests on a CI server (Debian via Docker, Xenon CPU). Are you running multiple Docker instances on the same database? AFAIK that won't work because of Docker's munging with POSIX namespaces. The crash happens