Below logs might be generated on the device after Managment daemon crash[MGD]

May 31 11:42:43 R1 mgd[73310]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:42:45 R1 mgd[73331]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:43:26 R1 mgd[73351]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:43:30 R1 mgd[73362]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:43:33 R1 mgd[73368]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:43:35 R1 mgd[73374]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:43:36 R1 mgd[73380]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:43:38 R1 mgd[73386]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:43:40 R1 mgd[73392]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:43:42 R1 mgd[73398]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:43:44 R1 mgd[73402]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:43:46 R1 mgd[73423]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:44:43 R1 mgd[73441]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:44:45 R1 mgd[73462]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:45:30 R1 mgd[73487]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed
May 31 11:45:34 R1 mgd[73494]: %DAEMON-0: ../../../../../../src/ui/lib/memory/getmem.c:559: insist '!"mmap: could not remap file"' failed

The logs generally will appear after mgd process crash on the device.

The Log indicates that the config db version has changed probably after some activity and hence the event is logged.
This is mostly mgd process and configuration-specific event and an impact on traffic forwarding is not expected.

This is most likely related to the database corruption issue that occurs when the database is being accessed over 2 or more Netconf channels in parallel. 

The recommendation is to Reboot the device using the command "request system reboot hypervisor" command during an MW. This should re-initialize the database and resolve the database mismatch issue.

2023-30-08 :-  Version 1
2023-09-07:- Version 2