# Kibana Package creation issue

**URL:** <https://discuss.elastic.co/t/kibana-package-creation-issue/88149>\
**Category:** Kibana\
**Created:** [June 3, 2017, 8:56am UTC](https://discuss.elastic.co/t/kibana-package-creation-issue/88149 "2017-06-03T08:56:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sravya](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@sravya](https://discuss.elastic.co/u/sravya)\
**Post date:** [June 3, 2017, 8:56am UTC](https://discuss.elastic.co/t/kibana-package-creation-issue/88149/1 "2017-06-03T08:56:38Z")

</div>

Hi! iwas trying to create kibana rpm package "npm run build -- --rpm", and ran into this issue.  
Fatal error: Path must be a string. Received true  
npm ERR! code ELIFECYCLE  
npm ERR! errno 1  
npm ERR! kibana@6.0.0-alpha2 build: grunt build "--rpm"  
npm ERR! Exit status 1  
npm ERR!  
npm ERR! Failed at the kibana@6.0.0-alpha2 build script.  
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.  
npm ERR! A complete log of this run can be found in:  
npm ERR! /home/farya/.npm/\_logs/2017-05-31T10\_36\_12\_445Z-debug.log

i did try upgarding my babel-core@6.10.4 but that agin didnt help me out.

$ npm run build -- --rpm

kibana@6.0.0-alpha2 build /home/farya/kibana  
grunt build "--rpm"  
Running "build" task

Running "clean:build" (clean) task

1 path cleaned.  
Running "clean:target" (clean) task

0 paths cleaned.  
Running "\_build:downloadNodeBuilds" task

Downloading darwin-x86\_64 and corresponding sha  
Downloading linux-x86\_64 and corresponding sha  
Downloading windows-x86\_64 and corresponding sha  
darwin-x86\_64 downloaded and verified  
linux-x86\_64 downloaded and verified  
windows-x86\_64 downloaded and verified  
Running "\_build:extractNodeBuilds" task

Running "copy:devSource" (copy) task  
Created 483 directories, copied 2032 files

Running "clean:devSourceForTestbed" (clean) task

1 path cleaned.  
Running "babel:build" (babel) task

Running "\_build:babelOptions" task

Running "\_build:plugins" task

Running "\_build:data" task

Running "i18nextract:default\_options" (i18nextract) task

Create file: build/i18n\_extract/en.json  
Statistics : empty: 47 (100%) / Updated: 0 / Deleted: 0 / New: 47

Running "\_build:check" task

Running "\_build:packageJson" task

Running "\_build:readme" task

Running "\_build:babelCache" task

Running "\_build:installNpmDeps" task

Running "\_build:notice" task  
Fatal error: Path must be a string. Received true  
npm ERR! code ELIFECYCLE  
npm ERR! errno 1  
npm ERR! kibana@6.0.0-alpha2 build: grunt build "--rpm"  
npm ERR! Exit status 1  
npm ERR!  
npm ERR! Failed at the kibana@6.0.0-alpha2 build script.  
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

# npm ERR! A complete log of this run can be found in: npm ERR! /home/farya/.npm/\_logs/2017-06-01T12\_59\_41\_662Z-debug.log

here is the log file o/p:  
0 info it worked if it ends with ok  
1 verbose cli [ '/home/farya/.nvm/versions/node/v6.10.2/bin/node',  
1 verbose cli '/home/farya/.nvm/versions/node/v6.10.2/bin/npm',  
1 verbose cli 'run',  
1 verbose cli 'build',  
1 verbose cli '--',  
1 verbose cli '--rpm' ]  
2 info using npm@4.6.1  
3 info using node@v6.10.2  
4 verbose run-script ['prebuild', 'build', 'postbuild']  
5 info lifecycle kibana@6.0.0-alpha2~prebuild: kibana@6.0.0-alpha2  
6 silly lifecycle kibana@6.0.0-alpha2~prebuild: no script for prebuild, continuing  
7 info lifecycle kibana@6.0.0-alpha2~build: kibana@6.0.0-alpha2  
8 verbose lifecycle kibana@6.0.0-alpha2~build: unsafe-perm in lifecycle true  
9 verbose lifecycle kibana@6.0.0-alpha2~build: PATH: /home/farya/.nvm/versions/node/v6.10.2/lib/node\_modules/npm/bin/node-gyp-bin:/home/farya/kibana/node\_modules/.bin:/home/farya/.nvm/versions/node/v6.10.2/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/farya/.local/bin:/home/farya/bin:/home/farya/.nvm/versions/node/v6.10.2/bin/grunt  
10 verbose lifecycle kibana@6.0.0-alpha2~build: CWD: /home/farya/kibana  
11 silly lifecycle kibana@6.0.0-alpha2~build: Args: ['-c', 'grunt build "--rpm"']  
12 silly lifecycle kibana@6.0.0-alpha2~build: Returned: code: 1 signal: null  
13 info lifecycle kibana@6.0.0-alpha2~build: Failed to exec build script  
14 verbose stack Error: kibana@6.0.0-alpha2 build: grunt build "--rpm"  
14 verbose stack Exit status 1  
i also tried to edit tasks/build/notice.js by adding console.log({ kibanaDir, noticePath }); after line 22 where noticePath is initialized and the ran npm run build -- --rpm but again i ran into same issue

---

<div class="post-metadata">

**Author:** ![FareehaNaaz](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@FareehaNaaz](https://discuss.elastic.co/u/FareehaNaaz)\
**Post date:** [June 5, 2017, 7:01am UTC](https://discuss.elastic.co/t/kibana-package-creation-issue/88149/2 "2017-06-05T07:01:20Z")

</div>

Hi! can anyone help us with this issue?

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [June 7, 2017, 4:21pm UTC](https://discuss.elastic.co/t/kibana-package-creation-issue/88149/3 "2017-06-07T16:21:16Z")

</div>

I think the `pleaserun` must be built on the linux machine, and you might also have to do `gem install pleaserun`

I haven't tried it, so I'm not sure if it will work.

---

<div class="post-metadata">

**Author:** ![sravya](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@sravya](https://discuss.elastic.co/u/sravya)\
**Post date:** [June 7, 2017, 4:29pm UTC](https://discuss.elastic.co/t/kibana-package-creation-issue/88149/4 "2017-06-07T16:29:09Z")

</div>

hi@tsullivan, I have tried this and i got the output as :gem install pleaserun  
Fetching: dotenv-2.2.1.gem (100%)  
Successfully installed dotenv-2.2.1  
Fetching: pleaserun-0.0.29.gem (100%)  
Successfully installed pleaserun-0.0.29  
/usr/local/share/ruby/site\_ruby/rubygems/core\_ext/kernel\_require.rb:45:in `require': cannot load such file -- json/pure (LoadError) from /usr/local/share/ruby/site_ruby/rubygems/core_ext/kernel_require.rb:45:in`require'  
from /usr/share/gems/gems/json-1.7.7/lib/json.rb:60:in `rescue in <module:JSON>' from /usr/share/gems/gems/json-1.7.7/lib/json.rb:57:in`module:JSON'  
from /usr/share/gems/gems/json-1.7.7/lib/json.rb:54:in `<top (required)>' from /usr/local/share/ruby/site_ruby/rubygems/core_ext/kernel_require.rb:45:in`require'  
from /usr/local/share/ruby/site\_ruby/rubygems/core\_ext/kernel\_require.rb:45:in `require' from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/text.rb:16:in`\<top (required)\>'  
from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/code\_object.rb:28:in `<class:CodeObject>' from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/code_object.rb:26:in`\<top (required)\>'  
from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/generator/markup.rb:59:in `<top (required)>' from /usr/local/share/ruby/site_ruby/rubygems/core_ext/kernel_require.rb:45:in`require'  
from /usr/local/share/ruby/site\_ruby/rubygems/core\_ext/kernel\_require.rb:45:in `require' from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/generator/darkfish.rb:6:in`\<top (required)\>'  
from /usr/local/share/ruby/site\_ruby/rubygems/core\_ext/kernel\_require.rb:45:in `require' from /usr/local/share/ruby/site_ruby/rubygems/core_ext/kernel_require.rb:45:in`require'  
from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/rdoc.rb:563:in `<top (required)>' from /usr/local/share/ruby/site_ruby/rubygems/core_ext/kernel_require.rb:45:in`require'  
from /usr/local/share/ruby/site\_ruby/rubygems/core\_ext/kernel\_require.rb:45:in `require' from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/rubygems_hook.rb:64:in`load\_rdoc'  
from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/rubygems\_hook.rb:229:in `setup' from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/rubygems_hook.rb:142:in`generate'  
from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/rubygems\_hook.rb:54:in `block in generation_hook' from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/rubygems_hook.rb:53:in`each'  
from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/rubygems\_hook.rb:53:in `generation_hook' from /usr/local/share/ruby/site_ruby/rubygems/dependency_installer.rb:382:in`call'  
from /usr/local/share/ruby/site\_ruby/rubygems/dependency\_installer.rb:382:in `block (2 levels) in install' from /usr/local/share/ruby/site_ruby/rubygems/dependency_installer.rb:381:in`each'  
from /usr/local/share/ruby/site\_ruby/rubygems/dependency\_installer.rb:381:in `block in install' from /usr/local/share/ruby/site_ruby/rubygems/dependency_installer.rb:401:in`in\_background'  
from /usr/local/share/ruby/site\_ruby/rubygems/dependency\_installer.rb:380:in `install' from /usr/local/share/ruby/site_ruby/rubygems/commands/install_command.rb:166:in`block in execute'  
from /usr/local/share/ruby/site\_ruby/rubygems/commands/install\_command.rb:158:in `each' from /usr/local/share/ruby/site_ruby/rubygems/commands/install_command.rb:158:in`execute'  
from /usr/local/share/ruby/site\_ruby/rubygems/command.rb:305:in `invoke_with_build_args' from /usr/local/share/ruby/site_ruby/rubygems/command_manager.rb:170:in`process\_args'  
from /usr/local/share/ruby/site\_ruby/rubygems/command\_manager.rb:130:in `run' from /usr/local/share/ruby/site_ruby/rubygems/gem_runner.rb:60:in`run'  
from /usr/bin/gem:21:in `'

---

<div class="post-metadata">

**Author:** ![sravya](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@sravya](https://discuss.elastic.co/u/sravya)\
**Post date:** [June 7, 2017, 4:30pm UTC](https://discuss.elastic.co/t/kibana-package-creation-issue/88149/5 "2017-06-07T16:30:34Z")

</div>

but after this I am facing the same error while running this command:npm run build -- --rpm --force

---

<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:** [July 5, 2017, 4:30pm UTC](https://discuss.elastic.co/t/kibana-package-creation-issue/88149/6 "2017-07-05T16:30:50Z")

</div>

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