Cisco III System Message Guide - Page 240

REGISTRY Messages Chapter 2 Messages and Recovery Procedures REGISTRY Messages This section contains registry-related (REGISTRY) messages. REGISTRY-2 Error Message %REGISTRY-2-REG_FLAG_DEADLOCK: Registry call to [chars] timed out due to deadlock Explanation When a remote registry is not serviced within 25 seconds, the remote process (and presumably the entire system) is deadlocked. This message is printed when the deadlock is broken by a timeout. Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Error Message %REGISTRY-2-REG_PARSE_ERROR: [chars]: Could not parse notification [chars] : error/no. of items = [dec] Explanation The registry library is unable to parse a notification that was received from a name server. This condition might exist for several reasons: - There is a bug in the sscanf function. - The notification block is corrupted. - The pathname published to the name server is invalid. This issue is serious and affects IPC. Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. 2-210 Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY OL-11469-02