Monitoring errors and access with the Directory Server job log
When you get an error on your Directory Server and want more details, another action to take is to view the QDIRSRV job log.
Viewing the job log for your Directory Server can alert you to errors and help you to monitor server access. The job log contains:
- Messages about server operation and any problems within the server such as SQL server jobs or replication failures.
- Security related messages reflecting operations by clients such as wrong passwords.
- Messages giving details about client errors such as missing required attributes.
You might not want to log the client errors unless you are debugging client problems. You can control the logging of client errors on the General properties tab of the Directory Server in iSeries™ Navigator.
Parent topic:
Troubleshooting Directory Server
Viewing the QDIRSRV job log if your server is started
If your server is started, take these steps to view the QDIRSRV job log:
- In iSeries Navigator, expand Network.
- Expand Servers.
- Click TCP/IP.
- Right-click IBM Directory Server and select Server Jobs.
- From the File menu, choose Job Log.
Viewing the QDIRSRV job log if your server is stopped
If your server is stopped, take these steps to view the QDIRSRV job log:
- In iSeries Navigator, expand Basic Operations.
- Click Printer Output.
- QDIRSRV appears in the User column of iSeries Navigators right panel. To view the job log, double-click Qpjoblog to the left of QDIRSRV in the same row.
iSeries Navigator can be configured to show only spooled files. If QDIRSRV does not appear on the list, click Printer Output, then choose Include from the Options menu. Specify All in the User field, then click OK.
Directory Server uses other system resources to perform some tasks. If an error occurs with one of those resources, the job log will indicate where to go for information. In some cases Directory Server might not be able to determine where to look. In those cases, look in the Structured Query Language (SQL) servers job log to see if the problem was related to SQL servers.