<div class="gmail_quote">2009/10/12 Håkon Nessjøen <span dir="ltr"><<a href="mailto:haakon@avelia.no">haakon@avelia.no</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>I'm getting a bounch of these:<br>[Oct 12 13:26:53] DEBUG[7738]: app_queue.c:3364 try_calling: Skipping dialing interface 'DAHDI/g0' since it has already been dialed<br>[Oct 12 13:26:53] DEBUG[7738]: app_queue.c:3364 try_calling: Skipping dialing interface 'DAHDI/g0' since it has already been dialed<br>
<br>Actually every time a user calls into a queue, this message is shown one extra time. So the amount of these messages grow proportionally with the number of calls gone through the system.<br>(after 5 calls, it shows 5 notices when the user enters the queue)<br>
<br>So after 2000 calls, you can think the notices are many for each queue call.<br><br>This didn't seem too critical, since it wass "DEBUG" messages, not warnings. But now the server suddenly died with a lot of calls going on, and the last message it wrote before it segfaulted was indeed the "skipping dialing interface" message.<br>
<br>Anyone other than me, that have had problems with this?<br><br>Regards,<br><font color="#888888">Håkon Nessjøen<br>
</font></blockquote></div><br>Seems like this has something to do with Realtime. Have anyone else had problems with this?<br><br>If I do a "queue show 33" where 33 is a name of one of my queues, i get a whole bunch of:<br>
40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls (last was 5721 secs ago)<br> 40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls (last was 5523 secs ago)<br> 40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls yet<br>
40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls (last was 5362 secs ago)<br> 40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls yet<br> 40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls yet<br>
40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls yet<br> 40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls (last was 5131 secs ago)<br> 40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls (last was 4437 secs ago)<br>
40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls yet<br> 40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls yet<br> 40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls (last was 3904 secs ago)<br>
40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls yet<br><br>All this (and much more, this was just a snippet) even though member 40 is indeed only 1 member, not several. So it seems like each time it tries to call the queuemember, it generates a new dynamic member in the queue. Even though the member info has not changed.<br>
<br>Håkon<br>