Re: crashing at startup?
e...@cirr.com (Eric Schnoebelen) writes: > I've not see anything like that on NetBSD 6_STABLE/alpha. I do > see mu-conference crashing semi-regularly, as well as it > occasionally running away (but not nearly as much after the > last set of patches.) It's cool you are running this on alpha. The sm crash was only once. I am seeing ongoing mu-conference crashes, which look like they are hitting asserts in glib unlocking mutexes. I have built stuff with -g but haven't flipped it to run yet (production box with only 66 active connections right now, lower than the usual ~90). > Anything odd/unusual in the sm.xml configuration file? No. Just switching logging to file, setting hostname, and stuff you basically have to edit. pgp3biTOXDYYj.pgp Description: PGP signature
Re: crashing at startup?
Greg Troxel writes: - On a netbsd-5 i386 box (xen domU) that is otherwise stable, with jabberd - 2.3.2 and mu-conference 0.8.81, on boot we saw: - - Feb 6 05:33:34 foo /netbsd: pid 317 (sm), uid 1001: exited on signal 11 (c - ore not dumped, err = 13) - Feb 6 05:34:26 foo /netbsd: pid 540 (mu-conference), uid 1001: exited on s - ignal 5 (core not dumped, err = 13) - - Once up, after restarting servers with "/etc/rc.d/jabberd restart" (and - then muc), the jabberd2 programs were stable, but mu-conference has - occasional crashes. [...] - Other than getting a core dump and examining it, which is the obvious - thing to do, I'm curious if anyone else has seen something like this. I've not see anything like that on NetBSD 6_STABLE/alpha. I do see mu-conference crashing semi-regularly, as well as it occasionally running away (but not nearly as much after the last set of patches.) Anything odd/unusual in the sm.xml configuration file? fyi: I'm running 2.3.2nb8 from pkgsrc-2014Q4 (not that anything has changed in pkgsrc since Q4 was branched.) -- Eric Schnoebelene...@cirr.com http://www.cirr.com I'm not a minion of evil I'm upper management.
crashing at startup?
On a netbsd-5 i386 box (xen domU) that is otherwise stable, with jabberd 2.3.2 and mu-conference 0.8.81, on boot we saw: Feb 6 05:33:34 foo /netbsd: pid 317 (sm), uid 1001: exited on signal 11 (core not dumped, err = 13) Feb 6 05:34:26 foo /netbsd: pid 540 (mu-conference), uid 1001: exited on signal 5 (core not dumped, err = 13) Once up, after restarting servers with "/etc/rc.d/jabberd restart" (and then muc), the jabberd2 programs were stable, but mu-conference has occasional crashes. I noticed that the order of starting up the components is c2s sm s2s router muc which strikes me as odd (why isn't router first). But, it's not like these are fully up before the parent exits, and in theory all daemons should cope/retry. Other than getting a core dump and examining it, which is the obvious thing to do, I'm curious if anyone else has seen something like this. Greg pgp2HHXicyxbe.pgp Description: PGP signature
