[i-Diário sicronizando com I-educar] erro

#1

(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)

#2

Ao clicar no botão sincronizar apresenta o seguinte erro acima. Porém seguir um procedimento em um topico aqui no forum e ao executar o comando bundle exec sidekiq aparesenta o seguinte erro abaixo.

.ss,  $$:         .,d$
`$$P,d$P'    .,md$P"'
 ,$$$$$bmmd$$$P^'

.d$$$$$$$$$$P’
$$^’ "^$$$' ____ _ _ _ _ $: ,$$: / ___|(_) __| | ___| | _(_) __ _b :$$ ___ | |/ |/ _ \ |/ / |/ _ |
$$: ) | | (| | __/ <| | (| |
$$ |
/||_,|___||__|_, |
.d$$ |
|

2019-04-12T19:07:50.820Z 31925 TID-go26kmjq0 INFO: Running in ruby 2.2.6p396 (2016-11-15 revision 56800) [x86_64-linux]
2019-04-12T19:07:50.820Z 31925 TID-go26kmjq0 INFO: See LICENSE and the LGPL-3.0 for licensing details.
2019-04-12T19:07:50.820Z 31925 TID-go26kmjq0 INFO: Upgrade to Sidekiq Pro for more features and support: http://sidekiq.org
getaddrinfo: Temporary failure in name resolution
/usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/connection/ruby.rb:229:in getaddrinfo' /usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/connection/ruby.rb:229:inconnect’
/usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/connection/ruby.rb:313:in connect' /usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/client.rb:336:inestablish_connection’
/usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/client.rb:101:in block in connect' /usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/client.rb:293:inwith_reconnect’
/usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/client.rb:100:in connect' /usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/instrumentation/redis.rb:66:inblock in connect’
/usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/datastores.rb:111:in block in wrap' /usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/method_tracer.rb:73:inblock in trace_execution_scoped’
/usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/method_tracer_helpers.rb:82:in trace_execution_scoped' /usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/method_tracer.rb:71:intrace_execution_scoped’
/usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/datastores.rb:108:in wrap' /usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/instrumentation/redis.rb:65:inconnect’
/usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/client.rb:364:in ensure_connected' /usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/client.rb:221:inblock in process’
/usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/client.rb:306:in logging' /usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/client.rb:220:inprocess’
/usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis/client.rb:120:in call' /usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/instrumentation/redis.rb:42:inblock in call’
/usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/datastores.rb:111:in block in wrap' /usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/method_tracer.rb:73:inblock in trace_execution_scoped’
/usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/method_tracer_helpers.rb:82:in trace_execution_scoped' /usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/method_tracer.rb:71:intrace_execution_scoped’
/usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/datastores.rb:108:in wrap' /usr/share/rvm/gems/ruby-2.2.6/gems/newrelic_rpm-3.14.0.305/lib/new_relic/agent/instrumentation/redis.rb:41:incall’
/usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis.rb:251:in block in info' /usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis.rb:58:inblock in synchronize’
/usr/share/rvm/rubies/ruby-2.2.6/lib/ruby/2.2.0/monitor.rb:211:in mon_synchronize' /usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis.rb:58:insynchronize’
/usr/share/rvm/gems/ruby-2.2.6/gems/redis-3.3.5/lib/redis.rb:250:in info' /usr/share/rvm/gems/ruby-2.2.6/gems/sidekiq-5.0.3/lib/sidekiq.rb:113:inblock in redis_info’
/usr/share/rvm/gems/ruby-2.2.6/gems/sidekiq-5.0.3/lib/sidekiq.rb:95:in block in redis' /usr/share/rvm/gems/ruby-2.2.6/gems/connection_pool-2.2.2/lib/connection_pool.rb:65:inblock (2 levels) in with’
/usr/share/rvm/gems/ruby-2.2.6/gems/connection_pool-2.2.2/lib/connection_pool.rb:64:in handle_interrupt' /usr/share/rvm/gems/ruby-2.2.6/gems/connection_pool-2.2.2/lib/connection_pool.rb:64:inblock in with’
/usr/share/rvm/gems/ruby-2.2.6/gems/connection_pool-2.2.2/lib/connection_pool.rb:61:in handle_interrupt' /usr/share/rvm/gems/ruby-2.2.6/gems/connection_pool-2.2.2/lib/connection_pool.rb:61:inwith’
/usr/share/rvm/gems/ruby-2.2.6/gems/sidekiq-5.0.3/lib/sidekiq.rb:92:in redis' /usr/share/rvm/gems/ruby-2.2.6/gems/sidekiq-5.0.3/lib/sidekiq.rb:106:inredis_info’
/usr/share/rvm/gems/ruby-2.2.6/gems/sidekiq-5.0.3/lib/sidekiq/cli.rb:81:in run' /usr/share/rvm/gems/ruby-2.2.6/gems/sidekiq-5.0.3/bin/sidekiq:12:in<top (required)>’
/usr/share/rvm/gems/ruby-2.2.6/bin/sidekiq:23:in load' /usr/share/rvm/gems/ruby-2.2.6/bin/sidekiq:23:in
/usr/share/rvm/gems/ruby-2.2.6/bin/ruby_executable_hooks:24:in eval' /usr/share/rvm/gems/ruby-2.2.6/bin/ruby_executable_hooks:24:in

Alguém sabe como resolver essa questão? Muito obrigado a todos do forum.

#3

Kara ainda nao cheguei nessa parte, mais acabei de ver em outro topico algo sobre isso.

#4

O redis foi instalado?

o conteúdo do arquivo ‘initializers/sidekiq.rb’ aqui é esse:

require ‘sidekiq’

Sidekiq.configure_server do |config|
config.redis = { url: ‘redis://localhost:6379’ }
end

Sidekiq.configure_client do |config|
config.redis = { url: ‘redis://localhost:6379’ }
end