patronit
(Oliver)
20 Octubre, 2025 09:20
1
Hola.
Desde hace dos o tres semanas, nuestra instancia de Discourse no actualiza ninguna notificación como leída (nuevo tema/mensaje/chat).
Y supongo que ningún usuario conectado recibe notificaciones de nuevos mensajes/temas/chats mientras está conectado.
La versión instalada es: 3.6.0.beta2-latest (1354173224) en Ubuntu Server 22.04.5.
No parece ser un problema del navegador. El problema ocurre en Firefox y Chrome.
¿Algún consejo o pista?
Gracias por tu ayuda.
¿Hay algún error en /logs? ¿Sucede esto también en modo seguro? Gracias.
patronit
(Oliver)
20 Octubre, 2025 09:35
3
Seguridad - Protocolos y Controles - Registros de errores no es un error.
En modo seguro, recibo un nuevo mensaje solo si recargo la página.
patronit
(Oliver)
20 Octubre, 2025 09:36
4
… y si leo el nuevo mensaje, el icono de notificación de mensajes no leídos no desaparece.
1 me gusta
patronit
(Oliver)
20 Octubre, 2025 09:45
5
Ok. There is a warning with the date of the last update (October 18th):
Message
Sidekiq heartbeat test failed for 7409, restarting
Backtrace
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.3/lib/active_support/broadcast_logger.rb:218:in block in dispatch' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.3/lib/active_support/broadcast_logger.rb:217:in map’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.3/lib/active_support/broadcast_logger.rb:217:in dispatch' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.3/lib/active_support/broadcast_logger.rb:129:in warn’
/var/www/discourse/lib/demon/sidekiq.rb:39:in block in heartbeat_check' /var/www/discourse/lib/demon/sidekiq.rb:31:in each’
/var/www/discourse/lib/demon/sidekiq.rb:31:in heartbeat_check' config/unicorn.conf.rb:131:in block (2 levels) in reload’
One error October 3rd:
Message (4 copies reported)
Job exception: Unsupported command argument type: TrueClass
Backtrace
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-client-0.25.3/lib/redis_client/command_builder.rb:37:in block in generate' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-client-0.25.3/lib/redis_client/command_builder.rb:28:in map!’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-client-0.25.3/lib/redis_client/command_builder.rb:28:in generate' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-client-0.25.3/lib/redis_client.rb:313:in call_v’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-5.4.0/lib/redis/client.rb:90:in call_v' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/mini_profiler/profiling_methods.rb:90:in block in profile_method’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-5.4.0/lib/redis.rb:152:in block in send_command' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-5.4.0/lib/redis.rb:151:in synchronize’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-5.4.0/lib/redis.rb:151:in send_command' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-5.4.0/lib/redis/commands/hashes.rb:51:in hmset’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-5.4.0/lib/redis/commands/hashes.rb:66:in mapped_hmset' /var/www/discourse/lib/discourse_redis.rb:144:in public_send’
/var/www/discourse/lib/discourse_redis.rb:144:in block (3 levels) in <class:DiscourseRedis>' /var/www/discourse/lib/discourse_redis.rb:29:in ignore_readonly’
/var/www/discourse/lib/discourse_redis.rb:144:in block (2 levels) in <class:DiscourseRedis>' /var/www/discourse/lib/discourse_updates.rb:116:in block in missing_versions=’
/var/www/discourse/lib/discourse_updates.rb:114:in each' /var/www/discourse/lib/discourse_updates.rb:114:in missing_versions=’
/var/www/discourse/app/jobs/scheduled/call_discourse_hub.rb:19:in execute' /var/www/discourse/app/jobs/base.rb:318:in block (2 levels) in perform’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rails_multisite-7.0.0/lib/rails_multisite/connection_management/null_instance.rb:49:in with_connection' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rails_multisite-7.0.0/lib/rails_multisite/connection_management.rb:17:in with_connection’
/var/www/discourse/app/jobs/base.rb:305:in block in perform' /var/www/discourse/app/jobs/base.rb:301:in each’
/var/www/discourse/app/jobs/base.rb:301:in perform' /var/www/discourse/app/jobs/base.rb:381:in perform’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_scheduler-0.18.0/lib/mini_scheduler/manager.rb:137:in process_queue' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_scheduler-0.18.0/lib/mini_scheduler/manager.rb:77:in worker_loop’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_scheduler-0.18.0/lib/mini_scheduler/manager.rb:63:in `block (2 levels) in ensure_worker_threads’
And one error in September 16th:
Message (5 copies reported)
Job exception: execution expired
Backtrace
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-smtp-0.5.1/lib/net/smtp.rb:663:in initialize' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-smtp-0.5.1/lib/net/smtp.rb:663:in open’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-smtp-0.5.1/lib/net/smtp.rb:663:in tcp_socket' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-smtp-0.5.1/lib/net/smtp.rb:672:in block in do_start’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/timeout-0.4.3/lib/timeout.rb:185:in block in timeout' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/timeout-0.4.3/lib/timeout.rb:192:in timeout’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-smtp-0.5.1/lib/net/smtp.rb:671:in do_start' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-smtp-0.5.1/lib/net/smtp.rb:642:in start’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mail-2.8.1/lib/mail/network/delivery_methods/smtp.rb:109:in start_smtp_session' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mail-2.8.1/lib/mail/network/delivery_methods/smtp.rb:100:in deliver!’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mail-2.8.1/lib/mail/message.rb:269:in deliver!' /usr/local/lib/ruby/3.3.0/delegate.rb:87:in method_missing’
/var/www/discourse/lib/email/sender.rb:296:in send' /var/www/discourse/app/jobs/regular/user_email.rb:79:in send_user_email’
/var/www/discourse/app/jobs/regular/user_email.rb:39:in execute' /var/www/discourse/app/jobs/base.rb:318:in block (2 levels) in perform’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rails_multisite-7.0.0/lib/rails_multisite/connection_management/null_instance.rb:49:in with_connection' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rails_multisite-7.0.0/lib/rails_multisite/connection_management.rb:17:in with_connection’
/var/www/discourse/app/jobs/base.rb:305:in block in perform' /var/www/discourse/app/jobs/base.rb:301:in each’
/var/www/discourse/app/jobs/base.rb:301:in perform' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:220:in execute_job’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:185:in block (4 levels) in process' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:180:in traverse’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in block in traverse' /var/www/discourse/lib/sidekiq/discourse_event.rb:6:in call’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in traverse' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in block in traverse’
/var/www/discourse/lib/sidekiq/pausable.rb:131:in call' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in traverse’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in block in traverse' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job/interrupt_handler.rb:9:in call’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in traverse' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in block in traverse’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/metrics/tracking.rb:26:in track' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/metrics/tracking.rb:134:in call’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in traverse' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:173:in invoke’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:184:in block (3 levels) in process' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:145:in block (6 levels) in dispatch’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_retry.rb:118:in local' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:144:in block (5 levels) in dispatch’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/config.rb:39:in block in <class:Config>' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:139:in block (4 levels) in dispatch’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:281:in stats' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:134:in block (3 levels) in dispatch’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_logger.rb:15:in call' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:133:in block (2 levels) in dispatch’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_retry.rb:85:in global' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:132:in block in dispatch’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/job_logger.rb:40:in prepare' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:131:in dispatch’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:183:in block (2 levels) in process' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:182:in handle_interrupt’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:182:in block in process' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:181:in handle_interrupt’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:181:in process' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:86:in process_one’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/processor.rb:76:in run' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/component.rb:10:in watchdog’
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/sidekiq-7.3.9/lib/sidekiq/component.rb:19:in `block in safe_thread’
sam
(Sam Saffron)
22 Octubre, 2025 06:06
6
Lo que sea que esté sucediendo aquí, es poco probable que sean esos problemas.
¿Tienes algún plugin personalizado instalado?
1 me gusta
@sam Intentaron el modo seguro, pero no parece estar funcionando bien.
@patronit ¿pudiste resolver esto?
patronit
(Oliver)
31 Octubre, 2025 10:14
9
No activamos plugins personalizados, ni siquiera los que ahora se incluyen:
Como tema, Minima es seleccionable.
patronit
(Oliver)
31 Octubre, 2025 10:25
10
Hoy, 31 de octubre, usamos la versión 3.6.0.beta2-latest (47559c86f5 ) en modo seguro:
Cuando escribo un mensaje (Nachricht), el nuevo mensaje se muestra en el menú “Benachrichtigungen und Konto” pero sin la marca y el número de “nuevo”.
En modo normal:
Solo F5 ayuda.
Mañana es el día de la actualización…
¿Se ha solucionado este problema con la última actualización? Parece grave y es algo que no había oído antes. ¿Está seguro de que no ha realizado ninguna personalización?
Quizás intente usar el tema foundation u horizon, pero no estoy seguro de cómo eso podría causar el problema.
¿O tal vez intente con un navegador web o dispositivo diferente? ¿Todos los usuarios de su sitio informan del mismo problema? Quizás tenga una extensión del navegador que esté interfiriendo con Discourse.
patronit
(Oliver)
13 Noviembre, 2025 10:46
12
Gracias por tu compromiso.
Hoy estoy en 3.6.0.beta3-latest (bd135646c3).
Cambié a “Foundation” y escribo mensajes y chats de mi usuario normal a administrador y viceversa.
Mi cliente es Xubuntu 22.04. En Chrome (141.0.7390.76) y Firefox (145.0) no hay cambios. No hay notificaciones mientras estoy conectado y los “nuevos” iconos no desaparecen si se leen. Solo al recargar.
Intentaré más tarde en Ubuntu 24.04 y Win11.
patronit:
ubuntu server 22.04.5.
Probablemente no esté relacionado, pero es posible que desees actualizar a 24.04.
¿Podría ser un problema de red?
¿Se ha resuelto/desaparecido este problema para @patronit ? Es un acertijo.
Si todavía tienes el problema, ¿puedes asegurarte de que estás probando con dos cuentas de usuario completamente separadas usando dos navegadores web o dispositivos separados? ¿Funciona en modo seguro?