Skip to content

Troubleshooting

The fact that OpenDAF is of a highly modular architecture can be readily used to help hunt down many kind of issues.

By selectively disabling/enabling individual modules, performance bottlenecks can be quickly found, and bugs quickly isolated.

This disabling/enabling of individual modules (and even measurements, commands, alarms) is achieved by editing configuration files in /etc/opendaf/.

The easiest way do disable the module is to comment it out with # on line beginning.

Files can be regenerated with dafman render --force, if they are changed beyond repair.

To apply changes, opendaf processes must be restarted:

systemctl restart opendaf
systemctl restart opendaf-archive

In following sections individual file groups will be described.

svc.conf

This is realtime opendaf process service configuration files. Only service libraries configured in this file are loaded into the process.

Interesting services:

  • Logger (logging configuration)
  • Core (transaction execution - enable logging with --dump-transactions 1)
  • MeasurementStack (enable/disable individual layers)
  • CommandStack (enable/disable individual layers)

svc-recorder.conf

Service configuration file of opendaf archivation process.

Interesting services:

  • Logger (logging configuration)
  • Core (transaction execution - enable logging with --dump-transactions 1)

connectors.conf

Connectors are implemented as services, and each connector has an entry in this file. Each connector can be individually disabled.

connector-<name>.vars

Configuration variables of given connector. To quickly experiment with connector settings, they can be changed here without the need to change configuration database.

providers.conf

Providers are implemented as services, and each provider has an entry in this file. Each provider can be individually disabled.

provider-<name>.vars

Configuration variables of given provider. To quickly experiment with provider settings, they can be changed here without the need to change configuration database.

measurements.csv, commands.csv, alarms.csv, alarm-groups.csv

Data tables of individual object classes.

By manipulating rows in these tables, various setups can be tested quickly, without need to change configuration database.