Skocz do zawartości


 

Zdjęcie

Mysql potrzebna pomoc

Mysql potrzebna pomoc

  • Proszę się zalogować aby odpowiedzieć
13 odpowiedzi na ten temat

Mysql potrzebna pomoc

#1 Kochan

Kochan

    Czasami na forum

  • Użytkownicy
  • 44 postów

Napisany 31 sierpień 2017 - 12:40

Panowie mysql mi się wykrzaczył  

 Error connecting to MySQL: Can't connect to local MySQL server through socket '/usr/local/mysql/data/mysql.sock' (2)

 

Prośba o pomoc, niby uruchomiony a nie działa nawet phpmyadmin 


  • 0

#2 Gość_Kamikadze_*

Gość_Kamikadze_*
  • Goście

Napisany 31 sierpień 2017 - 12:48

Podałeś informacje w stylu. Samochód mi nie działa. Nie mogę go uruchomić. Gdy przekręcam kluczyk to słychać rozrusznik.


  • 0

#3 Kochan

Kochan

    Czasami na forum

  • Użytkownicy
  • 44 postów

Napisany 31 sierpień 2017 - 12:52

Sory, padł serwer mysql. W uruchomionych usługach niby jest widoczny. Dostaje błąd w directadminie Error connecting to MySQL: Can't connect to local MySQL server through socket '/usr/local/mysql/data/mysql.sock' (2)

 

 

 ps auxf | grep mysql
root     22028  0.0  0.0  13444  3216 pts/0    S    13:30   0:00  |       \_ /bi                                                                                                                                                             n/sh /usr/bin/mysqld_safe --skip-grant-tables
mysql    22413  0.0  0.1 550988 47348 pts/0    Sl   13:30   0:00  |       |   \_                                                                                                                                                              /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/                                                                                                                                                             mysql/plugin --user=mysql --skip-grant-tables --log-error=/var/log/mysql/error.l                                                                                                                                                             og --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --                                                                                                                                                             port=3306
root     24697  0.0  0.0  12732  2252 pts/0    S+   13:51   0:00  |       \_ gre                                                                                                                                                             p mysql

Status

mysql.service - LSB: Start and stop the mysql database server daemon
   Loaded: loaded (/etc/init.d/mysql)
   Active: active (exited) since Thu 2017-08-31 13:23:44 CEST; 29min ago
  Process: 19433 ExecStop=/etc/init.d/mysql stop (code=exited, status=0/SUCCESS)
  Process: 19490 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS)

Aug 31 13:23:44 serwer.szukampracypl.kylos.net.pl mysql[19490]: Starting MySQL database server: mysqld ..
Aug 31 13:23:44 serwer.szukampracypl.kylos.net.pl mysql[19490]: Checking for tables which need an upgrade, are corrupt or were
Aug 31 13:23:44 serwer.szukampracypl.kylos.net.pl mysql[19490]: not closed cleanly..
Aug 31 13:23:44 serwer.szukampracypl.kylos.net.pl systemd[1]: Started LSB: Start and stop the mysql database server daemon.
Aug 31 13:34:20 serwer.szukampracypl.kylos.net.pl systemd[1]: Started LSB: Start and stop the mysql database server daemon.


w mysql status jest 

mysql  Ver 15.1 Distrib 5.5.46-MariaDB, for Linux (x86_64) using readline 5.1

Connection id:          7
Current database:
Current user:           root@localhost
SSL:                    Not in use
Current pager:          stdout
Using outfile:          ''
Using delimiter:        ;
Server:                 MySQL
Server version:         5.5.57-0+deb8u1 (Debian)
Protocol version:       10
Connection:             Localhost via UNIX socket
Server characterset:    latin1
Db     characterset:    latin1
Client characterset:    utf8
Conn.  characterset:    utf8
UNIX socket:            /var/run/mysqld/mysqld.sock
Uptime:                 27 min 23 sec


Edytowany przez Kochan, 31 sierpień 2017 - 12:59.

  • 0

#4 Gość_Kamikadze_*

Gość_Kamikadze_*
  • Goście

Napisany 31 sierpień 2017 - 13:00

Error loga sprawdź /var/log/mysql/error.log


  • 0

#5 Gość_patrys_*

Gość_patrys_*
  • Goście

Napisany 31 sierpień 2017 - 13:03

mysql


Edytowany przez patrys, 09 wrzesień 2017 - 00:09.

  • 0

#6 Kochan

Kochan

    Czasami na forum

  • Użytkownicy
  • 44 postów

Napisany 31 sierpień 2017 - 13:06

170831 13:16:02 [Note]
170831 13:16:02 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
170831 13:16:02 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170831 13:16:02 [Note] Plugin 'FEDERATED' is disabled.
170831 13:16:02 InnoDB: The InnoDB memory heap is disabled
170831 13:16:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170831 13:16:02 InnoDB: Compressed tables use zlib 1.2.8
170831 13:16:02 InnoDB: Using Linux native AIO
170831 13:16:02 InnoDB: Initializing buffer pool, size = 128.0M
170831 13:16:02 InnoDB: Completed initialization of buffer pool
170831 13:16:02 InnoDB: highest supported file format is Barracuda.
170831 13:16:02  InnoDB: Waiting for the background threads to start
170831 13:16:03 InnoDB: 5.5.57 started; log sequence number 1595685
170831 13:16:03 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170831 13:16:03 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
170831 13:16:03 [Note] Server socket created on IP: '127.0.0.1'.
170831 13:16:03 [Note] Event Scheduler: Loaded 0 events
170831 13:16:03 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.57-0+deb8u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
170831 13:21:48 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
170831 13:21:48 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.46-MariaDB) starting as process 16884 ...
170831 13:21:48 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 728 error messages, but it should contain at least 933 error messages.
Check that the above file is the right version for this program!
170831 13:21:48 [ERROR] Aborting

170831 13:21:48 [Note]
170831 13:21:48 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
170831 13:21:51 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
170831 13:21:51 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.46-MariaDB) starting as process 17322 ...
170831 13:21:51 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 728 error messages, but it should contain at least 933 error messages.
Check that the above file is the right version for this program!
170831 13:21:51 [ERROR] Aborting

170831 13:21:51 [Note]
170831 13:21:51 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
170831 13:22:00 [Note] /usr/sbin/mysqld: Normal shutdown

170831 13:22:00 [Note] Event Scheduler: Purging the queue. 0 events
170831 13:22:00  InnoDB: Starting shutdown...
170831 13:22:01  InnoDB: Shutdown completed; log sequence number 1595685
170831 13:22:01 [Note] /usr/sbin/mysqld: Shutdown complete

170831 13:22:07 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170831 13:22:07 [Note] Plugin 'FEDERATED' is disabled.
170831 13:22:07 InnoDB: The InnoDB memory heap is disabled
170831 13:22:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170831 13:22:07 InnoDB: Compressed tables use zlib 1.2.8
170831 13:22:07 InnoDB: Using Linux native AIO
170831 13:22:07 InnoDB: Initializing buffer pool, size = 128.0M
170831 13:22:07 InnoDB: Completed initialization of buffer pool
170831 13:22:07 InnoDB: highest supported file format is Barracuda.
170831 13:22:07  InnoDB: Waiting for the background threads to start
170831 13:22:08 InnoDB: 5.5.57 started; log sequence number 1595685
170831 13:22:08 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170831 13:22:08 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
170831 13:22:08 [Note] Server socket created on IP: '127.0.0.1'.
170831 13:22:08 [Note] Event Scheduler: Loaded 0 events
170831 13:22:30 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
170831 13:22:30 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.46-MariaDB) starting as process 18440 ...
170831 13:22:30 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 728 error messages, but it should contain at least 933 error messages.
Check that the above file is the right version for this program!
170831 13:22:30 [ERROR] Aborting

170831 13:22:30 [Note]
170831 13:22:30 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
170831 13:23:25 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
170831 13:23:25 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.46-MariaDB) starting as process 18958 ...
170831 13:23:25 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 728 error messages, but it should contain at least 933 error messages.
Check that the above file is the right version for this program!
170831 13:23:25 [ERROR] Aborting

170831 13:23:25 [Note]
170831 13:23:25 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
170831 13:23:33 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
170831 13:23:33 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.46-MariaDB) starting as process 19408 ...
170831 13:23:33 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 728 error messages, but it should contain at least 933 error messages.
Check that the above file is the right version for this program!
170831 13:23:33 [ERROR] Aborting

170831 13:23:33 [Note]
170831 13:23:33 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
170831 13:23:38 [Note] /usr/sbin/mysqld: Normal shutdown

170831 13:23:38 [Note] Event Scheduler: Purging the queue. 0 events
170831 13:23:38  InnoDB: Starting shutdown...
170831 13:23:39  InnoDB: Shutdown completed; log sequence number 1595685
170831 13:23:39 [Note] /usr/sbin/mysqld: Shutdown complete

170831 13:23:42 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170831 13:23:42 [Note] Plugin 'FEDERATED' is disabled.
170831 13:23:42 InnoDB: The InnoDB memory heap is disabled
170831 13:23:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170831 13:23:42 InnoDB: Compressed tables use zlib 1.2.8
170831 13:23:42 InnoDB: Using Linux native AIO
170831 13:23:42 InnoDB: Initializing buffer pool, size = 128.0M
170831 13:23:42 InnoDB: Completed initialization of buffer pool
170831 13:23:42 InnoDB: highest supported file format is Barracuda.
170831 13:23:42  InnoDB: Waiting for the background threads to start
170831 13:23:43 InnoDB: 5.5.57 started; log sequence number 1595685
170831 13:23:43 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170831 13:23:43 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
170831 13:23:43 [Note] Server socket created on IP: '127.0.0.1'.
170831 13:23:43 [Note] Event Scheduler: Loaded 0 events
170831 13:23:43 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.57-0+deb8u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
170831 13:28:29 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
170831 13:28:29 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.46-MariaDB) starting as process 20632 ...
170831 13:28:29 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 728 error messages, but it should contain at least 933 error messages.
Check that the above file is the right version for this program!
170831 13:28:29 [ERROR] Aborting

170831 13:28:29 [Note]
170831 13:28:29 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
170831 13:29:46 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
170831 13:29:46 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.46-MariaDB) starting as process 21134 ...
170831 13:30:40 InnoDB: 5.5.57 started; log sequence number 1595685
170831 13:30:40 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170831 13:30:40 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
170831 13:30:40 [Note] Server socket created on IP: '127.0.0.1'.
170831 13:30:40 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.57-0+deb8u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
170831 13:32:07 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
170831 13:32:07 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.46-MariaDB) starting as process 23261 ...
170831 13:32:07 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 728 error messages, but it should contain at least 933 error messages.
Check that the above file is the right version for this program!
170831 13:32:07 [ERROR] Aborting

170831 13:32:07 [Note]
170831 13:32:07 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
170831 13:34:29 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
170831 13:34:29 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.46-MariaDB) starting as process 23811 ...
170831 13:34:29 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 728 error messages, but it should contain at least 933 error messages.
Check that the above file is the right version for this program!
170831 13:34:29 [ERROR] Aborting

170831 13:34:29 [Note]
170831 13:34:29 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
170831 13:34:40 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
170831 13:34:40 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.46-MariaDB) starting as process 24254 ...
170831 13:34:40 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 728 error messages, but it should contain at least 933 error messages.
Check that the above file is the right version for this program!
170831 13:34:40 [ERROR] Aborting

170831 13:34:40 [Note]
170831 13:34:40 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
170831 13:36:56 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170831 13:36:56 [Note] Plugin 'FEDERATED' is disabled.
170831 13:36:56 InnoDB: The InnoDB memory heap is disabled
170831 13:36:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170831 13:36:56 InnoDB: Compressed tables use zlib 1.2.8
170831 13:36:56 InnoDB: Using Linux native AIO
170831 13:36:56 InnoDB: Initializing buffer pool, size = 128.0M
170831 13:36:56 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
170831 13:36:56  InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
170831 13:38:36  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
170831 13:38:36  InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
170831 13:38:36 InnoDB: Could not open or create data files.
170831 13:38:36 InnoDB: If you tried to add new data files, and it failed here,
170831 13:38:36 InnoDB: you should now edit innodb_data_file_path in my.cnf back
170831 13:38:36 InnoDB: to what it was, and remove the new ibdata files InnoDB created
170831 13:38:36 InnoDB: in this failed attempt. InnoDB only wrote those files full of
170831 13:38:36 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
170831 13:38:36 InnoDB: remove old data files which contain your precious data!
170831 13:38:36 [ERROR] Plugin 'InnoDB' init function returned error.
170831 13:38:36 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
170831 13:38:36 [ERROR] Unknown/unsupported storage engine: InnoDB
170831 13:38:36 [ERROR] Aborting

170831 13:38:36 [Note] mysqld: Shutdown complete

170831 14:00:01 [Note] /usr/sbin/mysqld: Normal shutdown

170831 14:00:01  InnoDB: Starting shutdown...
170831 14:00:02  InnoDB: Shutdown completed; log sequence number 1595685
170831 14:00:02 [Note] /usr/sbin/mysqld: Shutdown complete

170831 14:00:03 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170831 14:00:03 [Note] Plugin 'FEDERATED' is disabled.
170831 14:00:03 InnoDB: The InnoDB memory heap is disabled
170831 14:00:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170831 14:00:03 InnoDB: Compressed tables use zlib 1.2.8
170831 14:00:03 InnoDB: Using Linux native AIO
170831 14:00:03 InnoDB: Initializing buffer pool, size = 128.0M
170831 14:00:03 InnoDB: Completed initialization of buffer pool
170831 14:00:03 InnoDB: highest supported file format is Barracuda.
170831 14:00:03  InnoDB: Waiting for the background threads to start
170831 14:00:04 InnoDB: 5.5.57 started; log sequence number 1595685
170831 14:00:04 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170831 14:00:04 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
170831 14:00:04 [Note] Server socket created on IP: '127.0.0.1'.
170831 14:00:04 [Note] Event Scheduler: Loaded 0 events
170831 14:00:04 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.57-0+deb8u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)

Powtarza się 

InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process


  • 0

#7 Gość_mariaczi_*

Gość_mariaczi_*
  • Goście

Napisany 31 sierpień 2017 - 13:11

No to "ło Panie" napisz cóżeś Pan zrobił na tym serwerze, bo tak samo to się nie wzięło i nie wysypało.

 

Dostałeś już podpowiedź od kolegi patrys.

 

DA próbuje się łączyć do socketa w

/usr/local/mysql/data/mysql.sock

a status serwera zgłasza, że ma go w

/var/run/mysqld/mysqld.sock

i se musisz to uspójnić.

 


Edytowany przez mariaczi, 31 sierpień 2017 - 13:13.

  • 0

#8 Kochan

Kochan

    Czasami na forum

  • Użytkownicy
  • 44 postów

Napisany 31 sierpień 2017 - 13:13

po  restarcie 
170831 14:10:18 [Note] Event Scheduler: Purging the queue. 0 events
170831 14:10:18  InnoDB: Starting shutdown...
170831 14:10:19  InnoDB: Shutdown completed; log sequence number 1595685
170831 14:10:19 [Note] /usr/sbin/mysqld: Shutdown complete

170831 14:10:19 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170831 14:10:19 [Note] Plugin 'FEDERATED' is disabled.
170831 14:10:19 InnoDB: The InnoDB memory heap is disabled
170831 14:10:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170831 14:10:19 InnoDB: Compressed tables use zlib 1.2.8
170831 14:10:19 InnoDB: Using Linux native AIO
170831 14:10:19 InnoDB: Initializing buffer pool, size = 128.0M
170831 14:10:19 InnoDB: Completed initialization of buffer pool
170831 14:10:19 InnoDB: highest supported file format is Barracuda.
170831 14:10:19  InnoDB: Waiting for the background threads to start
170831 14:10:20 InnoDB: 5.5.57 started; log sequence number 1595685
170831 14:10:20 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170831 14:10:20 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
170831 14:10:20 [Note] Server socket created on IP: '127.0.0.1'.
170831 14:10:20 [Note] Event Scheduler: Loaded 0 events
170831 14:10:20 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.57-0+deb8u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)

Prawdopodobnie poszła druga  instalacja mysql-server z mysqltunnera, ewentualnie zmieniło się hasło da_admin ale to odpada bo zmieniłem w configu.

 

Tu chyba problem 

# service mysqld status
● mysqld.service - MySQL database server
   Loaded: loaded (/etc/systemd/system/mysqld.service; enabled)
   Active: inactive (dead) since Thu 2017-08-31 14:15:38 CEST; 1s ago
  Process: 27911 ExecStart=/usr/local/mysql/bin/mysqld_safe --datadir=/usr/local/mysql/data --pid-file=/usr/local/mysql/data/mysqld.pid --socket=/usr/local/mysql/data/mysql.sock (code=exited, status=0/SUCCESS)
 Main PID: 27911 (code=exited, status=0/SUCCESS)

 


Edytowany przez Kochan, 31 sierpień 2017 - 13:16.

  • 0

#9 Kochan

Kochan

    Czasami na forum

  • Użytkownicy
  • 44 postów

Napisany 31 sierpień 2017 - 13:47

zrobiłem symlinka na szybko, błędu w DA niema ale wywaliło wszystkie bazy ;/ mam backup zarz przywrócę i zerknę czy pójdzie. 

 

Niestety nie chodzi ;/ błędu nie ma. 


Edytowany przez Kochan, 31 sierpień 2017 - 13:49.

  • 0

#10 Gość_mariaczi_*

Gość_mariaczi_*
  • Goście

Napisany 31 sierpień 2017 - 13:49

Coś tu nie kuka. DA chyba sam instaluje serwer MySQLa i umieszcza go tam, gdzie próbował się podłączyć. Ty natomiast chciałeś go doinstalować przez menadżera pakietów z dystrybucji?


  • 0

#11 Gość_Kamikadze_*

Gość_Kamikadze_*
  • Goście

Napisany 31 sierpień 2017 - 13:54

W DA przez CB kompilujesz mysql albo mariadb do wyboru.


  • 0

#12 Kochan

Kochan

    Czasami na forum

  • Użytkownicy
  • 44 postów

Napisany 31 sierpień 2017 - 13:58

Dobra backup przywrócony, odpaliła się baza poprawnie. 

Dziękuje bardzo za pomoc


Edytowany przez Kochan, 31 sierpień 2017 - 14:17.

  • 0

#13 Kochan

Kochan

    Czasami na forum

  • Użytkownicy
  • 44 postów

Napisany 01 wrzesień 2017 - 00:10


Nadal, mam problem, po updejcie php-fpm + apache nie ruszył ponownie mysql
 mysqld.service - MySQL database server
   Loaded: loaded (/etc/systemd/system/mysqld.service; enabled)
   Active: inactive (dead) since Fri 2017-09-01 00:59:24 CEST; 6min ago
  Process: 19684 ExecStart=/usr/local/mysql/bin/mysqld_safe --datadir=/usr/local/mysql/data --pid-file=/usr/local/mysql/data/mysqld.pid --socket=/usr/local/mysql/data/mysql.sock (code=exited, status=0/SUCCESS)
 Main PID: 19684 (code=exited, status=0/SUCCESS)
 
Sep 01 00:59:24 serwer.szukampracypl.kylos.net.pl systemd[1]: Started MySQL database server.
Sep 01 00:59:24 serwer.szukampracypl.kylos.net.pl mysqld_safe[19684]: 170901 00:59:24 mysqld_safe Can't log to error log and syslog at the same time.  Remove ...effect.
Sep 01 00:59:24 serwer.szukampracypl.kylos.net.pl mysqld_safe[19684]: 170901 00:59:24 mysqld_safe Logging to '/var/log/mysql/error.log'.
Sep 01 00:59:24 serwer.szukampracypl.kylos.net.pl mysqld_safe[19684]: 170901 00:59:24 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
Sep 01 00:59:24 serwer.szukampracypl.kylos.net.pl mysqld_safe[19684]: 170901 00:59:24 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended
Hint: Some lines were ellipsized, use -l to show in full.
 

Edytowany przez Kochan, 01 wrzesień 2017 - 00:19.

  • 0

#14 Gość_mariaczi_*

Gość_mariaczi_*
  • Goście

Napisany 01 wrzesień 2017 - 09:28

...po updejcie php-fpm + apache nie ruszył ponownie mysql

Jak robiłes tą aktualizację apache i php-fpm'a?
  • 0





0 użytkowników czyta ten temat

0 użytkowników, 0 gości, 0 anonimowych użytkowników