web.log continnually writing

[sub]

I've asked him for more info on what it's doing. It shouldn't be doing that in my opinion. If it is about free space determination he might be able to update it to use the same approach as the modern web app.

[eskimoquin]

Any word from UJB? Three days ago I set the web interface back to modern. Over the weekend, the web.log was still continually written to (when the computer was awake). Today I restarted the recording service but still I see the web.log being written. Fortunately this is nothing compared to what Firefox does with cookies.sqlite-wal but I'd still like to get a handle on it.

[sub]

He said he'll looking into it later, but I didn't hear back. I've emailed a reminder.

[UncleJohnsBand]

Try this....drop it into the public\services folder. I commented out the logging.

Basically what is happening is that the windows based checks to get drive space fail on your drive... you should see the error in the log once the noise is removed. So it falls back to a heavy lift space calculation that basically parses every folder & file on the recording drive and adds up the space being used. Code has been there about 5 years based on source control....but unfortunately I didn't have any notes in regards to exactly why it was added....other than to support drives that would fail.

This page is used by the gadget and was written for the gadget....neither of which I created but I have applied updates over the years.

[eskimoquin]

OK, I replaced the file and restarted. As expected, the web.log is still written to multiple times per minute but there is just less information written. I changed the gadget refresh from 5 min to 10 min but still multiple writes per minute are done and all my recordings are "processed" every refresh (5 or 10 minutes).

I suppose what may help is getting to the bottom of why "windows based checks to get drive space fail on your drive". Primary drive is an SSD but I record to a secondary drive (D:\) which is a traditional HDD. Additionally, I'm not seeing an error in the web.log to indicate these space checks are failing. What is the text indicating this? About the only lines I can see are like this:

Code:

2017-02-06 21:34:59.028    [INFO][21]    Using wmi for free space determination.....
2017-02-06 21:34:59.028    [DEBUG][21]    Root: D:
2017-02-06 21:34:59.028    [DEBUG][21]    Scope: \\.
2017-02-06 21:34:59.028    [DEBUG][21]    Mgmt Obj Scope: \\.\root\cimv2
2017-02-06 21:34:59.028    [DEBUG][21]    Mgmt Obj Path Win32_LogicalDisk.DeviceID="D:"

For reference, in the attached log, the computer was awake for most of the late evening of Feb 7th under the new conditions (10 minute refresh).

Thanks for the help.

[mvallevand]

Try this....drop it into the public\services folder. I commented out the logging.

The logging for me is a small concern it is the useless 10-30 second delays and waking up my NAS drives that frustrates me so I still will need to comment it out.

Martin

[eskimoquin]

As described in post #14-15, any idea why "windows based checks to get drive space fail on your drive"? Any ideas I can start looking into or at least errors that I can track down?

Thanks