| 17 Oct 2024 |
 Andreas Rammhold |
Oct 17 14:34:43 matrix synapse-client_worker2[1163]: synapse.http.server: [PUT-5896459] <XForwardedForRequest at 0x7ff39a3da050 method='PUT' uri='/_matrix/client/v3/rooms/!cacbMwUwsLZ6GKac:nichi.co/event/$RKy3adIpkxQtqI0TwSFLMMOg8Oct 17 14:34:43 matrix synapse-client_worker2[1163]: synapse.http.server: [PUT-5896459] <XForwardedForRequest at 0x7ff39a3da050 method='PUT' uri='/_matrix/client/v3/rooms/!cacbMwUwsLZ6GKac:nichi.co/event/$RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34' clientproto='HTTP/1.1' site='7501'> SynapseError: 405 - Unrecognized request
-mYhYARrXWVfrajz34' clientproto='HTTP/1.1' site='7501'> SynapseError: 405 - Unrecognized request
| 14:45:49 |
 Yorusaka Miyabi | Redacted or Malformed Event | 14:46:20 |
| Yorusaka Miyabi | In reply to @andir:nixos.dev
Oct 17 14:34:43 matrix synapse-client_worker2[1163]: synapse.http.server: [PUT-5896459] <XForwardedForRequest at 0x7ff39a3da050 method='PUT' uri='/_matrix/client/v3/rooms/!cacbMwUwsLZ6GKac:nichi.co/event/$RKy3adIpkxQtqI0TwSFLMMOg8Oct 17 14:34:43 matrix synapse-client_worker2[1163]: synapse.http.server: [PUT-5896459] <XForwardedForRequest at 0x7ff39a3da050 method='PUT' uri='/_matrix/client/v3/rooms/!cacbMwUwsLZ6GKac:nichi.co/event/$RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34' clientproto='HTTP/1.1' site='7501'> SynapseError: 405 - Unrecognized request
-mYhYARrXWVfrajz34' clientproto='HTTP/1.1' site='7501'> SynapseError: 405 - Unrecognized request
* | 14:46:23 |
| Yorusaka Miyabi | In reply to @andir:nixos.dev
Oct 17 14:34:43 matrix synapse-client_worker2[1163]: synapse.http.server: [PUT-5896459] <XForwardedForRequest at 0x7ff39a3da050 method='PUT' uri='/_matrix/client/v3/rooms/!cacbMwUwsLZ6GKac:nichi.co/event/$RKy3adIpkxQtqI0TwSFLMMOg8Oct 17 14:34:43 matrix synapse-client_worker2[1163]: synapse.http.server: [PUT-5896459] <XForwardedForRequest at 0x7ff39a3da050 method='PUT' uri='/_matrix/client/v3/rooms/!cacbMwUwsLZ6GKac:nichi.co/event/$RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34' clientproto='HTTP/1.1' site='7501'> SynapseError: 405 - Unrecognized request
-mYhYARrXWVfrajz34' clientproto='HTTP/1.1' site='7501'> SynapseError: 405 - Unrecognized request
No not this, I managed to made the HTTP method wrong | 14:46:31 |
| Andreas Rammhold |
Oct 17 14:37:00 matrix synapse-client_worker2[1163]: synapse.http.server: [GET-5896991] <XForwardedForRequest at 0x7ff3cf4a33d0 method='GET' uri='/_matrix/client/v3/rooms/!cacbMwUwsLZ6GKac%3Anichi.co/event/%24RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34' clientproto='HTTP/1.1' site='7501'> SynapseError: 404 - Event not found.
this?
| 14:46:52 |
| Yorusaka Miyabi | In reply to @andir:nixos.dev
Oct 17 14:37:00 matrix synapse-client_worker2[1163]: synapse.http.server: [GET-5896991] <XForwardedForRequest at 0x7ff3cf4a33d0 method='GET' uri='/_matrix/client/v3/rooms/!cacbMwUwsLZ6GKac%3Anichi.co/event/%24RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34' clientproto='HTTP/1.1' site='7501'> SynapseError: 404 - Event not found.
this?
Yes, like this | 14:47:26 |
| Yorusaka Miyabi | It also affected the public log on https://logs.nixos.dev/room/!cacbMwUwsLZ6GKac:nichi.co/ where lots events are missing from sync too | 14:49:58 |
 andi- | Oct 17 13:14:23 matrix synapse-federation_sender2[1165]: synapse.federation.federation_server: [_process_incoming_pdus_in_room_inner-131398] handling received PDU in room !cacbMwUwsLZ6GKac:nichi.co: <FrozenEventV3 event_id=$RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34, type=m.room.message, state_key=None, outlier=False>
Oct 17 13:14:23 matrix synapse-federation_sender2[1165]: synapse.handlers.federation_event: [_process_incoming_pdus_in_room_inner-131398-$RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34] While checking auth of <FrozenEventV3 event_id=$RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34, type=m.room.message, state_key=None, outlier=False> against auth_events: 403: During auth for event $RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34: found rejected event $gptoDaHlOKSxtvJP713Mc0ywTnQDvcDy400d0jCAtfo in the state
Oct 17 13:14:23 matrix synapse-federation_sender2[1165]: synapse.http.client: [_process_incoming_pdus_in_room_inner-131398-$RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34] Received response to POST synapse-replication://master/_synapse/replication/fed_send_events/uLADjbYQlB: 200
Oct 17 13:14:23 matrix synapse-federation_sender2[1165]: synapse.replication.tcp.client: [_process_incoming_pdus_in_room_inner-131398-$RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34] Waiting for repl stream 'events' to reach 21684842 (master); currently at: 21684841
Oct 17 13:14:23 matrix synapse-federation_sender2[1165]: synapse.replication.tcp.client: [_process_incoming_pdus_in_room_inner-131398-$RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34] Finished waiting for repl stream 'events' to reach 21684842 (master)
Oct 17 13:42:31 matrix synapse-client_worker2[1163]: synapse.http.server: [GET-5884919] <XForwardedForRequest at 0x7ff3d7824050 method='GET' uri='/_matrix/client/v3/rooms/!cacbMwUwsLZ6GKac:nichi.co/event/$RKy3adIpkxQtqI0TwSFLMMOg8-mYhYARrXWVfrajz34' clientproto='HTTP/1.1' site='7501'> SynapseError: 404 - Event not found.
| 14:55:37 |
| andi- | restarted synapse (and the workers) to purge any potential wrong in-memory caches that might exist | 14:57:33 |
| andi- | In reply to @shadowrz:nixos.dev
It also affected the public log on https://logs.nixos.dev/room/!cacbMwUwsLZ6GKac:nichi.co/ where lots events are missing from sync too What timeframe? For me that looked fine | 14:57:43 |
| Yorusaka Miyabi | In reply to @andi:kack.it
What timeframe? For me that looked fine At least for a week but even earlier, I have confirmed that there should be even more messages, it's actually a room bridged with Telegram, and vast majority messaged are bridged to Matrix from Telegram via a bridge on the nichi.co homeserver | 14:59:26 |
| Yorusaka Miyabi | In reply to @andi:kack.it
What timeframe? For me that looked fine * | 14:59:36 |
| Yorusaka Miyabi | In reply to @andi:kack.it
What timeframe? For me that looked fine * | 14:59:50 |
| Yorusaka Miyabi | 
Download image.png | 15:00:30 |
| andi- | Mhm, we seem to be getting 403's if I read the message correct. At least that is what I see for that above event. It was first rejected at 12:55:43 and then again at 13:14:23 with a 403 | 15:01:10 |
| Yorusaka Miyabi | For example this part, there should be replied events but strangely it can't be found on nixos.dev and thus Cinny failed to render the replied events. | 15:01:11 |
| andi- | Could this be pruning on the sending server? A message that has been old and pruned from there but still referenced and available on other servers? | 15:02:13 |
| 25 Oct 2024 |
| Yorusaka Miyabi | In reply to @andi:kack.it
Could this be pruning on the sending server? A message that has been old and pruned from there but still referenced and available on other servers? They said it's some sort of Synapse bug, and upgrading room (actually rebuilding room) might fix this | 02:08:02 |
| Yorusaka Miyabi | In reply to @shadowrz:nixos.dev
They said it's some sort of Synapse bug, and upgrading room (actually rebuilding room) might fix this Or you can just clean the room state | 02:09:58 |
| andi- | Nothing is “just” with synapse :) | 04:42:29 |
| Yorusaka Miyabi | In reply to @shadowrz:nixos.dev
Or you can just clean the room state https://element-hq.github.io/synapse/latest/admin_api/rooms.html#version-2-new-version
You can use this JSON Body:
{ "message": "Cleaning room.", "purge": true } | 05:32:43 |
| Yorusaka Miyabi | In reply to @shadowrz:nixos.dev
https://element-hq.github.io/synapse/latest/admin_api/rooms.html#version-2-new-version
You can use this JSON Body:
{ "message": "Cleaning room.", "purge": true } Room ID is !cacbMwUwsLZ6GKac:nichi.co | 05:34:40 |
| 28 Oct 2024 |
|  Justinas Stankevičius joined the room. | 09:28:24 |
| 31 Oct 2024 |
 Enzime | any idea what's up with this error? MatrixError: [502] Failed to make_join via any server (https://matrix.nixos.dev/_matrix/client/v3/join/!HpHRwRmgRTMyvMwVSE%3Amatrix.lrn.fm) | 16:52:31 |
| andi- | I think that’s someone spamming people. I’ve had multiple invites to chat with someone in there. | 17:05:23 |
| 15 Nov 2024 |
| Yorusaka Miyabi changed their display name from 夜坂雅 to Yorusaka Miyabi | Emotional Bugged. | 04:23:08 |
| Yorusaka Miyabi changed their display name from Yorusaka Miyabi | Emotional Bugged to Yorusaka Miyabi | Emotional Bugged | No DM. | 04:24:18 |
| 10 Dec 2024 |
| Yorusaka Miyabi changed their display name from Yorusaka Miyabi | Emotional Bugged | No DM to Yorusaka Miyabi. | 06:22:08 |
| 27 Feb 2025 |
| Enzime | 
Download Screenshot 2025-02-27 at 11.46.41 pm.png | 16:46:47 |
| Enzime | I'm trying to log into Element X | 16:46:53 |
