High CPU on bridge

The UDM DB files in C:\ProgramData\Event Zero\UDM Pro Bridge\DB can become locked, this is usually due to another application accessing the files. UDM in a busy system will be reading and writing to these files constantly, interrupting this process can produce inconsistent data. You can check if the DB is locked by looking in the C:\ProgramData\Event Zero\UDM Pro Bridge\Logs\Bridge V2_xxx.log files and searching for the message “SQLite Error 5: 'database is locked'“. If you see this message, then resolution can be achieved by trying the following:

  1. Identify what has caused the lock and the database. This can be a backup, virus scanning or operating system service. If the system has been working for some time then check if there have been any changes made, patches or new applications or functionality turned on. If you cannot identify what has caused the lock, then following steps below will clear the problem but it will most likely reoccur again. So it is essential to identify the cause.

  2. Stop and restart the UDM Pro services

  3. If the service restart does not clear the issue then reboot the bridge server

  4. If a server reboot does not clear the issue, then the lock is more complex

    1. Stop the UDM services – EZ UDM Pro Bridge and EZ UDM Pro Bridge Helper Service

    2. Go to the C:\ProgramData\Event Zero\UDM Pro Bridge\DB directory copy all the .db files to a temporary directory

    3. Delete the .db files from C:\ProgramData\Event Zero\UDM Pro Bridge directory

    4. Copy .db files from the temporary directory back to C:\ProgramData\Event Zero\UDM Pro Bridge

    5. Restart the UDM services

  5. If copying the files and copying back doesn’t work then

    1. Stop the UDM services – EZ UDM Pro Bridge and EZ UDM Pro Bridge Helper Service

    2. Go to the C:\ProgramData\Event Zero\UDM Pro Bridge\DB directory move all the files to a temporary directory. So the DB directory is completely empty

    3. Restart the UDM services

    4. Note by doing this UDM will regather information on all the devices, when this happens until a device checks in the reboot and Rest API commands will not work