Dear list, Lately we have had problems loading up new VCLs to our varnish machines, with the following message:
Command failed with error code 106 VCL compiled.dlopen(./vcl.K_vwYyM9.so): ./vcl.K_vwYyM9.so: failed to map segment from shared object: Cannot allocate memory The list of VCLs loaded at the time of failure was: $ varnishadm vcl.list CLI connected to 10.140.106.18 8081 available 0 boot available 0 jafb-test available 0 jafb-tes2 available 0 cap_release_1326203294 available 0 cap_release_1326203474 available 0 cap_release_1326204927 available 0 cap_release_1326210562 available 0 cap_release_1326275426 active 127 cap_release_1326275758 The machine in question should have plenty of memory free and available. The Varnish instance has an uptime of 48-50 hours. The Varnish version is varnish-3.0.1 revision 6152bf7 and the command line parameters used are -u nobody -f /etc/varnish/default.vcl -T <removed>:8081 -s malloc,14G -p thread_pools=4 -p thread_pool_max=1500 -p listen_depth=2048 -p lru_interval=1800 -h classic,169313 -p connect_timeout=600 Would anyone have any ideas on how we can pinpoint the source of the problem and/or whether there are any obvious tuning knobs we should have twiddled? Thanks in advance for your kind assistance. Best regards Jan _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
