Quote from: olegoleg117 on September 03, 2017, 07:51:11 AM

Quote from: crypto_patriot on September 01, 2017, 02:49:52 PM

Quote from: olegoleg117 on September 01, 2017, 02:29:29 PM

Quote from: fromtash on September 01, 2017, 04:26:03 AM

Quote from: mg_home on August 22, 2017, 08:52:15 AM

Quote from: fromtash on August 22, 2017, 07:39:52 AM

Quote from: mg_home on August 21, 2017, 07:27:54 PM

My debug.log size is more than 2GB!

My debug file was 7 GB, but MN works fine. Previous wallet hadn't such issue.

You have the same problem? How did you fix it? And what you mean "Previous wallet hadn't such issue"? I got DAS source from git clone https://github.com/Truckman83/DAS-source

I didn't fix it, just delete debug file manually.
Regarding previous wallet: I mean previous version 0.12.1

my file took up all the free space and stopped MN
30GB
Manually deleted
Really nobody knows how to disable logging?

I believe this was addressed on the DAS Slack for linux. I will look for and repost here. (or you can review the slack yourself)

Not on the DAS Slack for technical advice and communication? Please join now:
https://join.slack.com/t/godas/shared_invite/MjI5OTE5NzkyMDk2LTE1MDM0OTQxMTgtNDEwZGQyM2RjYg

(link expires in 20 days from this date)

Regards,

c_p

In the slack you can see the solution for problem logs only for Linux
I have Windows MN
If you try to delete a file while running MN, it shows that the file is not allowed

Well, yeah. It is constantly being added to. IF you have a debug.log size problem in Win, you can shut down the DAS core, clear the log (edit, select all, delete, save) or copy/paste to a compressed archive then immediately reboot the DAS core while it remains ENABLED. I do this occasionally in less than 2-3 mins and my MNs remain ENABLED. (I *believe* the threshold to remain enabled is 15 mins but I never let keep it down for less than 5 for a system reboot and no more than 15 mins per day to play it safe with MN rewards). This works for me just fine on my local Win servers.

FYI: Every time you restart the DAS core, make sure your bandwidth and CPU use is low/available to allow for the fast re-sync with the DAS network.

Hope this helps.

Regards,

c_p