# Help debugging Memory Lock failure on windows server **URL:** \ **Category:** Elasticsearch\ **Created:** [May 14, 2017, 3:35am UTC](https://discuss.elastic.co/t/help-debugging-memory-lock-failure-on-windows-server/85661 "2017-05-14T03:35:21Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Luckyj13](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/luckyj13/32/24522_2.png) [@Luckyj13](https://discuss.elastic.co/u/Luckyj13)\ **Post date:** [May 14, 2017, 3:35am UTC](https://discuss.elastic.co/t/help-debugging-memory-lock-failure-on-windows-server/85661/1 "2017-05-14T03:35:21Z")
Hi Experts, I have been reworking my code to use ES 5.3.1 and I am getting a bootstrap error trying to disable swapping. I run my code locally ES starts as expected, on the server i get this. my heap settings are -Xms30g -Xmx30g. I have 128g total mem on the box. ``` ""[2017-05-14T03:25:00,977][DEBUG][io.netty.channel.DefaultChannelId] -Dio.netty.processId: 9312 (auto-detected) ""[2017-05-14T03:25:00,977][DEBUG][io.netty.util.NetUtil] -Djava.net.preferIPv4Stack: false ""[2017-05-14T03:25:00,977][DEBUG][io.netty.util.NetUtil] -Djava.net.preferIPv6Addresses: false ""[2017-05-14T03:25:01,008][DEBUG][io.netty.util.NetUtil] Loopback interface: lo (Software Loopback Interface 1, 127.0.0.1) ""[2017-05-14T03:25:01,008][DEBUG][io.netty.util.NetUtil] \proc\sys\net\core\somaxconn: 200 (non-existent) ""[2017-05-14T03:25:01,039][DEBUG][io.netty.channel.DefaultChannelId] -Dio.netty.machineId: b0:83:fe:ff:fe:fb:c9:57 (auto-detected) ""[2017-05-14T03:25:01,055][DEBUG][io.netty.util.internal.ThreadLocalRandom] -Dio.netty.initialSeedUniquifier: 0xdc7115ac9f4c7e1e ""[2017-05-14T03:25:01,071][DEBUG][io.netty.util.ResourceLeakDetector] -Dio.netty.leakDetection.level: simple ""[2017-05-14T03:25:01,071][DEBUG][io.netty.util.ResourceLeakDetector] -Dio.netty.leakDetection.maxRecords: 4 ""[2017-05-14T03:25:01,133][DEBUG][io.netty.buffer.PooledByteBufAllocator] -Dio.netty.allocator.numHeapArenas: 40 ""[2017-05-14T03:25:01,133][DEBUG][io.netty.buffer.PooledByteBufAllocator] -Dio.netty.allocator.numDirectArenas: 40 ""[2017-05-14T03:25:01,133][DEBUG][io.netty.buffer.PooledByteBufAllocator] -Dio.netty.allocator.pageSize: 8192 ""[2017-05-14T03:25:01,133][DEBUG][io.netty.buffer.PooledByteBufAllocator] -Dio.netty.allocator.maxOrder: 11 ""[2017-05-14T03:25:01,133][DEBUG][io.netty.buffer.PooledByteBufAllocator] -Dio.netty.allocator.chunkSize: 16777216 ""[2017-05-14T03:25:01,133][DEBUG][io.netty.buffer.PooledByteBufAllocator] -Dio.netty.allocator.tinyCacheSize: 512 ""[2017-05-14T03:25:01,133][DEBUG][io.netty.buffer.PooledByteBufAllocator] -Dio.netty.allocator.smallCacheSize: 256 ""[2017-05-14T03:25:01,133][DEBUG][io.netty.buffer.PooledByteBufAllocator] -Dio.netty.allocator.normalCacheSize: 64 ""[2017-05-14T03:25:01,133][DEBUG][io.netty.buffer.PooledByteBufAllocator] -Dio.netty.allocator.maxCachedBufferCapacity: 32768 ""[2017-05-14T03:25:01,133][DEBUG][io.netty.buffer.PooledByteBufAllocator] -Dio.netty.allocator.cacheTrimInterval: 8192 ""[2017-05-14T03:25:01,133][DEBUG][io.netty.buffer.PooledByteBufAllocator] -Dio.netty.allocator.useCacheForAllThreads ""[2017-05-14T03:25:01,180][DEBUG][io.netty.buffer.ByteBufUtil] -Dio.netty.allocator.type: pooled ""[2017-05-14T03:25:01,180][DEBUG][io.netty.buffer.ByteBufUtil] -Dio.netty.threadLocalDirectBufferSize: 65536 ""[2017-05-14T03:25:01,180][DEBUG][io.netty.buffer.ByteBufUtil] -Dio.netty.maxThreadLocalCharBufferSize: 16384 ""[2017-05-14T03:25:01,461][DEBUG][org.elasticsearch.transport.netty4.Netty4Transport] Bound profile [default] to address {[::1]:9300} ""[2017-05-14T03:25:01,571][DEBUG][org.elasticsearch.transport.netty4.Netty4Transport] Bound profile [default] to address {127.0.0.1:9300} ""[2017-05-14T03:25:01,680][DEBUG][org.elasticsearch.transport.netty4.Netty4Transport] Bound profile [default] to address {25.255.90.3:9300} ""[2017-05-14T03:25:01,696][INFO][org.elasticsearch.transport.TransportService] publish_address {25.255.90.3:9300}, bound_addresses {[::1]:9300}, {127.0.0.1:9300}, {25.255.90.3:9300} ""[2017-05-14T03:25:01,696][INFO][org.elasticsearch.bootstrap.BootstrapChecks] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks "ERROR: bootstrap checks failed memory locking requested for elasticsearch process but memory is not locked "[2017-05-14T03:25:01,696][INFO][org.elasticsearch.node.Node] stopping ... ""[2017-05-14T03:25:02,196][INFO][org.elasticsearch.node.Node] stopped ""[2017-05-14T03:25:02,196][INFO][org.elasticsearch.node.Node] closing ... ""[2017-05-14T03:25:02,196][TRACE][org.elasticsearch.node.Node] Close times for each service: StopWatch 'node_close': running time = 0s ----------------------------------------- ms % Task name ----------------------------------------- ""[2017-05-14T03:25:02,196][TRACE][org.elasticsearch.env.NodeEnvironment] releasing lock [NativeFSLock(path=K:\data\elasticsearch\nodes\0\node.lock,impl=sun.nio.ch.FileLockImpl[0:9223372036854775807 exclusive valid],creationTime=2017-04-25T20:55:13.681673Z)] ""[2017-05-14T03:25:02,196][INFO][org.elasticsearch.node.Node] closed "Info: Child Process [19508] is no longer running, exiting. ExitProcess(0) ``` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 11, 2017, 3:36am UTC](https://discuss.elastic.co/t/help-debugging-memory-lock-failure-on-windows-server/85661/2 "2017-06-11T03:36:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.