Security Discrepancy from Master ?

(Fenris) #1

From time to time I am getting this error on the server I’m running. The problem is solved by restarting the ET server, but I’m curious as to why this happens and if it can be prevented so I don’t have to restart ?

I’ve mailed Evenbalance about it a few days ago but pending any answer from them I thought I’d check if anyone here has run into it and already knows the answer.

(Note: The error occurs both at the automatic updates, and as below can be provoked by doing a pb_sv_update from the console or rcon)

pb_sv_update
ET PB Server: Master Query Sent to (MASTER4.EVENBALANCE.COM) 216.40.250.37
ET PB Server: Security Discrepancy from Master at :0
pb_sv_update
ET PB Server: Master Query Sent to (ID2.EVENBALANCE.COM) 192.246.40.80
ET PB Server: Security Discrepancy from Master at :0
pb_sv_update
ET PB Server: Master Query Sent to (ET1.EVENBALANCE.COM) 216.40.250.82
ET PB Server: Security Discrepancy from Master at :0
pb_sv_update
ET PB Server: Master Query Sent to (MASTER3.EVENBALANCE.COM) 216.40.230.37
ET PB Server: Security Discrepancy from Master at :0

(Lekdevil.NL) #2

That error is probably caused by a corrupted pbsv.db file on your server. I don’t know exactly how, but some months ago this happened to a lot of servers too. This leads me to believe that the cause is external (for instance by garbage data sent from the PB master servers). It also explains why suddenly there are a lot of not-updated PB servers out there (including our very own Spash Damage server).

To fix the problem: make a backup copy of your pbsv.db file (I’m sure Even Balance would like to take a look at it, otherwise I’d be interested as well; PM me the file if you like), and delete the original. Then issue a pb_sv_update to let the server reacquire the security checksum data and recreate the pbsv.db file.

HTH.

(Fenris) #3

Thanks, I’ll try that after I get home today and I’ll send you the file as well. :drink:

(Fenris) #4

Ok, in case anyone else has this and is interested I got a reply from Evenbalance today. The problem is caused by a bug, but they are not yet sure of why it happens. A workaround is, as Lekdevil also suggested, to delete the file.