• This forum has a zero tolerance policy regarding spam. If you register here to publish advertising, your user account will be deleted without further questions.

Msql hat öfters ausetzer

Dennisda

Registered User
Moinsen,

habe ein komisches Verhalten meines Mysql-Servers. Öfters konnte heute keine Verbingung zur mysql hergestellt werden, erst nach einem Neustart ging es wieder.

Laut Munin ist alles okay (sehe Anhang). In der Mysql.log sowie in der Mysql.err sind keine Einträge vorhanden.

Anbei meine my.cnf

Code:
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0

[mysqld]
#
# * Basic Settings
#
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
#bind-address           = 127.0.0.1
#
# * Fine Tuning
#
key_buffer              = 16M
max_allowed_packet      = 16M
thread_stack            = 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
max_connections        = 6
table_cache            = 450
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit       = 4M
query_cache_size        = 320M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log             = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
#log_slow_queries       = /var/log/mysql/mysql-slow.log
long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id              = 1
#log_bin                        = /var/log/mysql/mysql-bin.log
expire_logs_days        = 10
max_binlog_size         = 100M
#binlog_do_db           = include_database_name
#binlog_ignore_db       = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer              = 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/

Da keine ein-zigste Zeile in den Mysql.logs stehen, stehe ich ehrlich gesagt auf den Schlauch und weiß Grad nicht so recht voran es liegt das es sich aufhängt..Denke mal ist ne symple Sache, die ich wohl übersehen habe, jemand nen Tipp für mich `?
Gru´ß
Dennis
 

Attachments

  • mysql_innodb-day.png
    mysql_innodb-day.png
    13.9 KB · Views: 176
  • mysql_queries-day.png
    mysql_queries-day.png
    41.5 KB · Views: 165
  • mysql_slowqueries-day.png
    mysql_slowqueries-day.png
    13.5 KB · Views: 169
  • mysql_threads-day.png
    mysql_threads-day.png
    28.6 KB · Views: 181
  • mysql_bytes-day.png
    mysql_bytes-day.png
    30 KB · Views: 161
Ja, jedoch wird nichts rein geschrieben.
Mit mysqld -l /var/log/mysql.log
erhalte ich aufn Schirm ohne Ende folgendes;

Code:
140115 17:40:41 [Warning] Using unique option prefix key_buffer instead of key_uffer_size is deprecated and will be removed in a future release. Please use th full name instead.
140115 17:40:41 [Warning] The syntax '--log-slow-queries' is deprecated and wil be removed in a future release. Please use '--slow-query-log'/'--slow-query-lo-file' instead.
140115 17:40:41 [Warning] The syntax '--log' is deprecated and will be removed n a future release. Please use '--general-log'/'--general-log-file' instead.
140115 17:40:41 [Warning] Using unique option prefix myisam-recover instead of yisam-recover-options is deprecated and will be removed in a future release. Plase use the full name instead.
140115 17:40:41 [Note] Plugin 'FEDERATED' is disabled.
140115 17:40:41 InnoDB: The InnoDB memory heap is disabled
140115 17:40:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140115 17:40:41 InnoDB: Compressed tables use zlib 1.2.7
140115 17:40:41 InnoDB: Using Linux native AIO
140115 17:40:41 InnoDB: Initializing buffer pool, size = 128.0M
140115 17:40:41 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.
140115 17:40:41  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: 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
140115 17:42:21  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
140115 17:42:21  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
140115 17:42:21 InnoDB: Could not open or create data files.
140115 17:42:21 InnoDB: If you tried to add new data files, and it failed here,
140115 17:42:21 InnoDB: you should now edit innodb_data_file_path in my.cnf back
140115 17:42:21 InnoDB: to what it was, and remove the new ibdata files InnoDB created
140115 17:42:21 InnoDB: in this failed attempt. InnoDB only wrote those files full of
140115 17:42:21 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
140115 17:42:21 InnoDB: remove old data files which contain your precious data!
140115 17:42:21 [ERROR] Plugin 'InnoDB' init function returned error.
140115 17:42:21 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
mysqld: Too many arguments (first extra is '/var/log/mysql.log').
Use --verbose --help to get a list of available options
140115 17:42:21 [ERROR] Aborting

140115 17:42:21 [Note] mysqld: Shutdown complete

Scheint wohl nen Problem mit InnoDB zu haben !!
 
Hey,
als erstes sichern.

Dann lösche mal alle Deine Logfiles des mysql-servers, starte neu und checke Deine log erneut.

Und überprüfe was er so oft ausgibt: Läuft noch ein weiterer Daemon oder eine andere Instanz?

emerge
 
Gelöscht, jetzt legt er auch ne Error.log an;

Code:
140115 18:10:47 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140115 18:10:47 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please $
140115 18:10:47 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-qu$
140115 18:10:47 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future relea$
140115 18:10:47 [Note] Plugin 'FEDERATED' is disabled.
140115 18:10:47 InnoDB: The InnoDB memory heap is disabled
140115 18:10:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140115 18:10:47 InnoDB: Compressed tables use zlib 1.2.7
140115 18:10:47 InnoDB: Using Linux native AIO
140115 18:10:47 InnoDB: Initializing buffer pool, size = 128.0M
140115 18:10:47 InnoDB: Completed initialization of buffer pool
140115 18:10:47 InnoDB: highest supported file format is Barracuda.
140115 18:10:48  InnoDB: Waiting for the background threads to start
140115 18:10:49 InnoDB: 5.5.33 started; log sequence number 21730226
140115 18:10:49 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140115 18:10:49 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
140115 18:10:49 [Note] Server socket created on IP: '0.0.0.0'.
140115 18:10:49 [Note] Event Scheduler: Loaded 0 events
140115 18:10:49 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.33-0+wheezy1-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)

Kann iwie nicht verstehen das er wegen der Host so meckert, kann es an der Networks liegen ?
 
Last edited by a moderator:
Das sieht doch gut aus. Und nun abwarten und beobachten bis er wieder langsam wird => log file nachschauen, was war ...

Wenn Dein Server nicht allzu leistungsfähig ist und Deine Logdateien, die du gerade gelöscht hast riesig waren, war Dein Server vielleicht zu sehr mit den Logdateien beschäftigt. Wenn Sie groß waren, solltest du logrotate installieren.

emerge
 
Das system ist nen Frisches also Kaum last (hat 16GB Ram und Quad-Core) Prozessor) Besucher sind nur ganz wenig so 5 Leutchen Momentan !
Werds mal beobachten, Danke.
 
Dann liegt es nicht an den Logdateien! Also: Inhalt der Logdateien lesen, wenn es wieder so weit ist! - emerge -

Ergänzung: Vielleicht steht ja noch was verwertbares in /var/log ...
 
Habe eben folgende Beobachtung gemacht. Habe eben zwei mal hintereinander den Apache2 restartet. zack war Mysqk abgeschmiert, jedoch nach einigen Sekunden (ca. 10-40sec) wieder da. Die Webseiten haben mir Signalisiert, das keine Mysql Verbindung aufgebaut werden konnte.

Die Logs sind sauber und unauffällig, dadurch bin ich gerade sehr verwirrt Oo
 
Gibt es eine echte Fehlermeldung von MySQL?
Kannst Du Dich als root (bei Plesk als "admin") noch in die MySQL-Console einloggen? Wenn ja: "show processlist;".

Ansonsten tippe ich darauf:
#bind-address = 127.0.0.1
Zu viele Connections von Außen. Egal ob erfolgreiche Logins oder nicht.
Das würde ich zumindest mal abstellen.

huschi.
 
Gibt es eine echte Fehlermeldung von MySQL?

Hier die mysqld.error.log;

Code:
140116 16:39:29 [Note] /usr/sbin/mysqld: Normal shutdown

140116 16:39:29 [Note] Event Scheduler: Purging the queue. 0 events
140116 16:39:31 [Warning] /usr/sbin/mysqld: Forcing close of thread 196  user: 'ispconfig'

140116 16:39:31 [Warning] /usr/sbin/mysqld: Forcing close of thread 195  user: 'ispconfig'

140116 16:39:31 [Warning] /usr/sbin/mysqld: Forcing close of thread 194  user: 'ispconfig'

140116 16:39:31 [Warning] /usr/sbin/mysqld: Forcing close of thread 193  user: 'ispconfig'

140116 16:39:31 [Warning] /usr/sbin/mysqld: Forcing close of thread 192  user: 'ispconfig'

140116 16:39:31  InnoDB: Starting shutdown...
140116 16:39:33  InnoDB: Shutdown completed; log sequence number 22537828
140116 16:39:33 [Note] /usr/sbin/mysqld: Shutdown complete

140116 16:39:33 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140116 16:39:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140116 16:39:34 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full n$
140116 16:39:34 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' $
140116 16:39:34 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use$
140116 16:39:34 [Note] Plugin 'FEDERATED' is disabled.
140116 16:39:34 InnoDB: The InnoDB memory heap is disabled
140116 16:39:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140116 16:39:34 InnoDB: Compressed tables use zlib 1.2.7
140116 16:39:34 InnoDB: Using Linux native AIO
140116 16:39:34 InnoDB: Initializing buffer pool, size = 128.0M
140116 16:39:34 InnoDB: Completed initialization of buffer pool
140116 16:39:34 InnoDB: highest supported file format is Barracuda.
140116 16:39:34  InnoDB: Waiting for the background threads to start
140116 16:39:35 InnoDB: 5.5.33 started; log sequence number 22537828
140116 16:39:35 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
140116 16:39:35 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
140116 16:39:35 [Note] Server socket created on IP: '127.0.0.1'.
140116 16:39:35 [Note] Event Scheduler: Loaded 0 events
140116 16:39:35 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.33-0+wheezy1-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)

In andere Log's schreibt er gar nichts mehr.

Kannst Du Dich als root (bei Plesk als "admin") noch in die MySQL-Console einloggen? Wenn ja: "show processlist;".
Verwende kein Plesk.. auf der Mühle läuft noch ispconfig.

hier die alte Ausgabe von show processlist;

Code:
+------+-----------+-----------------+-------------+---------+------+-------+---                                                                                        ---------------+
| Id   | User      | Host            | db          | Command | Time | State | In                                                                                        fo             |
+------+-----------+-----------------+-------------+---------+------+-------+---                                                                                        ---------------+
| 1499 | ispconfig | localhost:55192 | dbispconfig | Sleep   | 2055 |       | NU                                                                                        LL             |
| 1591 | ispconfig | localhost:55265 | dbispconfig | Sleep   |  255 |       | NU                                                                                        LL             |
| 4443 | root      | localhost       | NULL        | Query   |    0 | NULL  | sh                                                                                        ow processlist |
+------+-----------+-----------------+-------------+---------+------+-------+---                                                                                        ---------------+
3 rows in set (0.00 sec)

Dann habe ich das # bei der Bind Adresse entfernt und nu sieht es so aus;

Code:
+-----+------+-----------+------+---------+------+-------+------------------+
| Id  | User | Host      | db   | Command | Time | State | Info             |
+-----+------+-----------+------+---------+------+-------+------------------+
| 178 | root | localhost | NULL | Query   |    0 | NULL  | show processlist |
+-----+------+-----------+------+---------+------+-------+------------------+
1 row in set (0.00 sec)
Also recht Passabel.
 
Mit "echter Fehlermeldung" meinte ich eine konkrete Ausgabe eines MySQL-Fehlers in Erweiterung von "konnte heute keine Verbingung zur mysql hergestellen". (Sprich: Was kam auf dem Bildschirm?)

Der "show processlist;" wäre natürlich genau in einem Ausfallzeitraum abzusetzen. Zu jeder anderen Zeit erhält man natürlich keine brauchbaren Daten.

Fällt MySQL denn weiterhin regelmäßig aus?

huschi.
 
Back
Top