ERROR #2013 Lost connection to MySQL

Post your questions about Web Server usage and Apache + PHP + MySQL/SQLite web applications.

ERROR #2013 Lost connection to MySQL

Postby bezerk » Thu Jan 29, 2009 1:25 pm

JANUARY 28th 2009
Just bought a TS-509 Pro and out of the box I got:
"#2013 - Lost connection to MySQL server at 'reading initial communication packet', system error: 111"
phpMyAdmin 2.11.4
defalut password of root/admin does not work - neither did admin/root
so I did the DB maint and reset the password - did not work
so i tried to re-initialize the DB - did not work

EDIT:
I SEEMED TO HAVE SOLVED THIS BY SELECTING:
ENABLE TCP/IP NETWORKING > APPLY > "Then" selecting MAINTENANCE > RESET PASSWORD
I am now able to get into the phpMyAdmin!

Hope this helps others.
seems that if you have problems with this - also lookup "mysql remote login" which is also what helped me
TS-509 Pro (2 each) | Version 3.4.0 Build 0212T| 5x 1.5TB Seagate ST31500341AS CC1J (Raid6)
TS-509 Pro (2 each) | Version 3.4.0 Build 0212T| 5x 1TB Seagate ST31000333AS CC1H (Raid6)
TS-239 Pro (2 each) | Version 3.4.0 Build 0212T| 2x 1TB Seagate ST31000333AS CC1H
TS-119 | Version 3.4.0 Build 0212T| 1x 1.5TB Seagate ST31500341AS CC1H
TS-109 Pro II | Version 3.3.0 Build0903 | 1x 1.5TB Seagate ST31500341AS CC1G
User avatar
bezerk
Know my way around
 
Posts: 119
Joined: Mon Jan 26, 2009 4:22 pm
Location: Alaska
NAS Model: TS-419P

Re: ERROR #2013 Lost connection to MySQL

Postby mar1b0r0man » Fri Apr 24, 2009 11:06 am

Thanks bezerk,

Your solution helped me solve the exact same problem :)
NAS Model: TS-119
FW Ver: 3.0.0 (Build 0428T)
OS: WinXP SP3
No. of HDDs: 1
HDD Model: Western Digital WD10EACS
HDD Capacity: 1TB
mar1b0r0man
Starting out
 
Posts: 10
Joined: Fri Apr 17, 2009 2:30 am
NAS Model: TS-109/209 Pro II

Re: ERROR #2013 Lost connection to MySQL

Postby jondrodriguez » Tue Sep 01, 2009 10:57 pm

Effective solution on the 509 also.
Thanks!
jondrodriguez
Starting out
 
Posts: 10
Joined: Fri Oct 31, 2008 9:42 am
NAS Model: TS-109/209 Pro

Re: ERROR #2013 Lost connection to MySQL

Postby budhe888 » Mon Dec 07, 2009 2:23 pm

I have a TS-119 and am experiencing the same problem. However, unlike the other folks posting on this thread, enabling TCP/IP networking does not work for me. I get the same error, using the default root/admin username/passwd combo.

Any other thoughts would be much appreciated.

Here is my /etc/my.cnf file:
Code: Select all
[~] # cat /etc/my.cnf
# Example MySQL config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/mysql/var) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password   = your_password
port = 3306
socket      = /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port = 3306
socket      = /tmp/mysql.sock
skip-locking
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
bind-address = 192.168.1.195

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id   = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Point the following paths to different dedicated disks
#tmpdir      = /tmp/      
#log-update    = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/mysql/var/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /usr/local/mysql/var/
#innodb_log_arch_dir = /usr/local/mysql/var/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
budhe888
New here
 
Posts: 3
Joined: Mon Dec 07, 2009 2:20 pm
NAS Model: TS-109/209 Pro II

Re: ERROR #2013 Lost connection to MySQL

Postby crawler » Tue Dec 08, 2009 12:12 am

try to comment out "bind-address = 192.168.1.195"
I don' t have this line in my setting and mine work fine.
see if this will work

Also, check the config.inc.php in your phpMyAdmin folder
change 127.0.0.1 to localhost
I help my friend to setup his TS-210 that has the same problem
crawler
First post
 
Posts: 1
Joined: Tue Nov 10, 2009 5:00 pm
NAS Model: TS-101/TS-201

Re: ERROR #2013 Lost connection to MySQL

Postby budhe888 » Wed Dec 09, 2009 12:51 am

Thanks, I removed the "bind-address" line and it worked. I added that line per some other instructions I saw about how to remote login to a mysql server.
budhe888
New here
 
Posts: 3
Joined: Mon Dec 07, 2009 2:20 pm
NAS Model: TS-109/209 Pro II

Re: ERROR #2013 Lost connection to MySQL

Postby meanderingthemaze » Fri Jan 29, 2010 2:15 pm

Enabling TCP/IP under MySQL worked for me on TS-419P.
Yeah!
meanderingthemaze
Getting the hang of things
 
Posts: 77
Joined: Sat Aug 01, 2009 6:11 am
NAS Model: TS-419P

Re: ERROR #2013 Lost connection to MySQL

Postby memphix » Sat Jan 30, 2010 2:47 pm

Ahhh thank you. Reset password did the trick for my TS-410.
memphix
First post
 
Posts: 1
Joined: Sat Jan 30, 2010 2:15 pm
NAS Model: SS-839 Pro

Re: ERROR #2013 Lost connection to MySQL

Postby seanfod » Wed Mar 03, 2010 5:15 am

Also, check the config.inc.php in your phpMyAdmin folder
change 127.0.0.1 to localhost
I help my friend to setup his TS-210 that has the same problem


Thanks, this alone worked for me (TS-239 Pro)
seanfod
New here
 
Posts: 2
Joined: Tue Nov 24, 2009 11:47 pm
NAS Model: TS-239 Pro

Re: ERROR #2013 Lost connection to MySQL

Postby TheBearGren » Thu Aug 19, 2010 5:39 pm

Worked for me also (TS-100 Turbo NAS)
TheBearGren
First post
 
Posts: 1
Joined: Thu Aug 19, 2010 3:36 am
NAS Model: TS-210

Re: ERROR #2013 Lost connection to MySQL

Postby bezerk » Thu Aug 26, 2010 2:12 am

Thanks!
TS-509 Pro (2 each) | Version 3.4.0 Build 0212T| 5x 1.5TB Seagate ST31500341AS CC1J (Raid6)
TS-509 Pro (2 each) | Version 3.4.0 Build 0212T| 5x 1TB Seagate ST31000333AS CC1H (Raid6)
TS-239 Pro (2 each) | Version 3.4.0 Build 0212T| 2x 1TB Seagate ST31000333AS CC1H
TS-119 | Version 3.4.0 Build 0212T| 1x 1.5TB Seagate ST31500341AS CC1H
TS-109 Pro II | Version 3.3.0 Build0903 | 1x 1.5TB Seagate ST31500341AS CC1G
User avatar
bezerk
Know my way around
 
Posts: 119
Joined: Mon Jan 26, 2009 4:22 pm
Location: Alaska
NAS Model: TS-419P

Re: ERROR #2013 Lost connection to MySQL

Postby Stephane » Thu Sep 09, 2010 2:42 am

None of the above worked for me after the firmware update ;-(
TS-269 L - 4.0.5 1023
HDD1 : 3TB - xxx EXT4
HDD2 : 2TB - xxx EXT4
No RAID
Services enabled : SAMBA, FTP, MySQL
QPKG : Plex 0.9.8.17.2, phpMyAdmin 3.3.5, Xdove 1.3, MLDonkey 3.1.0.1
External devices - UPS APC

TS-109 3.3.2 Build0918
HDD : SAMSUNG HD103UJ 1AA0 EXT3 1 TB
No RAID
Services enabled - WebFileManager,WebServer, Xdove
External devices - None

Mac OS X 10.6.8
NAS connection speed/ MTU - 1000 Mbps, MTU: 1500 Bytes
Stephane
Know my way around
 
Posts: 101
Joined: Sun Dec 23, 2007 3:59 am
Location: France
NAS Model: TS-x69L

Re: ERROR #2013 Lost connection to MySQL

Postby bezerk » Tue Sep 14, 2010 6:09 am

have you tried refreshing your browser cache?
if that doesnt work please try mozilla vs explorer - the latest versions of explorer have had many issues.
TS-509 Pro (2 each) | Version 3.4.0 Build 0212T| 5x 1.5TB Seagate ST31500341AS CC1J (Raid6)
TS-509 Pro (2 each) | Version 3.4.0 Build 0212T| 5x 1TB Seagate ST31000333AS CC1H (Raid6)
TS-239 Pro (2 each) | Version 3.4.0 Build 0212T| 2x 1TB Seagate ST31000333AS CC1H
TS-119 | Version 3.4.0 Build 0212T| 1x 1.5TB Seagate ST31500341AS CC1H
TS-109 Pro II | Version 3.3.0 Build0903 | 1x 1.5TB Seagate ST31500341AS CC1G
User avatar
bezerk
Know my way around
 
Posts: 119
Joined: Mon Jan 26, 2009 4:22 pm
Location: Alaska
NAS Model: TS-419P

Re: ERROR #2013 Lost connection to MySQL

Postby Stephane » Wed Sep 15, 2010 7:05 pm

One of the first thing I did...

Anyway I made it work
http://forum.qnap.com/viewtopic.php?f=160&t=33342#p148844
TS-269 L - 4.0.5 1023
HDD1 : 3TB - xxx EXT4
HDD2 : 2TB - xxx EXT4
No RAID
Services enabled : SAMBA, FTP, MySQL
QPKG : Plex 0.9.8.17.2, phpMyAdmin 3.3.5, Xdove 1.3, MLDonkey 3.1.0.1
External devices - UPS APC

TS-109 3.3.2 Build0918
HDD : SAMSUNG HD103UJ 1AA0 EXT3 1 TB
No RAID
Services enabled - WebFileManager,WebServer, Xdove
External devices - None

Mac OS X 10.6.8
NAS connection speed/ MTU - 1000 Mbps, MTU: 1500 Bytes
Stephane
Know my way around
 
Posts: 101
Joined: Sun Dec 23, 2007 3:59 am
Location: France
NAS Model: TS-x69L

Re: ERROR #2013 Lost connection to MySQL

Postby witkacy26 » Sun Apr 24, 2011 10:50 am

Change 127.0.0.1 to localhost only worked for me.
witkacy26
First post
 
Posts: 1
Joined: Sun Apr 24, 2011 9:10 am
NAS Model: None

Next

Return to Web Server & Applications (Apache + PHP + MySQL / SQLite)

Who is online

Users browsing this forum: No registered users and 5 guests