The following items should help you to identify the cause of the failure and to remedy it:
-
Logs
You definitely should check the log files first.
The Opmantek logs are all stored in the directory
/usr/local/omk/log
.
The Opmantek Web Application uses the file
opDaemon.log
, and the individual
application modules generally use the application name, e.g.
open-audit.log
(and possibly a few other secondary log files).
There is also the legacy log file
common.log
to check.
-
Unmerged Configuration after Upgrade
If you are encountering this problem just after upgrading your installation, please check
whether there are any unmerged differences between the shipped new configuration files
in
/usr/local/omk/install
and the active ones in
/usr/local/omk/conf
.
open-audit includes the tool
opdiffconfigs.pl
in
/usr/local/omk/bin/
for this purpose.
The installation and upgrade log in
/usr/local/omk/install.log
may also contain
relevant information.
-
The Community Wiki
Don't forget to check our wiki site at
community.opmantek.com, which
contains documentation and tips for all Opmantek applications.
-
The Support Tool
If you need to
contact Opmantek
please include the output of the Opmantek Support Tool, which provides valuable information for
troubleshooting purposes.
The Support Tool is usually installed as
/usr/local/omk/bin/support.pl
,
and further details about the tool can be found on
its wiki page.