[1] MLD-5.x / Systems / x86 Systeme (PC) / MLD 5.3 - mysql-server startet nicht
 

Offline skippy

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 2280
    • View Profile
MLD 5.3 - mysql-server startet nicht
« on: February 11, 2017, 17:52:00 »
Hallo zusammen,

ich versuche mich auch mal an der MLD 5.3. Die Grundinstallation meines Servers hat problemlos funktioniert. Danach habe ich dann egp-daemon installiert und im WebIf konfiguriert. Soweit ich es ermittelt habe, läuft der mysql-server nicht. Hier das Log vom mysql-server:

Code: [Select]
2017-02-11 17:15:47 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-02-11 17:15:47 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30-1) starting as process 3185 ...
2017-02-11 17:15:47 3185 [Warning] Can't create test file /var/cache/mysql-data/MLD-Server.lower-test
2017-02-11 17:15:47 3185 [Warning] Can't create test file /var/cache/mysql-data/MLD-Server.lower-test
G/usr/sbin/mysqld: Can't change dir to '/var/cache/mysql-data/' (Errcode: 2 - No such file or directory)
2017-02-11 17:15:47 3185 [ERROR] Aborting

2017-02-11 17:15:47 3185 [Note] Binlog end
2017-02-11 17:15:47 3185 [Note] /usr/sbin/mysqld: Shutdown complete

170211 17:15:48 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
170211 17:26:06 mysqld_safe Starting mysqld daemon with databases from /var/cache/mysql-data
2017-02-11 17:26:07 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-02-11 17:26:07 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30-1) starting as process 10633 ...
2017-02-11 17:26:07 10633 [Warning] Can't create test file /var/cache/mysql-data/MLD-Server.lower-test
2017-02-11 17:26:07 10633 [Warning] Can't create test file /var/cache/mysql-data/MLD-Server.lower-test
G/usr/sbin/mysqld: Can't change dir to '/var/cache/mysql-data/' (Errcode: 2 - No such file or directory)
2017-02-11 17:26:07 10633 [ERROR] Aborting

2017-02-11 17:26:07 10633 [Note] Binlog end
2017-02-11 17:26:07 10633 [Note] /usr/sbin/mysqld: Shutdown complete

170211 17:26:07 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Das Verzeichnis /var/cache/mysql-data ist nicht vorhanden. Ich habe es angelegt und komme laut Log ein Stück weiter:

Code: [Select]
170211 17:30:27 mysqld_safe Starting mysqld daemon with databases from /var/cache/mysql-data
2017-02-11 17:30:28 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-02-11 17:30:28 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30-1) starting as process 11430 ...
2017-02-11 17:30:28 11430 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
2017-02-11 17:30:28 11430 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2017-02-11 17:30:28 11430 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-02-11 17:30:28 11430 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-11 17:30:28 11430 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-02-11 17:30:28 11430 [Note] InnoDB: Memory barrier is not used
2017-02-11 17:30:28 11430 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-02-11 17:30:28 11430 [Note] InnoDB: Using Linux native AIO
2017-02-11 17:30:28 11430 [Note] InnoDB: Not using CPU crc32 instructions
2017-02-11 17:30:28 11430 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-02-11 17:30:28 11430 [Note] InnoDB: Completed initialization of buffer pool
2017-02-11 17:30:28 11430 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2017-02-11 17:30:28 11430 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2017-02-11 17:30:28 11430 [Note] InnoDB: Database physically writes the file full: wait...
2017-02-11 17:30:29 11430 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2017-02-11 17:30:30 11430 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2017-02-11 17:30:31 11430 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2017-02-11 17:30:31 11430 [Warning] InnoDB: New log files created, LSN=45781
2017-02-11 17:30:31 11430 [Note] InnoDB: Doublewrite buffer not found: creating new
2017-02-11 17:30:31 11430 [Note] InnoDB: Doublewrite buffer created
2017-02-11 17:30:31 11430 [Note] InnoDB: 128 rollback segment(s) are active.
2017-02-11 17:30:31 11430 [Warning] InnoDB: Creating foreign key constraint system tables.
2017-02-11 17:30:31 11430 [Note] InnoDB: Foreign key constraint system tables created
2017-02-11 17:30:31 11430 [Note] InnoDB: Creating tablespace and datafile system tables.
2017-02-11 17:30:31 11430 [Note] InnoDB: Tablespace and datafile system tables created.
2017-02-11 17:30:31 11430 [Note] InnoDB: Waiting for purge to start
2017-02-11 17:30:31 11430 [Note] InnoDB: 5.6.30 started; log sequence number 0
2017-02-11 17:30:31 11430 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 680f9290-f077-11e6-b2e6-003005c8d061.
2017-02-11 17:30:31 11430 [Note] Server hostname (bind-address): '*'; port: 3306
2017-02-11 17:30:31 11430 [Note] IPv6 is available.
2017-02-11 17:30:31 11430 [Note]   - '::' resolves to '::';
2017-02-11 17:30:31 11430 [Note] Server socket created on IP: '::'.

Der empfohlene Befehl mysql_upgrade läuft auf Fehler:

Code: [Select]
MLD-Server> mysql_upgrade
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
Error: Failed while fetching Server version! Could be due to unauthorized access.
FATAL ERROR: Upgrade failed

Da ich noch nichts weiter konfiguriert habe, gehe ich von einem generellen Problem aus?!

Logs habe ich hochgeladen => der Upload Code lautet: XHPjZi

Viele Grüße skippy
meine MLDs (show / hide)

Online clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20445
    • View Profile
    • ClausMuus.de
MLD 5.3 - mysql-server startet nicht
« Reply #1 on: February 12, 2017, 19:49:59 »
Danke für den Hinweis.

Es geht jetzt wieder.

Claus
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 5.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 12TB HDD - Lian Li PC-C37B - Samsung LE40A559

Offline foehn

  • Newbie
  • *
  • Posts: 39
    • View Profile
MLD 5.3 - mysql-server startet nicht
« Reply #2 on: February 12, 2017, 21:30:27 »
Den gleichen Fehler hatte ich auch, als ich den EPG Deamon installiert hatte. Der my-sql demon hatte ein Problem beim Start und der Zugriff funktionierte nicht...

Der eigentliche Grund war, das dieses my-sqlserver paket garnicht installiert war. Einmal installiert funktionierte das EPG!!

Gruß Föhn
« Last Edit: February 12, 2017, 23:32:11 by foehn »

Offline goerdi

  • Profi Member
  • ****
  • Posts: 363
    • View Profile
MLD 5.3 - mysql-server startet nicht
« Reply #3 on: February 13, 2017, 00:15:02 »
Komisch ich kriege jetzt
Code: [Select]
Feb 13 00:13:17 (MLD) user.err epgd: Checking table structure and indices ...
Feb 13 00:13:17 (MLD) user.err epgd: SQL-Error in 'create index idxmovietitle on movie(movie_title);' - Specified key was too long; max key length is 767 bytes (1071)
Feb 13 00:13:17 (MLD) user.err epgd: SQL-Error in 'createIndices()' - Specified key was too long; max key length is 767 bytes (1071) '' [create index idxmovietitle on movie(movie_title);]
Feb 13 00:13:17 (MLD) user.err epgd: Closing mysql connection and calling mysql_thread_end(20443)

Offline skippy

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 2280
    • View Profile
MLD 5.3 - mysql-server startet nicht
« Reply #4 on: February 13, 2017, 16:24:52 »
Hi Claus,

auch bei mir funktioniert der mysql-server noch nicht. Ich bin noch einmal auf den Snapshot vor Installation des epg-daemon zurück gegangen. Nach Aktualisierung und Reboot habe ich dann den epg-daemon erneut installiert. Hier die Fehlermeldung aus dem error.log von /var/log/mysql:

Code: [Select]
170213 16:12:06 mysqld_safe Starting mysqld daemon with databases from /var/cache/mysql-data
2017-02-13 16:12:07 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-02-13 16:12:07 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30-1) starting as process 3088 ...
2017-02-13 16:12:07 3088 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
2017-02-13 16:12:07 3088 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2017-02-13 16:12:07 3088 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-02-13 16:12:07 3088 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-13 16:12:07 3088 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-02-13 16:12:07 3088 [Note] InnoDB: Memory barrier is not used
2017-02-13 16:12:07 3088 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-02-13 16:12:07 3088 [Note] InnoDB: Using Linux native AIO
2017-02-13 16:12:07 3088 [Note] InnoDB: Not using CPU crc32 instructions
2017-02-13 16:12:07 3088 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-02-13 16:12:07 3088 [Note] InnoDB: Completed initialization of buffer pool
2017-02-13 16:12:07 3088 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-13 16:12:07 3088 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2017-02-13 16:12:07 3088 [Note] InnoDB: Database was not shutdown normally!
2017-02-13 16:12:07 3088 [Note] InnoDB: Starting crash recovery.
2017-02-13 16:12:07 3088 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-02-13 16:12:07 3088 [Note] InnoDB: Restoring possible half-written data pages
2017-02-13 16:12:07 3088 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2017-02-13 16:12:08 3088 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2017-02-13 16:12:08 3088 [Note] InnoDB: 128 rollback segment(s) are active.
2017-02-13 16:12:08 3088 [Note] InnoDB: Waiting for purge to start
2017-02-13 16:12:08 3088 [Note] InnoDB: 5.6.30 started; log sequence number 1600607
2017-02-13 16:12:08 3088 [Note] Server hostname (bind-address): '*'; port: 3306
2017-02-13 16:12:08 3088 [Note] IPv6 is available.
2017-02-13 16:12:08 3088 [Note]   - '::' resolves to '::';
2017-02-13 16:12:08 3088 [Note] Server socket created on IP: '::'.
2017-02-13 16:12:08 3088 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
170213 16:12:08 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Aus meiner Sicht hat sich nicht viel geändert, außer dass nun das Verzeichnis /var/cache/mysql-data vorhanden war.

Noch eine Idee? Ich habe den grünen Haken erst einmal wieder entfernt  ;)

Viele Grüße skippy
meine MLDs (show / hide)

Offline skippy

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 2280
    • View Profile
MLD 5.3 - mysql-server startet nicht
« Reply #5 on: February 13, 2017, 17:39:55 »
Sorry, ich nehme alles zurück - mein Fehler!

Ich hatte zwar eine weitere SSD in den Server gepackt, auf dem ich die MLD 5.3 installiert habe. Allerdings hatte ich dieselbe Datenplatte verwendet. Dort ist ja auch der /var/cache Bereich drauf, auf der bereits die mysql-DB von der MLD 5.1 drauf ist. Habe jetzt mal eine frische Datenplatte genommen und siehe da, der mysql-server läuft. Hm, da muss ich wohl künftig mit Links arbeiten, wenn ich ein neues System testen will.

Haken wieder gesetzt  :-[

Viele Grüße skippy
meine MLDs (show / hide)

Offline skippy

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 2280
    • View Profile
MLD 5.3 - mysql-server startet nicht
« Reply #6 on: February 13, 2017, 18:05:21 »
Jetzt bekomme ich auch die Fehler, wie goerdi. Das scheint jedoch nicht der mysql-server, sondern der epg-daemon zu sein. Ich mache dazu mal einen neuen Thread auf.

Viele Grüße skippy
meine MLDs (show / hide)

Online clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20445
    • View Profile
    • ClausMuus.de
MLD 5.3 - mysql-server startet nicht
« Reply #7 on: February 13, 2017, 19:01:29 »
Hast Du mal ausprobiert, ob Du die alte DB, wie im Log vorgeschlagen, mit dem Befehl "mysql_upgrade" für die neue Version fitt machen kannst?

Claus
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 5.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 12TB HDD - Lian Li PC-C37B - Samsung LE40A559

Offline skippy

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 2280
    • View Profile
MLD 5.3 - mysql-server startet nicht
« Reply #8 on: February 13, 2017, 19:10:06 »
Ja hatte ich, siehe ersten Post oder hier:

Code: [Select]
MLD-Server> mysql_upgrade
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
Error: Failed while fetching Server version! Could be due to unauthorized access.
FATAL ERROR: Upgrade failed

Viele Grüße skippy
meine MLDs (show / hide)

[1] MLD-5.x / Systems / x86 Systeme (PC) / MLD 5.3 - mysql-server startet nicht
 



Users Online Users Online

0 Members and 1 Guest are viewing this topic.