Announcement

Collapse
No announcement yet.

Plugin Crash

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

  • Plugin Crash

    Hi -

    I purchased the Envisalink plugin for my DSC panel. I went away on vacation, and my Homeseer installation stopped responding the second I landed at my destination. It turns out, upon reviewing the logs, that HS3 crashed after the Envisalink plugin crashed. I was wondering if someone could take a look at the events (below) that the plugin generated when it crashed to help me determine how to prevent this in the future.

    Also - is it normal that when the Envisalink plugin crashes, it brings down all of HS3?

    Thanks

    --------------
    Application: HSPI_ENVISALINK.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.NullReferenceException
    Stack:
    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_ENVISALINK.Logger.Log(System.String, ELogLevel)
    at EnvisaLink.Communications.Communicator.ListenForData()
    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()
    ------------
    Faulting application name: HSPI_ENVISALINK.exe, version: 3.0.0.10, time stamp: 0x52bf5f59
    Faulting module name: mscorlib.ni.dll, version: 4.0.30319.18449, time stamp: 0x528fdb6a
    Exception code: 0xc0000005
    Fault offset: 0x00343a42
    Faulting process id: 0xd18
    Faulting application start time: 0x01cf72f613df0533
    Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HSPI_ENVISALINK.exe
    Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\3915 41c89ed7585fc7e8936c43cee387\mscorlib.ni.dll
    Report Id: d48945b7-e144-11e3-be84-6c71d9bd2e62
    --------------
    Fault bucket , type 0
    Event Name: CLR20r3
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: hspi_envisalink.exe
    P2: 3.0.0.10
    P3: 52bf5f59
    P4: mscorlib
    P5: 4.0.30319.18449
    P6: 528fdb6a
    P7: 5721
    P8: 13
    P9: System.NullReferenceException
    P10:

    Attached files:

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_hs pi_envisalink._8f7975e135e960723f33f38979e663777dfb5c_197fcd 6c

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: d48945b7-e144-11e3-be84-6c71d9bd2e62
    Report Status: 4
    ----------------

    Fault bucket 94502165542, type 5
    Event Name: CLR20r3
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: hspi_envisalink.exe
    P2: 3.0.0.10
    P3: 52bf5f59
    P4: mscorlib
    P5: 4.0.30319.18449
    P6: 528fdb6a
    P7: 5721
    P8: 13
    P9: System.NullReferenceException
    P10:

    Attached files:

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ hspi_envisalink._8f7975e135e960723f33f38979e663777dfb5c_18f7 d01c

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: d48945b7-e144-11e3-be84-6c71d9bd2e62
    Report Status: 0

  • #2
    A crash of a plugin should not bring down HS3
    It's hard to tell what exactly happened, but from the call stack you posted, it looks like EnvisaLink tried to log something but somehow the communication with HS3 was broken, so it failed and the plugin crashed.

    My guess is that something wrong happened in HS3, which made it unresponsive, then EnvisaLink crashed when it tried to communicate with it, and then the problem made HS3 crashed itself.

    If you post your HS logs maybe I could do some more investigations.

    Can you replicate this crash?

    Comment


    • #3
      Thanks for getting back to me!
      I pulled the HS3 logs for that timeframe, and they stop just after the Envisalink plugin crashed, but I see no reference to the plugin at all...

      May-21 7:05:22 PM Z-Wave Aeon ZStick: Z-Wave WakeUp Notification Received for Node 3
      May-21 7:05:22 PM Z-Wave Device: 3rd Floor Hallway HomeSeer Tech Luminance Node 3 Child value set to 21 (%)
      May-21 7:05:22 PM Z-Wave Device: 3rd Floor Hallway HomeSeer Tech Battery Node 3 Child Status set to value 66
      May-21 7:01:13 PM Z-Wave Device: 2nd Floor Kitchen HomeSeer Tech Sensor Binary Node 4 Child Status set to ON/OPEN/MOTION
      May-21 7:01:11 PM Z-Wave Aeon ZStick: Z-Wave WakeUp Notification Received for Node 4
      May-21 7:01:11 PM Z-Wave Device: 2nd Floor Kitchen HomeSeer Tech Temperature Node 4 Child value set to 76.7 (F)
      May-21 7:01:11 PM Z-Wave Device: 2nd Floor Kitchen HomeSeer Tech Luminance Node 4 Child value set to 41 (%)
      May-21 7:01:11 PM Z-Wave Device: 2nd Floor Kitchen HomeSeer Tech Sensor Binary Node 4 Child Status set to OFF/CLOSED/NO MOTION
      May-21 6:59:12 PM Z-Wave Aeon ZStick: Z-Wave WakeUp Notification Received for Node 3
      May-21 6:59:12 PM Z-Wave Device: 3rd Floor Hallway HomeSeer Tech Temperature Node 3 Child value set to 79.4 (F)
      May-21 6:59:12 PM Z-Wave Device: 3rd Floor Hallway HomeSeer Tech Battery Node 3 Child Status set to value 67
      May-21 6:55:12 PM Z-Wave Aeon ZStick: Z-Wave WakeUp Notification Received for Node 4
      May-21 6:55:12 PM Z-Wave Device: 2nd Floor Kitchen HomeSeer Tech Luminance Node 4 Child value set to 43 (%)
      May-21 6:53:02 PM Z-Wave Aeon ZStick: Z-Wave WakeUp Notification Received for Node 3

      Comment


      • #4
        nothing interesting in those logs.

        I think the original problem is in HS3, so the best I can do is to try to prevent the plugin from crashing when it happens, but I guess that will not prevent HS3 from crashing.

        How often do you see this crash? Can you replicate it?

        Comment


        • #5
          I will try to replicate - I thought it might be related to a new plugin I added but I see nothing in the logs. I'm going to mess with it tonight.
          I just logged into HS3 to re-enable the suspected plugin and replicate and noticed the Envisalink status says:
          **FATAL**: Failed getting InterfaceStatus from EnvisaLink - the interface was not found in the list of active interfaces.

          Can you help me determine what that means?

          Thanks again for your great support!

          Comment


          • #6
            Actually just noticed plugin was out of date - just updated and seems to be ok now. Still curious as to what that message means.

            Thanks

            Comment


            • #7
              not sure what this means, but I see this as well fairly often when I try to enable a plugin.

              it usually disappear after another try to start the plugin

              Comment

              Working...
              X