# Read the manual, too, if you want chroot! # Read the manual for more InnoDB related options. # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/. #binlog_ignore_db = include_database_name # note: if you are setting up a replication slave, see README.Debian about # The following can be used as easy to replay backup logs or for replication. #log_slow_queries = /var/log/mysql/mysql-slow.log # Here you can see queries with especially long duration # Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf. #general_log_file = /var/log/mysql/mysql.log ![]() ![]() # As of 5.1 you can enable the log at runtime! # Be aware that this log type is a performance killer. # Both location gets rotated by the cronjob. # This replaces the startup script and checks MyISAM tables if needed # Instead of skip-networking the default is now to listen only on # The following values assume you have at least 32M ram # Here is entries for some specific programs # Remember to edit /etc/mysql/debian.cnf when changing the socket location. # It has been reported that passwords should be enclosed with ticks/quotes # This will be passed to all mysql clients # -print-defaults to see which it would actually understand and use. # Run program with -help to get a list of available options and with # One can use all long options that the program supports. # - "~/.my.cnf" to set user-specific options. # - "/etc/mysql/my.cnf" to set global options, # The MySQL database server configuration file. Then I restarted the server: sudo service mysql restart # localhost which is more compatible and is not less secure. I commented out the line below using vim in /etc/mysql/my.cnf: # Instead of skip-networking the default is now to listen only on and you can restart your system.I am unable to connect to on my ubuntu installation a remote tcp/ip which contains a mysql installation: mysql -u user.name -p -h -P 3306ĮRROR 2003 (HY000): Can't connect to MySQL server on '' (111) Otherwise, to solve this issue permanently, open "msconfig" and uncheck that particular process from the services list and click on apply.So it is best to keep your PC in sleep-mode. Now, the issue has been solved! But might have to do the same thing again when you restart your PC.'Right-Click' and then click on "end process tree". You will be redirected to the "Processes" tab with focus on a process corresponding to that service.When you find that service, 'right-click', and then click in option. ![]() Now look for a service named "" <- filename that was diplayed in the error message in xampp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |