Forum Discussion
UCS saving process failed. How to resolve the UCS error
UCS saving process failed. F5 version 11.1.0. How to resolve the UCS error. Please find the error below
Operation Status Saving active configuration... tar: root/.tmsh-history-corporate\bhagwan.kanna: Cannot stat: No such file or directory tar: Error exit delayed from previous errors Fatal: executing: tar --no-recursion -rf /var/tmp/im2015/configsync-2.0-1-Linux-2.6.3271.18.2.6.5.8664.im --files-from=/tmp/im.2104/Files Operation aborted. /tmp/configsync.spec: Error creating package
WARNING:There are error(s) during saving. Not everything was saved. Be very careful when using this saved file!
Error creating package Error during config save. Unexpected Error: UCS saving process failed.
7 Replies
natheCirrocumulus
My first thought would be is their sufficient storage to save the ucs file? See this doc too: http://support.f5.com/kb/en-us/solutions/public/14000/400/sol14403.html?sr=31851042
dawn_20802Nimbostratus
I'm experiencing the same problem on 11.2.1. Did a df -i and there is plenty of space. Do you remember what resolved the issue? There doesn't seem to be anything on AskF5. The log file just says that the UCS file create failed. Not terribly helpful. Nothing jumps out on iHealth either.
EmadCirrostratus
What is in LTM log
- dawn_20802
The log was super helpful :) Nov 16 02:40:38 xxx-xxx-xx01 err tmsh[2233]: 01420006:3: UCS saving process failed. Nov 16 02:42:28 xxx-xxx-xx01 err tmsh[4042]: 01420006:3: UCS saving process failed.
The problem ended up being with how the authentication is done. We have to enter domain\UID to authenticate. That created files /root/.tmsh-history-root-. The "\" was hosing up the archive creation. I ended up fixing the problem by deleting the files that had "\" in the file name. We are working with the AD folks to get rid of the requirement to have the domain explicitly presented during authentication. Good times.
JGCumulonimbus
Thanks for sharing the solution. Have you contacted F5 Support to get a bug id for this?
- dawn_20802
Contacted F5 support, no bug ID was given or requested from Product Development.
- JGNo bug ID, no fix, really.
