Lots of invalid item issues since update
I have not updated since around October. We had a small corpse issue, but I handled that easy enough. A new issue has popped up when we got an influx of people using Titanium it seems. My UF players have not yet reported this issue. When zoning in and out they have no inventory. Zones we have seen this in are GL, Cab East and Dagnor. Here is a piece of the dagnor log.
Code:
[02-03-2015 :: 04:41:45] Zone Shutdown: cauldron (70) |
The zoning with no gear issue is usually from too man DB updates while the server is up, that is the only time Ive ever seen that happen.
edit.. nvm the invalid item_id is from items that don't exist in the items table that are in player's inventory... I was thinking of the invalid_slot thing that is spamming my logs :p |
The only thing I did last night was add a few things to the loottable for Kael. It may had been 6 rows. I did do a boatload of #reloadqst while working on some Lua. I am going to shutdown/restart EqEmu in a bit once everyone can log. Never had this issue before in two years.
|
I don't actually think the number of changes is that important. As soon as something you change interacts with a character, there's a chance your items table will no longer connect.
|
That is the strange issue, I have not modified the items table at all. I added a few loottables to the database. I will know in a few hours. I think you guys are right though, because the first day after the upgrade we had no issues. The issues started when I added to the loottables, which I will never do on our production server after knowing this.
|
Yes, that is most likely related to shared mem. If you run the sharedmem executable again while the server is up, it may correct the issue of zoning with no gear showing up. It seems to be related to the DB not matching your last run of sharedmem. I don't really know the details and it is pretty annoying to not be able to edit the DB while the server is running. This only happens when editing certain tables (normally items table from what I have seen).
The best thing to do is a restart when the issue shows up. |
Quote:
|
Well, I know that 9990 and 9991 are the 'starting' food and drink..so, if those are messed up...
The shared_mem.exe should be run in downtime conditions. I don't believe there is a refresh feature in either world or zone to allow run-time changes. (You might look into doing a repair on the table as well, if the issue doesn't resolve itself.) |
I think things are resolved, crossing my fingers.
|
All times are GMT -4. The time now is 01:27 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.