[Home]

Summary:ASTERISK-25644: No event in queue log when member leaves the queue
Reporter:newborn (newborn838)Labels:
Date Opened:2015-12-22 07:54:12.000-0600Date Closed:2020-01-14 11:14:14.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Applications/app_queue
Versions:11.17.1 Frequency of
Occurrence
Related
Issues:
is related toASTERISK-19793 Only last realtime member of a queue is not actually removed from queue when removed from database
is related toASTERISK-12128 [patch]Log member adding and removing for realtime members
Environment:Attachments:( 0) config_files.txt
Description:I'm using static queues in queues.conf and realtime queue members in PostgeSQL DB table via odbc.

The problem is when i erase everything from queue_members table corresponding to my queue, i have no 'REMOVEMEMBER' event in queue log.
If at least one member is still present in queue, everything is OK, i'm getting this event.

Is this a bug or feature?
Comments:By: Asterisk Team (asteriskteam) 2015-12-22 07:54:14.269-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Rusty Newton (rnewton) 2015-12-22 19:07:58.784-0600

Sounds like a bug, but someone will probably want to look into the code to be sure.

Can you specify which resource and backend modules you are using, provide sanitized configuration (odbc module config, queues.conf table dump, etc).?

If you can then provide steps to reproduce the issue so that we are very clear on exactly what you are doing to reproduce it.
By: newborn (newborn838) 2015-12-23 02:27:19.481-0600

All modules are native, no third-party or custom modules used.
OS is CentOS 6.7 i386

{noformat}
asterisk=> \d queue_member;
                                     Table "public.queue_member"
  Column   |          Type          |                            Modifiers
------------+------------------------+-----------------------------------------------------------------
uniqueid   | integer                | not null default nextval('queue_member_uniqueid_seq'::regclass)
membername | character varying(128) | default ''::character varying
queue_name | character varying(128) | default ''::character varying
interface  | character varying(128) | not null default 'SIP/'::character varying
penalty    | integer                | not null default 0
paused     | character varying(11)  | default ''::character varying
Indexes:
   "queue_member_pkey" PRIMARY KEY, btree (uniqueid)
{noformat}

When i insert values in queue_member and then place a call or type in CLI 'queue show ...', i've got an ADDMEMBER event in queue_log
{noformat}
SELECT * FROM queue_log WHERE id = '59';
id |             time              |  callid  |   queuename    |   agent   |   event   | data1 | data2 | data3 | data4 | data5
----+-------------------------------+----------+----------------+-----------+-----------+-------+-------+-------+-------+-------
59 | 2015-12-23 11:18:21.236065+03 | REALTIME | queue1 | operator2 | ADDMEMBER |       |       |       |       |
{noformat}

Steps to reproduce:

* (Erase everything from queue_member table)
** {{asterisk=> DELETE FROM queue_member;}}
* (Refresh realtime data)
** {{\[~]# asterisk -rx 'queue show queue1'}}

SELECT * FROM queue_log; => last event is ADDMEMBER. I see no REMOVEMEMBER events at all. If at least one member is present in queue1, i'm getting REMOVEMEMBER event with respect to target member\queue.
By: Rusty Newton (rnewton) 2015-12-28 11:25:54.145-0600

Cleaned up your comment to make it readable. Extracted your debug and I'm attaching it to the issue per the guidelines.

In the future please attach debug and config files to the issue as .txt files for accessibility.
By: Rusty Newton (rnewton) 2015-12-30 14:12:07.861-0600

We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information


By: Rusty Newton (rnewton) 2015-12-30 14:13:02.813-0600

Please capture the debug log described in the wiki page. Capture it while you reproduce the issue. We'd like to see what gets logged as the sync happens after you erase all members.

Please capture a second log where you erase all but one member.

Basically a working and failing scenario comparison. Thanks!
By: Asterisk Team (asteriskteam) 2016-01-14 12:00:21.103-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines