Tag Info

New answers tagged

1

# yum install --enablerepo=ius-archive php53u-mysql # yum install --enablerepo=ius-archive phpMyAdmin3 Works now on RHEL 5.5


-1

I was having the same headache error (The error is "Can't connect to MySQL Server (4)) for about 3 weeks, finally i discovered that my problem was based on a firewall rule. The solution was to ask to my hosting provider to open the port 3306 but in the OUT way. Don´t try to expect as this is the big solution, because there are many things to be considered ...


2

.. assuming the CentALT repo doesn't mysql-devel rpm, you'd need to re-install mysql-server, by un-installing the one that you already have and installing it from base before installing mysql-devel (both has to be installed from same place). yum remove mysql yum install mysql-devel


0

Your mysql version differs from the mysql-devel version you're trying to install. This is because you have installed mysql from CentALT repo according to your output. Try yum --enablerepo=CentALT install mysql-devel


1

I do not think, that this is a good idea. The mysqld process is listening to the network on some port (3306), so preventing particular system users to connect to particular port with particular mysql username could be hard. Why to give some people a mysql password, if you do not want them to login? What do you want to achieve with such setup? However, you ...


0

Create a .my.cnf in a secure location, and populate it with the following: [client] password = "somepassword" Then in your cron job call mysql like this: mysql --defaults-extra-file=/localtion/to/.my.cnf -e "CREATE..."


-1

It turned out the problem was selinux and I needed to disable it. Here's how I did it: 192.168.1.1$ nano /etc/selinux/config And then changed SELINUX=enforcing into SELINUX=disabled. Finally a reboot is in order to apply this settings.


1

If the purpose is to warm up the cache, you could also do something like: select max(concat( col1,col2 ) ) from mytable where ... The engine is forced to read the real pages to compute the max (with little overhead relative to the I/O anyway) Note that if you select only columns from an index, only the index is red, there is no need to go to the table ...


1

The key to this problem is the (13), which means "Permission Denied" (via perror). Because I can connect from the command line, the permission must be in the web app. Since I know that the credentials in the web app match the ones on the command line, the only thing left is the web server. Via an strace, I discovered SELinux was blocking it. To fix: ...


-1

It seems you are using CentALT repository. Error messages say mysql rpm from CentALT is installed; it is the source of the problem. Remove the mysql rpm and disable CentALT repository; after then, try to install mysql-devel again. Or you can temporarily disable CentALT to install mysql-devel: #remove mysql from CentALT yum remove mysql #install mysql and ...


-1

Well, you are trying to install a devel package for a previous mysql version. Package mysql-devel.x86_64 0:5.1.73-3.el6_5 will be installed Requires: mysql = 5.1.73-3.el6_5 Installed: mysql-5.5.29-1.el6.x86_64


1

Something is eating your Ram, possibly the mysql recover. Add more swap (dd if=/dev/zero count=1000 bs=1M of=swapfile; mkswap swapfile; swapon swapfile) go to singleuser mode (init 1) so that nothing else is running and start your mysql recover. Watch with top or htop for memory usage.


1

Thanks all, I found the solution: Run ls -al /var/lib/mysql, take the size of the file ib_logfile1 and run the following: /usr/sbin/mysqld -innodb_log_file_size={the previous length} -innodb_force_recovery=4 Then start mysql normally (everything should be fine now) and be sure you run the following: mysqldump --all-databases > ...


0

I fund the problem. I got an attack on the server by someone executing constantly the search function on the website. I just banned this IP and it is fine at the moment.


0

I have never experienced it, but it could look like the query broke mid transaction Try and see if you can force the transaction to continue. Try and just commit, see if that opens up. And last but not least, try and rollback and see if that could free the transaction. Thats my 5 cents. http://dev.mysql.com/doc/refman/5.6/en/innodb-recovery.html


0

Execute the following command : # rpm -qa | grep mysql It will list all installed mysql packages on your system. Eg: mysql-libs-5.1.73-3.el6_5.x86_64 now execute the command: # yum remove <name displayed in above step-1> Eg: yum remove mysql-libs-5.1.73-3.el6_5.x86_64


2

It's really something you will need to judge for yourself based on your knowledge of your environment and research into the vulerabilities of your environment. Basically you need to analyze the risk of someone capturing the network traffic on the subnet. If you feel the risk is low enough to not justify the performance hit, then don't use SSL. If you feel ...


1

This is because 2 potential heavy SELECT queries are running. The load of all threads is then summed up for the main process and may show more than 100%.


4

Like many programs the MySQL (client) can and will read credentials from file instead of relying on commandline options or reading credentials from STDIN. The recommended method is to store your credentials encrypted with the MySQL config Editor in ~/.mylogin.cnf mysql_config_editor encrypts the .mylogin.cnf file so it cannot be read as clear text, ...


2

pure-ftpd-mysql supports sha512 crypt with salt. It's as easy as: MYSQLCrypt crypt And do make sure that your Password column is long enough. For crypt $6$ it's 106 characters. So the table structure working with your query might be like this: CREATE TABLE ftpd ( User varchar(16) NOT NULL default '', status enum('0','1') NOT NULL default '0', ...


0

you can set the below in my.cnf file for standard server instances. 1.Stop MySQL service. 2.Open my.ini/my.cnf file and do the following changes innodb_buffer_pool_size = 2G innodb_log_file_size = 512M max_connections=2000 max_allowed_packet=64M wait_timeout=604800 table_cache = 4096 sort_buffer_size = 2M ...


1

Checked it by replacing "xx.xx.xx.xx" with ip address of remote mysql server and make sure database is allowed to access through your ip address. $cfg['Servers'][$i]['host'] = 'XX.XX.XX.XX';


0

The easiest solution is in the below link: http://stackoverflow.com/a/22940024/2146313 I've tried and succeeded. The solution is essentially: Create a new Parameter Group in RDS. What I changed was character_set_* and collation_*. There are about 8 settings, I changed all of them to utf8 and utf8_unicode_ci. Then assign your DB instance to use this new ...


1

It looks like you simply ran out of ram as the error suggets cannot allocate memory for the buffer pool. Your options are: Upgrade the (virtual) hardware so that it has more ram And/Or get more swap Reduce RAM usage by other application, namely apache. Your apache alone is consuming all the memory your system can afford. There is no room left for your ...


1

Because it was not yet considered GA (stable) when RHEL 7 went into feature freeze (about a year ago). If you need it, MariaDB provide their own yum repositories.


0

Getting BruteForced, or simply stuck in a connect loop, could more likely be a faulty application you installed, what was your recent installation?


1

You should never have to drop and create new events automatically. You should just make the event repeatable: Every minute, check the date and time If the hour is 23 and minute is 50 on the last day of the month, call IncidentsSummaryRecorder(); Here is that code DELIMITER $$ CREATE EVENT ISRSP ON SCHEDULE EVERY 1 MINUTE STARTS '2014-10-31 ...


0

On your server, you need to install the mysql-client package to have this binary available. # apt-get install mysql-client For Ruby, you'll need to install bindings and mysql dev lib: # apt-get install libmysql-ruby libmysqlclient-dev then, install the gem : # gem install mysql


0

This script gives a more clear output than mysqldumpslow: https://github.com/LeeKemp/mysql-slow-query-log-parser/


0

You could try running SELECT * FROM information_schema.global_variables WHERE variable_name = 'hostname'; or SHOW GLOBAL VARIABLES LIKE 'hostname'; It may or may not give you what mysqld sees from DNS.


0

Since you set strict permissions on your script file and it is stored in the root directory, nobody should read it who should not But: You could try http://www.comp.eonworks.com/scripts/obfuscate_shell_script-20011012.html or convert the bash script to a binary using SHC if the script (for which reason) should be executed by users


1

I would guess there are lots of disk-based temporary tables created for sorting and other stuff. Keep your eye on created_disk_tmp_tables MySQL variable.


0

Take pt-ioprofile and check, what mysql is reading and writing. http://www.percona.com/doc/percona-toolkit/2.1/pt-ioprofile.html


0

Always control services as root. While you can log in as root to control a service, it isn't recommended. Instead, use either: sudo /etc/init.d/mysql restart Or: su -c "/etc/init.d/mysql restart" The former requires the logged in user to be configured within sudo. This involves being a member of a certain group - the group depends on the distro. The ...


0

If you don't want REDO the complete procedure, a good fix would be to use STOP SLAVE; SET GLOBAL sql_slave_skip_counter=1; START SLAVE; If there are too many such errors, a good idea would be to automate it using a bash script. Ref: Fixing Duplicate Entry Error


0

Your problem in related with MySQL, as it's making the server run out of memory. In ubuntu, theres a script called "mysqltuner" sudo apt-get install mysqltuner. It could give you some pointers of what you need to modify in your my.cnf file.


1

Possibly http://bugs.mysql.com/bug.php?id=32158, which is the top hit for open_table_from_share If its reproducible, perhaps you should install the debuginfo package for mysql; that might make the callstack a bit clearer (although that would assume that gdb is the one creating the stack-trace, and I don't think it is)


2

From the information you gave it seems to be an issue with the user permission in which the MySQL instance is running. Try running the below command and check whether it fixes your issue: chown -R mysql:mysql /var/lib/mysql Also check whether MySQL instance is running at your machine by executing the following command: ps ax | grep mysql If it is not ...


0

I have seen this recently. I built some Exim 4.84 rpms for a friend on Amazon EC2 servers based on CentOS 6 (you don't say which version of Amazon's servers you are running). I had to reconfigure the spec file to compile and link the mysql module directly into the Exim binary, instead of making it a loadable module. I do not know why this global variable ...


2

You have to ensure that at least indices of your DBs are fit into the cache. Also it is good idea to make join and sort buffers big enough to prevent on-disk temporary tables creation. My config for 32GB RAM is looks like that: . . . . . [mysqld] . . . . . max_connections = 64 thread_cache_size = 8 thread_concurrency ...


1

Exim can't load mysql.so because it hasn't built. You have to ensure you have at least mysql-client installed properly.


1

In my case I had used yum remove mysql mysql-server. My VPS is using centos release 6.5. I simply ran cpanel upcp script: root@server [~]# /scripts/upcp It has worked for me.


2

Here is the bash script I have running on my webserver. It has served me well for some time now. It includes a part at the end to remove old backups. You can specify the number of files you would like to keep in the variables section. You have to uncomment that part of the script to get it to run. #!/bin/sh ...


0

do better debugging), try run php index.php in CLI, you'll get error right there..


0

What makes you think these spikes are strange? It could just be mysql working through queries like normal. What you'll need to do is analyse what queries are taking the longest and correlate this with the times of cpu increase. What you should start by doing is turning on slow query logging and looking over the queries that are taking the longest. Once these ...


1

You should make your programmers to fix cron queries, that they do not block mysql. That is the only one right way. If a programmer needs to process a lot data it must run it in a loop in small and fast chunks.


0

You could monitor the thread traffic from MySQL's point-of-view with two status variables Bytes_sent Bytes_received How does Replication affect these status variables ? Bytes_sent : IO Thread requesting binlog entries from the Master Bytes_received IO Thread reading binlogs entries from its Master SQL thread reading its own relay logs I have ...


0

It ends up that it was indeed a lack of storage space on the instance that hosts RDS. The error code 28 that MySQL threw was accurate. The SQL processes just kept backing up as there was no storage left. We also had a query that one site was executing that was quite inefficient - it took over one minute to execute. This query may have been propagating the ...


0

SFTPAuthorizedUserKeys, SFTPAuthorizedHostKeys and SQLNamedQuery are the parameters you are looking for, I guess. There is good explanation at the mod_sftp_sql modules documentation page: http://www.proftpd.org/docs/contrib/mod_sftp_sql.html


1

When setting up a new monitoring host (I use Nagios as well), I try to make sure that it has as little in common (as far as infrastructure goes) with the hosts to be monitored as possible. So, if you're monitoring internal servers/services in a VMware environment, then maybe set up a standalone ESXi host for your monitoring VM. If you're monitoring services ...



Top 50 recent answers are included