04-25-2011 11:49 PM
hi,
we are using ironport c160 7.0 when we upgrade the ironport to 7.1.2 (inbuild upgrade) we got some mail regading an error
Warning: update - CASE - Error transferring uridb/uridb-20110419_224805.case: Timeout error reading data
when checked the case it is showing that the last date of update is date when ironport was upgraded.
can anyone please advice so that i update the case.
Thanks in advance..
Regards
Omar Fatah
Solved! Go to Solution.
05-23-2011 02:17 PM
As a follow up for those that may be reviewing this thread I wanted to post some additional data.
Since the case was not opened via the threads I will be posting resolution data manually.
We ended up changing the update time out for this system. Network latency appeared to be causing the updates to fail. Given enough time the updates would finish successfully. Normally these settings do not need to be changed and in the event of an update failure the system will continue to try until successful however in this case that was not happening. We were seeing incomplete downloads. The default time out period turned out to be just around the midpoint of the download.
Extending the time out period resolved this and allowed the system to update successfully.
These settings can be modified from the CLI using the command 'updateconfig'
smurf.run> updateconfig
Service (images): Update URL:
------------------------------------------------------------------------------
Sophos Anti-Virus definitions http://downloads.ironport.com/av
IronPort Anti-Spam rules http://downloads.ironport.com/as
Virus Outbreak Filters rules http://downloads.ironport.com/as
Feature Key updates http://downloads.ironport.com/asyncos
McAfee Anti-Virus definitions IronPort Servers
PXE Engine Updates IronPort Servers
IronPort AsyncOS upgrades IronPort Servers
Service (list): Update URL:
------------------------------------------------------------------------------
McAfee Anti-Virus definitions IronPort Servers
PXE Engine Updates IronPort Servers
IronPort AsyncOS upgrades IronPort Servers
Update intervals: 5m, 5m
Proxy server: not enabled
HTTPS Proxy server: not enabled
Choose the operation you want to perform:
- SETUP - Edit update configuration.
04-26-2011 05:14 AM
Hello Omar,
Case updates generally occur every 15 minutes or so. If your seeing a failure to update and your antispam rule sets have not been updated since your install this could be due to a network related issue.
From the CLI you can check the status of the case updates using the command 'antispamstatus'
> antispamstatus
Component Last Update Version
CASE Core Files 30 Jan 2009 03:57 (GMT) 2.7.0-102
Structural Rules 03 Feb 2009 19:47 (GMT) 2.7.0-102-20090203_003604
Content Rules 03 Feb 2009 23:22 (GMT) 20090203_231909
Content Rules Update 03 Feb 2009 23:22 (GMT) 20090203_232104
CASE Utilities 30 Jan 2009 03:52 (GMT) 2.7.0-102
You should see at least 2 items updated in the last half hour.
Case core files and case utilities are typically only updated during an upgrade.
You can force an update from the CLI
You can force an update using the following;
smurf.run> antispamupdate ironport force
Forcing updates for CASE rules.
smurf.run>
04-26-2011 05:36 AM
Hi Christoper,
thank you for the assistance. i did the same as per your last post but it is getting struck after the some update the antivirus is working fine we are able to update the antivirus the only issue is with case update for virus outbreak and anti spam. below is the details during the force update
Tue Apr 26 16:09:59 2011 Info: case antispam - engine (18802) : case-daemon: ser
ver pid: 18802
Tue Apr 26 16:09:59 2011 Info: case antispam - engine (18823) : case-daemon: Ini
tializing Child
Tue Apr 26 16:09:59 2011 Info: case antispam - engine (18824) : case-daemon: Ini
tializing Child
Tue Apr 26 16:09:59 2011 Info: case antispam - engine (18825) : case-daemon: Ini
tializing Child
Tue Apr 26 16:23:55 2011 Info: update - CASE - Update finished after 861.527 sec
Tue Apr 26 16:23:55 2011 Info: update - CASE - Attempting to update: 3600 second
timeout
Tue Apr 26 16:23:55 2011 Info: update - CASE - Starting update
Tue Apr 26 16:23:55 2011 Info: update - CASE - Checking for CASE Update
Tue Apr 26 16:24:09 2011 Info: case antispam - engine (19336) : startup: Region
profile: Using profile global
Tue Apr 26 16:24:09 2011 Info: case antispam - engine (19336) : logger: removing
stderr method
Tue Apr 26 16:24:20 2011 Info: case antispam - engine (19336) : config: Finished
loading configuration
Tue Apr 26 16:24:20 2011 Info: case antispam - engine (19336) : case-daemon: ser
ver started on UNIX domain socket [tmpdir]case_srv.sock (running version 3.0.0)
Tue Apr 26 16:24:20 2011 Info: case antispam - engine (19336) : case-daemon: ser
ver pid: 19336
Tue Apr 26 16:24:20 2011 Info: case antispam - engine (19357) : case-daemon: Ini
tializing Child
Tue Apr 26 16:24:20 2011 Info: case antispam - engine (19358) : case-daemon: Ini
tializing Child
Tue Apr 26 16:24:20 2011 Info: case antispam - engine (19359) : case-daemon: Ini
tializing Child
we are also able to telnet to the downloads.ironport.com.
please advice
Thanks in advance
Omar Fatah
04-26-2011 06:41 AM
Hi Omar,
This appears to be an issue that will require a bit more investigation. I would recommend opening a service request , so we can investigate this further. Support will likely want to access your appliance via the remote access tunnel to trouble shoot this issue.
Christopher C Smith
CSE
Cisco IronPort Customer Support
04-26-2011 07:16 AM
Hi Christoper,
i already opened the case and they are investigating on it. any way thank you for the support. if you get some tips please post to slove it.
Regards
Omar Fatah
04-26-2011 08:50 AM
Hi Omar,
Do you know what the SR number is for your issue?
Christopher C Smith
CSE
Cisco IronPort Customer Support
04-26-2011 09:50 AM
Hi,
The case number is SR 617508993. Expecting further assistance from you.
Regards
Omar Fatah
Case created outside of Forums
05-23-2011 02:17 PM
As a follow up for those that may be reviewing this thread I wanted to post some additional data.
Since the case was not opened via the threads I will be posting resolution data manually.
We ended up changing the update time out for this system. Network latency appeared to be causing the updates to fail. Given enough time the updates would finish successfully. Normally these settings do not need to be changed and in the event of an update failure the system will continue to try until successful however in this case that was not happening. We were seeing incomplete downloads. The default time out period turned out to be just around the midpoint of the download.
Extending the time out period resolved this and allowed the system to update successfully.
These settings can be modified from the CLI using the command 'updateconfig'
smurf.run> updateconfig
Service (images): Update URL:
------------------------------------------------------------------------------
Sophos Anti-Virus definitions http://downloads.ironport.com/av
IronPort Anti-Spam rules http://downloads.ironport.com/as
Virus Outbreak Filters rules http://downloads.ironport.com/as
Feature Key updates http://downloads.ironport.com/asyncos
McAfee Anti-Virus definitions IronPort Servers
PXE Engine Updates IronPort Servers
IronPort AsyncOS upgrades IronPort Servers
Service (list): Update URL:
------------------------------------------------------------------------------
McAfee Anti-Virus definitions IronPort Servers
PXE Engine Updates IronPort Servers
IronPort AsyncOS upgrades IronPort Servers
Update intervals: 5m, 5m
Proxy server: not enabled
HTTPS Proxy server: not enabled
Choose the operation you want to perform:
- SETUP - Edit update configuration.
05-23-2011 10:09 PM
thnak you Smith,
Regards
Omar Fatah
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