[OpenSIPS-Users] Failed to trigger pkg stats in logs

[Yury Kirsanov]

Hi Bogdan,
Can't say for sure at the moment but I believe this was happening during
the scale-down procedure. Currently that server is running without an
autoscaler as it's a production one, unfortunately.

Regards,
Yury.

On Thu, Oct 13, 2022 at 5:56 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi Yury,
>
> OK, but could you try to see the relation between the pkg status and
> errors, like such errors appear after:
>     * simple scaling up ?
>     * simple scaling down ?
>     * scaling up and down ?
>
> Thanks,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 27-30 Sept 2022, Athens
>   https://www.opensips.org/events/Summit-2022Athens/
>
> On 10/12/22 1:34 AM, Yury Kirsanov wrote:
>
> Hi Bogdan,
> No, after I removed all the autoscaling I'm not getting any
> 'core:signal_pkg_status' errors.
>
> Regards,
> Yury.
>
> On Tue, Oct 11, 2022 at 10:56 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> Hi Yury,
>>
>> trying to recap here - after completely removing the auto-scaling, do you
>> still have issues with fetching the pkg stats?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>> OpenSIPS Summit 27-30 Sept 2022, Athens
>>   https://www.opensips.org/events/Summit-2022Athens/
>>
>> On 9/22/22 5:39 PM, Yury Kirsanov wrote:
>>
>> Hi Bogdan,
>> Sorry, I just realized that I haven't turned off the auto-scaler for UDP
>> processes so you're right - that error is for them. I've switched TCP
>> auto-scaling off due to all my previous issues that I wasn't able to
>> overcome.
>>
>> auto_scaling_profile = PROFILE_UDP
>>      scale up to 32 on 80% for 4 cycles within 5
>>      scale down to 2 on 10% for 5 cycles
>>
>> udp_workers=1 use_auto_scaling_profile PROFILE_UDP
>>
>> socket=udp:10.x.x.x:5060
>> socket=udp:103.x.x.x:7060
>>
>> In regards to pkg memory - I only have 32MB as -M parameter, maybe that's
>> not enough? I'm not sure how to do 'pkg dump' - never tried to do that
>> before, is this what you're asking about?
>>
>> Sep 21 18:52:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
>> for process 45
>>  opensips-cli -x mi ps
>> {
>>     "Processes": [
>> ...
>>         {
>>             "ID": 45,
>>             "PID": 310115,
>>             "Type": "SIP receiver udp:103.x.x.x:7060"
>>         }
>>     ]
>> }
>> root at osgw1:~# opensips-cli -x mi mem_pkg_dump 310115
>> ERROR: command 'mem_pkg_dump' returned: 500: Internal error
>>
>> Best regards,
>> Yury.
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20221013/079f36fb/attachment.html>