Tag Info

New answers tagged

0

I don't think this is a memory leak. It could simply be that without large pages your memory usage hit an upper bounds (ceiling) which was why memory usage looks flat. After switching to large pages MySQL may have simply been able to better make use of the available memory. The system isn't hitting swap. I'd say closely monitor and stop flushing tables.


0

You can try to find the database configuration xml. Copied from https://www.igniterealtime.org/builds/openfire/docs/latest/documentation/db-integration-guide.html Configuration Stop Openfire. Edit conf/openfire.xml in your Openfire installation folder as described below using your favorite editor. Restart Openfire. Database Connection Settings ...


0

I used: # Generate a CA key and certificate with SHA1 digest openssl genrsa 2048 > ca-key.pem; openssl req -sha1 -new -x509 -nodes -days 3650 -key ca-key.pem > ca-cert.pem; # Create server key and certficate with SHA1 digest, sign it and convert # the RSA key from PKCS #8 (OpenSSL 1.0 and newer) to the old PKCS #1 format openssl req -sha1 -newkey ...


0

This has been somewhat useful to me: https://sourceforge.net/projects/win-mysql-bench/


0

I found my mistake. GRANT ALL ON user.* << this should be diddata. I noticed it when I went to change the database name in the question.


5

Rsyslog can group multiline log message into a single message via imfile module, however only following three read modes are supported: Line based (default) - each line is a new message. Paragraph - there is a blank line between log messages. Indented - new log messages start at the beginning of a line. If a line starts with a space it is part of the log ...


0

It's because if the DB is not on the same server as the frontend you have to do a round trip for each query (potentially more, depending on the size of the answer). It can easily take up to 1 ms to ping another server in the same datacenter. Much less if the two servers are on the same rack, but 1 ms is a good rule of thumb. That means that for ~300 small ...


2

There is a program mysqlcheck which ships with mysql that allows you to repair tables, if you can start mysql and your tables are corrupt. It doesn't sound like that's the case. There is another program myisamchk, which allows you to ensure the integrity of your MyISAM tables (you weren't using innodb for this, were you?) as long as you have the files ...


0

after shutting down mysql service (using mysqladmin -h127.0.0.1 -uroot -p shutdown) and start it again, I could not connect to that server from external clients I looked up the problem and I found this question, applied the answer, so that the problem is solved. that was because of waste DNS reverse query of mysqld.


0

It's pretty difficult to say what is the best backup strategy - it all depends on the value of your data, and the penalty you will pay if you lose last X hours. You have correctly identified a problem with incrementals - if you lose one, you lose everything after that one. Another problem is if the full gets corrupted, you have lost everything, period. ...


0

OK i resolved the issue. Culprit was setting my /etc/pw.conf umask from 022 to 007 (trying to make it a bit more secure) which resulted in creating basejail's /usr directory with 750 permissions instead of 755 so offending /usr/sbin/daemon couldn't get reached from jail. Immediately after rebooting the jail service started and works as it supposed to. I ...


-1

You'll need to add the localhost user separately. You can do it in one command (rather than two). GRANT ALL on database.* to 'user'@'localhost' identified by 'paswword'; If you want to add the user so it can connect from anywhere (less secure), use this: GRANT ALL on database.* to 'user'@'%' identified by 'password';


2

The error message indicates that you're not connecting to the remote MySQL at all, but to localhost. Make sure you connect to the remote server.


0

The error message: IOError: failed to write data generally indicates that the HTTP client communicating with your web site is dropping the connection. One would normally only see it if you are using mod_wsgi embedded mode. It is usually a transient issue and should not be a permanent issue. If it is a permanent issue and your site is no longer accepting ...


1

This is legit, as this is a user that gets created by default. It's a fairly dumb default and you should delete the user.


0

Try installing MySQL :: MySQL Workbench then connect to MySQL via socket and make sure you have network enabled. OR in other words, just make sure you don't have skip-networking inside of your my.cnf. if you don't have one, you'd need to create it.


0

I found out that due to this bug, MySQL 5.6.17 uses 6kb memory per open subpartition. This would result in about 500 GB of memory usage for 100 connections each having 100 tables with 800 partitions each, with 8 subpartitions each.


0

There are several things you can do: Check dmesg output for segmentation faults (maybe its segfaulting) Do minutely dumps of mysql and unix process lists Graph memory, disk, buffer pool usage and any other metric you can think of Use sysdig to try and catch whatever is going wrong


0

I am not a mysql expert but there is script which can help you or suggest some tuning fix http://mysqltuner.com/ The longer the system is running much better recommendation you will get.As recommended please use this script in your test environment before using it in PRD.


1

It sounds to me like something in your paths is incorrect. The reason most of the posts you find being about "open" are because most of the time it's a permissions issue, but the paths are correct. When you see errors about "create" it's because (generally) the path that my.conf is telling the service to find the files does not contain them. Find any of ...


0

You need to look in /var/log/apache2/error_log (or wherever your apache error log is configured to go) It will tell you in there what the actual problem is. A problem which arises over time, and is solved by an apache and/or mysql restart could be something memory/resource related. I guess memory is the most obvious, but that's speculation.


0

Completely agree with Grant,Swap utilization is not always a performance issue but if Database is swapping you will see a performance issue but it all depend on the situation.Next time when your system is swapping can you please run this script to find out which process is swapping http://northernmost.org/blog/find-out-what-is-using-your-swap/ ...


0

The answer to this is that the debian-sys-maint account is a red-herring. The phenomena I was looking at was a MySQL "anonymous" user. This is answered by these 2 questions, as well as my own that I posted yesterday: MySQL allows entry without Password MySQL 5.5.16 allows anonymous connections Default user for MySQL


0

I found an answer to my own question. The problem was that the domain name was in mydestination, which made the emails sent through the domain to go through local_recipients_maps. Removing the domain solved the problem. I don't know if that's the best practice or overriding local_recipients_maps to use mysql is. If anyone has an answer to that please write ...


1

MySQL treats unknown username as anonymous user, so check for any lines in user-table that have empty string in the username column. Removing these, or setting the password, will prevent logging in without password. You can check if you are connected as anonymous user with SELECT CURRENT_USER().


1

I addressed an issue in the DBA StackExchange about the kernel and journaling. I learned this from Percona back in May that a certain flush behavior is actually simulated. You may have to change how journaling is done. You may have to tune InnoDB Loosening ACID compliance for write performance (setting innodb_flush_log_at_trx_commit to 0 or 2) Larger ...


2

cat /usr/lib/systemd/system/mysqld.service # For example, if you want to increase mysql's open-files-limit to 10000, # you need to increase systemd's LimitNOFILE setting, so create a file named # "/etc/systemd/system/mysqld.service.d/limits.conf" containing: # [Service] # LimitNOFILE=10000


5

You don't mention any performance problems, just that it is using swap. This is completely normal. If there are things in RAM that are being used very infrequently, the kernel will swap them out to make more room for caches that are being used frequently. This can be adjusted with the vm.swappiness kernel parameter, but generally it works well the way it ...


0

File corruption comes in many flavors or situations....I think you are right concerning possible disk corruption....if this is true, you should IMMEDIATELY restart your system, and force a full fsck so as to hopefully repair the damage to make a backup. Leaving things the way they are may cause other more serious damage to your disk. I'd also be checking ...


0

Yes, it is. Just use 0.0.0.0 for a binding address in your MySQL configuration file (e.g. /etc/mysql/my.cnf) as follows: bind-address = 0.0.0.0 If the address is 0.0.0.0, the server accepts TCP/IP connections on all server host IPv4 interfaces. Furthermore if the address is ::, the server accepts TCP/IP connections on all server host IPv4 and IPv6 ...


0

In /var/lib/mysql/mysql there is a file named general_log.csv created by default. You can also use this file to specify (e.g log=/var/lib/mysql/mysql/general_log.csv)


0

Yes, you could use sa_username_maps to split it up.


1

Here is the [mysqld] section of your my.cnf without comments and blank lines [mysqld] user = mysql pid-file = /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port = 3306 basedir = /usr datadir = /var/lib/mysql tmpdir = /tmp lc-messages-dir = /usr/share/mysql skip-external-locking bind-address = ...


2

You should use mysqladmin drop blah -f -uroot -pbleble. Look at the docs: --force, -f Do not ask for confirmation for the drop db_name command. With multiple commands, continue even if an error occurs.


0

I know you didn't ask for DB related things, but I still have to mention this. Your tables should use InnoDB as the engine. The problem with MyISAM is that it has only table-level locking. That is, if you insert data to the table, the whole table is locked, and other queries have to wait for the operation to finish before they can proceed. With InnoDB, the ...


0

First, having this query to run on only one CPU is normal. Your problem is likely that the database will be occupied with INSERTing your data into the tables and doesn't have time or I/O capacity left to handle SELECT queries to display your site. One approach you can try is to break down the import data as much as possible and use INSERT LOW PRIORITY or ...


1

You need to be aware of what the InnoDB Buffer Pool breakdown is from the status variables Please run the following query select var,concat(numunit,' ',unit) size from ( select var,format(num/power(1024,ex),2) numunit,SUBSTR(units,ex*2+1,2) unit from ( select var,num,FLOOR(LOG(IF(num=0,1,num))/LOG(1024)) ex from ( ...


-1

Best method is to take a average request time for your site page, divide second from that and multiply by number of cores. Let's say your site loads in 0.2s and you have 4 cores. So there is a good chance, that you will be able to serve 20 pages/s. But it's a lie called statistics and everything may go boom, if you users will like hitting a one page, that ...


1

Use something like JMeter to load test it. It is impossible to predict scaling with any accuracy because the bottlenecks you hit will depend on your individual implentation of both website and hardware.


0

Typing SHOW GRANTS FOR 'root'@'localhost'; showed me some obscured password, so I logged into mysql of that system using HeidiSQL on another system (using root as the username and the corresponding password) and typed GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED BY 'thepassword' WITH GRANT OPTION; and it worked when I went back to the ...


6

If I understand correctly what you want to achieve, you can try it with the \G separator (instead of semicolon), like this: echo 'SELECT * FROM mytable\G' | mysql -u myuser -p mypassword mydb Example output: *************************** 1. row *************************** id: 1 locale: de name: Afghanistan *************************** 2. row ...


3

As recommended in sysadmin1138's answer, these kind of situations are why VPCs were added to Amazon Web Services: so you can have a private intranet between EC2 instances. In my opinion, that's part one of the solution: put your database server in a VPC with your application server and only allow access to the database server from the internal ...


2

include(../scripts/connect.php) Your script is using a relative directory. These are linked to the current working directory. When cron is running your CWD is almost certainly not what you think it is. Either set the CWD in your cron script, or update your PHP code to use use a path relative to themselves. Something like ...


6

Using a VPC will solve a lot of your problems, as private IP addresses will be static there. Amazon is strongly encouraging people to move to VPC for reasons like this. Once you have one, your two systems should be able to talk over the AWS-internal network. To answer your question about exposure along the aws-public <---> aws-public route, it is ...


0

Instead of using the Sequel to create the tunnel, what is you create the tunnel yourself ? ssh -Cc blowfish -Nf -vv -L3306:localhost:3306 sshuser@domain Then connect with Sequel to 127.0.0.1:3306 Can you connect ? Does anything appear on your terminal (or ssh client logs)?


1

It turns out ufw disable doesn't actually turn iptables rules off. I had this line in my iptables: REJECT all -- anywhere anywhere reject-with icmp-host-prohibited and this prevented the appended ACCEPT lines to be ignored. I added the iptables -I INPUT -i eth0 -p tcp -m tcp --dport 3306 -j ACCEPT line with -I instead of -A ...


0

Ultimately, it is not a curl_setopt issue. It was just an error caused by a PHP configuration file (wordpress.stackexchange.com answer).


3

Capistrano is setup to use the production environment, but whatever command/script/etc you are using to actually start the Rails app on the box is likely in development mode. export RAILS_ENV=production bin/rails s


1

If you're using micro or small instances, mysql database running websites can can put a pretty big load on your VMs memory which will end up constantly crashing your mysql server. Consider using RDS which might be more expensive or at least ec2 t2.medium to save money and still run fine. For IPs, you'd have to allocate your instance elastic IP which will ...


1

First, you have to backup your databases: cp -r /var/lib/mysql /tmp/mysql_backup Then, remove the file from /var/lib/mysql. rm -rf ibdata1 Now restart the mysql server. /etc/init.d/mysqld start



Top 50 recent answers are included