Announcement

Collapse
No announcement yet.

Log errors - Processing skipped because previous call is still running!

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Log errors - Processing skipped because previous call is still running!

    All of a sudden I'm getting repeating sets of log errors. Any ideas?
    Thanks

    4/12/2023 1:31:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:29:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because the previous call is still running!

    4/12/2023 1:27:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:25:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:23:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:21:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:19:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:17:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:15:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:13:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:11:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:09:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:07:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    4/12/2023 1:05:43 PM
    Legacy-Plugin
    SDJ-Health
    Warning - Processing skipped because previous call is still running!

    ​
    Tags: None
    #2
    I received about 800 of these warnings starting on 4/10 thru 4/11. At the same time, I was noticing a slowdown in Zwave response times. I tried a restart of the Zwave plugin (4.1.1.0) but it didn't help. I then applied the monthly Windows update and rebooted the system and since then I have received 0 warnings. Don't know what caused it or what fixed it (probably the reboot) but it has gone away.
    • Likes 1

    Comment

      #3
      Originally posted by johnpeterson View Post
      I received about 800 of these warnings starting on 4/10 thru 4/11. At the same time, I was noticing a slowdown in Zwave response times. I tried a restart of the Zwave plugin (4.1.1.0) but it didn't help. I then applied the monthly Windows update and rebooted the system and since then I have received 0 warnings. Don't know what caused it or what fixed it (probably the reboot) but it has gone away.
      I've never seen that happen. The log message is every 2 minutes because that will be what you have the refresh interval set to. The plug-in checks that the previous processing has completed before starting afresh. If it hasn't then it aborts until the next refresh cycle with this message. Something must have got stuck, possibly the plug-in waiting for a response from the Z-Wave plug-in, but it could be a lot of things. If it happens again I will investigate further.

      Steve

      Comment

        #4
        Originally posted by SteveMSJ View Post

        I've never seen that happen. The log message is every 2 minutes because that will be what you have the refresh interval set to. The plug-in checks that the previous processing has completed before starting afresh. If it hasn't then it aborts until the next refresh cycle with this message. Something must have got stuck, possibly the plug-in waiting for a response from the Z-Wave plug-in, but it could be a lot of things. If it happens again I will investigate further.

        Steve
        I'm on Linux.

        Comment

          #5
          Originally posted by avpman View Post

          I'm on Linux.
          Try restarting the plug-in and see if it happens again.

          Steve

          Comment

            #6
            Originally posted by SteveMSJ View Post

            Try restarting the plug-in and see if it happens again.

            Steve
            that seemed to have stopped it. I'll keep an eye on it.

            Comment

              #7
              Originally posted by avpman View Post

              that seemed to have stopped it. I'll keep an eye on it.
              Fingers crossed, although two of you experiencing the same issue is unlikely to be a coincidence 🙁
              Steve

              Comment

                #8
                I am seeing this periodically, and have noticed when the plugin is running a status check that I have slow or no zwave response to the point where some events are missed. The cleanup thread takes 30+ seconds. How do I troubleshoot this? HS4 on Windows.
                |
                | - Gordon

                "I'm a Man, but I can change, if I have to, I guess." - Man's Prayer, Possum Lodge, The Red Green Show
                HiddenGemStudio.com - MaineMusicians.org - CunninghamCreativeMaine.website

                Comment

                  #9
                  Originally posted by huggy591 View Post
                  I am seeing this periodically, and have noticed when the plugin is running a status check that I have slow or no zwave response to the point where some events are missed. The cleanup thread takes 30+ seconds. How do I troubleshoot this? HS4 on Windows.
                  This is not something I have been able to recreate and, apart from the three of you in this thread, I haven’t seen any other reports.

                  Try setting the log level to 2 debug, and post or attach the log for 2 minutes running up to the next time you get the error message. Also post your System Profile.

                  Then set the log level back to 1 and restart the plug-in. If that doesn’t cure it, restart HomeSeer and if that doesn’t cure it, restart the computer.

                  Let me know the outcome of the above and I will investigate further.

                  Steve

                  Comment

                    #10
                    FYI - I haven't seen this error since April (reboot). Running HS4 Win10 (4.2.18.15), Zwave (4.1.1.0), and SDJ-Health (3.1.1.4) monitoring 39 battery devices.

                    Comment

                      #11
                      Originally posted by johnpeterson View Post
                      FYI - I haven't seen this error since April (reboot). Running HS4 Win10 (4.2.18.15), Zwave (4.1.1.0), and SDJ-Health (3.1.1.4) monitoring 39 battery devices.
                      Thanks for the update.
                      My suspicion is that it is a symptom of the ZWave pi or HS getting into a high cpu state but I haven’t ruled out it being a bug in SDJ-Health. Either way, it appears to be a fairly rare occurrence.

                      Steve

                      Comment

                      Previous template Next
                      Working...
                      X