Few problems on new install

[bostwick]

Running with Ubuntu 9.10.

Server is up and running but with these errors. First one when it starts:

---------------------------------------------
14467 [02.03. - 15:41:46] Starting Log: logs/eqemu_error_zone.log
14467 [02.03. - 15:41:46] Unable to load titles: SELECT `id`, `skill_id`, `min_skill_value`, `max_skill_value`, `min_aa_points`, `max_aa_points`, `class`, `gender`, `char_id`, `status`, `item_id`, `prefix`,$
---------------------------------------------
14478 [02.03. - 15:41:46] Starting Log: logs/eqemu_error_zone.log
14478 [02.03. - 15:41:46] Unable to load titles: SELECT `id`, `skill_id`, `min_skill_value`, `max_skill_value`, `min_aa_points`, `max_aa_points`, `class`, `gender`, `char_id`, `status`, `item_id`, `prefix`,$
---------------------------------------------
14471 [02.03. - 15:41:46] Starting Log: logs/eqemu_error_zone.log
14471 [02.03. - 15:41:46] Unable to load titles: SELECT `id`, `skill_id`, `min_skill_value`, `max_skill_value`, `min_aa_points`, `max_aa_points`, `class`, `gender`, `char_id`, `status`, `item_id`, `prefix`,$
---------------------------------------------
14473 [02.03. - 15:41:46] Starting Log: logs/eqemu_error_zone.log
14473 [02.03. - 15:41:46] Unable to load titles: SELECT `id`, `skill_id`, `min_skill_value`, `max_skill_value`, `min_aa_points`, `max_aa_points`, `class`, `gender`, `char_id`, `status`, `item_id`, `prefix`,$
---------------------------------------------
14475 [02.03. - 15:41:46] Starting Log: logs/eqemu_error_zone.log
14475 [02.03. - 15:41:46] Unable to load titles: SELECT `id`, `skill_id`, `min_skill_value`, `max_skill_value`, `min_aa_points`, `max_aa_points`, `class`, `gender`, `char_id`, `status`, `item_id`, `prefix`,$




And we get this when anyone logs in:

Error in CheckStatus query 'SELECT `status`, UNIX_TIMESTAMP(`suspendeduntil`) as `suspendeduntil`, UNIX_TIMESTAMP() as `current` FROM `account` WHERE `id` = 0' #1054: Unknown column 'suspendeduntil' in 'field list'




Also, this is the second time we've installed, last time we could lock the server and still log in with 250 access account. This time when it's locked we can't get in with 250 access. I'm not sure if I've just missed something somewhere but I can't see why that is.