@Rvtravlr - I have seen this as well, since I upgraded to ZWave .148 in the last couple weeks, I have worked around it by clicking settings triangle just after the firmware one. I thought it had to do with not being on the latest HS version. . .just upgraded to HS3 .379 last night and haven't gone back to check that yet.
Announcement
Collapse
No announcement yet.
Discussions related to HomeSeer Beta builds 3.0.0.369->3.0.0.423
Collapse
X
-
Originally posted by TechFan View Post@Rvtravlr - I have seen this as well, since I upgraded to ZWave .148 in the last couple weeks, I have worked around it by clicking settings triangle just after the firmware one. I thought it had to do with not being on the latest HS version. . .just upgraded to HS3 .379 last night and haven't gone back to check that yet.Michael
Comment
-
Day 5 here on two Homeseer 3 Linux boxes with no issues to report using Homeseer V.379
HSConsole memory on Zee OS is a bit over 100Mb and Pro around 180Mb.
HSPro is running HSTouch. HS3 Lite is not running HSTouch.
Both boxes are now at Mono V.5.4X having updated from Mono V.4.X
No changes from day #1.
Updated Z-Wave plugin from V.148 to V.152.Last edited by Pete; October 27, 2017, 10:33 AM.- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
I thought I would give it a try to go to .379 with my production system. Had .368 running on my test system and did not see much issues.
My production is running on a 5 Watt Zotac Pico system with Windows 10 on it. Not a strong machine, but very energy friendly. It was running on .357 as I skipped .368 seeing all the issues emerging on that version.
Normal behaviour with HS3 .357 on this system was:
- HS3 CPU usage between 6 and 15% Averages around 10%
- HS3 Memory usage growing from 110 Mb to 900 Mb in 20 days (does it already for years)
- HS3 Handles growing from 2000 to 15000 in the same 20 days (does it already for years)
Normally after 20 days the Pico needs a restart as it will crawl by then.
2 days ago I did the upgrade to .379 and did not have a nice start. With the first start the HS3 window just sat there waiting. The log was initialised (I saw the line "Creating ASP.NET application host..." in the log and it just sat there.
I waited for almost 25 minutes and suddenly things started working. But I saw many lags in the events. I have Jon00's network script running here and have set it to allow only one script running at a time. With .379 the script is very often not finishing in time, showing errors like
Code:okt-27 21:01:19 Warning Not running script since its already running: C:\HS3\scripts\Jon00RCCNMHS3_A.vben Single instance option enabled in event properties
From this first start on CPU did not go below 22% usage. Definitly something to worry about! That is doubling the CPU usage?
.357 is already having HSTouch build in, so that is definitly not the cause for CPU rising?
To check is things would change I disabled all suspisious plugins, without real changes. CPU went down to 20%, which is still high.
I then disabled HSTouch and let it run for a few hours. Thsi did not change anything but the handles that went down a bit, but that might also be caused by other processes.
As this was not the issue, I re-enabled HSTouch again. This caused a nice list of 40.000 errors:
Code:[COLOR="Red"]okt-27 20:01:48 HSTouch Server Error Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting... okt-27 20:01:48 HSTouch Server Error Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting... okt-27 20:01:48 HSTouch Server Error Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting... okt-27 20:01:48 HSTouch Server Error Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting... okt-27 20:01:48 HSTouch Server Error Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting... okt-27 20:01:48 HSTouch Server Error Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting... okt-27 20:01:48 HSTouch Server Error Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...[/COLOR]
When HS3 started the CPU usage climbed to 28%.....
I did check on the event reports in the about (sorry forgot to copy that) but all queues were at 0. Ont thing I noticed though is that event threads were at 8 and only 6 were mentioned...
I did let this run overnight till yesterday afternoon Memory usage of HS3 was rising fast, faster then normal and so did handles.
This is where I decided to revert to .357. This beta is not ready for prime time for me yet....
The current about:
Current Date/Time: 28-10-2017 12:16:47
HomeSeer Version: HS3 Pro Edition 3.0.0.357
Operating System: Microsoft Windows 10 Home N - Work Station
System Uptime: 0 Days 15 Hours 17 Minutes 27 Seconds
IP Address: 192.168.192.3
Number of Devices: 650
Number of Events: 346
Available Threads: 400
Enabled Plug-Ins
2.0.47.0: BLBackup
2.0.5.0: BLGarbage
2.0.40.0: BLGData
2.0.12.0: BLRoombaWifi
3.0.0.21: Buienradar
2.0.1.0: JowiHue
3.0.1.109: PHLocation
0.0.0.34: Pushover 3P
1.0.0.5: Restart
30.0.0.35: RFXCOM
3.1.0.22: Sonos
3.1.4.15: SqueezeBox
3.0.0.77: weatherXML
3.0.1.152: Z-Wave
My two cents
Wim-- Wim
Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData
1210 devices/features ---- 392 events ----- 40 scripts
Comment
-
Note this a Homeseer 3 users stuff from the SouthWest.
Current Date/Time: 10/28/2017 8:38:59 AM
HomeSeer Version: HS3 Pro Edition 3.0.0.297
Linux version: Linux Box 4.8.0-59-generic #64-Ubuntu SMP Thu Jun 29 19:38:34 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 54 Days 14 Hours 2 Minutes 51 Seconds
IP Address: 192.168.1.30
Number of Devices: 295
Number of Events: 16
Available Threads: 400
Enabled Plug-Ins
2.0.47.0: BLBackup
3.0.0.18: DirecTV
3.0.0.18: DirecTV
3.0.0.18: DirecTV
3.0.0.18: DirecTV
1.1.11.0: Honeywell WiFi Thermostat
1.1.3.1: JowiHue
2.1.6.0: OpenSprinkler
30.0.0.35: RFXCOM
3.0.1.144: Z-Wave
Hardware Haswell motherboard using an iSeries 3 / 16Gb of memory - multitasking running a Windows Pro 7 Oracle VB, CCTV, music NAS, NAS=8 drives using an LSi controller.
It is running in a compact 8 drive NAS box similiar to my 8 drive NAS box.
Thinking I picked up my NAS box for around $160. (adds were drives, LSi controller, server style power supply).
[ATTACH]64130[/ATTACH]
[ATTACH]64129[/ATTACH]Last edited by Pete; October 28, 2017, 11:21 AM.- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
It appears that the plugin callback queue issue may be a symptom, not a cause. I have RFXCOM disabled, but I enabled DeviceHistory. Overall cpu utilization is normal, and although gradually climbing, memory is still only around 340MB for HS3.
But I still have occasional CPU spikes. They are of two types. One is the HSConsole.exe tasks using over 300% CPU. It can last for about an hour, then goes back to normal. This slows down event processing, but otherwise there doesn't appear to be any other symptom.
The other is what seems to cause, or is related to, the plugin callback queue. It also causes severe slowdown of HS3 processing. The CPU goes up above 200%. More than half of it is IOWAIT, according to webmin. In reading up on troubleshooting IOWAIT issues, I installed iotop. The top two processes in iotop are HSConsole.exe and jdb2, with IO percentages that are much higher than normal (I thought I had snipped a picture of it but can't find it). While this high cpu was going on, the plugin callback queue climbed up above 50,000, but dropped back down to 0 when the CPU dropped back to normal. It happened twice today. This morning it lasted about an hour and a half. This afternoon, about 20 minutes. In both instances the high iowait events were followed about 20 to 30 minutes later by a high cpu event of similar length. The first attachment is the webmin CPU chart from today. The yellow is IOWAIT. The second graphic is the htop from the high cpu event following the first IOWAIT event.
I wrote a script to screen grab the plugin callback queue values one a minute. I log any value over 100. Here is the filtered log from today.
Code:Oct-28 3:52:25 PM GetPluginQ Plugin Callback Queue Count > 100: 9168 Oct-28 3:52:19 PM GetPluginQ Plugin Callback Queue Count > 100: 10608 Oct-28 3:52:11 PM GetPluginQ Plugin Callback Queue Count > 100: 10878 Oct-28 3:52:00 PM GetPluginQ Plugin Callback Queue Count > 100: 9837 Oct-28 3:51:51 PM GetPluginQ Plugin Callback Queue Count > 100: 9370 Oct-28 3:51:42 PM GetPluginQ Plugin Callback Queue Count > 100: 8648 Oct-28 3:51:31 PM GetPluginQ Plugin Callback Queue Count > 100: 8183 Oct-28 3:51:20 PM GetPluginQ Plugin Callback Queue Count > 100: 8756 Oct-28 3:50:33 PM GetPluginQ Plugin Callback Queue Count > 100: 8905 Oct-28 3:47:00 PM GetPluginQ Plugin Callback Queue Count > 100: 8574 Oct-28 3:45:55 PM GetPluginQ Plugin Callback Queue Count > 100: 7712 Oct-28 3:44:30 PM GetPluginQ Plugin Callback Queue Count > 100: 6189 Oct-28 3:43:59 PM GetPluginQ Plugin Callback Queue Count > 100: 5152 Oct-28 3:43:05 PM GetPluginQ Plugin Callback Queue Count > 100: 3131 Oct-28 3:41:50 PM GetPluginQ Plugin Callback Queue Count > 100: 2605 Oct-28 3:39:57 PM GetPluginQ Plugin Callback Queue Count > 100: 2817 Oct-28 3:38:05 PM GetPluginQ Plugin Callback Queue Count > 100: 2471 Oct-28 3:36:10 PM GetPluginQ Plugin Callback Queue Count > 100: 2405 Oct-28 3:34:24 PM GetPluginQ Plugin Callback Queue Count > 100: 1779 Oct-28 3:33:35 PM GetPluginQ Plugin Callback Queue Count > 100: 531 Oct-28 9:15:36 AM GetPluginQ Plugin Callback Queue Count > 100: 18190 Oct-28 9:14:41 AM GetPluginQ Plugin Callback Queue Count > 100: 28506 Oct-28 9:14:26 AM GetPluginQ Plugin Callback Queue Count > 100: 30644 Oct-28 9:14:13 AM GetPluginQ Plugin Callback Queue Count > 100: 32836 Oct-28 9:14:03 AM GetPluginQ Plugin Callback Queue Count > 100: 34840 Oct-28 9:13:53 AM GetPluginQ Plugin Callback Queue Count > 100: 36761 Oct-28 9:13:41 AM GetPluginQ Plugin Callback Queue Count > 100: 38833 Oct-28 9:13:31 AM GetPluginQ Plugin Callback Queue Count > 100: 40773 Oct-28 9:13:21 AM GetPluginQ Plugin Callback Queue Count > 100: 43036 Oct-28 9:13:12 AM GetPluginQ Plugin Callback Queue Count > 100: 45102 Oct-28 9:13:02 AM GetPluginQ Plugin Callback Queue Count > 100: 46725 Oct-28 9:12:53 AM GetPluginQ Plugin Callback Queue Count > 100: 48618 Oct-28 9:12:41 AM GetPluginQ Plugin Callback Queue Count > 100: 49385 Oct-28 9:12:28 AM GetPluginQ Plugin Callback Queue Count > 100: 49890 Oct-28 9:12:16 AM GetPluginQ Plugin Callback Queue Count > 100: 49402 Oct-28 9:12:03 AM GetPluginQ Plugin Callback Queue Count > 100: 50068 Oct-28 9:11:50 AM GetPluginQ Plugin Callback Queue Count > 100: 50534 Oct-28 9:11:39 AM GetPluginQ Plugin Callback Queue Count > 100: 50854 Oct-28 9:11:27 AM GetPluginQ Plugin Callback Queue Count > 100: 51754 Oct-28 9:11:16 AM GetPluginQ Plugin Callback Queue Count > 100: 51927 Oct-28 9:09:59 AM GetPluginQ Plugin Callback Queue Count > 100: 51321 Oct-28 9:09:07 AM GetPluginQ Plugin Callback Queue Count > 100: 50812 Oct-28 9:08:10 AM GetPluginQ Plugin Callback Queue Count > 100: 48574 Oct-28 9:07:05 AM GetPluginQ Plugin Callback Queue Count > 100: 47672 Oct-28 9:06:07 AM GetPluginQ Plugin Callback Queue Count > 100: 46638 Oct-28 9:05:29 AM GetPluginQ Plugin Callback Queue Count > 100: 45999 Oct-28 9:04:54 AM GetPluginQ Plugin Callback Queue Count > 100: 44718 Oct-28 9:03:53 AM GetPluginQ Plugin Callback Queue Count > 100: 43136 Oct-28 9:02:13 AM GetPluginQ Plugin Callback Queue Count > 100: 42750 Oct-28 9:00:15 AM GetPluginQ Plugin Callback Queue Count > 100: 42077 Oct-28 8:58:34 AM GetPluginQ Plugin Callback Queue Count > 100: 41371 Oct-28 8:57:24 AM GetPluginQ Plugin Callback Queue Count > 100: 40032 Oct-28 8:56:12 AM GetPluginQ Plugin Callback Queue Count > 100: 39143 Oct-28 8:55:14 AM GetPluginQ Plugin Callback Queue Count > 100: 37917 Oct-28 8:54:01 AM GetPluginQ Plugin Callback Queue Count > 100: 37183 Oct-28 8:53:02 AM GetPluginQ Plugin Callback Queue Count > 100: 35740 Oct-28 8:51:55 AM GetPluginQ Plugin Callback Queue Count > 100: 35506 Oct-28 8:51:05 AM GetPluginQ Plugin Callback Queue Count > 100: 34582 Oct-28 8:50:05 AM GetPluginQ Plugin Callback Queue Count > 100: 33998 Oct-28 8:49:31 AM GetPluginQ Plugin Callback Queue Count > 100: 33234 Oct-28 8:48:14 AM GetPluginQ Plugin Callback Queue Count > 100: 31634 Oct-28 8:47:32 AM GetPluginQ Plugin Callback Queue Count > 100: 30588 Oct-28 8:46:15 AM GetPluginQ Plugin Callback Queue Count > 100: 30131 Oct-28 8:45:00 AM GetPluginQ Plugin Callback Queue Count > 100: 29183 Oct-28 8:43:27 AM GetPluginQ Plugin Callback Queue Count > 100: 28568 Oct-28 8:42:07 AM GetPluginQ Plugin Callback Queue Count > 100: 27536 Oct-28 8:41:02 AM GetPluginQ Plugin Callback Queue Count > 100: 26731 Oct-28 8:39:56 AM GetPluginQ Plugin Callback Queue Count > 100: 26657 Oct-28 8:38:15 AM GetPluginQ Plugin Callback Queue Count > 100: 26614 Oct-28 8:37:18 AM GetPluginQ Plugin Callback Queue Count > 100: 25198 Oct-28 8:36:12 AM GetPluginQ Plugin Callback Queue Count > 100: 24219 Oct-28 8:35:09 AM GetPluginQ Plugin Callback Queue Count > 100: 23211 Oct-28 8:34:39 AM GetPluginQ Plugin Callback Queue Count > 100: 22678 Oct-28 8:33:29 AM GetPluginQ Plugin Callback Queue Count > 100: 20950 Oct-28 8:32:10 AM GetPluginQ Plugin Callback Queue Count > 100: 20811 Oct-28 8:30:32 AM GetPluginQ Plugin Callback Queue Count > 100: 20091 Oct-28 8:29:59 AM GetPluginQ Plugin Callback Queue Count > 100: 18326 Oct-28 8:28:49 AM GetPluginQ Plugin Callback Queue Count > 100: 19044 Oct-28 8:26:25 AM GetPluginQ Plugin Callback Queue Count > 100: 19366 Oct-28 8:24:30 AM GetPluginQ Plugin Callback Queue Count > 100: 19505 Oct-28 8:22:27 AM GetPluginQ Plugin Callback Queue Count > 100: 18936 Oct-28 8:20:24 AM GetPluginQ Plugin Callback Queue Count > 100: 18419 Oct-28 8:18:00 AM GetPluginQ Plugin Callback Queue Count > 100: 17887 Oct-28 8:16:21 AM GetPluginQ Plugin Callback Queue Count > 100: 17620 Oct-28 8:15:25 AM GetPluginQ Plugin Callback Queue Count > 100: 17077 Oct-28 8:14:21 AM GetPluginQ Plugin Callback Queue Count > 100: 16547 Oct-28 8:13:58 AM GetPluginQ Plugin Callback Queue Count > 100: 15496 Oct-28 8:13:36 AM GetPluginQ Plugin Callback Queue Count > 100: 14879 Oct-28 8:12:47 AM GetPluginQ Plugin Callback Queue Count > 100: 14632 Oct-28 8:12:04 AM GetPluginQ Plugin Callback Queue Count > 100: 13127 Oct-28 8:11:21 AM GetPluginQ Plugin Callback Queue Count > 100: 12581 Oct-28 8:09:50 AM GetPluginQ Plugin Callback Queue Count > 100: 11911 Oct-28 8:08:36 AM GetPluginQ Plugin Callback Queue Count > 100: 11530 Oct-28 8:07:35 AM GetPluginQ Plugin Callback Queue Count > 100: 10605 Oct-28 8:05:33 AM GetPluginQ Plugin Callback Queue Count > 100: 10117 Oct-28 8:04:21 AM GetPluginQ Plugin Callback Queue Count > 100: 9056 Oct-28 8:01:20 AM GetPluginQ Plugin Callback Queue Count > 100: 7789 Oct-28 7:59:31 AM GetPluginQ Plugin Callback Queue Count > 100: 7575 Oct-28 7:57:58 AM GetPluginQ Plugin Callback Queue Count > 100: 7155 Oct-28 7:57:14 AM GetPluginQ Plugin Callback Queue Count > 100: 7880 Oct-28 7:56:30 AM GetPluginQ Plugin Callback Queue Count > 100: 8091 Oct-28 7:55:57 AM GetPluginQ Plugin Callback Queue Count > 100: 7388 Oct-28 7:55:13 AM GetPluginQ Plugin Callback Queue Count > 100: 6295 Oct-28 7:54:22 AM GetPluginQ Plugin Callback Queue Count > 100: 5763 Oct-28 7:54:02 AM GetPluginQ Plugin Callback Queue Count > 100: 4781 Oct-28 7:53:06 AM GetPluginQ Plugin Callback Queue Count > 100: 4129 Oct-28 7:52:02 AM GetPluginQ Plugin Callback Queue Count > 100: 3600 Oct-28 7:50:42 AM GetPluginQ Plugin Callback Queue Count > 100: 3540 Oct-28 7:49:37 AM GetPluginQ Plugin Callback Queue Count > 100: 3342 Oct-28 7:48:37 AM GetPluginQ Plugin Callback Queue Count > 100: 2756 Oct-28 7:47:28 AM GetPluginQ Plugin Callback Queue Count > 100: 1400 Oct-28 7:45:22 AM GetPluginQ Plugin Callback Queue Count > 100: 1145 Oct-28 7:44:20 AM GetPluginQ Plugin Callback Queue Count > 100: 559 Oct-28 7:43:02 AM GetPluginQ Plugin Callback Queue Count > 100: 279
Overall the memory leak issue seems to be much better. I am going to enable more plugins now and see what happens.
Comment
-
I haven't gathered all the nice details, but I do have to add that the latest beta of HS3 and ZWave are not running smoothy for me. I have been running well behind with my updates and decided to get up with the current.
I was running .312 (since March) and ZWave (updated to .14x a few weeks ago to update my ZWave bulbs and then to .148 and .152 since then). But, I also completely rebuilt my Pi2 image on a brand new SanDisk Extreme microSD card (which brought me the newer Mono 4.5.1 and allowed me to run jon00's device grouping script after years of wanting to).
Unforutnately, things are very noticeably slower, by which I mean my 17+ LB60z-1 bulbs are much less responsive. I have a virtual device setup to represent the group of bulbs in one fixture and I have been using the linked device option to trigger the first actual bulb and then down the line with the others in the fixture. Prior to all the updates, bulbs would turn on nearly instantly together with a slight lag once in a while. Now, it is painful to watch as each bulb noticeably turns off individually. . .with the series of lights no consistently getting to all the bulbs in the group. I saw it just a few minutes ago. . .only the first bulb in the chain turned on. . .
I am not sure what exactly might be helpful to identify. . .
I am using a LAN connected Z-Net for my ZWave interface, but that hasn't changed in a long time.
Current Date/Time: 10/28/2017 10:30:41 PM
HomeSeer Version: HS3 Standard Edition 3.0.0.379
Linux version: Linux HomeTrollerZeeS2V2 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux System Uptime: 0 Days 17 Hours 36 Minutes 55 Seconds
IP Address: x.x.x.x
Number of Devices: 238
Number of Events: 258
Available Threads: 386
HSTouch Enabled: True
Event Threads: 1
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
Plugin Callback Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed:
Enabled Plug-Ins
2.0.47.0: BLBackup
3.4.316.2: HSBuddy
30.0.0.33: RFXCOM
3.0.5.5: SDJ-Health
3.0.1.152: Z-Wave
Comment
-
I woke up to a crash this morning..... happened when BLBackup started. I'm running on Win10 Pro version 1703.
Running HS3 v379
Znet on Zwave plugin v130
worked great for a week.... checked task manager every morning and saw no signs of memory leakage.
From the Windows Application Log:
Application: HSPI_BLBackup.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at System.Runtime.Remoting.Messaging.LogicalCallContext.Propaga teIncomingHeadersToCallContext(System.Runtime.Remoting.Messa ging.IMessage)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Syst em.Runtime.Remoting.Proxies.MessageData ByRef, Int32)
at HomeSeerAPI.IHSApplication.WriteLog(System.String, System.String)
at HSPI_BLBackup.BackupFunctions.Perform_Backup()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Obj ect)
at System.Threading.ExecutionContext.RunInternal(System.Threadi ng.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.Execu tionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.Execu tionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Comment
-
This could be a blbackup issue as that is where the crash happened, but it happened when it tried to access the HS log so its possible HS went away first. Can you look at the Windows event log and see if any other exceptions were logged.
Originally posted by Tomgru View PostI woke up to a crash this morning..... happened when BLBackup started. I'm running on Win10 Pro version 1703.
Running HS3 v379
Znet on Zwave plugin v130
worked great for a week.... checked task manager every morning and saw no signs of memory leakage.
From the Windows Application Log:
Application: HSPI_BLBackup.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at System.Runtime.Remoting.Messaging.LogicalCallContext.Propaga teIncomingHeadersToCallContext(System.Runtime.Remoting.Messa ging.IMessage)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Syst em.Runtime.Remoting.Proxies.MessageData ByRef, Int32)
at HomeSeerAPI.IHSApplication.WriteLog(System.String, System.String)
at HSPI_BLBackup.BackupFunctions.Perform_Backup()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Obj ect)
at System.Threading.ExecutionContext.RunInternal(System.Threadi ng.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.Execu tionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.Execu tionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Comment
-
Originally posted by rjh View PostThis could be a blbackup issue as that is where the crash happened, but it happened when it tried to access the HS log so its possible HS went away first. Can you look at the Windows event log and see if any other exceptions were logged.
Power source change.
but nothing else in details
Comment
-
Originally posted by rjh View PostThis could be a blbackup issue as that is where the crash happened, but it happened when it tried to access the HS log so its possible HS went away first. Can you look at the Windows event log and see if any other exceptions were logged.
Comment
-
I can add HSBuddy and EasyTrigger as plugins that cause the callback queue to grow. With HSBuddy, the queue count started to rise immediately. Yesterday I let it go all day, and the queue count went up over 8 million. The HSConsole process got up to 1.6GB of virtual memory and then things started failing, so I restarted HS3. But all day HS3 was working well, some slowness at times, but no failures and no major slowdowns. I've got those two plugins disabled again and so far so good today.
Current Date/Time: 10/31/2017 7:12:42 PM
HomeSeer Version: HS3 Pro Edition 3.0.0.379
Linux version: Linux rpi5855 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux System Uptime: 0 Days 20 Hours 41 Minutes 14 Seconds
IP Address: 192.x.x.x
Number of Devices: 327
Number of Events: 176
Available Threads: 399
HSTouch Enabled: False
Event Threads: 0
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
Plugin Callback Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed:
Enabled Plug-Ins
2.0.70.0: BLSpeech
1.2.0.0: Device History
3.0.1.90: PHLocation
3.0.6413.20219: UltraNetCam3
Remote:
BLLAN
BLRF
JowiHue
Z-Wave
Comment
Comment