Link to home
Start Free TrialLog in
Avatar of RandomThoughts
RandomThoughts

asked on

MOSS logs are filled with repetitive messages & take up space

The 12\logs on the server(one of WFE's only) are being filled up with messages like this:
The logs are taking around 60+ GB space for a single day.

OWSTIMER.EXE (0x0704)                   	0x071C	Windows SharePoint Services   	Timer                         	5uuf	Monitorable	The previous instance of the timer job 'Application Server Timer Job', id '{19C28EEA-26CC-4784-9B09-C7540F2C0F3C}' for service '{03DC0298-0924-459E-823F-A00776FAFE50}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs.	
Its happening for the timer jobs : 'Config Refresh', 'Scheduled Approval', 'Workflow', 'Immediate Alerts', 'Variations Propagate Site Job Definition', etc.
Also, all the jobs on the "Timer Job Definitions"  of Central Admin are success.
Platform: Moss 2007 on Win 2008 R2
Avatar of shahzadbux
shahzadbux
Flag of United Kingdom of Great Britain and Northern Ireland image

have you looked at how long these jobs are taking to run? looks like there is a overlap - "Consider increasing the interval between jobs"
Avatar of RandomThoughts
RandomThoughts

ASKER

Set to 4 min using the following command, but no luck.
stsadm -o setproperty -pn job-config-refresh -pv "Every 4 minutes between 0 and 59"
No luck? Meaning u couldn't set the command or it didn't help solve the problem?
Its now set to 4 min, but that didn't help solve the problem. The logs are still growing in size with repititive messages.
how long does the job take to complete?
The logs are really huge up to 1-4GB each file.  In the smallest log file that i could open, i see these messages repeatedly.
ASKER CERTIFIED SOLUTION
Avatar of shahzadbux
shahzadbux
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
All these jobs are admin timer jobs and not ssp timer jobs. I'm not able to see any information that states the job is complete in the logs.

When I tried to delete those specific jobs using stsadm -o deleteconfigurationobject, the operation was successful, but the jobs restarted with different id.
Partial solution