On Thu, 1 Apr 2004, Etienne Goyer wrote: > Any idea what is causing the signal 11 ? I wonder if it could be > related to the first two issue in any way. > > I am currently writing a mechanism to watch over the mupdate service and > page/restart the service int he event of a failure. Would there be a > way to have master monitor its children and restart mupdate on failure ?
If you use cyrus 2.2, mupdate should restart automatically almost immediately. Otherwise, I'll need to see a core dump backtrace (and since it is a threaded process, it is likely that getting a useful one will be hard). I think the only times I ever saw our 2.1 mupdate master crash is when it ran out of file descriptors... (This is also fixed with some configurable limits in 2.2) -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper --- Home Page: http://asg.web.cmu.edu/cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
