I'd suggest taking a look at the database to see where all of that space is going.

Another place to look is portals/default/log to see if there are large files there. If so, you might want to look at the most recent file to see what is filling the log.

Thanks.

Over 1GB is in my dbo.Exceptions table.  Something with Lucene.net which may be the search provider in DNN core?

How do I stop this from happening going forward?

 

 

 

   at Lucene.Net.Util.BitVector.Get(Int32 bit)
   at Lucene.Net.Index.SegmentTermDocs.ReadNoTf(Int32[] docs, Int32[] freqs, Int32 length)
   at Lucene.Net.Index.SegmentTermDocs.Read(Int32[] docs, Int32[] freqs)
   at Lucene.Net.Search.TermScorer.NextDoc()
   at Lucene.Net.Search.ConstantScoreQuery.ConstantScorer.NextDoc()
   at Lucene.Net.Search.ConjunctionScorer..ctor(Similarity similarity, Scorer[] scorers)
   at Lucene.Net.Search.BooleanScorer2.CountingConjunctionSumScorer(List`1 requiredScorers)
   at Lucene.Net.Search.BooleanScorer2.MakeCountingSumScorerSomeReq()
   at Lucene.Net.Search.BooleanScorer2.MakeCountingSumScorer()
   at Lucene.Net.Search.BooleanScorer2..ctor(Similarity similarity, Int32 minNrShouldMatch, List`1 required, List`1 prohibited, List`1 optional)
   at Lucene.Net.Search.BooleanQuery.BooleanWeight.Scorer(IndexReader reader, Boolean scoreDocsInOrder, Boolean topScorer)
   at Lucene.Net.Index.DocumentsWriter.ApplyDeletes(IndexReader reader, Int32 docIDStart)
   at Lucene.Net.Index.DocumentsWriter.ApplyDeletes(SegmentInfos infos)
   at Lucene.Net.Index.IndexWriter.ApplyDeletes()
   at Lucene.Net.Index.IndexWriter.DoFlushInternal(Boolean flushDocStores, Boolean flushDeletes)
   at Lucene.Net.Index.IndexWriter.DoFlush(Boolean flushDocStores, Boolean flushDeletes)
   at Lucene.Net.Index.IndexWriter.PrepareCommit(IDictionary`2 commitUserData)
   at Lucene.Net.Index.IndexWriter.Commit(IDictionary`2 commitUserData)
   at DotNetNuke.Services.Search.Internals.LuceneControllerImpl.Commit()
   at DotNetNuke.Services.Search.Internals.InternalSearchControllerImpl.Commit()
   at DotNetNuke.Services.Search.SearchEngineScheduler.DoWork()

For my personal tracking, 
I am re-indexing content per this post https://www.dnnsoftware.c...arch-not-working-721

Of note.... when I go to Settings...Site Log, even logged in as a host.. it is blank.
Should there be a module there to view the site log?  mydomain.com/Admin/Site-Log has no modules or content...

 

This github issue may relate

This one and this other one are two with Schedule History issues

Sabastian said this:

if you want to purge the schedule history, you should just execute
TRUNCATE TABLE {databaseOwner}[{objectQualifier}EventLog]
in BersonaBar > Settings > SQL console.

Purging Eventlog is a different task, and due to some changes in DNN 7.4, you may use my TruncateEventlog script (which does not require TurboScripts to be installed). My TurboScripts however try to provide better automated maintenance of the log tables, but require proper application of the scripts (and I am still working on the version for DNN 9.4.x)

https://github.com/dnnsof...Platform/issues/3205

Maybe this can help

Thanks --

Is there no Exceptions log viewer in DNN?  Where I can clear the Exceptions log?

I logged in with SQL studio and ran "TRUNCATE TABLE [databasename].[dbo].[Exceptions]" and now the Exceptions table has 0 records.  

__________________

To identify the table as culprit in SQL Studio... Right Click on the database, Hit Reports... Standard Reports...Disk Usage by Top Tables

Sort by size

_________________

 

My dbo.ScheduleHistory is also large.. but only 5mb.  Is there a way to safely clear this within the DNN GUI?  I hate clearing with scripts that could have unintended consequences...

https://github.com/dnnwer...runcateEventlog2.sql

This should do them all that are needed.  Thanks Sebastian!