Skocz do zawartości
Zaloguj się, aby obserwować  
czaczawik

Po edycji my.cnf MySQL nie wstaje

Polecane posty

Tak jak w temacie, Chciałem według jakiegoś tutka zoptymalizować SQL, zatem wrzuciłem 'gotowca' do /etc/my.cnf dokładnie to:

 

 

# Example MySQL config file for very large systems.
#
# This is for a large system with memory of 1G-2G where the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# 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 MySQL clients
[client]
#password = your_password
port  = 3306
socket  = /tmp/mysql.sock
# Here follows entries for some specific programs
# The MySQL server
[mysqld]
port  = 3306
socket  = /tmp/mysql.sock
skip-locking
key_buffer = 384M
max_allowed_packet = 1M
table_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 1
# 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
# Disable Federated by default
skip-federated
# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin
# 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
# Point the following paths to different dedicated disks
#tmpdir  = /tmp/
#log-update  = /path-to-dedicated-directory/hostname
# Uncomment the following if you are using BDB tables
#bdb_cache_size = 384M
#bdb_max_lock = 100000
# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/mysql/data/
#innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend
#innodb_log_group_home_dir = /usr/local/mysql/data/
#innodb_log_arch_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 = 384M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 100M
#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
[isamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M
[myisamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout

 

no i przy takim my.cnf nie mogę wystartować MySQL z panelu DA.

Czy jakaś dobra dusza moze mnie nakierować na to, co w tym pliku może powodować w/o problemy? Na mój lamerski móżdżek to coś ze ściezkami do mysql.sock ale nie wiem jak to ogarnąć

Udostępnij ten post


Link to postu
Udostępnij na innych stronach

zerknij w logach

 

tail /home/mysql/*.err

 

czy gdzie tam masz dane mysql

 

Powinien pokazać co mu nie pasuje

Udostępnij ten post


Link to postu
Udostępnij na innych stronach

jedynie takie dwa errory

 

 

120901 19:19:19 mysqld_safe mysqld from pid file /usr/local/mysql/data/serwer.pid ended
120901 19:20:04 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
120901 19:20:05 [Note] Plugin 'FEDERATED' is disabled.
120901 19:20:05 InnoDB: The InnoDB memory heap is disabled
120901 19:20:05 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120901 19:20:05 InnoDB: Compressed tables use zlib 1.2.3
120901 19:20:05 InnoDB: Using Linux native AIO
120901 19:20:05 InnoDB: Initializing buffer pool, size = 128.0M
120901 19:20:05 InnoDB: Completed initialization of buffer pool
120901 19:20:05 InnoDB: highest supported file format is Barracuda.
120901 19:20:09 InnoDB: Waiting for the background threads to start
120901 19:20:10 InnoDB: 1.1.5 started; log sequence number 1659688
120901 19:20:10 [ERROR] /usr/local/mysql/bin/mysqld: unknown option '--skip-locking'
120901 19:20:10 [ERROR] Aborting

 

zaraz zakomentuje i zobaczymy

 

EDIT

tak to był problem, ale na wczesniejszym vps ten my.cnf dzialal. Możliwe ze przy nowszym mysal / php dzieją sie takie kwiatki ?

Edytowano przez czaczawik (zobacz historię edycji)

Udostępnij ten post


Link to postu
Udostępnij na innych stronach

Bądź aktywny! Zaloguj się lub utwórz konto

Tylko zarejestrowani użytkownicy mogą komentować zawartość tej strony

Utwórz konto

Zarejestruj nowe konto, to proste!

Zarejestruj nowe konto

Zaloguj się

Posiadasz własne konto? Użyj go!

Zaloguj się

Zaloguj się, aby obserwować  

×