Just to make sure I got it right: Although the graph says "memory
usage", it actually graphs "free memory", correct?
If yes, could you please redo the test, properly wait for all calls to
finish, and then generate a memory map with "kill -SIGUSR1
<opensips_attendant_pid>"? You can find out the attendant's PID with
"opensipsctl fifo ps".
These logs should give us a strong hint as to what happens with the
shared memory on that CentOS 7 box. Also, you may send any relevant
out-of-memory error logs to [email protected], if privacy is a concern.
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 24.07.2017 14:38, Evgeniy G. via Users wrote:
<http://opensips-open-sip-server.1449251.n2.nabble.com/file/n7608083/Sharemem_CentOS_7.jpg>
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Does-not-release-shared-memory-tp7608065p7608083.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
