This article describes an issue where the device shows a commit failure even though no configuration changes are pending, and logs indicate "libmmf.so.1" not found. This may be related to software corruption, and the article explains how to resolve it.
"libmmf.so.1" not found
When attempting to commit, we receive the following error messages and the commit fails, even though there are no pending configuration changes:
warning: ffp: failed to open shared library: //usr/lib/ffp//libvsyncd-ffp.so: Shared object "libmmf.so.1" not found, required by "libvsyncd-ffp.so"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "rpd"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "dfwd"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "dcd"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "mib2d"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "pfed"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "lacpd"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "jdhcpd"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "bdbrepd"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "authd"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "smid"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "dot1xd"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "l2ald"
ld-elf.so.1: Shared object "libmmf.so.1" not found, required by "l2cpd"
error: configuration check-out failed
This issue may be related to software corruption. You can try the following workarounds to clear the corruption:
Power cycle the unit.
If the device is part of a Virtual Chassis (VC), isolate the member first from the rest of the VC before proceeding with the power cycle.
Format install.
If the power cycle does not resolve the issue, please perform a format install on the device.
There are multiple scenarios in which a device’s software files can become corrupted. If you would like to understand more about this, please visit the following link:
https://supportportal.juniper.net/s/article/Understanding-File-System-Corruption-in-Junos