Windows 10 - MAMP Pro - MySQL Issue - windows

I recently installed MAMP Pro demo version on my Windows 10 and my issue is that mysql is not running, even if green light is on.
My setup:
Using multiple versions of PHP, 5.4.45 and 7.1.5.
locahost has 7.1.5
.dev domains have 5.4.45
Using default ports: 80, 443 and 3306
Issues:
I can not connect with databases on .dev domains, says Error
establishing a database connection.
I can not connect with mysql through command line, says Error 2003,
Can't connect to MySQL server on 'localhost' (10061).
I can not change MySQL password from MAMP says, can not update please
check if mysql is running. But both Apache and MySQL have green
light. But when I open XAMPP Netstat I only see that port 80 is being
used and not port 3306. PHP is also running.
Other information:
I can start Xampp MySQL with no problem while MAMP is also running.
But XAMPP can not connect to Apache.
I can open phpMyAdmin, but in Server section is only showing port number. Server: .:3306.
Before It
worked fine, but somehow I messed up and now I can not connect to mysql.
Send help!

Solution:
Uncheck "Local access only to MySQL database" under MySQL settings.

Related

Why can't Sequel Pro connect to my local XAMPP server on Catalina?

I'm trying to set up my first XAMPP server. Most recent version of XAMPP, Catalina 10.15.3. XAMPP seems to run ok, I have Apache and mySQL on. Doesn't seem to work at localhost default, but I selected the option to run at localhost:8080 and when I visit that url I see the sample site.
BUT when I try to connect with Sequel Pro using host: 127.0.0.1, username root, port 8080 it thinks for a minute (vs. instant failure with no port specified) then times out. Have restarted my computer, but no luck. Any clues?

Laravel: browse to phpmyadmin in Homestead Vagrant box

I just installed Homestead / Vagrant box for a project. I was able to set it up and now I can see the page of the Laravel project in the browser.
I am used to MAMP so the servers are there and I can just browse to http://127.0.0.1/phpmyadmin/ but how can I access it in the virtual machine? where are the settings to be made for port forwarding etc?
Since you're on MacOS you're better off using Sequel Pro. It's a free app to connect to MySQL servers.
You can connect to homestead by using the following settings:
Host: 127.0.0.1
Port: 33060
User: homestead
Pass: secret

Unable to access the database of homestead environment (laravel) through MYSQL workbench

Unable to access the homestead database through MYSQL workbench Please help me out to solve this issue
error messages at time of testing the connection - "Failed to Connect to MySQL at 127.0.0.1:33060 with user homestead Lost connection to MySQL server at 'reading initial communication packet', system error: 0"
please take a note that
Bind address in my.cnf file is 127.0.0.1 (my.cnf file located at /etc/mysql/)
hosts file contains: 127.0.0.1 localhost projectname (which is located at /etc/)
I have tried changing bind address to 0.0.0.0 but it was also not worked.
Actually I was keep trying to setup the database connectivity by just considering the homestead environment ... But on Keep searching I found one link http://www.acnenomor.com/171821p1/laravel-homestead-vagrant-box-database-problems from where I got idea and I tried once again with the data shown in attached image and it worked for me ... so I am sharing this answer in general .. it may help someone...
Please take a note that I have also tried to connect the database of Laravel homestead environment by installing all the stuffs in other system too and it was worked fine as described in the official document.. so in my case it might be the problem of some changes in configuration file of mysql or any other related environment... so please first go through the official document... http://laravel.com/docs/4.2/homestead#daily-usage
The first thing you need to do is
vagrant up
and then use these connections below for a default homestead installation.
Connection Method: Standard (TCP/IP)
Hostname: 127.0.0.1
Port: 33060
Username: homestead
Password: secret
Try the alternate IP of 192.168.10.10
hostname = 192.168.10.10
port = 3306
username = homestead
password = secret
This works for me on Windows 10 Home Version 20H2 OS Build 19042.1165 (To find this information navigate to Start, Type 'About' and click 'About your PC').
ran into a similar problem while trying to use SQLyog on my windows machine to connect to mySQL on a Homestead environment. I was able to resolve this issue by adding
skip-name-resolve
to the VMs /etc/mysql/my.conf file.
Apparently (according the mysql error logs) connections from the local machine were coming from '10.0.2.2', which caused the warning "IP Address '10.0.0.2' could not be resolved".
You will need to re-add this line every time you spin up the environment.

Postgresql refusing connection to server

I have been trying to connect to my postgresql 9.3 server but I keep getting this error.
Server doesn't listen
The server doesn't accept connections: the connection library reports
could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host "localhost" (::1) and accepting TCP/IP
connections on port 5433? could not connect to server: Connection
refused (0x0000274D/10061) Is the server running on host "localhost" (127.0.0.1)
and accepting TCP/IP connections on port 5432?
I have tried connecting through pgadmin3 and the command line.
psql.exe -h localhost -U postgres
This command also gives the same error.
I am on a windows machine. I have tried creating a separate server also with the same result.
I have no idea whats happening. Please help.
Thanks
As the error clearly tells or asks actually, Is the server running on host "localhost"?
So the chances are, the Postgres server is not running on your machine.
You can start the service(the layman way) by going to services and starting the service.
Here is how you do it:
Open Run Window by Winkey + R
Type services.msc
Search Postgres service based on the version installed.
Click stop, start or restart the service option.
Start the server with postgres -D ['data folder']
As in docs:
http://www.postgresql.org/docs/9.1/static/server-start.html
So in my Windows postgres installation from the bin folder:
postgres.exe -D ..\data
where data is in the postgresql installation folder
I had the same issue like Venkatesh had. But in my case I had installed pgadmin in version 9. But also installed version 12 at the same time.
When I now uninstalled version 9, the port was already set in the config of version 12 and not given free.
So my solution was to change the port of version 12 in the postgresql.conf file. Or even simplier, change the port in the server creation from 5432 to 5433. Now you are able to create a server again.
I got this same error. This happened when I uninstall and re-install postgress, for some reason after second-time installation, pgadmin tries to connect to the server on port 5433 whereas the server is running on 5432.
Rightclick server properties and change the port to 5432 and try to connect again. It should work now.
Your server running on port 5432 but in the properties, the port is set to 5433.
You must go to pgAdmin, click on database version, ex: PostgresSQL 10 and edit properties.
A new window appears and you need to change the port to 5432 [this is default port].
Hope this helps.

Oracle setup on Mac with VM Port Forwarding Problems

I'm facing strange issues with regards to port forwarding an oracle port (1521) from localhost (127.0.0.1) to an Oracle Linux VM (10.0.2.15) I've setup on VirtualBox on my Macbook Pro.
Below is a screenshot of the vm network setting
Below is the screenshot of port forwarding rules for the vm network setting
Telnet on the port works without any issues
Firewall is disabled both on the guest and the host
However, if I try to connect to the oracle instance using SQL Developer or IntelliJ IDE, I get an invariable "IO Error" as below
Any suggestions please?
Got it resolved by reimporting the Oracle OS on the VirtualBox
Everything seems to be working fine now.
Try to stop iptables in your db box. Just run 'sudo service iptables stop'.

Resources