Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
After some time debuging, I could replicate this issue of memory increase when using a CRL and tls.reload.
One possible issue according to memory statistics printed frequently while we have while true ; do /usr/sbin/kamcmd tls.reload ; /usr/sbin/kamcmd tls.reload ; sleep 0.5 ; done running is:
INFO: qm_sums: qm_sums(): count= 5288 size= 183440 bytes from tls: tls_init.c: ser_realloc(372)
INFO: qm_sums: qm_sums(): count= 17378 size= 1275712 bytes from tls: tls_init.c: ser_malloc(364)
---
INFO: qm_sums: qm_sums(): count= 5341 size= 242768 bytes from tls: tls_init.c: ser_realloc(372)
INFO: qm_sums: qm_sums(): count= 17325 size= 1381936 bytes from tls: tls_init.c: ser_malloc(364)
---
INFO: qm_sums: qm_sums(): count= 5331 size= 248544 bytes from tls: tls_init.c: ser_realloc(372)
INFO: qm_sums: qm_sums(): count= 17335 size= 1422112 bytes from tls: tls_init.c: ser_malloc(364)
---
INFO: qm_sums: qm_sums(): count= 5360 size= 290560 bytes from tls: tls_init.c: ser_realloc(372)
INFO: qm_sums: qm_sums(): count= 17306 size= 1466000 bytes from tls: tls_init.c: ser_malloc(364)
Memory here increases until we exhaust the shared memory max allocation and then tls.reload fails.
Some notes:
When using tls.reload without a CRL, I didn't see any notable increase in memory usage. The above-noted allocations are steady around
count= 9415 size= 948432 bytes from tls: tls_init.c: ser_malloc(364)
count= 1011 size= 151408 bytes from tls: tls_init.c: ser_realloc(372)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.