
22
Release Note for Cisco ACNS Software, Release 5.5.7
OL-13139-01
Open Caveats in Software Version 5.5.7
• CScsh46848
Symptom: The Content Engine cache process restarts continuously and creates core dumps.
Condition: This problem occurs when ACNS 5.5.5 software is running on a Content Engine with an
external storage array and a CFS partition size that is greater than 440 GB. This defect is not seen
on Content Engines running versions prior to the ACNS 5.5.5 release. This caveat is not seen on on
Content Engines running the ACNS 5.5.5 software that are using the internal disk drives because the
maximum CFS partition size for internal disks is 384 GB.
Workaround: Reduce the CFS partition size to less than 440 GB.
• CSCsi10052
Symptom: A core file is generated in th ftp_ctlpxy.
Condition: The Content Engine is operating as an FTP proxy.
Workaround: None. The process is restarted after a few tries.
• CSCsi47286
Symptom: A cache core file is seen in the /local1/core_dir. The core file is located in
sf_lookup_ldap_groups.
Condition: Smartfilter is enabled.
Workaround: None. The cache process restarts on its own.
• CSCsj07968
Symptom: Database corruption occurs when a large number of Content Engines are added to a new
device group or channel, or are registered to the Content Distribution Manager.
Condition: The site has about 2,200 Content Engines, but the exact number of Content Engines that
cause the database corruption has not been identified yet.
Workaround: Perform database maintenance regularly, and especially before adding Content
Engines to a channel, by using this CLI command: cms database maintenance full
• CSCsj07986
Symptom: An SNMP core file is generated.
Condition: This problem occurs in a lab environment with very little traffic. A MIB walk was done
just before the core was generated.
Workaround: None.
• CSCsj08016
Symptom: The webserver module caused a crash.
Workaround: None.
• CSCsj21531
Symptom: Retrieving objects on HTML pages causes long delays (from 3 to 15 or more seconds).
Condition: This problem occurs when the first configured name server is down and replies with
ICMP unreachable for the DNS queries.
Workaround: Either remove the first name server from the configuration, or fix the server problem.
Kommentare zu diesen Handbüchern