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

Error on docker container #1

Closed
ghost opened this issue May 23, 2018 · 10 comments
Closed

Error on docker container #1

ghost opened this issue May 23, 2018 · 10 comments

Comments

@ghost
Copy link

ghost commented May 23, 2018

optimizer_1 | [ E 2018-05-23 13:06:16.8901 10/Ti age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /srv/app: The application encountered the following error: undefined local variable or method `server' for #<Rack::Builder:0x005569e292e7c0 @run=nil, @Map=nil, @use=[]> (NameError)

it runs without errors but on optimizing reques it fails and gives back an html back and this error

@frodrigo
Copy link
Contributor

Do you have more logs ?

@ghost
Copy link
Author

ghost commented May 24, 2018

/usr/local/rvm/gems/ruby-2.4.1/gems/json-1.8.6/lib/json/common.rb:155:in parse' /usr/local/rvm/gems/ruby-2.4.1/gems/json-1.8.6/lib/json/common.rb:155:in parse'
/server_mapotempo/mapotempo-web/lib/optim/optimizer_wrapper.rb:162:in optimize' /server_mapotempo/mapotempo-web/app/jobs/optimizer_job.rb:40:in block in perform'
/server_mapotempo/mapotempo-web/app/models/planning.rb:393:in block (2 levels) in optimize' /server_mapotempo/mapotempo-web/app/models/planning.rb:652:in unnil_positions'
/server_mapotempo/mapotempo-web/app/models/planning.rb:354:in block in optimize' /server_mapotempo/mapotempo-web/app/models/planning.rb:610:in amalgamate_stops_same_position'
/server_mapotempo/mapotempo-web/app/models/planning.rb:348:in optimize' /server_mapotempo/mapotempo-web/app/jobs/optimizer_job.rb:39:in perform'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/backend/base.rb:84:in block in invoke_job' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:61:in block in initialize'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:66:in execute' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:40:in run_callbacks'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/backend/base.rb:81:in invoke_job' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:230:in block (2 levels) in run'
/usr/local/rvm/rubies/ruby-2.4.1/lib/ruby/2.4.0/timeout.rb:93:in block in timeout' /usr/local/rvm/rubies/ruby-2.4.1/lib/ruby/2.4.0/timeout.rb:103:in timeout'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:230:in block in run' /usr/local/rvm/rubies/ruby-2.4.1/lib/ruby/2.4.0/benchmark.rb:308:in realtime'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:229:in run' /server_mapotempo/mapotempo-web/config/initializers/delayed_job.rb:21:in block in run'
/usr/local/rvm/gems/ruby-2.4.1/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in block in transaction' /usr/local/rvm/gems/ruby-2.4.1/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/transaction.rb:184:in within_new_transaction'
/usr/local/rvm/gems/ruby-2.4.1/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in transaction' /usr/local/rvm/gems/ruby-2.4.1/gems/activerecord-4.2.10/lib/active_record/transactions.rb:220:in transaction'
/server_mapotempo/mapotempo-web/config/initializers/delayed_job.rb:20:in run' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:306:in block in reserve_and_run_one_job'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:61:in block in initialize' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:66:in execute'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:40:in run_callbacks' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:306:in reserve_and_run_one_job'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:213:in block in work_off' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:212:in times'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:212:in work_off' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:175:in block (4 levels) in start'
/usr/local/rvm/rubies/ruby-2.4.1/lib/ruby/2.4.0/benchmark.rb:308:in realtime' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:174:in block (3 levels) in start'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:61:in block in initialize' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:66:in execute'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:40:in run_callbacks' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:173:in block (2 levels) in start'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:172:in loop' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:172:in block in start'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/plugins/clear_locks.rb:7:in block (2 levels) in <class:ClearLocks>' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:79:in block (2 levels) in add'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:61:in block in initialize' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:79:in block in add'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:66:in execute' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/lifecycle.rb:40:in run_callbacks'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/worker.rb:171:in start' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/command.rb:132:in run'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/command.rb:120:in block in run_process' /usr/local/rvm/gems/ruby-2.4.1/gems/daemons-1.2.4/lib/daemons/application.rb:266:in block in start_proc'
/usr/local/rvm/gems/ruby-2.4.1/gems/daemons-1.2.4/lib/daemons/application.rb:275:in start_proc' /usr/local/rvm/gems/ruby-2.4.1/gems/daemons-1.2.4/lib/daemons/application.rb:296:in start'
/usr/local/rvm/gems/ruby-2.4.1/gems/daemons-1.2.4/lib/daemons/controller.rb:59:in run' /usr/local/rvm/gems/ruby-2.4.1/gems/daemons-1.2.4/lib/daemons.rb:197:in block in run_proc'
/usr/local/rvm/gems/ruby-2.4.1/gems/daemons-1.2.4/lib/daemons/cmdline.rb:92:in catch_exceptions' /usr/local/rvm/gems/ruby-2.4.1/gems/daemons-1.2.4/lib/daemons.rb:196:in run_proc'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/command.rb:118:in run_process' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/command.rb:99:in block in daemonize'
/usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/command.rb:97:in times' /usr/local/rvm/gems/ruby-2.4.1/gems/delayed_job-4.1.2/lib/delayed/command.rb:97:in daemonize'

@ghost
Copy link
Author

ghost commented May 24, 2018

this is the delayer response log

@ghost
Copy link
Author

ghost commented May 25, 2018

sems like passenger crashes

@ghost
Copy link
Author

ghost commented May 25, 2018

redis-cache_1 | 1:M 25 May 11:05:20.884 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis-cache_1 | 1:M 25 May 11:05:20.884 # Server started, Redis version 3.2.11
redis-cache_1 | 1:M 25 May 11:05:20.884 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis-cache_1 | 1:M 25 May 11:05:20.884 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis-cache_1 | 1:M 25 May 11:05:20.884 * The server is now ready to accept connections on port 6379
optimizer_1 | [ N 2018-05-25 11:05:29.1745 7/T1 age/Wat/WatchdogMain.cpp:1259 ]: Starting Passenger watchdog...
optimizer_1 | [ N 2018-05-25 11:05:29.3008 10/T1 age/Cor/CoreMain.cpp:1236 ]: Starting Passenger core...
optimizer_1 | [ N 2018-05-25 11:05:29.3242 10/T1 age/Cor/CoreMain.cpp:251 ]: Passenger core running in multi-application mode.
optimizer_1 | [ N 2018-05-25 11:05:29.3599 10/T1 age/Cor/CoreMain.cpp:971 ]: Passenger core online, PID 10
optimizer_1 | [ N 2018-05-25 11:05:31.6493 10/T5 age/Cor/SecurityUpdateChecker.h:517 ]: Security update check: no update found (next check in 24 hours)
optimizer_1 | App 164 output: Error: The application encountered the following error: undefined local variable or method server' for #<Rack::Builder:0x00562e276d6658 @run=nil, @map=nil, @use=[]> (NameError) optimizer_1 | App 164 output: config.ru:1:in block in

'
optimizer_1 | App 164 output: /var/lib/gems/2.3.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in instance_eval' optimizer_1 | App 164 output: /var/lib/gems/2.3.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in initialize'
optimizer_1 | App 164 output: config.ru:1:in new' optimizer_1 | App 164 output: config.ru:1:in '
optimizer_1 | App 164 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:101:in eval' optimizer_1 | App 164 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:101:in preload_app'
optimizer_1 | App 164 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:189:in block in <module:App>' optimizer_1 | App 164 output: /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:380:in run_block_and_record_step_progress'
optimizer_1 | App 164 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:188:in <module:App>' optimizer_1 | App 164 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:30:in module:PhusionPassenger'
optimizer_1 | App 164 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:29:in <main>' optimizer_1 | [ E 2018-05-25 11:09:23.0680 10/Ti age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /srv/app: The application encountered the following error: undefined local variable or method server' for #<Rack::Builder:0x00562e276d6658 @run=nil, @Map=nil, @use=[]> (NameError)
optimizer_1 | Error ID: cb968664
optimizer_1 | Error details saved to: /tmp/passenger-error-G6lEdf.html
optimizer_1 |
optimizer_1 | [ E 2018-05-25 11:09:23.0709 10/T8 age/Cor/Con/CheckoutSession.cpp:276 ]: [Client 1-1] Cannot checkout session because a spawning error occurred. The identifier of the error is cb968664. Please see earlier logs for details about the error.
optimizer_1 | 2018/05/25 11:09:23 [error] 19#19: *1 recv() failed (104: Connection reset by peer) while sending to client, client: ::ffff:192.168.0.1, server: , request: "POST /0.1/vrp/submit.json HTTP/1.1", upstream: "passenger:unix:/tmp/passenger.kshteOQ/agents.s/core:", host: "192.168.0.1:8083"
optimizer_1 | ::ffff:192.168.0.1 - - [25/May/2018:11:09:23 +0000] "POST /0.1/vrp/submit.json HTTP/1.1" 500 4384 "-" "rest-client/2.0.2 (linux-gnu x86_64) ruby/2.4.1p111"
optimizer_1 | App 208 output: Error: The application encountered the following error: undefined local variable or method server' for #<Rack::Builder:0x005592b8b1be80 @run=nil, @map=nil, @use=[]> (NameError) optimizer_1 | App 208 output: config.ru:1:in block in '
optimizer_1 | App 208 output: /var/lib/gems/2.3.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in instance_eval' optimizer_1 | App 208 output: /var/lib/gems/2.3.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in initialize'
optimizer_1 | App 208 output: config.ru:1:in new' optimizer_1 | App 208 output: config.ru:1:in '
optimizer_1 | App 208 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:101:in eval' optimizer_1 | App 208 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:101:in preload_app'
optimizer_1 | App 208 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:189:in block in <module:App>' optimizer_1 | App 208 output: /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:380:in run_block_and_record_step_progress'
optimizer_1 | App 208 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:188:in <module:App>' optimizer_1 | App 208 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:30:in module:PhusionPassenger'
optimizer_1 | App 208 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:29:in <main>' optimizer_1 | [ E 2018-05-25 11:09:47.7260 10/Tn age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /srv/app: The application encountered the following error: undefined local variable or method server' for #<Rack::Builder:0x005592b8b1be80 @run=nil, @Map=nil, @use=[]> (NameError)
optimizer_1 | Error ID: 85be73f3
optimizer_1 | Error details saved to: /tmp/passenger-error-HkG0cy.html

@ghost
Copy link
Author

ghost commented May 28, 2018

Any solution?

@braktar
Copy link
Contributor

braktar commented May 28, 2018

Are those logs coming from Mapotempo Web ? Did you try to send a problem directly to the optimizer-api ?

@ghost
Copy link
Author

ghost commented May 28, 2018

yes i try.. the second log is from mapotempo web ..

@ghost
Copy link
Author

ghost commented May 29, 2018

i cant resolve this error. it gives me the same.. does optimizer api needs osrm inside the machine and maybe vroom does not find default instance for osrm?

@braktar
Copy link
Contributor

braktar commented May 29, 2018

Optimizer api doesn't need to have OSRM in the same machine, it only requires to have the correct url and api_key for the router in the config/environments files

Vroom uses the matrix provided by the router through Optimizer API.

@braktar braktar closed this as completed Dec 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants