Basically I am having a problem with mysql. The problem is that after a period of time, lets say 6-12 hours, my plugins using mysql can no longer connect to the database. and the only way for me to give them access again is to restart my server, which is running perfectly again until the time comes again and stops the access. as my server is running all hours, this can be troubling as many of my users cannot log on and Idon't know there is a problem until I get up and try going on, also i can't be watching it all the time waiting for mysql to stop allowing access. Is there a way to stop this time out, and if so please instruct me how to do it. I am using VPN Linux shell in ubuntu, and accessing it with puTTy and Filezilla. also this is not a plugin problem, they are well known and trusted plugins that show no problems on other servers, so it must me a mysql config problem, or something else to do with mysql. Thanks for any help you can supply
Set up a cronjob to reload your server every x hours, or pastebin the mysql config and we'll have a poke
sorry i don't know how to make this so you can click on it to read it, so here it is in a post # # The MySQL database server configuration file. # # You can copy this to one of: # - "/etc/mysql/my.cnf" to set global options, # - "~/.my.cnf" to set user-specific options. # # One can use all long options that the program supports. # Run program with --help to get a list of available options and with # --print-defaults to see which it would actually understand and use. # # For explanations see # http://dev.mysql.com/doc/mysql/en/server-system-variables.html # This will be passed to all mysql clients # It has been reported that passwords should be enclosed with ticks/quotes # escpecially if they contain "#" chars... # Remember to edit /etc/mysql/debian.cnf when changing the socket location. [client] port= 3306 socket= /var/run/mysqld/mysqld.sock # Here is entries for some specific programs # The following values assume you have at least 32M ram # This was formally known as [safe_mysqld]. Both versions are currently parsed. [mysqld_safe] socket= /var/run/mysqld/mysqld.sock nice= 0 [mysqld] # # * Basic Settings # # # * IMPORTANT # If you make changes to these settings and your system uses apparmor, you may # also need to also adjust /etc/apparmor.d/usr.sbin.mysqld. # user= mysql socket= /var/run/mysqld/mysqld.sock port= 3306 basedir= /usr datadir= /var/lib/mysql tmpdir= /tmp skip-external-locking # # Instead of skip-networking the default is now to listen only on # localhost which is more compatible and is not less secure. #bind-address= 199.127.226.155 # # * Fine Tuning # key_buffer= 16M max_allowed_packet= 16M thread_stack= 192K thread_cache_size = 8 # This replaces the startup script and checks MyISAM tables if needed # the first time they are touched myisam-recover = BACKUP #max_connections = 100 #table_cache = 64 #thread_concurrency = 10 # # * Query Cache Configuration # query_cache_limit= 1M query_cache_size = 16M # # * Logging and Replication # # Both location gets rotated by the cronjob. # Be aware that this log type is a performance killer. # As of 5.1 you can enable the log at runtime! #general_log_file = /var/log/mysql/mysql.log #general_log = 1 log_error = /var/log/mysql/error.log # Here you can see queries with especially long duration #log_slow_queries= /var/log/mysql/mysql-slow.log #long_query_time = 2 #log-queries-not-using-indexes # # The following can be used as easy to replay backup logs or for replication. # note: if you are setting up a replication slave, see README.Debian about # other settings you may need to change. #server-id= 1 #log_bin= /var/log/mysql/mysql-bin.log expire_logs_days= 10 max_binlog_size = 100M #binlog_do_db= include_database_name #binlog_ignore_db= include_database_name # # * InnoDB # # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/. # Read the manual for more InnoDB related options. There are many! # # * Security Features # # Read the manual, too, if you want chroot! # chroot = /var/lib/mysql/ # # For generating SSL certificates I recommend the OpenSSL GUI "tinyca". # # ssl-ca=/etc/mysql/cacert.pem # ssl-cert=/etc/mysql/server-cert.pem # ssl-key=/etc/mysql/server-key.pem [mysqldump] quick quote-names max_allowed_packet= 16M [mysql] #no-auto-rehash# faster start of mysql but no tab completition [isamchk] key_buffer= 16M # # * IMPORTANT: Additional settings that can override those from this file! # The files must end with '.cnf', otherwise they'll be ignored. # !includedir /etc/mysql/conf.d/
I prefer offsite mysql databases, but this: #max_connections = 100 query_cache_limit= 1M query_cache_size = 16M seems suspicious to me. Using offsite the plugins configure the sql they need automatically, and connection information stays correct for me. Try www.freemysql.net or a similar service.
It's much better to put the mysql server locally, when you have your own VPN. I dont see a reason to not put it locally.
Well, its very slow compared to have it local (often low limits too) and its very easy to set it up by yourself.
i thought it was local, it is linux after all, or were u just saying not to listen to that guy saying to use those other people well i changed the max connection, well i basically deleted the number, assumed that would make it unlimited, but i still have the same problem. so this still isn't resolved.