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

2022-10-17 Thread Bogdan-Andrei Iancu 

Hi Yury,

OK, let me check a bit the related code, to see if I can spot anything 
bogus there.


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 10/13/22 9:59 AM, Yury Kirsanov wrote:

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 
mailto:bog...@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
mailto:bog...@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@osgw1:~# opensips-cli -x mi mem_pkg_dump 310115
ERROR: command 'mem_pkg_dump' returned: 500: Internal error

Best regards,
Yury.






___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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

2022-10-13 Thread 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 
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 
> 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@osgw1:~# opensips-cli -x mi mem_pkg_dump 310115
>> ERROR: command 'mem_pkg_dump' returned: 500: Internal error
>>
>> Best regards,
>> Yury.
>>
>>
>>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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

2022-10-13 Thread Bogdan-Andrei Iancu 

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 
mailto:bog...@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@osgw1:~# opensips-cli -x mi mem_pkg_dump 310115
ERROR: command 'mem_pkg_dump' returned: 500: Internal error

Best regards,
Yury.




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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

2022-10-11 Thread Yury Kirsanov 
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 
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@osgw1:~# opensips-cli -x mi mem_pkg_dump 310115
> ERROR: command 'mem_pkg_dump' returned: 500: Internal error
>
> Best regards,
> Yury.
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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

2022-10-11 Thread Bogdan-Andrei Iancu 

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@osgw1:~# opensips-cli -x mi mem_pkg_dump 310115
ERROR: command 'mem_pkg_dump' returned: 500: Internal error

Best regards,
Yury.


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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

2022-09-22 Thread Yury Kirsanov 
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@osgw1:~# opensips-cli -x mi mem_pkg_dump 310115
ERROR: command 'mem_pkg_dump' returned: 500: Internal error

Best regards,
Yury.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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

2022-09-21 Thread Yury Kirsanov 
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@osgw1:~# opensips-cli -x mi mem_pkg_dump 310115
ERROR: command 'mem_pkg_dump' returned: 500: Internal error

Best regards,
Yury.

On Wed, Sep 21, 2022 at 4:07 PM Bogdan-Andrei Iancu 
wrote:

> Hi Yury,
>
> By the IDs of the faulty processes, I see they are auto-scaled procs.
>
> Could you confirm that the pkg status ever works for such processes - with
> or without below error, is the pkg dump ever done by the auto-scaled procs ?
>
> 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/20/22 8:23 PM, Yury Kirsanov wrote:
>
> Hi,
> We're experiencing a lot of messages like this:
>
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 42
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 43
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 45
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 42
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 43
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 45
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 42
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 43
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 45
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 42
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 43
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 45
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 42
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 43
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 45
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 42
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 43
> Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
> for process 45
>
> Here's a list of all processes:
>
> opensips-cli -x mi get_statistics load:
> {
> "load:load-proc-1": 0,
> "load:load1m-proc-1": 0,
> "load:load10m-proc-1": 0,
> "load:load-proc-2": 0,
> "load:load1m-proc-2": 0,
> "load:load10m-proc-2": 0,
> "load:load-proc-3": 0,
> "load:load1m-proc-3": 0,
> "load:load10m-proc-3": 0,
> "load:load-proc-4": 0,
> "load:load1m-proc-4": 0,
> "load:load10m-proc-4": 0,
> "load:load-proc-5": 0,
> "load:load1m-proc-5": 0,
> "load:load10m-proc-5": 1,
> "load:load-proc-6": 1,
> "load:load1m-proc-6": 1,
> "load:load10m-proc-6": 1,
> "load:load-proc-7": 0,
> "load:load1m-proc-7": 1,
> "load:load10m-proc-7": 1,
> "load:load-proc-8": 0,
> "load:load1m-proc-8": 1,
> "load:load10m-proc-8": 1,
> "load:load-proc-9": 0,
> "load:load1m-proc-9": 1,
> "load:load10m-proc-9": 1,
> "load:load-proc-10": 0,
> "load:load1m-proc-10": 1,
> "load:load10m-proc-10": 1,
> "load:load-proc-11": 0,
> "load:load1m-proc-11": 1,
> "load:load10m-proc-11": 1,
> "load:load-proc-12": 0,
> "load:load1m-proc-12": 1,
> "load:load10m-proc-12": 1,
> "load:load-proc-13": 0,
> "load:load1m-proc-13": 1,
> "load:load10m-proc-13": 1,
> "load:load-proc-14": 0,
> "load:load1m-proc-14": 1,
> "load:load10m-proc-14": 1,
> "load:load-proc-15": 7,
> "load:load1m-proc-15": 0,
> "load:load10m-proc-15": 0,
> "load:load-proc-16": 0,
> "load:load1m-proc-16": 1,
> "load:load10m-proc-16": 0,
> "load:load-proc-17": 4,
> "load:load1m-proc-17": 0,
>

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

2022-09-21 Thread Bogdan-Andrei Iancu 

Hi Yury,

By the IDs of the faulty processes, I see they are auto-scaled procs.

Could you confirm that the pkg status ever works for such processes - 
with or without below error, is the pkg dump ever done by the 
auto-scaled procs ?


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/20/22 8:23 PM, Yury Kirsanov wrote:

Hi,
We're experiencing a lot of messages like this:

Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 45
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 45
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 45
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 45
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 45
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg 
stats for process 45


Here's a list of all processes:

opensips-cli -x mi get_statistics load:
{
    "load:load-proc-1": 0,
    "load:load1m-proc-1": 0,
    "load:load10m-proc-1": 0,
    "load:load-proc-2": 0,
    "load:load1m-proc-2": 0,
    "load:load10m-proc-2": 0,
    "load:load-proc-3": 0,
    "load:load1m-proc-3": 0,
    "load:load10m-proc-3": 0,
    "load:load-proc-4": 0,
    "load:load1m-proc-4": 0,
    "load:load10m-proc-4": 0,
    "load:load-proc-5": 0,
    "load:load1m-proc-5": 0,
    "load:load10m-proc-5": 1,
    "load:load-proc-6": 1,
    "load:load1m-proc-6": 1,
    "load:load10m-proc-6": 1,
    "load:load-proc-7": 0,
    "load:load1m-proc-7": 1,
    "load:load10m-proc-7": 1,
    "load:load-proc-8": 0,
    "load:load1m-proc-8": 1,
    "load:load10m-proc-8": 1,
    "load:load-proc-9": 0,
    "load:load1m-proc-9": 1,
    "load:load10m-proc-9": 1,
    "load:load-proc-10": 0,
    "load:load1m-proc-10": 1,
    "load:load10m-proc-10": 1,
    "load:load-proc-11": 0,
    "load:load1m-proc-11": 1,
    "load:load10m-proc-11": 1,
    "load:load-proc-12": 0,
    "load:load1m-proc-12": 1,
    "load:load10m-proc-12": 1,
    "load:load-proc-13": 0,
    "load:load1m-proc-13": 1,
    "load:load10m-proc-13": 1,
    "load:load-proc-14": 0,
    "load:load1m-proc-14": 1,
    "load:load10m-proc-14": 1,
    "load:load-proc-15": 7,
    "load:load1m-proc-15": 0,
    "load:load10m-proc-15": 0,
    "load:load-proc-16": 0,
    "load:load1m-proc-16": 1,
    "load:load10m-proc-16": 0,
    "load:load-proc-17": 4,
    "load:load1m-proc-17": 0,
    "load:load10m-proc-17": 0,
    "load:load-proc-18": 0,
    "load:load1m-proc-18": 0,
    "load:load10m-proc-18": 0,
    "load:load-proc-19": 0,
    "load:load1m-proc-19": 0,
    "load:load10m-proc-19": 0,
    "load:load-proc-20": 0,
    "load:load1m-proc-20": 0,
    "load:load10m-proc-20": 0,
    "load:load-proc-21": 0,
    "load:load1m-proc-21": 0,
    "load:load10m-proc-21": 0,
    "load:load-proc-22": 0,
    "load:load1m-proc-22": 0,
    "load:load10m-proc-22": 0,
    "load:load-proc-23": 0,
    "load:load1m-proc-23": 0,
    "load:load10m-proc-23": 0,
    "load:load-proc-24": 0,
    "load:load1m-proc-24": 0,
    "load:load10m-proc-24": 0,
    "load:load-proc-25": 0,
    "load:load1m-proc-25": 0,
    "load:load10m-proc-25": 0,
    "load:load-proc-26": 0,
    "load:load1m-proc-26": 0,
    "load:load10m-proc-26": 0,
    "load:load-proc-27": 0,
    "load:load1m-proc-27": 0,
    "load:load10m-proc-27": 0,
    "load:load-proc-28": 0,
    "load:load1m-proc-28": 0,
    "load:load10m-proc-28": 0,
    "load:load-proc-29": 0,
    "load:load1m-proc-29": 0,
    "load:load10m-proc-29": 0,
    "load:load-proc-30": 0,
    "load:load1m-proc-30": 0,
    "load:load10m-proc-30": 0,
    "load:load-proc-31": 0,
    "load:load1m-proc-31": 0,
    "load:load10m-proc-31": 0,
    "load:load-proc-32": 0,
   

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

2022-09-20 Thread Yury Kirsanov 
Hi,
We're experiencing a lot of messages like this:

Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 45
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 45
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 45
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 45
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 45
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 42
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 43
Sep 21 03:18:09 ERROR:core:signal_pkg_status: failed to trigger pkg stats
for process 45

Here's a list of all processes:

opensips-cli -x mi get_statistics load:
{
"load:load-proc-1": 0,
"load:load1m-proc-1": 0,
"load:load10m-proc-1": 0,
"load:load-proc-2": 0,
"load:load1m-proc-2": 0,
"load:load10m-proc-2": 0,
"load:load-proc-3": 0,
"load:load1m-proc-3": 0,
"load:load10m-proc-3": 0,
"load:load-proc-4": 0,
"load:load1m-proc-4": 0,
"load:load10m-proc-4": 0,
"load:load-proc-5": 0,
"load:load1m-proc-5": 0,
"load:load10m-proc-5": 1,
"load:load-proc-6": 1,
"load:load1m-proc-6": 1,
"load:load10m-proc-6": 1,
"load:load-proc-7": 0,
"load:load1m-proc-7": 1,
"load:load10m-proc-7": 1,
"load:load-proc-8": 0,
"load:load1m-proc-8": 1,
"load:load10m-proc-8": 1,
"load:load-proc-9": 0,
"load:load1m-proc-9": 1,
"load:load10m-proc-9": 1,
"load:load-proc-10": 0,
"load:load1m-proc-10": 1,
"load:load10m-proc-10": 1,
"load:load-proc-11": 0,
"load:load1m-proc-11": 1,
"load:load10m-proc-11": 1,
"load:load-proc-12": 0,
"load:load1m-proc-12": 1,
"load:load10m-proc-12": 1,
"load:load-proc-13": 0,
"load:load1m-proc-13": 1,
"load:load10m-proc-13": 1,
"load:load-proc-14": 0,
"load:load1m-proc-14": 1,
"load:load10m-proc-14": 1,
"load:load-proc-15": 7,
"load:load1m-proc-15": 0,
"load:load10m-proc-15": 0,
"load:load-proc-16": 0,
"load:load1m-proc-16": 1,
"load:load10m-proc-16": 0,
"load:load-proc-17": 4,
"load:load1m-proc-17": 0,
"load:load10m-proc-17": 0,
"load:load-proc-18": 0,
"load:load1m-proc-18": 0,
"load:load10m-proc-18": 0,
"load:load-proc-19": 0,
"load:load1m-proc-19": 0,
"load:load10m-proc-19": 0,
"load:load-proc-20": 0,
"load:load1m-proc-20": 0,
"load:load10m-proc-20": 0,
"load:load-proc-21": 0,
"load:load1m-proc-21": 0,
"load:load10m-proc-21": 0,
"load:load-proc-22": 0,
"load:load1m-proc-22": 0,
"load:load10m-proc-22": 0,
"load:load-proc-23": 0,
"load:load1m-proc-23": 0,
"load:load10m-proc-23": 0,
"load:load-proc-24": 0,
"load:load1m-proc-24": 0,
"load:load10m-proc-24": 0,
"load:load-proc-25": 0,
"load:load1m-proc-25": 0,
"load:load10m-proc-25": 0,
"load:load-proc-26": 0,
"load:load1m-proc-26": 0,
"load:load10m-proc-26": 0,
"load:load-proc-27": 0,
"load:load1m-proc-27": 0,
"load:load10m-proc-27": 0,
"load:load-proc-28": 0,
"load:load1m-proc-28": 0,
"load:load10m-proc-28": 0,
"load:load-proc-29": 0,
"load:load1m-proc-29": 0,
"load:load10m-proc-29": 0,
"load:load-proc-30": 0,
"load:load1m-proc-30": 0,
"load:load10m-proc-30": 0,
"load:load-proc-31": 0,
"load:load1m-proc-31": 0,
"load:load10m-proc-31": 0,
"load:load-proc-32": 0,
"load:load1m-proc-32": 0,
"load:load10m-proc-32": 0,
"load:load-proc-33": 0,
"load:load1m-proc-33": 0,
"load:load10m-proc-33": 0,
"load:load-proc-34": 0,
"load:load1m-proc-34": 0,
"load:load10m-proc-34": 0,
"load:load-proc-35": 0,
"load:load1m-proc-35": 0,
"load:load10m-proc-35": 0,
"load:load-proc-36": 0,
"load:load1m-proc-36": 0,
"load:load10m-proc-36": 0,
"load:load-proc-37": 0,
"load:load1m-proc-37": 0,
"load:load10m-proc-37": 0,