Product: Xtradyne I-DBC
Version: ALL

Description:

How to diagnose problems: Logging

Resolution:

If anything goes wrong take a look at the log file(s) and the event output. Additionally, service clients may receive CORBA System Exceptions (when operating an I-DBC Proxy) or HTTP or SOAP Error Messages (when operating a WS-DBC). In summary:
To diagnose problems take a look at:

• Events: are either logged by syslog or sent to an external (user defined) command according to the audit policy, cf. “Audit Policy” on page 185. DBC audit events are listed in appendix A, “Audit Events” on page 331. Events can be viewed with the Admin Console’s event browser, cf. “Audit Event Browser” on page 115.

• Error Messages:
  • DBC and SPS error messages: By default DBC and SPS error messages are written to the adm directory into the file sps.log on the SPS host and on the DBC Proxy host into the file dbc.log. A list of DBC error messages can be found in Appendix B, section “DBC and SPS Error Messages” on page 349.
  • CORBA system exceptions (I-DBC only): A list of CORBA system exceptions and minor codes received by service clients can be found in Appendix B, section “CORBA System Exceptions and Minor Codes” on page 354.
  • HTTP Error Messages (WS-DBC only): Appendix B, section “HTTP Error Messages” on page 363 lists and explains HTTP Error Messages received by service clients.
  • SOAP Error Messages (WS-DBC only): Appendix B, section “SOAP Error Messages” on page 363 lists and explains SOAP Error Messages.