riclolsen/json-scada

A portable and scalable SCADA/IIoT-I4.0 platform centered on the MongoDB database server.

{json:scada}

A portable and scalable SCADA/IIoT-I4.0 platform centered on the MongoDB database server.

Mission Statement

To provide an easy to use, fully-featured, scalable, and portable SCADA/IIoT-I4.0 platform built by leveraging mainstream open-source IT tools.

Screenshots

Major features

• Standard IT tools applied to SCADA/IoT (MongoDB, PostgreSQL/TimescaleDB, Node.js, C#, Golang, Grafana, etc.).
• MongoDB as the real-time core database, persistence layer, config store, SOE historian.
• Event-based realtime async data processing with MongoDB Change Streams.
• Portability and modular interoperability over Linux, Windows, Mac OSX, x86/64, ARM.
• Windows installer available in the releases section.
• Unlimited tags, servers, and users.
• Horizontal scalability, from a single computer to big clusters (MongoDB-sharding), Docker containers, VMs, Kubernetes, cloud, or hybrid deployments.
• Modular distributed architecture. Lightweight redundant data acquisition nodes can connect securely over TLS to the database server. E.g. a Raspberry PI can be a data acquisition node.
• Extensibility of the core data model (MongoDB: NoSQL/schema-less).
• HTML5 Web interface. UTF-8/I18N. Mobile access. Web-based configuration management.
• Role-based access control (RBAC).
• Various high-quality protocol drivers.
• Integration with MQTT brokers (compatibility with Sparkplug B).
• Live point configuration updates.
• Inkscape-based SVG synoptic display editor.
• PostgreSQL/TimescaleDB historian integrated with Grafana for easy creation of dashboards.
• Easy development of custom applications with modern stacks like MEAN/MERN, etc. Extensive use of JSON from bottom up.
• Leverage a huge ecosystem of MongoDB/PostgreSQL tools, community, services, etc.

Use cases

• Power/Oil/Gas/Manufacturing/etc Local Station HMI.
• SCADA Protocol Gateway.
• SCADA Control Centers.
• SCADA/IIoT Historian.
• Intranet/Internet HTTPS Gateway - Visualization Server.
• Multilevel Systems Integration (SCADA/IIoT/ERP/MES/PLC).
• Global-Level/Cloud SCADA Systems Integration.
• Edge processing.
• Data concentrator for Big Data / ML processing.
• Digital Transformation, Industry 4.0 enabler.

Architecture

Documentation

• Generic Install Guide
• Windows Installer
• RedHat/Rocky Linux Installer
• Docker Demo
• Schema Documentation
• Config File
• SVG Synoptic Display Editor
• IEC61850 Client Driver
• IEC60870-5-104 Server Driver
• IEC60870-5-104 Client Driver
• IEC60870-5-101 Server Driver
• IEC60870-5-101 Client Driver
• DNP3 Client Driver
• Telegraf Listener Driver
• MQTT Sparkplug-B Client Driver
• OPC-UA Client Driver
• OPC-UA Server Driver
• CIP Ethernet/IP PLCTags Client Driver
• I104M Client Driver
• Calculations
• Change Stream Data Processor
• Custom Data Processor
• Realtime Data Server
• OSHMI2JSON Tool
• Report Generators
• SAGE-web Displays

Protocols Roadmap

• IEC 60870-5-104 Server TCP/TLS
• IEC 60870-5-104 Client TCP/TLS
• IEC 60870-5-101 Server (Serial, TCP)
• IEC 60870-5-101 Client (Serial, TCP)
• IEC 60870-5-103 Client
• DNP3 Client (TCP, UDP, TLS, Serial) - Windows x64 only!
• DNP3 Server (TCP, UDP, TLS, Serial)
• MQTT/Sparkplug-B Client
• I104M (adapter for some OSHMI drivers)
• ICCP Client (via I104M)
• Telegraf Client (OPC-UA, MQTT, MODBUS, SNMP, ...)
• OPC UA Client
• OPC UA Server
• OPC UA Historical Data Server
• OPC DA Client
• Modbus Client
• IEC 61850 MMS Client
• IEC 61850 MMS Server
• IEC 61850 GOOSE Client
• CIP Ethernet/IP (libplctag, experimental)
• Siemens S7
• BACNET

Features Roadmap

• Web-based Viewers
• Web-based Configuration Manager
• Excel-based Configuration
• User auth/Role-based Access Control (RBAC)
• Inkscape-based SVG Synoptic Editor
• Compiled Calculations Engine
• Customizable Change-Stream Processor (for user implemented scripts)
• Low-latency/Interpreted Calculations Engine
• Basic Alarms Processor
• Advanced Alarms Processor
• PostgreSQL/TimescaleDB Historian
• Grafana Integration
• Metabase Integration (via PostgreSQL/MongoDB connectors)
• One-way realtime replication (over eth diode/tap device) w/ point db sync and historical backfill
• Windows Installer
• Online Demo
• Docker Demo (docker-compose.yaml scripts)
• Install Script for RedHat/Rocky 9.4 Linux
• Linux Image / VM
• Supervisor (Linux process manager) examples
• InfluxDB Integration
• Telegraf Integration
• Kafka Integration
• PowerBI Integration (via PostgreSQL connector)
• PowerBI Direct Integration
• NodeRed Integration
• Alerta Integration (https://alerta.io/)
• PLC4X Integration (https://plc4x.apache.org/)
• Managed Cloud Service
• SAGE (brazilian SCADA from CEPEL) web displays visualization

Online Demo (substations simulation)

• http://150.230.171.172

This demo provides a public IEC 60870-5-104 server port on IP address 150.230.171.172:2404 (common address = 1) for testing.

The demo data is published as regular MQTT topics to the public broker mqtt://test.mosquitto.org:1883 (about 8600 topics in JsonScadaDemoVPS/# and ACME_Utility/#).

Data is also published as Sparkplug-B to mqtt://test.mosquitto.org:1883 (about 4300 device metrics in spBv1.0/Sparkplug B Devices/+/JSON-SCADA Server/#). Data/birth messages are compressed by Eclipse Tahu Javascript libs.

Developer Contact

• https://www.linkedin.com/in/ricardo-olsen/

json-scada's Issues

Not able to see other type of data

when i am trying to send my json data from mqtt broker i am not able see the tag update with the value. but it is working for the integer type data

Enhancing Data Retrieval for EON Nodes

Description :

The capability to efficiently gather detailed information from EON nodes is essential for a robust monitoring. While JSON-SCADA currently supports basic interactions with these nodes, expanding this functionality to more comprehensively understand the data they hold could significantly enhance system insights and operational capabilities.

Proposed Enhancement :

I suggest we enhance the system by storing metrics from EON nodes. This approach could provide valuable insights, as the nature and usefulness of the data can vary across different scenarios and types of nodes, such as devices or gateways, making the system more adaptable and informative.

What is the license of the product?

in some project files, there is a header,
"* DNP3 Client Protocol driver for {json: scada}

• {json: scada} - Copyright (c) 2020 - Ricardo L. Olsen
• This file is part of the JSON-SCADA distribution (https://github.com/riclolsen/json-scada).
• This program is free software: you can redistribute it and / or modify
• it under the terms of the GNU General Public License as published by
• the Free Software Foundation, version 3. "

and some do not - (src/dnp3/Dnp3Client/Dnp3Client.sln)

the license section in the readme.md file is not obvious

p.s.
as a suggestion, can you put the license file in the project root.
Sounds trivial, but clarifies a lot.

[mqtt-sparkplug] from topic to groups

Given the general MQTT-Sparkplug topic structure

namespace/group_id/message_type/edge_node_id/[device_id]

I was surprised the "auto tag" feature would break the topic into the following:

• group1: MQTT:1200
• group2: group_id
• group3:

rather than what I was expecting:

• group1: group_id
• group2: edge_node_id
• group3: device_id

MQTT:1200 does not appear to be very helpful (we know it from protocolSourceConnectionNumber), and I feel at least edge_node_id is missing.

It could look like this.

Am I missing something? or making wrong assumptions?
Thank you very much for all you've done.

Events.html "Uncaught ReferenceError" the server still works without errors, remotely error

Uncaught ReferenceError: EventsViewer_MaxHistoricalEvents is not defined at events.html:74

found an i18n tool seems to be universal for vue.

https://github.com/titusdecali/vue-i18n-ultimate-guide

How can I reflect the data on the view?

Thank you for your work.

I read the document and ran the demo, but I still don't understand how I can provide the data so that it can be reflected on the view, because the data in the demo is all from the online demo where I can't see the details.

May I ask you a few questions?

• What is the model of the data in the view?

• How can I define views and their data models?

• How do data and views relate?

Thank you very much again!

mqtt broker to json-scada connection

I have mosquitto broker v3.1 and I'm using arduino to send my data to mqtt broker (mosquitto) and from there i want to send these data to json scada , when i downloaded windows installer inside it in mqtt-sparkplug folder i given my mqtt ip adress , username and password . when im building all mqtt data is getting to mqtt broker and im checking it in mqtt explorer , but im unable to configure whether these data is going to json-scada or not, in json scada web page nothing is showing and in log file im getting this:

2023/08/03 11:15:17.632851 find
2023/08/03 11:15:17.632851 server selection error: server selection timeout, current topology: { Type: Single, Servers: [] }
2023/08/03 11:15:17.989929 {json:scada} - CALCULATIONS - Version 0.1.2
2023/08/03 11:15:17.990595 Usage: calculations [instance number] [log level] [period of calculation in seconds] [config file path/name]
2023/08/03 11:15:17.990595 Default args: calculations 1 1 2.0 ../conf/json-scada.json
2023/08/03 11:15:17.990595 Instance number: 1
2023/08/03 11:15:17.990595 Log level: 1
2023/08/03 11:15:17.990595 Period of calculation (s): 2
2023/08/03 11:15:17.990595 Config file: c:\json-scada\conf\json-scada.json

im unable to figure out where is the issue , is there any way to confirm whether json-scada is connected with mqtt mosquitto broker or not?

thanks in advance

why in tabular some alarms look normal, others are inactive and without timestamps

base demo monitoring

please see an example for a your demo-docker

• grafana container in the docker-compose.yaml stack commented out
• raised the stack for monitoring
  monitor stack
  login admin
  passwd jsonscada

next Features: ()

• MongoDB Server Status metrics (cursors, operations, indexes, storage, etc)
• MongoDB Replica Set metrics (members, ping, replication lag, etc)
• MongoDB Replication Oplog metrics (size, length in time, etc)
• MongoDB Sharding metrics (shards, chunks, db/collections, balancer operations)
• MongoDB RocksDB storage-engine metrics (levels, compactions, cache usage, i/o rates, etc)
• MongoDB WiredTiger storage-engine metrics (cache, blockmanger, tickets, etc)
• MongoDB Top Metrics per collection (writeLock, readLock, query, etc*)

Dnp3Client.exe does not update values of MongoDB tags created through web Admin page

On a Windows 10 install of json-scada_setup_v.0.14, the Dnp3Client.exe fails to update the values of tags created through the Administrative Management web page.

When using the Admin web page to create tags, the fields for protocolSourceCommonAddress and protocolSourceObjectAddress are created in MongoDB as strings, however it seems that Dnp3Client.exe expects the fields to be double. Using MongoDB Compass to change the field types from string to double resolves the issue, and the tag value is then updated by Dnp3Client.exe as expected.

Either Dnp3Client.exe should expect the fields to be strings, or the web Admin page should create the fields as doubles; I am unsure which is the correct resolution.

Open port for demo json:scada

Hi, Ricardo what ports should be open for demo json:scada

How to increase tooltip preview of screen? Now we have some cut at it's edge:

ESP32-MQTT-JSONSCADA- MONGODB flow

Dear companion,

Here am working on project , My Sensor data (Temperature and Speed ) get from module and its connected through mqtt protocol. now so I want to see that data on JSON-SCADA Display Viewer which is in .SVG file .

In SVG file I created my Own layout Shape and also i done Tag . Now the

Que 1. how my .svg file and inside Tag will communicate to my Real time Data with help of MQTT Protocol Driver.

Que 2 : I need some details about Json-Scada and MQTT protocol connection. below i attached image reference

que 3 : How to set configuration between MongoDB , MQTT Protocol Connection and tag ID

Que 4: Should i add MongoDB Library In my Arduino Code or Not for storing data ? Or only Mqtt config is Enough ? Like just giving mqtt broker details in my arduino code as im getting my data in mqtt broker frome there I'm confused about sending data to json scada

hope i explained you as much understandable if not pls excuse and am expecting your valid reply...:)

How to feed back commands sent from views?

I have configured the command point in the realtimedata collection, and can send the command from the view.

I also received the command using my sparkplug program and made the action I need.

However, after sending commands in the view, the response of the view is different from that of your online demo. It seems that your online demo receives a response from the mqtt device and displays "OK", while my view displays "???", It's like this:

My demo:

Your online demo:

In all the documents you provided, I only found the following related content:

https://github.com/riclolsen/json-scada/blob/master/docs/schema.md

commandsQueue collection

This collection has no configuration, it is written by the system when user issue commands in the UI. Commands are inserted here to be dispatched by protocols drivers. Protocol acknowledgement information is updated here also by protocol drivers.

The last sentence seems to be the key point. How to feed back to the system that I have received and successfully executed the command so that it can be displayed on the view like your online demo.

New tag will not be processed by cs_data_processor.

Hello.

When I created a new label on the admin page and configured it, sending data to the mqtt subject of the new label did not work.

I checked the realtimeData collection of mongo db and confirmed that the sourceDataUpdate field of this collection has been written with the data I just sent, which shows that the sparkplug-mqtt module is working properly.

So I went to debug the cs_data_processor module and found that the data update of the new label did not trigger the change event of the changeStream of cs_data_processor, so I saw this piece of code. It seems that one condition that triggers the change event is that the tag has a value field.

json-scada/src/cs_data_processor/cs_data_processor.js:

I noticed that creating a new tag is achieved through the /Invoke/auth/createTag route of server_realtime_auth.

json-scada/src/server_realtime_auth/app/controllers/auth.controller.js:

But the mongooseSchema used by this route does not contain the value field.

json-scada/src/server_realtime_auth/app/models/tag.model.js:

Is the reason for the missing value field because of my wrong way of using it?

Did I miss something?

Thank you!

MongoDB monitoring with Netdata

set up an alternative to pmm in the form of a netdate, you can look at publiс lab link
the state of mongodb local can be viewed by selecting in the menu from the right, the rest of the services are basic by default

still testing several solutions

Monitors performance and health metrics of MongoDB.

Number of charts depends on mongodb version, storage engine and other features (replication):

1. Read requests:

   • query
   • getmore (operation the cursor executes to get additional data from query)

2. Write requests:

   • insert
   • delete
   • update

3. Active clients:

   • readers (number of clients with read operations in progress or queued)
   • writers (number of clients with write operations in progress or queued)

4. Journal transactions:

   • commits (count of transactions that have been written to the journal)

5. Data written to the journal:

   • volume (volume of data)

6. Background flush (MMAPv1):

   • average ms (average time taken by flushes to execute)
   • last ms (time taken by the last flush)

7. Read tickets (WiredTiger):

   • in use (number of read tickets in use)
   • available (number of available read tickets remaining)

8. Write tickets (WiredTiger):

   • in use (number of write tickets in use)
   • available (number of available write tickets remaining)

9. Cursors:

• opened (number of cursors currently opened by MongoDB for clients)
• timedOut (number of cursors that have timed)
• noTimeout (number of open cursors with timeout disabled)

10. Connections:

    • connected (number of clients currently connected to the database server)
    • unused (number of unused connections available for new clients)

11. Memory usage metrics:

    • virtual
    • resident (amount of memory used by the database process)
    • mapped
    • non mapped

12. Page faults:

    • page faults (number of times MongoDB had to request from disk)

13. Cache metrics (WiredTiger):

    • percentage of bytes currently in the cache (amount of space taken by cached data)
    • percantage of tracked dirty bytes in the cache (amount of space taken by dirty data)

14. Pages evicted from cache (WiredTiger):

    • modified
    • unmodified

15. Queued requests:

    • readers (number of read request currently queued)
    • writers (number of write request currently queued)

16. Errors:

    • msg (number of message assertions raised)
    • warning (number of warning assertions raised)
    • regular (number of regular assertions raised)
    • user (number of assertions corresponding to errors generated by users)

17. Storage metrics (one chart for every database)

    • dataSize (size of all documents + padding in the database)
    • indexSize (size of all indexes in the database)
    • storageSize (size of all extents in the database)

18. Documents in the database (one chart for all databases)

• documents (number of objects in the database among all the collections)

19. tcmalloc metrics

    • central cache free
    • current total thread cache
    • pageheap free
    • pageheap unmapped
    • thread cache free
    • transfer cache free
    • heap size

20. Commands total/failed rate

    • count
    • createIndex
    • delete
    • eval
    • findAndModify
    • insert

21. Locks metrics (acquireCount metrics - number of times the lock was acquired in the specified mode)

    • Global lock
    • Database lock
    • Collection lock
    • Metadata lock
    • oplog lock

22. Replica set members state

    • state

23. Oplog window

    • window (interval of time between the oldest and the latest entries in the oplog)

24. Replication lag

    • member (time when last entry from the oplog was applied for every member)

25. Replication set member heartbeat latency

    • member (time when last heartbeat was received from replica set member)

docker demo start failure

Running latest arch linux,

sudo pacman -Q docker docker-compose
docker 1:24.0.5-1
docker-compose 2.20.3-1

I get the following output from docker compose up

jonb@jonb-work-desktop ~/P/j/compile-docker (master)> docker compose up
[+] Running 14/0
 ✔ Container js_server_realtime_auth_update  Created                                                                                                             0.0s
 ✔ Container js_opcua_server_update          Created                                                                                                             0.0s
 ✔ Container js_config_server_update         Created                                                                                                             0.0s
 ✔ Container js_htdocs_admin_update          Created                                                                                                             0.0s
 ✔ Container js_cs_custom_processor_update   Created                                                                                                             0.0s
 ✔ Container js_server_realtime_update       Created                                                                                                             0.0s
 ✔ Container js_mqtt_sparkplug_update        Created                                                                                                             0.0s
 ✔ Container js_cs_data_processor_update     Created                                                                                                             0.0s
 ✔ Container js_calculations_compile         Created                                                                                                             0.0s
 ✔ Container js_alarm_beep_update            Created                                                                                                             0.0s
 ✔ Container js_telegraf_listener_update     Created                                                                                                             0.0s
 ✔ Container js_oshmi2json_update            Created                                                                                                             0.0s
 ✔ Container js_i104m_compile                Created                                                                                                             0.0s
 ✔ Container js_dotnet_compile               Created                                                                                                             0.0s
Attaching to js_alarm_beep_update, js_calculations_compile, js_config_server_update, js_cs_custom_processor_update, js_cs_data_processor_update, js_dotnet_compile, js_htdocs_admin_update, js_i104m_compile, js_mqtt_sparkplug_update, js_opcua_server_update, js_oshmi2json_update, js_server_realtime_auth_update, js_server_realtime_update, js_telegraf_listener_update
js_htdocs_admin_update          | node: --openssl-legacy-provider is not allowed in NODE_OPTIONS
js_mqtt_sparkplug_update        | npm
js_mqtt_sparkplug_update        | ERR! code EBADENGINE
js_mqtt_sparkplug_update        | npm ERR! engine
js_mqtt_sparkplug_update        |  Unsupported engine
js_mqtt_sparkplug_update        | npm ERR!
js_mqtt_sparkplug_update        |  engine Not compatible with your version of node/npm: [email protected]
js_mqtt_sparkplug_update        | npm ERR!
js_mqtt_sparkplug_update        |  notsup Not compatible with your version of node/npm: [email protected]
js_mqtt_sparkplug_update        | npm ERR!
js_mqtt_sparkplug_update        | notsup Required: {"node":"^18.17.0 || >=20.5.0"}
js_mqtt_sparkplug_update        | npm
js_mqtt_sparkplug_update        |
js_mqtt_sparkplug_update        | ERR!
js_mqtt_sparkplug_update        |
js_mqtt_sparkplug_update        | notsup
js_mqtt_sparkplug_update        |  Actual:   {"npm":"8.1.0","node":"v16.13.0"}
js_mqtt_sparkplug_update        |
js_mqtt_sparkplug_update        | npm ERR! A complete log of this run can be found in:
js_mqtt_sparkplug_update        | npm ERR!     /root/.npm/_logs/2023-09-06T11_05_22_202Z-debug.log
js_mqtt_sparkplug_update        |
js_server_realtime_update       | npm
js_server_realtime_update       |
js_server_realtime_update       | ERR! code
js_server_realtime_update       |  EBADENGINE
js_server_realtime_update       | npm
js_server_realtime_update       | ERR!
js_server_realtime_update       | engine
js_server_realtime_update       |  Unsupported engine
js_server_realtime_update       | npm
js_server_realtime_update       |  ERR!
js_server_realtime_update       |  engine
js_server_realtime_update       |  Not compatible with your version of node/npm: [email protected]
js_server_realtime_update       | npm
js_server_realtime_update       | ERR!
js_server_realtime_update       |  notsup
js_server_realtime_update       |  Not compatible with your version of node/npm: [email protected]
js_server_realtime_update       | npm
js_server_realtime_update       |  ERR! notsup
js_server_realtime_update       |  Required: {"node":"^18.17.0 || >=20.5.0"}
js_server_realtime_update       | npm ERR!
js_server_realtime_update       |  notsup Actual:   {"npm":"8.1.0","node":"v16.13.0"}
js_server_realtime_update       |
js_server_realtime_update       | npm ERR!
js_server_realtime_update       |  A complete log of this run can be found in:
js_server_realtime_update       | npm ERR!
js_server_realtime_update       |      /root/.npm/_logs/2023-09-06T11_05_22_495Z-debug.log
js_opcua_server_update          | npm
js_opcua_server_update          | ERR! code EBADENGINE
js_opcua_server_update          | npm
js_opcua_server_update          | ERR!
js_opcua_server_update          | engine
js_opcua_server_update          |  Unsupported engine
js_opcua_server_update          | npm
js_opcua_server_update          |  ERR!
js_opcua_server_update          |  engine
js_opcua_server_update          |  Not compatible with your version of node/npm: [email protected]
js_opcua_server_update          | npm ERR!
js_opcua_server_update          |  notsup
js_opcua_server_update          |  Not compatible with your version of node/npm: [email protected]
js_opcua_server_update          | npm ERR!
js_opcua_server_update          |
js_opcua_server_update          | notsup Required: {"node":"^18.17.0 || >=20.5.0"}
js_opcua_server_update          | npm
js_opcua_server_update          | ERR!
js_opcua_server_update          |  notsup
js_opcua_server_update          |  Actual:   {"npm":"8.1.0","node":"v16.13.0"}
js_opcua_server_update          |
js_opcua_server_update          |
js_opcua_server_update          | npm ERR!
js_opcua_server_update          |  A complete log of this run can be found in:
js_opcua_server_update          | npm ERR!     /root/.npm/_logs/2023-09-06T11_05_22_843Z-debug.log
js_mqtt_sparkplug_update exited with code 1
js_htdocs_admin_update exited with code 9
js_server_realtime_update exited with code 1
js_opcua_server_update exited with code 1
js_config_server_update         | npm
js_config_server_update         | ERR! code
js_config_server_update         |  EBADENGINE
js_config_server_update         | npm ERR! engine
js_config_server_update         |  Unsupported engine
js_config_server_update         | npm ERR!
js_config_server_update         | engine Not compatible with your version of node/npm: [email protected]
js_config_server_update         | npm ERR!
js_config_server_update         |  notsup Not compatible with your version of node/npm: [email protected]
js_config_server_update         | npm ERR!
js_config_server_update         | notsup Required: {"node":"^18.17.0 || >=20.5.0"}
js_config_server_update         | npm
js_config_server_update         |  ERR!
js_config_server_update         |
js_config_server_update         | notsup
js_config_server_update         |  Actual:   {"npm":"8.1.0","node":"v16.13.0"}
js_config_server_update         |
js_config_server_update         | npm ERR! A complete log of this run can be found in:
js_config_server_update         | npm
js_config_server_update         | ERR!
js_config_server_update         |      /root/.npm/_logs/2023-09-06T11_05_23_446Z-debug.log
js_oshmi2json_update            | npm
js_oshmi2json_update            | ERR! code EBADENGINE
js_oshmi2json_update            | npm
js_oshmi2json_update            | ERR! engine
js_oshmi2json_update            |  Unsupported engine
js_oshmi2json_update            | npm ERR!
js_oshmi2json_update            |  engine Not compatible with your version of node/npm: [email protected]
js_oshmi2json_update            | npm ERR!
js_oshmi2json_update            |  notsup Not compatible with your version of node/npm: [email protected]
js_oshmi2json_update            | npm
js_oshmi2json_update            | ERR! notsup Required: {"node":"^18.17.0 || >=20.5.0"}
js_oshmi2json_update            | npm
js_oshmi2json_update            |  ERR!
js_oshmi2json_update            | notsup
js_oshmi2json_update            |  Actual:   {"npm":"8.1.0","node":"v16.13.0"}
js_oshmi2json_update            |
js_oshmi2json_update            |
js_oshmi2json_update            | npm ERR!
js_oshmi2json_update            |  A complete log of this run can be found in:
js_oshmi2json_update            | npm ERR!
js_oshmi2json_update            |      /root/.npm/_logs/2023-09-06T11_05_23_461Z-debug.log
js_server_realtime_auth_update  | npm notice
js_server_realtime_auth_update  |
js_server_realtime_auth_update  | npm
js_server_realtime_auth_update  | notice New major version of npm available! 8.1.0 -> 10.0.0
js_server_realtime_auth_update  | npm notice
js_server_realtime_auth_update  |  Changelog: <https://github.com/npm/cli/releases/tag/v10.0.0>
js_server_realtime_auth_update  | npm notice
js_server_realtime_auth_update  |  Run `npm install -g [email protected]` to update!
js_server_realtime_auth_update  | npm
js_server_realtime_auth_update  | notice
js_server_realtime_auth_update  | npm ERR! code EBADENGINE
js_server_realtime_auth_update  | npm ERR!
js_server_realtime_auth_update  | engine Unsupported engine
js_server_realtime_auth_update  | npm ERR! engine
js_server_realtime_auth_update  |  Not compatible with your version of node/npm: [email protected]
js_server_realtime_auth_update  | npm ERR!
js_server_realtime_auth_update  | notsup Not compatible with your version of node/npm: [email protected]
js_server_realtime_auth_update  | npm ERR!
js_server_realtime_auth_update  |  notsup
js_server_realtime_auth_update  |  Required: {"node":"^18.17.0 || >=20.5.0"}
js_server_realtime_auth_update  | npm ERR! notsup
js_server_realtime_auth_update  |  Actual:   {"npm":"8.1.0","node":"v16.13.0"}
js_server_realtime_auth_update  |
js_server_realtime_auth_update  | npm ERR! A complete log of this run can be found in:
js_server_realtime_auth_update  | npm ERR!     /root/.npm/_logs/2023-09-06T11_05_23_960Z-debug.log
js_server_realtime_auth_update  |
js_calculations_compile         | fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/main/x86_64/APKINDEX.tar.gz
js_i104m_compile                | fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/main/x86_64/APKINDEX.tar.gz
js_oshmi2json_update exited with code 1
js_server_realtime_auth_update exited with code 1
js_cs_custom_processor_update   | npm
js_cs_custom_processor_update   | ERR! code
js_cs_custom_processor_update   |  EBADENGINE
js_cs_custom_processor_update   | npm
js_cs_custom_processor_update   | ERR!
js_cs_custom_processor_update   | engine
js_cs_custom_processor_update   |  Unsupported engine
js_cs_custom_processor_update   | npm
js_cs_custom_processor_update   |  ERR!
js_cs_custom_processor_update   | engine
js_cs_custom_processor_update   |  Not compatible with your version of node/npm: [email protected]
js_cs_custom_processor_update   | npm ERR!
js_cs_custom_processor_update   |  notsup
js_cs_custom_processor_update   |  Not compatible with your version of node/npm: [email protected]
js_cs_custom_processor_update   | npm ERR! notsup Required: {"node":"^18.17.0 || >=20.5.0"}
js_cs_custom_processor_update   | npm
js_cs_custom_processor_update   |  ERR! notsup
js_cs_custom_processor_update   |  Actual:   {"npm":"8.1.0","node":"v16.13.0"}
js_cs_custom_processor_update   |
js_cs_custom_processor_update   | npm ERR! A complete log of this run can be found in:
js_cs_custom_processor_update   | npm ERR!
js_cs_custom_processor_update   |      /root/.npm/_logs/2023-09-06T11_05_25_078Z-debug.log
js_cs_data_processor_update     | npm
js_cs_data_processor_update     | ERR! code EBADENGINE
js_cs_data_processor_update     | npm
js_cs_data_processor_update     | ERR!
js_cs_data_processor_update     | engine
js_cs_data_processor_update     |  Unsupported engine
js_cs_data_processor_update     | npm
js_cs_data_processor_update     |  ERR!
js_cs_data_processor_update     |  engine Not compatible with your version of node/npm: [email protected]
js_cs_data_processor_update     | npm ERR!
js_cs_data_processor_update     |  notsup
js_cs_data_processor_update     |  Not compatible with your version of node/npm: [email protected]
js_cs_data_processor_update     | npm
js_cs_data_processor_update     |
js_cs_data_processor_update     | ERR! notsup
js_cs_data_processor_update     |  Required: {"node":"^18.17.0 || >=20.5.0"}
js_cs_data_processor_update     | npm
js_cs_data_processor_update     |  ERR!
js_cs_data_processor_update     |  notsup
js_cs_data_processor_update     |  Actual:   {"npm":"8.1.0","node":"v16.13.0"}
js_cs_data_processor_update     |
js_cs_data_processor_update     | npm ERR! A complete log of this run can be found in:
js_cs_data_processor_update     | npm
js_cs_data_processor_update     | ERR!
js_cs_data_processor_update     |      /root/.npm/_logs/2023-09-06T11_05_25_146Z-debug.log
js_config_server_update exited with code 1
js_i104m_compile                | fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/x86_64/APKINDEX.tar.gz
js_cs_custom_processor_update exited with code 1
js_i104m_compile                | v3.18.3-149-g8225da85c11 [https://dl-cdn.alpinelinux.org/alpine/v3.18/main]
js_i104m_compile                | v3.18.3-151-g6953e6f988a [https://dl-cdn.alpinelinux.org/alpine/v3.18/community]
js_i104m_compile                | OK: 20063 distinct packages available
js_i104m_compile                | fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/main/x86_64/APKINDEX.tar.gz
js_calculations_compile         | fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/x86_64/APKINDEX.tar.gz
js_dotnet_compile               | MSBuild version 17.3.2+561848881 for .NET
js_telegraf_listener_update     | npm
js_telegraf_listener_update     | ERR!
js_telegraf_listener_update     |  code EBADENGINE
js_telegraf_listener_update     | npm ERR! engine
js_telegraf_listener_update     |  Unsupported engine
js_telegraf_listener_update     | npm ERR!
js_telegraf_listener_update     |  engine Not compatible with your version of node/npm: [email protected]
js_telegraf_listener_update     | npm ERR!
js_telegraf_listener_update     |  notsup
js_telegraf_listener_update     |  Not compatible with your version of node/npm: [email protected]
js_telegraf_listener_update     | npm
js_telegraf_listener_update     | ERR! notsup Required: {"node":"^18.17.0 || >=20.5.0"}
js_telegraf_listener_update     | npm ERR!
js_telegraf_listener_update     | notsup Actual:   {"npm":"8.1.0","node":"v16.13.0"}
js_telegraf_listener_update     |
js_telegraf_listener_update     |
js_telegraf_listener_update     | npm ERR!
js_telegraf_listener_update     |  A complete log of this run can be found in:
js_telegraf_listener_update     | npm
js_telegraf_listener_update     | ERR!     /root/.npm/_logs/2023-09-06T11_05_25_896Z-debug.log
js_cs_data_processor_update exited with code 1
js_calculations_compile         | v3.18.3-149-g8225da85c11 [https://dl-cdn.alpinelinux.org/alpine/v3.18/main]
js_calculations_compile         | v3.18.3-151-g6953e6f988a [https://dl-cdn.alpinelinux.org/alpine/v3.18/community]
js_calculations_compile         | OK: 20063 distinct packages available
js_i104m_compile                | fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/x86_64/APKINDEX.tar.gz
js_calculations_compile         | fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/main/x86_64/APKINDEX.tar.gz
js_dotnet_compile               |   Determining projects to restore...
js_i104m_compile                | OK: 18 MiB in 24 packages
js_alarm_beep_update            | npm
js_alarm_beep_update            | ERR! code EBADENGINE
js_alarm_beep_update            | npm ERR!
js_alarm_beep_update            |  engine
js_alarm_beep_update            |  Unsupported engine
js_alarm_beep_update            | npm
js_alarm_beep_update            |  ERR! engine
js_alarm_beep_update            |  Not compatible with your version of node/npm: [email protected]
js_alarm_beep_update            | npm
js_alarm_beep_update            | ERR!
js_alarm_beep_update            |  notsup
js_alarm_beep_update            |  Not compatible with your version of node/npm: [email protected]
js_alarm_beep_update            | npm ERR! notsup Required: {"node":"^18.17.0 || >=20.5.0"}
js_alarm_beep_update            | npm ERR! notsup Actual:   {"npm":"8.1.0","node":"v16.13.0"}
js_alarm_beep_update            |
js_alarm_beep_update            | npm ERR! A complete log of this run can be found in:
js_alarm_beep_update            | npm ERR!     /root/.npm/_logs/2023-09-06T11_05_26_115Z-debug.log
js_alarm_beep_update            |
js_calculations_compile         | fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/x86_64/APKINDEX.tar.gz
js_telegraf_listener_update exited with code 1
js_dotnet_compile               |   Restored /src/lib60870.netcore/lib60870.netcore/lib60870.netcore.csproj (in 188 ms).
js_calculations_compile         | OK: 18 MiB in 24 packages
js_alarm_beep_update exited with code 1
js_dotnet_compile               |   lib60870.netcore -> /publish_bin/lib60870.netcore.dll
js_dotnet_compile               |
js_dotnet_compile               | Build succeeded.
js_dotnet_compile               |
js_dotnet_compile               |     0 Warning(s)
js_dotnet_compile               |     0 Error(s)
js_dotnet_compile               |
js_dotnet_compile               | Time Elapsed 00:00:00.82
js_dotnet_compile               |
js_dotnet_compile               | MSBuild version 17.3.2+561848881 for .NET
js_i104m_compile exited with code 0
js_dotnet_compile               |   Determining projects to restore...
js_calculations_compile exited with code 0
js_dotnet_compile               |   Restored /src/lib60870.netcore/lib60870.netcore/lib60870.netcore.csproj (in 169 ms).
js_dotnet_compile               |   1 of 2 projects are up-to-date for restore.
js_dotnet_compile               |   lib60870.netcore -> /src/lib60870.netcore/lib60870.netcore/bin/Release/net6.0/lib60870.netcore.dll
js_dotnet_compile               |   iec101client -> /src/lib60870.netcore/iec101client/bin/Release/net6.0/linux-x64/iec101client.dll
js_dotnet_compile               |   iec101client -> /publish_bin/
js_dotnet_compile               | MSBuild version 17.3.2+561848881 for .NET
js_dotnet_compile               |   Determining projects to restore...
js_dotnet_compile               |   All projects are up-to-date for restore.
js_dotnet_compile               |   lib60870.netcore -> /src/lib60870.netcore/lib60870.netcore/bin/Release/net6.0/lib60870.netcore.dll
js_dotnet_compile               |   iec101server -> /src/lib60870.netcore/iec101server/bin/Release/net6.0/linux-x64/iec101server.dll
js_dotnet_compile               |   iec101server -> /publish_bin/
js_dotnet_compile               | MSBuild version 17.3.2+561848881 for .NET
js_dotnet_compile               |   Determining projects to restore...
js_dotnet_compile               |   All projects are up-to-date for restore.
js_dotnet_compile               |   lib60870.netcore -> /src/lib60870.netcore/lib60870.netcore/bin/Release/net6.0/lib60870.netcore.dll
js_dotnet_compile               |   iec104client -> /src/lib60870.netcore/iec104client/bin/Release/net6.0/linux-x64/iec104client.dll
js_dotnet_compile               |   iec104client -> /publish_bin/
js_dotnet_compile               | MSBuild version 17.3.2+561848881 for .NET
js_dotnet_compile               |   Determining projects to restore...
js_dotnet_compile               |   All projects are up-to-date for restore.
js_dotnet_compile               |   lib60870.netcore -> /src/lib60870.netcore/lib60870.netcore/bin/Release/net6.0/lib60870.netcore.dll
js_dotnet_compile               |   iec104server -> /src/lib60870.netcore/iec104server/bin/Release/net6.0/linux-x64/iec104server.dll
js_dotnet_compile               |   iec104server -> /publish_bin/
js_dotnet_compile               | MSBuild version 17.3.2+561848881 for .NET
js_dotnet_compile               |   Determining projects to restore...
js_dotnet_compile               |   All projects are up-to-date for restore.
js_dotnet_compile               |   OPC-UA-Client -> /src/OPC-UA-Client/bin/Release/net6.0/linux-x64/OPC-UA-Client.dll
js_dotnet_compile               |   OPC-UA-Client -> /publish_bin/
js_dotnet_compile               | MSBuild version 17.3.2+561848881 for .NET
js_dotnet_compile               |   Determining projects to restore...
js_dotnet_compile               |   All projects are up-to-date for restore.
js_dotnet_compile               |   libplctag -> /publish_bin/libplctag.dll
js_dotnet_compile               |
js_dotnet_compile               | Build succeeded.
js_dotnet_compile               |
js_dotnet_compile               |     0 Warning(s)
js_dotnet_compile               |     0 Error(s)
js_dotnet_compile               |
js_dotnet_compile               | Time Elapsed 00:00:00.45
js_dotnet_compile               |
js_dotnet_compile               | MSBuild version 17.3.2+561848881 for .NET
js_dotnet_compile               |   Determining projects to restore...
js_dotnet_compile               |   All projects are up-to-date for restore.
js_dotnet_compile               |   PLCTagsClient -> /src/libplctag/PLCTagsClient/bin/Release/net6.0/linux-x64/PLCTagsClient.dll
js_dotnet_compile               |   PLCTagsClient -> /publish_bin/
js_dotnet_compile               | Hit:1 http://deb.debian.org/debian bullseye InRelease
js_dotnet_compile               | Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease
js_dotnet_compile               | Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
js_dotnet_compile               | Reading package lists...
js_dotnet_compile               |
js_dotnet_compile               |
js_dotnet_compile               | Reading package lists...
js_dotnet_compile               |
js_dotnet_compile               |
js_dotnet_compile               | Building dependency tree...
js_dotnet_compile               |
js_dotnet_compile               | Reading state information...
js_dotnet_compile               |
js_dotnet_compile               |
js_dotnet_compile               | gcc is already the newest version (4:10.2.1-1).
js_dotnet_compile               | make is already the newest version (4.3-4.1).
js_dotnet_compile               | 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
js_dotnet_compile               | make: Nothing to be done for 'all'.
js_dotnet_compile               | mkdir -p ./.install/include
js_dotnet_compile               | mkdir -p ./.install/lib
js_dotnet_compile               | cp hal/inc/hal_time.h  hal/inc/hal_thread.h hal/inc/hal_filesystem.h hal/inc/tls_config.h hal/inc/lib_memory.h hal/inc/hal_base.h src/common/inc/libiec61850_common_api.h src/common/inc/linked_list.h src/iec61850/inc/iec61850_client.h src/iec61850/inc/iec61850_common.h src/iec61850/inc/iec61850_server.h src/iec61850/inc/iec61850_model.h src/iec61850/inc/iec61850_cdc.h src/iec61850/inc/iec61850_dynamic_model.h src/iec61850/inc/iec61850_config_file_parser.h src/mms/inc/mms_value.h src/mms/inc/mms_common.h src/mms/inc/mms_types.h src/mms/inc/mms_type_spec.h src/mms/inc/mms_client_connection.h src/mms/inc/mms_server.h src/mms/inc/iso_connection_parameters.h src/goose/goose_subscriber.h src/goose/goose_receiver.h src/goose/goose_publisher.h src/sampled_values/sv_subscriber.h src/sampled_values/sv_publisher.h src/logging/logging_api.h ./.install/include
js_dotnet_compile               | cp ./build/libiec61850.a ./.install/lib
js_dotnet_compile               | MSBuild version 17.3.2+561848881 for .NET
js_dotnet_compile               |   Determining projects to restore...
js_dotnet_compile               |   Restored /src/libiec61850/dotnet/core/2.0/IEC61850.NET.core.2.0/IEC61850.NET.core.2.0.csproj (in 75 ms).
js_dotnet_compile               |   IEC61850.NET.core.2.0 -> /src/libiec61850/dotnet/core/2.0/IEC61850.NET.core.2.0/bin/Release/net60/linux-x64/IEC61850.NET.core.2.0.dll
js_dotnet_compile               |   IEC61850.NET.core.2.0 -> /src/libiec61850/dotnet/core/2.0/IEC61850.NET.core.2.0/bin/Release/net60/linux-x64/publish/
js_dotnet_compile               | MSBuild version 17.3.2+561848881 for .NET
js_dotnet_compile               |   Determining projects to restore...
js_dotnet_compile               |   Restored /src/libiec61850/dotnet/core/2.0/IEC61850.NET.core.2.0/IEC61850.NET.core.2.0.csproj (in 126 ms).
js_dotnet_compile               |   1 of 2 projects are up-to-date for restore.
js_dotnet_compile               |   IEC61850.NET.core.2.0 -> /src/libiec61850/dotnet/core/2.0/IEC61850.NET.core.2.0/bin/Release/net60/IEC61850.NET.core.2.0.dll
js_dotnet_compile               |   iec61850_client -> /src/libiec61850/dotnet/core/2.0/iec61850_client/bin/Release/net60/linux-x64/iec61850_client.dll
js_dotnet_compile               |   iec61850_client -> /publish_bin/
js_dotnet_compile               | MSBuild version 17.3.2+561848881 for .NET
js_dotnet_compile               |   Determining projects to restore...
js_dotnet_compile               |   All projects are up-to-date for restore.
js_dotnet_compile               |   Dnp3Client -> /src/dnp3/Dnp3Client/bin/Release/net6.0/win-x64/Dnp3Client.dll
js_dotnet_compile               |   Dnp3Client -> /publish_bin_win/
js_dotnet_compile exited with code 0