Portál AbcLinuxu, 10. května 2025 10:12
[uzivatel@mr_server ~]$ mysqld
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.
070820 10:04:35 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.
20.8.2007 15:58
Dalibor Smolík | skóre: 54
| blog: Postrehy_ze_zivota
| 50°5'31.93"N,14°19'35.51"E
# mysql config file for medium systems. # # This is for a system with little memory (32M - 64M) where MySQL plays # a important part and systems up to 128M where MySQL is used together with # other programs (like a web server) # # One can in this file use all long options that the program supports. # If you want to know which options a program support, run the program # with --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 datadir = /var/lib/mysql skip-locking key_buffer = 16M max_allowed_packet = 1M table_cache = 64 sort_buffer_size = 512K net_buffer_length = 16K myisam_sort_buffer_size = 8M # 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 # 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 # 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 = 4M #bdb_max_lock = 10000 # Uncomment the following if you are using InnoDB tables #innodb_data_home_dir = /var/lib/mysql #innodb_data_file_path = ibdata1:10M:autoextend #innodb_log_group_home_dir = /var/lib/mysql #innodb_log_arch_dir = /var/lib/mysql # 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 [isamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [myisamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [mysqlhotcopy] interactive-timeout
mysqld už neběží:
ps ax | grep mysqlPak by to také ještě mohl být problém v nastsavení přístupových práv k adresáři, kam mysql ukládá data (např. vlastníkem je
root, místo uživatele mysql).
20.8.2007 16:32
Dalibor Smolík | skóre: 54
| blog: Postrehy_ze_zivota
| 50°5'31.93"N,14°19'35.51"E
mysqld (klidně grepnout mysql, ať je jistota), protože init skript si může myslet, že mysqld neběží, a on mezitím vesele běží mimo kontrolu init skriptu.
Jasne, to jsem zkousel ... kdyz tam neco bylo, tak jsem to killnul a pak jsem znovu zkusil spoustet, ale nic. Grepuju "ps aux | grep my" btw. A ten demon se skutecne spousti "/etc/rc.d/mysqld start" ... za a) tam mysql neni, za b) je to tak i v navodu na arch wiki.Kontroloval jste, zda pak
mysqld už skutečně neběží? Pokud jste ji musel zabít nějakým drsnějším způsobem, nezůstaly po ní nějaké soubory-zámky?
Jeste to zkusim s prenastavenim prav.
PS: Jinak ted jsem udelal kompletni reinstall, odinstaloval jsem vsechno co souvisi s mysql (mysql, mysql-clients, libmysqlclient, phmyadmin) a pak jsem smazal vetsinu pozustatku pres "find /etc/ -name *mysql* |xargs rm -f" a " find /etc/ -name *mysql* |xargs rmdir". To mi pomohlo uz asi 3x, problem je ze se to pak stejne vetsinou pohnoji .....Pochybuji o tom, že to pomohlo, spíš to jenom skrylo problém. Na Linuxu se problémy neřeší tak, že budete něco reinstalovat pořád dokola. Jediný problém, kdy reinstalace pomůže, je pokud předchozí instalace neproběhne korektně a nějaké soubory se nainstalují špatně nebo vůbec, případně nedoběhnou poinstalační úpravy. Ale to nebude tenhle případ.
vydrzi ... no uvidime ... jdu pridat uzivatele a nastavit galerii
Dam vedet co a jak ... zatim diky moc!
PS: Pozabijel jsem co se dalo, procesy poznal stredovek ... ale tim to nebylo ...
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.