Pages: 12Next
Current Page: 1 of 2
Cannot connect to mySQL
Posted by: goldwinger (---.lightspeed.hstntx.sbcglobal.net)
Date: September 04, 2013 03:47PM

I have been using mySQL with WAMP for some time now. The other day I tried to install XAMP. I went back to WAMP but now I cannot connect with my dbForge tool.

I can connect with sqlBuddy running on the WAMP server and I can connect using the console.

The error msg I get in dbForge is target machine actively refused it 127.0.0.1:3306 and the same message using localhost.

I have already put a port 3306 exception in my XP SP3 firewall.

I don't know what else to try at this point.

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: RiggsFolly (---.as13285.net)
Date: September 12, 2013 08:41PM

Installing XAMPP will lhave messed up your WAMP install.

They both install he same basic things i.e. Apache / MySQL / PHP


Make sure that you have uninstalled XAMPP completely so that there is no longer a service called 'MYSQL' Wamps MYSQL is called 'wampmysql' and will probably be getting confused with xampp's as they both use port 3306 by default.

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: goldwinger (---.lightspeed.hstntx.sbcglobal.net)
Date: September 13, 2013 12:57AM

Thanks for the response.
I realize that I messed up WAMP with XAMP(I was researching TOMCAT)
XAMP, much like WAMP can run as a program and does not have to run as a service. I was not running XAMP , as far as I know, as a service.
Plus....
I ran NetStat looking for port 3306 and who might be holding it.

I'm am not very knowledgeable about netstat, but while I see references to 3306 I don't know who to stop, delete or remove.

Here's a partial printout. Any help or suggestions would be appreciated.
Proto Local Address Foreign Address State
TCP stillbright:epmap stillbright:0 LISTENING
TCP stillbright:microsoft-ds stillbright:0 LISTENING
TCP stillbright:5800 stillbright:0 LISTENING
TCP stillbright:5900 stillbright:0 LISTENING
TCP stillbright:1026 stillbright:0 LISTENING
TCP stillbright:1041 localhost:1042 ESTABLISHED
TCP stillbright:1042 localhost:1041 ESTABLISHED
TCP stillbright:1093 localhost:1094 ESTABLISHED
TCP stillbright:1094 localhost:1093 ESTABLISHED
TCP stillbright:1913 stillbright:0 LISTENING
TCP stillbright:5152 stillbright:0 LISTENING
TCP stillbright:5354 stillbright:0 LISTENING
TCP stillbright:netbios-ssn stillbright:0 LISTENING
TCP stillbright:1034 sbserver:netbios-ssn ESTABLISHED
TCP stillbright:1036 sb2:netbios-ssn ESTABLISHED
TCP stillbright:1051 imap.perfora.net:imap ESTABLISHED
TCP stillbright:1365 oa-in-f189.1e100.net:https ESTABLISHED
TCP stillbright:1382 sb2:3306 CLOSE_WAIT
TCP stillbright:1384 oa-in-f189.1e100.net:https ESTABLISHED
TCP stillbright:1525 sb2:3306 CLOSE_WAIT

TCP stillbright:2763 ec2-54-225-154-241.compute-1.amazonaws.com:http TIME_WAIT
TCP stillbright:2765 a23-78-220-210.deploy.static.akamaitechnologies.com:http TIME_WAIT
TCP stillbright:2769 edge-star-shv-06-lax1.facebook.com:https ESTABLISHED
TCP stillbright:2856 imap.perfora.net:imap ESTABLISHED
TCP stillbright:2869 oa-in-f16.1e100.net:993 ESTABLISHED
TCP stillbright:2946 173.192.82.196-static.reverse.softlayer.com:http ESTABLISHED
TCP stillbright:3143 sb2:3306 CLOSE_WAIT
TCP stillbright:3144 sb2:3306 CLOSE_WAIT

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: RiggsFolly (---.as13285.net)
Date: September 13, 2013 01:02AM

Try this

netstat -aon | find "3306"

Using the PID from the above result do


netstat /fi "PID eq 999"

replace 999 with the PID number

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: goldwinger (---.lightspeed.hstntx.sbcglobal.net)
Date: September 13, 2013 12:54PM

Great, now I have hope.
When using natstat with the command: netstat -aon "3306", I get the following results:

C:\WINDOWS\system32>netstat -aon|find "3306"
TCP 192.168.1.64:1382 192.168.1.66:3306 CLOSE_WAIT 5376
TCP 192.168.1.64:1525 192.168.1.66:3306 CLOSE_WAIT 5376
TCP 192.168.1.64:3143 192.168.1.66:3306 CLOSE_WAIT 5376
TCP 192.168.1.64:3144 192.168.1.66:3306 CLOSE_WAIT 5376

But when I enter:
C:\WINDOWS\system32>netstat /fi "PID eq 5376"

I get:

Displays protocol statistics and current TCP/IP network connections.

NETSTAT [-a] [-b] [-e] [-n] [-o] [-p proto] [-r] [-s] [-v] [interval]

-a Displays all connections and listening ports.
-b Displays the executable involved in creating each connection or
listening port. In some cases well-known executables host
multiple independent components, and in these cases the
sequence of components involved in creating the connection
or listening port is displayed. In this case the executable
name is in [] at the bottom, on top is the component it called,
and so forth until TCP/IP was reached. Note that this option
can be time-consuming and will fail unless you have sufficient
permissions.
-e Displays Ethernet statistics. This may be combined with the -s
option.
-n Displays addresses and port numbers in numerical form.
-o Displays the owning process ID associated with each connection.
-p proto Shows connections for the protocol specified by proto; proto
may be any of: TCP, UDP, TCPv6, or UDPv6. If used with the -s
option to display per-protocol statistics, proto may be any of:
IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, or UDPv6.
-r Displays the routing table.
-s Displays per-protocol statistics. By default, statistics are
shown for IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, and UDPv6;
the -p option may be used to specify a subset of the default.
-v When used in conjunction with -b, will display sequence of
components involved in creating the connection or listening
port for all executables.
interval Redisplays selected statistics, pausing interval seconds
between each display. Press CTRL+C to stop redisplaying
statistics. If omitted, netstat will print the current
configuration information once

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: RiggsFolly (---.as13285.net)
Date: September 13, 2013 01:18PM

Sorry !!!

My mistake, typo.

Try this

netstat -aon | find "3306"


tasklist /fi "PID eq 999"

replacing 999 with the PID number from the previous command

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: goldwinger (---.lightspeed.hstntx.sbcglobal.net)
Date: September 13, 2013 02:01PM

No Problem.

OK, before when I ran netstat -aon | find "3306", I got :
TCP 192.168.1.64:1382 192.168.1.66:3306 CLOSE_WAIT 5376
TCP 192.168.1.64:1525 192.168.1.66:3306 CLOSE_WAIT 5376
TCP 192.168.1.64:3143 192.168.1.66:3306 CLOSE_WAIT 5376
TCP 192.168.1.64:3144 192.168.1.66:3306 CLOSE_WAIT 5376
But, come to find out, those results were because I had my dbForge database tool open.

After I closed it and ran the same command, I got nothing.

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: RiggsFolly (---.as13285.net)
Date: September 13, 2013 02:13PM

That would indictate that MySQL has not started!

Check this as follows

wampmanager -> MySQL -> Service
If the menu 'Start/Resume service is GREEN and clickable then MysQL has not stated.

Check the mysql error log

Also check the Windows Event Viewer for error messages from MYSQL.

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: goldwinger (---.lightspeed.hstntx.sbcglobal.net)
Date: September 13, 2013 02:20PM

WAMP was running

Log results:

2013-09-13 07:14:39 3804 [Note] Plugin 'FEDERATED' is disabled.
2013-09-13 07:14:39 3804 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-13 07:14:39 3804 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-13 07:14:39 3804 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-13 07:14:39 3804 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-13 07:14:39 3804 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-09-13 07:14:39 3804 [Note] InnoDB: Completed initialization of buffer pool
2013-09-13 07:14:39 3804 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-13 07:14:39 3804 [Note] InnoDB: 128 rollback segment(s) are active.
2013-09-13 07:14:39 3804 [Note] InnoDB: Waiting for purge to start
2013-09-13 07:14:39 3804 [Note] InnoDB: 5.6.12 started; log sequence number 1626017
2013-09-13 07:14:39 3804 [Note] Server hostname (bind-address): '*'; port: 3307
2013-09-13 07:14:39 3804 [Note] IPv6 is available.
2013-09-13 07:14:39 3804 [Note] - '::' resolves to '::';
2013-09-13 07:14:39 3804 [Note] Server socket created on IP: '::'.
2013-09-13 07:14:39 3804 [Warning] Failed to reset IPV6_V6ONLY flag (error: 10042). The server will listen to IPv6 addresses only.
2013-09-13 07:14:39 3804 [Note] Event Scheduler: Loaded 0 events
2013-09-13 07:14:39 3804 [Note] wampmysqld: ready for connections.
Version: '5.6.12-log' socket: '' port: 3307 MySQL Community Server (GPL)

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: goldwinger (---.lightspeed.hstntx.sbcglobal.net)
Date: September 13, 2013 02:54PM

Dearest Riggs,
I need to play catch up.
It was 8 days from the time this problem started and your responded. I had been trying everything I could think of to get mysql to work with dbForge. I assumed that the problem was not dbForge because it works with mySQL on my Synology web servers and because of the XAMP

During my flailing around, I change the port number, thinking it was a firewall issue.

After seeing the logs and realizing I had left the my.ini file in an abnormal state I went back and verified everything with the mySQL port set to 3306.


C:\WINDOWS\system32>netstat -aon|find "3306"
TCP 192.168.1.64:3306 23.78.220.193:80 TIME_WAIT 0
TCP [::]:3306 [::]:0 LISTENING 7676

C:\WINDOWS\system32>tasklist /fi "PID
ERROR: The search filter cannot be recognized.

C:\WINDOWS\system32>netstat -aon|find "3306"
TCP [::]:3306 [::]:0 LISTENING 7676

C:\WINDOWS\system32>tasklist /fi "PID eq 7676"

Image Name PID Session Name Session# Mem Usage
========================= ====== ================ ======== ============
mysqld.exe 7676 Console 0 442,648 K

So the issue, as I initially stated is that I can access mySQL with tools on the WAMP server or with my console, but I am being blocked from accessing it with external tools.

I have submitted a help request to the dbForge forum but only you have been kind enough to give, what is obviously a windows XP problem a go.

Thanks for your help and any advice is appreciated.

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: RiggsFolly (---.as13285.net)
Date: September 13, 2013 03:20PM

I am afraid I dont know DBForge, but I am thinking that somehow you would tell it how to find the MySQL Server that is should be accessing. Maybe Service name or Port number.

I guess this is what you need to look at within the DBForge software.

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: goldwinger (---.lightspeed.hstntx.sbcglobal.net)
Date: September 13, 2013 04:37PM

Again,
Thanks for all your input.

I do not believe the issue is with dbForge. I get the same problem with mySQL workbench from the mySQL people themselves.

The issue, I believe is port management. Even though netstat show mySQL on 3306, something is blocking it.


It was my hope that someone within the WAMP community had similar problem running queries against port 3306.

The obvious issue would be firewall, but that is not the case as far as I can tell. Although, I don't understand whats going on when you add a exe to the firewall. I did try adding an exception to the mySQL program as well as port 3306, to no avail.

It's also obvious that XAMP changed something that causes the message:
" target machine actively refused it 127.0.0.1:3306"

I just my hoped that someone had run into this issue before.

Thanks,

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: RiggsFolly (---.as13285.net)
Date: September 13, 2013 05:51PM

Install TeamViewer and I will troubleshoot for you.

Install TV, then run it.

Do this before attempting a connection.

How to Configure Team Viewer so it does not require port 80 or 443

Run TV
Extras -> Options -> Advanced -> Press the Advanced Button -> Advanced Network Connections

Check the checkbox saying [ Dont use incomming port 80 (recommended for web servers only ) ]
Stop and restart TV.

Then
Send me a Private Message containing the TV ID and PASSWORD so I can connect.
Leave TV running as it will change the password each time you restart it.

I am on UK time (GMT+1) and am normally available 09:00 - 16:00 and sometimes later into the evening.

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: goldwinger (---.lightspeed.hstntx.sbcglobal.net)
Date: September 15, 2013 09:15PM

Many Thanks to RiggsFolly,

He got on line with TV and after 15 minutes of research found that somehow I or some other program or update had configured mySQL to expect a IPV6 address instead of a IPV4. Once this was changed, mySQL was back to its old self.

People like RiggsFolly within the WAMP community is what makes WAMP the best server around.

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: eking13 (---.hsd1.fl.comcast.net)
Date: September 16, 2013 07:42PM

I had wampserver 2.4 installed under windows 7 and it was working perfectly. I then uninstalled it and reinstalled it again. Now I cannot login to phpMyAdmin with user root (no password). The error message I get is:

#1045 Cannot log in to the MySQL server.

I have tried everything I can think of, but no luck. I did notice that the MySQL service is running on port 5932, not the default 3306.

Any ideas? Thanks for your help!

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: RiggsFolly (---.as13285.net)
Date: September 16, 2013 09:08PM

If you did not manually delete the \wamp folder and all subfolders the uninstall will not have deleted the mysql database that holds users and password. So if you had set a password on the 'root' userid on your original install it will likely still be set.

Try using the password you set before.

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: eking13 (---.hsd1.fl.comcast.net)
Date: September 18, 2013 08:11PM

Thanks Riggs, but I did manually delete the c:\wamp folder and the problem still exists. Is there some way to manually set a new username and password for phpAdmin?

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: stevenmartin99 (Moderator)
Date: September 18, 2013 08:49PM

phpmyadmin cant have a username and password

it only allows you to enter one that it will pass to mysql...

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]

Options: ReplyQuote
Re: Cannot connect to mySQL
Posted by: RiggsFolly (---.as13285.net)
Date: September 19, 2013 12:03AM

In that case try username = root and password = (leave it blank)

Options: ReplyQuote
Re: Cannot connect to PhpAdmin and mySQL
Posted by: vncho (---.blackberry.net)
Date: September 19, 2013 12:05AM

I am unable to access phpmyadmin and the other alliases on my wamp interface
I keep having a message thus:
Forbidden
You don't have permission to access /phpmyadmin/ on this srver, whereas my Joomla
Projects are able to create daabasees, but then I can't write my codes; please if only you
Could help me out

Options: ReplyQuote
Pages: 12Next
Current Page: 1 of 2


Sorry, only registered users may post in this forum.