Tag Info

New answers tagged

0

Have you seen bish-bosh? It should do the job. MQTT shell script client, for bash, dash, BusyBox ash and others https://github.com/raphaelcohn/bish-bosh


1

An RPM package for Fedora 21 is now available on the official downloads page: http://dev.mysql.com/downloads/workbench


0

After wasting some time I got it working. I just had to escape the character like this: $pass = '\)d@340kgfj';


0

Try to install MariaDB-shared first. It should statisfy all dependencies normally provided by mariadb-libs.


2

There's not really any meaningful formula here; there's just arbitrary rules of thumb that get thrown around. E.g., "The perceived wisdom seems to be that for servers the ratio of Swap to RAM is lower than for PCs." Perhaps that assumes a gargantuan amount of RAM, as servers are more likely to have. But this is still mostly meaningless. It says ...


0

Check which libraries postfix requires: rpm -q --requires postfix Check which libraries that compat RPM provides: rpm -q --provides mariadb-compat # (please check the name) If compat does provide what is needed, you can delete the 5.5. libs: sudo rpm -e mariadb-libs If that gives an error of unsatisfied references, bug the MariaDB people to provide a ...


0

There are no RPMs of MySQL 5.1 for CentOS 7. Your only chance is to take the "generic tar-ball", its installation is described in the manual. At the top of my head, I see two potential points of trouble: 1) You may need to disable SElinux. 2) Some system library may have had an API change between the build platform of the binaries and CentOS 7. I have no ...


0

By deleting a whole database directory, you have made your system inconsistent: most probably, you still have references to that database in "ibdata*" and "ib_logfile*" (assuming there are InnoDB tables in that database). The error message "log sequence number is in the future" is another sign of similar inconsistencies. You might try to start your MySQL ...


0

The MYISAM storage engine isn't crash safe, there is no automatic log write plus recovery like there is for InnoDB. The least you should do is a periodic backup (daily?) to some second storage device or to some other machine, provided your setup has one.


1

Credit from: http://askubuntu.com/a/451889 Create a script to check status and start if not found: #!/bin/bash if [[ ! "$(/usr/sbin/service mysql status)" =~ "start/running" ]] then /usr/sbin/service mysql start fi Make sure script is executable: chmod +x /path/to/script Finally create a cron to run the script: sudo ...


0

I had a very similar problem when /var/lib/mysql filled /root. Have a look at http://dba.stackexchange.com/questions/91575/moved-mysql-datadir-now-server-will-not-run Use a symlink as there are so many paths buried in various configuration files it is hard to track them down.


1

As @Costas pointed out, you are using globbing patterns whereas sed uses BRE regular expressions (or ERE if using sed's -r option). Your command should resemble something like this : sed -i -r 's/-[0-9]+x[0-9]+\.jpg/.jpg/g' myfile.sql Explanation : [0-9] means "any number" (0, 1, 2, 3, 4, 5, 6, 7, 8, 9) + means "one or more of the previous atom" (The ...


0

Most systems have a locate database which is updated every night. This does a find over the whole system and stores the result in an optimized database. In this case locate mysql-connector-java should have given an answer quicker than the find solution. Note that locate will only show files that are findable by every user, so files in protected directories ...


0

find / -mount -name '*mysql-connector-java*' -print the -mount predicate is so that find skips searching virtual filesystems like /proc and /sys (useless to search) and other things that might be mounted like network-mounted filesystems (which could make it really slow!), but you can omit it if you want to search absolutely everything.


0

I used the above information and wanted to provide one more minor update that actually truncates one of the really large tables that was slowing up our backups. Hopefully this helps someone else. Using the above information I created a basic shell script named mysqlbackup.sh with the following content: #!/bin/sh find /data/var/backups/mysql/dumps -type f ...


0

I think you need to comment out these two lines in the my.ini table_cache and max_connection Hope that helps.



Top 50 recent answers are included