| 1 |
"unable to join environment" error |
| 2 |
---------------------------------- |
| 3 |
|
| 4 |
This error is caused if you build Berkley DB 4 with threading support, |
| 5 |
but do not then link the pthreads library to Cyrus. This is commonly |
| 6 |
caused by a Linux distribution which supplies the pre-threaded library |
| 7 |
version. |
| 8 |
|
| 9 |
One workaround is to rebuild the db4 library without thread support. |
| 10 |
Another is provided by Scott Adkins ([email protected]):: |
| 11 |
|
| 12 |
I talked to SleepyCat about it and they suggested making sure that the |
| 13 |
threads library was being linked into the IMAP server. It used to be |
| 14 |
that when compiling db3 that the IMAP server would automatically link in |
| 15 |
the threads library, probably because of an rpath listed in the db3 |
| 16 |
shared library. They must have changed something with db4, since the |
| 17 |
threads library is no longer linked into applications if they link |
| 18 |
against the db4 library. |
| 19 |
|
| 20 |
As it turns out, linking with threads (I believe I simply included the |
| 21 |
``-pthread CC`` command line option to have that happen) caused the join |
| 22 |
errors to go away. I was still having some flakiness with db4 though... |
| 23 |
|
| 24 |
Starting with Cyrus 2.2.1, it is possible to build without linking |
| 25 |
Berkeley DB at all, which may be a viable option for some sites. |
| 26 |
|
| 27 |
|