WS-SVC-IDS upgrade error

Unanswered Question
Feb 5th, 2007


I am trying to update WS-SVC-IDS from 4.1 to 5.0(1).

The output:

s(config)#upgrade ftp://x.x.x.x/IPS-K9-maj-5.0-1e-S149.rpm.pkg

User: abc

Password: ****

Warning: Executing this command will apply a major version upgrade to the application partition. The system may be rebooted to complete the upgrade.

Continue with upgrade? :

% Please answer 'yes' or 'no'.

Continue with upgrade? : yes

I get the following error:

Error: idsPackageMgr: digital signature of the update file was not valid, use CCO to replace corrupted file

Can anyone help me please?

Thank you!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
wsulym Tue, 02/06/2007 - 04:47

Lets start with the obvious. Does the md5 sum of your download match what is on CCO?

This might be bug CSCsd17267 where the sensor runs out of disk space to fully decrypt and decompress the update file. As a workaround to that, Log in to the sensor via the service account and remove the files in the following directory:


jamesand Tue, 02/06/2007 - 13:46

My guess is that the parentheses in the hostname are causing this failure. We are aware of the slash character in the hostname causing a similar issue. Remove the open and close parenthesis characters from your hostname and re-try the upgrade.

jamesand Tue, 02/06/2007 - 13:52

Disregard the comment about the parenthesis - I misread your example. They are illegal characters for a sensor hostname anyway.

However, it is true that a slash in the hostname will cause this same upgrade error.

dorin.pena Thu, 02/08/2007 - 02:32

The image is according to CCO. I have no files in /usr/cids/idsRoot/var/updates/backups/*.

An output of df command shows that

/dev/hdc1 mounted on / has 357M available and /dev/hdc2 mounted on /usr/cids/idsRoot/var has 12G available.

But the show version command in admin mode shows 97% memory usage, almost 2G.

I restarted the moduled, the memory usage is 5%, the upgrade still doesn't work. The same error.

Thank you!


This Discussion