acidjunk / acidjunk/autoleaf-tickets
WFO worker crasht
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 0
- Forks
- 0
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
_Originally: https://github.com/virge-io/pricelist-frontend/issues/407_
N.a.v. Appje van Daan:
----
Draait weer: ik heb een ticket op het bord gezet. Volgende week gaat de WFO naar 4.8.0, en dan zet ik Sentry aan.
Het probleem is een beetje dat de worker niets doet, wanneer er niets is: ik denk dat ik iets van een heartbeat moet gaan implementeren: zodat we dat kunnen monitoren.
Dit is wat je ziet in de worker:
```
System information as of Wed Mar 4 18:20:17 UTC 2026
System load: 0.03
Usage of /: 32.2% of 95.82GB
Memory usage: 25%
Swap usage: 0%
, in asynloop
next(loop)
File "/usr/local/lib/python3.11/site-packages/kombu/asynchronous/hub.py", line 373, in create_loop
cb(*cbargs)
File "/usr/local/lib/python3.11/site-packages/kombu/transport/redis.py", line 1359, in on_readable
self.cycle.on_readable(fileno)
File "/usr/local/lib/python3.11/site-packages/kombu/transport/redis.py", line 576, in on_readable
chan.handlers[type]()
File "/usr/local/lib/python3.11/site-packages/kombu/transport/redis.py", line 974, in _brpop_read
dest__item = self.client.parse_response(self.client.connection,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/redis/client.py", line 635, in parse_response
response = connection.read_response()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/redis/connection.py", line 637, in read_response
raise response
redis.exceptions.ResponseError: caller gone
```
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
No project file or test is named; begin by reviewing the worker entry point and its Kombu/Redis configuration, then compare the original issue with the reported current state. Done should mean the idle-worker failure is reproducible or ruled out and the required heartbeat or monitoring change is specified, since the report says the worker is currently running.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- python, redis
- Bereich
- backend
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 35/100