Commit fails on EX Series with the log message error: Init daemon binary /sbin/init not regular file! . Most likely this is due to some file corruption. This article shows how to diagnose the problem and recommends a format install to resolve it.
Init daemon binary /sbin/init not regular file!
When trying to commit on a switch which has some file system corruption, the commit fails.
admin@access11# commit fpc1: configuration check succeeds fpc0: error: Init daemon binary /sbin/init not regular file! error: configuration check-out failed fpc1: error: remote commit-configuration failed on fpc0 error:
commit failed
The possible cause is file system corruption due to ungraceful shutdown.
Use the following commands to see if this is a file system corruption.
root@access11> file show /var/run/dmesg.boot.detail ----Sniffed---- FPC 0: Read-only file system Creating initial configuration... mgd: Running FIPS Self-tests mgd: FIPS Self-tests Passed mgd: error: Init daemon binary /sbin/init not regular file! mgd: error: configuration check-out failed Warning: Commit failed, activating partial configuration. Warning: Edit the router configuration to fix these errors. Setting initial options: debugger_on_panic=NO debugger_on_break=NO --- Sniffed -----
Since this file system is read-only, it is not possible to correct the file. Check the files under directory /sbin to see if the symlink is correct or not.
/sbin
root@switch:RE:0% pwd /sbin root@switch:RE:0% ls -l | grep init lrwxr-xr-x 1 root wheel 29 Nov 30 12:54 init -> /packages/mnt/jbase/sbin/init <<<<< Correct symbol link .
Resolve this issue by performing a format install on the switch. Refer to KB20643 - [EX Switch] Rewrite the entire file system by issuing "install --format" command from "Loader" mode (Format Install) [juniper.net]