ruby-on-rails - Sidekiq 死于以下错误 :NOAUTH Authentication required-6ren

ruby-on-rails - Sidekiq 死于以下错误 :NOAUTH Authentication required

转载作者：可可西里更新时间：2023-11-01 11:47:38

我在centos7.1部署gitlab，启动gitlab时出现错误:“pid 为 9307 的 GitLab Unicorn Web 服务器正在运行。GitLab Sidekiq 作业调度程序未运行。”我检查 sidekiq.log 如下:

2016-01-22T12:52:37.630Z 9990 TID-osgvasil4 INFO: [Sidetiq] Sidetiq v0.6.3 - Copyright (c) 2012-2013, Tobias Svensson <tob@tobiassvensson.co.uk>
2016-01-22T12:52:37.631Z 9990 TID-osgvasil4 INFO: [Sidetiq] Sidetiq is covered by the 3-clause BSD license.
2016-01-22T12:52:37.631Z 9990 TID-osgvasil4 INFO: [Sidetiq] See LICENSE and http://opensource.org/licenses/BSD-3-Clause for licensing details.
2016-01-22T12:52:37.631Z 9990 TID-osgvasil4 INFO: [Sidetiq] Sidetiq::Supervisor start
2016-01-22T12:52:37.632Z 9990 TID-osgvy7rgw INFO: [Sidetiq] Sidetiq::Actor::Clock id: 69937594813880 initialize
2016-01-22T12:52:37.633Z 9990 TID-osgvy6rww INFO: [Sidetiq] Sidetiq::Actor::Handler id: 69937594769280 initialize
2016-01-22T12:52:37.634Z 9990 TID-osgvy6kqk INFO: [Sidetiq] Sidetiq::Actor::Handler id: 69937594759400 initialize
2016-01-22T12:52:38.498Z 9990 TID-osgvasil4 INFO: Booting Sidekiq 3.3.0 with redis options {:url=>"redis://:REDACTED@127.0.0.1:6379", :namespace=>"resque:gitlab"}
2016-01-22T12:52:40.445Z 9990 TID-osgvasil4 INFO: Running in ruby 2.1.7p400 (2015-08-18 revision 51632) [x86_64-linux]
2016-01-22T12:52:40.445Z 9990 TID-osgvasil4 INFO: See LICENSE and the LGPL-3.0 for licensing details.
2016-01-22T12:52:40.445Z 9990 TID-osgvasil4 INFO: Upgrade to Sidekiq Pro for more features and support: http://sidekiq.org/pro
2016-01-22T12:52:40.534Z 9990 TID-osgwye4lc ERROR: heartbeat: ERR invalid password
2016-01-22T12:52:40.534Z 9990 TID-osgvjnc5c ERROR: Error fetching message: ERR invalid password
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis/client.rb:113:in `call'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis/client.rb:95:in `block in connect'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis/client.rb:279:in `with_reconnect'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis/client.rb:93:in `connect'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis/client.rb:262:in `with_socket_timeout'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis/client.rb:194:in `call_with_timeout'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis.rb:1064:in `block in _bpop'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis.rb:37:in `block in synchronize'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /usr/local/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis.rb:37:in `synchronize'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis.rb:1061:in `_bpop'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis.rb:1106:in `brpop'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-namespace-1.5.1/lib/redis/namespace.rb:392:in `call_with_namespace'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-namespace-1.5.1/lib/redis/namespace.rb:289:in `method_missing'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/fetch.rb:102:in `block in retrieve_work'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/connection_pool-2.1.0/lib/connection_pool.rb:58:in `with'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq.rb:72:in `redis'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/fetch.rb:102:in `retrieve_work'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/fetch.rb:37:in `block in fetch'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/util.rb:15:in `watchdog'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/fetch.rb:33:in `fetch'
2016-01-22T12:52:40.535Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in `public_send'
2016-01-22T12:52:40.536Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in `dispatch'
2016-01-22T12:52:40.536Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:122:in `dispatch'
2016-01-22T12:52:40.536Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:60:in `block in invoke'
2016-01-22T12:52:40.536Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:71:in `block in task'
2016-01-22T12:52:40.536Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/actor.rb:357:in `block in task'
2016-01-22T12:52:40.536Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/tasks.rb:57:in `block in initialize'
2016-01-22T12:52:40.536Z 9990 TID-osgvjnc5c ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/tasks/task_fiber.rb:15:in `block in create'
2016-01-22T12:52:45.535Z 9990 TID-osgwye4lc ERROR: heartbeat: NOAUTH Authentication required.
2016-01-22T12:52:50.536Z 9990 TID-osgwye4lc ERROR: heartbeat: NOAUTH Authentication required.
2016-01-22T12:52:53.526Z 9990 TID-osgvjkvm4 ERROR: NOAUTH Authentication required.
2016-01-22T12:52:53.526Z 9990 TID-osgvjkvm4 ERROR: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis/client.rb:113:in `call'
2016-01-22T12:52:53.527Z 9990 TID-osgvjkvm4 WARN: {:context=>"scheduling poller thread died!"}
2016-01-22T12:52:53.527Z 9990 TID-osgvjkvm4 WARN: NOAUTH Authentication required.
2016-01-22T12:52:53.527Z 9990 TID-osgvjkvm4 WARN: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis/client.rb:113:in `call'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis.rb:1320:in `block in smembers'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis.rb:37:in `block in synchronize'
/usr/local/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis.rb:37:in `synchronize'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis.rb:1319:in `smembers'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-namespace-1.5.1/lib/redis/namespace.rb:392:in `call_with_namespace'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-namespace-1.5.1/lib/redis/namespace.rb:289:in `method_missing'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/api.rb:557:in `block in cleanup'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/connection_pool-2.1.0/lib/connection_pool.rb:58:in `with'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq.rb:72:in `redis'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/api.rb:556:in `cleanup'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/api.rb:549:in `initialize'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/scheduled.rb:79:in `new'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/scheduled.rb:79:in `poll_interval'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/scheduled.rb:58:in `block in poll'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/util.rb:15:in `watchdog'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/sidekiq-3.3.0/lib/sidekiq/scheduled.rb:23:in `poll'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in `public_send'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in `dispatch'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:122:in `dispatch'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:60:in `block in invoke'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:71:in `block in task'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/actor.rb:357:in `block in task'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/tasks.rb:57:in `block in initialize'
/home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/celluloid-0.16.0/lib/celluloid/tasks/task_fiber.rb:15:in `block in create'
2016-01-22T12:52:53.527Z 9990 TID-osgwye73c WARN: Sidekiq died due to the following error, cannot recover, process exiting
2016-01-22T12:52:53.527Z 9990 TID-osgwye73c WARN: NOAUTH Authentication required.
2016-01-22T12:52:53.527Z 9990 TID-osgwye73c WARN: /home/git/gitlab/vendor/bundle/ruby/2.1.0/gems/redis-3.2.1/lib/redis/client.rb:113:in `call'

我真的不知道如何解决它。谢谢!

最佳答案

您是否验证过 redis 密码是否正确，而且它看起来应该与您设置的不同。

configure redis auth on sidekiq

关于ruby-on-rails - Sidekiq 死于以下错误 :NOAUTH Authentication required，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/34947299/

文章推荐： postgresql - 在 PostgreSQL 之上实现区间分析

文章推荐： windows - 在windows批处理文件中获取环境变量

sidekiq - 如何在 Sidekiq 中重新启动失败的作业？
我想使用 rails 控制台重新启动所有失败的作业。有没有办法做到这一点？我可以使用以下方法获取工作列表: require 'sidekiq/api' Sidekiq::Queue.new("mail
sidekiq - Sidekiq 中队列的 Redis 键是什么？
我想使用 Datadog 来监控一些后台作业的队列长度。基本上我需要知道 Sidekiq 中代表队列的键的名称，以便我可以按照此处所述对其进行监控: https://docs.datadoghq.
ruby-on-rails - Rails + Sidekiq : Sidekiq. options[ :concurrency] returns 10 instead of 3, 这是我的 config/sidekiq.yml 文件中的值
我将 Sidekiq 与 Rails 一起使用，返回的并发值似乎是错误的。 Sidekiq.options[:concurrency] 返回 10 而不是 3，这是我的 config/sidekiq.
sidekiq - 如何使用 ActiveJob 设置 Sidekiq 的重试次数？
从Rails API中，我发现ActiveJob可以retry_job间隔: my_job_instance.enqueue my_job_instance.enqueue wait: 5.minut
ruby-on-rails - 当 sidekiq 停止时，sidekiq 生成的进程也会停止
我正在一个作业中进行一些处理，最终执行一个外部 shell 命令。该命令正在执行需要数小时才能完成的脚本。问题是在我使用 spawn 启动脚本后和 detach如果我使用 kill -15 信号关闭
ruby-on-rails - Rails + Sidekiq : Sidekiq running in wrong environment
我有一个使用 Capistrano 部署的 Rails 3 应用程序。我最近添加了 Sidekiq。它在我的开发中运行良好。我同时主持 staging和 preview在同一台服务器上，它的预览无法正
ruby-on-rails - Sidekiq::测试.假的!不伪造 Sidekiq::Queue
我有一个简单的工作线程正在访问其自己的队列的大小: 需要“sidekiq/api” class TestWorker include Sidekiq::Worker def perform(*
ruby - 我如何用密码保护我的/sidekiq 路由(即要求对 Sidekiq::Web 工具进行身份验证)？
我在我的 Rails 应用程序中使用 sidekiq。默认情况下，任何人都可以通过在 url 后附加“/sidekiq”来访问 Sidekiq。我只想用密码保护/验证 sidekiq 部分。我该怎么做
ruby-on-rails - 将 ActiveJob 与 Sidekiq 一起使用与单独使用 Sidekiq 相比的优势
我正在在线阅读一些教程，这些教程告诉我们将 ActiveJob 与 Sidekiq 结合使用。但我不知道我们为什么要这样做。我看到 Sidekiq 具有 ActiveJob 的所有功能。此外，在 S
ruby-on-rails - 测试 Sidekiq/ActiveJob - 工作在 ActiveJob 但不是 Sidekiq
我猴子修补了我的用户类(由设计支持)以像这样使用 ActiveJob: class User ActionMailer::DeliveryJob, :args=>["Devise::Mailer",
ruby-on-rails - 当现有的 sidekiq 作业正在处理特定资源时，阻止/重新排队处理其他 sidekiq 作业
我有 sidekiq 作业对多种类型的资源进行处理。但是，对于特定类型的资源，例如:资源 X，我需要确保在任何给定时间只有一个 sidekiq 作业可以处理该特定资源。例如，如果我有 3 个 sid
ruby-on-rails - 旧的 Sidekiq 作业永远重试。在 Sidekiq UI 上看不到
在过去的一年里，我对我的一项工作的流程进行了大量更改。诸如从相应模型上的 after_commit 而不是 after_create 触发它，以及清理逻辑和覆盖极端情况我在我的 Heroku Rub
ruby-on-rails - 带有 Sidekiq 适配器的 ActiveJob 是否对纯 Sidekiq worker 有性能问题？
我看到this在 Sidekiq 官方 wiki 中，ActiveJob 会慢得多。但它是在 2018 年 3 月根据此 issue 基于 Rails 4.2 和 Sidekiq 5.1.1 提到的
ruby-on-rails - 防止 Sidekiq 在测试中打印 "(...) INFO: Sidekiq client with redis options {}"
我使用 Rails 4 默认测试框架并编写了一些测试，这些测试也希望 Sidekiq 在“后台”做一些工作。但是当我运行 rake test 时，我的测试结果看起来像这样: .............
ruby-on-rails - Rails : Sidekiq is sometimes "down" - doesn't process requests. 我们可以通过 Sidekiq 发送的请求有限制吗？
我们几周前在我们的系统中添加了监控用户事件，如下所示: class ApplicationController < ActionController::Base before_filter :lo
ruby-on-rails - 对于多个 sidekiq 进程，sidekiq 和 postgres 的 activerecord 连接池大小是否合适？
我正在运行 7 个 sidekiq 进程(货币设置为 40)和一个乘客网络服务器，连接到 postgres 数据库。 Rails 池设置设置为 100，postgres max_connectio
ruby-on-rails - rails/Sidekiq : Help me understand the duplication in this example of `initializers/sidekiq.rb`
我第一次在 Rails 应用程序中使用 Sidekiq。这也是我第一次使用Redis。我见过几个示例(Here、here、here)，其中 initializers/sidekiq.rb 包含以下几
ruby-on-rails - 在 Heroku 上启动 sidekiq 时出错，缺少 sidekiq.log 文件崩溃
我刚开始使用 sidekiq 和 redis，我试图让 sidekiq 在 Heroku 上运行，但每次我部署 Rails 4 应用程序时它似乎都会崩溃。我在 Papertrail 中收到此错误: M
ruby-on-rails - 如何为我的 rails 应用程序扩展 sidekiq 性能。需要每秒运行 100 个 sidekiq 作业
我有一个要求，我应该能够每秒运行 100 个 sidekiq 作业。我将服务器容量增加到 8 个 CPU 并创建了 4 个 sidekiq 进程，但它仍然每分钟服务 50 个作业。我不确定我在哪里
ruby-on-rails - 如何配置 procfile，sidekiq.yml 以便不同的 sidekiq 队列在 heroku 中的不同 dynos 上运行？
我在 Sidekiq 中有两种队列:“default/low”——满足网络请求和“background_queue”——运行后台进程，比如获取推文。我想在不同的 dyno 上运行“background

可可西里

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

ruby-on-rails - Sidekiq 死于以下错误 :NOAUTH Authentication required