This Article will explain the reason behind following error, while performing the commit and steps to troubleshoot the issue.
root@device# commit check
error: /config/juniper.conf+: write failed: Broken pipe
error: /config/juniper.conf+: was not properly closed: Broken pipe
error: configuration check-out failed: commit to file failed during export to /config/juniper.conf+
Follow error logs will be seen while performing the commit:
@device> configure
Entering configuration mode
The configuration has been changed but not committed
device# show | compare
error: file copy of database failed
This error message seen during commit is generated when trying to commit a configuration. After this error message is generated, the configuration will not be committed, and you will not be able to proceed further with the configuration.
Cause of this error could be either of following:
Please ask customer to plan a MW to perform below steps:
1. Please run the following command to get the list of files, to clear some space:
>request system storage cleanup dry-run
From the list please remove the unwanted files
2. In case if the above didn't solve the issue, reboot of the RE/device generally resolves the issue, as it will help fix the file system corruption.
>request system reboot
Perform the file system check for any corruptions, refer below KB for the procedure:
https://supportportal.juniper.net/s/article/MX-How-to-repair-a-corrupted-partition-in-a-router-running-Junos-with-FreeBSD-10-kernel-Junos-15-1
3.If the above steps didn’t help to solve the issue, we need to proceed with the RE replacement. This would resolve the issue.
Please reach out to escalation for their feedback, if the above step didn't solve the issue.