# error\[EPERM\]Operation not permitted **URL:** \ **Category:** Kibana\ **Created:** [June 19, 2018, 11:44am UTC](https://discuss.elastic.co/t/error-eperm-operation-not-permitted/136482 "2018-06-19T11:44:58Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Yong\_Rhee](https://avatars.discourse-cdn.com/v4/letter/y/aeb1de/32.png) [@Yong\_Rhee](https://discuss.elastic.co/u/Yong_Rhee)\ **Post date:** [June 19, 2018, 11:44am UTC](https://discuss.elastic.co/t/error-eperm-operation-not-permitted/136482/1 "2018-06-19T11:44:58Z")
Hello, After reinstalled Kibana and Elasticsearch, things are not easy for me now. This is Window 10 machine and both are 6.3.0 I installed Elasticsearch with msi file and did Kibana with zip file and unzip. I got Auto password for all applications previously and It works for the new installed versions as well. So I modified kibana.yml elasticsearh.user and .pass setting. this is log from kibana execution after launched elasticsearch. I have no idea why Kibana does not work now... help me plus, there is no information in 'bable-register.json' file . ![elastic](https://us1.discourse-cdn.com/elastic/original/3X/d/8/d8d91eba945cd7c3113c50667aa9f257e0648414.PNG) ![9200](https://us1.discourse-cdn.com/elastic/original/3X/7/d/7db0ead7d0ddbc4a212907d01f963ea39e31efdf.PNG) ``` C:\Program Files\kibana-6.3.0-windows-x86_64\bin>kibana.bat fs.js:646 return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode); ^ Error: EPERM: operation not permitted, open 'C:\Program Files\kibana-6.3.0-windows-x86_64\optimize\.babelcache.json' at Object.fs.openSync (fs.js:646:18) at Object.fs.writeFileSync (fs.js:1299:33) at save (C:\Program Files\kibana-6.3.0-windows-x86_64\node_modules\babel-register\lib\cache.js:45:16) at _combinedTickCallback (internal/process/next_tick.js:131:7) at process._tickCallback (internal/process/next_tick.js:180:9) at Function.Module.runMain (module.js:695:11) at startup (bootstrap_node.js:188:16) at bootstrap_node.js:609:3`Preformatted text` ``` ---
**Author:** ![Larry\_Gregory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_gregory/32/34969_2.png) [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)\ **Post date:** [June 19, 2018, 1:56pm UTC](https://discuss.elastic.co/t/error-eperm-operation-not-permitted/136482/2 "2018-06-19T13:56:39Z")
Hi @Yong_Rhee, We've [seen this symptom](https://discuss.elastic.co/t/install-failure-on-windows-eperm-operation-not-permitted/66381) on Windows machines before, and it seems that temporarily disabling anti-virus/anti-malware fixes this problem. Can you try this and let me know if that helps? ---
**Author:** ![Yong\_Rhee](https://avatars.discourse-cdn.com/v4/letter/y/aeb1de/32.png) [@Yong\_Rhee](https://discuss.elastic.co/u/Yong_Rhee)\ **Post date:** [June 20, 2018, 5:10am UTC](https://discuss.elastic.co/t/error-eperm-operation-not-permitted/136482/3 "2018-06-20T05:10:23Z")
I tried deactivate anti-virus/anti-malware program and got same result. I also found strange log when I tried to connect localport:9200 with the "elastic" : "AUTO password" although it seems that it is not relevant to the Kibana connection issue. I also retrieved my machine to the Window system point where I installed Elasticsearch which is couple days ago (It doesn't make any difference regarding this issue) `[2018-06-20T14:04:26,900][INFO][o.e.x.s.a.AuthenticationService] [DESKTOP-C93E9FL] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]` It is really strange... for window machine I got different log every time I tried differently. Can I try with Ubuntu on Window10 to make it works (although I don't know how to do it)? ---
**Author:** ![Larry\_Gregory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_gregory/32/34969_2.png) [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)\ **Post date:** [June 20, 2018, 12:01pm UTC](https://discuss.elastic.co/t/error-eperm-operation-not-permitted/136482/4 "2018-06-20T12:01:14Z")
The authentication error you see is expected if you provide an invalid username/password combination, and you're right, that's unrelated to your Kibana issue. ``` EPERM: operation not permitted ``` This is a very general Windows OS error, so all we know is that something on your machine is preventing `C:\Program Files\kibana-6.3.0-windows-x86_64\optimize\.babelcache.json` from being accessed. If it's not AV, then it's possible that your user account does not have the appropriate privileges for that directory/file. Have you tried running Kibana with administrator privileges? If that doesn't work, then you're more than welcome to try to install the [Kibana Debian distribution](https://www.elastic.co/downloads/kibana) under the Ubuntu subsytem ---
**Author:** ![Yong\_Rhee](https://avatars.discourse-cdn.com/v4/letter/y/aeb1de/32.png) [@Yong\_Rhee](https://discuss.elastic.co/u/Yong_Rhee)\ **Post date:** [June 21, 2018, 4:25am UTC](https://discuss.elastic.co/t/error-eperm-operation-not-permitted/136482/5 "2018-06-21T04:25:55Z")
Thanks Larry. Apparently, administrator privileges gave me some improvement. It goes to connection with following logs. And I was able to Kibana login window. However, from there, I am still not able to log in because of the following statement. ps. I am still using credentials that I have auto generated at the first place when I installed elastic search. It is reflected in kibana.yml (user and password) Both X-pack installed. (I think) (Login is currently disabled. Administrators should consult the Kibana logs for more details.) ``` log [04:21:48.705] [error][status][plugin:index_management@6.3.0] Status changed from red to red - [security_exception] missing authentication token for REST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\" charset=\"UTF-8\"" } } log [04:21:48.706] [error][status][plugin:graph@6.3.0] Status changed from red to red - [security_exception] missing authentication token for REST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\" charset=\"UTF-8\"" } } log [04:21:48.707] [error][status][plugin:security@6.3.0] Status changed from red to red - [security_exception] missing authentication token for REST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\" charset=\"UTF-8\"" } } log [04:21:48.708] [error][status][plugin:grokdebugger@6.3.0] Status changed from red to red - [security_exception] missing authentication token for REST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\" charset=\"UTF-8\"" } } log [04:21:48.709] [error][status][plugin:logstash@6.3.0] Status changed from red to red - [security_exception] missing authentication token for REST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\" charset=\"UTF-8\"" } } log [04:21:48.710] [error][status][plugin:reporting@6.3.0] Status changed from red to red - [security_exception] missing authentication token for REST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\" charset=\"UTF-8\"" } } log [04:21:53.724] [info][listening] Server running at http://localhost:5601 log [04:22:18.705] [warning][license][xpack] License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. [security_exception] missing authentication token for REST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\" charset=\"UTF-8\"" } } :: {"path":"/_xpack","statusCode":401,"response":"{\"error\":{\"root_cause\":[{\"type\":\"security_exception\",\"reason\":\"missing authentication token for REST request [/_xpack]\",\"header\":{\"WWW-Authenticate\":\"Basic realm=\\\"security\\\" charset=\\\"UTF-8\\\"\"}}],\"type\":\"security_exception\",\"reason\":\"missing authentication token for REST request [/_xpack]\",\"header\":{\"WWW-Authenticate\":\"Basic realm=\\\"security\\\" charset=\\\"UTF-8\\\"\"}},\"status\":401}","wwwAuthenticateDirective":"Basic realm=\"security\" charset=\"UTF-8\""} log [04:22:48.720] [warning][license][xpack] License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. [security_exception] missing authentication token for REST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\" charset=\"UTF-8\"" } } :: {"path":"/_xpack","statusCode":401,"response":"{\"error\":{\"root_cause\":[{\"type\":\"security_exception\",\"reason\":\"missing authentication token for REST request [/_xpack]\",\"header\":{\"WWW-Authenticate\":\"Basic realm=\\\"security\\\" charset=\\\"UTF-8\\\"\"}}],\"type\":\"security_exception\",\"reason\":\"missing authentication token for REST request [/_xpack]\",\"header\":{\"WWW-Authenticate\":\"Basic realm=\\\"security\\\" charset=\\\"UTF-8\\\"\"}},\"status\":401}","wwwAuthenticateDirective":"Basic realm=\"security\" charset=\"UTF-8\""} log [04:23:18.732] [warning][license][xpack] License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. [security_exception] missing authentication token for REST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\" charset=\"UTF-8\"" } } :: {"path":"/_xpack","statusCode":401,"response":"{\"error\":{\"root_cause\":[{\"type\":\"security_exception\",\"reason\":\"missing authentication token for REST request [/_xpack]\",\"header\":{\"WWW-Authenticate\":\"Basic realm=\\\"security\\\" charset=\\\"UTF-8\\\"\"}}],\"type\":\"security_exception\",\"reason\":\"missing authentication token for REST request [/_xpack]\",\"header\":{\"WWW-Authenticate\":\"Basic realm=\\\"security\\\" charset=\\\"UTF-8\\\"\"}},\"status\":401}","wwwAuthenticateDirective":"Basic realm=\"security\" charset=\"UTF-8\""} log [04:23:48.750] [warning][license][xpack] License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. [security_exception] missing authentication token for REST request [/_xpack], with { header={ WWW-Authenticate="Basic realm=\"security\" charset=\"UTF-8\"" } } :: {"path":"/_xpack","statusCode":401,"response":"{\"error\":{\"root_cause\":[{\"type\":\"security_exception\",\"reason\":\"missing authentication token for REST request [/_xpack]\",\"header\":{\"WWW-Authenticate\":\"Basic realm=\\\"security\\\" charset=\\\"UTF-8\\\"\"}}],\"type\":\"security_exception\",\"reason\":\"missing authentication token for REST request [/_xpack]\",\"header\":{\"WWW-Authenticate\":\"Basic realm=\\\"security\\\" charset=\\\"UTF-8\\\"\"}},\"status\":401}","wwwAuthenticateDirective":"Basic realm=\"security\" charset=\"UTF-8\""} ``` ![login](https://us1.discourse-cdn.com/elastic/original/3X/e/a/eab2cb271438ebdd7e8407a8c635c09808a70d5c.PNG) ---
**Author:** ![Larry\_Gregory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_gregory/32/34969_2.png) [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)\ **Post date:** [June 21, 2018, 11:41am UTC](https://discuss.elastic.co/t/error-eperm-operation-not-permitted/136482/6 "2018-06-21T11:41:45Z")
Can you check your `kibana.yml` file and verify that you have `elasticsearch.username` and `elasticsearch.password` set and configured correctly? This is needed so that the Kibana server can authenticate to Elasticsearch. See [https://www.elastic.co/guide/en/kibana/current/settings.html](https://www.elastic.co/guide/en/kibana/current/settings.html) for more information on configuring Kibana ---
**Author:** ![Yong\_Rhee](https://avatars.discourse-cdn.com/v4/letter/y/aeb1de/32.png) [@Yong\_Rhee](https://discuss.elastic.co/u/Yong_Rhee)\ **Post date:** [June 22, 2018, 12:24pm UTC](https://discuss.elastic.co/t/error-eperm-operation-not-permitted/136482/7 "2018-06-22T12:24:38Z")
Thank you! This ticket is resolved! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 20, 2018, 12:24pm UTC](https://discuss.elastic.co/t/error-eperm-operation-not-permitted/136482/8 "2018-07-20T12:24:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.