Ich hatte mit einer SQL DB bei einer Neueinrichtung etwas mit den Werten getestet, die ganze Zeit funktionierte die DB. Der Zugriff von extern etc. funktionierte, phpMyAdmin ebenso.
Mittlerweile geht weder phpMyAdmin noch der externe Zugriff. Im Ereignis Log finde ich folgende Einträge:
Code
180726 08:40:11 mysqld_safe mysqld from pid file /var/lock/qmysql.pid ended
180726 08:40:46 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
180726 8:40:46 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.5.57-MariaDB) starting as process 6354 ...
180726 8:40:46 InnoDB: The InnoDB memory heap is disabled
180726 8:40:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180726 8:40:46 InnoDB: Compressed tables use zlib 1.2.3
180726 8:40:46 InnoDB: Initializing buffer pool, size = 254.0M
180726 8:40:46 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file /usr/local/mysql/data/ibdata1 did not exist:
InnoDB: a new database to be created!
180726 8:40:46 InnoDB: Setting file /usr/local/mysql/data/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
180726 8:40:46 InnoDB: Error: Write to file /usr/local/mysql/data/ibdata1 failed at offset 0 8388608.
InnoDB: 1048576 bytes should have been written, only 888832 were written.
InnoDB: Operating system error number 28.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 28 means 'No space left on device'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: Error in creating /usr/local/mysql/data/ibdata1: probably out of disk space
180726 8:40:46 InnoDB: Could not open or create data files.
180726 8:40:46 InnoDB: If you tried to add new data files, and it failed here,
180726 8:40:46 InnoDB: you should now edit innodb_data_file_path in my.cnf back
180726 8:40:46 InnoDB: to what it was, and remove the new ibdata files InnoDB created
180726 8:40:46 InnoDB: in this failed attempt. InnoDB only wrote those files full of
180726 8:40:46 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
180726 8:40:46 InnoDB: remove old data files which contain your precious data!
180726 8:40:46 [ERROR] Plugin 'InnoDB' init function returned error.
180726 8:40:46 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
180726 8:40:46 [Note] Plugin 'FEEDBACK' is disabled.
180726 8:40:46 [Note] Server socket created on IP: 'x.x.x.x'.
180726 8:40:46 [Note] Event Scheduler: Loaded 0 events
180726 8:40:46 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.57-MariaDB' socket: '/tmp/mysql.sock' port: 3306 MariaDB Server
Alles anzeigen
Das /usr/local/mysql/data/ Verzeichnis war gar nicht da. Wenn ich das erzeuge, dann wir die Datei erstellt aber es kommt dennoch der Fehler oben.
Ich habe unter den Anwendungen/SQL Server schon die DB neu initialisieren lassen.
Habt ihr eine Idee zur Lösung?
Hier noch die my.cnf, wobei diese original zu sein scheint:
Code
# Example MariaDB config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MariaDB plays
# an important part, or systems up to 128M where MariaDB is used together with
# other programs (such as a web server)
#
# MariaDB programs look for option files in a set of
# locations which depend on the deployment platform.
# You can copy this option file to one of those
# locations. For information about these locations, do:
# 'my_print_defaults --help' and see what is printed under
# Default options are read from the following files in the given order:
# More information at: http://dev.mysql.com/doc/mysql/en/option-files.html
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.
# The following options will be passed to all MariaDB clients
[client]
#password = your_password
port = 3306
socket = /tmp/mysql.sock
# Here follows entries for some specific programs
# The MariaDB server
[mysqld]
port = 3306
socket = /tmp/mysql.sock
skip-external-locking
key_buffer_size = 16M
max_allowed_packet = 1M
table_open_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
default-storage-engine = MyISAM
#skip-innodb
# Point the following paths to different dedicated disks
#tmpdir = /tmp/
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking
# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin
# binary logging format - mixed recommended
binlog_format=mixed
# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1
# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin
# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/mysql/data
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /usr/local/mysql/data
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50
[mysqldump]
quick
max_allowed_packet = 16M
[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates
[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
Alles anzeigen