Bug #7918
closedMon hangs at start after upgrading to leveldb-1.12.0-3.fc18.x86_64 from the ceph-extras repo
0%
Description
I had a working 0.72.2 installation using the standard Fedora 18 RPMs.
I upgraded leveldb from 1.7.0-4.fc18 to 1.12.0-3.fc18 from ceph-extras. Afterwards my mon would hang at start.
Even with debug level 20, the only thing logged is:
2014-03-30 20:31:31.829959 7f3c989877c0 0 ceph version 0.72.2 (a913ded2ff138aefb8cb84d347d72164099cfd60), process ceph-mon, pid 21310
I captured a backtrace of the hung process:
#0 0x00007ffff73e6e4d in __lll_lock_wait () from /lib64/libpthread.so.0
#1 0x00007ffff73e2cc1 in _L_lock_885 () from /lib64/libpthread.so.0
#2 0x00007ffff73e2bda in pthread_mutex_lock () from /lib64/libpthread.so.0
#3 0x00007ffff69839f9 in leveldb::port::Mutex::Lock (this=<optimized out>) at port_posix.cc:26
#4 0x00007ffff6966132 in MutexLock (mu=0x7fffffffd518, this=0x7fffffffd2c0) at ../util/mutexlock.h:27
#5 leveldb::DBImpl::Get (this=0x7fffffffd410, options=..., key=..., value=0x0) at db_impl.cc:1098
#6 0x0000000000873921 in LevelDBStore::_get_iterator() ()
#7 0x00000000005d62d7 in KeyValueDB::get_iterator(std::string const&) ()
#8 0x00000000005d63e5 in MonitorDBStore::exists(std::string const&, std::string const&) ()
#9 0x00000000005cf5d1 in main ()
Downgrading to leveldb 1.7.0-4.fc18 fixes the problem and lets the mon start without hanging.
Updated by Ian Colle about 10 years ago
We've pulled those packages until we can figure what's causing this.
Updated by Sage Weil about 10 years ago
- Status changed from New to Won't Fix
we're not going to worry about fc18 at this point; let's focus on making sure the fc10 and centos/rhel stuff works.