Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start kibana 5.1.1. Gives Module build failed: ModuleBuildError: Module build failed: URIError: URI malformed at decodeURIComponent (native) #9435

Closed
uxinaz opened this issue Dec 9, 2016 · 13 comments

Comments

@uxinaz
Copy link

uxinaz commented Dec 9, 2016

Downloaded es 5.1.1 and starts up fine. When trying to start kibana 5.1.1, I get the issue described in the txt file attached.

Let me know if you need more info.

Kibana version:
5.1.1

Elasticsearch version:
5.1.1

Server OS version:
MacOS 10.12.1

Browser version:
Chrome v54.0.2840.98 (64-bit)

Original install method (e.g. download page, yum, from source, etc.):
download from:
https://artifacts.elastic.co/downloads/kibana/kibana-5.1.1-darwin-x86_64.tar.gz

Description of the problem including expected versus actual behavior:
This looks like it is same problem mentioned here in April 2016:
#6858

I noticed autoprefixer-loader is still looking for:
"loader-utils": "^0.2.5",

Instead of 0.2.12 as mentioned in the issue 6858 above, so not sure what the fix is.

Steps to reproduce:

  1. Download kibana 5.1.1 tar:
    https://artifacts.elastic.co/downloads/kibana/kibana-5.1.1-darwin-x86_64.tar.gz

  2. Untar and cd into kibana-5.1.1/

  3. run bin/kibana

Errors in browser console (if relevant):
see txt file below...taken from my bash console.

Provide logs and/or server output (if relevant):
issueoutput.txt

@epixa
Copy link
Contributor

epixa commented Dec 12, 2016

Are you upgrading from a previous version of Kibana or installing fresh? I'm unable to reproduce this on a fresh install.

@uxinaz
Copy link
Author

uxinaz commented Dec 12, 2016 via email

@rccclr
Copy link

rccclr commented Dec 14, 2016

I have the same problem (@uxinaz) with the same version 5.1.1 in Ubuntu.

@epixa
Copy link
Contributor

epixa commented Dec 14, 2016

Did you verify the sha of the download as the docs encourage? Perhaps your downloads somehow got corrupted.

I'm still unable to reproduce, and I've verified the sha as well:

courtmbp:Desktop Court$ wget https://artifacts.elastic.co/downloads/kibana/kibana-5.1.1-darwin-x86_64.tar.gz
--2016-12-14 10:54:52--  https://artifacts.elastic.co/downloads/kibana/kibana-5.1.1-darwin-x86_64.tar.gz
Resolving artifacts.elastic.co... 184.73.171.14, 107.22.240.134, 184.72.218.178, ...
Connecting to artifacts.elastic.co|184.73.171.14|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 37098756 (35M) [application/x-gzip]
Saving to: 'kibana-5.1.1-darwin-x86_64.tar.gz'

kibana-5.1.1-darwin-x86_64.t 100%[==============================================>]  35.38M  7.05MB/s   in 6.5s   

2016-12-14 10:54:59 (5.42 MB/s) - 'kibana-5.1.1-darwin-x86_64.tar.gz' saved [37098756/37098756]

courtmbp:Desktop Court$ wget https://artifacts.elastic.co/downloads/kibana/kibana-5.1.1-darwin-x86_64.tar.gz.sha1
--2016-12-14 10:55:05--  https://artifacts.elastic.co/downloads/kibana/kibana-5.1.1-darwin-x86_64.tar.gz.sha1
Resolving artifacts.elastic.co... 107.22.240.134, 184.72.218.178, 184.73.171.14, ...
Connecting to artifacts.elastic.co|107.22.240.134|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 40 [application/octet-stream]
Saving to: 'kibana-5.1.1-darwin-x86_64.tar.gz.sha1'

kibana-5.1.1-darwin-x86_64.t 100%[==============================================>]      40  --.-KB/s   in 0s     

2016-12-14 10:55:05 (2.24 MB/s) - 'kibana-5.1.1-darwin-x86_64.tar.gz.sha1' saved [40/40]

courtmbp:Desktop Court$ echo "`cat kibana-5.1.1-darwin-x86_64.tar.gz.sha1`"
9ce0613681871739663424eea666f843f96a050e
courtmbp:Desktop Court$ shasum kibana-5.1.1-darwin-x86_64.tar.gz
9ce0613681871739663424eea666f843f96a050e  kibana-5.1.1-darwin-x86_64.tar.gz
courtmbp:Desktop Court$ tar -xzf kibana-5.1.1-darwin-x86_64.tar.gz
courtmbp:Desktop Court$ cd kibana-5.1.1-darwin-x86_64
courtmbp:kibana-5.1.1-darwin-x86_64 Court$ bin/kibana
  log   [15:57:11.436] [info][status][plugin:kibana@5.1.1] Status changed from uninitialized to green - Ready
  log   [15:57:11.485] [info][status][plugin:elasticsearch@5.1.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [15:57:11.515] [info][status][plugin:console@5.1.1] Status changed from uninitialized to green - Ready
  log   [15:57:11.793] [info][status][plugin:timelion@5.1.1] Status changed from uninitialized to green - Ready
  log   [15:57:11.798] [info][listening] Server running at http://localhost:5601
  log   [15:57:11.799] [info][status][ui settings] Status changed from uninitialized to yellow - Elasticsearch plugin is yellow
  log   [15:57:16.824] [info][status][plugin:elasticsearch@5.1.1] Status changed from yellow to yellow - No existing Kibana index found
  log   [15:57:17.265] [info][status][plugin:elasticsearch@5.1.1] Status changed from yellow to green - Kibana index ready
  log   [15:57:17.265] [info][status][ui settings] Status changed from yellow to green - Ready

@rccclr
Copy link

rccclr commented Dec 14, 2016

In Ubuntu with VirtualBox
(Linux rccclr-VirtualBox 3.13.0-101-generic #148-Ubuntu SMP Thu Oct 20 22:08:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux)

The result of the same steps, its not ok. Attach image

Many thanks

image

@uxinaz
Copy link
Author

uxinaz commented Dec 14, 2016

I"ve been able to get 5.1.1 kibana/es running as expected on a different mac. I think i may need to chalk this issue up to some conflict on my previous mac that may have caused it.

It's something I'll continue to take a look at to see if I can reason out the conflict, but I don't see a need to keep this issue open. If I find a resolution, I'll reopen with comments.

@uxinaz uxinaz closed this as completed Dec 14, 2016
@epixa
Copy link
Contributor

epixa commented Dec 14, 2016

@uxinaz Please let us know if you do track it down! If there's a problem, we definitely want to fix it.

@rccclr
Copy link

rccclr commented Dec 15, 2016

Sorry for the confusion in the version (ubuntu-mac).
I have repeated the process and it works.
The previous time, I got the same error as @uxinaz
For me it's ok.
Many thanks

@rccclr
Copy link

rccclr commented Dec 15, 2016

@epixa I think I reproduced the problem.

Installation 5.1.1 without modification --->OK
Installation 5.1.1 with modification for debug in kibana.yml --->ERROR

optimize:
sourceMaps: '#cheap-source-map'
unsafeCache: true
lazyPrebuild: false

(see
https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#setting-up-your-development-environment)

In earlier versions it worked.
How do you configure these options for version 5.1.1?

Many thanks

@epixa
Copy link
Contributor

epixa commented Dec 15, 2016

@rccclr Those configurations are only intended to be used while Kibana is in dev mode when you're running it from source. I've just confirmed that they do still work in that context.

Are you sure they used to work on production builds? If so, that was purely by accident, and I strongly discourage anyone from using any of those things in production.

@rccclr
Copy link

rccclr commented Dec 15, 2016

@epixa Right now, we're still working, in mode development, not in production.
In an earlier version of Kibana 5.0 this configuration worked ok:
sh bin/kibana --dev
+
Optimize:
SourceMaps: '# cheap-source-map'
UnsafeCache: true
LazyPrebuild: false

The same with the version Kibana 5.1.1 ---> ERROR
"--dev unknow option"

How can I configure version 5.1.1 to work in "--dev" mode, as in the previous version?

Many thanks for help.

@epixa
Copy link
Contributor

epixa commented Dec 15, 2016

@rccclr While you're developing, I'd recommend using kibana directly from the git repo (per the contributing.md instructions) rather than downloading the production binaries from the website.

@rccclr
Copy link

rccclr commented Dec 16, 2016

@epixa I execute from git repo, and its OK, for me. Not problem.

Many thanks for the help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants