# Package Creation Errors **URL:** \ **Category:** Kibana\ **Created:** [June 1, 2017, 3:10am UTC](https://discuss.elastic.co/t/package-creation-errors/87831 "2017-06-01T03:10:26Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![FareehaNaaz](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@FareehaNaaz](https://discuss.elastic.co/u/FareehaNaaz)\ **Post date:** [June 1, 2017, 3:10am UTC](https://discuss.elastic.co/t/package-creation-errors/87831/1 "2017-06-01T03:10:26Z")
Hi! iwas trying to create kibana rpm package "npm run build -- --rpm", and went 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. ---
**Author:** ![softec17](https://avatars.discourse-cdn.com/v4/letter/s/4af34b/32.png) [@softec17](https://discuss.elastic.co/u/softec17)\ **Post date:** [June 1, 2017, 11:15am UTC](https://discuss.elastic.co/t/package-creation-errors/87831/2 "2017-06-01T11:15:41Z")
hi, i too face the same problem can anyone help us? ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [June 1, 2017, 1:12pm UTC](https://discuss.elastic.co/t/package-creation-errors/87831/3 "2017-06-01T13:12:32Z")
> [@FareehaNaaz](#): > > 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 Could you share the contents of `/home/farya/.npm/_logs/2017-05-31T10_36_12_445Z-debug.log` here? There might be some further clues in there. Also, could you share the complete output of `npm run build -- --rpm` as well? That will give me a better idea of where the build process failed. Thanks, Shaunak ---
**Author:** ![FareehaNaaz](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@FareehaNaaz](https://discuss.elastic.co/u/FareehaNaaz)\ **Post date:** [June 1, 2017, 1:56pm UTC](https://discuss.elastic.co/t/package-creation-errors/87831/4 "2017-06-01T13:56:41Z")
[farya@kibanasgpl kibana]$ 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 **and 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 ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [June 1, 2017, 2:42pm UTC](https://discuss.elastic.co/t/package-creation-errors/87831/5 "2017-06-01T14:42:06Z")
Hmm... Nothing in the output or error log seems to help. I am unable to reproduce it on my end as well. Would you mind editing your `tasks/build/notice.js` file and adding a debugging statement? Specifically, could you add `console.log({ kibanaDir, noticePath });` after line 22 where `noticePath` is initialized? Then run `npm run build -- --rpm` again and paste here the output of that debugging statement. Thanks! ---
**Author:** ![softec17](https://avatars.discourse-cdn.com/v4/letter/s/4af34b/32.png) [@softec17](https://discuss.elastic.co/u/softec17)\ **Post date:** [June 1, 2017, 3:28pm UTC](https://discuss.elastic.co/t/package-creation-errors/87831/6 "2017-06-01T15:28:44Z")
hi@shaunak, I followed your suggestion.....and i got the error below: [farya@kibanasgpl kibana]$ 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 { kibanaDir: '/home/farya/kibana/build/kibana', noticePath: '/home/farya/kibana/build/kibana/NOTICE.txt' } 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-01T15\_16\_28\_153Z-debug.log ---
**Author:** ![softec17](https://avatars.discourse-cdn.com/v4/letter/s/4af34b/32.png) [@softec17](https://discuss.elastic.co/u/softec17)\ **Post date:** [June 1, 2017, 3:40pm UTC](https://discuss.elastic.co/t/package-creation-errors/87831/7 "2017-06-01T15:40:15Z")
@shaunak....the edited notice.js file (as per your suggestion) is below: import { resolve } from 'path'; import { getInstalledPackages, generateNoticeText, } from '../lib'; async function generate(grunt, directory) { return await generateNoticeText({ packages: await getInstalledPackages({ directory, licenseOverrides: grunt.config.get('licenses.options.overrides') }), nodeDir: grunt.config.get('platforms')[0].nodeDir }); } export default function (grunt) { grunt.registerTask('\_build:notice', 'Adds a notice', function () { const done = this.async(); const kibanaDir = resolve(grunt.config.get('buildDir'), 'kibana'); const noticePath = resolve(kibanaDir, 'NOTICE.txt'); console.log({ kibanaDir, noticePath }); ``` generate(grunt, kibanaDir).then( (noticeText) => { grunt.file.write(noticePath, noticeText); done(); }, (error) => { grunt.fail.fatal(error); done(error); } ); ``` }); } ---
**Author:** ![softec17](https://avatars.discourse-cdn.com/v4/letter/s/4af34b/32.png) [@softec17](https://discuss.elastic.co/u/softec17)\ **Post date:** [June 1, 2017, 3:43pm UTC](https://discuss.elastic.co/t/package-creation-errors/87831/8 "2017-06-01T15:43:03Z")
Logs of the /home/farya/.npm/\_logs/2017-06-01T15\_16\_28\_153Z-debug.log:: 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 ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [June 1, 2017, 3:46pm UTC](https://discuss.elastic.co/t/package-creation-errors/87831/9 "2017-06-01T15:46:36Z")
Thanks, unfortunately that didn't help much either ☹ Hmm... I'm stumped as to why this is happening. I asked a few other folks on my team and one of them suggested a possible workaround: could you try `rm -rf node_modules`, then `npm install`again, and then running `npm run build -- --rpm`? ---
**Author:** ![softec17](https://avatars.discourse-cdn.com/v4/letter/s/4af34b/32.png) [@softec17](https://discuss.elastic.co/u/softec17)\ **Post date:** [June 1, 2017, 4:15pm UTC](https://discuss.elastic.co/t/package-creation-errors/87831/10 "2017-06-01T16:15:10Z")
@shaunak, I got the same error...after running those two commands: 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 linux-x86\_64 and corresponding sha > > Downloading windows-x86\_64 and corresponding sha > > Downloading darwin-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-01T16\_08\_54\_544Z-debug.log ---
**Author:** ![softec17](https://avatars.discourse-cdn.com/v4/letter/s/4af34b/32.png) [@softec17](https://discuss.elastic.co/u/softec17)\ **Post date:** [June 3, 2017, 8:41am UTC](https://discuss.elastic.co/t/package-creation-errors/87831/12 "2017-06-03T08:41:21Z")
Hi Shaunak, Please let me know if you get any chance to look into this issue. ---
**Author:** ![FareehaNaaz](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@FareehaNaaz](https://discuss.elastic.co/u/FareehaNaaz)\ **Post date:** [June 6, 2017, 6:17am UTC](https://discuss.elastic.co/t/package-creation-errors/87831/13 "2017-06-06T06:17:17Z")
can anyone guide us on this? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 4, 2017, 6:17am UTC](https://discuss.elastic.co/t/package-creation-errors/87831/14 "2017-07-04T06:17:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.