Skip to main content

Okay we have K2 setup and works fine. Over the months i noticed that the log file called HostServer_log of database Hostserver which consist of K2 data keeps increasing rapidly to a point where we are running out of diskspace.


Have no clue why this log files is increasing so quickly and already has reached 14GB.


Any ideas what should be done here?


 


Regards


Sheldon.


 


 

Hi Sheldon,


 


What kind of forms do you user in you organization ?


The K2ServerLog database is larger than K2Server but yours is a little bit too big...


Please read this article to archive K2 databases: http://help.k2.com/en/KB000322.aspx


 


Regards


Benoit


Hi,


This is very strange and uncommon.


The one culprit which might be to blame for this could be the K2 logging. If the archive logging extension is enabled for K2 blackpoint in the HostServerLogging.config file (%K2 blackpoint installation folder%Host ServerBin) then K2 will log to the LogArchive table in the K2HostServer database. If you are logging all information and you have a fairly busy K2 Server then this table might grow to this size. You can reduce the logging level of the Archive Extension or turn it off if you do not want it to log any further.


If it is not the logging framework then it might be something with Roles. I suggest that you run a SQL Profiler Trace on this database to determine what gets called. You might be able to spot why the log file is growing so rapidly.


Depending on your backup strategy you can also switch this database to use the Simple recovery method. This method will truncate the transaction log when a transaction is committed and you will not have this problem anymore.


Hope one of these resolve it!


ok, what i did finally was i took the log file of SQL server offline moved it to another location and re attached. Thats the only solution till now, the logs files still grow.


Reply