Error starting Kibana if special chars in path

Elastic Stack Kibana
1

After yarn start in github repository, I had this error when accessing to Kibana:

WARNING in ./src/legacy/ui/public/styles/font_awesome.less
    Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
    ModuleNotFoundError: Module not found: Error: Can't resolve '../fonts/fontawesome-webfont.eot' in '/Users/User/Documents/#Code - Check Out/elastic/kibana/src/legacy/ui/public/styles'
        at factory.create (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/webpack/lib/Compilation.js:814:10)
        at factory (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/webpack/lib/NormalModuleFactory.js:397:22)
        at actualFactory (/Users/User/Documents/#Code - Check Out/elastic/kibana/src/optimize/dynamic_dll_plugin/dynamic_dll_plugin.js:127:15)
        at resolver (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/webpack/lib/NormalModuleFactory.js:130:21)
        at asyncLib.parallel (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/webpack/lib/NormalModuleFactory.js:224:22)
        at /Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/neo-async/async.js:2817:7
        at /Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/neo-async/async.js:6783:13
        at normalResolver.resolve (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/webpack/lib/NormalModuleFactory.js:214:25)
        at doResolve (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/enhanced-resolve/lib/Resolver.js:184:12)
        at hook.callAsync (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/enhanced-resolve/lib/Resolver.js:238:5)
        at _fn0 (eval at create (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/tapable/lib/HookCodeFactory.js:32:10), <anonymous>:15:1)
        at resolver.doResolve (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/enhanced-resolve/lib/UnsafeCachePlugin.js:37:5)
        at hook.callAsync (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/enhanced-resolve/lib/Resolver.js:238:5)
        at _fn0 (eval at create (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/tapable/lib/HookCodeFactory.js:32:10), <anonymous>:15:1)
        at hook.callAsync (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/enhanced-resolve/lib/Resolver.js:238:5)
        at _fn0 (eval at create (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/tapable/lib/HookCodeFactory.js:32:10), <anonymous>:12:1)
        at resolver.doResolve (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/enhanced-resolve/lib/DescriptionFilePlugin.js:42:38)
        at hook.callAsync (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/enhanced-resolve/lib/Resolver.js:238:5)
        at _fn43 (eval at create (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/tapable/lib/HookCodeFactory.js:32:10), <anonymous>:402:1)
        at hook.callAsync (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/enhanced-resolve/lib/Resolver.js:238:5)
        at _fn0 (eval at create (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/tapable/lib/HookCodeFactory.js:32:10), <anonymous>:12:1)
        at resolver.doResolve (/Users/User/Documents/#Code - Check Out/elastic/kibana/node_modules/enhanced-resolve/lib/DescriptionFilePlugin.js:42:38)

I realized that maybe the path #Code - Check Out was maybe problematic and moved the whole kibana folder to /Users/User/Documents/ where it worked successfully.

Is it the plugin which is faulty not checking the special chars in folder or kibana code ?

Where/who should a bug be created ?

2

Hi, thanks for raising this issue. We think it is something related to Webpack and/or one of its loaders that Kibana is using. There may be some configuration options we can adjust to fix the issue. Would you mind opening an issue in Kibana repository? Then our Operations team can do some more digging.

1 Like
3

Jen-Huang, thanks for your quick answer, bug has been filled here. Awesome support, thanks!

4

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