Following an instance by adding URL results in DB timeout and error message "Already following"
Description
When following an instance by adding its URL in the federation pannel of the admin UI, i get the error "already following" displayed in the UI, but this in the log:
Sep 17 12:32:56 gandibass2 mobilizon[772]: 12:32:56.616 request_id=FxWl1iin_XKKzlMAAFbB [info] Making relay follow relay@mobilizon.fr (approved: false)
Sep 17 12:32:56 gandibass2 mobilizon[772]: 12:32:56.638 [info] Sending https://events.basspistol.org/follow/844417fb-929c-4f91-bdbb-4e79a044d5f7 out via AP
Sep 17 12:32:56 gandibass2 mobilizon[772]: 12:32:56.645 request_id=FxWl1iin_XKKzlMAAFbB [info] Relay: followed instance https://mobilizon.fr/relay; id=https://events.basspistol.org/follow/844417fb-929c-4f91-bdbb-4e79a044d5f7
Sep 17 12:32:56 gandibass2 mobilizon[772]: 12:32:56.647 [info] Federating https://events.basspistol.org/follow/844417fb-929c-4f91-bdbb-4e79a044d5f7 to https://mobilizon.fr/inbox
Sep 17 12:33:11 gandibass2 mobilizon[772]: 12:33:11.648 [error] Postgrex.Protocol (#PID<0.4049.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.11534.0> timed out because it queued and checked out the connection for longer than 15000ms
Sep 17 12:33:11 gandibass2 mobilizon[772]: #PID<0.11534.0> was at location:
Sep 17 12:33:11 gandibass2 mobilizon[772]: :prim_inet.recv0/3
Sep 17 12:33:11 gandibass2 mobilizon[772]: (postgrex 0.16.3) lib/postgrex/protocol.ex:3108: Postgrex.Protocol.msg_recv/4
Sep 17 12:33:11 gandibass2 mobilizon[772]: (postgrex 0.16.3) lib/postgrex/protocol.ex:2138: Postgrex.Protocol.recv_bind/3
Sep 17 12:33:11 gandibass2 mobilizon[772]: (postgrex 0.16.3) lib/postgrex/protocol.ex:1993: Postgrex.Protocol.bind_execute_close/4
Sep 17 12:33:11 gandibass2 mobilizon[772]: (db_connection 2.4.2) lib/db_connection/holder.ex:354: DBConnection.Holder.holder_apply/4
Sep 17 12:33:11 gandibass2 mobilizon[772]: (db_connection 2.4.2) lib/db_connection.ex:1364: DBConnection.run_execute/5
Sep 17 12:33:11 gandibass2 mobilizon[772]: (db_connection 2.4.2) lib/db_connection.ex:1459: DBConnection.run/6
Sep 17 12:33:11 gandibass2 mobilizon[772]: (db_connection 2.4.2) lib/db_connection.ex:595: DBConnection.parsed_prepare_execute/5
Sep 17 12:33:11 gandibass2 mobilizon[772]: 12:33:11.659 request_id=FxWl1iin_XKKzlMAAFbB [info] Sent 500 in 15052ms
Sep 17 12:33:12 gandibass2 mobilizon[772]: 12:33:12.308 request_id=FxWl2dCIi4rhaMoAAFbx [info] POST /api
Sep 17 12:33:12 gandibass2 mobilizon[772]: 12:33:12.327 request_id=FxWl2dCIi4rhaMoAAFbx [warning] Error while following remote instance: :already_following
Sep 17 12:33:12 gandibass2 mobilizon[772]: 12:33:12.328 request_id=FxWl2dCIi4rhaMoAAFbx [warning] Unhandled error code: :already_following
If the instance is availble in the existing list, it get's status "pending response". If the instance is not in the existing list, status is no where to be seen (no entry for the instance in the lists All
, Following
or Followed
Steps to Reproduce
- Enter an URL in the "Follow a new instance" box and hit the button
- wait wait wait while the spinning wheel thinks
- Error message in red box in lower right corner says "already following"
Expected behaviour:
Add an entry in the list with status "Pending Response" or tell me the DB failed instead of "Already Following"
Actual behaviour:
No entry in the list what so ever, error message says "Already Following"
Reproduces how often:
Every time
Versions
Mobilizon 2.1.0
Additional Information
Postgress Data base is configured according to PG Tune (https://pgtune.leopard.in.ua/) set to linux, Web Application according to spec of the machine.