Joomla installation prevention with a mysql warning - mysql

I seem to keep encountering an installation issue for installing Joomla on Linux. Although without Joomla I can still independently create/modify sql queries accessing mariadb with mysql -u root -p then starting lampp with sudo /opt/lampp/lampp start and website building as soon as I xdg-open /opt/lampp/htdocs, I am still unable to figure out how to by pass the Warning I keep getting when I try to install Joomla by creating that Admin account installation process.
The warning message I keep getting is: `The installer was not able to connect to the MySQL. Please make sure MySQL is running and introduce a valid password to connect to the MySQL server.
I was assuming the MYSQL was automatically running since I am able to create sql fields and input them from mariadb... and also the fact that when I run: mysqladmin -u root -p status because I still see Uptime, but I do not think that is the case.. so I am not really sure...

Related

Using HomeBrew to install MySQL

I have MySQL stable 8.0.19 (bottled) installed via mac HomeBrew:
brew install mysql
and it asks me to follow these instructions in the Caveat section:
We've installed your MySQL database without a root password. To secure it run:
mysql_secure_installation
MySQL is configured to only allow connections from localhost by default
To connect run:
mysql -uroot
To have launchd start mysql now and restart at login:
brew services start mysql
Or, if you don't want/need a background service you can just run:
mysql.server start
and when I run the mysql_secure_installation command with or without sudo I get:
Securing the MySQL server deployment.
Enter password for user root:
Now I tried looking for the default password. The MySQL installation process for macOS here shows that on the last step a temporary password is provided for the user:
[][5]
(source: [mysql.com](https://dev.mysql.com/doc/mysql-osx-excerpt/5.7/en/images/mac-installer-root-password.png))
However, I do not see any information about a temporary password within the HomeBrew terminal outputs. From here I tried:
sudo grep 'temporary password' /var/log/mysqld.log
but I get:
grep: /var/log/mysqld.log: No such file or directory
then I tried looking for that log file:
sudo find / -name mysqld.log
but I get lots of find: ... Operation not permitted instead of any meaningfull results.
I would appreciate if you could help me know
if I have done everything correctly so far,
if not what mistakes I have made and how to fix them
if yes how I can acquire the temporary password
what are the next steps
Ideally, I should be able to follow the rest of this tutorial within the GUI.
Ok, I think I had some progress. I ran
brew services list
and it showed that mysql stopped, now I ran:
brew services start mysql
now the mysql_secure_installation script ran smoothly with
Securing the MySQL server deployment.
Connecting to MySQL using a blank password.
helping me set up a password and other settings. Now you may install the MySQL Workbench (the GUI seen in the tutorial) by:
brew cask install mysqlworkbench
and you should be able to find and run MYSQLWorkbench from your /Applications/ folder!
P.S. Wrote simple instructions here.
For macOS users, there is DBngin (https://dbngin.com) that gives
you push-button start/stop for MySql, PostgreSQL (and redis) .. different
versions with non-overlapping config/data directories.
Really saves me - and my students! - in my DB course.

New MySQL Workbench Install (Will not connect to root) Ubuntu 18.04

My newly installed MySQL workbench is refusing to connect to the root of my newly installed MySQL Community Server. Whenever I attempt to access "Local Instance 3306" (the default MySQL connection) I get the following error message.
This error message does change if I open "Local Instance 3306" via the "edit connection" tab and then "test connection". I'll get a different but similar error code.
I can access the server via the command line
and can confirm that the server appears to be active also via command line.
It is a fresh install of MySQLCommunity Server and MySQL Workbench running on Ubuntu 18.04 with only one user account. I installed both the server and workbench using apt and used the guide created by DevAnswers.co here.
After installing the server and workbench I attempted to access the server using the workbench BEFORE I ran the sudo mysql_secure_installation command. I got the same two errors. I then ran the secure installation command and assigned a password which I do remember and did input into the password field of mySQL workbench albeit with the same results. I am very new to mySQL and databases and am trying to install mySQL to learn how to use SQL. I'd appreciate any help you all can provide in resolving this issue.
Additional pictures:
and .
I suspect that you just need to follow this short guide to set a root password:
https://whs-dot-hk.github.io/ubuntu-18.04/install-mysql.html
After setting a root password, you should be able to connect to mysql-workbench.
In short the root user in MySQL is authenticated using an auth socket, not a password. That's what's giving the message you're getting in the first screenshot.
(I'm assuming this is for a development project, for a production project you should keep the default config)

AWS Lightsail Bitnami LAMP - Installing 2nd Wordpress Module not working

I have a LAMP stack on my AWS Lightsail server with one wordpress application currently. I am trying to load another wordpress intall, wordpresskva, on my server (not using multisite for personal reasons). So I ran the bitnami installer with --wordpress_instance_name wordpresskva. But it fails when I get to:
Create Admin account
Please enter the MySQL password for "root" for the existing Bitnami installation
Password :
I put in the application password (bitnami_application_password in the ~ directory) but it then says:
Warning: The installer was not able to connect to the MySQL server. Please make
sure MySQL is running and introduce a valid password to connect to the MySQL
server.
Press [Enter] to continue:
This is strange, since when I enter the same password here:
$ mysql -u root -p
Enter password:
It lets me get into the mysql server. I checked the status of the server and everything seems fine, so I am really confused as to what is wrong with the password/setup I am using.
Could you please help me troubleshoot this problem?
I guess you're following the guide below:
https://docs.bitnami.com/installer/apps/wordpress/#how-to-install-several-wordpress-modules-on-the-same-stack
And I also guess you're using the WordPress module installer below:
https://downloads.bitnami.com/files/stacks/wordpress/4.9.4-2/bitnami-wordpress-4.9.4-2-module-linux-x64-installer.run
I just launched a new LAMP Server on Lightsail and run the commands:
wget https://downloads.bitnami.com/files/stacks/wordpress/4.9.4-2/bitnami-wordpress-4.9.4-2-module-linux-x64-installer.run
chmod +X bitnami-wordpress-4.9.4-2-module-linux-x64-installer.run
sudo ./bitnami-wordpress-4.9.4-2-module-linux-x64-installer.run
And I chose /opt/bitnami as installation directory:
Please choose a folder that contains an installation of Bitnami.
Select a folder []: /opt/bitnami/
Then I use the use the password obtained from bitnami_application_password when prompted for the MySQL password:
Please enter the MySQL password for "root" for the existing Bitnami installation
Password :
----------------------------------------------------------------------------
WordPress
Please configure WordPress installation
As you can check everything worked as expected. Please repeat the process and ensure you type the password correctly (with no spaces), it should work.

MySQL issue: Table 'data_dictionary.CHARACTER_SETS' doesn't exist

Recently I have updated from MySQL 5.1 to 5.5 and after few weeks the following error message was displayed each time I access the phpMyAdmin application:
1146 - Table 'data_dictionary.CHARACTER_SETS' doesn't exist
I have investigated the issue to the point where I have been forced to downgrade the MySQL service to 5.0.95 and then to upgrade the service once again to 5.1.
None of the above outlines steps however resolved the issue and the error message in questions still persist . This error disables me to access any database/table via the phpMyAdmin interface.
The error logs on the server are not providing additional information at all. The checked logs were:
-> mysql.err log
-> the cpanel error log
Any help will be highly appreciated
Run sudo mysql_upgrade -u root -p --force
Then restart mysql
i.e. sudo service mysql restart or sudo service mysqld restart depending on the version and distribution you have
You need to logout of phpMyAdmin then login for the change to take effect.
I was facing the same problem. It can be resolved by reconfiguring phpMyAdmin.
sudo dpkg-reconfigure phpmyadmin
Close phpMyAdmin page and

Cannot connect to Database server (mysql workbench)

Could you help me solve this problem ?
When I try to click "query database" under database menu in Mysql workbench. it gives me an error:
Cannot Connect to Database Server
Your connection attempt failed for user 'root' from your host to server at
127.0.0.1:3306:Can't connect to mysql server on '127.0.0.1'(10061)
Please:
Check that mysql is running on server 127.0.0.1
Check that mysql is running on port 3306 (note: 3306 is the default, but this can be changed)
Check the root has rights to connect to 127.0.0.1 from your address (mysql rights define what clients can connect to the server and from which machines)
Make sure you are both providing a password if needed and using the correct password for 127.0.0.1 connecting from the host address you're connecting from
The issue is likely due to socket authentication being enabled for the root user by default when no password is set, during the upgrade to ubuntu 16.04.
The solution is to revert back to native password authentication. You can do this by logging in to MySQL using socket authentication by doing:
sudo mysql -u root
Once logged in:
ALTER USER 'root'#'localhost' IDENTIFIED WITH mysql_native_password BY 'password';
which will revert back to the native (old default) password authentication.
Now use password as the password whenever required by MySQL.
Try opening services.msc from the start menu search box and try manually starting the MySQL service or directly write services.msc in Run box
It looks like there are a lot of causes of this error.
My Cause / Solution
In my case, the cause was that my server was configured to only accept connections from localhost. I fixed it by following this article: How Do I Enable Remote Access To MySQL Database Server?. My my.cnf file had no skip-networking line, so I just changed the line
bind-address = 127.0.0.1
to
bind-address = 0.0.0.0
This allows connections from any IP, not just 127.0.0.1.
Then, I created a MySql user that could connect from my client machine by running the following terminal commands:
# mysql -u root -p
mysql> CREATE USER 'username'#'1.2.3.4' IDENTIFIED BY 'password';
-> GRANT ALL PRIVILEGES ON *.* TO 'username'#'1.2.3.4' WITH GRANT OPTION;
-> \q
where 1.2.3.4 is the IP of the client you are trying to connect from. If you really have trouble, you can use '%' instead of '1.2.3.4' to allow the user to connect from any IP.
Other Causes
For a fairly extensive list, see Causes of Access-Denied Errors.
Did you try to determine if this is a problem with Workbench or a general connection problem? Try this:
Open a terminal
Type mysql -u root -p -h 127.0.0.1 -P 3306
If you can connect successfully you will see a mysql prompt after you type your password (type quit and Enter there to exit).
Report back how this worked.
I had a similar issue on Mac OS and I was able to fix it this way:
From the terminal, run:
mysql -u root -p -h 127.0.0.1 -P 3306
Then, I was asked to enter the password. I just pressed enter since no password was setup.
I got a message as follows:
Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL
connection id is 181. Server version: 8.0.11 Homebrew.
If you succeeded to log into mysql>, run the following command:
ALTER USER 'root'#'localhost' IDENTIFIED WITH mysql_native_password BY 'password';
You should get a message like this:
Query OK, 0 rows affected (0.19 sec)
Now, your password is "password" and your username is "root".
Happy coding :)
Run the ALTER USER command. Be sure to change password to a strong password of your choosing.
sudo mysql # Login to mysql`
Run the below command
ALTER USER 'root'#'localhost' IDENTIFIED WITH mysql_native_password BY 'password';
Now you can access it by using the new password.
Ref : https://www.digitalocean.com/community/tutorials/how-to-install-mysql-on-ubuntu-18-04
I had to start Workbench as Administrator. Apparently it didn't have the required permissions to connect to my localhost database server process.
Right-click the Workbench shortcut and select Run as Administrator. In the shortcut's Properties window, you can click on "Advanced" and tick the box next to "Run as Administrator" to always run the Workbench with Admin privileges.
The error occur because the mysql server is not starting on your computer. You should start it manually. Do following steps:
Download and install wamp server according to your bit version(32bit or 64bit) in your computer(http://wampserver-64bit.en.softonic.com/) this link allows you to download wamp server for 64bit.
As soon as you install it you can double click and run it..(you can see a icon in the right hand of the taskbar.It may be hidden .so you can click the arrow which show you the hide apps runing).So click the icon and go to Mysql
Then go to Service and there you can find Start/Resume Services click on it..
And now it is done.Open mysql workbench and see.It will work..
I had same problem with Workbench on Ubuntu, problem was with permission.
Find Workbench app
Click button Permissions
Give all permission for this app
I struggled with this problem for awhile and did several reinstalls of MySQL before discovering this.
I know that MySQL server was running OK because I could access all my DB's using the command line.
Hope this works for you.
In MySQL Workbench (5.2.47 CE)
click Mange Server Instances (bottom right corner)
click Connection
in the Connection box select:
Local Instance ($ServerName) - root#127.0.0.1:3306 '<'Standard(TCP/IP)>
click Edit Selected...
under Parameters, Hostname change localhost or 127.0.0.1 to your NetBIOS name
click Test Connection
If this works for you, great. If not change the hostname back to what it was.
Even I faced a similar error when I opened MySQL Workbench.
The solution that worked for me was:
Click on the Start button on a Windows machine
Type services and press Enter
Find MySQL and click on it
On the top side of the left panel, you will find an option as Start the service
Click on Start which is visible as a hyperlink
Forr me reason was that I tried to use newest MySQL Workbench 8.x to connect to MySQL Server 5.1 (both running on Windows Server 2012).
When I uninstalled MySQL Workbench 8.x and installed MySQL Workbench 6.3.10 it successfully connected to localhost database
For those who ignored that the initial error message displaying is the following one:
The name org.freedesktop.secrets was not provided by any .service files
Make sure to install gnome-keyring using the following
sudo apt install gnome-keyring
I tried these steps -
Step 1 : Go to Ubuntu Software Center
Step 2 : Searched for MySql Workbench
Step 3 : And Click on Permissions
Step 4 : Enable Read, add, change or remove saved passwords
Then, enter Login Password
And then, I found that my problem solved
The problem is that MySQL server is not installed.
You can get the installer from here.
Then watch this 6-minute installation tutorial.
If then creating a new connection in MySQL Workbench is not working, make sure you run that connection as root as show below:
If you don't find your .ini file, check this answer (also written below).
Enter "services.msc" on the Start menu search box.
Find MySQL service under Name column, for example, MySQL56.
Right click on MySQL service, and select Properties menu.
Look for "Path To Executable" under General tab, and there is your .ini file, for instance, "C:\Program Files (x86)\MySQL\MySQL Server 5.6\bin\mysqld.exe" --defaults-file="C:\ProgramData\MySQL\MySQL Server 5.6\my.ini" MYSQL56
I was in similar situations before and last time I found it was some Windows update issue(not sure). This time, I opened MySQL workbench and found no connection to my local database. I cannot see my tables, but yesterday I could connect to the database.
I found that my cause is that, after letting my computer sleeping for some time and wake it again, the mysql service is not running.
My solution: restart the service named "mysql" and rerun the workbench. Restarting the service takes a while, but it works.
To be up to date for upper versions and later visitors :
Currently I'm working on a win7 64bit having different tools on it including python 2.7.4 as a prerequisite for google android ...
When I upgraded from WB 6.0.8-win32 to upper versions to have 64bit performance I had some problems for example on 6.3.5-winx64 I had a bug in the details view of tables (disordered view) caused me to downgrade to 6.2.5-winx64.
As a GUI user, easy forward/backward engineering and db server relative items were working well but when we try to Database>Connect to Database we will have Not connected and will have python error if we try to execute a query however the DB server service is absolutely ran and is working well and this problem is not from the server and is from workbench. To resolve it we must use Query>Reconnect to Server to choose the DB connection explicitly and then almost everything looks good (this may be due to my multiple db connections and I couldn't find some solution to define the default db connection in workbench).
As a note : because I'm using latest Xampp version (even in linux addictively :) ), recently Xampp uses mariadb 10 instead of mysql 5.x causes the mysql file version to be 10 may cause some problems such as forward engineering of procedures which can be resolved via mysql_upgrade.exe but still when we try to check a db connection wb will inform about the wrong version however it is not critical and works well.
Conclusion : Thus sometimes db connection problems in workbench may be due to itself and not server (if you don't have other db connection relative problems).
My problem was that the MySQL server wasn't actually installed. I had run the MySQL Installer, but it didn't install the MySQL server.
I reran the installer, click "Add", and then added MySQL server to the list. Now it works fine.
In my case I have just installed MySQL Workbench but after uninstalling MySQL Workbench and installing MySQL installer and is same for both 32 and 64 bit then after it working like a charm. Hope it could be useful.
I just use:
sudo snap connect mysql-workbench-community:ssh-keys
sudo snap connect mysql-workbench-community:password-manager-service
I also struggled with this problem for quite a while.
I came accross this interesting thread from MySQL forum: http://forums.mysql.com/read.php?11,11388,11388#msg-11388
I also came accross (obviously) some good SO Q/A.
It seems that the message mentioned in "user948950" 's question can be coming from a wide range of reasons: log file too big, incorrect mysql.ini file values, spaces in the file path, security/acl issue, old entries in the registry, and so on.
So, after trying for 3h to fix this... I abandonned and decided to do a good old re-install.
This is where this post from (again) this MySQL thread came in useful, I quote:
Gary Williams wrote: Hi Guys,
I've had exactly the same problem and this is how I got it working
for me, starting with a non working installation.
Stop the windows service for any existing mysql installation.
Uninstall Mysql.
As with most uninstalls, old files are left behind. If your directory
is C:\mysql\ etc then delete the innob, etc, files but leave the
directories themselves as well as any existing databases in 'data'.
If your directory is C:\Program Files\ etc, delete all the mysql
directories.
It's now worth running regedit to make sure the old registry entries are deleted as well by the uninstall. If not, delete them.
It's ok to use the new .msi installer (essential files only), however ....
Do not use their default install path! Some genius set a path with spaces in it! Choose the custom install and select a sensible path,
ie, C:\mysql (note from Adrien: C:\mysqldata for ... the data)
Do not choose to alter the security settings. Uncheck the relevant box and the install will complete without having to set a root
password.
I think I have remembered everything.
Good luck
Gary
I did get into troubles when simply copy/pasting the databases I had in my previous "data" directory to the new one. So the work around I found was to export each database (I know... a lot of fun) and then re-import them one by one.
FYI: I used the following command to import C:/<MySQLInstallDir>/My SQL Server x.x/bin/mysql -u root -p <dbName> < "<dirPathOfDump>\<dumpName>.sql", that is for instance C:/mysql/MySQL Server 5.6/bin/mysql -u root -p mySupaCoolDb < "C:\mySupaCoolDbDump20130901.sql"
2022 and beyond this works for me:
sudo nano /etc/mysql/mysql.conf.d/mysqld.cnf
change
bind-address = 127.0.0.1
to
bind-address = 0.0.0.0
Then remember to restart mysql sudo systemctl restart mysql
Initially I was confused, but I was able to solve the problem.
If your workbench was downloaded through the Snap package manager you could easily use this command to solve the problem, very simple:
sudo snap connect mysql-workbench-community:password-manager-service :password-manager-service
Go to services.msc and find MySQL.
If "Log on As" section is 'Network Service', then:
Double click on the MySQL row to open a pop-up
go to "Log on" tab
Select Log on as: "Local System account" and check "Allow service to interact with desktop"
VoilĂ , now you can start your service on localhost and make sure you enter correct root/user password on your MySQL Workbench, and you are good to go.
If you are using snap to install mysql workbench, try this:
sudo snap connect mysql-workbench-community:password-manager-service :password-manager-service to allow sandboxed package to access password service
askubuntu.com/a/1242777/1621549
This Solution was made as a comment before by Rohim Chou