# Error building Kibana RPM package (6.4.2)

**URL:** <https://discuss.elastic.co/t/error-building-kibana-rpm-package-6-4-2/152371>\
**Category:** Kibana\
**Created:** [October 14, 2018, 6:32am UTC](https://discuss.elastic.co/t/error-building-kibana-rpm-package-6-4-2/152371 "2018-10-14T06:32:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nick-george](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nick-george/32/23318_2.png) [@nick-george](https://discuss.elastic.co/u/nick-george)\
**Post date:** [October 14, 2018, 6:32am UTC](https://discuss.elastic.co/t/error-building-kibana-rpm-package-6-4-2/152371/1 "2018-10-14T06:32:24Z")

</div>

Hi,

I'm trying to build Kibana into an RPM. I keep getting an error from FPM, saying the 'target' directory doesn't exist. Trying to get around this, I manually create the 'target' before doing the build. Unfortunately, it seems that part of the build process involves deleting the 'target' directory as part of a cleanup step. See below for excerpts from my build log (all in docker).

```
Step 51/58 : RUN mkdir /opt/kibana/target 

Step 58/58 : RUN node scripts/build --oss --release --rpm --skip-archives --debug
 ---> Running in dbba4716ad7b
 info [global] Verifying environment meets requirements
   │ succ Node.js version verified
   │ succ ✓ 0 sec

 info [global] Cleaning artifacts from previous builds
   │ debg Deleting patterns: ['/opt/kibana/build', '/opt/kibana/target']
   │ debg Deleted 1 files/directories
   │ succ ✓ 0 sec

info $ fpm --force -t rpm --package /opt/kibana/target/NAME-6.4.2-ARCH.TYPE -s dir 
--name kibana-oss --description Explore and visualize your Elasticsearch data --version 6.4.2 
--iteration 18021 --url [https://www.elastic.co](https://www.elastic.co/) --vendor Elasticsearch, Inc. 
--maintainer Kibana Team &lt;info@elastic.co&gt; --license ASL 2.0 --conflicts kibana --after-install 
/opt/kibana/src/dev/build/tasks/os_packages/package_scripts/post_install.sh --before-install 
/opt/kibana/src/dev/build/tasks/os_packages/package_scripts/pre_install.sh --before-remove 
/opt/kibana/src/dev/build/tasks/os_packages/package_scripts/pre_remove.sh --after-remove 
/opt/kibana/src/dev/build/tasks/os_packages/package_scripts/post_remove.sh --config-files 
/etc/kibana/kibana.yml --template-value user=kibana --template-value group=kibana --template-value 
optimizeDir=/usr/share/kibana/optimize --template-value configDir=/etc/kibana --template-value 
pluginsDir=/usr/share/kibana/plugins --template-value dataDir=/var/lib/kibana --exclude 
usr/share/kibana/config --exclude usr/share/kibana/data --architecture x86_64 
--rpm-os linux /opt/kibana/build/oss/kibana-6.4.2-linux-x86_64/=/usr/share/kibana/ 
/opt/kibana/build/oss/kibana-6.4.2-linux-x86_64/config/=/etc/kibana/ /opt/kibana/build/oss/kibana-6.4.2-linux-x86_64/data/=/var/lib/kibana/ 
/opt/kibana/src/dev/build/tasks/os_packages/service_templates/sysv/etc/=/etc/ 
/opt/kibana/src/dev/build/tasks/os_packages/service_templates/systemd/etc/=/etc/ │ info 

{:timestamp=&gt;"2018-10-14T05:24:34.577506+0000", :message=&gt;"Parent directory does not exist: 
/opt/kibana/target - cannot write to /opt/kibana/target/kibana-oss-6.4.2-x86_64.rpm", :level=&gt;:fatal} │ERROR failure │ERROR Error: 
{:timestamp=&gt;"2018-10-14T05:24:34.577506+0000", :message=&gt;"Parent directory does not exist: /opt/kibana/target - cannot write to /opt/kibana/target/kibana-oss-6.4.2-x86_64.rpm", 
:level=&gt;:fatal} │ │ 
at makeError (/opt/kibana/node_modules/execa/index.js:172:9) │ 
at Promise.all.then.arr (/opt/kibana/node_modules/execa/index.js:277:16) │ at &lt;anonymous&gt;

```

Any suggestions for what I might be doing wrong? Should I be running the build from a different location?

Many thanks,  
Nick

---

<div class="post-metadata">

**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\
**Post date:** [October 15, 2018, 5:46pm UTC](https://discuss.elastic.co/t/error-building-kibana-rpm-package-6-4-2/152371/2 "2018-10-15T17:46:47Z")

</div>

Hmm, it may be a bug on the Kibana side. I think the rpm task is depending on the archives task to create the target dir. We tend to always build everything, so it makes sense that this would slip through the cracks.

Pending a bug fix can we try removing --skip-archives and see If that gets us closer?

---

<div class="post-metadata">

**Author:** ![nick-george](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nick-george/32/23318_2.png) [@nick-george](https://discuss.elastic.co/u/nick-george)\
**Post date:** [October 15, 2018, 9:32pm UTC](https://discuss.elastic.co/t/error-building-kibana-rpm-package-6-4-2/152371/3 "2018-10-15T21:32:04Z")

</div>

Thanks for that Jon. Your suggestion has fixed my build issue.

Cheers,  
Nick

---

<div class="post-metadata">

**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\
**Post date:** [October 15, 2018, 9:43pm UTC](https://discuss.elastic.co/t/error-building-kibana-rpm-package-6-4-2/152371/4 "2018-10-15T21:43:58Z")

</div>

And thank you! I opened [https://github.com/elastic/kibana/issues/24050](https://github.com/elastic/kibana/issues/24050) for tracking.

---

<div class="post-metadata">

**Author:** ![nick-george](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nick-george/32/23318_2.png) [@nick-george](https://discuss.elastic.co/u/nick-george)\
**Post date:** [October 21, 2018, 2:09am UTC](https://discuss.elastic.co/t/error-building-kibana-rpm-package-6-4-2/152371/5 "2018-10-21T02:09:55Z")

</div>

Thanks for your help 🙂

---

<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:** [November 18, 2018, 2:09am UTC](https://discuss.elastic.co/t/error-building-kibana-rpm-package-6-4-2/152371/6 "2018-11-18T02:09:56Z")

</div>

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