# Cannot copy file, the destination path is probably a directory and I attempted to write a file

**URL:** <https://discuss.elastic.co/t/cannot-copy-file-the-destination-path-is-probably-a-directory-and-i-attempted-to-write-a-file/192796>\
**Category:** Kibana\
**Created:** [July 30, 2019, 12:39am UTC](https://discuss.elastic.co/t/cannot-copy-file-the-destination-path-is-probably-a-directory-and-i-attempted-to-write-a-file/192796 "2019-07-30T00:39:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![First\_Love](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/first_love/32/51105_2.png) [@First\_Love](https://discuss.elastic.co/u/First_Love)\
**Post date:** [July 30, 2019, 12:39am UTC](https://discuss.elastic.co/t/cannot-copy-file-the-destination-path-is-probably-a-directory-and-i-attempted-to-write-a-file/192796/1 "2019-07-30T00:39:11Z")

</div>

kibana version: 6.2.3  
When I run `npm run release --force`(release is a script under package.json: `release: grunt release -v`)

```auto
Cannot copy file, the destination path is probably a directory and I attempted to write a file. {:path=>"/etc/./
default/kibana", :staging=>"/tmp/package-dir-staging-90e75e0f4bacef21574c79a172d717a7c71a207d6a70959c4519fcc3657
6", :level=>:error, "method"=>"input"}  
Debian packaging tools generally labels all files in /etc as config files, as mandated by policy, so fpm default
s to this behavior for deb packages. You can disable this default behavior with --deb-no-default-config-files fl
ag {:level=>:warn}

```

As the error show above, it'll try to find a config file named `/etc/default/kibana` and it find this is a dir, instead of a file. But in fact , I cannot find a file/dir named kibana under `/etc/default/`.

How can I fix this without breaking kibana's config feature? Editting kibana source code is also acceptable.

---

<div class="post-metadata">

**Author:** ![jen-huang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jen-huang/32/74327_2.png) [@jen-huang](https://discuss.elastic.co/u/jen-huang)\
**Post date:** [July 30, 2019, 5:48pm UTC](https://discuss.elastic.co/t/cannot-copy-file-the-destination-path-is-probably-a-directory-and-i-attempted-to-write-a-file/192796/2 "2019-07-30T17:48:01Z")

</div>

Is it possible for you to post a full output of everything that happens when you run `npm run release --force`? I looked in the [release script of our 6.2 branch](https://github.com/elastic/kibana/blob/6.2/tasks/release.js) but I didn't see anything that would trigger Debian packaging. There are Debian commands in [another script](https://github.com/elastic/kibana/blob/6.2/tasks/release_packages.js) but I'm not sure if that would be triggered.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 27, 2019, 5:48pm UTC](https://discuss.elastic.co/t/cannot-copy-file-the-destination-path-is-probably-a-directory-and-i-attempted-to-write-a-file/192796/3 "2019-08-27T17:48:02Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.