04-27-2008
example
=======
Server A
192.168.10.10 ABOX loghost
192.168.10.20 BBOX
Server B
192.168.10.20 BBOX
192.168.10.10 ABOX loghost
Server A check your /etc/hosts to see if you host ip address has a loghost next to it.
Server B check the /etc/hosts to see if there is an entry that pointing to Server A as the loghost
check your /etc/syslog.conf
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hiho,
my sun ultra1 print me in my /var/adm/message file:
Aug 3 03:16:29 dazinger1 raid: AEN event =
Host=3Ddazinger1 Ctrl=3D1T04359235 Dev=3Dc1t1d0
Aug 3 03:16:29 dazinger1 raid: ASC=3DA0 =
ASCQ=3D00 FRU=3D00 LUN=3D00 LUN Stat=3D00
Aug 3 03:16:29 dazinger1 raid: =... (3 Replies)
Discussion started by: pressy
3 Replies
2. UNIX for Advanced & Expert Users
Hello group,
How can I separate "named daemon" messages to the other file instead of /var/adm/messages. I still want all other daemons log the messages to /var/adm/messages.
i.e.
named => /var/adm/named.message
other daemons => /var/adm/messages.
I searched unix.com, and google but I still... (5 Replies)
Discussion started by: dannytrinh
5 Replies
3. Solaris
hi sirs
can u tell the difference between /var/log/syslogs and /var/adm/messages
in my working place i am having two servers.
in one servers messages file is empty and syslog file is going on increasing..
and in another servers message file is going on increasing but syslog file is... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies
4. UNIX for Advanced & Expert Users
The /var/adm/messages in Solaris seem to log more system messages/errors compared to /var/log/messages in Linux.
I checked the log level in Linux and they seem OK.
Is there any other log file that contains the messages or is it just that Linux doesn't log great many things? (2 Replies)
Discussion started by: gomes1333
2 Replies
5. Solaris
Hi,
Is the contents in /var/log/syslog and /var/adm/messages are same??
Regards (3 Replies)
Discussion started by: vks47
3 Replies
6. Solaris
Hi Friends,
Please help me to resove this issue ASAP.
Nov 17 16:25:52 server1 sendmail: pAH8Pnh22099: SYSERR: putoutmsg (NO-HOST): error on output channel sending "553 5.1.3 @123.com.... User address required": File too large
Nov 17 16:25:53 server1 sendmail: pAH8Pnh22099:... (1 Reply)
Discussion started by: holds_me
1 Replies
7. Solaris
Hi,
I am getting the below messsage in /var/adm/message after patching but sendmail is working after restoring the backup file.
sendmail: q4G7U1Cj014774: SYSERR(root): 127.0.0.1 config error: mail loops back to me (MX problem?)
sendmail: q4G801cw025824: SYSERR(root): 127.0.0.1 config... (3 Replies)
Discussion started by: fayaz
3 Replies
8. Solaris
Good Morning..
Hello Everyone, I've been receiving this message in /Var/adm 2 days ago, I'm a new administrator for Solaris 10 and don't know what it means..
Thanks for your help
Here is the full message:
Feb 18 03:30:45 sun3000 ebus: se0 at ebus0: offset 1,400000
Feb 18 03:30:45... (4 Replies)
Discussion started by: alexelchivo
4 Replies
9. Solaris
Hi All
I am facing an issue with our new solaris machine.
in /var/adm/messages
root@Prod-App1:/var/tmp#
root@Prod-App1:/var/tmp#
root@Prod-App1:/var/tmp# cat /var/adm//messages
Apr 20 03:10:01 Prod-App1 syslogd: line 25: WARNING: loghost could not be resolved
Apr 20 08:24:18 Prod-App1... (0 Replies)
Discussion started by: javeedkaleem
0 Replies
10. Solaris
Hi All
I am facing an issue with our new solaris machine.
in /var/adm/messages
Apr 22 16:43:05 Prod-App1 in.routed: interface net0 to 172.16.101.1 turned off
Apr 22 16:43:33 Prod-App1 mac: NOTICE: nxge0 link up, 1000 Mbps, full duplex
Apr 22 16:43:34 Prod-App1 mac: NOTICE: nxge0 link... (2 Replies)
Discussion started by: javeedkaleem
2 Replies
auditd(1m) auditd(1m)
NAME
auditd - Starts the DCE Audit Daemon.
SYNOPSIS
auditd [-t trail_file] [-a] [-s size] [-wrap] [-w svc_route] [-d debug_level]
OPTIONS
Specifies the pathname of the audit trail file used by the Audit daemon. The default path of the audit trail file is dcelo-
cal/var/aud/adm/central_trail. If an audit trail file name (instead of an absolute pathname) is specified, the file will be created in the
dcelocal/var/aud/adm/ directory. Audits the Audit daemon's control interface access. Sets a warning threshold on the size of the audit
trail file. The Audit daemon displays a warning message each time an audit record is appended to the audit trail after the threshold has
been reached. Wraps the recording of audit events to the beginning of the audit trail file when its size limit is reached. The default
action when the size limit has been reached is to stop auditing. Specifies where each level of serviceability messages are routed. The
svc_route argument is divided into three fields, separated by colons - the level, a routing identifier, and a routing parameter:
severity:how:where
See svcroute(5) for possible values for these fields. Specifies debugging level of sub-components. The debug_level argument contains four
fields separated by a colon:
component:flags:how:where
See svcroute(5) for possible values of these fields.
DESCRIPTION
The auditd command starts the Audit daemon. The Audit daemon must be run on the host before the audit clients.
The Audit daemon can only service audit clients that are on the host where it is running. Thus, an Audit daemon must be installed and run
on every host in the cell that has audit clients (audit clients include DCE servers and user-written application servers).
The Audit daemon has two functions. It maintains the filter files which are shared by all audit clients running on the host. It also pro-
vides an audit record logging service to these clients.
The Audit daemon runs under the local host's machine principal identity (host/hostname/self).
A DCE Host daemon (dced) must be running on the local host when auditd is started. Typically, dced and auditd are started at boot time.
The auditd process places itself in the background and sends messages indicating it is ready to service requests for updating or querying
filters and logging audit records.
Privileges Required
You must be logged into a privileged account (cell_admin or a member of the audit-admin group) to be able to run auditd.
EXAMPLES
The following example starts the Audit daemon using the default audit trail file (dcelocal/var/aud/adm/central_trail): $ auditd
The following example starts the Audit daemon and specifies my_trail_file as the audit trail file. $auditd -t my_trail_file
The following example starts the Audit daemon and specifies where each level of serviceability messages is going to be routed. $ auditd -w
FATAL:FILE:/dev/console -w NOTICE:FILE:/opt/dcelocal/var/audit/adm/svc_log
The following example starts the Audit daemon and specifies the debugging level. $ auditd -d 1,esl.9
RELATED INFORMATION
aud(1m), audevents(1m), audfilter(1m), audtrail(1m), dcecp(1m).
auditd(1m)