I have a MySQL server which was starting to scrunch its data more and more slowly. Some analysis led me to blame an autoextending innodb file which had grown somewhat unkept to several GB. I wish the autoextend behaviour could be configured to grow more files rather than grow one file, but that’s another rant. I decided to clear it up which is a simple process :
I decided to create 500 data files of 100MB. When MySQL started, it ignored the config I had set in my.cnf and loaded the innodb defaults – 5MB log files and an ibdata file of 10MB which could autoextend.
It turns out that if the innodb_data_file_path line is too long then the innodb section is ignored and the defaults will prevail. I changed the plan to create 200 files of 250MB, which made for much smaller config, and the innodb settings loaded just fine.
If you want a perl one liner to generate the innodb_data_file_path, I used:
perl -e ‘$i=1; do { $padded = sprintf(“%03d”, $i); print “ibdata$padded:250M;”; $i++; } until ($i eq 200)’;
I have been trying to get a patch applied to Debian’s openssh-client packages since February which would fix a bug that prevents me from logging into Extreme switches via ssh:
trials:/usr/src/openssh-5.1p1# ssh hextreeme -l netadmin
Keyboard-interactive authentication
Enter password for netadmin:
channel 0: open failed: resource shortage: Channel open failed
The bug is described in Debian bug 495917, and it also prevents connection to some NetScreen firewalls. I have this bug with Debian 4 (openssh-client 4.3p2-9etch3) and Debian 5 (openssh-client 1:5.1p1-5).
If anyone else is experiencing the same bug and needs a quick fix, then you can download my Debian packages which replace openssh-client. You of course need to hold the packages if you don’t want them overwriting by a security fix.
By using this software you agree to hassle both the debian-ssh team and extreme to sort their stuff out!