@pomstan@xn–p1abe3d.xn–80asehdb I’ve pasted the transcript with the images linked, I’ll see if I can dig up the link to the .zip file somewhere
Notices by Sanae Respecter (frogmaiden@shrine.moe), page 2
-
Sanae Respecter (frogmaiden@shrine.moe)'s status on Thursday, 14-Sep-2023 22:05:19 JST Sanae Respecter -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Thursday, 14-Sep-2023 22:05:10 JST Sanae Respecter @Owl @EdBoatConnoisseur @pressure @colonelj @pomstan "Oh my God he used dunce! That's a high class word! Clearly, this is material for mockery!"
t. Lobotomite -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Thursday, 14-Sep-2023 22:04:49 JST Sanae Respecter @jetzkrieg you blaspheme the holy spirit regularly yet expect me to think you wrote this in good faith? Fuck off. :aifukkyu: -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Thursday, 14-Sep-2023 22:04:46 JST Sanae Respecter @EdBoatConnoisseur @jetzkrieg I don't think a man who DMs people about sticking hairbrush handles up his ass while masturbating should slander Christians with such misplaced confidence. -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Thursday, 14-Sep-2023 22:04:45 JST Sanae Respecter @EdBoatConnoisseur @jetzkrieg What does that inbred paki have to do with you shoving hairbrushes up your ass? The DM leaks are public you faggot. -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Thursday, 14-Sep-2023 22:04:41 JST Sanae Respecter @Owl @pomstan
"zomg he's discussing leaks that have been public knowledge for months"
I don't think that remotely compares to being somebody who shoves hairbrushes up his ass -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Thursday, 14-Sep-2023 22:04:36 JST Sanae Respecter @Owl @EdBoatConnoisseur @pressure @colonelj @pomstan I think the fact he shoves hairbrush handles up his ass is more funny and relevant than a small typo :marisa:
You must be the type of dunce to see pic related as peak humour -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Thursday, 14-Sep-2023 17:59:59 JST Sanae Respecter @jetzkrieg so not only are you a gay, atheistic pedophile but you're a bitch too :tenmasmug:
You should kill yourself so we need less millstones -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Tuesday, 16-May-2023 21:00:20 JST Sanae Respecter Gm -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Tuesday, 16-May-2023 04:52:54 JST Sanae Respecter Is Schwartzwelt down for anyone else? Can’t connect to it atm and SSH-ing doesn’t seem to work. I suspect there was a power interruption or something. I’ll be checking it in person myself shortly.
Furthermore if anyone knows resources to get dropbear running in initramfs on Alpine please let me know. Best I found so far is this merge request for mkinitfs
-
Sanae Respecter (frogmaiden@shrine.moe)'s status on Tuesday, 16-May-2023 04:52:47 JST Sanae Respecter CC: @mint @PurpCat -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Wednesday, 26-Apr-2023 08:14:56 JST Sanae Respecter @mint successfully compiled! To avoid this in the future, I'll put ```export MIX_ENV=prod``` to the pleroma user's .bashrc or .profile or whaever it is -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Wednesday, 26-Apr-2023 07:40:15 JST Sanae Respecter @mint Re-ran mix deps.get and ecto.migrate and am still getting the error
fuuuuuck -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Wednesday, 26-Apr-2023 07:36:41 JST Sanae Respecter @mint Haven't changed any of them recently and oh dear lord I just realized I forgot to set MIX_ENV to prod -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Wednesday, 26-Apr-2023 07:35:13 JST Sanae Respecter @mint Understood. On a related note, I just ran an update for pleroma (haven’t messed with postgres yet) and got this spat out at me:
17:31:03.213 [error] Postgrex.Protocol (#PID<0.17775.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "pleroma_dev" does not exist 17:31:03.213 [error] Postgrex.Protocol (#PID<0.17776.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "pleroma_dev" does not exist 17:31:04.718 [error] Postgrex.Protocol (#PID<0.17775.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "pleroma_dev" does not exist 17:31:05.581 [error] Postgrex.Protocol (#PID<0.17776.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "pleroma_dev" does not exist 17:31:06.097 [error] Could not create schema migrations table. This error usually happens due to the following: * The database does not exist * The "schema_migrations" table, which Ecto uses for managing migrations, was defined by another library * There is a deadlock while migrating (such as using concurrent indexes with a migration_lock) To fix the first issue, run "mix ecto.create". To address the second, you can run "mix ecto.drop" followed by "mix ecto.create". Alternatively you may configure Ecto to use another table and/or repository for managing migrations: config :pleroma, Pleroma.Repo, migration_source: "some_other_table_for_schema_migrations", migration_repo: AnotherRepoForSchemaMigrations The full error report is shown below. ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2974ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by: 1. Ensuring your database is available and that you can connect to it 2. Tracking down slow queries and making sure they are running fast enough 3. Increasing the pool_size (although this increases resource consumption) 4. Allowing requests to wait longer by increasing :queue_target and :queue_interval See DBConnection.start_link/2 for more information (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1 (elixir 1.14.2) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/2 (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:1005: Ecto.Adapters.SQL.execute_ddl/4 (ecto_sql 3.9.2) lib/ecto/migrator.ex:677: Ecto.Migrator.verbose_schema_migration/3 (ecto_sql 3.9.2) lib/ecto/migrator.ex:491: Ecto.Migrator.lock_for_migrations/4 (ecto_sql 3.9.2) lib/ecto/migrator.ex:403: Ecto.Migrator.run/4 (ecto_sql 3.9.2) lib/ecto/migrator.ex:146: Ecto.Migrator.with_repo/3 (pleroma 2.5.51-102-g3867b52a-develop+dev) lib/mix/tasks/pleroma/ecto/migrate.ex:63: Mix.Tasks.Pleroma.Ecto.Migrate.run/1 (mix 1.14.2) lib/mix/task.ex:421: anonymous fn/3 in Mix.Task.run_task/4 (mix 1.14.2) lib/mix/task.ex:479: Mix.Task.run_alias/6 (mix 1.14.2) lib/mix/cli.ex:84: Mix.CLI.run_task/2 (elixir 1.14.2) lib/code.ex:1260: Code.require_file/2``` -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Wednesday, 26-Apr-2023 07:31:28 JST Sanae Respecter @mint off the top of your head how simple is pgupgrade? I want to get this database from 14 to 15 and preferably not fuck it up. I backed up the data beforehand of course -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Monday, 17-Apr-2023 03:15:48 JST Sanae Respecter @PhenomX6 SSD, bought new about a month ago. This is the second time an IO failure like this as happened and last time I fixed it by changing the port it was plugged into -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Monday, 17-Apr-2023 03:05:41 JST Sanae Respecter OK even trying to cfdisk the drive is giving I/O errors. Is this drive totally fucked?
CC: @PhenomX6 -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Saturday, 15-Apr-2023 03:19:31 JST Sanae Respecter @mint @PhenomX6 @splitshockvirus it seems to be these postgres processes that shit themselves and crash everything. Would it be possible my changing of Pleroma-FE version caused this? Also how should I go about fixing this problem? ```DELETE FROM oban_jobs WHERE 1``` didn't work -
Sanae Respecter (frogmaiden@shrine.moe)'s status on Thursday, 13-Apr-2023 00:39:41 JST Sanae Respecter @mint I wonder what happened with it? Before the power outage when I first spun up the instance I had privoxy + tor up with no issues. God willing that SQL command + restart will clear it up