Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

newly-configured AS didn't receive new events #11629

Open
matrixbot opened this issue Dec 19, 2023 · 0 comments
Open

newly-configured AS didn't receive new events #11629

matrixbot opened this issue Dec 19, 2023 · 0 comments

Comments

@matrixbot
Copy link
Collaborator

matrixbot commented Dec 19, 2023

This issue has been migrated from #11629.


Description

Resurgence of matrix-org/synapse#1834 on latest Synapse

Steps to reproduce

  • Register new AS (mautrix-signal in my case)
  • Observe that the AS tokens work, the AS sets up its users with avatars etc
  • Try to invite the bridgebot user
  • Observe that it does not follow the join to the room
  • Check AS logs to see that it didn't see any transactions come in
  • Check Synapse logs to see that it doesn't have any AS/transactions errors

Context

application_services_state only contained a single row, an entry from a very old IRC bridge I had removed years ago, not the as_id=signal it should for the bridge I had just configured.
appservice_stream_position had a single row, lock=X, stream_ordering=12345 (not exact, but very small number relatively speaking)

Workaround

Updating the stream_ordering value as per the workaround in matrix-org/synapse#1834 unwedged everything.

Version information

  • Version: 1.49.2

  • Install method: Docker

  • Platform: Linux

@matrixbot matrixbot changed the title Dummy issue newly-configured AS didn't receive new events Dec 21, 2023
@matrixbot matrixbot reopened this Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant