Lots of invalid item issues since update

[provocating]

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.

[02-03-2015 :: 04:41:45] Zone Shutdown: cauldron (70)
[02-03-2015 :: 04:41:45] Zone shutdown: going to sleep
[02-03-2015 :: 04:41:45] Destroying EQEmuIO=HASH(0x3a9c898)
[02-03-2015 :: 04:41:45] Destroying EQEmuIO=HASH(0x3a9cf70)
[02-03-2015 :: 04:41:45] Tying perl output to eqemu logs
[02-03-2015 :: 04:41:45] Creating EQEmuIO=HASH(0x2e33ad8)
[02-03-2015 :: 04:41:45] Creating EQEmuIO=HASH(0x2e341b0)
[02-03-2015 :: 04:41:45] Loading perlemb plugins.
[02-03-2015 :: 04:46:59] Time Broadcast Packet: EQTime [11:19 am]
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 40095 in inventory slot 1
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 83176 in inventory slot 6
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 87274 in inventory slot 7
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 40051 in inventory slot 8
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 11625 in inventory slot 13
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 1843 in inventory slot 14
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 2744 in inventory slot 15
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 87278 in inventory slot 17
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 87276 in inventory slot 18
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 87275 in inventory slot 19
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 32601 in inventory slot 22
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 17005 in inventory slot 23
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 77821 in inventory slot 24
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 17969 in inventory slot 25
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 96421 in inventory slot 26
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15499 in inventory slot 27
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 77781 in inventory slot 28
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15496 in inventory slot 29
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 9991 in inventory slot 251
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 9990 in inventory slot 252
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15089 in inventory slot 253
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 5351 in inventory slot 254
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15015 in inventory slot 255
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15498 in inventory slot 256
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 10015 in inventory slot 257
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15497 in inventory slot 258
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 7632 in inventory slot 261
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 7634 in inventory slot 262
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 11816 in inventory slot 263
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 16082 in inventory slot 264
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 3312 in inventory slot 266
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 26970 in inventory slot 281
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15309 in inventory slot 282
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15411 in inventory slot 283
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15080 in inventory slot 284
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15852 in inventory slot 285
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15083 in inventory slot 287
[02-03-2015 :: 04:47:37] Warning: charid 157621 has an invalid item_id 15068 in inventory slot 289
[02-03-2015 :: 04:47:58] Zoning 'Zonka' to: unrest (63) - (0) x=330.000000, y=64.000000, z=3.130000
[02-03-2015 :: 04:48:13] Zoning 'Arle' to: unrest (63) - (0) x=330.000000, y=64.000000, z=3.130000
[02-03-2015 :: 04:48:37] Zone Shutdown: cauldron (70)
[02-03-2015 :: 04:48:37] Zone shutdown: going to sleep
[02-03-2015 :: 04:48:37] Destroying EQEmuIO=HASH(0x2e33ad8)
[02-03-2015 :: 04:48:37] Destroying EQEmuIO=HASH(0x2e341b0)
[02-03-2015 :: 04:48:37] Tying perl output to eqemu logs
[02-03-2015 :: 04:48:37] Creating EQEmuIO=HASH(0x7f8fc4125d58)
[02-03-2015 :: 04:48:37] Creating EQEmuIO=HASH(0x7f8fc4126430)
[02-03-2015 :: 04:48:37] Loading perlemb plugins.
[02-03-2015 :: 04:50:32] Time Broadcast Packet: EQTime [12:30 pm]

[NatedogEZ]

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

[provocating]

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.

[dagulus2]

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.

[provocating]

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.

[trevius]

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.

[provocating]

Originally Posted by trevius

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.

Yeah I have tried running shared memory while the server is up and running and what would happen is the next time the players zone, they would go LD. I try to tread lightly on the production server as to not interfere with the player's experience, I will just make sure all my changes are done on test from now on.

[Uleat]

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.)

[provocating]

I think things are resolved, crossing my fingers.