New answers tagged mysql
You can use: help contents to retrieve a list of the top-level help categories. If you type: help 'Data Manipulation' Possible result will be: CALL DELETE DO DUAL HANDLER INSERT INSERT DELAYED INSERT SELECT JOIN LOAD DATA LOAD XML REPLACE SELECT UNION UPDATE More info you can find: Server-Side Help HELP Syntax
You're expecting systemd to work on a version of Fedora that pre-dates the full introduction of systemd into Fedora. That came in Fedora 15. Fedora 14 had but a "feature preview" that wasn't enabled straight out of the box. Out of the box, Fedora 14 ran upstart, so you'll have to make sure that you installed an upstart job definition for mysqld and start ...
grep is not the right tool for the job for loading XML. XML is a data structure that is tag oriented, so anything line oriented (like grep) will only work for a subset. Sometimes you get away with that, but you always create code that's brittle and prone to exploding messily, when someone 'upstream' generates perfectly valid XML which doesn't work because ...
You have to use ip_conntrack netfilter module, Then you can manipulate maximum connections. You have to change value of net.ipv4.netfilter.ip_conntrack_max via sysctl
I checked. The issue was with thr firewall. Iptables was not registered as a service. So issuing a firewall command to allow from my ip worked. Command used was: iptables -I INPUT -p tcp -s xxx.xxx.xxx.xxx --dport 3306 -j ACCEPT
The mysql command is the thing that actually generates the output, so redirect its standard output (stdout). Change the second line to mysql -uUSER -p'PASSWORD' >> myfile.csv << EndOfFile using >> to append to myfile.csv, if it already exists.
If a slave server goes down, replication will stop but it won't require you to reconfigure master/slave replication. The master will simply wait for the slave to become available again at which point pending transactions will be synchronised to the slave. If you need to reboot the master server you will have to promote the slave to master. This can be ...
The gzip error message states pretty much what is going on -- the file is being written to (by MySQL in this case) during compression. Try using delaycompress (with compress); from the man page: delaycompress Postpone compression of the previous log file to the next rotation cycle. This only has effect when used in combination with compress. It ...
As far as all your services are located on the same host you really do not need any SSL encryption between services. Just restrict internal services to the localhost - that is all. In term of MySQL you have to modify my.cnf: . . . . . . [mysqld] bind-address = 127.0.0.1 port = 3306 socket = /tmp/mysql.sock . . . . . . Here you restrict ...
Alternative approach, but the one you tried is also right and should work: cat /Users/path/to/file/backup.sql | mysql -h hostname -u user -pPassword -D databasename > update.log Just in case, do you have mysql-client installed on your local machine?
You have to run that command in the machine where the file exists. Not on the MySQL Server. Alternatively copy it to the MySQL server and run.
Top 50 recent answers are included