Added check and error log for chronograph db method

Right now processing lock time is choosen by some reasonable assumption that 1 second is always enough to process data. Added some checks and logging to this assumption. In case real life processing time will be higher than 1 second immediate actions should be taken to solve this issue. Otherwise we may end up in race conditions between workers updating same auction twice