zabbix server not starting

[neurovish]

The server version is 1.1.7. When I try starting the server, it doesn't load, and the only logged messages are

023922:20070514:170903 Starting zabbix_server. ZABBIX 1.1.7.
023922:20070514:170903 Executing query:select refresh_unsupported from config 
023922:20070514:170903 Query::select refresh_unsupported from config
023922:20070514:170903 Query failed:Incorrect information in file: './zabbix/config.frm' [1033]

I'm not terribly MySQL savvy, so what would be the best way to fix this?

Some additional background:
Before I started getting this error I made some changes to the innodb settings in my.cnf, increasing the max size of the data file, buffer pool, and log file. I've already tried resetting these to the old values, but that did nothing.

[neurovish]

Found more info on what happened...aka what I did wrong.

Essentially, it is somewhat explained at http://dev.mysql.com/doc/refman/5.0/...-removing.html towards the bottom where it references the proper way to change things such as the innodb log file size.

If innodb_fast_shutdown is not set to 2: You must stop the MySQL server and make sure that it shuts down without errors (to ensure that there is no information for outstanding transactions in the logs). Then copy the old log files into a safe place just in case something went wrong in the shutdown and you need them to recover the tablespace. Delete the old log files from the log file directory, edit my.cnf to change the log file configuration, and start the MySQL server again. mysqld sees that no log files exist at startup and tells you that it is creating new ones.

innodb_fast_shutdown defaults to a value of 1. http://dev.mysql.com/doc/refman/5.1/...arameters.html

The reason it wasn't starting up after I reset the values to what they were before I changed them, was that I really didn't do what I thought I did. My innodb_ log_file_size was 1M off. After changing everything back to what it really was and then following directions, everything came back. It took a couple service restarts (shutdown mysql and zabbix-server, make sure all the pids are cleared out and daemons really aren't running, then start zabbix-server) for everything to go back to normal due to the way the gentoo init scripts are written.