9 More Discussions You Might Find Interesting
1. Solaris
This is isolated to just 1 non-global zone out of many zones managed
This is a Solaris 11 system on SPARC
This is NOT a branded zone
syslogd is active
This came to our attention when one of our scripts didn't run over the weekend prompting us to check our messages logging in... (6 Replies)
Discussion started by: samthewildone
6 Replies
2. SuSE
How are you?
SUSE V10 and 11.
In /var/log/messages I see these lines in some servers. I'd like to know what causes these errors and how to fix them.
Thank you,
error: PAM: Authentication failure for root from XXXXXXXX
Did not receive identification string from XXXXXXX
Invalid user suse-gm... (2 Replies)
Discussion started by: JDBA
2 Replies
3. UNIX for Dummies Questions & Answers
Hi folks,
In what circumstance does the log move to
/var/adm/messages.0.......messages.1,messages.2,messages.3 .......etc
---------- Post updated at 06:23 PM ---------- Previous update was at 06:17 PM ----------
To make my questions more understandable,
What are the processes that... (4 Replies)
Discussion started by: kimurayuki
4 Replies
4. UNIX for Dummies Questions & Answers
Whenever a user uses su I get the following error messages in /var/log/messages:
Nov 23 04:24:55 <REMOVED> abrt: saved core dump of pid 26141 (/usr/libexec/fprintd) to /var/spool/abrt/ccpp-1322018695-26141.new/coredump (753664 bytes)
Nov 23 04:24:55 <REMOVED> abrtd: Directory... (3 Replies)
Discussion started by: JakesHat
3 Replies
5. Solaris
Hello,
I am using Solaris 10 and I'm geting the folowing error in /var/adm/messages.
Feb 12 09:01:18 srp21ce1 uamod: NOTICE: (uamod480 @ Q 0x600159db710) set threshold to default values
Feb 12 09:01:18 srp21ce1 uamod: NOTICE: (uamod480 @ Q 0x600159db710) threshold values... (4 Replies)
Discussion started by: toshibelul
4 Replies
6. Solaris
Hi
Having looked through the log file /var/adm/messages i've noticed these kernel warning messages and i don't know what they mean:
!-- @page { size: 8.5in 11in; margin: 0.79in } P { margin-bottom: 0.08in } --> cpudrv: NOTICE: cpu_acpi: _TSS package not found.
cpudrv: WARNING:... (1 Reply)
Discussion started by: jpg.2009
1 Replies
7. Solaris
Hi
I've been using solaris for a few days now. During the install process i had some problems configuring my nic as i needed to install a third-party driver, which i got from a a linked site from the Sun Device Detector tool a ran prior to installing. I got it working eventually, but i'm... (1 Reply)
Discussion started by: jpg.2009
1 Replies
8. Solaris
Hi all,
where I can find a list and meaning of the ID number (for example ID 353554 kern.warning)?
Thanks in advance
Pierluigi (1 Reply)
Discussion started by: Petrucci
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
I have a SunFire V490, Solaris 10 with XP1024 storage and HP Library. I have noticed the following error messages in the /var/adm/messages file. These errors are being generated constantly. Also commands like devfsadm, format cfgadm etc are getting hung. After a reboot it works fine for a... (1 Reply)
Discussion started by: nitinp82
1 Replies
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)