Description:
Could not able to access mysql server from remote machine excpet localhost.
I have checked all the credentials are working perfectly from localhost. If I access from remote machine its not connecting.
I have checked in database - access privileges are given for all remote machines '%'
Could not able replicate the issue - please reply ASAP
Below the log is just for your reference
101216 10:27:20 [Note] Event Scheduler: Purging the queue. 0 events
101216 10:27:20 InnoDB: Starting shutdown...
101216 10:27:22 InnoDB: Shutdown completed; log sequence number 136 3414268263
101216 10:27:22 [Note] /usr/local/mysql_3307/bin/mysqld: Shutdown complete
101216 10:27:22 mysqld_safe mysqld from pid file /usr/local/mysql_3307/data/gfs.pid ended
101216 10:31:53 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql_3307/data
101216 10:31:53 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
101216 10:31:53 [Note] Plugin 'FEDERATED' is disabled.
101216 10:31:54 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
101216 10:31:54 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql2b8b_13_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
101216 10:31:54 InnoDB: Started; log sequence number 136 3414268263
101216 10:31:54 [Note] Event Scheduler: Loaded 0 events
101216 10:31:54 [Note] /usr/local/mysql_3307/bin/mysqld: ready for connections.
Version: '5.1.45-enterprise-gpl-advanced' socket: '/tmp/mysql_3307.sock' port: 3307 MySQL Enterprise Server - Advanced Edition (GPL)
How to repeat:
101216 10:27:20 [Note] Event Scheduler: Purging the queue. 0 events
101216 10:27:20 InnoDB: Starting shutdown...
101216 10:27:22 InnoDB: Shutdown completed; log sequence number 136 3414268263
101216 10:27:22 [Note] /usr/local/mysql_3307/bin/mysqld: Shutdown complete
101216 10:27:22 mysqld_safe mysqld from pid file /usr/local/mysql_3307/data/gfs.pid ended
101216 10:31:53 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql_3307/data
101216 10:31:53 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
101216 10:31:53 [Note] Plugin 'FEDERATED' is disabled.
101216 10:31:54 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
101216 10:31:54 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './tmp/#sql2b8b_13_0.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
101216 10:31:54 InnoDB: Started; log sequence number 136 3414268263
101216 10:31:54 [Note] Event Scheduler: Loaded 0 events
101216 10:31:54 [Note] /usr/local/mysql_3307/bin/mysqld: ready for connections.
Version: '5.1.45-enterprise-gpl-advanced' socket: '/tmp/mysql_3307.sock' port: 3307 MySQL Enterprise Server - Advanced Edition (GPL)
