log.LiveUpdate log entry question
Over the past couple of days our network management team have come to us say that some of out remote sites are having there network links flooded with LiveUpdate traffic. This has not been a problem in the past only a resent thing, we have had SEP 11 in our environment for 3 years.
On inspection of the Log.LiveUpdate file on the clients which where pulling the updates I noticed the below in the log. I have marked (in Bold) the things that sparked my interest. I have not delved into the Log.LiveUpdate before and would like to know if this is something I should expect or do we have a problem with our LiveUpdate Server?
Should all updates be divided into bandwidth reducing segments? And what criteria do the files need to meet to be divided and is common for the files not to be divided into bandwidth reducing segments?
SEP Environment Details
SEPM Version = 11 RU6 MP3
SEP Client Versions = Ranging from 11 MR2 MP2 --> RU6 MP1
Client OS Version = WinXP
Internal LiveUpdate server.
05/08/2011, 5:16:10 GMT -> Update file 1311125543jtun_nav2k8ennful25.m25 may be divided into bandwidth reducing segments.
05/08/2011, 5:16:10 GMT -> Progress Update: DOWNLOAD_SEGMENT_BATCH_START: Downloading segmented file 1311125543jtun_nav2k8ennful25.m25.full.zip (size 112181174) instead of update file http://liveupdate.sep.<DOMAIN_NAME>.local:9009/clu... (size 131664756)
05/08/2011, 5:16:10 GMT -> Progress Update: DOWNLOAD_SEGMENT_FILE_START: Downloading segment file http://liveupdate.sep.<DOMAIN_NAME>.local:9009/clu... instead of update 1311125543jtun_nav2k8ennful25.m25: file size 3584000
05/08/2011, 5:16:10 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "1311125543jtun_nav2k8ennful25.m25", Estimated Size: 3584000, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
05/08/2011, 5:16:10 GMT -> HttpSendRequest (status 404): Request failed - File does not exist on the server.
05/08/2011, 5:16:10 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "1311125543jtun_nav2k8ennful25.m25", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\1311125543jtun_nav2k8ennful25.m25.seg1.zip" HR: 0x802A0026
05/08/2011, 5:16:10 GMT -> HR 0x802A0026 DECODE: E_HTTP_NOT_FOUND
05/08/2011, 5:16:10 GMT -> Progress Update: DOWNLOAD_SEGMENT_FILE_END: Downloaded file http://liveupdate.sep.<DOMAIN_NAME>.local:9009/clu... instead of update 1311125543jtun_nav2k8ennful25.m25: file size 3584000
05/08/2011, 5:16:10 GMT -> Progress Update: DOWNLOAD_SEGMENT_BATCH_FAILED: Download of segmented file 1311125543jtun_nav2k8ennful25.m25.full.zip (size 131664756) failed. LiveUpdate will download the full update file http://liveupdate.sep.<DOMAIN_NAME>.local:9009/clu... (size 112181174)
05/08/2011, 5:16:10 GMT -> Progress Update: DOWNLOAD_SEGMENT_BATCH_END: Downloaded segmented file 1311125543jtun_nav2k8ennful25.m25.full.zip (size 112181174) instead of update file http://liveupdate.sep.<DOMAIN_NAME>.local:9009/clu... (size 131664756)
05/08/2011, 5:16:10 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "1311125543jtun_nav2k8ennful25.m25", Estimated Size: 131664756, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
05/08/2011, 5:16:10 GMT -> HttpSendRequest (status 200): Request succeeded
05/08/2011, 5:16:28 GMT -> Download complete: Original estimated file size: 131664756; Actual bytes downloaded: 131664756
05/08/2011, 5:16:28 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "1311125543jtun_nav2k8ennful25.m25", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\1311125543jtun_nav2k8ennful25.m25" HR: 0x0
05/08/2011, 5:16:28 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "1312334922jtun_sescwps110802001.x86", Estimated Size: 1065548, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
05/08/2011, 5:16:28 GMT -> HttpSendRequest (status 200): Request succeeded
Comments
hi
The client will not download the entire LU , it would download just the Delta segments (only updates)
This log is normal.
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
Thanks Rafeeq. One quest what
Thanks Rafeeq. One quest what do I look for in the log to see if it is downloading the Delta or entire LU?
What are the typical sizes of the delta? This particular client pulled down ~165Mb LU(size determined via a Riverbed log), I would expect the delta to be smaller than that?
hi
You cannot say what delta would be ; coz it depends of Lu supplied from Symantec.
if you are having group update content distributor that would give you an idea.
https://www-secure.symantec.com/connect/videos/sep-content-distribution-monitor-introduction
check if you have assigned any packages to the group using clients auto upgrade feature
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
Thanks again Rafeeq. No we
Thanks again Rafeeq.
No we don't use GUP's and no we are not using SEPM to deliver uprade package all our updates are done via MS SCCM.
One of my coleagues has a case logged with Symantec Tech support will see what comes of that.
Corrupt defs maybe?
Hi.
Interesting that this happened suddenly to all your clients.
If you've always been using an internal LU server with no GUPs and never had bandwith issues, but now clients are flooding the line, I suspect a corrupt definition was distributed from the LU server.
That's my first though anyway. Are your clients actually updating?
Would you like to reply?
Login or Register to post your comment.