cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - You can change your system assigned username to something more personal in your community settings. X

Memory Allocation Error after OPC Network Disconnection

TS_11980678
2-Explorer

Memory Allocation Error after OPC Network Disconnection

Issue Description:

  • Environment:
    • Operating System: Windows Server 2022 Datacenter 64-bit (Build 20348)
    • Instance Type: Amazon EC2 - t3.large
    • Processor: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz (2 CPUs)
    • Memory: 8192MB RAM (8GB)
    • Available Memory: 5999MB
    • DirectX Version: DirectX 12
    • BIOS: Default System BIOS
    • Database: AWS RDS Aurora PostgreSQL
      • Instance Type: Serverless v2
      • Minimum Capacity: 0.5 ACUs (1 GiB)
      • Maximum Capacity: 4 ACUs (8 GiB)
    • Software: KEPServerEX v6.16 (6.16.217.0) - Data Logger Plug-in
    • Log Group: 'TH_SF_BBO_1M'
    • Logger Group Trigger: Static Every 1 minute
    • Number of Items: 236 items
  • Issue Details:
    • The issue occurred after the OPC network connection was lost. When the connection was restored, the logger group attempted to resume recording to the existing table, but encountered the following error:
      {"timestamp":"2024-10-16T03:03:07.401","event":"Error","source":"Data Logger Plug-in","message":"Unable to open recordset on log group 'TH_SF_BBO_1M'. Reason: Out of memory while reading tuples.;memory allocation error???"}
    • The error indicates a memory allocation issue when trying to resume logging into the table after the connection loss.
    • Current temporary fix: We created a new table for the logger to write data, and it is currently functioning correctly.
    • Long-term expectation: We need a solution that allows the logger to continue writing to the same existing table, rather than creating a new table each time this issue arises.
  • Impact:
    • This issue affects the continuity of the logging system, requiring manual intervention to create new tables in case of connection loss.
    • It disrupts long-term data logging and complicates data analysis by splitting data across multiple tables.

Steps Taken:

  • Verified database connectivity and identified no issues.
  • Restarted services and observed the same memory error.
  • As a workaround, created a new table for the logger to write data, which temporarily resolved the issue.

Priority:
High - The issue affects the stability of the logging process and requires a sustainable solution.

ACCEPTED SOLUTION

Accepted Solutions

1 REPLY 1

Greetings,

Here is one suggestion you could try - https://karthikvankadara.com/2018/08/28/alteryx-postgresql-out-of-memory-while-reading-tuples/

 

 

Regards,

Mohit 

Announcements


Top Tags