View Full Version : Problems after upgrading from June to current release
gnode
02-11-2009, 12:59 AM
I upgraded from the june build to the Sep 2 build tonight.
I have the following problems:
1. Disciplines no longer work, but all other spells do.
2. PEQZONE no longer works, but I have the status for it set to 0. When I #peqzone, it says command not recognized.
Any idea?
trevius
02-11-2009, 02:03 AM
Maybe you don't have all of the required SQL changes in. Also, why would you use the Sep 2 build? You should be using the SVN revisions found here:
http://code.google.com/p/projecteqemu/
There are hundreds of changes and updates in the SVN since that Sep 2 build, so it would be best to use it instead. Make sure you run the SQL updates in the /utils/sql/svn directory though.
I believe there was some changes to #peqzone in there at some point, but it should be working on the latest revisions from the SVN.
gnode
02-11-2009, 12:43 PM
Sep 2 is just the latest one here:
http://www.eqemulator.net/download.php
So that is what I used. I will try the other stuff tonight I guess.
cavedude
02-11-2009, 01:04 PM
Yep, the full version of #peqzone as used on TGC is only available on SVN. It is not in the ancient builds on the EQEmu page.
gnode
02-11-2009, 11:47 PM
First thing first. I want to thank you all for all the effort you have put into this project. After reading through the changelog, I see just how much work you have put into this and I appreciate it.
Ok I reviewed the changelog and went through and did all sql updates I saw in the changelog and all that were referenced by the changelog that are on the SVN.
I fixed my perl (got the dll error and used search function :))
When I tried to start the server, I get a ton of errors and a message in the log of:
If you got boat loads of errors, make sure you sourced: utils/items-0.6.0-DR2-0.6.1-DR1-convert.sql
I pulled that script from the SVN and ran it. The script itself gave a boatload of errors. Mainly like this:
Unknown column 'unknown021' in 'items'
It looks like it is trying to update the items table from a version other than the one I have. I suspect I may be missing some earlier changes that this script relies on.
Here is the error I got that prompted the mentioning of that SQL script:
[02.11. - 21:25:53] Starting Log: logs/eqemu_error_world_10016.log
[02.11. - 21:25:53] DBLoadItems query 'select source,itemclass,name,lore,idfile,id,weight,norent ,nodrop,size,slots,price,icon,UNK012,UNK013,benefi tflag,tradeskills,cr,dr,pr,mr,fr,astr,asta,aagi,ad ex,acha,aint,awis,hp,mana,ac,deity,skillmodvalue,U NK033,skillmodtype,banedmgrace,banedmgamt,banedmgb ody,magic,casttime_,reqlevel,bardtype,bardvalue,li ght,delay,reclevel,recskill,elemdmgtype,elemdmgamt ,range,damage,color,classes,races,UNK054,maxcharge s,itemtype,material,sellrate,UNK059,casttime,UNK06 1,procrate,combateffects,shielding,stunresist,stri kethrough,extradmgskill,extradmgamt,spellshield,av oidance,accuracy,charmfileid,factionmod1,factionmo d2,factionmod3,factionmod4,factionamt1,factionamt2 ,factionamt3,factionamt4,charmfile,augtype,augslot 1type,augslot1visible,augslot2type,augslot2visible ,augslot3type,augslot3visible,augslot4type,augslot 4visible,augslot5type,augslot5visible,ldontheme,ld onprice,ldonsold,bagtype,bagslots,bagsize,bagwr,bo ok,booktype,filename,banedmgraceamt,augrestrict,lo regroup,pendingloreflag,artifactflag,summonedflag, favor,fvnodrop,endur,dotshielding,attack,regen,man aregen,enduranceregen,haste,damageshield,recastdel ay,recasttype,guildfavor,augdistiller,UNK123,UNK12 4,attuneable,nopet,UNK127,pointtype,potionbelt,pot ionbeltslots,stacksize,notransfer,stackable,UNK134 ,clickeffect,clicktype,clicklevel,clicklevel2,proc effect,proctype,proclevel,proclevel2,worneffect,wo rntype,wornlevel,wornlevel2,focuseffect,focustype, focuslevel,focuslevel2,scrolleffect,scrolltype,scr olllevel,scrolllevel2,updated from items order by id', #1054: Unknown column 'augslot1visible' in 'field list'
This is preventing zone.exe from loading. Also, if this helps, these errors are what happen when a character gets to char select:
[02.11. - 21:26:24] Warning: acctid 1158 has an invalid item_id 30088 in inventory slot 2500
[02.11. - 21:26:24] Warning: acctid 1158 has an invalid item_id 30096 in inventory slot 2501
[02.11. - 21:26:48] Warning: acctid 860 has an invalid item_id 17005 in inventory slot 2500
[02.11. - 21:26:48] Warning: acctid 860 has an invalid item_id 17005 in inventory slot 2501
[02.11. - 21:26:48] Warning: acctid 860 has an invalid item_id 17005 in inventory slot 2500
[02.11. - 21:26:48] Warning: acctid 860 has an invalid item_id 17005 in inventory slot 2501
[02.11. - 21:29:10] Warning: acctid 329 has an invalid item_id 17970 in inventory slot 2500
[02.11. - 21:29:10] Warning: acctid 329 has an invalid item_id 17969 in inventory slot 2501
Andrew80k
02-11-2009, 11:55 PM
You haven't applied all the updates. This one is in 292_augslots.sql in the svn. You may have appled them and then overwrote them with a database or something.
gnode
02-12-2009, 12:44 AM
I only applied SQL explicitly mentioned in the changelog. Should I apply everything in this section?:
http://code.google.com/p/projecteqemu/source/browse/?r=313#svn/branches/DB_LoadSPDat/utils/sql/svn
gnode
02-12-2009, 12:50 AM
So I tried what you suggested, then also re-ran the item update, and still get a ton of errors. I must be missing a lot of fields. How do I know what SQL updates to do?? I have done all of them referenced in the change log, but apparently that is not comprehensive.
Andrew80k
02-12-2009, 01:23 AM
You've probably already backed up your database...I hope. The thing to do would be to restore your database. Then begin applying the changes that you see in the changelog but make sure you compare the changelog with the files in the utils/sql/svn directory so that you don't duplicate columns. You don't want to update something twice. I would go through the changelog, compare the changelog entry to the sql directory to see if there is a related change. Import that sql file or if there is no sql file, use the entry in the changelog. Sometimes if the change was pretty small it seems like an sql file didn't get created and just the entry in the changelog was made. Sometimes a reference in the changelog will point you to a sql file. Keep in mind there are a number of people making changes, and while I think they try to be consistent it doesn't always happen. Since you have a custom database it is going to be a little harder for you to get up to date and kind of painful. It will be well worth it. Any changes I make I keep in a custom.sql file that I can basically just import after I have made a database update. It's much easier that way. But that's harder to accomplish if you didn't do it from the start and don't remember all your customizations. Good luck. Let us know if we can help somehow.
gnode
02-12-2009, 11:04 AM
It is only custom for itemization/spawns/npcs. I am doing all of this on a test/mirror server.
What you just suggested I do I have now done 3 times. Every single SQL reference in the changelog since my original install (a late june build) is in my update script. I also have included every single reference SQL file. Something is missing from the changelog, but I have no idea what.
gnode
02-12-2009, 07:26 PM
Is there perhaps a master schema somewhere? I could just compare my DB to it and correct errors as I see them.
Andrew80k
02-12-2009, 07:29 PM
I do think there is a schema in the Wiki, but I don't know how current it is. One thing you could do is just download a peq database from the CVS, load it into a different DB and then compare the 2. That might be faster than anything else.
gnode
02-12-2009, 07:33 PM
Got a link? I originally installed peq off the distro from their website, but based on the filename at least (have not downloaded a 2nd time) it appears to be the same version I am still on, 1110
cavedude
02-12-2009, 09:47 PM
Use the PEQ CVS. It is up to date.
gnode
02-12-2009, 10:15 PM
Use the PEQ CVS. It is up to date.
Ok I got your db downloaded and tried to import it to a new fresh empty db but got mysql errno 121 regarding foreign keys. Uninstalled mysql (was on 5.0.x) and downloading 5.1 to install and try again.....
Just keep getting road blocks :(
gnode
02-12-2009, 10:24 PM
So, this is my game plan. Once I get the current PEQ db loaded and my recent backup db loaded, I am going to use this tool:
http://www.databasejournal.com/features/mysql/article.php/1584401/Synchronizing-Your-MySQL-Databases-Using-a-Free-MySQL-Admin-Tool---SQLyog.htm
to bring my backup db's structure up to the same as the new peq db structure.
Then I am going to do all of the inserts in my existing db update script to fill in the necessary data from the updates.
Hope this works...
Andrew80k
02-12-2009, 11:52 PM
You shouldn't need to upgrade your Mysql though. I've been using 5.0 for over a year and I've not had any issues. Let us know if we can help some way. Keep in mind it is hard for us to see what's going on so give as much detail as you can.
gnode
02-13-2009, 12:01 AM
Upon further examination, I don't know if my db is the problem at all.
I straight up copied the current peq db right in and overwrote all my files just to see if it would get world to boot... it did not.
This is a syntax error, not a missing/wrong column error:
[02.12. - 21:50:31] DBLoadItems query 'select source,itemclass,name,lore,idfile,id,weight,norent ,nodrop,size,slots,price,icon,UNK012,UNK013,benefi tflag,tradeskills,cr,dr,pr,mr,fr,astr,asta,aagi,ad ex,acha,aint,awis,hp,mana,ac,deity,skillmodvalue,U NK033,skillmodtype,banedmgrace,banedmgamt,banedmgb ody,magic,casttime_,reqlevel,bardtype,bardvalue,li ght,delay,reclevel,recskill,elemdmgtype,elemdmgamt ,range,damage,color,classes,races,UNK054,maxcharge s,itemtype,material,sellrate,UNK059,casttime,UNK06 1,procrate,combateffects,shielding,stunresist,stri kethrough,extradmgskill,extradmgamt,spellshield,av oidance,accuracy,charmfileid,factionmod1,factionmo d2,factionmod3,factionmod4,factionamt1,factionamt2 ,factionamt3,factionamt4,charmfile,augtype,augslot 1type,augslot1visible,augslot2type,augslot2visible ,augslot3type,augslot3visible,augslot4type,augslot 4visible,augslot5type,augslot5visible,ldontheme,ld onprice,ldonsold,bagtype,bagslots,bagsize,bagwr,bo ok,booktype,filename,banedmgraceamt,augrestrict,lo regroup,pendingloreflag,artifactflag,summonedflag, favor,fvnodrop,endur,dotshielding,attack,regen,man aregen,enduranceregen,haste,damageshield,recastdel ay,recasttype,guildfavor,augdistiller,UNK123,UNK12 4,attuneable,nopet,UNK127,pointtype,potionbelt,pot ionbeltslots,stacksize,notransfer,stackable,UNK134 ,clickeffect,clicktype,clicklevel,clicklevel2,proc effect,proctype,proclevel,proclevel2,worneffect,wo rntype,wornlevel,wornlevel2,focuseffect,focustype, focuslevel,focuslevel2,scrolleffect,scrolltype,scr olllevel,scrolllevel2,updated from items order by id', #1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'range,damage,color,classes,races,UNK054,maxcharge s,itemtype,material,sellrate,UN' at line 1
I now suspect I have a bad program file somewhere. Can anyone check the source to see where this query is done?
cavedude
02-13-2009, 12:15 AM
Which files exactly are you sourcing? What is the address you are getting them from?
gnode
02-13-2009, 12:24 AM
Which files exactly are you sourcing? What is the address you are getting them from?
http://code.google.com/p/projecteqemu/
Featured download: Revision302.zip
That is the changelog I originally followed, also.
Andrew80k
02-13-2009, 12:27 AM
I think cavedude means which database.
gnode
02-13-2009, 12:31 AM
peqdb_1129Rev311.sql
Then all of the miscellaneous *.sql files that did not involve dropping tables.
Thanks for the help... going to bed tonight and will look at it later. I am about ready to zip my db up and send it to someone to make an update script for me for some $$ because this is getting kind of ridiculous.
Andrew80k
02-13-2009, 12:54 AM
Just use the peqdb_1129Rev311.sql file. Don't use any other files unless you know you need to. Which you don't. I did this once before and it hosed me up too. Had to drop it all and re-import it.
gnode
02-13-2009, 01:19 AM
Just use the peqdb_1129Rev311.sql file. Don't use any other files unless you know you need to. Which you don't. I did this once before and it hosed me up too. Had to drop it all and re-import it.
I know I need to because I am missing several tables such as group and raid related.
Also, I am somewhat convinced the problem has nothing to do with my db. The error I am getting is a mysql syntax error in world.exe.
Andrew80k
02-13-2009, 01:28 AM
How do you know you need to? I dump my entire database and reimport it using just the peqdb file and I don't have any missing tables. If you are missing table then you have a database problem with the import. As you say you may have an issue with the code. What code rev are you using? 301? Or 311? Make sure your code matches your database. Database can be before the code but not the other way around. You shouldn't use a database that is numbered after your code rev.
gnode
02-13-2009, 01:30 AM
Cavedude: You may be uniquely suited to help me. Disregard everything that has been done here already.
Here is the situation in the most simple of terms.
I originally installed peq from: http://www.projecteq.net/downloads.php
The 1110a version and your standard db.
I have since done the following:
Created a couple items
Add them to some loot tables
Modified some loot tables
Modified some factions
Modified some spawn tables
I need to be able to move to the current version of the software while preserving these changes. In other words, I need to get current and instead of replacing these tables, alter them to add the necessary columns while also not harming my characters and their inventories. I have a tool that will alter them for me, as long as I have a good schema to bring the columns in from.
How exactly would you go about doing this? This can't be a unique situation other than that it is coming from such an old version.
cavedude
02-13-2009, 03:12 AM
Easily done. First, get yourself the Rev 233 update: http://www.projecteq.net/phpBB2/viewtopic.php?t=4612 You're only using this to update your db, don't worry about quests or anything. The 1110a DB is very old, so that might be why you are having trouble. This assume you have not changed your db name, user, or password. If you have, then the update will fail as it depends on the settings the original installer provided. You will know if it failed if the DOS window that sources the DB doesn't stay up for at least a minute or so.
From there, grab the newest PEQ CVS. Source drop_system.sql, then source in the gz file after you unpack it. Go into the updates folder and run EVERY update from 233 up. So, start at Rev247 and go through Rev294. DO NOT skip right to the end, or run any other updates before 247. Also, don't source any sql from the EQEmu SVN, including from the changelog. Everything you need is handled by PEQ CVS.
Then, grab the newest quests from PEQ Quests CVS, and the newest server build from the EQEmu SVN and you should be set.
While all of your character data will be safe, your content will be lost. There is no way to preserve that other than keeping a sql record of every change you make and source it after you resource the content. PEQ makes so many changes to its database daily that there is no way we can offer individual table changes.
gnode
02-13-2009, 11:04 AM
Easily done. First, get yourself the Rev 233 update: http://www.projecteq.net/phpBB2/viewtopic.php?t=4612 You're only using this to update your db, don't worry about quests or anything. The 1110a DB is very old, so that might be why you are having trouble. This assume you have not changed your db name, user, or password. If you have, then the update will fail as it depends on the settings the original installer provided. You will know if it failed if the DOS window that sources the DB doesn't stay up for at least a minute or so.
From there, grab the newest PEQ CVS. Source drop_system.sql, then source in the gz file after you unpack it. Go into the updates folder and run EVERY update from 233 up. So, start at Rev247 and go through Rev294. DO NOT skip right to the end, or run any other updates before 247. Also, don't source any sql from the EQEmu SVN, including from the changelog. Everything you need is handled by PEQ CVS.
Then, grab the newest quests from PEQ Quests CVS, and the newest server build from the EQEmu SVN and you should be set.
While all of your character data will be safe, your content will be lost. There is no way to preserve that other than keeping a sql record of every change you make and source it after you resource the content. PEQ makes so many changes to its database daily that there is no way we can offer individual table changes.
Thanks I will give it a try. I am going to try it exactly that way first to see if I can get it running. If so, I am going to alter my original tables mentioned above up to the current schema and bring them in to try to skip on content changes. We aren't going beyond PoP and I did a lot of work to restore PoM back to original. Unless, do you know if PoM has a separate spawn table now? I wonder how many of my customizations might be standard by now..
cavedude
02-13-2009, 11:50 AM
PoM is by the default the original version as best as I could get it. It's a spawn_condition now, so the default setting of 1 is for PoM 1.0, and changing it to 2 switches the spawns to version 2.0.
gnode
02-13-2009, 12:31 PM
PoM is by the default the original version as best as I could get it. It's a spawn_condition now, so the default setting of 1 is for PoM 1.0, and changing it to 2 switches the spawns to version 2.0.
Hmm... awesome. The only other really involved change I made was cleaning up airplane's spawn times and loot tables. Perhaps I should redo that on the new version and submit it back to you guys if needed.
I also made a quest that upgrades people's kunark and old planar armor up to low-tier velious specs. I can live without that given the stage we are in. But my only concern with that is all the old item ids floating around. Many of those items are in the 1400-1500 range and used by some people still...
What guidelines do you have regarding item ids? If I were to change all of these IDs to something that won't interfere with the peq db, what number range should I use?
It sounds like a lot of the big "fixes" I put in are standard now. I may just have to re-import a minority of my changes and clean up inventory.
cavedude
02-13-2009, 01:09 PM
Sure, any work you do on airplane or any other zone submit to me on the PEQ forums. If it's good, I'll merge it :) I never turn good work away.
The item IDs are Sony's so I don't handle the ranges at all. Because of that, I can't give you IDs that I can say with certainty won't be taken when I do the 13th floor dump again.
gnode
02-13-2009, 04:29 PM
Sure, any work you do on airplane or any other zone submit to me on the PEQ forums. If it's good, I'll merge it :) I never turn good work away.
The item IDs are Sony's so I don't handle the ranges at all. Because of that, I can't give you IDs that I can say with certainty won't be taken when I do the 13th floor dump again.
So really, with any luck, a lot of my items may not even be harmed if I re-insert it back in.
gnode
02-15-2009, 01:07 AM
Easily done. First, get yourself the Rev 233 update: http://www.projecteq.net/phpBB2/viewtopic.php?t=4612 You're only using this to update your db, don't worry about quests or anything. The 1110a DB is very old, so that might be why you are having trouble. This assume you have not changed your db name, user, or password. If you have, then the update will fail as it depends on the settings the original installer provided. You will know if it failed if the DOS window that sources the DB doesn't stay up for at least a minute or so.
From there, grab the newest PEQ CVS. Source drop_system.sql, then source in the gz file after you unpack it. Go into the updates folder and run EVERY update from 233 up. So, start at Rev247 and go through Rev294. DO NOT skip right to the end, or run any other updates before 247. Also, don't source any sql from the EQEmu SVN, including from the changelog. Everything you need is handled by PEQ CVS.
Then, grab the newest quests from PEQ Quests CVS, and the newest server build from the EQEmu SVN and you should be set.
While all of your character data will be safe, your content will be lost. There is no way to preserve that other than keeping a sql record of every change you make and source it after you resource the content. PEQ makes so many changes to its database daily that there is no way we can offer individual table changes.
I did this exactly and it did not work. So then I backtracked to find exactly what point it did not work.
I installed peq fresh, straight from: http://prdownloads.sourceforge.net/peq/PEQServerPack-4.0-1110a.exe?download
Then I loaded my DB, which is structurally identical to the one in the installer.
Then I applied the 233 patch to update db and server files.
For giggles, I loaded up eqemu right then and there. When I log in, I am blasted with this error and I am able to get my char in the game, but he has no gear. Almost all of these items are in fact in the db. So maybe there are other changes I need to make before the 233 patch?
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 17005 in inventory slot 2500
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 17005 in inventory slot 2501
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 19255 in inventory slot 2531
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 4301 in inventory slot 2532
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 19418 in inventory slot 2533
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 4555 in inventory slot 2534
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 19330 in inventory slot 2535
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 6678 in inventory slot 2536
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 11631 in inventory slot 2538
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 6675 in inventory slot 2541
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 19496 in inventory slot 2542
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 11611 in inventory slot 2543
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 4175 in inventory slot 2544
[02.14. - 22:55:01] Warning: acctid 1 has an invalid item_id 11668 in inventory slot 2545
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11584 in inventory slot 2546
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6692 in inventory slot 2547
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6300 in inventory slot 2548
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 17005 in inventory slot 2500
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 17005 in inventory slot 2501
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19255 in inventory slot 2531
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4301 in inventory slot 2532
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19418 in inventory slot 2533
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4555 in inventory slot 2534
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19330 in inventory slot 2535
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6678 in inventory slot 2536
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11631 in inventory slot 2538
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6675 in inventory slot 2541
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19496 in inventory slot 2542
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11611 in inventory slot 2543
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4175 in inventory slot 2544
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11668 in inventory slot 2545
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11584 in inventory slot 2546
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6692 in inventory slot 2547
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6300 in inventory slot 2548
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 17005 in inventory slot 2500
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 17005 in inventory slot 2501
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19255 in inventory slot 2531
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4301 in inventory slot 2532
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19418 in inventory slot 2533
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4555 in inventory slot 2534
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19330 in inventory slot 2535
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6678 in inventory slot 2536
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11631 in inventory slot 2538
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6675 in inventory slot 2541
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19496 in inventory slot 2542
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11611 in inventory slot 2543
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4175 in inventory slot 2544
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11668 in inventory slot 2545
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11584 in inventory slot 2546
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6692 in inventory slot 2547
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6300 in inventory slot 2548
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 17005 in inventory slot 2500
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 17005 in inventory slot 2501
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19255 in inventory slot 2531
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4301 in inventory slot 2532
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19418 in inventory slot 2533
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4555 in inventory slot 2534
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19330 in inventory slot 2535
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6678 in inventory slot 2536
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11631 in inventory slot 2538
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6675 in inventory slot 2541
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19496 in inventory slot 2542
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11611 in inventory slot 2543
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4175 in inventory slot 2544
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11668 in inventory slot 2545
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11584 in inventory slot 2546
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6692 in inventory slot 2547
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6300 in inventory slot 2548
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 17005 in inventory slot 2500
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 17005 in inventory slot 2501
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19255 in inventory slot 2531
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4301 in inventory slot 2532
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19418 in inventory slot 2533
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4555 in inventory slot 2534
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19330 in inventory slot 2535
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6678 in inventory slot 2536
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11631 in inventory slot 2538
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6675 in inventory slot 2541
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 19496 in inventory slot 2542
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11611 in inventory slot 2543
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 4175 in inventory slot 2544
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11668 in inventory slot 2545
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 11584 in inventory slot 2546
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6692 in inventory slot 2547
[02.14. - 22:55:02] Warning: acctid 1 has an invalid item_id 6300 in inventory slot 2548
gnode
02-15-2009, 02:01 AM
Also, #npcloot show on any npc shows no loot. It is as though items simply won't load right... but the table is fully populated.
cavedude
02-15-2009, 04:48 AM
The items table has changed since 233... You need to update past that to work with the current server after you've restored your inventory table.
What part of the procedure didn't work? What were the errors you were getting?
cavedude
02-15-2009, 05:02 AM
Could you do a describe items; at a MySQL prompt and post the output? I have a feeling that you are overwriting the stock table with an outdated or altered table and that is where your trouble is.
gnode
02-15-2009, 12:44 PM
Just a sec... I did a fresh install 10 minutes ago, with no changes, and created a new char and he had no inventory and nothing item related worked.
I then uninstalled mysql 5.1, installed 5.0, installed the base peq, and items worked.
I am going to redo everything this morning in 5.0 instead of 5.1 and report back. I also think somewhere along the line I switched a few tables to myisam for performance troubleshooting. I am keeping everything straight innodb for now.
cavedude
02-15-2009, 12:51 PM
5.1 isn't supported until Rev 316, so unless you've compiled yourself, it isn't going to work.
gnode
02-15-2009, 01:03 PM
Ok after fresh install + rev233 update and nothing else, I am able to log in and items/inventory work normally, minus custom stuff (will reinsert later after I have all the base working).
So far so good.... may have just been a mysql 5.1 or myisam problem. Not getting that syntax error from earlier now.
gnode
02-15-2009, 02:04 PM
Ok... server starts up, I can log in, my character shows gear in the char select screen, but can not enter any zones. zone.exe is not running/started.
This is what I did:
Installed mysql 5.0
Installed base peq - logged in, tested good
Loaded my db - logged in, tested good
Installed the peq rev233 update - logged in, tested good, minus custom items
Sourced drop_system.sql (from peq cvs)
Sourced the sql from the gz.. waited a minute (from peq cvs)
Applied the various rev updates from 247 and up (from peq cvs)
(did not change binaries yet) Logged in for giggles - items did not work, but zone loaded and I could walk around - no sweat
Dropped in all files from Revision302.zip from the google svn "featured download"
Logged in, my char shows equipment in char select, but zone.exe is unable to load. Perhaps I need to download a different set of binaries? Can you point me in the right direction? Maybe rev302.zip relies on changes made to the db since rev299 of peq?
These are the only logs produced:
eqemu_world_0224.log:
---------------------------------------------
[02.15. - 11:49:56] Starting Log: logs/eqemu_world_0224.log
[02.15. - 11:49:56] Using database 'peq' at localhost:3306
[02.15. - 11:49:56] EMuShareMem loaded
[02.15. - 11:49:57] Loading items from database: count=76214
eqemu_debug_world_0224.log:
---------------------------------------------
[02.15. - 11:49:56] Starting Log: logs/eqemu_debug_world_0224.log
[02.15. - 11:49:56] [WORLD__INIT] Loading server configuration..
[02.15. - 11:49:56] [WORLD__INIT] Log settings loaded from log.ini
[02.15. - 11:49:56] [WORLD__INIT] CURRENT_WORLD_VERSION:EQEMu 0.7.0
[02.15. - 11:49:56] [WORLD__INIT] Connecting to MySQL...
[02.15. - 11:49:56] [WORLD__INIT] Starting HTTP world service...
[02.15. - 11:49:56] [WORLD__HTTP] Loaded mime types from mime.types
[02.15. - 11:49:56] [WORLD__INIT] Loading variables..
[02.15. - 11:49:56] [WORLD__INIT] Loading zones..
[02.15. - 11:49:56] [WORLD__INIT] Clearing groups..
[02.15. - 11:49:56] [WORLD__INIT] Clearing raids..
[02.15. - 11:49:56] [WORLD__INIT] Loading items..
[02.15. - 11:50:01] [WORLD__INIT] Loading guilds..
[02.15. - 11:50:01] [RULES__CHANGE] Loading rule set 'default' (1)
[02.15. - 11:50:01] [RULES__CHANGE] Set rule GM:MinStatusToZoneAnywhere to value 250
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:MaxLevel to value 65
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:LeaveCorpses to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:LeaveNakedCorpses to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ExpMultiplier to value 0.7500000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:DeathExpLossLevel to value 10
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:CorpseDecayTimeMS to value 86400000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:AutosaveIntervalS to value 300
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:HPRegenMultiplier to value 100
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ManaRegenMultiplier to value 100
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:EnduranceRegenMultiplier to value 100
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Guild:MaxMembers to value 2048
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Skills:MaxTrainTradeskills to value 21
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Pets:AttackCommandRange to value 150.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:ZoneAutobootTimeoutMS to value 120000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:ClientKeepaliveTimeoutMS to value 95000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:UseBannedIPsTable to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:MaxClientsPerIP to value -1
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:ExemptMaxClientsStatus to value -1
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Aggro:PetSpellAggroMod to value 10
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Aggro:SongAggroMod to value 33
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Aggro:SpellAggroMod to value 100
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:BaseCritChance to value 0.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:WarBerBaseCritChance to value 0.0299999993294
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:BerserkBaseCritChance to value 0.0599999986589
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:NPCBashKickLevel to value 6
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ConsumptionMultiplier to value 100
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:AutoResistDiff to value 15
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:ResistChance to value 2.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:ResistMod to value 0.4000000059605
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:PartialHitChance to value 0.6999999880791
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:ClientBaseCritChance to value 0.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:NPCGlobalPositionUpdateInterval to value 60000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule NPC:MinorNPCCorpseDecayTimeMS to value 600000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule NPC:MajorNPCCorpseDecayTimeMS to value 1200000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:GraveyardTimeMS to value 1200000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:EnableShadowrest to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Map:FixPathingZWhenLoading to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Map:FixPathingZAtWaypoints to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Map:FixPathingZWhenMoving to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Map:FixPathingZOnSendTo to value false
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:ClientLinkdeadMS to value 180000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule NPC:UseItemBonusesForNonPets to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Map:FixPathingZMaxDeltaSendTo to value 12.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Map:FixPathingZMaxDeltaLoading to value 12.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Map:FixPathingZMaxDeltaMoving to value 12.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Map:FixPathingZMaxDeltaWaypoint to value 12.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:HealOnLevel to value false
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:FeignKillsPet to value false
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ItemManaRegenCap to value 15
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ItemHealthRegenCap to value 15
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:UseIntervalAC to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:PetAttackMagicLevel to value 30
[02.15. - 11:50:01] [RULES__CHANGE] Set rule NPC:SayPauseTimeInSec to value 10
[02.15. - 11:50:01] [RULES__CHANGE] Set rule NPC:OOCRegen to value 0
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Aggro:SmartAggroList to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Aggro:SittingAggroMod to value 35
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Aggro:MeleeRangeAggroMod to value 20
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Aggro:CurrentTargetAggroMod to value 0
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Aggro:CriticallyWoundedAggroMod to value 100
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Aggro:SlowAggroMod to value 450
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Aggro:IncapacitateAggroMod to value 500
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Aggro:MovementImpairAggroMod to value 175
[02.15. - 11:50:01] [RULES__CHANGE] Set rule NPC:BuffFriends to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:DeathItemLossLevel to value 10
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Watermap:CheckWaypointsInWaterWhenLoading to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Watermap:CheckForWaterAtWaypoints to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Watermap:CheckForWaterWhenMoving to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Watermap:CheckForWaterOnSendTo to value false
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Watermap:CheckForWaterWhenFishing to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Watermap:FishingRodLength to value 30.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Watermap:FishingLineLength to value 40.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ItemDamageShieldCap to value 30
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ItemAccuracyCap to value 150
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ItemAvoidanceCap to value 100
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ItemCombatEffectsCap to value 100
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ItemShieldingCap to value 35
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ItemSpellShieldingCap to value 35
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ItemDoTShieldingCap to value 35
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ItemStunResistCap to value 35
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:ItemStrikethroughCap to value 35
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:PartialHitChanceFear to value 0.2500000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:MQWarpExemptStatus to value -1
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:MQZoneExemptStatus to value -1
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:MQGateExemptStatus to value -1
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:MQGhostExemptStatus to value -1
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:EnableMQWarpDetector to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:EnableMQZoneDetector to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:EnableMQGateDetector to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:EnableMQGhostDetector to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:MQWarpDetectorDistance to value 4900.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:MQWarpLagThreshold to value 140.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:MQWarpThresholdTimer to value 90000.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:EnableFearPathing to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:FleeHPRatio to value 22
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:FleeIfNotAlone to value false
[02.15. - 11:50:01] [RULES__CHANGE] Set rule NPC:EnableNPCQuestJournal to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:SkillUpModifier to value 100
[02.15. - 11:50:01] [RULES__CHANGE] Set rule NPC:CorpseUnlockTimer to value 150000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule NPC:EmptyNPCCorpseDecayTimeMS to value 0
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:ClearTempMerchantlist to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:AddMaxClientsPerIP to value -1
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:AddMaxClientsStatus to value -1
[02.15. - 11:50:01] [RULES__CHANGE] Set rule TaskSystem:EnableTaskSystem to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule TaskSystem:PeriodicCheckTimer to value 5
[02.15. - 11:50:01] [RULES__CHANGE] Set rule TaskSystem:RecordCompletedTasks to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule TaskSystem:RecordCompletedOptionalActivities to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule TaskSystem:KeepOneRecordPerCompletedTask to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule TaskSystem:EnableTaskProximity to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:EnableTutorialButton to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:EnableReturnHomeButton to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:MaxLevelForTutorial to value 10
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:MinOfflineTimeToReturnHome to value 21600
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Zone:AutoShutdownDelay to value 5000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:MaxExpLevel to value 0
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:AdjustProcPerMinute to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:AvgProcsPerMinute to value 18.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:ProcPerMinDexContrib to value 0.0750000029802
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:BaseProcChance to value 0.0350000001490
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:ProcDexDivideBy to value 11000.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Chat:ServerWideOOC to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Chat:ServerWideAuction to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:BaseCritChance to value 0
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:BaseCritRatio to value 100
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:WizCritLevel to value 12
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:WizCritChance to value 7
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:WizCritRatio to value 0
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:SharedBankPlat to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:ResistPerLevelDiff to value 85
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:BaseHitChance to value 54.0000000000000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:HitPerLevelDiff to value 145
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Combat:AgiHitFactor to value 0.0149999996647
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:UseDeathExpLossMult to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:DeathExpLossMultiplier to value 3
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Character:BindAnywhere to value false
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Bazaar:AuditTrail to value false
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Bazaar:MaxSearchResults to value 50
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:TutorialZoneID to value 189
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Bazaar:EnableWarpToTrader to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Bazaar:MaxBarterSearchResults to value 200
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:AccountSessionLimit to value 1
[02.15. - 11:50:01] [RULES__CHANGE] Set rule World:ExemptAccountLimitStatus to value -1
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Mail:EnableMailSystem to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Mail:ExpireTrash to value 0
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Mail:ExpireRead to value 31536000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Mail:ExpireUnread to value 31536000
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Channels:RequiredStatusAdmin to value 251
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Channels:RequiredStatusListAll to value 251
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Channels:DeleteTimer to value 1440
[02.15. - 11:50:01] [RULES__ERROR] Unable to find rule 'EQOffline:BotManaRegen'
[02.15. - 11:50:01] [RULES__ERROR] Unable to interpret rule record for EQOffline:BotManaRegen
[02.15. - 11:50:01] [RULES__ERROR] Unable to find rule 'EQOffline:BotFinishBuffing'
[02.15. - 11:50:01] [RULES__ERROR] Unable to interpret rule record for EQOffline:BotFinishBuffing
[02.15. - 11:50:01] [RULES__ERROR] Unable to find rule 'EQOffline:BotCount'
[02.15. - 11:50:01] [RULES__ERROR] Unable to interpret rule record for EQOffline:BotCount
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Chat:EnableVoiceMacros to value true
[02.15. - 11:50:01] [RULES__CHANGE] Set rule Spells:TranslocateTimeLimit to value 0
[02.15. - 11:50:01] [RULES__CHANGE] Set rule EventLog:RecordSellToMerchant to value false
[02.15. - 11:50:01] [RULES__CHANGE] Set rule EventLog:RecordBuyFromMerchant to value false
[02.15. - 11:50:01] [WORLD__INIT] Loaded default rule set 'default'
[02.15. - 11:50:01] [WORLD__INIT] Clearing temporary merchant lists..
[02.15. - 11:50:01] [WORLD__INIT] Loading EQ time of day..
[02.15. - 11:50:01] [WORLD__INIT] Loading launcher list..
[02.15. - 11:50:01] [WORLD__INIT] Reboot zone modes ON
[02.15. - 11:50:01] [WORLD__INIT] Deleted 0 stale player corpses from database
[02.15. - 11:50:01] [WORLD__INIT] Deleted 0 stale player backups from database
[02.15. - 11:50:01] [WORLD__INIT] Zone (TCP) listener started.
[02.15. - 11:50:01] [WORLD__INIT] Client (UDP) listener started.
[02.15. - 11:50:01] [NET__IDENTIFY] Registered patch 6.2
[02.15. - 11:50:01] [NET__IDENTIFY] Registered patch Titanium
[02.15. - 11:50:01] [NET__IDENTIFY] Registered patch Anniversary
[02.15. - 11:50:01] [NET__IDENTIFY] Registered patch Live
[02.15. - 11:50:01] [WORLD__LS] Connecting to login server...
[02.15. - 11:50:01] [WORLD__LS] Connected to Loginserver: eqemulator.net:5998
[02.15. - 11:50:01] [WORLD__LS] Loginserver provided 72.181.213.95 as world address
[02.15. - 11:50:43] [WORLD__CLIENT] New connection from 10.10.1.105:1193
[02.15. - 11:50:43] [NET__IDENT_TRACE] 10.10.1.105:1193: First opcode 0x4dd0 did not match expected 0x2792
[02.15. - 11:50:43] [NET__IDENT_TRACE] 10.10.1.105:1193: Tried patch 6.2_world, and it did not match.
[02.15. - 11:50:43] [NET__IDENT_TRACE] 10.10.1.105:1193: First opcode 0x4dd0 did not match expected 0x2ec9
[02.15. - 11:50:43] [NET__IDENT_TRACE] 10.10.1.105:1193: Tried patch 6.2_zone, and it did not match.
[02.15. - 11:50:43] [NET__IDENT_TRACE] 10.10.1.105:1193: First opcode matched 0x4dd0 and length matched 464
[02.15. - 11:50:43] [NET__IDENTIFY] Identified stream 10.10.1.105:1193 with signature Titanium_world
[02.15. - 11:50:43] [WORLD__CLIENT] Checking inbound connection 10.10.1.105 against BannedIPs table
[02.15. - 11:50:43] [WORLD__CLIENT] Connection 10.10.1.105 PASSED banned IPs check. Processing connection.
[02.15. - 11:50:43] [WORLD__CLIENT] gnode: Logged in. Mode=(CharSel)
[02.15. - 11:50:43] [WORLD__CLIENT] gnode: LS Account #115285
[02.15. - 11:51:20] [WORLD__CLIENT] gnode: Attempting autobootup of nexus (152)
[02.15. - 11:51:20] [WORLD__CLIENT_ERR] gnode: No zoneserver available to boot up.
leslamarch
02-15-2009, 02:34 PM
I'm guessing this may be part of the problem?
[02.15. - 11:50:01] [RULES__ERROR] Unable to find rule 'EQOffline:BotManaRegen'
[02.15. - 11:50:01] [RULES__ERROR] Unable to interpret rule record for EQOffline:BotManaRegen
[02.15. - 11:50:01] [RULES__ERROR] Unable to find rule 'EQOffline:BotFinishBuffing'
[02.15. - 11:50:01] [RULES__ERROR] Unable to interpret rule record for EQOffline:BotFinishBuffing
[02.15. - 11:50:01] [RULES__ERROR] Unable to find rule 'EQOffline:BotCount'
[02.15. - 11:50:01] [RULES__ERROR] Unable to interpret rule record for EQOffline:BotCountNot sure what version binaries your using vs. database version?
gnode
02-15-2009, 02:48 PM
I am using PEQ rev299 for the db
The actual eqemu server files are from the revision302.zip from the peq google svn featured download section.
That error looks like I have rules in the rule table that it does not know how to use. I suspect that should not cause any crash... but I could be wrong. I will delete those rules to test..
gnode
02-15-2009, 02:55 PM
I removed those rules and now the error is not in the log file, but zone.exe still does not start.
gnode
02-15-2009, 04:15 PM
Ok. I feel comfortable moving my live server up to eqemu rev233 for now. Going to do that now and then wait until I can get the newer versions working on my backup machine before proceeding.
Better than nothing.
gnode
02-15-2009, 05:35 PM
Alright we are live on rev233 with no loss of custom loot/quests/npcs...
Going to resume trying the full upgrade next weekend. For now, time to play!
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.