Notification Engine, repetitive warnings
In the event where the Doremi server (DCP2000 or ShowVault) shows the same warnings over and over at each boot, this issue is caused by a system date or time conflict.
For example: In case a Dolphin RTC has failed, the time is reverted back to the past or to the future. This may cause any previously shows warnings to re-appear again at each boot. Even if the Dolphin is fixed or replaced, the system still detects the faulty date & time.
You may encounter different warning, (Doremi Maintenance Program or Secured Clock):
In the log /doremi/log/hotplug.log you may see something like the below:
[Wed Apr 8 11:41:24 WEST 2015]: System startup
[Wed Apr 8 11:41:25 WEST 2015]: Mediablock plugged; initializing...
[Wed Apr 8 11:41:27 WEST 2015]: Serial number changed from 218991 to 219333
[Wed Apr 8 11:41:27 WEST 2015]: Firmware version 21.3s
[Wed Apr 8 11:41:49 WEST 2015]: done.
[Wed Apr 8 11:48:19 WEST 2015]: System startup
[Wed Oct 24 18:48:14 WEST 2029]: Mediablock plugged; initializing...
[Wed Oct 24 18:48:16 WEST 2029]: Serial number 219333
[Wed Oct 24 18:48:16 WEST 2029]: Firmware version 21.3s
[Wed Oct 24 18:48:36 WEST 2029]: done.
[Wed Apr 8 11:53:15 WEST 2015]: System startup
[Wed Oct 24 18:53:10 WEST 2029]: Mediablock plugged; initializing...
[Wed Oct 24 18:53:11 WEST 2029]: Serial number 219333
[Wed Oct 24 18:53:11 WEST 2029]: Firmware version 21.3s
[Wed Oct 24 18:53:19 WEST 2029]: done.
[Wed Apr 8 11:59:42 WEST 2015]: System startup
[Wed Oct 24 18:59:37 WEST 2029]: Mediablock plugged; initializing...
[Wed Oct 24 18:59:38 WEST 2029]: Serial number 219333
[Wed Oct 24 18:59:38 WEST 2029]: Firmware version 21.3s
[Wed Oct 24 18:59:46 WEST 2029]: done.
[Wed Apr 8 12:09:31 WEST 2015]: System startup
[Wed Apr 8 12:09:34 WEST 2015]: Mediablock plugged; initializing...
[Wed Apr 8 12:09:35 WEST 2015]: Serial number changed from 219333 to 218991
[Wed Apr 8 12:09:35 WEST 2015]: Firmware version 21.3s
This failure may also be caused by a faulty motherboard battery, and since the BIOS clock is used as the master clock until the media block is detected (IMB or Dolphin).
In order to fix this issue, please follow the guidelines below:
Open a terminal window and log in as root, or you can ssh into the server and log in as root, then type:
# /doremi/etc/init.d/drmldbd.init stop <enter>
# mv /doremi/opt/dbs/doremi.db /doremi/opt/dbs/doremi.db.orig <enter>
# reboot <enter>
The first command above will stop the database daemon temporary, the second we will rename the database file, and the third will reboot the server.
At the next boot, the system will not detect the database file, therefore it will generate a new/clean db file. If the error is solved, then you can delete the back-up/orig file
# rm -f /doremi/opt/dbs/doremi.db.orig
If you have any further questions you may contact the technical support department by creating a ticket on the support portal.
Last Updated on Friday, 24 July 2015 07:09
