3 Replies Latest reply on Jun 21, 2018 5:22 PM by gmichaud-verreault

    DNP3 Interface keeps dropping

    Koerkel

      We are using a DNP3 interface to retrieve data from the Aclara SMS system that connects to several power line sensors.  This interface starts up fine and works for a few days and then drops.  The errors in the message log file are:

       

      6/15/2018 6:59:55.20795 PM ,Debug ,ID: 8501; Duration: 0. min.; kbytes sent: 4.004883; kbytes recv: 0.734375; app: ; user: ; osuser: ; trust: ; ip address: ; ip host:  ,pinetmgr ,Connection Statistics

      6/15/2018 6:59:55.20793 PM ,Debug ,Deleting connection:  PIDNP3_ReadOnly.exe(7052); Shutdown request received from PIDNP3_ReadOnly.exe(7052); ID: 8501  :0 ,pinetmgr ,

      6/15/2018 6:59:55.20786 PM ,Debug ,ID: 8500; Duration: 0. min.; kbytes sent: 4.004883; kbytes recv: 0.734375; app: ; user: ; osuser: ; trust: ; ip address: ; ip host:  ,pinetmgr ,Connection Statistics

      6/15/2018 6:59:55.20782 PM ,Debug ,Deleting connection:  PIDNP3_ReadOnly.exe(7052); Shutdown request received from PIDNP3_ReadOnly.exe(7052); ID: 8500  :0 ,pinetmgr ,

      6/15/2018 6:59:55.20769 PM ,Debug ,ID: 8499; Duration: 0.9 min.; kbytes sent: 35.45605; kbytes recv: 454.8379; app: ; user: ; osuser: ; trust: ; ip address: ; ip host:  ,pinetmgr ,Connection Statistics

      6/15/2018 6:59:55.20764 PM ,Debug ,Deleting connection:  PIDNP3_ReadOnly.exe(7052); Shutdown request received from PIDNP3_ReadOnly.exe(7052); ID: 8499  :0 ,pinetmgr ,

      6/15/2018 6:59:55.19447 PM ,Information ,Connection accepted:     Process name:  PIDNP3_ReadOnly.exe(7052) ID: 8537 ,pinetmgr ,

      6/15/2018 6:59:55.14616 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

      6/15/2018 6:59:55.14542 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

      6/15/2018 6:59:55.10545 PM ,Information ,Connection accepted:     Process name:  PIDNP3_ReadOnly.exe(7052) ID: 8536 ,pinetmgr ,

      6/15/2018 6:59:55.03683 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

      6/15/2018 6:59:55.03596 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

      6/15/2018 6:59:55.00974 PM ,Information ,Connection accepted:     Process name:  PIDNP3_ReadOnly.exe(7052) ID: 8535 ,pinetmgr ,

      6/15/2018 6:59:54.9429 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

      6/15/2018 6:59:54.94223 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

      6/15/2018 6:59:54.91447 PM ,Information ,Connection accepted:     Process name:  PIDNP3_ReadOnly.exe(7052) ID: 8534 ,pinetmgr ,

      6/15/2018 6:59:54.84909 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

      6/15/2018 6:59:54.84836 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

      6/15/2018 6:59:54.82207 PM ,Information ,Connection accepted:     Process name:  PIDNP3_ReadOnly.exe(7052) ID: 8533 ,pinetmgr ,

      6/15/2018 6:59:54.75539 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

      6/15/2018 6:59:54.75464 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

      6/15/2018 6:59:54.72804 PM ,Information ,Connection accepted:     Process name:  PIDNP3_ReadOnly.exe(7052) ID: 8532 ,pinetmgr ,

      6/15/2018 6:59:54.66144 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

      6/15/2018 6:59:54.6608 PM ,Error ,Failed to start SDKQueue thread ReconnectThread: . Errno was 12; _doserrno was 8 : 0xc ,PIDNP3_ReadOnly ,PISDK

       

      I googled these error message but found nothing helpful.

        • Re: DNP3 Interface keeps dropping
          Steve Boyko

          It's probably best to contact OSIsoft Technical Support to get them involved so they can examine the PI interface machine.

           

          These errors seem very low level, like there is something wrong on the computer itself. In Task Manager can you see if there is sufficient memory remaining? Disk space? Does the problem persist after rebooting the computer?

          • Re: DNP3 Interface keeps dropping
            gmichaud-verreault

            Setting up some performance counters, either via PI Interface for PerfMon or with by setting up a data collector set in perfmon, I would suggest looking at the following:

            • Memory\Committed Bytes
            • Page Faults
            • \Memory\Available Bytes
            • \Process(_Total)\Working Set

            If the problem is still ongoing, then I would look at the task manager as Steve mentioned. Also, if an application is using an absurd amount of memory, and it is a PI application, you could collect a set of successive hang dumps (right click the process -> Capture Hang Dump), and send those to Tech Support with the logs and Counter values, etc.

             

            Additionally, you may find relevant information in the Windows Event Viewer. You may have an application using all the memory and causing the interface and possibly other applications to crash / misbehave.

             

            Gabriel