Summary: | MongoDB or vim in jail hang during mi_switch | ||
---|---|---|---|
Product: | Base System | Reporter: | Randy Westlund <rwestlun> |
Component: | threads | Assignee: | freebsd-threads (Nobody) <threads> |
Status: | Closed Not A Bug | ||
Severity: | Affects Some People | CC: | jail, pi, sirl33tname |
Priority: | --- | ||
Version: | 10.2-RELEASE | ||
Hardware: | amd64 | ||
OS: | Any |
Description
Randy Westlund
2015-10-03 03:13:28 UTC
I'm seeing the same thing with vim in a separate jail. This jail launches okay, but vim won't start. root@jakory:~ # procstat -kk 37514 PID TID COMM TDNAME KSTACK 37514 101411 vim - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_lock_umutex+0x1f74 __umtx_op_wait_umutex+0x78 amd64_syscall+0x357 Xfast_syscall+0xfb root@jakory:~ # procstat -r 37514 PID COMM RESOURCE VALUE 37514 vim user time 00:00:00.032873 37514 vim system time 00:00:00.064690 37514 vim maximum RSS 12132 KB 37514 vim integral shared memory 23760 KB 37514 vim integral unshared data 1260 KB 37514 vim integral unshared stack 1152 KB 37514 vim page reclaims 437 37514 vim page faults 285 37514 vim swaps 0 37514 vim block reads 184 37514 vim block writes 0 37514 vim messages sent 0 37514 vim messages received 0 37514 vim signals received 0 37514 vim voluntary context switches 244 37514 vim involuntary context switches 15 root@jakory:~ # procstat -t 37514 PID TID COMM TDNAME CPU PRI STATE WCHAN 37514 101411 vim - 0 126 sleep umtxn This is clearly not specific to MongoDB. Appears jail-related as well? Yes. So far, I've only seen this in jails. I saw the same thing today on a system, with git, mysql and mongodb in different jails. Is there any workaround for it? Not that I've found. This problem is over my head. Even if I restart the server, it's the same programs in the same jails that hang during the context switch. In the mean time, I've moved my services to a VPS (with no jails) because I can't get my jails to start. I'm not updating any system with working jails, for fear of my other servers breaking. (In reply to Sir l33tname from comment #4) Nevermind, I just missed to update my libs to 10.2 in the base jail. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203765 I've recreated the base jail, and the problem seems to be resolved. My guess is that ezjail didn't handle an upgrade properly. Closing. |