sql log file growing quickly till dusk is full. ePO

First, in order to prevent worst issues, move the log to a Disk with more space available. Open the SQL Profiler to investigate what's running on your SQL/DB.

ePO 5.1 is EOL since end 2017. No chance to update it?

Can you reboot the server?

Can you stop ePO? Will the log stop filling up the disk after that?

Anything useful in ePO logs why it might be happening?

hi thanks.

it was on a 10gb drive now upped to 50.     I’m not wanting to let it grow.  the growth is not normal.   it ran fine for a few months. with logs been a few mb.      it’s 5.10.  not 5.1.
yes can reboot/stop epo.    yes. it stops growing. but expected it’s the epodb log file
no nothing in log files   or sql traces.    if it were the db growing it would be easier but it’s just this log file.

also a new build.  (exactly same it’s an automated build) and it doesn’t start growing yet.  but did take a couple of months before this issue presented its self.

What is filling up the log file?

So you rebooted the server?

also a new build.

Not catching on this. New build of ePO?

it’s been on going for months. rebooted lots of times.  don’t know what’s filling up the log that’s half the problem 😊.
rebuild.   =. I have several environments. it’s the same build but built multiple times.   so the same set up has been built from scratch. and fine for a month or so then this log issue starts.

 but now the log file of epo_db. grows at 1gb a minute till it fills the disk

That's almost certainly some type of run-away / looping process.

Traces aren't normally needed that much anymore, but it would probably be a good idea to do one here.  You should be able to see the bad process that is just running over and over, when it shouldn't, then correct it.

Something had to change in ePO / for ePO. Have you made any changes recently? First, you need to investigate what is causing the issue, then you can take an appropriate action. Windows event log, ePO event log... You need to get more information first. Also, I am not sure how difficult is to reinstall and set up ePO again but I'd consider it as an option too.

How to troubleshoot a full ePolicy Orchestrator database:
https://kc.mcafee.com/corporate/index?page=content&id=KB90100

Please check out this too. This link might be irrelevant but might tell you something.
https://www.mssqltips.com/sqlservertip/2092/sql-server-transaction-log-grows-and-fills-up-drive/

the logs are (on apperance normal ). this is a reinstall.  I have epo on multiple rigs.  after a month or three they all start to grow this log.    the database is fine and with in normal size it’s just the log file that grows

the links you sent are very similar. and I do see transactions and sps that tie in but they are supposed to be working.  I just can’t see why they are being run to the point everything fills up so quick

this is a reinstall.

So you reinstalled ePO and the issue is still there?

If ePO is working fine and there are no warnings in logs, I'd create a task in Task Scheduler to delete the log every 15/30/60 minutes, depends on you. As a workaround.

I am a bit confused. What kind of log is growing? If the transaction log:

Use the Simple recovery model for your database. The Simple recovery model allows SQL to manage the transaction log for you, which avoids future transaction log growth.

only changes are the dat files every few days.   no new clients config changes or software since it stopped working properly

Well, to sum this up.

ePO is working fine. Correct?
ePO database is working fine. Correct?
ePO database doesn't grow. Correct?
Only a log file is growing. Correct?
Anything else is messed up?

What is the path to the log file which is growing? What is the exact name of the log file?

it is the normal sql log  that accompanies the database. it is in Simple mode.   epodb_log.  path is just the long sql server default oaths for logs

sum up. correct in all those assumptions     well epo stops when the disk fills up
did try shrink rather than delete.   but often it’s busy so can’t.

update not a fix.    it stoped growing   I did disable all jobs.   shrunk db and logs.  then enabled a few jobs every few days see if I could spot one to blame.   but they all went back on with out growing the log.       the built in db index grew about 700 mb but that’s nothing   I haven’t actually changed anything.  configure is the same. just had some disable enable moments. in between.   bit concerned I didn’t have a cause in cases it happens in the customers site

Ok. Just monitor it and you will see.

i have three test rigs all separate. it happend in two of them.    o e I rebuilt. and it hasn’t happened again the other seems to have resolved itself.     they are built and configured the same.      the third one never had an issue.