On Wed, 4 Oct 2006 15:27:23 +0100 Stuart Henderson <[EMAIL PROTECTED]> wrote:
> On 2006/10/04 23:13, Steve wrote: > > I have an issue where intermittently asterisk stops responding. > > > > show channels shows a call locked in progress. > > stop now is ineffective and just returns a cli prompt. > > after issuing a stop now all other commands just return a > cli prompt > > kill pid requires several attempts before the process dies. > > > > After it is restarted thing are happy again. > > > > I have had this problem in the past on versions that were provide with > > 3.8 release and 3.9 release. > > I've seen similar things on linux, I'm not certain but you could quite > possibly be running into an asterisk problem rather than an asterisk-on- > openbsd problem. If so there's a fair chance it's somewhere on > bugs.digium.com but it can take quite some searching, debug log in hand... > > The -current port is now updated to the newest 1.2 release, btw; it's > not difficult to update the old one yourself if you're not running -current. > > We started running into this problem on a production asterisk server (OpenBSD 3.9 i386 and asterisk 1.2.9.1 from packages). We use SIP and IAX2. We were getting to the point where we'd have to reboot the box (and more than once a day at the end) to get asterisk to pass traffic again. The CLI would come up, but any commands entered would just return a command prompt without any effect. Logging would stop, except for some IAX2 peer checks. Registrations to the box would drop. Because we'd been happy with asterisk on FreeBSD for a fax project we were working on (no rxfax on OpenBSD), we moved the configs over to a freshly installed FreeBSD 6.1-i386 box with asterisk 1.2.9.1 from ports, and the problem ceased. It's been running for a couple weeks with no hiccups. That's pretty well torpedoed my argument that it was probably an error we'd introduced in the dialplan... The phone guys here think that the lack of timing from ztdummy is a likely candidate. This is 100% anecdotal & I'd love to be able to provide more debug... the original server is still in the rack, powered off for a bit. If anyone has a good debug strategy for this situation, I could probably get some traffic pointed back at it & wait for asterisk to hang. Frank
