nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

what would cause log files to go from 2mb to 300mb?

CRB

hello,
these last couple days, every morning i notice that the log files in the receiver of couple of our deployments went from 3MB to 261MB in one day and no they are on 310MB...

i couldnt see any changes in the deployment job file, it looks the same, i attached the deployment job from the base for you to see it.

so in the receiver the size went up way too large, and in the sender i couldnt see any log files, i only see sender_odbase, and sender_eventreporting.

any ideas wht might caused this problem?
we are on DO 5.6 SP1 and W2K

Find more posts tagged with

Comments

nipper

You are running date different deployments (with deletes turned off) , if you have a lot of non TS content, then you see a lot of

dir/foo.html not found in source deleting... skipped

Those get big quick. Also how often are you running OD ? If you are running a date different deployment within a workflow then you may be running hundreds of deployments a da. If this is the case, change it to filelist deployment

HTH

Andy

CRB

this deployment is scheduled 3 times a day, and it is all static data, like just HTML pages... also this not part of a workflow, it is just kicked off 3 times a day when it is scheduled. also my log rules are

maxBytes="2Mb"
level="verbose"
/>
since the max size is 2MB how does that affect the process since the size is more than 2mb? and if i change the log level from verbose to normal would that help?

but how does that cause log files to not show up in the sender log directory even all OD services are running ? the same thing happend yesterday but when we rebooted the server that has TS and the OD sender, the log files showed up again.
also in the sender_odbase i see alot of:

ENG: 2006-11-14 00:34:16 MST GMT-07:00 ***ERROR - Rcvr read deployment attributes got null, exiting

ENG: 2006-11-14 00:35:16 MST GMT-07:00 Rcvr got request to receive a deployment.
ENG: 2006-11-14 00:35:16 MST GMT-07:00 Rcvr OpenDeploy Version is 5.6.0.1.0

ENG: 2006-11-14 00:35:16 MST GMT-07:00 Rcvr received base version string
ENG: 2006-11-14 00:35:16 MST GMT-07:00 ***ERROR - Rcvr read deployme

CRB

also to answer Nipper: this is what it is in the log file in the receiver, just hundreds of likes that says ... included, or processing ...

so i think your guess is correct here? that the html content are causing too much loggin? if i change the level of logging from verbose ro normal, would it avoid this kid of long long logs of each deployment?...

LIB: (3) id=0 2006-11-15 12:45:04 Path(.\images\CompMktOffer_WashDC_Showtime_2.JPG) included.
LIB: (3) id=0 2006-11-15 12:45:04 Path(.\images\Config-images) included.
LIB: (3) id=0 2006-11-15 12:45:04 Path(.\images\congratulations_dtv.jpg) included.
LIB: (3) id=0 2006-11-15 12:45:04 Path(.\images\conn_coax.jpg) included.
LIB: (3) id=0 2006-11-15 12:45:04 Path(.\images\conn_component.jpg) included.
LIB: (3) id=0 2006-11-15 12:45:04 Path(.\images\conn_dvi2.jpg) included.
LIB: (3) id=0 2006-11-15 12:45:04 Path(.\images\conn_hdmi.jpg) included.
LIB: (3) id=0 2006-11-15 12:45:04 Path(.\images\conn_hdmi2dvi.jpg) included.
LIB: (3) id=0 2006-11-15 12:45:04 Path(.\images\conn_optical2.jpg) included.
LIB: (3) id=0 2006-11-15 12:45:04 Path(.\images\conn_rca.jpg) included.
-------------------------------------------
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\cti\XTRAS\FLASHASSET)
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\odev85\certificate\images)
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\odev85\help\getting_started)
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\odev85\help\images)
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\odev85\help\introduction)
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\odev85\help\using_the_ondemand_ player)
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\odev85\help\whdata)
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\odev85\help\whgdata)
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\odev85\help\whxdata)
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\odev85\preferences\images)
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\odev85\querydb\ctxex)
LIB: (3) id=0 2006-11-15 12:53:55 Processing excluded directory for (.\cbt\prod\conted\odev85\querydb\ctxod)

nipper

Certainly try changing the log level from verbose. I also noticed that max log size has no affect. One should file a bug.

Andy

CRB

thank you, but where do i need to change it?
do i change it in the deployment job file? or in the odbase.xml of the sender, or the odbase.xml of the receiver? (the receiver has admin, base, and rcvr no odrcvr.xml though)
the problem that i am having is int he receivers log files(rcvr.deployment.from.to.definition....log) the sender is fine.

it is true the maxbyte doesnt limit the size of the log file and even if it does, it should have an explaination to how it works? some deployment jobs will take longer and will need more space than what maxbyte specifies. so how does OD manage that? does it make part_1, _2 for each log for each deployment job...