# 502 Fehler / Unicorn Timeout auf der Rewind-Seite für sehr aktive Benutzer

**URL:** https://meta.discourse.org/t/502-error-unicorn-timeout-on-rewind-page-for-highly-active-users/392494
**Category:** Bug
**Tags:** rewind
**Created:** [1. Januar 2026 um 13:34 UTC](https://meta.discourse.org/t/502-error-unicorn-timeout-on-rewind-page-for-highly-active-users/392494 "2026-01-01T13:34:11Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![Don](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/don/32/228726_2.png) [@Don](https://meta.discourse.org/u/Don)
#### Post date: [1. Januar 2026 um 13:34 UTC](https://meta.discourse.org/t/502-error-unicorn-timeout-on-rewind-page-for-highly-active-users/392494/1 "2026-01-01T13:34:11Z")

</div>

Hallo 👋

Wir haben ein Problem mit dem Discourse Rewind Plugin. Bei einigen unserer aktivsten Benutzer lädt die Rewind-Seite nicht und gibt einen 502-Fehler zurück.

- Das Problem scheint ein Timeout während des Datenaggregationsprozesses zu sein.
- Es tritt konsistent bei Benutzern mit hohem Aktivitätsniveau auf, funktioniert aber bei durchschnittlichen Benutzern einwandfrei.
- Die Protokolle zeigen, dass der Unicorn-Worker ein `USR2`-Signal empfängt, weil er das Timeout-Limit überschreitet, während er eine Datenbankabfrage ausführt.

Fehler in der Konsole:

 ![Screenshot 2026-01-01 at 14.28.11](https://global.discourse-cdn.com/meta/original/4X/1/6/9/169012184e12aa54ed693fde2746b36d68ce21b8.png)

Warnung in den Protokollen:

````plaintext
Nachricht

Unicorn worker received USR2 signal indicating it is about to timeout, dumping backtrace for main thread
config/unicorn.conf.rb:204:in `backtrace'
config/unicorn.conf.rb:204:in `block (2 levels) in reload'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/db/pg/alias_method.rb:112:in `exec'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/db/pg/alias_method.rb:112:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.4/lib/active_record/connection_adapters/postgresql/database_statements.rb:167:in `perform_query'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.4/lib/active_record/connection_adapters/abstract/database_statements.rb:556:in `block (2 levels) in raw_execute'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.4/lib/active_record/connection_adapters/abstract_adapter.rb:1017:in `block in with_raw_connection'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.4/lib/active_support/concurrency/null_lock.rb:9:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.4/lib/active_record/connection_adapters/abstract_adapter.rb:986:in `with_raw_connection'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.4/lib/active_record/connection_adapters/abstract/database_statements.rb:555:in `block in raw_execute'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.4/lib/active_support/notifications/instrumenter.rb:58:in `instrument'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.4/lib/active_record/connection_adapters/abstract_adapter.rb:1137:in `log'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.4/lib/active_record/connection_adapters/abstract/database_statements.rb:554:in `raw_execute'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.4/lib/active_record/connection_adapters/abstract/database_statements.rb:591:in `...

Backtrace

/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.4/lib/active_support/broadcast_logger.rb:218:in `block in dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.4/lib/active_support/broadcast_logger.rb:217:in `map'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.4/lib/active_support/broadcast_logger.rb:217:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.4/lib/active_support/broadcast_logger.rb:129:in `warn'
/var/www/discourse/lib/signal_trap_logger.rb:40:in `public_send'
/var/www/discourse/lib/signal_trap_logger.rb:40:in `block (2 levels) in ensure_logging_thread_running'
```internal:kernel`:187:in `loop'
/var/www/discourse/lib/signal_trap_logger.rb:37:in `block in ensure_logging_thread_running'

````

Danke

---

_[View the full topic](https://meta.discourse.org/t/502-error-unicorn-timeout-on-rewind-page-for-highly-active-users/392494)._