This article provides the workaround, when below Warning logs were seen, after uninstalling Junos Openconfig package.
/packages/db/junos-openconfig-x86-32-0.0.0.10-1
Rebuilding schema and Activating configuration...
Event processing process: mgd: warning: ddl_sequence_number_match: sequence numbers don't match
Event processing process: mgd: warning: 2531824958 0
Event processing process: mgd: warning: Database header sequence numbers mismatch for file
Event processing process: '/tmp/eventd-temp-db.cfwHJ'. If a package has just been
Event processing process: added or deleted, please verify and commit the configuration.
Event processing process: UI_DBASE_MISMATCH_SEQUENCE: Database header sequence numbers mismatch for file
Event processing process: <xnm:error xmlns="http://xml.juniper.net/xnm/1.1/xnm" xmlns:xnm="http://xml.juniper.net/xnm/1.1/xnm">
Event processing process: <source-daemon>eventd</source-daemon>
Event processing process: <message>Opening configuration database: Could not open configuration database</message>
Event processing process: </xnm:error>
mgd: error: configuration check-out failed
WARNING: Errors found while loading configuration.
WARNING: Correct the errors and commit the configuration.
Restarting MGD ...
The below mentioned issue might be seen on below release :LAB-re> show version
Hostname: LAB-re
Model: mx960
Junos: 18.2R3-S2.9
You may see the following logs, on deleting the Junos Openconfig package
Deleting package..
Event processing process: '/tmp/eventd-temp-db.p0JKZ'. If a package has just been
Also, below logs would be seen in the messages:
mgd[33816]: %DAEMON-4-UI_DBASE_MISMATCH_SEQUENCE: Database header sequence numbers mismatch for file '/var/run/db/juniper.data'. If a package has just been added or deleted, please verify and commit the configuration.mgd[33816]: %DAEMON-4-UI_DBASE_MISMATCH_SEQUENCE: Database header sequence numbers mismatch for file '/var/run/db/juniper.data'. If a package has just been added or deleted, please verify and commit the configuration.
In order to recover from the situation, We need to perform below steps :
Step 1 : Deactivate [event-options event-scripts] configuration while installing or deleting the open-config package as a precautionary measure as it may help avoiding similar issues.
[edit]
LAB-re# deactivate event-options
LAB-re# commit
commit complete
Step 2 : Delete the Junos Openconfig package For example: LAB-re> request system software delete junos-openconfig NOTICE: Validating configuration against absence of junos-openconfig Initializing... <Snipped> WARNING: cli has been replaced by an updated version: CLI release 18.2R3-S2.9 built by builder on 2019-11-16 03:39:54 UTC Restart cli using the new version ? [yes,no] (yes) Yes -------------------------- Enter Yes here
Step 3 : You need to enter into configuration mode, you may see below prompt. If it's seen we need to enter "yes" at the below prompt.
LAB-re> configure exclusive
warning: ddl_sequence_number_match: sequence numbers don't match
warning: 2531824958 123
warning: 0 2531824958
warning: Database header sequence numbers mismatch for file
'/var/run/db/juniper.db'. If a package has just been
added or deleted, please verify and commit the configuration.
error: Could not initialize database
Database was created by software version:
MGD release 18.2R3-S2.9 built by builder on 2019-11-16 07:12:52 UTC
Current software version:
The database can be re-created with the current software version and
reloaded with the currently committed configuration (using rollback).
Attempt to re-create database? [yes,no] (no) yes
And perform a Blank commit to recover the MGD (Please check by show | compare, there should be no uncommitted configuration)
LAB-re# show | compare
LAB-re#
2023-08-28: Initial version