search for: avoiding

Hi! We have an Asterisk Bussines Edition ABE-A.1-6 on a PowerEdge 2850 with 4Gb RAM. It was working 24/7 without any for a month, but for not related causes I rebooted it a week ago. Yesterday the machine suddenly stop working, with a kernel panic. We was watching logs, and found in /var/log/asterisk just before the machine hung the messages posted avobe(is the first time we see it). Anyone

Hello list, today I experienced the following for the first time : [Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock for channel '0x114af2c0' [Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock for channel '0x114af2c0' [Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock for channel '0x114af2c0' [Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock for chan...

...calls to the chan_sip. System from that point on reports the following in the logs. Dec 13 12:07:04 DEBUG[16415] chan_zap.c: Took Zap/1-1 off hook Dec 13 12:07:04 VERBOSE[16415] logger.c: -- Executing Wait("Zap/1-1", "1") in new stack Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80' Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80' Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial deadlock for 'SIP/100-09883f80' Dec 13 12:07:04 DEBUG[2049] channel.c: Avoiding initial dea...

Dec 1 12:08:43 WARNING[6189]: channel.c:495 ast_channel_walk_locked: Avoided deadlock for 'SIP/2502-6303', 10 retries! Dec 1 12:08:44 WARNING[6189]: channel.c:495 ast_channel_walk_locked: Avoided deadlock for 'SIP/2502-6303', 10 retries! Dec 1 12:08:44 WARNING[6189]: channel.c:495 ast_channel_walk_locked: Avoided deadlock for 'SIP/2502-6303', 10 retries! what does this

For some reason we are seeing "Avoiding deadlock for channel" in our Asterisk logs, the logs are getting filled up with an amazing speed around 12000 lines a second, and all of them are "Avoiding deadlock". What could be the potential reason for this to be happening? The Asterisk is used as auto dialler, therefore differen...

Dear all,    I am having a recurring problem when I attempt to conduct a GLM.  Here is what I am attempting (with fake data): First, I created a txt file, changed the directory in R (to the proper folder containing the file) and loaded the file: #avoid<-read.table("avoid.txt",header=TRUE);avoid #  treatment feeding avoid noavoid #1   control  nofeed     1     357 #2  

Dear users, Couple of days ago I have updated my * to 1.2.4 with ZAP 1.2.3 Since the upgrade I am having these problems: Feb 7 16:21:18 WARNING[387] channel.c: Avoided deadlock for '0x91a8b20', 10 retries!$ Feb 7 16:23:16 WARNING[16176] channel.c: Avoided deadlock for '0x91a8b20', 10 retries!$ Feb 7 16:23:28 WARNING[16176] channel.c: Avoided deadlock for '0x91a8b20',

Hi, My asterisk sometimes stop responding to iax calls. In the log, I've found this: Mar 29 13:35:45 DEBUG[8386] channel.c: Avoiding initial deadlock for 'IAX2/trunkjstpcn-3' Mar 29 13:35:45 DEBUG[13002] chan_sip.c: update_call_counter(1409) - decrement call limit counter Mar 29 13:35:45 DEBUG[8386] channel.c: Avoiding initial deadlock for 'IAX2/trunkjstpcn-3' Mar 29 13:35:45 DEBUG[8386] channel.c: Avoiding in...

Hello, I have previously open a topic on the mailing list about deadlocking on Asterisk 1.2.35. After upgrading to 1.4.29.1 we still experienced the same problem : Mar 5 12:05:56] DEBUG[8647] channel.c: Avoiding initial deadlock for channel '0xb7689840' [Mar 5 12:06:41] DEBUG[7130] channel.c: Avoiding deadlock for channel '0xb7c04788' [Mar 5 12:06:41] DEBUG[7130] channel.c: Avoiding deadlock for channel '0xb7c04788' [Mar 5 12:06:51] DEBUG[8647] channel.c: Avoiding initial dead...

We've experienced the same problem twice now in the past month. The asterisk pid stops responding. We aren't able to connect to the CLI and all calls are dropped. The lots are pretty bare as well. This is the message log: Oct 24 09:12:35 WARNING[20711] channel.c: Avoided initial deadlock for '0x8444a70', 10 retries! Oct 24 09:12:35 WARNING[20711] channel.c: Avoided initial

Could anyone tell me what happened here - we lost all active calls around this time. I've included more detail below. Jul 15 14:16:20 WARNING[4225] chan_zap.c: [Span 0 D-Channel 0] PRI: ACK received for '1' outside of window of '0' to '0', restarting Jul 15 14:16:20 WARNING[4225] chan_zap.c: No D-channels available! Using Primary on channel anyway 16! Jul 15

The Wine development release 1.5.17 is now available. What's new in this release (see below for details): - Sub-pixel font anti-aliasing in the DIB engine. - Support for automatic installation of ActiveX controls. - Automatic fallback to TLS 1.0 for secure connections. - Beginnings of the DirectWrite text analyzer. - Better handling of font outlines in OpenGL. - Various bug fixes.

This creates libnbdkit.so as discussed in the following thread: https://www.redhat.com/archives/libguestfs/2020-March/thread.html#00203 test-delay-shutdown.sh fails for unclear reasons. This series starts by reverting "tests: Don't strand hung nbdkit processes" which is because several other tests fail randomly unless I revert this patch. I didn't investigate this yet so it

Anyone have any idea what's causing this or how to debug it? I'm pretty sure the root cause is with chan_sccp.so, but not sure how to prove it. I recently upgraded from CVS-head to 1.2.1 and the chan_sccp from 12-17-2005. Now, once or twice a week, I get this on the console: Jan 31 10:39:08 WARNING[10586]: channel.c:784 channel_find_locked: Avoided deadlock for '0xbf1013e0',

Hello all, I'm running Asterisk 1.2.35 with chan_mgcp activated. The process host around 2,4K users. Along the day I've got some debug reports like : Feb 24 22:25:42 DEBUG[28546] channel.c: Avoiding deadlock for 'MGCP/aaln/1 at 028421223635-1' Feb 24 22:29:04 DEBUG[28670] channel.c: Avoiding initial deadlock for 'MGCP/aaln/1 at 028421223635-1' Then, at random time (around 10~16 hours after a restart), Asterisk comes into deadlocks : Feb 25 16:28:22 WARNING[8149] channe...

My Asterisk is Asterisk 1.2.30.2 currently running on viciserver the problem is : Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided deadlock for '0x861f6d8', 9 retries! Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided deadlock for '0x85a6420', 9 retries! Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided

...returning 0 Jul 29 09:38:55 WARNING[896] res_agi.c: Connect to 'agi://127.0.0.1/callhangup' failed: Bad file descriptor Jul 29 09:38:55 VERBOSE[896] logger.c: == Spawn extension (route-out, h, 1) exited non-zero on 'Local/1@route-ou t-eeae,2' Jul 29 09:38:55 DEBUG[893] channel.c: Avoiding deadlock for 'Local/1@route-out-eeae,2' Jul 29 09:38:55 DEBUG[893] channel.c: Avoiding deadlock for 'Local/1@route-out-eeae,2' Jul 29 09:38:55 DEBUG[893] channel.c: Avoiding deadlock for 'Local/1@route-out-eeae,2' Jul 29 09:38:55 DEBUG[893] channel.c: Avoiding deadlock for &...

I'm trying to code more R-like and avoid loops. Here is an example I'm having a hard time getting away from loops with, and the real matrices are rather large, and the computation is too time-consuming. ### Dimensions N <- 2 M <- 3 P <- 4 ### Array and Matrices nu <- array(NA,dim=c(N,M,P)) Lambda <- matrix(1:12,P,M) F <- matrix(1:8,N,P) ### Loop to avoid for (i in 1:N)

The Wine development release 1.5.11 is now available. What's new in this release (see below for details): - Multi-channel support in the ALSA driver. - Removal of the big X11 lock. - Support for pair positioning adjustments in Uniscribe. - More I/O stream implementations in the C++ runtime. - Various bug fixes. The source is available from the following locations:

Hello list, I have plots with long strings in main=, ylab= or xlab=. So, in I my script I use break long lines to avoid lines hiden on my monitor and in sweave document pages. I use graphics like this plot(1, main="aaaaaaaaaaaaaaaaaaaa bbbbbbbbbbbbbbbbbbbb") but I would like a plot result like this plot(1, main="aaaaaaaaaaaaaaaaaaaa bbbbbbbbbbbbbbbbbbbb") I