Close

No Response from Sighthound Support

Having trouble with Sighthound Video? Post here for help.

Moderator: Staff

no avatar
Alsaeed
 
Posts: 3
Joined: Fri Aug 11, 2017 8:08 am

No Response from Sighthound Support

by Alsaeed » Sat Aug 12, 2017 7:09 am

Greetings all,

I am a paying and customer and I have been trying to get in touch with Support team through their email without any success.

I am stuck with what seems to be a software bug and I am seeking assistance from support team.

Any suggestion?

Thanks,

User avatar
ryan
 
Posts: 1015
Joined: Wed Aug 25, 2010 2:52 pm
Location: Palo Alto, California

Re: No Response from Sighthound Support

by ryan » Sat Aug 12, 2017 12:59 pm

Hi Alsaeed,

Please check your spam folder in case things wound up there as we've been responding to your emails. Here's the core of what the support staff had to say:

As to the issue itself, the cause is pretty simple: Sighthound Video requires at least 1GB or 256MB per camera, whichever is greater, free on the system drive; otherwise it stops recording of the camera. This is done to prevent filling the drive to capacity, and subsequent data corruption. You’d also need to have an ample amount of space on the video storage location, if different from the system drive.

It seems that in your case system drive is nearly full (only 1001MB is reported free), which is why camera recording is being terminated.
Learn more about Sighthound Video in our support pages - Reference Guide | All Articles
Are you a developer? Check out our cloud APIs - Demo | Docs

no avatar
Alsaeed
 
Posts: 3
Joined: Fri Aug 11, 2017 8:08 am

Re: No Response from Sighthound Support

by Alsaeed » Sun Aug 13, 2017 1:07 pm

Hi Ryan,

Thank you for the hint. In deed, it resolved my problem.

I do have plenty of disk space on system drive. However, I have configured a 1 GB RAM disk for the scratch folder of Sighthound Video to reduce the DISK IO overhead and improve system overall performance. This was working perfectly until version v4.0.4, where I faced the issue. So, based on your hint, I increased the allocated RAM and it worked; although I don't see any increase in the disk space utilization of the scratch folder. It looks like that you changed something to do with disk space housekeeping algorithm in v4.0.4 onward.

On the other hand, I recommend to consider having an option to use the system RAM instead of disks for the scratch folder because it helps to improve system performance by reducing disk IO operations and save the disk life especially in case of SSD.

Unfortunately, I haven't received your responses and I not sure what is wrong.Nevertheless, the issue is now resolved. Thank you :)


Return to Technical Support