This article shows the reason why the mgd fails to load the configuration file and how to resolve it.

@ 1718348391 [2024-06-14 06:59:51 UTC] mgd start
Creating initial configuration:  ...
mgd: error: Cannot open configuration file: /config/juniper.conf <<-------
mgd: warning: activating factory configuration
[1] 13349
mgd: commit complete
@ 1718348404 [2024-06-14 07:00:04 UTC] mgd done


/var/pdb/profile_db initialized

Profile database initialized
lag enhanced disabled 0
No core dumps found.
Prefetching /usr/sbin/rpd ...
Prefetching /usr/libexec64/rpd ...
Prefetching /usr/sbin/lacpd ...
Prefetching /usr/sbin/chassisd ...
Starting jlaunchhelperd.
Invoking jdid_diag_mode_setup.sh on junos
Starting cron.

Fri Jun 14 07:00:06 UTC 2024

FreeBSD/amd64 (Amnesiac) (ttyu0) <<<<<------------------

Failed to open the configuration file

• While the device is booting up after upgrading, it possibly failed to open the configuration file.
• As a result, the device will boot up with factory default configuration.

• It maybe the specific case when the file system in this chassis is corrupted.
• This will prohibit mgd from accessing the config file and hence the device will boot up in Amnesiac mode.

• Sometimes the RE goes bad during the upgrade process, and this will cause the similar signatures and issues.

• When the config is huge, it takes a lot of time to load. The mgd was able to load part of the config and throws similar error for rest.
• Due to partial config, it boots up in Amnesiac mode.

• Reboot the device again to check if it restores and mgd is able to access the config file.
• In Amnesiac mode, login as root, and check the config. If you see partial config loaded, please allow the device sometime to load the full config. Once complete, then reboot the device.
• Try to login from alternate disk to check if that restores the problem.
• If the issue still persists, then file system might be corrupted/ RE might be bad. RMA the RE.