When I tried to save the configuration, i can see the following error:
OnlineSW01# commit and-quit error: error copying files (/config/juniper.conf.3.gz->/var/db/config/juniper.conf.4.gz): No such file or directoryerror: rotation of old files failed
root@SW01% cd /configroot@SW01% ls.snap juniper.conf.2.gz ssh_host_dsa_key ssh_host_rsa_key vchassisdb juniper.conf.3.gz ssh_host_dsa_key.pub ssh_host_rsa_key.pubjuniper.conf+.gz juniper.conf.gz ssh_host_key support-filejuniper.conf.1.gz rescue.conf.gz ssh_host_key.pub usage.dbroot@SW01% cd dbroot@SW01% ls -altotal 16drwxr-xr-x 3 root wheel 512 Jan 19 2009 .drwxr-xr-x 5 root wheel 512 Dec 3 16:57 ..-rw-r--r-- 1 root wheel 236 Jan 19 2009 commitsdrwxr-xr-x 2 root wheel 512 Jan 19 2009 configroot@SW01% cd configroot@SW01% lsjuniper.conf.4.gz juniper.conf.6.gz juniper.conf.8.gzjuniper.conf.5.gz juniper.conf.7.gz juniper.conf.9.gz
intadmin@SW01> show configuration | compare rollback 0 ^syntax error.
intadmin@SW01> show configuration | compare rollback 1 ^value 1 is not equal to 0.
intadmin@SW01> show configuration | compare rollback 2 ^value 2 is not equal to 0.
intadmin@SW01> show configuration | compare rollback ? No valid completions
Anyone can advise what happened
Try to apply the commit from the config prompt. Enter cli at %, enter configure, then try to commit.
Great, it worked , Thank you
It sounds like you have run into the PR/460909 caveat. JUNOS release 9.3S6, 9.5S4.1, and 9.6S2.1 are the latest releases for the 9.3, 9.5 and 9.6 trains respectively as of this posting. I hope included references are helpful.
The first publication that I noticed the PR/460909 caveat being published was PSN-2009-07-461.
PR/460909 Commit failed because rotation of configuration files to /var/db/config failed
Committed in JUNOS 9.3R4; 9.4R4; 9.5R3; 9.6R2; 10.0R1
PSN-2009-07-461 JUNOS Service Release Service Release 9.3S4.1 for the EX-Series Switch service impacted issues resolved.
PSN-2009-12-598 JUNOS Service Release 9.3S6 for the EX-series Switch service impacted issues resolved.
PSN-2009-12-600 JUNOS Service Release 9.5S4.1 for EX-Series Switch service impacting issues resolved.
https://www.juniper.net/alerts/viewalert.jsp?actionBtn=Search&txtAlertNumber=PSN-2009-11-581&viewMode=view" target="_blank" title="PSN-2009-11-581" rel="nofollow noopener noreferrer">PSN-2009-11-581 JUNOS Service Release 9.6S2.1 for EX-Series Switch service impacting issues resolved.
Im running 11.4R2.14 and Im having this issue. What can I do to fix this???
Did you see this KB?
Can you please tell me how did you run into this? Was it after upgrade?
I upgraded the OS from 9.2R3.5 to 10.0R2.10 but same erros occurs again.
admin@SW> show system snapshot media internalInformation for snapshot on internal (da0s1)Creation date: Jan 15 06:55:54 2009JUNOS version on snapshot: jbase : 9.2R3.5 jcrypto-ex: 9.2R3.5 jdocs-ex: 9.2R3.5 jkernel-ex: 9.2R3.5 jroute-ex: 9.2R3.5 jswitch-ex: 9.2R3.5 jweb-ex: 9.2R3.5 jpfe-ex42x: 9.2R3.5admin@SW> show versionHostname: -SWModel: ex3200-24tJUNOS Base OS boot [10.0R2.10]JUNOS Base OS Software Suite [10.0R2.10]JUNOS Kernel Software Suite [10.0R2.10]JUNOS Crypto Software Suite [10.0R2.10]JUNOS Online Documentation [10.0R2.10]JUNOS Enterprise Software Suite [10.0R2.10]JUNOS Packet Forwarding Engine Enterprise Software Suite [10.0R2.10]JUNOS Routing Software Suite [10.0R2.10]JUNOS Web Management [10.0R2.10]admin@SW>editadmin@# commiterror: error copying files (/config/juniper.conf.3.gz->/var/db/config/juniper.conf.4.gz): No such file or directoryerror: rotation of old files failedPls guide
I'm not exactly sure what went wrong, but you can fix this easily by dropping into the shell as root (start shell root) followed by the command "mkdir /var/db/config/"
Pls check and comment
root@-SW:RE:0% mkdir /var/db/configmkdir: /var/db/config: File existsroot@-SW:RE:0%
is there already a symbolic link perhaps?
It could be a typo while following the previously referenced KB with an invalid pointer, which could explain the error.
Sorry i didnt get you , if you can explain what "" symbolic link "" you are pointing to.
I had this issue on EX-8208 with dual RE and as per KB24760 implemented the workaround but it did not help me... I was still getting the commit sync problem.
The current Junos version is 10.1R1.8. The workaround mentioned in earlier posts or the KB does a soft linking but when it did not work for me, a hard link will be done as per Linux process.
Now the switch is taking 'commit sync' command wihtout any issue.
the workaround mention that the db/config did not exist initially and when the soft linking was done, it gives in output.
user@switch>start shell user rootuser@switch%user@switch% ls -ld db/configls: db/config: No such file or directoryuser@switch%
In my case. this file was already created and so, gave the alert as
root@OKH-EX8208-SW1:RE:0% ls -ld db/configlrwxr-xr-x 1 root wheel 17 Mar 24 2010 /var/db/config -> /config/db/configroot@OKH-EX8208-SW1:RE:0% cd /var/db/root@OKH-EX8208-SW1:RE:0% ln -s /config/db/config . ln: ./config: File existsroot@OKH-EX8208-SW1:RE:0% ln -s /config/db/commits . ln: ./commits: File exists
Why is this so?? This workaround this did not work for me in spite of its exact match with my issue.
user@switch>start shell user root
user@switch% ls -ld db/config
You are in /var/home/user folder. Command "ls -ld /var/db/config" should be the one you expected. Try "cd /var/db" and see if it works.
Ckim, the /var/home/user is visible in the workaround excample which JTAC has mentioned in their KB but I have tried with the /var/db/config directory but it didn't help me either.
You may go through the log file attached in my post... Please suggest if you find something there..
Pardon my ignorance here, and I truly when it comes to linux file system, but any special reason why the files stored in the directory "/var/db/config" need to be linked to "config -> /config/db/config"
error copying files (/config/juniper.conf.3.gz->/var/db/config/juniper.conf.4.gz): No such file or directory
error: remote commit-configuration failed on re1
config -> /config/db/config
I think the way you are creating a link is making the system thinks the link is back to the same directory hence it creates an infinite loop when it does the path lookup. If you simply remove any links you have created and allow the system to do its own thing, does it work? Also >show log dcd, it may have something in it too.use the command rm -r /path/folder to remove the symlinks you have created then test it.
I have the plan for upgrade but the upgrade process may require the commit sync command at some instances so I want to resolve the issue first and then go for the upgrade.
If JTAC has given some workaround then I expect it to work. Shouldn't we?