#1
|
|||
|
|||
Large database.log file >84GB!
Yep, that is over 84GB in size! I was wondering why my HDD space was disappearing
A bit of searching and it seems the file can just be deleted when JDownloader isn't running. But, before I do delete it I have renamed it to (old_database.log) prior to re-starting JD. Currently the new database.log file is showing zero bytes. Is it really safe to delete the 84GB file? Also, why should it become that large and is there a setting I need to adjust to ensure it doesn't in the future? Thanks. |
#2
|
||||
|
||||
stable log system over writes each time it starts. I'm not sure why it would have reached that sort of size, unless it has been dumping stacks to the log, or that you had debug modes enabled and ran JD for many months but then that's unlikely also.
if you meant to say config/database.script, I've seen those expand very large when corruption takes place
__________________
raztoki @ jDownloader reporter/developer http://svn.jdownloader.org/users/170 Don't fight the system, use it to your advantage. :] Last edited by raztoki; 24.05.2014 at 07:15. |
#3
|
|||
|
|||
It's most definitely the database.log. The database.script is currently around 190MB.
|
#4
|
|||
|
|||
Having deleted the database.log file on 23rd I see that it has returned and has risen to 108GB!
|
#5
|
||||
|
||||
Database.script around 190MB is not normal, too big, and may cause large database.log.
Strange that you can start JD with that size of database.script.
__________________
FAQ: How to upload a Log |
#6
|
||||
|
||||
Enter our support chat, contact coalado on german workdays between 6AM and 6PM.
GreeZ psp
__________________
JD Supporter, Plugin Dev. & Community Manager
Erste Schritte & Tutorials || JDownloader 2 Setup Download |
Thread Tools | |
Display Modes | |
|
|