[OpenSIPS-Users] mi_fifo lock on reply after a period of time in 3.1.3

[Andrew Yager]

Just further to this, I think it's the ul_dump command that seems to cause
the issue first.

Andrew


On Sat, 2 Oct 2021 at 13:05, Andrew Yager <andrew at rwts.com.au> wrote:

> Hi,
>
> Not entirely sure where to start digging on this one. On 3.1.3 we've had
> an issue appear "suddenly" whereby our mi command output seems to "block"
> and not return any useful data. Restarting opensips processes restores
> comms.
>
> We end up with a huge number of opensips_fifo_reply_\* files in the /tmp
> directory, but effectively no data is ever written and opensips-cli freezes.
>
> We've restarted twice to "resolve" now, but the issue appears to reoccur.
> We're using the mi get_statistics command to monitor stats/health and
> uldump to pull some detail about usrloc data every 5 minutes.
>
> I don't think I can cause a debug level increase because the MI process
> doesn't seem to be communicating (at least it doesn't seem to work).
>
> opensips                             3.1.3-1
> opensips-cli                         0.1~20210707~572d2db-
> 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 17:29:00 UTC 2021 x86_64 x86_64
> x86_64 GNU/Linux
>
> I can restart again, but if this is going to keep happening, I want to
> make sure I have something useful in the logs to be able to trace down.
>
> Andrew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211004/3a97ddc6/attachment.html>