This question was originally posted on DCIM Support by Boris on 2019-03-27
One my customer got the following error in high frequency when DCO is opening .
This is servers location into same location. In indefinitely the customer has been increase the response timeout to 900 sec.
This answer was originally posted on DCIM Support by Jef Faridi on 2019-03-27
That notification/error message usually occurs if DCO is unable to receive data from the integrated DCE. There could be several reasons for this, some scenarios described here:
You might basically want to verify the communication, eg. edit the External Systems Configuration settings for the integrated DCE and verify host name/IP and the user name/password are valid - push the Test button if it returns "Server test successful", then click on OK to accept the ssl handshake (if communicating via port 443), and then "Save and close".
You might also want to try increase the timeout settings for the integrated DCE to even higher value such as 1800 or 3600 s.
This comment was originally posted on DCIM Support by Boris on 2019-03-27
We haven't problem with communication .
I provide the error from jboss-console that relevant to this issue
This comment was originally posted on DCIM Support by Jef Faridi on 2019-03-28
The selected lines (from your attached image) dose not seem to be relevant here, but it is concerning the rack pdu (AP8886) that may have "issues" reporting the power bank info to DCO (from DCE). For more details, please see the following page: https://sxwhelpcenter.ecostruxureit.com/display/UADCO8x/Correcting+False+Power+Values+Reported+by+St..., which also contains a ddf file to resolve the issue.
However, if you can provide the server logs, then I can take a look. In latest version of DCO (such as 8.2.12) server logs can be collected from the web-client (Administration>Download log files), but in previous versions (such as 8.2.7) it can be collected from webmin interface (StruxureWare DC Operation>Download Log Files> Download log files).
I will send you an invite to my =S= box shortly, so the logs safely can be shared with me if you would, thanks.
This comment was originally posted on DCIM Support by Boris on 2019-03-31
We have tried to "Downlaod Log" but it's a very huge size of the log.
This very difficult transfer out-side from customer .
Would you like point to specific log .
This comment was originally posted on DCIM Support by Jef Faridi on 2019-04-01
That's correct they are usually large - I would at least need to look into the following files: server.log and job.log files located in /opt/jboss-as/standalone/log
This comment was originally posted on DCIM Support by Boris on 2019-04-02
Many thanks Jef .
I'm working to transfer these logs to support
This comment was originally posted on DCIM Support by Boris on 2019-04-08
I attach the log file .
If this don't enough I’ll try transfer additionaljob.tar.gz logs when I will be in customer
This comment was originally posted on DCIM Support by Jef Faridi on 2019-04-09
According to the provided job.log, power measurement retrieval is failing - seems to be caused by Read timed out.
You might want to increase the timeout settings to higher value (such as 3600 as illustrated):
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!