Announcement

Collapse
No announcement yet.

New Error on .460

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #61
    Got to love htop. I learned a lot more about hs3s structure than I did just using ps to look at tasks when I put it in a mode that allows you to see the threads.
    HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
    Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
    IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

    Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
    mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

    Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

    Comment


    • #62
      64 is String change
      2048 is value set
      16384 is run script special (plugin is notified if a string changes and a script was registered to run on the change)

      The next version of HS3 has descriptive names for the event types.

      There is no reason for this queue to fill and I have yet to find out which plugin is causing it. HS simply sends an event to whoever has registered for the event. It would be a plugin registering for this. The plugin should return immediately from this call but it appears some are taking a long time to process. The end result is that the event queue starts to fill.

      I would disable plugins until this stops happening to see which plugins is causing it. I would happy to contact the plugin author.

      In your case the 16384 is a rare event as that is a script that runs when a string changes. I would see which plugin is registering for that event and disable that one first.

      The 500 limit is just a number to keep memory from growing out of control.

      Originally posted by sparkman View Post
      rjh Hi Rich, can you provide clarity as to what the different Types mean in these warning messages? I'm trying to track down which of my plugins could be causing these issues as events and ImperiHome updates don't always seem to happen when they should.

      The last three warnings I received are Type 64, 1024 and 16384, but I also see 32, and 2048. 16384 seems to be the most common one on my system. Can any more debugging info be provided to see what is in the queue? Having an adjustable queue size would be great as well. Is there a reason for the hard limit of 500?

      Thanks
      Al
      Jan-04 11:46:47 AM Warning Dropping event callbacks due to full queue (Type: 64) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
      Jan-04 9:22:39 AM Warning Dropping event callbacks due to full queue (Type: 1024) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
      Jan-04 8:46:12 AM Warning Dropping event callbacks due to full queue (Type: 16384) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
      website | buy now | support | youtube

      Comment


      • #63
        rjh. Thanks Rich. On my system the main culprit appears to be the BLLED plugin. I've been communicating with Blade and he's released a new version which has improved the situation, but not eliminated it. With BLLED disabled, I do still see a few Type 32 messages at startup, but none otherwise. None of the other people that have posted which plugins they are running list BLLED as one of their plugins, so there are other plugins causing issues as well.
        HS 3.0.0.532: 1963 Devices 1141 Events
        Z-Wave 3.0.1.261: 122 Nodes on one Z-Net

        Comment


        • #64
          type 32 does happen a lot, what does it mean?

          Comment


          • #65
            I have been disabling plugins but have not been able to pinpoint a culprit - perhaps it is more than one? My biggest issue is that I cannot consistently reproduce the situation - it doesn't happen at start-up (most of the time) as it does with others. Is there no way to have homeseer point a finger at a misbehaving plugin as an option in the log?

            Comment


            • #66
              Originally posted by simonmason View Post
              I have been disabling plugins but have not been able to pinpoint a culprit - perhaps it is more than one? My biggest issue is that I cannot consistently reproduce the situation - it doesn't happen at start-up (most of the time) as it does with others. Is there no way to have homeseer point a finger at a misbehaving plugin as an option in the log?

              same here. rjh

              Comment


              • #67
                Originally posted by simonmason View Post
                I have been disabling plugins but have not been able to pinpoint a culprit - perhaps it is more than one? My biggest issue is that I cannot consistently reproduce the situation - it doesn't happen at start-up (most of the time) as it does with others. Is there no way to have homeseer point a finger at a misbehaving plugin as an option in the log?
                Its very likely to be more than one, basically all your plugins need to process data faster than HS sends it, or the queue grows and you get the error. Queues generally are either full or empty, its rare to see a queue of 500 'hover' between 2-500. It is normal for the queue to briefly fill because some rare event occurs.

                So that said, one bad plugin can certainly cause this, but so can 8 kinda medium speed ones, that together feel like on bad one. Thats why this is difficult to track down, you an disable one plugin and the problem won't go away unless its a really bad one. CPU usage of the plugins (overall CPU time vs HSconsoles time) is a way to start, the ultimate answer is Rich keeping statistics on each plugin and dumping those when this error occurs.

                Comment


                • #68
                  To complicate things, it is not just which plugins are slow to handle events, but plugins that flood the system with device changes. Media plugins like Sonos continually update multiple devices for each media device as music is played, ie track position. Every plugin registered for events must handle all of these events. Not saying they shouldn't, just that it is the combination of event generators and event handlers.

                  If you run tenScripting with events enabled, you can dynamically watch all of the events being generated.
                  tenholde

                  Comment


                  • #69
                    Is there any way the maximum queue level could be adjusted for those of us who can handle the additional impact on memory? Mine normally runs at 1.3GB, so memory is not an issue here.

                    I have disabled almost every plugin, but still get between 40-50 warnings each time I start HS3.
                    Randy Prade
                    Aurora, CO
                    Prades.net

                    PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

                    Comment


                    • #70
                      Originally posted by rprade View Post
                      Is there any way the maximum queue level could be adjusted for those of us who can handle the additional impact on memory? Mine normally runs at 1.3GB, so memory is not an issue here.

                      I have disabled almost every plugin, but still get between 40-50 warnings each time I start HS3.
                      Same here... I get a similar number every time I restart HomeSeer.
                      Billy Draper

                      Comment


                      • #71
                        Originally posted by rprade View Post
                        Is there any way the maximum queue level could be adjusted for those of us who can handle the additional impact on memory? Mine normally runs at 1.3GB, so memory is not an issue here.

                        I have disabled almost every plugin, but still get between 40-50 warnings each time I start HS3.
                        This is what i implicitly asked for in my #59 post.

                        your suggestion would be the best. But that means a user changeable setting , and the user needs to know what he is doing?

                        Comment


                        • #72
                          You can always have a minimum value to which you cannot set the queue lower. But I agree why limit the upper end within reason unless there is a performance hit if it get too high.
                          HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
                          Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
                          IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

                          Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
                          mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

                          Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

                          Comment


                          • #73
                            Originally posted by MattLau View Post

                            This is what i implicitly asked for in my #59 post.

                            your suggestion would be the best. But that means a user changeable setting , and the user needs to know what he is doing?
                            Therein lies the problem. I would say we have a broad spectrum of HS users represented on these forums. Some clearly have an understanding of what they are doing and others not so much.

                            Randy Prade
                            Aurora, CO
                            Prades.net

                            PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

                            Comment


                            • #74
                              Originally posted by rprade View Post
                              Therein lies the problem. I would say we have a broad spectrum of HS users represented on these forums. Some clearly have an understanding of what they are doing and others not so much.
                              Well said...
                              Billy Draper

                              Comment


                              • #75
                                32 is a config change. I would not think that should happen often as it is normally a change in setup.

                                Originally posted by MattLau View Post
                                type 32 does happen a lot, what does it mean?
                                website | buy now | support | youtube

                                Comment

                                Working...
                                X