![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| |||||||
Chapter 2Accessing and Maintaining Log FilesInformation, error, and alert messages are logged to system log files. Use the system log files to diagnose problems or errors. By configuring the log files, you can direct different categories of messages to files or to the console window. In this way, you can make the information in logs more accessible and prevent the occurrence of large log files. For information about using log files generated by the Solaris operating system and the Foundation Services, consult the syslog(3) and syslogd(1M) man pages. This chapter contains the following sections: Accessing System Log FilesAll information, error, and alert messages generated by the Foundation Services are sent to the system log files. The messages can be processed by client programs or by the Node Management Agent (NMA). To configure your access to the system log files, edit the/etc/syslog.conf file. You can add or change the message sources, priorities, and message locations according to the syntax described in the syslog.conf(4) man page. See the man pages of the individual daemons for details of the error levels used by each service. All Foundation Services messages have the syslog facility set to local0. You can configure system log files to contain selected categories of messages. The Foundation Services have the following error message categories:
For information about error message categories, see the syslog.conf(4) man page. Note - The console window on the Netra CP21xx board is a 9600-bps serial line. If you are using a Netra CP21xx board, configure the syslog.conf file to direct messages to files.
|
local0.info;local0.notice / ifdef /var/adm/logfile |
Note - Use tabulation in the /etc/syslog.conf file.
Save the /etc/syslog.conf file and exit the text editor.
Create a /var/adm/logfile file if this file does not already exist:
# touch /var/adm/logfile |
Stop the syslogd daemon:
# /etc/init.d/syslog stop |
Restart the syslogd daemon:
# /etc/init.d/syslog start |
This procedure configures messages to be sent to a specific node. This procedure can be used to prevent disruption of Network File System (NFS) traffic by high volumes of messages.
Log in to the master node as superuser.
In a text editor, open the /etc/hosts file for the diskless node.
If your cluster was created by the nhinstall tool, the /etc/hosts file is located at /export/root/diskless-node-name/etc/hosts.
Remove the loghost state for the localhost entry.
Enter the loghost state for the cgtp0 address of the master node.
For example:
10.x.3.y master loghost |
If the master node is using a default class C address, 10.x.3.y is the IP address of the cgtp0 interface. The system log messages are directed to the logfile specified for the master node.
Save the /etc/hosts file and exit the text editor.
Stop the syslogd daemon:
# /etc/init.d/syslog stop |
Restart the syslogd daemon:
# /etc/init.d/syslog start |
System log messages are sent to the node specified in the /etc/hosts file. The node can be the current node or any other peer node. On the specified node, the messages are logged to a file called logfile, specified in the /etc/syslog.conf file. For information about redirecting messages to a nonpeer node, see To Redirect System Log Messages to a Nonpeer Node.
Messages generated by the Foundation Services are stored in message catalogs. You can set the access permissions to the internationalized catalogs in one of the following ways:
Set the access permissions for an individual shell session, as described in To Set NLSPATH for an Individual Shell Session.
Set the access permissions permanently, as described in To Set NLSPATH Permanently.
![]() ![]() |