You are currently reviewing an older revision of this page.
To correct it, I think shutting down the engine and then renaming the kdbs to positive numbers (making sure the most recent is highest of course) is sufficient.
Also, if you're currently running on a negative numbered kdb, you should immediately make sure that there are no positive numbered kdbs in the gw directory. The usual "highest number kdb" rules still apply, so we want to make sure any restart would select the kdb you're currently writing to.
I believe this issue can occur after improperly resetting a particular engine's KDBs.