Red Hat 8.1 Guia de Instalação Página 18

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 67
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 17
Example 2.1. Example Access Logs
127.0.0.1 - cn=directory manager [23/Dec/2008:19:32:52 -0500] "GET /admin-
serv/authenticate HTTP/1.0" 200 338
192.168.123.121 - cn=directory m anager [23/Dec/2008:19:33:14 -0500] "POST
/admin-serv/tasks/Configuration/ServerSetup HTTP/1.0" 200 244
192.168.123.121 - cn=directory m anager [23/Dec/2008:19:33:16 -0500] "GET
/admin-serv/tasks/Configuration/ReadLog?op=count&name=access HTTP/1.0" 200 10
The error log, by default, is at /var/log/dirsrv/admin-serv/errors. T o view the error log, open
it in an editor such as vi.
Error logs record any problem response from the Admin Server. Like the access log, error logs also
records entries based the client's IP address, along with the type of error message, and the message
text:
[timestamp] [severity] [client ip_address error_message
The severity message indicates whether the error is critical enough for administrator intervention.
[warning], [error], and [critical] require immediate administrator action. Any other severity
means the error is informational or for debugging.
Example logs are shown in Example 2.2,Example Error Logs.
Example 2.2. Example Error Logs
[Mon Dec 22 23:44:59 2008] [notice] [client 127.0.0.1] admserv_host_ip_check:
ap_get_remote_host could not resolve 127.0.0.1
[Mon Dec 22 23:44:59 2008] [notice] [client 127.0.0.1] admserv_host_ip_check:
host [localhost.localdomain] did not m atch pattern [*.example.com] -will scan
aliases
[Mon Dec 22 23:44:59 2008] [notice] [client 127.0.0.1] admserv_host_ip_check:
host alias [localhost] did not match pattern [*.example.com]
[Mon Dec 22 23:44:59 2008] [notice] [client 127.0.0.1] admserv_check_authz():
passing [/admin-serv/authenticate] to the userauth handler
[Mon Dec 22 23:45:16 2008] [notice] [client 192.168.123.121]
admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.123.121
2.4.3. Changing the Log Name in the Console
The access and error log files' names can be changed to rotate the files. T his rotation has to be done
manually to create new files if the existing log files become too large.
1. Open the Admin Server management window.
2. Click the Configuration tab.
3. Click Logs in the left panel.
4. In the Logs window on the right, enter the new log file name.
Chapter 2. Admin Server Configuration
15
Vista de página 17
1 2 ... 13 14 15 16 17 18 19 20 21 22 23 ... 66 67

Comentários a estes Manuais

Sem comentários