Understanding UNIX/Linux Enterprise Server Troubleshooting

This section discusses some typical problems that you might encounter and their solutions. When troubleshooting, follow these guidelines:

• Check the logs.

  Many times, the logs point to the problem. As soon as you notice an error, examine the log files. Messages near the end of the log files will probably reveal the most important information about the cause of the error.

• Try to narrow down the definition of any problem that you may have, particularly when communicating the issue to someone, such as JD Edwards Worldwide Customer Support Services.

  For example, rather than reporting that the batch application failed, explain how the batch application failed. The more specific the information, the faster the problem can be solved. For example, rather than reporting that "The report had the wrong data," say that "The batch status is E."

• When communicating an error message to someone, include all parts of the error message exactly as they appear in the log file or on the screen.

  Parts of the message that may not seem important may actually hold the key as to why an error occurred. Also, distinguish between characters that might be misinterpreted, such as the capital letter O and the numeral zero (0).

• Before you restart JD Edwards EnterpriseOne on the server, either delete or move the jde_xxx.log and jdedebug_xxx.log files (where xxx is a number).

  Do not rename the log files because it is easier to work with logs that use the standard naming convention (jde_xxx.log and jdedebug_xxx.log). If you need to save the log files until the problem is solved, then create a temporary directory and move the files.

• Clear the log directory regularly to avoid filling the file system.

  If the file system fills up, then the specification files can become corrupted.

• Always keep a backup of the specification files handy in case they become corrupted.

  Specification files should be backed up regularly for easy recovery of specification installs. If spec files have to be replaced, all specification installations will be lost if backups are not kept.

• To find problems that occur due to server failure, go to the system/bin32 directory:

  grep -n failed *log* > problems.txt

  The file problems.txt will contain a list of errors with the file and line number.

• Remember that UNIX is case-sensitive: jde.ini is not the same file as JDE.INI.

  Note: To complete the resolutions provided for these issues, you must sign on to the UNIX enterprise server using an account that has administrative privileges.