hey @bogdan-iancu I actually have an entirelog from startup to shutdown of this
happening - its not very verbose though.
basically i set up a cronjob to search the log fork pkg mem warnings - as soon
as it detects one it kills opensips and makes a back up of the log, then starts
opensips again, this is kind of a cheap way to keep things running as well as
catch it in the act.
The full log is available at the following link:
https://owncloud.uphreak.com/index.php/s/ql8qPgJD2vEqtTQ
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/651#issuecomment-149285944
_______________________________________________
Devel mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
