Question

Question about spinning up a new looker instance

  • 14 March 2015
  • 2 replies
  • 55 views

We are spinning up a new looker instance for a new product. I am having trouble getting started server is 500 when I pop in the git url for the repo i just created. Help!


2015-03-14 02:57:49.908 +0000 [ERROR|01358|] :: non-absolute home
org/jruby/RubyFile.java:754:in `expand_path'
lib/helltool/models/ssh_deploy_key.rb:27:in `ssh_path'
lib/helltool/models/ssh_deploy_key.rb:12:in `initialize'
lib/helltool/controllers/projects/git_setup_controller.rb:29:in `Engine'
org/jruby/RubyMethod.java:128:in `call'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:1540:in `compile!'
org/jruby/RubyProc.java:271:in `call'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:950:in `route!'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:966:in `route_eval'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:950:in `route!'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:987:in `process_route'
org/jruby/RubyKernel.java:1270:in `catch'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:985:in `process_route'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:948:in `route!'
org/jruby/RubyArray.java:1613:in `each'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:947:in `route!'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:1059:in `dispatch!'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:1041:in `invoke'
org/jruby/RubyKernel.java:1270:in `catch'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:1041:in `invoke'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:1056:in `dispatch!'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:882:in `call!'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:1041:in `invoke'
org/jruby/RubyKernel.java:1270:in `catch'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:1041:in `invoke'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:882:in `call!'
lib/helltool/engine.rb:124:in `__ensure__'
lib/helltool/engine.rb:122:in `call!'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:870:in `call'
/home/looker/looker/looker.jar!/gems/warden-1.2.1/lib/warden/manager.rb:35:in `call'
org/jruby/RubyKernel.java:1270:in `catch'
/home/looker/looker/looker.jar!/gems/warden-1.2.1/lib/warden/manager.rb:34:in `call'
lib/rack/static_cache.rb:81:in `call'
/home/looker/looker/looker.jar!/gems/rack-rewrite-1.2.1/lib/rack/rewrite.rb:20:in `call'
lib/rack/looker_frame_options.rb:14:in `call'
/home/looker/looker/looker.jar!/gems/rack_csrf-2.4.0/lib/rack/csrf.rb:44:in `call'
/home/looker/looker/looker.jar!/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'
lib/rack/flash.rb:119:in `call'
/home/looker/looker/looker.jar!/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in `context'
/home/looker/looker/looker.jar!/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:in `call'
lib/rack/secure.rb:10:in `call'
/home/looker/looker/looker.jar!/gems/rack-1.5.2/lib/rack/deflater.rb:25:in `call'
/home/looker/looker/looker.jar!/gems/rack-protection-1.5.0/lib/rack/protection/xss_header.rb:18:in `call'
/home/looker/looker/looker.jar!/gems/rack-protection-1.5.0/lib/rack/protection/path_traversal.rb:16:in `call'
/home/looker/looker/looker.jar!/gems/rack-protection-1.5.0/lib/rack/protection/json_csrf.rb:18:in `call'
/home/looker/looker/looker.jar!/gems/rack-protection-1.5.0/lib/rack/protection/base.rb:49:in `call'
/home/looker/looker/looker.jar!/gems/rack-protection-1.5.0/lib/rack/protection/base.rb:49:in `call'
/home/looker/looker/looker.jar!/gems/rack-protection-1.5.0/lib/rack/protection/base.rb:49:in `call'
/home/looker/looker/looker.jar!/gems/rack-1.5.2/lib/rack/nulllogger.rb:9:in `call'
/home/looker/looker/looker.jar!/gems/rack-1.5.2/lib/rack/head.rb:11:in `call'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:175:in `call'
/home/looker/looker/looker.jar!/gems/sinatra-1.4.3/lib/sinatra/base.rb:1949:in `call'
/home/looker/looker/looker.jar!/gems/rack-1.5.2/lib/rack/builder.rb:138:in `call'
/home/looker/looker/looker.jar!/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in `call'
org/jruby/RubyArray.java:1613:in `each'
/home/looker/looker/looker.jar!/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `call'
/home/looker/looker/looker.jar!/gems/rack-1.5.2/lib/rack/builder.rb:138:in `call'
/home/looker/looker/looker.jar!/gems/puma-2.8.1/lib/puma/server.rb:490:in `handle_request'
/home/looker/looker/looker.jar!/gems/puma-2.8.1/lib/puma/server.rb:488:in `handle_request'
/home/looker/looker/looker.jar!/gems/puma-2.8.1/lib/puma/server.rb:361:in `process_client'
/home/looker/looker/looker.jar!/gems/puma-2.8.1/lib/puma/server.rb:357:in `process_client'
/home/looker/looker/looker.jar!/gems/puma-2.8.1/lib/puma/server.rb:254:in `run'
org/jruby/RubyProc.java:271:in `call'
/home/looker/looker/looker.jar!/gems/puma-2.8.1/lib/puma/thread_pool.rb:92:in `spawn_thread'

2 replies

Userlevel 4
Badge

Hey Rex, this looks like a pathing issue. Are you using the looker startup script to start Looker? A ./looker restart might be worth a shot to see if it fixes the pathing.

So this was resolved by downloading the latest startup script and stopping our looker instance then starting it with the looker start up script. It appears that there is some initialization magic that happens that is not being triggered in our startup script.

sv stop looker

./looker start

./looker stop

sv start looker

We will be working to get our startup script aligned so that configuration management can spin up a new looker and not force us to do this manual intervention.

Reply