Paulo Scardine wrote: > Paulo Scardine escreveu: > >> Hi people. >> >> Sometimes I got unicall channels locked. >> >> Command "UC show channels" shows strange numeric status instead of >> "idle". Command "show channels" reports zero active channels but a >> number greater than zero (actually the number of unicall channels with >> numeric states) active calls. >> >> On the CLI, messages like "channel.c:885 channel_find_locked: Avoided >> initial deadlock for '0xb5ebafe8', 10 retries!" show up from times to >> times. I found no correlation with any other error message on the logs. >> >> Command "stop now" will not stop callweaver, I have to issue a "kill -9" >> and restart callweaver to clean up. >> > > I corrected another bug involving cdr_pgsql database with the wrong > charset and UTF8 characters on the callerid, and the unicall lockups > disappeared. Weird. Seems to be some race condition related to cdr errors. > Oh, good. :-)
We know there are lots of nasty locking conditions in the current code, just as there are in Asterisk. I guess this is probably one of those, rather than something Unicall specific. There are some threading issues I know about in the current Unicall code, but those only affect protocols like ISDN, where a single signaling channel handles multiple speech channels. By the time the first protocol module of that kind is released, those will be taken care of in the core Unicall library. Steve _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
