I am installing mysql-5.5.13.tar.gz in debian 6.0.4. I am following the steps from here
When I run the step
scripts/mysql_install_db --user=mysql I get the exception that
bash: scripts/mysql_install_db: No such file or directory
But file exist in the place. I made that executable too but its not working. I was working in the root terminal. Please help me to resolve this problem.
Thanks
I installed mysql-5.5.24-linux2.6-i686.tar.gz Now after executing command root#server06:/usr/local/mysql# scripts/mysql_install_db --user=mysql I got the message Installing MySQL system tables...
./bin/mysqld: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory
Installation of system tables failed! Examine the logs in
./data for more information.
You can try to start the mysqld daemon with:
shell> ./bin/mysqld --skip-grant &
and use the command line tool ./bin/mysql
to connect to the mysql database and look at the grant tables:
shell> ./bin/mysql -u root mysql
mysql> show tables
Try 'mysqld --help' if you have problems with paths. Using --log
gives you a log in ./data that may be helpful.
Please consult the MySQL manual section
'Problems running mysql_install_db', and the manual section that
describes problems on your OS. Another information source are the
MySQL email archives available at http://lists.mysql.com/.
Please check all of the above before mailing us! And remember, if
you do mail us, you MUST use the ./bin/mysqlbug script!
and mysql is not started. Please help me should I download another one?
I installed "libaio" using apt-get then it was successfully installed. but when i started mysql using commandbin/mysqld_safe --user=mysql & I got the message
root#server06:/usr/local/mysql# bin/mysqld_safe --user=mysql
120514 16:10:11 mysqld_safe Logging to '/var/lib/mysql/server06.err'.
120514 16:10:11 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120514 16:10:13 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
In the /var/lib/mysql/server06.err file I found following
20514 16:15:49 [Note]
120514 16:15:49 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
120514 16:17:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
120514 16:17:57 [ERROR] Can't find messagefile '/usr/share/mysql/english/errmsg.sys'
120514 16:17:57 [Note] Plugin 'FEDERATED' is disabled.
120514 16:17:57 InnoDB: The InnoDB memory heap is disabled
120514 16:17:57 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
120514 16:17:57 InnoDB: Compressed tables use zlib 1.2.3
120514 16:17:57 InnoDB: Using Linux native AIO
120514 16:17:57 InnoDB: Initializing buffer pool, size = 128.0M
120514 16:17:57 InnoDB: Completed initialization of buffer pool
120514 16:17:57 InnoDB: highest supported file format is Barracuda.
120514 16:17:57 InnoDB: Waiting for the background threads to start
120514 16:17:58 InnoDB: 1.1.8 started; log sequence number 1595675
120514 16:17:58 [ERROR] Aborting
120514 16:17:58 InnoDB: Starting shutdown...
120514 16:17:59 InnoDB: Shutdown completed; log sequence number 1595675
120514 16:17:59 [Note]
120514 16:17:59 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
I searched a lot about this but could not get the solution. Any help will be apprisiated
Thanks
You need to install libaio-dev
Instructions for Debian-based distributions:
sudo apt-get install libaio-dev
By the archive file name mysql-5.5.13.tar.gz I am guessing that you have probably downloaded the source code version of MySQL database. That's why the install procedure doesn't work. To follow the instruction you need an archive containing the binary version, which should have the filename more like mysql-5.5.24-linux2.6-x86_64.tar.gz or mysql-5.5.24-linux2.6-i686.tar.gz (depending on the architecture).
Another way to recognize whether you have the correct archive or not is looking into the extracted directory. A source code version will have a lot of files and directories in it including such as INSTALL-SOURCE, configure, Makefile.am, sql, mysys, unittest, etc. A binary version carries directories like bin, sbin, libexec, etc.
do
cd scripts
./mysql_install_db.sh
paste errors if there are any
Related
I'm trying to start the mysql server using the command
sudo /etc/init.d/mysql start
but it won't start. I don't get a specific error all I see is
* Starting MySQL database server mysqld [fail]
i've tried the same command but using restart instead but same results. I've also tried to start it using
sudo service start mysql
I am stuck at this point. please let me know if I can provide anymore information.
Thank you.
Here is my mysql error.log
150505 21:43:49 [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.
150505 21:43:49 [Note] Plugin 'FEDERATED' is disabled.
150505 21:43:49 InnoDB: The InnoDB memory heap is disabled
150505 21:43:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150505 21:43:49 InnoDB: Compressed tables use zlib 1.2.8
150505 21:43:49 InnoDB: Using Linux native AIO
150505 21:43:49 InnoDB: Initializing buffer pool, size = 128.0M
150505 21:43:49 InnoDB: Completed initialization of buffer pool
150505 21:43:49 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 30152041
150505 21:43:49 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 30161741
I know this question was posted long back. But I have figured out a solution since I had the same problem. This error might occurs due to multiple installations of MySQL, in the operating system.
sudo ps -A|grep mysql
Kill the process of mysql
sudo pkill mysql
Then run the command
sudo ps -A|grep mysqld
kill process of mysqld
sudo pkill mysqld
Now you can safely restart MySQL server
sudo service mysql restart
mysql -u root -p
Hope this helps
sudo /etc/init.d/mysql start this should work.
Or else
restart server using sudo /etc/init.d/mysql restart
Still down.
run service mysql status and check script name(this will be sometimes mysqld).
then
service mysqld status
service mysqld stop
service mysqld start
When I run mysql, I get the error of ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2). mysqld gives the error of
150101 12:08:19 [Warning] Can't create test file /var/lib/mysql/lamp-update.lower-test
150101 12:08:19 [Warning] Can't create test file /var/lib/mysql/lamp-update.lower-test
150101 12:08:19 [Warning] One can only use the --user switch if running as root
150101 12:08: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.
150101 12:08:19 [Note] Plugin 'FEDERATED' is disabled.
mysqld: Can't find file: './mysql/plugin.frm' (errno: 13)
150101 12:08:19 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
150101 12:08:19 InnoDB: The InnoDB memory heap is disabled
150101 12:08:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150101 12:08:19 InnoDB: Compressed tables use zlib 1.2.8
150101 12:08:19 InnoDB: Using Linux native AIO
150101 12:08:19 InnoDB: Initializing buffer pool, size = 128.0M
150101 12:08:19 InnoDB: Completed initialization of buffer pool
150101 12:08:19 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ibdata1
InnoDB: File operation call: 'open'.
InnoDB: Cannot continue operation.
sudo mysqld gives the output of 150101 12:11:59 [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 name instead.
I am running a virtual ubuntu linux server. Mysql has worked without a problem until yesterday, when I got this error.
I have tried to set the permissions of the files in /var/lib/mysql to 660, /var/lib/mysql to 755, and its subdirectories to 700. I then ran sudo chown -R mysql:mysql /var/lib/mysql. Then, I tried rebooting my server, and running mysqld. I got the same error.
Then, I tried disabling selinux by running sudo vim /etc/selinux/semanage.conf and adding SELINUX=disabled to the file as the first line. I rebooted again, and got the same error.
This is the extent of any advice I have seen on stackexchange or other sites.
Does anyone have any ideas for what I could do?
Thank you,
Daniel
Edit:
I "solved" my problem by running mysqld as root, but this doesn't seem like a good idea security wise, so I am still looking for a better solution.
I could solve this by changing the ownership of the folder to mysql from group root (sudo chown -R mysql:root folder). Once I did this, all started to work again.
Regards
In my case SELinux was enabled and by disabling SELinux i was able to start the service
To disable SELlinux, edit
/etc/sysconfig/selinux
and set
SELINUX=disabled
Reboot and verify with command
sestatus
Folder permissions in my case are
chown -R mysql:mysql /mnt/efs/fs1/mysql
chmod -R 750 /mnt/efs/fs1/mysql
where /mnt/efs/fs1/mysql is my data directory
I also troubled with this problem.I used 'setenforce 0' this command and then mysql service successfully start.Maybe you can try it.Good luck
first, type these command below;
chown -R root:mysql /opt/lampp/var/mysql
chown -R root:mysql /opt/lampp/mysql
chmod -R 777 /opt/lampp/var/mysql
chmod -R 777 /opt/lampp/mysql
second, rerun the installer.
it worked for me.
I found many similar question on Stackoverflow but didn't get the exact error solution.
My issue is when starting MySQL service on one of the Dedicated Centos 6.5 machine, I am getting error :
141018 05:13:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
141018 5:13:47 [Warning] Can't create test file /var/lib/mysql/ip-184-168-73-83.lower-test
141018 5:13:47 [Warning] Can't create test file /var/lib/mysql/ip-184-168-73-83.lower-test
/usr/libexec/mysqld: Can't create/write to file '/tmp/ibkTWnhE' (Errcode: 28)
141018 5:13:48 InnoDB: Error: unable to create temporary file; errno: 28
141018 5:13:48 [ERROR] Plugin 'InnoDB' init function returned error.
141018 5:13:48 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
141018 5:13:48 [ERROR] Can't start server : Bind on unix socket: No space left on device
141018 5:13:48 [ERROR] Do you already have another mysqld server running on socket: /var/lib/mysql/mysql.sock ?
141018 5:13:48 [ERROR] Aborting
141018 5:13:48 [Note] /usr/libexec/mysqld: Shutdown complete
141018 05:13:48 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Here are free command status:
free -m
total used free shared buffers cached
Mem: 3743 3631 111 0 2705 21
-/+ buffers/cache: 905 2838
Swap: 2047 0 2047
This error also happens when your Database data is corrupt. You may fix this issue by moving your Db data files (ib_logfile0 and ib_logfile1) mentioned below to another location. ib_logfile0 and ib_logfile1 are system tablespace for the InnoDB infrastructure. These files contains several classes for information vital for InnoDB. You may read about these files here.
Before following below steps please keep a copy of files (ib_logfile0 and ib_logfile1) so you may restore your data in case it is lost:
Follow below steps:
Login to server via SSH with root access.
Navigate to /var/lib/mysql.
If you see files like, ib_logfile0 and ib_logfile1, rename or move them to some other folder.
Stop and start the MySQL service by running sudo service mysql stop and sudo service mysql start
These files will be recreated after you restart the server and the issue will be fixed hopefully.
Thanks
I have the same problems, this my solution:
Add more RAM to the server
Decrease the value of innodb-buffer-pool size in the config file:
sudo nano /etc/mysql/my.cnf
innodb_buffer_pool_size = 10M
After save /etc/mysql/my.cnf.
Restart mysql service:
sudo service mysql restart
exit
This is frequently occurred issue. Do following -
delete/move out these "aria_log_contro, ib_logfile0, ib_logfile1, ib_data1" files from location "..\xampp\mysql\data" and also from "..\xampp\mysql\backup".
stop and start apache server and mysql form xampp control panel
This should fix the issue; actually it worked for me.
NOTE: THIS IS GOING TO RESET THE DB IN MANY CASES BE VERY CAREFUL
Changing the values of innodb_buffer_pool_size and innodb_log_file_size didn't work for me.
Moving ib_logfile0 and ib_logfile1 files didn't help either.
What did help was:
> service mysql stop
Edit my.cfg and add innodb_force_recovery = 1
> service mysql start
> service mysql stop
Comment the innodb_force_recovery = 1 line.
> service mysql start
And voilá. (I should note that I have no idea if this involves any data loss or not)
Although late but putting answer here so that solution that helped me can help someone. I took following steps:
Added more RAM to sever
Decrease the value of innodb-buffer-pool size
Set innodb_log_file_size
Restart mysql
Example of addition to my.cnf:
innodb_buffer_pool_size = 10M
innodb_log_file_size = 1000M
After few unsuccess hours, i checked the disk space... and was full...
I was getting below mysql error log:-
[Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Using Linux native AIO
InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
InnoDB: Completed initialization of buffer pool
InnoDB: Fatal error: cannot allocate memory for the buffer pool
[ERROR] Plugin 'InnoDB' init function returned error.
[ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
[ERROR] Unknown/unsupported storage engine: InnoDB
[ERROR] Aborting
[Note] /usr/libexec/mysqld: Shutdown complete
I found out there are two solutions which are:-
1)Set innodb_log_file_size equal to the actual size of the existing InnoDB log files.
To see what size of innoDB log allocated, login mysql and enter following cmd:-
SHOW GLOBAL VARIABLES LIKE 'innodb_log_file_size';
Expected result example:- 5242880
After that, insert that value in my.cnf:-
vi /etc/my.cnf
innodb_log_file_size =5242880
2)Rename or move both the ./ib_logfile0 and ./ib_logfile1 files, and then start the MySQL server.This normally will be located at /var/lib/mysql. After start mysql, it create new innoDB log file and restore possible half-written data from the file of .ibd.
The expexted mysql log example:-
InnoDB: Database physically writes the file full: wait...
161216 9:58:54 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
161216 9:58:54 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
161216 9:58:54 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
161216 9:58:54 InnoDB: Waiting for the background threads to start
161216 9:58:55 InnoDB: 5.5.50 started; log sequence number 1589772
161216 9:58:55 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
161216 9:58:55 [Note] - '0.0.0.0' resolves to '0.0.0.0';
161216 9:58:55 [Note] Server socket created on IP: '0.0.0.0'.
161216 9:58:55 [Note] Event Scheduler: Loaded 0 events
161216 9:58:55 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.50' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi
References:-
JUSTIN KULESZA (2011). MySQL: Failed Registration of InnoDB as a Storage Engine. Available at: https://spin.atomicobject.com/2011/05/09/mysql-failed-registration-of-innodb-as-a-storage-engine/.
RolandoMySQLDBA (2014). MySQL my.cnf: innodb_log_file_size is missing. Available at: https://dba.stackexchange.com/questions/75688/mysql-my-cnf-innodb-log-file-size-is-missing/158325#158325
Changing the Number or Size of InnoDB Redo Log Files. Available at: http://dev.mysql.com/doc/refman/5.7/en/innodb-data-log-reconfiguration.html
Nothing was working with reinstalls, removes, and others (I had no data to keep, not a fix; more of a data destruction process, big caveat there):
1005 mysql_install_db
1007 /usr/bin/mysqld_safe --datadir='/var/lib/mysql
1008 /usr/bin/mysqld_safe --datadir='/var/lib/mysql' (^z)
1009 bg
1010 mysql
1011 mysql_secure_installation
1012 mysql
1013 mysql -p
And viola; actually usable database.
for me the solution was to change the config to add
innodb_use_native_aio = 0
in mysql config
Just move this log file (ib_logfile0) to some other place for safer side and start the mysql services it worked for me.
I also met the same issue when restore a backup set made via innobackupex to a new instance. Finally ,the root cause is innodb_log_file_size doesn't match original instance that take the backup, and fix steps by steps like below:
Get innodb_log_file_size value from oragin instance via below command:
mysql uroot -ppasswd -NBe "show global variables like 'innodb_log_file_size';"
Modify the /etc/my.cnf of new instance with last get value:
vim /etc/my.cnf
Restart mysqld via :
systemctl restart mysqld
Any Ideas?
Joshs-MacBook-Pro:cdwhp joshc$ mysql.server start
Starting MySQL
.. ERROR! The server quit without updating PID file (/usr/local/var/mysql/Joshs-MacBook-Pro.local.pid).
Error Logs
120927 13:08:35 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
120927 13:08:36 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
120927 13:08:36 InnoDB: The InnoDB memory heap is disabled
120927 13:08:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120927 13:08:36 InnoDB: Compressed tables use zlib 1.2.5
120927 13:08:36 InnoDB: Initializing buffer pool, size = 128.0M
120927 13:08:36 InnoDB: Completed initialization of buffer pool
120927 13:08:36 InnoDB: highest supported file format is Barracuda.
120927 13:08:36 InnoDB: Waiting for the background threads to start
120927 13:08:37 InnoDB: 1.1.8 started; log sequence number 9531786
120927 13:08:37 [ERROR] /usr/local/Cellar/mysql/5.5.27/bin/mysqld: unknown variable 'default-character-set=utf8'
120927 13:08:37 [ERROR] Aborting
120927 13:08:37 InnoDB: Starting shutdown...
120927 13:08:37 InnoDB: Shutdown completed; log sequence number 9531786
120927 13:08:37 [Note] /usr/local/Cellar/mysql/5.5.27/bin/mysqld: Shutdown complete
120927 13:08:37 mysqld_safe mysqld from pid file /usr/local/var/mysql/Joshs-MacBook-Pro.local.pid ended
Complete reinstall of mysql solved this problem in my case:
brew uninstall mysql
rm -Rf /usr/local/var/mysql
brew install mysql
mysql.server start
Note: use this as last resort, all data will be deleted
I also had the same problem. I was doing
sudo mysql.server start
What I really should have been doing was running the command as my user (not su)
mysql.server start
Hope this helps someone.
The option default-character-set was removed in MySQL 5.5.3.
You should change it in my.cnf to the alternative;
character-set-server=utf8
I hope this helps but, I was having the same issue after I accidentally left mysql server running for a few days. I was getting
ERROR! The server quit without updating PID file (/usr/local/mysql/data/[NAS].pid).
I was able to fix it by typing
sudo kill 10191 - the process number for mysql on my computer
Then started up mysql again and it worked like fine. I hope this helps someone out of the same jam.
I found the log in bogon.log
InnoDB: The first innodb_system data file 'ibdata1' did not exist. A
new tablespace will be created! 2016-03-27T14:45:36.200398Z 0 [ERROR]
InnoDB: redo log file './ib_logfile0' exists. Creating system
tablespace with existing redo log files is not recommended. Please
delete all redo log files before creating new system tablespace. `
so I delete the ib* and mysql.server restart, that's work
use
`mysql.server status;` - tells you the process number/s
`sudo kill ######;` - enter process number repeat as needed
`mysql.server start;` - start everything up again
worked for me
I had a similar issue. Somehow the files YourComputerName.pid and "YourComputerName.err" in /usr/local/mysql/data were created under _mysql user. I just removed those files and started the sql server with the following command /usr/local/mysql/support-files/mysql.server start
delete file /usr/local/var/mysql/*********.local.err
run mysql.server start
Yesterday I was working using MySQL installed on my computer.
I downloaded xampp, so I have I changed on my.cnf file the path to the socket:
/opt/lampp/var/mysql/mysql.sock
That file was just there. Today I wanted to keep working on it, and I found that file is not there anymore, so I am getting the following error while I am starting mysql server:
ERROR 2002 (HY000):
Can't connect to local MySQL server through socket
'/opt/lampp/var/mysql/mysql.sock' (2)
Here are some tests I made:
mujeresponja#ubuntu:~$ ps -fea | grep mysqld
1000 15707 15615 0 16:28 pts/1 00:00:00 grep --color=auto mysqld
mujeresponja#ubuntu:~$ ps -fea | grep mysql
1000 15709 15615 0 16:29 pts/1 00:00:00 grep --color=auto mysql
As a possible solution I uninstalled xampp and reinstall it, and also a new MySQL server, just in case. Anyway, that file is not there anymore.
EDIT
Where the mysql.sock should be, instead there are two files mysql_upgrade_info (Which contains just 5.5.8) and another binary file called ubuntu.err:
mujeresponja#ubuntu:/opt/lampp/var/mysql$ sudo cat ubuntu.err
110403 17:28:52 mysqld_safe Starting mysqld daemon with databases from /opt/lampp/var/mysql
110403 17:28:52 [Note] Plugin 'FEDERATED' is disabled.
/opt/lampp/sbin/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13)
110403 17:28:52 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use InnoDB's own implementation
InnoDB: Compressed tables use zlib 1.2.3
110403 17:28:52 InnoDB: Initializing buffer pool, size = 16.0M
110403 17:28:52 InnoDB: Completed initialization of buffer pool
110403 17:28:52 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name /opt/lampp/var/mysql/ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.
110403 17:28:52 mysqld_safe mysqld from pid file /opt/lampp/var/mysql/ubuntu.pid ended
110403 17:29:22 mysqld_safe Starting mysqld daemon with databases from /opt/lampp/var/mysql
110403 17:29:22 [Note] Plugin 'FEDERATED' is disabled.
/opt/lampp/sbin/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13)
110403 17:29:22 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use InnoDB's own implementation
InnoDB: Compressed tables use zlib 1.2.3
110403 17:29:22 InnoDB: Initializing buffer pool, size = 16.0M
110403 17:29:22 InnoDB: Completed initialization of buffer pool
110403 17:29:22 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name /opt/lampp/var/mysql/ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.
110403 17:29:22 mysqld_safe mysqld from pid file /opt/lampp/var/mysql/ubuntu.pid ended
(Sorry, I don't know how to show terminal messages in an appropiuate way)
Can anybody help me on this? Thanks in advance!
You can locate the actual socket file and create a symbolic link leading to it as follows:
# check path to socket from mysql settings
mysqladmin | grep d.sock
# create a symbolic link
ln -s path_to_mysql_socket /opt/lampp/var/mysql/mysql.sock
Although the test you did is a bit garbled, Im going to assume that the test just prove mysql isnt running.
Depending on how the mysql configured itself there should be a startup file somewhere, usually around the /etc/rc.* directories, and you would need to run the rc.mysql start (or it could be a S<nn>MySQL in an rc3.d directory for example
I didn't find a certain reason for my problem.
I just unisntalled and reinstalled, and then everything went Ok.
That is not a real solution, but it worked. Good luck
I came in the same situation when I made a grant to *.* to other user. Mysql tried to give permissions over the mysql database and that provoked the disaster: instantly, the mysql.sock file disappeared.
this happened with the version 5.6
I had the same problem with you, and I found some useful information:
2015-08-14 10:51:17 30934 [ERROR] InnoDB: Unable to lock /opt/lampp/var/mysql/ibdata1, error: 11
2015-08-14 10:51:17 30934 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
So, I rebooted the computer and restarted XAMPP, and the problem was resolved.