Known issues in DCO 8.0

DCO server: Disk space issues

There is a known issue with DCO 8.0 log files growing in some setups, potentially taking up all disk space and preventing DCO from running.

Log files can be removed from /opt/jboss-as/standalone/log (SSH to the DCO server with administration credentials) to free the disk space (but don't delete the log directory).

Use ssh to connect to the DCO server.
Stop the Operations service by running the command: sudo systemctl stop operations.
Delete the files in the folder /opt/jboss-as/standalone/log, but not the log folder.
Commands:

cd /opt/jboss-as/standalone/log
sudo rm *.log

Start the Operations service by running the command: sudo systemctl start operations

Cluster: If the setup is a cluster environment, perform the above steps on each node.

This will delete the log files (which are using up all the disk space). In time, the log files will continue to grow in size. The issue is fixed in the upcoming version released shortly.

DCE integration: Using DCE 7.4 as an authentication server for DCO

There is a known communication error between DCE 7.4 and DCO. The issue affects most versions of DCO including 7.5 and 8.0. For now DCE 7.4 cannot be used as an authentication server for DCO. We are working on solving the issue.

Cluster setup: Cluster with DR node configuration issue

An issue appears in the server configuration interface (Webmin) when configuring a 2 node cluster with a DR node.

An error occurs (red text in Webmin) when making changes to the DR node's server configuration (in Webmin: DC Operation->Setup), for example: NTP server details, SNMPv1 community, SNMPv3 password, etc.

The error message is not critical. It doesn't affect the status of either the cluster nodes or the DR node.

To avoid getting this error, ensure you complete the DR node configuration before attaching the node to the cluster setup.

Webmin Data Center Operation - Setup page

DCO Vizor: Not supported

Data Center Operation: VIZOR is currently not supported in DCO 8.x but most of the functionality is available in the web client.

Energy Efficiency: Scripted sensors duplication

Potential risk of error when editing in duplicated script folders.

After upgrading from previous versions of DCO, the script folders may be duplicated, number of duplications being proportional to the number of scripted sensors. For example, if a folder contains 9 scripted sensors, the folder will appear 9 times.

The PUE calculations are not affected as the duplicates are only in the user interface, the virtual devices are not duplicated in the database. Therefore, you should avoid deleting any duplicates.

If you need to make changes to scripts, and you see the issue with multiple folders for the same scripted sensors, ensure you and all other users only make changes to the same folder. Avoid editing or deleting any of the duplicates.

Energy Efficiency: No popup warning for insufficient energy system configuration

Energy systems need a minimum required configuration.

When configuring a new system, if it doesn’t include the minimum required elements, a popup message should warn you of this issue, which will prevent calculations from running. This popup will not appear.

If you don't see any values after configuring an energy system, verify that your configuration fulfils these requirements:

Switchgear
Energy Efficiency properties set on the switchgear and PDU
A PDU connected to the switchgear
A script configured on the PDU
IT load properties set to include measured calculation source
Derate Capacity must be >0

DCO server: Memory issue

Some users running DCO 8.0-8.0.3 may experience an out of memory issue on the DCO server. Reboot the server if needed.
The engineering team is investigating and working on providing a fix as soon as possible.

Article info

In this article