Fubduck
Getting the hang of it
Hello BI newbie here so please be gentle.
New to BI for a little over a week. I have seen the following warning/error several times in the log:
1 7/27/2018 3:55:02 PM Clips MoveFile 2: R:\BlueIris\New\ptz1.20180726_162712.bvr
1 7/27/2018 3:55:02 PM Clips MoveFile 2: R:\BlueIris\New\East.20180726_162712.bvr
1 7/26/2018 7:24:52 AM Clips MoveFile 2: R:\BlueIris\New\ptz1.20180725_094031.bvr
1 7/26/2018 7:24:52 AM Clips MoveFile 2: R:\BlueIris\New\East.20180725_094031.bvr
There are more messages than these but they all follow the same pattern.
My file movement is as follows: 1 hour long recordings are saved to a dedicated 120GB SSD with 100GB allocated for the New folder. When the New folder is full the files are moved to a dedicated 4TB WD purple drive with 3600GB allocated for the Storage folder. When Storage is full the files will be deleted.
I use the default naming format of &CAM.%Y%m%d_%H%M%S
When I look on my storage drive the errored files are "kind of" there and have been moved from the New files drive to the Stored files drive. The only difference is that the filenames are off by 1 second in the naming.
For the first pair of messages above the file names are as follows:
ptz1.20180726_162713.bvr
East.20180726_162713.bvr
For the second pair of messages:
ptz1.20180725_094032.bvr
East.20180725_094032.bvr
The files throwing the errors are not full 1 hour files. I think they are partial files because of BI being restarted.
2 7/26/2018 4:27:10 PM App Restarted after unexpected shutdown
2 7/25/2018 9:40:29 AM App Restarted after unexpected shutdown
I am not sure how I was stopping and starting BI that caused the unexpected shutdown.
I saw in a thread from almost 2 years ago that the MoveFile 2 warning means the file is not found.
Other thread link -> Strange MoveFile warning. What does it mean?
As mentioned in that thread I have done a database Repair/Regenerate and I have not manually deleted any of the files in question.
My BI install is a full registered version, running the latest version 4.7.6.11 x64, and appears to be working just fine.
I am not sure if this is a serious issue or not.
Thanks
New to BI for a little over a week. I have seen the following warning/error several times in the log:
1 7/27/2018 3:55:02 PM Clips MoveFile 2: R:\BlueIris\New\ptz1.20180726_162712.bvr
1 7/27/2018 3:55:02 PM Clips MoveFile 2: R:\BlueIris\New\East.20180726_162712.bvr
1 7/26/2018 7:24:52 AM Clips MoveFile 2: R:\BlueIris\New\ptz1.20180725_094031.bvr
1 7/26/2018 7:24:52 AM Clips MoveFile 2: R:\BlueIris\New\East.20180725_094031.bvr
There are more messages than these but they all follow the same pattern.
My file movement is as follows: 1 hour long recordings are saved to a dedicated 120GB SSD with 100GB allocated for the New folder. When the New folder is full the files are moved to a dedicated 4TB WD purple drive with 3600GB allocated for the Storage folder. When Storage is full the files will be deleted.
I use the default naming format of &CAM.%Y%m%d_%H%M%S
When I look on my storage drive the errored files are "kind of" there and have been moved from the New files drive to the Stored files drive. The only difference is that the filenames are off by 1 second in the naming.
For the first pair of messages above the file names are as follows:
ptz1.20180726_162713.bvr
East.20180726_162713.bvr
For the second pair of messages:
ptz1.20180725_094032.bvr
East.20180725_094032.bvr
The files throwing the errors are not full 1 hour files. I think they are partial files because of BI being restarted.
2 7/26/2018 4:27:10 PM App Restarted after unexpected shutdown
2 7/25/2018 9:40:29 AM App Restarted after unexpected shutdown
I am not sure how I was stopping and starting BI that caused the unexpected shutdown.
I saw in a thread from almost 2 years ago that the MoveFile 2 warning means the file is not found.
Other thread link -> Strange MoveFile warning. What does it mean?
As mentioned in that thread I have done a database Repair/Regenerate and I have not manually deleted any of the files in question.
My BI install is a full registered version, running the latest version 4.7.6.11 x64, and appears to be working just fine.
I am not sure if this is a serious issue or not.
Thanks
