Error: Invalid spaceKey on retrieving a related space config.

Message reporting

All interactive BMC Remedy AR System tools (BMC Remedy Developer Studio and BMC Remedy Data Import) report errors directly to the terminal. If a tool fails during startup, the error messages appear at the command line from which the program was started.

Note

BMC Remedy Mid Tier might display slightly different error messages for the same issue. In BMC Remedy Mid Tier 7.5.00, a pure Java qualification parser replaced the C-based qualification parser used in earlier releases. Because of this change, the error messages cannot be synchronized as a result of which you might find a few differences.

Server error reporting in UNIX

BMC Remedy AR System daemons run in the background. These daemons are not associated with a terminal and thus cannot report errors to a terminal. Instead, all BMC Remedy AR System daemon error messages are sent to the syslog daemon where, depending on your system configuration, they are displayed or recorded. For more information about the syslogd process and the syslog.conf file, see your operating system reference manuals.

Remember the following points about the syslog process:

  • BMC Remedy AR System daemons send messages about all fatal system and database errors to syslog as type user.err. To receive these messages, configure your syslog instance (using syslog.conf ) to direct all messages of type user.err to one or more locations that you define (for example, to direct all messages to the console, specify the console device as /dev/console, or direct all messages to a file by specifying a complete path name).
  • If a line in syslog.conf contains an entry of the form user.none, no messages to class user are sent to the target on this line. Delete user.none or include a separate line that explicitly locates user.err messages and sends them to a target you specify.
    For example, the following line specifies that all messages of the type user.err intended for syslog are written to the /usr/ar/err.log file:
    user.err/usr/ar/err.log
  • To start logging, add a line similar to the preceding line to the /etc/syslog.conf file, and reset logging by sending a kill -1 signal to the syslogd process to cause it to reread its configuration file.
  • BMC Remedy AR System administrators can configure system logging options. See Enabling logs.
    All errors are also written to the arerror.log file in the ARServerInstallDir/db directory.

Server error reporting in UNIX

BMC Remedy AR System daemons run in the background. These daemons are not associated with a terminal and thus cannot report errors to a terminal. Instead, all BMC Remedy AR System daemon error messages are sent to the syslog daemon where, depending on your system configuration, they are displayed or recorded. For more information about the syslogd process and the syslog.conf file, see your operating system reference manuals.

Remember the following points about the syslog process:

  • BMC Remedy AR System daemons send messages about all fatal system and database errors to syslog as type user.err. To receive these messages, configure your syslog instance (using syslog.conf ) to direct all messages of type user.err to one or more locations that you define (for example, to direct all messages to the console, specify the console device as /dev/console, or direct all messages to a file by specifying a complete path name).
  • If a line in syslog.conf contains an entry of the form user.none, no messages to class user are sent to the target on this line. Delete user.none or include a separate line that explicitly locates user.err messages and sends them to a target you specify.
    For example, the following line specifies that all messages of the type user.err intended for syslog are written to the /usr/ar/err.log file:
    user.err/usr/ar/err.log
  • To start logging, add a line similar to the preceding line to the /etc/syslog.conf file, and reset logging by sending a kill -1 signal to the syslogd process to cause it to reread its configuration file.
  • BMC Remedy AR System administrators can configure system logging options. See Enabling logs.
    All errors are also written to the arerror.log file in the ARServerInstallDir/db directory.
Was this page helpful? Yes No Submitting... Thank you

Comments