!Friendica Support 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?
@OldKid @Tuxi (Backup) An dieser Stelle möchte ich Euch Beiden und allen anderen Administratoren herzlich für Eure Arbeit danken, die Ihr meines Wissens oft in Eurer Freizeit macht. LOB LOB LOB !!!
@Friendica Support Ich habe einen neuen #Circle erstellt, Welche #Einstellungen muss ich vornehmen, wenn ich die Einträge in diesem Circle ausschließlich für mich anzeigen lassen will?
Im Labor gezüchtet, Corona scharf präpariert, wer’s so benannte, wurd’ gleich attackiert. Kanzleramt schwieg, hielt Berichte zurück, Medien jagten den kritischen Blick. Jetzt kommt es heraus, doch was bringt es noch? Die Wahrheit verstaubt – im politischen Loch!
I've just realised something, which I assume is down to imperfect federation between Friendica and Mastodon: When I reply to someone on Mastodon, it automatically includes a mention of them @name.whatever - but I don't see that mention. If it's a nested comment, multiple mentions might be included. I only realised this when someone asked to stop mentioning them in a thread, and didn't realise I had.
Is this intentional? Is there a way to not mention someone in a comment on their post (or a reply to a comment)? Thanks.
@Noam writes I think "Settings" > "Additional features" > "Post composition" > "Explicit mentions" controls whether these mentions are hidden or not; if they are explicitly placed in the compose box, you can remove them. That's my understanding anyway.
„500 Millionen Europäer bitten 300 Millionen Amerikaner, sie vor 140 Millionen Russen zu schützen, die seit 3 Jahren nicht in der Lage sind, mit 40 Millionen Ukrainern ‚fertig zu werden.“
Some minutes ago i disabled maintenance-mode and manually called bin/worker.php. As result, the console showed this
bin/console maintenance 0 System set in normal mode
bin/worker.php [10-Mar-2025 21:50:31 UTC] PHP Notice: fwrite(): Write of 1040 bytes failed with errno=12 Cannot allocate memory in /var/www/virtual/snila/html/vendor/guzzlehttp/psr7/src/Stream.php on line 257 [10-Mar-2025 21:50:31 UTC] PHP Notice: include(): Read of 2266 bytes failed with errno=12 Cannot allocate memory in /var/www/virtual/snila/html/vendor/composer/ClassLoader.php on line 444 [10-Mar-2025 21:50:31 UTC] PHP Warning: include(): Failed opening '/var/www/virtual/snila/html/vendor/composer/../guzzlehttp/promises/src/RejectedPromise.php' for inclusion (include_path='.:/opt/remi/php82/root/usr/share/pear:/opt/remi/php82/root/usr/share/php:/usr/share/pear:/usr/share/php:/var/www/virtual/snila/html/include:/var/www/virtual/snila/html/library:/var/www/virtual/snila/html') in /var/www/virtual/snila/html/vendor/composer/ClassLoader.php on line 444 [10-Mar-2025 21:50:31 UTC] PHP Notice: fwrite(): Write of 3126 bytes failed with errno=12 Cannot allocate memory in /var/www/virtual/snila/html/src/Core/Logger/Type/StreamLogger.php on line 105 Getötet
As far as I know, nothing has changed in terms of available resources.
Hi @Michael 🇺🇦 , thank you for your quick view at my log-excerpts. So i will give Uberspace-support a try.
Anyway during the last weeks i noticed lots of reports related to high load and database-problems. From time to time i had to call dica.interfel.de twice to get an answer. These days libranet.de always needs two or three calls to get any result.
Hello , @Friendica Support It's been more than 2 months since UpdateContacts the one highlighted in red it doesn't end , can you tell me how i can remove it?
@Anomaly then if you open terminal on your server, and cd to your friendica dir, bin/worker.php it should run the worker, and one other thing you can try, is go to myphpadmin open your database for friendica, and in the sql tab enter DELETE FROM `workerqueue` WHERE `done` = 1; which will clear all jobs completed, the task may be completed, but not cleared out of the database table. other than that maybe @hypolite can help maybe better
@Anomaly also try, Admin/Site/Worker Maximum load average=50, Maximum number of parallel workers=20, Maximum load for workers=150, Worker defer limit=15, Worker fetch limit=25, it may help as well as double check your Database Lock Wait Timeouts, check the Friendica log files for any error messages related to lock wait timeouts, sorry I cant offer more, im a little limited on my knowledge, just sharing everything I know, because I have dealt with some of these issues, y
@Anomaly Deferred tasks aren't currently running. They failed during they initial run, which placed them in this wait list with a next try date in the future. From your screenshot it appears that the task creation date and the next try date are pretty close to each other, so it must only have failed a few times at most.
Running either the worker or the daemon manually will not clear deferred tasks which next try date have not been reached yet. There's an incremental back off system that increases the delay before the next try after each new failure. Once the task succeeds, the task will clear from the deferred list.
@Hypolite Petovan yes I thought this, but why has this entry been in the list for 2 months? All entries are successfully completed . I have no problems with friendica, if this entry does not cause problems,can be on the list
Diese Webseite verwendet Cookies zur Erkennung von wiederkehrenden Besuchern und eingeloggten Nutzern. Durch die weitere Benutzung der Webseite akzeptierst du die Verwendung der Cookies.
OldKid ⁂
Als Antwort auf Gerhard Hallstein • • •@Gerhard Hallstein forum.friendi.ca/display/8ffdf…
Tuxi (Backup)
2025-03-14 16:19:32
Gerhard Hallstein
Als Antwort auf Gerhard Hallstein • • •LOB LOB LOB !!!