01-18-2016 06:57 PM
Hi !
We are constantly receiving this critical message;
The Critical message is:
An application fault occurred: ('screen/AppController.py customActionCheckFailed|849', "<type 'exceptions.TypeError'>", 'actionRestrictedCheckFailed() takes exactly 2 arguments (1 given)', '[util/Aquarium.py screenLoop|408] [util/InternalLibrary.py inverseExtend|328] [util/InternalLibrary.py __call__|769] [screen/Controller.py __call__|23] [util/InternalLibrary.py __call__|769] [screen/CommonController.py __call__|47] [util/InternalLibrary.py __call__|769] [screen/AppController.py __call__|156] [screen/AppController.py _handleActionAllowed|789] [screen/AppController.py customActionCheckFailed|849]')
Version: 7.5.1-028
Serial Number: 0024E87F465B-FC490L1
Timestamp: 15 Jan 2016 15:57:08 +0700
Could anyone explain to me why?
Thanks,
01-19-2016 12:35 PM
https://tools.cisco.com/bugsearch/bug/CSCzv41663
I havent see this on any of code running 9.6 that I am on.
01-19-2016 01:11 PM
Upgrade needed. 7.5.1-028 is not supportable and older build. Your appliance is a C360, and will only go through to 8.5.7-043.
Upgrade path would be:
phoebe-7-5-1-028 --> phoebe-7-5-2-203 --> phoebe-8-0-1-023 --> phoebe-8-5-7-043
Release notes for all versions:
-Robert
01-19-2016 06:16 PM
Hi Robert,
Thank you for you respond. Can I ask you one more thing? What is the meaning of that critical message and why i get it?
Actually, I got this message when a warning message is appear too. This is the warning message that i got.
The case application tried and failed 3 times to successfully complete an update. This may be due to a network configuration issue or temporary outage.
I know that warning message. It means the update anti-spam was failed to successfully complete an update. After that, I try to adjust the timeout period of the anti-spam update and that was works. The warning message doesn't appear anymore until now and also the critical message.
Can you tell me, whether both of two message related or not?
Thanks,
01-21-2016 11:08 AM
Usually seeing "case application tried and failed" is an issue w/ local network/routing when the updater reaches out during specified time frames. You can take a look at the updater_logs to see similar to --->
Mon Jul 21 16:58:49 2014 Warning: case update failed
Mon Jul 21 17:03:49 2014 Warning: case update failed
Mon Jul 21 17:08:49 2014 Warning: case update failed
Mon Jul 21 17:08:51 2014 Warning: case update failed
Mon Jul 21 17:13:51 2014 Warning: case update failed
Mon Jul 21 17:18:51 2014 Warning: case update failed
Mon Jul 21 17:18:52 2014 Warning: case update failed
Mon Jul 21 17:23:52 2014 Warning: case update failed
Mon Jul 21 17:28:52 2014 Warning: case update failed
On older revisions, updater had issues similar to this --- and the solution was to go through and use the static URLs for updates. You can see the following for more information regarding static URLs:
I would recommend to proceed with upgrading and move off of 7.5 family first.
-Robert
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide