Hi, these messages are due to bug which is resolved (internal PR) , and notcausing any impact and can be ignored.
------------------------------
Anatoliy
------------------------------
Original Message:
Sent: 11-19-2020 00:09
From: Unknown User
Subject: LIBSDB_RSMON_INVALID_PARENT_OFFSET ?
Good day, can anyone explain what the log entries mean, and how to fix it ?
MX204 version 18.2R3-S3.11
Messages
Nov 19 07:45:05 GW-MX204 jdhcpd: LIBSDB_RSMON_INVALID_PARENT_OFFSET: Key(2432696322) points to incorrect parent key(33571209218).
Nov 19 07:45:05 GW-MX204 jdhcpd: LIBSDB_RSMON_INVALID_PARENT_OFFSET: Key(2449473538) points to incorrect parent key(33587986434).
Nov 19 07:45:05 GW-MX204 jdhcpd: LIBSDB_RSMON_INVALID_PARENT_OFFSET: Key(3506438146) points to incorrect parent key(33571209218).
Nov 19 07:45:05 GW-MX204 jdhcpd: LIBSDB_RSMON_INVALID_PARENT_OFFSET: Key(3523215362) points to incorrect parent key(33587986434).
Nov 19 07:45:08 GW-MX204 jdhcpd: LIBSDB_RSMON_INVALID_PARENT_OFFSET: Key(2432696321) points to incorrect parent key(33571209217).
Nov 19 07:45:08 GW-MX204 jdhcpd: LIBSDB_RSMON_INVALID_PARENT_OFFSET: Key(2449473537) points to incorrect parent key(33587986433).
Nov 19 07:45:08 GW-MX204 jdhcpd: LIBSDB_RSMON_INVALID_PARENT_OFFSET: Key(3506438145) points to incorrect parent key(33571209217).