High Queues in taskprocessors

1

Hi, can anyone tell me why these queues are so high and are growing day by day? This is a brand new Asterisk install. All it does is answers, plays hello and hangs up.

I also get lots of these messages:

[Mar 15 10:20:51] WARNING[10609][C-00000001]: taskprocessor.c:737 taskprocessor_push: The ‘811ad10a-c567-4e8f-9b50-bb6a367d9c2a’ task processor queue reached 500 scheduled tasks.

13.7.2

axis*CLI> core show taskprocessors

        +----- Processor -----+--- Processed ---+- In Queue -+- Max Depth -+
                 Sorcery                   0            0            0
a6823b23-c605-4533-9eb3-0d61b2344e4f                   1            0            0
9e435d66-b016-47ec-aa5d-8182cd891e52                   2            0            0
4aa00068-b970-4afd-bcf2-697116badb3b               27238            0          221
0afda83b-1426-464b-a39c-f56100bc901c                 298            0            1
21101681-ed6c-46d1-81fa-097bd59e67e5               27139            0          221
           app_voicemail                   0            0            0
5e6c2937-2799-4981-8f9b-a3f3df494723                 297            0            1
4f89920f-25a2-4444-9a5e-abf599b9fb70                   0            0            0
     stasis-core-control                  15            0            3
49697d1f-0aeb-4e83-9b62-0a1fb1dbeb8e                   1            0            0
0db48c9c-1752-4890-a42c-8a45fd11d3c5                 299            0            1
           ast_msg_queue                   0            0            0
               CCSS core                   0            0            0
4a190fc4-2ae1-415b-bb17-673432a499bf                 939            0            1
e24fb0b5-79e2-4d94-b702-c6224f7f1b64               21226            0          148
         Sorcery-control                   1            0            0
2969ee40-6d17-458f-82fd-9404834fddbc                 212            0            0
13a37567-4839-4740-80f3-3f7588dca499                   1            0            0
c55e375d-a031-49d6-8d3d-3cfdf9329f68                   0            0            0
70b91cc2-f352-45b4-a20e-f3d871d32527                 941            0           27
c378567f-3c77-4fc3-b9e7-505145d71195                   1            0            0
             stasis-core                   2            0            0
            hep_queue_tp                 211            0            0
           iax2_transmit                   0            0            0
31febb7d-fb3d-4b8f-bd43-063bcd9eeee8                 940            0            0
        +---------------------+-----------------+------------+-------------+
        26 taskprocessors
2

When Asterisk 13.8.0 is released the names of the taskprocessors will provide more detail about what it is for. From a general perspective though a taskprocessor is a queue of work items. If the act of handling these work items takes a long time then the queue will grow. The queue will also grow if a lot of work items are added to it at the same time. Your output doesn’t show any taskprocessor backed up, so there doesn’t appear to be anything blocking it indefinitely. A description of what was precisely going on when the message was output would help determine why it grew.

3

The message is outputted every time the system starts up before it accepts a single call. Then the queue just keep growing without the system doing anything at all. At least anything I’m aware of.

4

core show taskprocessors doesn’t show any queue that is growing out of control and not being handled, do you have a lot of devices or something?

5

Im not sure what you mean by devices. External Phones and such? I have no external devices.

Do you know when 13.8.0 will be available?

6

As I haven’t seen such message at startup and noone else has mentioned it there must be something unique to your system or configuration to cause it. What configuration do you actually have? Any SIP entries?

As for 13.8.0 I’d expect it in a few weeks.

7

Yep, I have 1 SIP registration.

8

Please provide the console output from startup showing where it shows a high taskprocessor queue…

9

restarted asterisk
Asterisk 13.7.2, Copyright © 1999 - 2014, Digium, Inc. and others.
Created by Mark Spencer markster@digium.com
Asterisk comes with ABSOLUTELY NO WARRANTY; type ‘core show warranty’ for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type ‘core show license’ for details.

Connected to Asterisk 13.7.2 currently running on axis (pid = 9691)
[Mar 15 13:20:13] NOTICE[9691]: loader.c:1364 load_modules: 221 modules will be loaded.
[Mar 15 13:20:13] WARNING[9691]: res_phoneprov.c:1229 get_defaults: Unable to find a valid server address or name.
Registered phoneprov provider ‘sipusers’.
SIP channel loading…
[Mar 15 13:20:14] WARNING[9691]: config_options.c:1352 uint_handler_fn: Attempted to set internal_sample_rate=auto, but set it to 0 instead due to default)
[Mar 15 13:20:14] NOTICE[9691]: confbridge/conf_config_parser.c:2054 verify_default_profiles: Adding default_bridge profile to app_confbridge
[Mar 15 13:20:14] NOTICE[9691]: confbridge/conf_config_parser.c:2065 verify_default_profiles: Adding default_user profile to app_confbridge
[Mar 15 13:20:14] NOTICE[9691]: confbridge/conf_config_parser.c:2076 verify_default_profiles: Adding default_menu menu to app_confbridge
[Mar 15 13:20:14] NOTICE[9691]: cel_custom.c:95 load_config: No mappings found in cel_custom.conf. Not logging CEL to custom CSVs.
Asterisk Ready.
[Mar 15 13:20:14] WARNING[9761][C-00000001]: taskprocessor.c:737 taskprocessor_push: The ‘6354383e-bdad-4901-8b4d-72ccf2c49e22’ task processor queue reached 500 scheduled tasks.

10

Your verbose level is not very high and thus doesn’t show much. asterisk -vvvvvvvvvvvvgc would be good.

11

Its a lot of output. Not sure how to remove the color so it can cause display issues but here it is:

console output link

12

I don’t see the message in the new log, does it happen all the time? Since the queue does get handled and not backed up it may just be worthwhile waiting until 13.8.0 to see what the queue in question is for.

13

Heh. Of course when I post the big log it doesn’t happen. Ill just wait for 13.8 to get more information. Thanks!