Hallo!
Seit geraumer Zeit lässt sich der VDR nicht mehr ausschalten ("wird später ausgeschaltet").
Ursache ist wohl, dass der EPGD offenbar permanent SQL-Errors bekommt, weil anscheinend der "Index events corrupted" ist:
Code
...
Jun 15 17:24:15 localhost epgd: Starting episode lookup ...
Jun 15 17:24:16 localhost epgd: SQL-Error in 'execute(store_result)' - Index events is corrupted (1712) 'Index events is corrupted' [select eventid, channelid, compshorttext, episodecomppartname, episodelang from events where comptitle = ?]
Jun 15 17:24:16 localhost epgd: message repeated 2775 times: [ SQL-Error in 'execute(store_result)' - Index events is corrupted (1712) 'Index events is corrupted' [select eventid, channelid, compshorttext, episodecomppartname, episodelang from events where comptitle = ?]]
Jun 15 17:24:16 localhost epgd: Lookup done for 2776 series, matched 0 parts by compare and 0 parts by lv in 1 seconds; Updated 0
Jun 15 17:24:16 localhost epgd: Calling 'mergeepg'
Jun 15 17:24:16 localhost epgd: SQL-Error in 'execute(stmt_execute)' - Index events is corrupted (1712) 'Index events is corrupted' [call mergeepg]
Jun 15 17:24:16 localhost epgd: State now 'busy (images)'
...Ich habe mich dann in mariadb (mysql) angemeldet und mit show tables; sehe ich u.a. die Tabelle "events".
check table events sagt auch, dass der Index kaputt ist:
Code
MariaDB [epg2vdr]> check table events;
+----------------+-------+----------+------------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+----------------+-------+----------+------------------------------------------------+
| epg2vdr.events | check | Warning | InnoDB: Index "PRIMARY" is marked as corrupted |
| epg2vdr.events | check | error | Corrupt |
+----------------+-------+----------+------------------------------------------------+Aber sämtliche Reparaturversuche scheitern damit, dass es die Tabelle anscheinend doch nicht gibt?!?!?!?
Code
MariaDB [epg2vdr]> optimize table events;
+----------------+----------+----------+------------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+----------------+----------+----------+------------------------------------------------+
| epg2vdr.events | optimize | Error | Table 'epg2vdr.events' doesn't exist in engine |
| epg2vdr.events | optimize | status | Operation failed |
+----------------+----------+----------+------------------------------------------------+
2 rows in set (0.00 sec)
...
MariaDB [epg2vdr]> repair table events;
+----------------+--------+----------+------------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+----------------+--------+----------+------------------------------------------------+
| epg2vdr.events | repair | Error | Table 'epg2vdr.events' doesn't exist in engine |
| epg2vdr.events | repair | status | Operation failed |
+----------------+--------+----------+------------------------------------------------+
2 rows in set (0.01 sec)Dann wollte ich den Index einfach löschen und neu anlegen, aber scheitere auch schon bei ersterem:
Code
MariaDB [epg2vdr]> alter table events drop index events;
ERROR 1932 (42S02): Table 'epg2vdr.events' doesn't exist in engine
=> Kann mir bitte dringend jemand sagen, wie ich am schnellsten und saubersten wieder aus der Nummer rauskomme?