You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
It didn't even get as far as resolve_state_groups, seemingly. Mjark wonders if this is associated with exhausting the DB conn pool and causing it to somehow loop on loading events?
Jan 06 16:15:28 ralith.com synapse[2085]: synapse.storage.events: [PUT-67272] Loaded 1 events (1 rows)
Jan 06 16:15:28 ralith.com synapse[2085]: synapse.state: [] calling resolve_state_groups from get_current_user_in_room
Jan 06 16:15:29 ralith.com synapse[2085]: synapse.storage.events: [PUT-67584] Loaded 1 events (1 rows)
Jan 06 16:15:29 ralith.com synapse[2085]: synapse.state: [] calling resolve_state_groups from get_current_user_in_room
Jan 06 16:15:30 ralith.com synapse[2085]: synapse.storage.events: [PUT-67625] Loaded 1 events (1 rows)
Jan 06 16:15:30 ralith.com synapse[2085]: synapse.state: [] calling resolve_state_groups from get_current_user_in_room
Jan 06 16:18:02 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6306 events (6306 rows)
Jan 06 16:18:10 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6284 events (6284 rows)
Jan 06 16:18:18 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6303 events (6303 rows)
Jan 06 16:18:26 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6347 events (6347 rows)
Jan 06 16:18:36 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6310 events (6310 rows)
Jan 06 16:18:45 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6304 events (6304 rows)
Jan 06 16:18:53 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6300 events (6300 rows)
Jan 06 16:19:01 ralith.com synapse[2085]: synapse.storage.events: [PUT-67653] Loaded 1 events (0 rows)
Jan 06 16:19:01 ralith.com synapse[2085]: synapse.storage.events: [PUT-67656] Loaded 1 events (0 rows)
Jan 06 16:19:02 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6303 events (6302 rows)
Jan 06 16:19:10 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6273 events (6273 rows)
Jan 06 16:19:19 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6289 events (6288 rows)
Jan 06 16:19:27 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6282 events (6282 rows)
Jan 06 16:19:35 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6274 events (6274 rows)
Jan 06 16:19:43 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 5726 events (5726 rows)
Jan 06 16:19:51 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6281 events (6281 rows)
Jan 06 16:19:58 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6069 events (6067 rows)
Jan 06 16:20:06 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6227 events (6225 rows)
Jan 06 16:20:14 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6278 events (6278 rows)
Jan 06 16:20:22 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6306 events (6306 rows)
Jan 06 16:20:30 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6275 events (6275 rows)
Jan 06 16:20:38 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6303 events (6303 rows)
Jan 06 16:20:46 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6308 events (6308 rows)
Jan 06 16:20:54 ralith.com synapse[2085]: synapse.storage.events: [] Loaded 6279 events (6279 rows)
Jan 06 16:22:08 ralith.com systemd[1]: matrix-synapse.service: Main process exited, code=killed, status=9/KILL
Jan 06 16:22:08 ralith.com systemd[1]: matrix-synapse.service: Unit entered failed state.
Jan 06 16:22:08 ralith.com systemd[1]: matrix-synapse.service: Failed with result 'signal'.
The text was updated successfully, but these errors were encountered:
ara4n
changed the title
Ralith's HS exploded repeatedly loading events in get_current_user_in_room
Ralith's HS OOMed after repeatedly loading events in get_current_user_in_room
Jan 6, 2017
It didn't even get as far as resolve_state_groups, seemingly. Mjark wonders if this is associated with exhausting the DB conn pool and causing it to somehow loop on loading events?
The text was updated successfully, but these errors were encountered: