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
LEARN ABOUT DEBIAN
nullmailer-send
nullmailer-send(8) System Manager's Manual nullmailer-send(8)
NAME
nullmailer-send - Send queued messages
SYNOPSIS
nullmailer-send [--daemon] [--syslog]
DESCRIPTION
This program is responsible for coordinating the transmission of messages that have been queued by nullmailer-queue. It uses a variety of
protocol modules to deliver the messages from the queue to remote "smart" servers.
When the program starts, the queue is scanned to build a list of messages to send. The queue is rescanned when either the trigger is
pulled, or after pausetime seconds have elapsed after the last failed delivery. When there are no messages in the queue, nullmailer does
no rescanning until the trigger is pulled. Pulling the trigger consists of opening up the trigger named pipe and writing a single byte to
it, which causes this program to be awakened (if it's not already processing the queue). This procedure is done by nullmailer-queue to
ensure that messages are delivered immediately.
Delivery of messages consists of reading the list of remote servers and then trying to deliver the messages to these servers as follows.
For each remote in the list, the named protocol handler is executed once for each message remaining in the queue. If the protocol handler
succeeds, the message is removed from the queue and processing continues with the next message. If it fails, the remote is skipped and
processing of the remaing messages continues with the next remote. When all the remotes have been tried, nullmailer-send sleeps for a num-
ber of seconds specified by pausetime before retrying sending the contents of the queue.
OPTIONS
-d, --daemon
Fork into the background, implies --syslog.
-s, --syslog
Use syslog for error and log messages. With --daemon, syslog will be used exclusively, without --daemon, syslog will be used addi-
tionally.
CONTROL FILES
All the control files are reread each time the queue is run.
helohost
Sets the environment variable $HELOHOST which is used by the SMTP protocol module to set the parameter given to the HELO command.
Defaults to the value of the me configuration file.
pausetime
The number of seconds to pause between successive queue runs when there are messages in the queue (defaults to 60). If this is set
to 0, nullmailer-send will exit immediately after going through the queue once (one-shot mode).
remotes
This file contains a list of remote servers to which to send each message. Each line of this file contains a remote host name or
address followed by an optional protocol string, separated by white space. The protocol name defaults to smtp, and may be followed
by command-line arguments for that module. For example, to connect to port 2525 on your SMTP smart host, which also requires SMTP
authentication, use:
smarthost.dom smtp --port=2525 --user=user --pass=pass
If your smarthost requires LOGIN authentication instead of the default PLAIN method, use:
smarthost.dom smtp --port=2525 --auth-login --user=user --pass=pass
Blank lines and lines starting with a pound are ignored.
sendtimeout
The number of seconds to wait for a remote module listed above to complete sending a message before killing it and trying again
(defaults to 3600). If this is set to 0, nullmailer-send will wait forever for messages to complete sending.
FILES
/var/spool/nullmailer/queue
The message queue.
/var/spool/nullmailer/trigger
A trigger file to cause immediate delivery.
/etc/nullmailer
The configuration directory.
/usr/lib/nullmailer
The protocol program directory.
SEE ALSO
nullmailer-queue(8), nullmailer-inject(1), mailq(1)
nullmailer-send(8)