From: Stephen C. <lvt...@lv...> - 2008-12-30 02:25:13
|
They are using version 4.1.25. I'm not really sure if I can run mysqladmin since the db is on a different server then Apache is. Here are the system variables from phpmyadmin. Variable Session value / Global value back log 512 basedir /usr/ binlog cache size 32,768 bulk insert buffer size 8,388,608 character set client utf8 (Global value) latin1 character set connection utf8 (Global value) latin1 character set database latin1 character set results utf8 (Global value) latin1 character set server latin1 character set system utf8 character sets dir /usr/share/mysql/charsets/ collation connection utf8_unicode_ci (Global value) latin1_swedish_ci collation database latin1_swedish_ci collation server latin1_swedish_ci concurrent insert ON connect timeout 5 datadir /var/lib/mysql/ date format %Y-%m-%d datetime format %Y-%m-%d %H:%i:%s default week format 0 delay key write ON delayed insert limit 100 delayed insert timeout 300 delayed queue size 1,000 expire logs days 0 flush OFF flush time 0 ft boolean syntax + -><()~*:""&| ft max word len 84 ft min word len 4 ft query expansion limit 20 ft stopword file (built-in) group concat max len 1,024 have archive YES have bdb NO have blackhole engine NO have compress YES have crypt YES have csv YES have example engine NO have geometry YES have innodb YES have isam YES have merge engine YES have ndbcluster DISABLED have openssl NO have query cache YES have raid YES have rtree keys YES have symlink YES init connect init file init slave innodb additional mem pool size 1,048,576 innodb autoextend increment 8 innodb buffer pool awe mem mb 0 innodb buffer pool size 8,388,608 innodb data file path ibdata1:10M:autoextend innodb data home dir innodb fast shutdown ON innodb file io threads 4 innodb file per table OFF innodb flush log at trx commit 1 innodb flush method innodb force recovery 0 innodb lock wait timeout 50 innodb locks unsafe for binlog OFF innodb log arch dir innodb log archive OFF innodb log buffer size 1,048,576 innodb log file size 5,242,880 innodb log files in group 2 innodb log group home dir ./ innodb max dirty pages pct 90 innodb max purge lag 0 innodb mirrored log groups 1 innodb open files 300 innodb table locks ON innodb thread concurrency 8 interactive timeout 28,800 join buffer size 67,104,768 key buffer size 268,435,456 key cache age threshold 300 key cache block size 1,024 key cache division limit 100 language /usr/share/mysql/english/ large files support ON lc time names en_US license GPL local infile ON locked in memory OFF log OFF log bin OFF log error log slave updates OFF log slow queries OFF log update OFF log warnings 1 long query time 10 low priority updates OFF lower case file system OFF lower case table names 0 max allowed packet 16,776,192 max binlog cache size 4,294,967,295 max binlog size 1,073,741,824 max connect errors 100,000 max connections 300 max delayed threads 20 max error count 64 max heap table size 67,107,840 max insert delayed threads 20 max join size 4,294,967,295 max length for sort data 1,024 max prepared stmt count 16,382 max relay log size 0 max seeks for key 4,294,967,295 max sort length 1,024 max tmp tables 32 max user connections 30 max write lock count 4,294,967,295 myisam data pointer size 4 myisam max extra sort file size 2,147,483,648 myisam max sort file size 2,147,483,647 myisam recover options OFF myisam repair threads 1 myisam sort buffer size 8,388,608 myisam stats method nulls_unequal ndb autoincrement prefetch sz 32 ndb force send ON ndb use exact count ON ndb use transactions ON (Global value) OFF net buffer length 16,384 net read timeout 30 net retry count 10 net write timeout 60 new OFF old passwords ON open files limit 49,462 pid file /var/run/mysqld/mysqld.pid port 3,306 preload buffer size 32,768 protocol version 10 query alloc block size 8,192 query cache limit 1,048,576 query cache min res unit 4,096 query cache size 268,435,456 query cache type ON query cache wlock invalidate OFF query prealloc size 8,192 range alloc block size 2,048 read buffer size 2,093,056 read only OFF read rnd buffer size 2,093,056 relay log purge ON relay log space limit 0 rpl recovery rank 0 secure auth OFF server id 0 skip external locking ON skip networking OFF skip show database OFF slave net timeout 3,600 slave transaction retries 0 slow launch time 2 socket /var/run/mysqld/mysqld.sock sort buffer size 3,145,720 sql mode sql notes ON sql warnings ON storage engine MyISAM sync binlog 0 sync frm ON sync replication 0 sync replication slave id 0 sync replication timeout 0 system time zone PST table cache 24,576 table type MyISAM thread cache size 50 thread stack 131,072 time format %H:%i:%s time zone SYSTEM tmp table size 67,108,864 tmpdir /tmp transaction alloc block size 8,192 transaction prealloc size 4,096 tx isolation REPEATABLE-READ version 4.1.25-Debian_mt1 version comment Source distribution version compile machine i386 version compile os pc-linux-gnu wait timeout 60 Hope this helps, Stephen Cupp "Goaltending is a normal job, Sure! How would you like it in your job if every time you made a mistake, a red light went on over your desk and fifteen thousand people stood up and yelled at you?" -Hall of Fame Goaltender Jacques Plante Bharat Mediratta wrote: > Stephen Cupp wrote: >> I tried to install G3 on my Media Temple Grid Service Hosting Service and I'm >> getting the following error when I try to install the g3 core. >> >> There was an SQL error: Specified key was too long; max key length is 1024 bytes >> - CREATE TABLE `vars` ( `id` int(9) NOT NULL auto_increment, `module_name` >> varchar(255) NOT NULL, `name` varchar(255) NOT NULL, `value` text, PRIMARY KEY >> (`id`), UNIQUE KEY(`module_name`, `name`)) ENGINE=InnoDB DEFAULT CHARSET=utf8; > > Hm. That's interesting, can you tell me what version of MySQL you're > using? "mysql --version" will help. The result of "mysqladmin -uroot > variables" would be useful too. > > My guess is that it's using multiple bytes per character in your > database, causing 2x255 char keys to turn into ~1020 bytes with some > overhead that probably pushes it over the threshold. I'm curious why I > don't see this in my development environment. > > In the meantime I've submitted r19488 which reduces some column sizes > and should fix this problem for you. > > -Bharat > > |