[goratnik]

I have noticed weird activity from both FaceBook and Instagram plugins:

files accountCheck_facebook.com_jd.plugins.hoster.FaceBookComVideos.log* are generated the whole time, at the rate of around 120MB per day, even when I'm not active, so no idea what it is trying to do - but it's dangerous for drive space; I have noticed this exactly because I ran out of drive space, unexpectedly, as I'm not very active in recent weeks.

The same applies to accountCheck_instagram.com_jd.plugins.hoster.InstaGramCom.log* files, that are generated at the speed of ~40-50MB per day, which makes a constant 1GB/six days of log production even when JDownloader is idle from my point of view.

I have accounts defined and active for both plugins.

[pspzockerscene]

Hi,

1. These logs look to be account check logs.
All enabled && valid accounts are checked every X minutes (default 30 minutes).

2. From your description it looks like these logs also contain the html code of the login processes.
This shall only happen in debug mode.
Make sure that debug mode is disabled, see advanced settings -> Log.debugmodeenabled
If debug logs were enabled before, all logs after disabling it should be much smaller.

3. Logs and "wasted" storage space:
Logs are by default only kept for X days so a constant waste of space will not happen.
However, if you still want to do something to prevent that space from being used, here are your options:
- Disable logging completely: Log.maxlogfilesize -> Set this to a value lower than 100
- or: Configure JD to cleanup logs more frequently e.g. every day, see: https://support.jdownloader.org/know...olders-cleanup

[Jiaz]

@goratnik: Would be good to know if both accounts are active/valid in JDownloader or in error state?

[goratnik]

I have accounts defined and active for both plugins.

Active and valid, yes.

I do have debug mode enabled, but I would rather use it for keeping an eye on results of my own activity, not an automatic production of "idle" logs. I estimate accountCheck* files to be 80% of the total log output at least for me - and this is where I'm concerned, because for example limiting log size could end up rotating out valuable files to replace them with automated junk.

[Jiaz]

@goratnik: Thanks for the feedback. debug means as much and as verbose logs as possible. accounts are getting checked regularly and in this case the responses are quiet large -> resulting in large files/much log data.

Originally Posted by goratnik

I have noticed weird activity from both FaceBook and Instagram plugins:

It's not weird but the facebook index page alone has 3MB of response data. Regular account check every 30 minutes = 48 checks per day * 3 MB = 144 MB of data when the plugin only has to check that page. I've checked other pages, like your own profile, that's also nearly 3MB of response. The settings page has about 2 MB of response. Most likey (not checked) the same reason for instagram.

We're happy to optimize the plugin and use a request that is more lightweight but I have not yet found one. If you know one, please let us know

I would recommend an easy workaround and place the logs folder into a *growing allowed* ramdisk as you system should have plenty of gb of ram and a few mb for logs won't hurt.

Originally Posted by goratnik

files accountCheck_facebook.com_jd.plugins.hoster.FaceBookComVideos.log* are generated the whole time, at the rate of around 120MB per day,
The same applies to accountCheck_instagram.com_jd.plugins.hoster.InstaGramCom.log* files, that are generated at the speed of ~40-50MB per day,

Let's say 200 MB per day, thats 73GB per year if you let JDownloader run 24/7 the complete year. Running JDownloader 10 years without interruption -> less than 1TB written.
Don't understand me wrong but I don't see any reason to act here.
Your browser causes multiple times of that. Chrome can easily cause 1GB/hour in idle. Firfox can cause 10-20GB/day in idle. When watching video/surfing the web, this number can reach 10-100gb/day. A larger windows update can easily reach more than 100gb.