Starting up worldserver and immediately have 'AccountMgr' messages?

I just pulled an update this morning and done the compile works, but when I started the worldserver up I got these messages immediately after the server booted up.

Anybody know what this might mean?

[ATTACH]2390._xfImport[/ATTACH]

Well, you can see in server/game/Accounts/AccountMgr.cpp that it’s caused by something calling AccountMgr::HasPermission without supplying an accountId. Since that file hasn’t been changed in a while, it’s an issue with the caller or your databases.

I suspect that one of your accounts has somehow got a zero account id or some change to the databases is causing HasPermission to be called without a valid account, but that’s just a guess. You might narrow the possibilities down by using git bisect (http://webchick.net/node/99) to figure out where the problem started.

You could also do a web search and find this (possibly related?) problem which referred to auction house code: https://community.trinitycore.org/topic/11138-account-manager/ If the auction house is to blame, you might be able to fix it by clearing the auction data.

Thanks dane!

Wasn’t sure if it might have been something to do with the auto updating of the SQL. I only get these messages when I’ve updated the server and run worldserver which adds the SQL updates automatically.

I’ll dig farther into it using your suggestion of git bisect.

Well tried to use git bisect, didn’t find anything.

So .pdumped characters, and rebuilt the databases, and am currently recompiling this morning to see if it happens again.

Did notice a lot of sql’s in the pull this morning, so will see if this corrected it or not.

Nope. Damn, had fingers crossed too. LOL!

[ATTACH]2392._xfImport[/ATTACH]

If bisect didn’t fix it, that suggests that your database was the problem. When you say you rebuilt it, do you mean you started with an empty database? That would be my next step (after backing up the old database, naturally). If that worked, I’d try restoring the backup and deleting all the auction data. Note that you need to remove the auction items as well as the sell data. I’ve done this before, but forgot to take notes on the queries I used.

If an empty database doesn’t work, I’m stumped. I need to update my server and see if there are any problems.

That’s exactly what I did. Deleted all 3 tables and pulled fresh source code to recompile and even changed out OS back to debian stretch.

Will have to wait until my next source pull to see if it works ok now.

Sweet! Everything worked smooth as silk this morning when I compiled and loaded up new sql statements.

Aokromes, if you would, you can close this topic now as the problems seems to have gone bye-bye now.

Thanks for the assist dane!