Excepción de trabajo: DistributedMutex::MaximumAttemptsExceeded

Hola,

Seguimos viendo estos avisos de error en los registros de nuestro foro. ¿Deberíamos preocuparnos o ajustar alguna configuración?

backtrace
/var/www/discourse/lib/distributed_mutex.rb:113:in `get_lock'

/var/www/discourse/lib/distributed_mutex.rb:62:in `block in synchronize'

/var/www/discourse/lib/distributed_mutex.rb:61:in `synchronize'

/var/www/discourse/lib/distributed_mutex.rb:61:in `synchronize'

/var/www/discourse/lib/distributed_mutex.rb:45:in `synchronize'

/var/www/discourse/app/jobs/regular/notify_reviewable.rb:25:in `execute'

/var/www/discourse/app/jobs/base.rb:249:in `block (2 levels) in perform'

rails_multisite-4.0.1/lib/rails_multisite/connection_management.rb:80:in `with_connection'
/var/www/discourse/app/jobs/base.rb:236:in `block in perform'

/var/www/discourse/app/jobs/base.rb:232:in `each'

/var/www/discourse/app/jobs/base.rb:232:in `perform'

sidekiq-6.5.8/lib/sidekiq/processor.rb:202:in `execute_job'

sidekiq-6.5.8/lib/sidekiq/processor.rb:170:in `block (2 levels) in process'

sidekiq-6.5.8/lib/sidekiq/middleware/chain.rb:177:in `block in invoke'

/var/www/discourse/lib/sidekiq/pausable.rb:134:in `call'

sidekiq-6.5.8/lib/sidekiq/middleware/chain.rb:179:in `block in invoke'

sidekiq-6.5.8/lib/sidekiq/middleware/chain.rb:182:in `invoke'

sidekiq-6.5.8/lib/sidekiq/processor.rb:169:in `block in process'

sidekiq-6.5.8/lib/sidekiq/processor.rb:136:in `block (6 levels) in dispatch'

sidekiq-6.5.8/lib/sidekiq/job_retry.rb:113:in `local'

sidekiq-6.5.8/lib/sidekiq/processor.rb:135:in `block (5 levels) in dispatch'

sidekiq-6.5.8/lib/sidekiq.rb:44:in `block in <module:Sidekiq>'

sidekiq-6.5.8/lib/sidekiq/processor.rb:131:in `block (4 levels) in dispatch'

sidekiq-6.5.8/lib/sidekiq/processor.rb:263:in `stats'

sidekiq-6.5.8/lib/sidekiq/processor.rb:126:in `block (3 levels) in dispatch'

sidekiq-6.5.8/lib/sidekiq/job_logger.rb:13:in `call'

sidekiq-6.5.8/lib/sidekiq/processor.rb:125:in `block (2 levels) in dispatch'

sidekiq-6.5.8/lib/sidekiq/job_retry.rb:80:in `global'

sidekiq-6.5.8/lib/sidekiq/processor.rb:124:in `block in dispatch'

sidekiq-6.5.8/lib/sidekiq/job_logger.rb:39:in `prepare'

sidekiq-6.5.8/lib/sidekiq/processor.rb:123:in `dispatch'

sidekiq-6.5.8/lib/sidekiq/processor.rb:168:in `process'

sidekiq-6.5.8/lib/sidekiq/processor.rb:78:in `process_one'

sidekiq-6.5.8/lib/sidekiq/processor.rb:68:in `run'

sidekiq-6.5.8/lib/sidekiq/component.rb:8:in `watchdog'

sidekiq-6.5.8/lib/sidekiq/component.rb:17:in `block in safe_thread'

[details=“env”]
|hostname||
|—|—|\n|process_id|189676|\n|application_version|2f8ad17aed81bbfa2fd20b6cc9210be92779bd74|\n|current_db|default|\n|current_hostname||\n|job|Jobs::NotifyReviewable|\n|problem_db|default|\n|time|4:02 pm|\n|||\n|opts||\n|reviewable_id|8980|\n|current_site_id|default|\n[/details]

¿Sigues viendo esto @kinetiksoft? ¿Es esa revisión específica la que está teniendo un problema? (/review/8980)

1 me gusta

No veo este error específico ahora, pero tenemos una excepción de trabajo diferente con una cantidad inapropiada de repeticiones que indica:

Excepción de trabajo: constante no inicializada Jobs::ClassifyChatMessage::ChatMessage

Backtrace

/var/www/discourse/plugins/disorder/app/jobs/regular/classify_chat_message.rb:11:in execute' /var/www/discourse/app/jobs/base.rb:249:in block (2 levels) in perform’
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rails_multisite-4.0.1/lib/rails_multisite/connection_management.rb:80:in with_connection' /var/www/discourse/app/jobs/base.rb:236:in block in perform’
/var/www/discourse/app/jobs/base.rb:232:in each' /var/www/discourse/app/jobs/base.rb:232:in perform’
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.8/lib/sidekiq/processor.rb:202:in execute_job' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.8/lib/sidekiq/processor.rb:170:in block (2 levels) in process’
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/sidekiq-6.5.8/lib/sidekiq/middleware/chain.rb:177:in block in invoke' /var/www/discourse/lib/sidekiq/pausable.rb:134:in call’

Detalles adicionales
Columna 1 Columna 2
hostname {redacted}
process_id 1657082
application_version c1c017f4333ad1aaec509c39bdc313420ea4e5a7
current_db default
current_hostname {redacted}
job Jobs::ClassifyChatMessage
problem_db default
time 1:06 pm
opts
chat_message_id 2444
current_site_id default


¿Puedo robar amablemente tu atención mientras estás aquí en relación con otro error que se describe aquí:
https://meta.discourse.org/t/discourse-gifs/158738/235?u=kinetiksoft

Por si acaso hay suerte en llamar la atención de alguien dentro de los chats internos del equipo de Discourse…

1 me gusta

Al menos esa es una buena noticia. :slight_smile: :partying_face:

No estoy seguro de este segundo error. ¿Parece que el módulo de clasificación de IA tiene un problema con un mensaje de chat? Es un poco vago, pero ¿eso ayuda en algo?

Te vi publicar un seguimiento en el tema de GIFS Discourse Gifs - #243 by Muhammed_EKİCİ Espero que eso le preste algo de atención. :crossed_fingers:

1 me gusta