Skip to main content

Huge monitor.log

Thread needs solution

I noted a significant drop in my free disk space.  Upon examination, I found that the acronis monitor.log was consuming about 80GB of space on the disk!  Checking the beginning and end of the file (more and tail commands since I couldn't read that file into any editor I have), it all seemed to be from a single date.

I deleted the file and it was recreated this morning with 51 error messages similar to below.  Seemed to be about when I restarted my computer this morning from 5:59:18 to 6:00:39 AM

id=1; level=4; module=402; code=1013; date/time=7/8/2018 5:59:18 AM
message=Sync Agent service error. Try to restart your computer.; line_tag=0xCAF802B9A1D5A026
Error_Code=AfUDkgEmoNWhuQL4ylN5bmMgQWdlbnQgc2VydmljZSBlcnJvci4gVHJ5IHRvIHJlc3RhcnQgeW91ciBjb21wdXRlci4AJG1vZHVsZQBBc3luY19hZ2VudF9hcGlfdnNfMjM1MAAkZmlsZQBBazpcMjM1MFxwcm9kdWN0c1xpbWFnZXJcaG9tZVxzeW5jX2FnZW50XGltcGxcYXBpXHN5bmNfYWdlbnRfYXBpX21hbi5jcHAAJGZ1bmMAQVN5bmNBZ2VudEFwaTo6U3luY0FnZW50QXBpTWFuOjpTdGFydExvZ2luU2Vzc2lvbkltcGwAJGxpbmUAToYEAAAAAAAAACMAkgHDnNWhuQL4ylN5bmMgQWdlbnQgc2VydmljZSBlcnJvci4gVHJ5IHRvIHJlc3RhcnQgeW91ciBjb21wdXRlci4AJG1vZHVsZQBBc3luY19hZ2VudF9hcGlfdnNfMjM1MAAkZmlsZQBBazpcMjM1MFxwcm9kdWN0c1xpbWFnZXJcaG9tZVxzeW5jX2FnZW50XGltcGxcYXBpXHN5bmNfYWdlbnRfYXBpX21hbi5jcHAAJGZ1bmMAQWBhbm9ueW1vdXMtbmFtZXNwYWNlJzo6Q29udmVydFJwY0Vycm9yQ29kZQAkbGluZQBOIwEAAAAAAAAA8P8AAPG47WS9/Si9VGhlIFJQQyBzZXJ2ZXIgaXMgdW5hdmFpbGFibGUAY29kZQBOugYHgAAAAAAkbW9kdWxlAEFzeW5jX2FnZW50X2FwaV92c18yMzUwACRmaWxlAEFrOlwyMzUwXGNvbW1vblxlcnJvci5jcHAAJGZ1bmMAQUNvbW1vbjo6RXJyb3I6OkFkZFdpbmRvd3NFcnJvcgAkbGluZQBOMwEAAAAAAAAA
id=2; level=4; module=402; code=35; date/time=7/8/2018 5:59:18 AM
message=Sync Agent service error. Try to restart your computer.; line_tag=0xCAF802B9A1D59CC3; hide=1
id=3; level=4; module=0; code=65520; date/time=7/8/2018 5:59:18 AM
message=The RPC server is unavailable; line_tag=0xBD28FDBD64EDB8F1; hide=1

 

I "disabled" Sync Agent service as I don't use it.  But what might be going on to create an 80GB file (and it appears this was created rather abruptly as there was a sudden drop in disk free space; not a gradual decrement?

I checked the registry entries for "debug" and they appeared to OK

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Acronis\TrueImageHome\Settings\TraceLevel = 2

 

Any other suggestions appreciated.

Thanks.

Ron

0 Users found this helpful

Ron, I have not seen any other reports of such very large log files (monitor or others) for a long time in the forums, so suspect this may have been a one-off event (hope so anyway!).

I have taken a look at my monitor logs for ATI 2018 and see no reference to Sync Agent anymore - this may be related to other changes introduced with 2018 & later versions.

In reply to by truwrikodrorow…

Thank you for responding, Steve.

I was hoping it would be a one time event.  But this morning the file size was maybe 10-15 kb.  I deleted the file (it seemed to be duplicated in two different locations:  C:\ProgramData\Acronis\TrueImageHome\Logs  and also in C:\Users\All Users\Acronis\TrueImageHome\Logs.

By this afternoon the size was up to 2GB!

I had not restarted my computer after disabling Sync Agent service.  So I shut down the computer, deleted the file in Safe Mode, and restarted. I confirmed that Sync Agent service was disabled.  But I'm still getting similar error messages in the file and it still seems to be growing!

Not sure what to do next. I've attached a copy of the file in case that is of any value.  Maybe I missed something in examining it.

 

Attachment Size
454688-149417.zip 3.64 KB

Ron, the messages in the log are typical for your older version of ATI as far as I remember seeing, so I can only suggest trying a Repair install of the ATI application to see if this helps?

To do the Repair install, download the latest / final ATI full installer and install over the top of the existing software without uninstalling anything.

In reply to by truwrikodrorow…

OK, I have reinstalled and run for a few days.  Although the same errors pop up, there do not seem to be as many of them -- certainly not enough to generate an 80GB file in the foreseeable future.

Thank you for the suggestion.

Ron

Ron, thanks for the update, long may things stay good for you!