search

TechieGuy12 / FileWatcher

A file and folder monitor that can send notifications, perform actions, or execute a command when a file or folder is changed.
MIT License
106 stars 27 forks source link

FileWatcher stopped without any message #25

Open maorui2k opened 1 year ago

maorui2k commented 1 year ago

Env: FileWatcher 1.40, WIndows Server 2008R2 64bit The FileWatcher monitored a folder with about 5000 folders and 35000 files, and no more than 200 files/folders would be created every week. But after a few hours or days, the FileWatcher stopped working without any message in the log file or console. This happened several times. Is there anyway to know what's going on?

TechieGuy12 commented 1 year ago

How are you running FileWatcher? As a service, scheduled task or as a process?

maorui2k commented 1 year ago

I tried both service and CLI process, same result.

TechieGuy12 commented 1 year ago

Is there anything in the event viewer? Can you attache the FileWatcher log files?

maorui2k commented 1 year ago

Nothing special in the event viewer, just FW service stop/start which was invoked by me manually.

I uploaded the config & log to Google drive. https://drive.google.com/drive/folders/19lT1hLP6Mw6LQBHBuFmpVeEvuAWdbhoM?usp=sharing

I masked the folder name with a shorter one for security reason. The D:\uploadfile\qualification\ folder has 35000 individual files, and the D:\uplaodfile\entcard\ folder has 5000 sub-folders and each sub folder has 1 to 5 files. I added two new exclusions (.tmp & .bak) just yesterday.

TechieGuy12 commented 1 year ago

As you said, there is nothing in the log file. I'm not sure if the watcher just errored out, or something external stopped it from running.

Can you try creating two watches: one on the D:\uploadfile\qualification and another on the D:\uploadfile\entercard folder, if possible? Just trying to see if that will prevent FileWatcher from exiting.

The largest watch I have right now monitors 85, 135 files and 1,103 folders, 993 GB. So far I haven't had it error/exit out on me.

My only other concern is that you are using Windows 2008 R2. FileWatcher uses .Net 6.0, which doesn't support 2008 R2, nly 2012+, but I am not sure if that is a factor.

maorui2k commented 1 year ago

Sure, I will try two watches. Regarding to .Net 6 with 2008 R2, I didn't notice this limitation, and the installer didn't give me an error... It's not easy to change the OS, maybe it is the very last thing to try.

maorui2k commented 1 year ago

I might find the root cause. Some temp files were deleted after few seconds. FW found these files, but when tried to copy them, the files disappeared, so FW crashed. I modified the conf file to exclude such file, and FW already run for a few weeks without any problem.

TechieGuy12 commented 1 year ago

Thanks for the information. While you have found a solution to your issue, I'll have a look at fixing the issue of preventing FW from crashing if a file was deleted before any action could be taken on the file.