Why Nostr? What is Njump?
2025-03-14 16:19:32

Tuxi (Backup) on Nostr: Hallo Profis, ich habe ein Problem mit meiner Instanz. In den Logs taucht folgender ...

Hallo Profis, ich habe ein Problem mit meiner Instanz. In den Logs taucht folgender DB-Fehler auf:
Index for table 'post-user' is corrupt; try to repair it

Ein CHECK TABLE `post-user`; in der MariaDB Konsole zeigt folgendes:
MariaDB [friendica]> CHECK TABLE `post-user`;
+---------------------+-------+----------+-----------------------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+---------------------+-------+----------+-----------------------------------------------------------+
| friendica.post-user | check | Warning | InnoDB: The B-tree of index PRIMARY is corrupted. |
| friendica.post-user | check | Warning | InnoDB: Index uid_uri-id is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index uri-id is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index parent-uri-id is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index thr-parent-id is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index external-id is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index owner-id is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index author-id is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index causer-id is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index vid is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index contact-id is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index event-id is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index psid is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index author-id_uid is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index parent-uri-id_uid is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index uid_contactid is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index uid_unseen_contactid is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index uid_unseen is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index uid_hidden_uri-id is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index uid_wall_received is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index author-id_created is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index owner-id_created is marked as corrupted |
| friendica.post-user | check | Warning | InnoDB: Index replies-id is marked as corrupted |
| friendica.post-user | check | error | Corrupt |
+---------------------+-------+----------+-----------------------------------------------------------+
24 rows in set (57,683 sec)

Wenn ich REPAIR TABLE `post-user`; kommt folgende Ausgabe:
MariaDB [friendica]> REPAIR TABLE `post-user`;
+---------------------+--------+----------+---------------------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+---------------------+--------+----------+---------------------------------------------------------+
| friendica.post-user | repair | note | The storage engine for the table doesn't support repair |
+---------------------+--------+----------+---------------------------------------------------------+
1 row in set (1 min 53,258 sec)

Ich habe keinen Plan mehr. Könnt ihr mich bitte Unterstützen?
Author Public Key
npub1m8vp0dqs8f9t2d7chs6mgze0rxy9wpxqj2thpyufey8vkv64dq6qfv8gv5