Author Topic: MySQL error running 0.3.4 svn (Read 11534 times)

Vallaroo · « **on:** June 30, 2006, 07:52:49 pm »

When i start the bot i get the following errors:

Connected to MySQL
MySQL error (# 0) on query: ALTER TABLE admin_groups ADD description VARCHAR(80)

Duplicate column name 'description'
MySQL error (# 1) on query: ALTER TABLE admin_groups ADD short VARCHAR(5)

MySQL error (# 2) on query: ALTER IGNORE TABLE guests ADD COLUMN name VARCHAR(25
) NOT NULL AFTER id
Duplicate column name 'name'
MySQL error (# 3) on query: ALTER IGNORE TABLE guests ADD COLUMN timeadd INT NOT
NULL AFTER name
Duplicate column name 'timeadd'
MySQL error (# 4) on query: ALTER IGNORE TABLE guests ADD COLUMN addby VARCHAR(2
5) NOT NULL AFTER timeadd
Duplicate column name 'addby'

and a few:

MySQL error (# 5) on query: SELECT nickname, level, rank_name, profession, id, a
ilevel FROM members WHERE id = 790755685
Table 'polbot2.members' doesn't exist

Looking at the DB the members table doesnt exist.

I installed 0.3.4 in an empty database.

Another thing too, all commands only work in tells. How can i allow them to work in gc ?

Khalem · « **Reply #1 on:** June 30, 2006, 08:54:52 pm »

The ALTER MySQL errors can be ignored.
You can comment out those queries from the modules that call them since they are only needed to be run once.

Error #5 is likely from the Online module.
I just committed a fix for that issue to svn, so do an update.

To adjust commands access, /tell botname !commands

When running svn versions, be sure to keep an eye on http://bebot.link/index.php/topic,147.105.html for any information related to SVN being broken etc.

Vallaroo · « **Reply #2 on:** July 01, 2006, 02:08:31 pm »

Thank you for the fast response

I updated online.php as you suggested, and the previous error #5 is gone. On the other hand, i now have a new one:

MySQL error (# 5) on query: SELECT nickname, level, org_rank, profession, id, de
fender_rank_id FROM whois WHERE id = 790755685
Unknown column 'nickname' in 'field list'

Also my bot.conf files currently contain 3 SA`s, when i do a /tell mybot admin groups, all groups come up emtpy. So there are no admins/SAs on my bot atm.

Ainen · « **Reply #3 on:** July 03, 2006, 11:56:27 am »

Think of the bot.conf SA's as hardcoded backdoors. The admin groups command reads from the database and that doesn't include what was put in the conf file.

It's handy for making org non-members SA's.

Vallaroo · « **Reply #4 on:** July 03, 2006, 08:04:14 pm »

Well my bot doesnt listen to anyone, and i get "you must be superadmin..." a lot. And i AM superadmin. Btw. in 2.5 those hardcoded guild or not guild SA`s appear in the list. So there is something wrong with my installation running 0.3.4.

Ainen · « **Reply #5 on:** July 03, 2006, 11:14:54 pm »

My mistake. Mine are there. Are you sure they're in the right format? When I changed from .2.5 to .3 I didn't move my Bot.conf over because I noticed some changes to how it was laid out and stuff (don't exactly remember now), I just re-entered the information.

Code: [Select]