Thinkbox License Server Memory Leak

[cparmar]

I’m not sure this is the right place to post but wasn’t sure where else.

We are running the Thinkbox License server on a Centos 5.5 server. It seems to be eating up the RAM on the machine from whenever it’s launched.

I ran a pmap on the running PID, here’s the output:

pmap 23232 | more 23232: thinkbox -T delany 11.12 6 -c /usr/local/Thinkbox/flexnet/Thinkbox_license.lic --lmgrd_start 54527eef -vdrestart 1 0000000000400000 1564K r-x-- /usr/local/Thinkbox/flexnet/thinkbox 0000000000787000 24K rw--- /usr/local/Thinkbox/flexnet/thinkbox 000000000078d000 124K rw--- [ anon ] 0000000011270000 1640680K rw--- [ anon ] 0000003250a00000 112K r-x-- /lib64/ld-2.5.so 0000003250c1c000 4K r---- /lib64/ld-2.5.so 0000003250c1d000 4K rw--- /lib64/ld-2.5.so 0000003250e00000 1340K r-x-- /lib64/libc-2.5.so 0000003250f4f000 2048K ----- /lib64/libc-2.5.so 000000325114f000 16K r---- /lib64/libc-2.5.so 0000003251153000 4K rw--- /lib64/libc-2.5.so 0000003251154000 20K rw--- [ anon ] 0000003251200000 8K r-x-- /lib64/libdl-2.5.so 0000003251202000 2048K ----- /lib64/libdl-2.5.so 0000003251402000 4K r---- /lib64/libdl-2.5.so 0000003251403000 4K rw--- /lib64/libdl-2.5.so 0000003251a00000 88K r-x-- /lib64/libpthread-2.5.so 0000003251a16000 2048K ----- /lib64/libpthread-2.5.so 0000003251c16000 4K r---- /lib64/libpthread-2.5.so 0000003251c17000 4K rw--- /lib64/libpthread-2.5.so 0000003251c18000 16K rw--- [ anon ] 0000003252a00000 28K r-x-- /lib64/librt-2.5.so 0000003252a07000 2048K ----- /lib64/librt-2.5.so 0000003252c07000 4K r---- /lib64/librt-2.5.so 0000003252c08000 4K rw--- /lib64/librt-2.5.so 0000003252e00000 84K r-x-- /lib64/libnsl-2.5.so 0000003252e15000 2044K ----- /lib64/libnsl-2.5.so 0000003253014000 4K r---- /lib64/libnsl-2.5.so 0000003253015000 4K rw--- /lib64/libnsl-2.5.so 0000003253016000 8K rw--- [ anon ] 0000003253200000 12K r-x-- /lib64/libcap.so.1.10 0000003253203000 2048K ----- /lib64/libcap.so.1.10 0000003253403000 4K rw--- /lib64/libcap.so.1.10 0000003253600000 628K r-x-- /lib64/libglib-2.0.so.0.1200.3 000000325369d000 2044K ----- /lib64/libglib-2.0.so.0.1200.3 000000325389c000 8K rw--- /lib64/libglib-2.0.so.0.1200.3 0000003253a00000 248K r-x-- /lib64/libgobject-2.0.so.0.1200.3 0000003253a3e000 2048K ----- /lib64/libgobject-2.0.so.0.1200.3 0000003253c3e000 8K rw--- /lib64/libgobject-2.0.so.0.1200.3 0000003255a00000 228K r-x-- /lib64/libdbus-1.so.3.4.0 0000003255a39000 2048K ----- /lib64/libdbus-1.so.3.4.0 0000003255c39000 8K rw--- /lib64/libdbus-1.so.3.4.0 0000003257600000 120K r-x-- /usr/lib64/libdbus-glib-1.so.2.1.0 000000325761e000 2048K ----- /usr/lib64/libdbus-glib-1.so.2.1.0 000000325781e000 8K rw--- /usr/lib64/libdbus-glib-1.so.2.1.0 0000003257a00000 40K r-x-- /usr/lib64/libhal.so.1.0.0 0000003257a0a000 2044K ----- /usr/lib64/libhal.so.1.0.0 0000003257c09000 4K rw--- /usr/lib64/libhal.so.1.0.0 00002af30c404000 8K rw--- [ anon ] 00002af30c410000 12K rw--- [ anon ] 00002af30c413000 4K ----- [ anon ] 00002af30c414000 10240K rw--- [ anon ] 00002af30ce1f000 40K r-x-- /lib64/libnss_files-2.5.so 00002af30ce29000 2044K ----- /lib64/libnss_files-2.5.so 00002af30d028000 4K r---- /lib64/libnss_files-2.5.so

It doesn’t shoot up instantly, it seems to be leaking memory and eventually use up most of the server’s RAM.

Secondly, is there a way to turn down the logging on the server or turn on automatic log rotation as the log file is almost a 1GB file.

[eamsler]

Hey sir,

Can you do a memory dump for me and send it to edwinamsler@thinkboxsoftware.com? We haven’t seen this yet. I’ve also never used pmap before, I’m impressed.

I added some code to the vendor daemon about four years ago, but it doesn’t allocate any memory outside of its original 64K static buffer.

The file size is a bit tricky. Because we log all checkouts/checkins (one each per render task), it’ll keep going. I have never personally played with logrotate, so if you’re better with this than I am I’d appreciate help here. For now, I can only recommend setting up an options file to silence the checkins/outs with the NOLOG option:
wwwasd.web.cern.ch/wwwasd/lhc++/ … /chap5.htm

I’m looking forward to the memory dump.

Regards,

Edwin

[cparmar]

Can you let me know how to complete the memory dump (do you want it just for the process or the server as a whole)

I have set up logrotate before, I may use the options file in the meantime.

Logrotate usually comes with Linux, A new logrotate config would need to be set up in /etc/logrotate.d/. Here’s a good reference link: linuxconfig.org/setting-up-logro … dhat-linux