UNICOS CMWServer User Manual  9.0.3
 All Files Pages
Troubleshooting

The very first requirement for solving potential problems, which can appear during configuration/operation of CMWServer, is clear understanding or terms. Keeping this in mind, all possible problems can be classified into main catefgories described in the next sections.

CMWServer component includes several panels for manager configuration, operations with configuration file and diagnostics. However:

Note
in case of problems the information from WinCC OA log is really essential for more detailed diagnostics.

CMWServer manager doesn't start

The CMWServer manager is designed to be able to start always, even if there are some errors in configuration and/or environment which prevent from successful start of CMW server. The main reasons why the manager itself can't be started are:

  • The reasons common to all types of managers, for example, the manager with this number if already running
  • Missing/invalid name of configuration DP for manager in command line arguments for manager

In either case, WinCC OA log shall contain error message, describing the reason why CMWServer manager was not able to start.

CMW server doesn't start

When CMWServer manager has started successfuly, it immediately tries to create and start CMW server according to configuration. If by any reason CMW server can't be created and/or started, the message with detailed description of reason is written to WinCC OA log, but CMWServer manager keeps running.
Such state of manager must be clearly indicated in different panels of CMWServer component, for example, the manager state will be IDLE in different panels where the 'overall' state is displayed. In the list of managers such state is indicated by STOP state in CMW column in table:

cmw_server_stop.png
CMW server is not started

In either case, WinCC OA log shall contain message with clear (hopefully) description of what is wrong in configuration. Here are some examples of messages which can appear; exhaustive list of possible errors is too long, but all of them must be descriptive enough.

Example 1: DPE, mentioned in configuration file, does not exist:

WCCOACMWServer(8), 2019.02.08 07:06:38.532, IMPL, SEVERE, 54, Unexpected state, parseConfigFile(): config file /opt/lkopylov/PVSS_projects/uses_config_2/uses_config_2/data/CMWServerData: Validation error(s), details: line(s) 2...7: Unknown DPE ExampleDP_Arg1.vvv
WCCOACMWServer(8), 2019.02.08 07:06:38.532, IMPL, SEVERE, 54, Unexpected state, create(): parsing of config file failed
WCCOACMWServer(8), 2019.02.08 07:06:38.532, IMPL, SEVERE, 54, Unexpected state, create(): Failed to create CMW server


Example 2: Empty name for 'data' tag in configuration:

WCCOACMWServer(8), 2019.02.08 07:26:39.841, IMPL, SEVERE, 54, Unexpected state, isValid(): new server settings are not valid: empty value tag name
WCCOACMWServer(8), 2019.02.08 07:26:39.841, IMPL, SEVERE, 54, Unexpected state, create(): Failed to create CMW server
Note
The operation mode is 'all or nothing': either all parts of configuration are correct - then CMW server is created and started, or some part of configuration is not correct - then CMW server will not be created.

Malfunction of successfully started CMW server

It can happen potentially that CMW server was started successfully, but 'does not work as expected', for example: DPE value changes do not reach CMW clients who subscribed to corresponding properties; or SET requests from CMW clients do not really update DPE value.

In principle, there can be many reasons for such problems, including:

  • overflow of internal queues in CMWServer manager
  • the value can't be converted from DPE to CMW/RDA format (or vice versa)
  • problems in CMW infrastructure and/or network
  • may be something else which is just not foreseen

The first type of problem can be detected using corresponding diagnostics panels and properly configured UNICOS system integrity for CMWServer.

Note
It is highly recommended to configure system intergity for CMWServer in production systems.

Other types of problems should normally result in some message in WinCC OA log, provided that problem occured inside CMWServer process. One example of such 'unexpected' message:

WCCOACMWServer(8), 2019.02.08 07:49:30.319, IMPL, INFO, 0, , create(): CMW Server created, 1 DPEs, 1 CMW devices, CMW server name: CMWServerName_Test2
WCCOACMWServer(8), 2019.02.08 07:49:30.321, IMPL, INFO, 0, , run(): CMW device server was started successfully: CMWServerName_Test2
WCCOACMWServer8:Exception creating or running RDAServer: Error opening file with public key: /user/rbac/pkey/rba-pub.txt

This particular error was explained in diagnostics chapter, as well as measures to solve such problem. It is shown here to stress once more: WinCC OA log is a main tool for troubleshooting.

CMWServer manager crashes

Of course, by design CMWServer manager shall not crash under any rcircumstances. Should this happen, and especially if this can be reproduced, the only solution is to contact support Iceco.nosp@m.ntro.nosp@m.ls.Su.nosp@m.ppor.nosp@m.t@cer.nosp@m.n.ch, providing enough relevant information.