topic Re: CSS "commit_redunConfig" error in Application Networking

CSS "commit_redunConfig" error

ggriebel — Thu, 08 Jul 2004 16:34:01 GMT

CSS's running version ap0500108s.

After issuing the commit command get a strange error message - have never seen this before. What does it mean and how to fix or kill the sync that it thinks is going on?

MINAFAP0922# commit_redundConfig "10.11.3.69 -int"

Verifying app and redundancy configs ... -

Previous synchronization still occurring on remote switch.

Re: CSS "commit_redunConfig" error

didyap — Wed, 14 Jul 2004 12:53:39 GMT

Looks like you are hitting the bug CSCdv50232 .

Re: CSS "commit_redunConfig" error

ggriebel — Thu, 15 Jul 2004 13:38:05 GMT

I don't think this is the bug:

The error message comes up right away - not after attempting to sync for a while.

Plus we have much larger configs on other devices and haven't seen anything like this - running same version of code too.

Re: CSS "commit_redunConfig" error

rajnagpal — Thu, 15 Jul 2004 15:36:32 GMT

Hi ggriebel,

"Previous synchronization still occurring on remote switch."

The message would occur because of the following reasons:

1. When you run the script, the software creates a lock file (config_sync_lock) in the script directory so that you cannot run the script from another session to the CSS. If the lock file exists and you run the script, the following message appears:

The script is in use by another session.

If the script terminates abnormally, the software does not remove the lock file. The next time you run the script, the above message appears. If you are certain that the script is not in use by another session, then you can use the -f argument to remove the lock file.

When you run the script with this argument, the following message appears and the script exits:

Config Sync lock file removed.

Now when you see the above message run the script again with the "-d" option, this should resove the issue.

2. First of all check for disk space on the CSS (show disk command) to make sure that there is enough space on the CSS. If there is not enough space on the CSS then it would not allow us to synchronize the configuration.

If running the script with the "-f" option does not seem to remove the lock then you can delete the lock (config_sync_lock) in the following manner.

CSS11150# llama

CSS11150(debug)# ap_file delete c:/ap0500063/script/?

Note: replace ap0500063 with the version of code currently on the CSS

Or remove old software:

CSS11150#config t

CSS11150(config)#boot

CSS11150(config-boot)# remove ?

ap0500207s

ap0500204

ap0610208s.adi.gz

ap0500309

ap0503025s

ap0610203

ap0610205s

CSS11150(config-boot)# remove

Look for the lock file and delete it. Now after deleting the lock file or removing the software, simpy run the script again.

3. In order for the script to work, it needs 4 configuration blocks: Global, Interface, Circuit and one more (group, owner etc.). So check your configuration and if there are only 3 of them then add another block and try the script once again.

Follow the above steps which should resolve your issue.

Regards,

Rajesh Nagpal

Re: CSS "commit_redunConfig" error

ggriebel — Thu, 15 Jul 2004 17:15:08 GMT

Hey Rajesh-

Step 1 worked like a champ - thanks for the info!

greg

Re: CSS "commit_redunConfig" error

rajnagpal — Thu, 15 Jul 2004 18:24:49 GMT

Hi Greg,

Good to know that the first step itself worked.

In future you could refer to the mentioned steps before troubleshooting any further.

Regards,

Rajesh Nagpal