Error message ENOENT when trying to add a new JDBC driver

Symptoms

When trying to add a new JDBC driver via the LucidWorks Search Admin UI, the following error is presented:


org.jruby.exceptions.RaiseException: (Errno::ENOENT) C:/tmp
    at org.jruby.RubyFile.stat(org/jruby/RubyFile.java:843)
    at RUBY.tmpdir(jar:file:/C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/lib/jruby-stdlib-complete-1.7.10.jar!/META-INF/jruby.home/lib/ruby/shared/tmpdir.rb:33)
    at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)
    at RUBY.tmpdir(jar:file:/C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/lib/jruby-stdlib-complete-1.7.10.jar!/META-INF/jruby.home/lib/ruby/shared/tmpdir.rb:30)
    at RUBY.tmpdir(jar:file:/C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/lib/jruby-stdlib-complete-1.7.10.jar!/META-INF/jruby.home/lib/ruby/shared/tmpdir.rb:109)
    at RUBY.create(jar:file:/C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/lib/jruby-stdlib-complete-1.7.10.jar!/META-INF/jruby.home/lib/ruby/shared/tmpdir.rb:141)
    at org.jruby.ext.tempfile.Tempfile.initialize19(org/jruby/ext/tempfile/Tempfile.java:94)
    at org.jruby.RubyIO.new(org/jruby/RubyIO.java:852)
    at RUBY.get_current_head_and_filename_and_content_type_and_name_and_body(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-1.4.5/lib/rack/multipart/parser.rb:104)
    at RUBY.parse(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-1.4.5/lib/rack/multipart/parser.rb:18)
    at org.jruby.RubyKernel.loop(org/jruby/RubyKernel.java:1519)
    at RUBY.parse(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-1.4.5/lib/rack/multipart/parser.rb:17)
    at RUBY.parse_multipart(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-1.4.5/lib/rack/multipart.rb:25)
    at RUBY.parse_multipart(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-1.4.5/lib/rack/request.rb:336)
    at RUBY.POST(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-1.4.5/lib/rack/request.rb:201)
    at RUBY.method_override(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-1.4.5/lib/rack/methodoverride.rb:26)
    at RUBY.call(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-1.4.5/lib/rack/methodoverride.rb:14)
    at RUBY.call(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-1.4.5/lib/rack/runtime.rb:17)
    at RUBY.call(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/activesupport-3.2.16/lib/active_support/cache/strategy/local_cache.rb:72)
    at RUBY.call(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-1.4.5/lib/rack/lock.rb:15)
    at RUBY.forward(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-cache-1.2/lib/rack/cache/context.rb:136)
    at RUBY.pass(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-cache-1.2/lib/rack/cache/context.rb:143)
    at RUBY.invalidate(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-cache-1.2/lib/rack/cache/context.rb:155)
    at RUBY.call!(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-cache-1.2/lib/rack/cache/context.rb:71)
    at RUBY.call(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/rack-cache-1.2/lib/rack/cache/context.rb:51)
    at RUBY.call(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/railties-3.2.16/lib/rails/engine.rb:484)
    at RUBY.call(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/railties-3.2.16/lib/rails/application.rb:231)
    at RUBY.method_missing(C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/gems/gems/railties-3.2.16/lib/rails/railtie/configurable.rb:30)
    at RUBY.call(file:/C:/LucidWorks/LucidWorksSearch27/app/webapps/admin/WEB-INF/lib/jruby-rack-1.1.13.3.jar!/rack/handler/servlet.rb:22)

Cause

 The Admin UI expects a temporary directory to be available in order to upload the JDBC drivers.

Resolution

As a workaround, you can create the missing temporary directory specified in the error message.

In the above case you could create a folder called C:/tmp and try uploading the JDBC driver again.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk