I-Diario - Sidekiq retornando erro

Após rodar o comando *bundle exec sidekiq* o sistema me retornou o seguinte erro:

2020-03-25T01:30:48.746Z 1283 TID-gpv0hlomo INFO: Running in ruby 2.3.7p456 (2018-03-28 revision 63024) [x86_64-linux]
2020-03-25T01:30:48.746Z 1283 TID-gpv0hlomo INFO: See LICENSE and the LGPL-3.0 for licensing details.
2020-03-25T01:30:48.747Z 1283 TID-gpv0hlomo INFO: Upgrade to Sidekiq Pro for more features and support: http://sidekiq.org
2020-03-25T01:30:48.747Z 1283 TID-gpv0hlomo INFO: Booting Sidekiq 5.0.3 with redis options {:id=>“Sidekiq-server-PID-1283”, :url=>nil}
Error connecting to Redis on 127.0.0.1:6379 (Errno::ECONNREFUSED)
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis/client.rb:345:in rescue in establish_connection' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis/client.rb:330:in establish_connection’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis/client.rb:101:in block in connect' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis/client.rb:293:in with_reconnect’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis/client.rb:100:in connect' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis/client.rb:364:in ensure_connected’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis/client.rb:221:in block in process' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis/client.rb:306:in logging’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis/client.rb:220:in process' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis/client.rb:120:in call’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis.rb:251:in block in info' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis.rb:58:in block in synchronize’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/2.3.0/monitor.rb:214:in mon_synchronize' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis.rb:58:in synchronize’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/redis-3.3.5/lib/redis.rb:250:in info' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/sidekiq-5.0.3/lib/sidekiq.rb:113:in block in redis_info’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/sidekiq-5.0.3/lib/sidekiq.rb:95:in block in redis' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:65:in block (2 levels) in with’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:64:in handle_interrupt' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:64:in block in with’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:61:in handle_interrupt' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:61:in with’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/sidekiq-5.0.3/lib/sidekiq.rb:92:in redis' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/sidekiq-5.0.3/lib/sidekiq.rb:106:in redis_info’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/sidekiq-5.0.3/lib/sidekiq/cli.rb:81:in run' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/sidekiq-5.0.3/bin/sidekiq:12:in <top (required)>’
/home/idiario/.rbenv/versions/2.3.7/bin/sidekiq:22:in load' /home/idiario/.rbenv/versions/2.3.7/bin/sidekiq:22:in <top (required)>’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/lib/bundler/cli/exec.rb:74:in load' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/lib/bundler/cli/exec.rb:74:in kernel_load’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/lib/bundler/cli/exec.rb:28:in run' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/lib/bundler/cli.rb:463:in exec’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor/command.rb:27:in run' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in invoke_command’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor.rb:387:in dispatch' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/lib/bundler/cli.rb:27:in dispatch’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor/base.rb:466:in start' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/lib/bundler/cli.rb:18:in start’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/exe/bundle:30:in block in <top (required)>' /home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/lib/bundler/friendly_errors.rb:124:in with_friendly_errors’
/home/idiario/.rbenv/versions/2.3.7/lib/ruby/gems/2.3.0/gems/bundler-1.17.3/exe/bundle:22:in <top (required)>' /home/idiario/.rbenv/versions/2.3.7/bin/bundle:22:in load’
/home/idiario/.rbenv/versions/2.3.7/bin/bundle:22:in `’

#######
Após este evento, cliquei no botão de sincronização completa e, na página carregada me apareceu o seguinte erro:

Error connecting to Redis on 127.0.0.1:6379 (Errno::ECONNREFUSED)

Extracted source (around line #33 ):

31 32 33 34 35 36 )

job_id = IeducarSynchronizerWorker.perform_in(

1.second,

entity_id,

synchronization.id,

Rails.root: /home/idiario/i-diario

Application Trace | Framework Trace | Full Trace

app/models/ieducar_api_configuration.rb:33:in `block in start_synchronization'app/models/ieducar_api_configuration.rb:22:in `start_synchronization'app/controllers/synchronizations_controller.rb:5:in `create'app/controllers/application_controller.rb:365:in `set_thread_origin_type'app/controllers/application_controller.rb:356:in `set_user_current'app/models/entity.rb:20:in `using_connection'app/controllers/application_controller.rb:67:in `handle_customer'

Request

Parameters :

{"_method"=>“post”, “authenticity_token”=>“2jU2lqk0Xhp4ThHFnBpShbkZx7jBok5mm+kYJDtrXtF3uQUr+o+4BYGwcfRg5DMHmiRsVCAWJcZs2DmGfOskAw==”, “full”=>“true”, “locale”=>“pt-BR”}

#######
Alguém poderia me indicar uma saída?
P.S. Os testes estão sendo realizados no S.O Ubuntu 18.04 com o Postgresql 9.4 em outro servidor dedicado.

Boa noite, você instalou o servidor radis?

sudo apt install redis-server

Bom dia, obrigado pelo retorno.
Realmente, eu instalei o redis-server e o sidekiq ficou funcional. Apenas a sincronização está apresentando o erro < Chave de acesso inválida! >
Valeu pela dica e, sugiro que essa informação faça parte do manual de instalação no tópico das dependências do I-Diário.

Oi @erton a chave está no i-educar, em Configurações, Configurações, Configurações gerais.

Olá @tiago.camargo e @flavio já inseri as chaves conforme orientação do @tiago.camargo porém continua o mesmo erro “Chave se acesso inválida”

@erton, da uma olhada aqui.

Olha sem saber como é a sua instalação fica difícil, é modo produção, dev.?
Isso acontece só na sincronização, quando sobe o servidor, qual comados você ta usando?

Olá @tiago.camargo, nesse caminho não encontrei o campo com a chave de acesso, poderia apresentar um print.