HSSentry Config?

[TrOjAn]

Is there ANY way at all of changing the timeout value on HSSentry?


Its a bit too strict atm.

TrOjAn

[jstaab]

Since you took the plunge, can you verify that HSSentry can at least be disabled? I'm just curious.

Thanks,
Jesse

[TrOjAn]

Jesse, I have not been able to do that, it rebot my pc 4 times overnight, I have killed the task via taskmanager and the pc has been up for about 6 hours..

TrOjAn

[cd-card-biz]

Since you took the plunge, can you verify that HSSentry can at least be disabled? I'm just curious.

Thanks,
Jesse

No way to disable that I can find, other than a manual kill in task manager.

If you rename or delete hs2sentry.exe HS will detect it is missing on next HS reboot and re-install the file.

[jstaab]

The backup I run at night causes a high CPU utilization during the backup, and if it watches the CPU, it would probably reboot it every night then. Plus, I have a few other things that spike the CPU on occasion as well. I guess if I take the unnecessary plunge to the PRO version, I'll have to come up with a way to kill it as you mentioned, with a script or something.

[Rupp]

This is how it works. HSSentry attempts to communicate with HomeSeer ever 20 seconds. If it gets 7 failures it will reboot the server. These settings are adjustable:

INI setting under Settings: SentryCheckInterval, default value is 20 (seconds)
INI setting also under Settings: SentryErrorCount, default value is 7

You can also look at HS_Sentry.log for information on when the system was rebooted.

If you are seeing issues it indicates to me that something is taxing your CPU so hard that it's blocking HS web server access for a good bit of time. (140 seconds by default).

[TrOjAn]

Thanks for that answer Mr Rupp, thats fine thankyou.

As Ive only been a PRO user for a night it will take some time to sort out what I need, but HSSentry has rebboted a few times, IMO it was not needed, I will make a few adjustments now I knwo how to do it.

TrOjAn

[jstaab]

I was thinking about the possibility about a slow web page load, say, taking a couple of seconds during high CPU times and HSSentry timing out waiting for the page to load. If HttpWebRequest was used to fetch the web page, the default timeout is suppose to be 100 seconds, unless it was overridden in the code...

[cd-card-biz]

These settings are adjustable:

INI setting under Settings: SentryCheckInterval, default value is 20 (seconds)
INI setting also under Settings: SentryErrorCount, default value is 7

Rupp, can I just confirm. The above entries do not exist in my default "settings.ini" file. Are they meant to be to be used only as overrides?

Thanks for the info.

[TrOjAn]

I added those to my settings.ini

TrOjAn

[Rupp]

Rupp, can I just confirm. The above entries do not exist in my default "settings.ini" file. Are they meant to be to be used only as overrides?

Thanks for the info.

Did you copy over your settings.ini file from your backup after installing HSPro? If so this is probably why they are not there. I need to add this to the upgrade process list.

[sdanks]

Just out of curiousity, can you set them to 0 to disable?

[tonlof]

Warning, IP-Binding is not working together with Hs-Sentry if not HS is on the "master ip"

I had IIS & and Homeseer running on same server( both port on 80) with an extra slave ip.

I think hs-sentry only try to talk to localhost. I had a restart every 2,5 minute. (20sec heartbeat x 7times failure)

If homeseer have the master ip with ip-binding and iis the second it would maybe work.

Homeseer must be accessible from http://localhost:Port or http://127.0.0.1ort for hs Sentry to operate.

[cd-card-biz]

Warning, IP-Binding is not working together with Hs-Sentry if not HS is on the "master ip"

I had IIS & and Homeseer running on same server( both port on 80) with an extra slave ip.

I think hs-sentry only try to talk to localhost. I had a restart every 2,5 minute. (20sec heartbeat x 7times failure)

If homeseer have the master ip with ip-binding and iis the second it would maybe work.

Homeseer must be accessible from http://localhost:Port or http://127.0.0.1ort for hs Sentry to operate.

This is exactly what I discovered today. With IP binding, localhost appears to be disabled on the HS box. The web interface then accesses HS through the bound IP (ie http://192.168.xxx.xxx). This does not seem to matter when using Homeseer standard. But with HS Pro which loads hs2sentry.exe, the sentry apparently looks to localhost for the web server. If sentry can't find the web server - it reboots the PC....again and again.

On the web server setup page where it says "strongly recommend no binding" - they mean it!

This has been a two day learning experience for me.

[TrOjAn]

After adding the config lines to the settings.ini file HSSentry has not restarted the pc (its not needed to) so all is good here...

TrOjAn