Notices by Matty (matty@gleasonator.com)

Embed this notice
Matty (matty@gleasonator.com)'s status on Wednesday, 19-Oct-2022 02:12:15 JST Matty
in reply to
- anime graf mays ?️?
- Alex Gleason
I've run the vacuum several times, but I'll give what you said a shot. I had considered that I turbo-fucked the database somehow, but I'm *really* hoping that's not the case. Should I stop the pleroma service prior to running the vacuum task? Thanks!

In conversation Wednesday, 19-Oct-2022 02:12:15 JST from gleasonator.com permalink
Embed this notice
Matty (matty@gleasonator.com)'s status on Wednesday, 19-Oct-2022 02:10:40 JST Matty
in reply to
- Alex Gleason
From git log
commit aba157c24048a1dbe40499d5b223c3bd09412dd4 (HEAD -> develop) Merge: e5afdaf04 044719737 Author: Matty <mattyboombalatty@protonmail.com> Date: Tue Oct 18 13:47:26 2022 +0000 Merge branch 'develop' of https://gitlab.com/soapbox-pub/soapbox-be into develop commit 0447197378e60ff2794acb13d1aa57b17aa6d883 (soapbox-be/develop, soapbox-be/HEAD) Merge: 22a153285 035d9e71e Author: Alex Gleason <alex@alexgleason.me> Date: Mon Oct 10 01:22:54 2022 +0000 Merge branch 'merge-pleroma' into 'develop' Merge Pleroma See merge request soapbox-pub/rebased!184 commit 22a1532850ce595cfc2bad110401a5bc661f09bb Merge: 04ee56407 0ee413400 Author: Alex Gleason <alex@alexgleason.me> Date: Sun Oct 9 22:36:58 2022 +0000 Merge branch 'link-tag-fix' into 'develop' Support FEP-e232 quote posts See merge request soapbox-pub/rebased!185
In conversation Wednesday, 19-Oct-2022 02:10:40 JST from gleasonator.com permalink
Attachments
1. Soapbox / Soapbox BE · GitLab
  
  Soapbox BE (Backend), the recommended backend for Soapbox based on Pleroma. https://soapbox.pub
2. Untitled attachment
3. Domain not in remote thumbnail source whitelist: proton.me
  
  Get a free, secure, and private email with Proton Mail
  
  Proton Mail is the world’s largest secure email service with over 70 million users. Available on Web, iOS, Android, and desktop. Protected by Swiss privacy law.
Embed this notice
Matty (matty@gleasonator.com)'s status on Wednesday, 19-Oct-2022 01:56:41 JST Matty
- Alex Gleason
Hey @alex , sorry to bother, but I seem to have super duper fucked my server up and I’m not quite sure how to remediate the issue. From what I can gather, there are too many database connections going on for some reason and the overwhelming majority of them are timing out. I upgraded to the latest develop branch of Soapbox-BE (not Rebased) and ran the mix ecto.migrate per the Pleroma administration documents.
I imagine this error is the one that’s causing the majority of my problems:
Oct 18 16:08:18 nicecrew mix[19683]: ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 153ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by: Oct 18 16:08:18 nicecrew mix[19683]: 1. Ensuring your database is available and that you can connect to it Oct 18 16:08:18 nicecrew mix[19683]: 2. Tracking down slow queries and making sure they are running fast enough Oct 18 16:08:18 nicecrew mix[19683]: 3. Increasing the pool_size (albeit it increases resource consumption) Oct 18 16:08:18 nicecrew mix[19683]: 4. Allowing requests to wait longer by increasing :queue_target and :queue_interval Oct 18 16:08:18 nicecrew mix[19683]: See DBConnection.start_link/2 for more information
But there’s also this error and I’m not sure if it’s relevant:
Oct 18 16:08:21 nicecrew mix[19683]: ** (ArgumentError) errors were found at the given arguments: Oct 18 16:08:21 nicecrew mix[19683]: * 1st argument: the table identifier does not refer to an existing ETS table Oct 18 16:08:21 nicecrew mix[19683]: (stdlib 3.17.2) :ets.lookup(Pleroma.Web.Endpoint, :__phoenix_url__)
I appreciate any help you can provide because I’m at a complete loss right now.

In conversation Wednesday, 19-Oct-2022 01:56:41 JST from gleasonator.com permalink

Public

Notices by Matty (matty@gleasonator.com)

User actions

Following 0

Followers 0

Groups 0

Statistics

Feeds