mysql remote connection refused after upgrade

T

TestUser

Verified User
Joined
Aug 26, 2011
Messages
220
Hello,
i yestrday i have upgraded mysql and from that point on i cannot connect to it via remote
what i already did
- i checked my NAT ip is set for the particular database (via DA)
- i have disabeled firewall.. iptables accept all
- i tried to open a connection via telent...
-i have tryed open port scanner.. and it is saying port is closed!?

i get connection refused...
Any help is highly apreciated in front!
 
Last edited:
locally you can connect to DB using old credentials?
your remote ip added to "access hosts" in DA panel for your DB_USER?
 
these are the settings set in options.conf
#MySQL Settings
mysql=5.7
mariadb=10.4
mysql_inst=mysql
mysql_backup=yes
mysql_backup_gzip=no
mysql_backup_dir=/usr/local/directadmin/custombuild/mysql_backups
mysql_force_compile=no
 
somewhere must be mysql log, it can be in /var/log/ or /var/lib/mysql/ or in /home/mysql/ depends on your configuration
or you must configure it path in my.cnf
 
/var/log/mysqld.log == empty
/var/lib/mysql/ no logs
/home/mysql/ dosent exist

i have enabled mysql log... i dont see any connectiong in it...
all i see is this
Code: 
2022-09-06T11:11:11.555172Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).                    
2022-09-06T11:11:11.555274Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled                                                                          
2022-09-06T11:11:11.555294Z 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.39) starting as process 7061 ...                                                                                                    
2022-09-06T11:11:11.558545Z 0 [Note] InnoDB: PUNCH HOLE support available
2022-09-06T11:11:11.558561Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-09-06T11:11:11.558564Z 0 [Note] InnoDB: Uses event mutexes
2022-09-06T11:11:11.558566Z 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2022-09-06T11:11:11.558569Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-09-06T11:11:11.558571Z 0 [Note] InnoDB: Using Linux native AIO
2022-09-06T11:11:11.558730Z 0 [Note] InnoDB: Number of pools: 1
2022-09-06T11:11:11.558797Z 0 [Note] InnoDB: Using CPU crc32 instructions
2022-09-06T11:11:11.559798Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M                                                                                       
2022-09-06T11:11:11.564740Z 0 [Note] InnoDB: Completed initialization of buffer pool
2022-09-06T11:11:11.566279Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().                                         
2022-09-06T11:11:11.577551Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2022-09-06T11:11:11.634041Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-09-06T11:11:11.634097Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...                                                                            
2022-09-06T11:11:11.674322Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-09-06T11:11:11.676205Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.                                                                                          
2022-09-06T11:11:11.676233Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2022-09-06T11:11:11.676907Z 0 [Note] InnoDB: Waiting for purge to start
2022-09-06T11:11:11.727175Z 0 [Note] InnoDB: 5.7.39 started; log sequence number 35940417489
2022-09-06T11:11:11.727602Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-09-06T11:11:11.728269Z 0 [Note] Plugin 'FEDERATED' is disabled.
2022-09-06T11:11:11.764089Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.                                                                
2022-09-06T11:11:11.764117Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.                                                                                 
2022-09-06T11:11:11.764127Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.                                                                                                 
2022-09-06T11:11:11.764136Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.                                                                                               
2022-09-06T11:11:11.765347Z 0 [Warning] CA certificate ca.pem is self signed.
2022-09-06T11:11:11.765406Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.                                                                                             
2022-09-06T11:11:11.766037Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2022-09-06T11:11:11.766062Z 0 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
2022-09-06T11:11:11.766104Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2022-09-06T11:11:11.806186Z 0 [Note] InnoDB: Buffer pool(s) load completed at 220906 13:11:11
2022-09-06T11:11:11.825001Z 0 [Note] Event Scheduler: Loaded 0 events
2022-09-06T11:11:11.825426Z 0 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
 
Last edited:
with da_admin credentials you can't connect too?
looks like mysql listen only local connections.
 
i cannot connect with anything....
even if i try to do a telnet myserver on port 3306 connection is refused
 
i dont have any firewall...
i have disabled firewall al together...
when i do
iptables -L
Code: 
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
 
Didn't the my.cnf change by accident on upgrade? Shouldn't happen.
But maybe something overruled the bind-address setting? Because if it says bind-address=127.0.0.1 somewhere in the my.cnf then it's closed too.
And I see this in the log:
Server hostname (bind-address): '127.0.0.1'; port: 3306
but I'm not sure if it also says this if bind address is set to * or % or whatever should be in there.
 
You must log in or register to reply here.
Back
Top