01-16-2014 03:46 PM
Thu Jan 16 17:44:31 2014 Warning: Network Participation: failed to connect to host: update-manifests.ironport.com port: 443, error: SSL error: Connection failed: <aplib.dns.SSLConnectError host="update-manifests.ironport.com" port="443" errors=[TimeoutError()]
Thu Jan 16 17:45:01 2014 Info: Failed to acquire the server manifest
01-16-2014 03:47 PM
Looks like it. I just got the same messages...
01-16-2014 03:53 PM
Me too.
01-16-2014 04:05 PM
Yep Appears to be down for me as well.... :-(
01-16-2014 04:43 PM
We are encountering problems with one of our data centers that hosts the update-manifests.ironport.com service. This is also effecting the Cisco Registered Envelope Service (CRES). We are working to resolve this issue as soon as possible.
Best Regards,
John Hess
Escalation Engineer
Content Security Technical Services
US Toll-Free Customer Support: 1-800-553-2447
.:|:.:|:.
c i s c o
01-16-2014 09:11 PM
UPDATE:
The issue has been fixed and connectivity has been restored. All appliances should be able to get udpates.
Regards,
Rehan Latif
Engineer
Content Security Technical Services
US Toll-Free Customer Support: 1-800-553-2447
.:|:.:|:.
c i s c o
01-17-2014 02:19 AM
Hi,
Having problems since the outage. The update process seems to start OK but does nothing.
Fri Jan 17 09:34:00 2014 Info: Scheduled next update to occur at Fri Jan 17 09:39:00 2014
Fri Jan 17 09:39:00 2014 Info: Starting scheduled update
Fri Jan 17 09:39:01 2014 Info: Scheduled next update to occur at Fri Jan 17 09:44:01 2014
Fri Jan 17 09:44:01 2014 Info: Starting scheduled update
Fri Jan 17 09:44:02 2014 Info: Scheduled next update to occur at Fri Jan 17 09:49:02 2014
If I compare it to pre outage.
Thu Jan 16 11:14:30 2014 Info: Starting scheduled update
Thu Jan 16 11:14:32 2014 Info: Acquired server manifest, starting update 21702
Thu Jan 16 11:14:32 2014 Info: Server manifest specified an update for case
Thu Jan 16 11:14:32 2014 Info: case was signalled to start a new update
Thu Jan 16 11:14:32 2014 Info: case processing files from the server manifest
Thu Jan 16 11:14:32 2014 Info: case started downloading files
Thu Jan 16 11:14:32 2014 Info: case waiting on download lock
Thu Jan 16 11:14:32 2014 Info: case acquired download lock
Thu Jan 16 11:14:32 2014 Info: case beginning download of remote file "http://updates.ironport.com/case/1.0/pkg_version/default/1389870826511457"
Any advice?
01-17-2014 05:12 AM
Try running 'antispamupdate ironport force' and 'antivirusupdate force'.
Once you issue those two commands - 'tail updater_logs' and watch the output --- allow it ~2-5 minutes to connect, lock, download, and update...
01-17-2014 06:45 AM
Hi Robert,
I was just about to reply that I remembered those commands from a previous issue and tried running them.
The updates run sucessfully when the force command is issued but the next update fails again.
So as it is I have to manually force an update each time to get the newest CASE and AV files down.
Force manual
Fri Jan 17 11:05:03 2014 Info: case cleaning up base dir [bindir]
Fri Jan 17 11:05:03 2014 Info: case verifying applied files
Fri Jan 17 11:05:03 2014 Info: case updating the client manifes
Fri Jan 17 11:05:04 2014 Info: case update completed
Fri Jan 17 11:05:04 2014 Info: case waiting for new updates
Fri Jan 17 11:09:15 2014 Info: Starting scheduled update
Fri Jan 17 11:09:16 2014 Info: Scheduled next update to occur at Fri Jan 17 11:14:16 2014
Fri Jan 17 11:14:16 2014 Info: Starting scheduled update
Fri Jan 17 11:14:17 2014 Info: Scheduled next update to occur at Fri Jan 17 11:19:17 2014
Fri Jan 17 11:19:17 2014 Info: Starting scheduled update
Fri Jan 17 11:19:19 2014 Info: Scheduled next update to occur at Fri Jan 17 11:24:19 2014
Not resolved unfortunately.
01-17-2014 06:58 AM
I was running into the same issue after the datacenter came back online. Running the following two commands resolved it.
antispamupdate ironport force
antivirusupdate force
01-17-2014 06:59 AM
You can hit me up direct (robsherw@cisco.com) --- if you'd like, let's take this off-forum, and get a case open and tunnel --- I can look, see what may be occurring on back end.
-Robert
01-17-2014 07:10 AM
How can I view the logs Sysadmin at TSSG mentioned?
01-17-2014 07:13 AM
That is just a 'tail updater_logs' --- you'll see the stream of updater activity there.
Issue a 'avupdate force' and 'asupdate ironport force' first --- that way you are assuring that you'll have the service reaching out while tailing the logs.
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