I installed XAMPP on Ubuntu. MySql-server fails to run properly.
I tried many solutions, as suggested by google "/opt/lampp/bin/mysql.server 264 kill no such process", but to no avail.
Username (root), database name and password in "config.inc.php" and wp-config.php are correct.
richard@HAL:/opt/lampp$ ./lampp status
Version: XAMPP for Linux 7.3.10-0
Apache is running.
MySQL is not running. <- the problem
ProFTPD is running.
===
richard@HAL:/opt/lampp$ sudo ./lampp startmysql
XAMPP: Starting MySQL...ok.
richard@HAL:/opt/lampp$ /opt/lampp/bin/mysql.server: 264: kill: No such process
===
root@HAL:/opt/lampp# service mysql stop
root@HAL:/opt/lampp# ./lampp restart
Restarting XAMPP for Linux 7.3.10-0...
XAMPP: Stopping Apache...ok.
XAMPP: Stopping MySQL...not running.
XAMPP: Stopping ProFTPD...ok.
XAMPP: Starting Apache...ok.
XAMPP: Starting MySQL...ok.
XAMPP: Starting ProFTPD...ok.
root@HAL:/opt/lampp# /opt/lampp/bin/mysql.server: 264: kill: No such process
===
This works:
root@HAL:/opt/lampp# mysql -p -u root -p
Enter password: ***
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 193
Server version: 5.7.28 MySQL Community Server (GPL)
Copyright (c) 2000, 2019, Oracle and/or its affiliates. All rights reserved.
I can also access http://localhost/phpmyadmin and see the wp1 database for my wordpress1 project (which I still need to begin due to all issues)
===
cd /var/log/mysql/ empty, no error.log (actually I deleted all in the process)
===
I tried also to stop/restart via /etc/init.d
Pressing start in ./manager-linux-x64.run shows MySQL in red after delay while trying to restart.
I applied this: chmod a-wx ./etc/my.cnf
and this:
mysql -u root -p
chmod -R 777 /opt/lampp
chown -hR nobody /opt/lampp
chmod -R 755 /opt/lampp
sudo service mysql stop
sudo /opt/lampp/lampp restart
===
sudo netstat -nap | grep :80
[sudo] password for richard:
tcp6 0 0 :::80 :::* LISTEN 18825/httpd
tcp6 0 0 2a02:1811:bc1b:7c:33792 2a00:1450:400e:80b::443
===
lsof -i :80
returns nothing
===
Please tell me which commands I need to run for extra data you may need to diagnose the problem.
Then what does this mysterious error 264 mean? BTW, I also checked similar issues with error 260, although I don't have that particular error.
How can I systematically tune in on the root cause?