PDA

View Full Version : ERROR 1054 Unknown column


Mistmaker
09-14-2019, 03:50 AM
Just tried adding bots to my server and getting these messages on server start. Have not tested them but figured id get this resolved before I go any further with them.

Any ideas on how to resolve this?


[Status] Loading items...
[Status] Loading factions...
[Status] Loading loot...
[Status] Loading skill caps...
[Status] Loading spells...
[Status] Loading base data...
Server started - use server_status.sh to check server status
root@srv3778:/home/eqemu/server#
Akka's Linux Server Launcher
Zones to launch: 30
ERROR 1054 (42S22) at line 1: Unknown column 'death_marquee' in 'bot_owner_options'
ERROR 1054 (42S22) at line 1: Unknown column 'stats_update' in 'bot_owner_options'
ERROR 1054 (42S22) at line 2: Unknown column 'spawn_message_enabled' in 'bot_owner_options'

Mistmaker
09-14-2019, 10:53 AM
Update: Did a complete reinstall with deleting the eqemu folder. Restored my DB back and checked all was OK. Then ran check_db_update and re-ran the bot installer. Get the same errors after server start.

Guess I will continue without bots until I know more on how to fix this. :-)

Uleat
09-14-2019, 06:57 PM
You're using stable binaries, I take it?


Download the unstable binaries, then update your dll files.

Mistmaker
09-15-2019, 03:11 AM
Yes, I'm running the standard code for Linux. I don't really see a way to this through the menu as this is only a Windows option. Thanks for looking at this though and I can wait until the changes gets into the stable code and then try it.

Uleat
09-15-2019, 07:23 PM
I think linux builds fresh each time for the installer...

Not sure how the linux flavor gets its updates - anyone else?

betawolf
01-19-2020, 01:18 AM
It's been a while since this thread has been updated but in case it is still an issue, here is what I did to fix it when I updated the server code from a fairly old install and it was failing to run with the same error you were getting.

You can run this query on your db:

alter table `bot_owner_options` ADD COLUMN `death_marquee` SMALLINT(3) UNSIGNED NULL DEFAULT '0';

and that fixed it for me and I was able to get to character select and log in.

Something is causing death_marquee added by 2018_10_09_bots_owner_options.sql to be droped from the table when updating the db.

While digging, I saw there are a bunch of db and bot db updates that don't get applied (9022 and 9025) while I see the table structure is identical to the changes they apply so I guess there is some issue with the check_db_updates and check_bot_db_updates code that identifies which patches are applied but I'll check on that at a later time as it's not causing identifiable issues on the server atm.

If it's still not working for you, drop the [Database] output from a server_start_dev.sh and I'll see if I can spot what is causing issues for you.

Uleat
01-19-2020, 02:12 AM
Update 9026 changes the table altogether: https://github.com/EQEmu/Server/blob/master/utils/sql/git/bots/required/2019_09_09_bots_owner_options_rework.sql

I was adding more and more owner options and got tired of all of the hassle associated with the old way of bookkeeping.


I made a change to the requirement criteria recently that 'should' avert that problem in future updating: https://github.com/EQEmu/Server/commit/79db824a3c7c279d09520cd1d6eb5d06f12c4dd5

Let me know if it doesn't, please :)


Note: The fix for this particular issue is to run this query:
UPDATE `db_version` SET `bots_version` = '9026';

You must be seeing the 9022 and 9025 errors to use this solution.