Tuxi (Backup) / is on Nostr

Dies ist das Backup-Profil von tux@anonsys.net.
(anonsys.net/profile/tux)

Last Notes

2025-03-21 18:59:49

- reply

Okay. Es scheint sich jetzt beruhigt zu haben. Seltsam.

2025-03-21 18:26:43

- reply

Hallo Profis,
habe eine neue Datenbank erstellt, dort die Sicherung eingespielt, die ich Ende Januar für den Serverumzug auch verwendet habe. In der "local.config.php habe ich den Namen der Datenbank auf die neue geändert.
Trotzdem funktioniert die Instanz nicht und ich habe massenhaft DB Errors im friendical.og. Wieso funktioniert die Sicherung die vor ein paar Wochen für den umzug noch funktioniert hat aufeinmal nicht mehr. Das passt doch irgendwie nicht zusammen.
Auszug aus dem friendica.log:2025-03-21T18:18:54Z app [ERROR]: DB Error {"code":1356,"error":"View 'friendicadb.account-user-view' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them","params":"SELECT `id`, `uid`, `pid` FROM `account-user-view` WHERE (`id` = 2467202) LIMIT 1"} - {"file":"Database.php","line":675,"function":"p","request-id":"67ddad8e2bdd7","stack":"Database::p (1494), Database::select (1379), Database::selectFirst (420), DBA::selectFirst (651), Contact::getPublicAndUserContactID (178), User::isBlocked (299), Contact::getVisitorByUrl (149), UserSession::setVisitorsContacts (318), Authentication::setForUser (182), Authentication::withSession (586), App::runFrontend (32)","uid":"2bc66a","process_id":4838}
2025-03-21T18:18:54Z app [ERROR]: DB Error {"code":1356,"error":"View 'friendicadb.account-user-view' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them","params":"SELECT `id`, `uid`, `pid` FROM `account-user-view` WHERE (`id` = 2468202) LIMIT 1"} - {"file":"Database.php","line":675,"function":"p","request-id":"67ddad8e2bdd7","stack":"Database::p (1494), Database::select (1379), Database::selectFirst (420), DBA::selectFirst (651), Contact::getPublicAndUserContactID (178), User::isBlocked (299), Contact::getVisitorByUrl (149), UserSession::setVisitorsContacts (318), Authentication::setForUser (182), Authentication::withSession (586), App::runFrontend (32)","uid":"2bc66a","process_id":4838}
2025-03-21T18:18:54Z worker [ERROR]: DB Error {"code":1356,"error":"View 'friendicadb.account-user-view' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them","params":"SELECT `platform`, `contact-type` FROM `account-user-view` WHERE (`uri-id` = 34862127) LIMIT 1"} - {"file":"Database.php","line":675,"function":"p","request-id":"67ddad8d549a0","stack":"Database::p (1494), Database::select (1379), Database::selectFirst (420), DBA::selectFirst (2038), Contact::getDefaultAvatar (2357), Contact::updateAvatar (2924), Contact::updateFromProbeArray (2704), Contact::updateFromProbe (32), UpdateContact::execute, Worker::execFunction (374), Worker::execute (109), Worker::processQueue (75)","uid":"c10296","process_id":4897}
2025-03-21T18:18:54Z worker [ERROR]: DB Error {"code":1356,"error":"View 'friendicadb.account-user-view' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them","params":"SELECT `platform`, `contact-type` FROM `account-user-view` WHERE (`uri-id` = 34862127) LIMIT 1"} - {"file":"Database.php","line":675,"function":"p","request-id":"67ddad8d6343c","stack":"Database::p (1494), Database::select (1379), Database::selectFirst (420), DBA::selectFirst (2038), Contact::getDefaultAvatar (2357), Contact::updateAvatar (2924), Contact::updateFromProbeArray (2704), Contact::updateFromProbe (2639), Contact::updateByIdIfNeeded (2654), Contact::updateByUrlIfNeeded (1763), Processor::processActivity (1691), Processor::fetchMissingActivity (34), FetchMissingActivity::execute, Worker::execFunction (374), Worker::execute (109)","uid":"00abbf","process_id":4900}
2025-03-21T18:18:54Z app [ERROR]: DB Error {"code":1356,"error":"View 'friendicadb.account-user-view' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them","params":"SELECT `id`, `uid`, `pid` FROM `account-user-view` WHERE (`id` = 4317477) LIMIT 1"} - {"file":"Database.php","line":675,"function":"p","request-id":"67ddad8e2bdd7","stack":"Database::p (1494), Database::select (1379), Database::selectFirst (420), DBA::selectFirst (651), Contact::getPublicAndUserContactID (178), User::isBlocked (299), Contact::getVisitorByUrl (149), UserSession::setVisitorsContacts (318), Authentication::setForUser (182), Authentication::withSession (586), App::runFrontend (32)","uid":"2bc66a","process_id":4838}
Seltsamerweise sagt mir ein "mysqlcheck -u root -p --check --databases friendicadb" das alles in Ordnung wäre:
mysqlcheck -u root -p --check --databases friendicadb
Enter password:
friendicadb.2fa_app_specific_password OK
friendicadb.2fa_recovery_codes OK
friendicadb.2fa_trusted_browser OK
friendicadb.account-suggestion OK
friendicadb.account-user OK
friendicadb.addon OK
friendicadb.advancedcontentfilter_rules OK
friendicadb.apcontact OK
friendicadb.application OK
friendicadb.application-marker OK
friendicadb.application-token OK
friendicadb.arrived-activity
note : The storage engine for the table doesn't support check
friendicadb.attach OK
friendicadb.auth_codes OK
friendicadb.cache OK
friendicadb.challenge OK
friendicadb.channel OK
friendicadb.check-full-text-search OK
friendicadb.clients OK
friendicadb.config OK
friendicadb.contact OK
friendicadb.contact-relation OK
friendicadb.conv OK
friendicadb.conversation OK
friendicadb.delayed-post OK
friendicadb.delivery-queue OK
friendicadb.diaspora-contact OK
friendicadb.diaspora-interaction OK
friendicadb.endpoint OK
friendicadb.event OK
friendicadb.fcontact OK
friendicadb.fetch-entry OK
friendicadb.fetched-activity
note : The storage engine for the table doesn't support check
friendicadb.fsuggest OK
friendicadb.group OK
friendicadb.group_member OK
friendicadb.gserver OK
friendicadb.gserver-tag OK
friendicadb.hook OK
friendicadb.host OK
friendicadb.inbox-entry OK
friendicadb.inbox-entry-receiver OK
friendicadb.inbox-status OK
friendicadb.intro OK
friendicadb.item-uri OK
friendicadb.key-value OK
friendicadb.locks OK
friendicadb.mail OK
friendicadb.mailacct OK
friendicadb.manage OK
friendicadb.notification OK
friendicadb.notify OK
friendicadb.notify-threads OK
friendicadb.oembed OK
friendicadb.openwebauth-token OK
friendicadb.parsed_url OK
friendicadb.pconfig OK
friendicadb.permissionset OK
friendicadb.photo OK
friendicadb.post OK
friendicadb.post-activity OK
friendicadb.post-category OK
friendicadb.post-collection OK
friendicadb.post-content OK
friendicadb.post-counts OK
friendicadb.post-delivery OK
friendicadb.post-delivery-data OK
friendicadb.post-engagement OK
friendicadb.post-history OK
friendicadb.post-link OK
friendicadb.post-media OK
friendicadb.post-origin OK
friendicadb.post-question OK
friendicadb.post-question-option OK
friendicadb.post-searchindex OK
friendicadb.post-tag OK
friendicadb.post-thread OK
friendicadb.post-thread-user OK
friendicadb.post-user OK
friendicadb.post-user-notification OK
friendicadb.process OK
friendicadb.processed-activity
note : The storage engine for the table doesn't support check
friendicadb.profile OK
friendicadb.profile_check OK
friendicadb.profile_field OK
friendicadb.push_subscriber OK
friendicadb.register OK
friendicadb.report OK
friendicadb.report-post OK
friendicadb.report-rule OK
friendicadb.search OK
friendicadb.session OK
friendicadb.storage OK
friendicadb.subscription OK
friendicadb.tag OK
friendicadb.tokens OK
friendicadb.user OK
friendicadb.user-contact OK
friendicadb.user-gserver OK
friendicadb.userd OK
friendicadb.verb OK
friendicadb.worker-ipc
note : The storage engine for the table doesn't support check
friendicadb.workerqueue OK

2025-03-21 18:25:06

- reply

2025-03-19 07:28:41

- reply

Der Dump ließ sich gestern ohne Probleme einspielen. Leider ist es nur so, dass ich mich mit diesem Dump nicht anmelden konnte.

2025-03-18 06:03:00

- reply

Also folgender Stand:
Ich konnte gestern einen Dump der DB ziehen. Danach konnte ich seltsamerweise euch ein mysqloptimize erfolgreich und ohne Fehlermeldung ausführen. Ob das am innodb_force_recovery 4 liegt oder an was anderem, kann ich, ehrlich gesagt nicht sagen.
Die Instanz lief danach auch für eine Zeit ohne Probleme. Allerdings sind dann nach so ca. 30 Minuten wieder die gleichen Fehlermeldungen im Friendica-Log aufgetaucht.
Aktuell läuft ein Testimport der gestern exportierten Datenbank. Wenn diese erfolgreich ist, dann hätte ich zumindest Daten auf einem Stand von gestern.
Allerdings frage ich mich, ob der mysqldump korrupt ist, oder nicht?
@nprofile…rgpg
Frage: Wenn ich den Import erfolgreich in eine andere DB durchführen konnte, kann ich dann in der local.config.php den Namen der DB einfach ändern und es ist alles lauffähig? Oder ist der Name der DB auch noch irgendwo anderes hinterlegt?

2025-03-17 13:50:18

- reply

@nprofile…n53r
Aufgrund des kaputten Indexes funktioniert leider auch kein mysqldump. Mist.
mysqldump: Error 1034: Index for table 'apcontact' is corrupt; try to repair it when dumping table `apcontact` at row: 1859034
Ich werde es aber jetzt mit der --force Option versuchen.

2025-03-17 08:18:33

- reply

@nprofile…6g6r
Habe auch das Gefühl, dass da mehr im argen ist.

2025-03-17 08:17:53

- reply

@nprofile…n53r
Danke. Werde ich mal durchlesen und testen.

2025-03-14 18:43:53

- reply

@nprofile…y0e7
😔
mysqldump: Error 1030: Got error 1877 "Unknown error 1877" from storage engine InnoDB when dumping table `post-user` at row: 0

2025-03-14 18:18:23

- reply

@nprofile…y0e7
Crap an ALTER TABLE `post-user` FORCE; produces the following output:MariaDB [friendica]> ALTER TABLE `post-user` FORCE;
ERROR 1177 (42000): Can't open table

2025-03-14 17:30:45

- reply

@nprofile…y0e7
Thanks! 👍

2025-03-14 17:28:19

- reply

2025-03-14 16:54:24

- reply

Thanks @nprofile…y0e7
Since I am not a database professional, I will ask to be on the safe side. The command is correctly ALTER TABLE post-user FORCE; ?
Um, how dangerous is this execution? Will data be lost?

2025-03-14 16:47:14

- reply

Es scheinen mehrere Tabellen corrupt zu sein. Ein mysqlcheck zeigt folgendes:mysqlcheck -u root -p --check --databases friendica
Enter password:
friendica.2fa_app_specific_password OK
friendica.2fa_recovery_codes OK
friendica.2fa_trusted_browser OK
friendica.account-suggestion OK
friendica.account-user OK
friendica.addon OK
friendica.advancedcontentfilter_rules OK
friendica.apcontact
Warning : InnoDB: The B-tree of index PRIMARY is corrupted.
Warning : InnoDB: Index uri-id is marked as corrupted
Warning : InnoDB: Index addr is marked as corrupted
Warning : InnoDB: Index alias is marked as corrupted
Warning : InnoDB: Index followers is marked as corrupted
Warning : InnoDB: Index baseurl is marked as corrupted
Warning : InnoDB: Index gsid is marked as corrupted
Warning : InnoDB: Index sharedinbox is marked as corrupted
error : Corrupt
friendica.application OK
friendica.application-marker OK
friendica.application-token OK
friendica.arrived-activity
note : The storage engine for the table doesn't support check
friendica.attach OK
friendica.auth_codes OK
friendica.cache OK
friendica.challenge OK
friendica.channel OK
friendica.check-full-text-search OK
friendica.clients OK
friendica.config OK
friendica.contact
Warning : InnoDB: The B-tree of index PRIMARY is corrupted.
Warning : InnoDB: Index uid_name is marked as corrupted
Warning : InnoDB: Index self_uid is marked as corrupted
Warning : InnoDB: Index pending_uid is marked as corrupted
Warning : InnoDB: Index blocked_uid is marked as corrupted
Warning : InnoDB: Index uid_rel_network_poll is marked as corrupted
Warning : InnoDB: Index uid_network_batch is marked as corrupted
Warning : InnoDB: Index attag_uid is marked as corrupted
Warning : InnoDB: Index network_uid_lastupdate is marked as corrupted
Warning : InnoDB: Index uid_network_self_lastupdate is marked as corrupted
Warning : InnoDB: Index uid_lastitem is marked as corrupted
Warning : InnoDB: Index alias_uid is marked as corrupted
Warning : InnoDB: Index addr_uid is marked as corrupted
Warning : InnoDB: Index nurl_uid is marked as corrupted
Warning : InnoDB: Index nick_uid is marked as corrupted
Warning : InnoDB: Index baseurl is marked as corrupted
Warning : InnoDB: Index batch_contact-type is marked as corrupted
Warning : InnoDB: Index uid_contact-type is marked as corrupted
Warning : InnoDB: Index uid_self_contact-type is marked as corrupted
Warning : InnoDB: Index self_network_uid is marked as corrupted
Warning : InnoDB: Index uri-id is marked as corrupted
Warning : InnoDB: Index next-update is marked as corrupted
Warning : InnoDB: Index local-data-next-update is marked as corrupted
Warning : InnoDB: Index gsid_uid_failed is marked as corrupted
error : Corrupt

2025-03-14 16:45:27

- reply

@nprofile…rgpg
Trotzdem Danke. Vielleicht weiß ja jemand anderes noch ein Rat?

2025-03-14 16:19:32

2025-01-20 07:00:05

- reply

@nprofile…uyml
Nein leider nicht. Heute Nacht ist der Import der DB mit einem Fehler abgebrochen. Es wird einen neuen Termin geben, wenn ich weiß, was los war.
anonsys.net/display/bf69967c-1…