PHWinfo banniere

Titres
PORTAIL ANNUAIRE ARTICLES COMPARATEUR HÉBERGEURS DEVIS FORUMS RÉDUCTEUR D'URL
Précédent   PHWinfo > Forums Hébergement > Forum Logiciels d'hébergement > comp.mail.sendmail > "flush queue mode requires no recipient"
S'inscrire FAQ Membres Recherche Messages du jour Marquer les forums comme lus
comp.mail.sendmail Configuring and using the BSD sendmail agent.

"flush queue mode requires no recipient"

Réponse
 
LinkBack Outils de la discussion
Vieux 30/10/2006, 18h20   #1
manishie@gmail.com
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut "flush queue mode requires no recipient"

hi all,

(yes i've googled, but haven't found a solution). i'm trying to
install scalix server 11, but i can't get sendmail to work. i'm on
rhel4. i've uninstalled the rpm, and reinstalled it (so there now
nothing scalix specific in the config files). whenever it try to start
sendmail, i get:

flush queue mode requires no recipient

ideas? i used to be running postfix. i did the redhat-switch-mail
command...

thanks.

mkm

  Réponse avec citation
Vieux 30/10/2006, 18h57   #2
Andrzej Adam Filip
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: "flush queue mode requires no recipient"

manishie@gmail.com writes:

> hi all,
>
> (yes i've googled, but haven't found a solution). i'm trying to
> install scalix server 11, but i can't get sendmail to work. i'm on
> rhel4. i've uninstalled the rpm, and reinstalled it (so there now
> nothing scalix specific in the config files). whenever it try to start
> sendmail, i get:
>
> flush queue mode requires no recipient
>
> ideas? i used to be running postfix. i did the redhat-switch-mail
> command...


Similiar problem has been (once) discussed in the group

http://groups.google.com/groups?selm...oglegroups.com
Subject: Sendmail fails to start....
From: Robert Harker
Date: Thurs, Jun 29 2006 7:24 pm
Groups: comp.mail.sendmail

1) Could post exact text produced by sendmail startup script?
[ "/etc/init.d/sendmail start" on red hat (AFAIR) ]

2) Could you post options passed to started sendmail daemon by the
script?
sh -vx "/etc/init.d/sendmail star

--
[pl2en: Andrew] Andrzej Adam Filip : anfi@priv.onet.pl : anfi@xl.wp.pl
  Réponse avec citation
Vieux 30/10/2006, 23h04   #3
manishie@gmail.com
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: "flush queue mode requires no recipient"

yes thanks, i've already seen that post, but it didn't .

1)
<root>/etc/init.d/sendmail start
Starting sendmail: [ OK ]
Starting sm-client: sendmail: fatal: flush queue mode requires no
recipient
[FAILED]
2)sh -vx /etc/init.d/sendmail start
#!/bin/bash
#
# sendmail This shell script takes care of starting and stopping
# sendmail.
#
# chkconfig: 2345 80 30
# description: Sendmail is a Mail Transport Agent, which is the program
\
# that moves mail from one machine to another.
# processname: sendmail
# config: /etc/mail/sendmail.cf
# pidfile: /var/run/sendmail.pid

# Source function library.
.. /etc/rc.d/init.d/functions
+ . /etc/rc.d/init.d/functions
# -*-Shell-script-*-
#
# functions This file contains functions to be used by most or all
# shell scripts in the /etc/init.d directory.
#

TEXTDOMAIN=initscripts
++ TEXTDOMAIN=initscripts

# Make sure umask is sane
umask 022
++ umask 022

# Set up a default search path.
PATH="/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin"
++ PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin
export PATH
++ export PATH

# Get a sane screen width
[ -z "${COLUMNS:-}" ] && COLUMNS=80
++ '[' -z '' ']'
++ COLUMNS=80

[ -z "${CONSOLETYPE:-}" ] && CONSOLETYPE="`/sbin/consoletype`"
++ '[' -z '' ']'
/sbin/consoletype
+++ /sbin/consoletype
++ CONSOLETYPE=pty

if [ -f /etc/sysconfig/i18n -a -z "${NOLOCALE:-}" ] ; then
. /etc/sysconfig/i18n
if [ "$CONSOLETYPE" != "pty" ]; then
case "${LANG:-}" in
ja_JP*|ko_KR*|zh_CN*|zh_TW*|bn_*|bd_*|pa_*|hi_*|ta _*|gu_*)
export LC_MESSAGES=en_US
export LANG
;;
*)
export LANG
;;
esac
else
[ -n "$LC_MESSAGES" ] && export LC_MESSAGES
export LANG
fi
fi
++ '[' -f /etc/sysconfig/i18n -a -z '' ']'
++ . /etc/sysconfig/i18n
LANG="en_US.UTF-8"
+++ LANG=en_US.UTF-8
SUPPORTED="en_US.UTF-8:en_US:en"
+++ SUPPORTED=en_US.UTF-8:en_US:en
SYSFONT="latarcyrheb-sun16"
+++ SYSFONT=latarcyrheb-sun16
++ '[' pty '!=' pty ']'
++ '[' -n '' ']'
++ export LANG

# Read in our configuration
if [ -z "${BOOTUP:-}" ]; then
if [ -f /etc/sysconfig/init ]; then
. /etc/sysconfig/init
else
# This all seem confusing? Look in /etc/sysconfig/init,
# or in /usr/doc/initscripts-*/sysconfig.txt
BOOTUP=color
RES_COL=60
MOVE_TO_COL="echo -en \\033[${RES_COL}G"
SETCOLOR_SUCCESS="echo -en \\033[1;32m"
SETCOLOR_FAILURE="echo -en \\033[1;31m"
SETCOLOR_WARNING="echo -en \\033[1;33m"
SETCOLOR_NORMAL="echo -en \\033[0;39m"
LOGLEVEL=1
fi
if [ "$CONSOLETYPE" = "serial" ]; then
BOOTUP=serial
MOVE_TO_COL=
SETCOLOR_SUCCESS=
SETCOLOR_FAILURE=
SETCOLOR_WARNING=
SETCOLOR_NORMAL=
fi
fi
++ '[' -z '' ']'
++ '[' -f /etc/sysconfig/init ']'
++ . /etc/sysconfig/init
# color => new RH6.0 bootup
# verbose => old-style bootup
# anything else => new style bootup without ANSI colors or positioning
BOOTUP=color
+++ BOOTUP=color
# Turn on graphical boot
GRAPHICAL=yes
+++ GRAPHICAL=yes
# column to start "[ OK ]" label in
RES_COL=60
+++ RES_COL=60
# terminal sequence to move to that column. You could change this
# to something like "tput hpa ${RES_COL}" if your terminal supports it
MOVE_TO_COL="echo -en \\033[${RES_COL}G"
+++ MOVE_TO_COL='echo -en \033[60G'
# terminal sequence to set color to a 'success' color (currently:
green)
SETCOLOR_SUCCESS="echo -en \\033[0;32m"
+++ SETCOLOR_SUCCESS='echo -en \033[0;32m'
# terminal sequence to set color to a 'failure' color (currently: red)
SETCOLOR_FAILURE="echo -en \\033[0;31m"
+++ SETCOLOR_FAILURE='echo -en \033[0;31m'
# terminal sequence to set color to a 'warning' color (currently:
yellow)
SETCOLOR_WARNING="echo -en \\033[0;33m"
+++ SETCOLOR_WARNING='echo -en \033[0;33m'
# terminal sequence to reset to the default color.
SETCOLOR_NORMAL="echo -en \\033[0;39m"
+++ SETCOLOR_NORMAL='echo -en \033[0;39m'
# default kernel loglevel on boot (syslog will reset this)
LOGLEVEL=3
+++ LOGLEVEL=3
# Set to anything other than 'no' to allow hotkey interactive
startup...
PROMPT=yes
+++ PROMPT=yes
++ '[' pty = serial ']'

if [ "${BOOTUP:-}" != "verbose" ]; then
INITLOG_ARGS="-q"
else
INITLOG_ARGS=
fi
++ '[' color '!=' verbose ']'
++ INITLOG_ARGS=-q

# Check if $pid (could be plural) are running
checkpid() {
local i

for i in $* ; do
[ -d "/proc/$i" ] && return 0
done
return 1
}


# A function to start a program.
daemon() {
# Test syntax.
local gotbase= force=
local base= user= nice= bg= pid=
nicelevel=0
while [ "$1" != "${1##[-+]}" ]; do
case $1 in
'') echo $"$0: Usage: daemon [+/-nicelevel] {program}"
return 1;;
--check)
base=$2
gotbase="yes"
shift 2
;;
--check=?*)
base=${1#--check=}
gotbase="yes"
shift
;;
--user)
user=$2
shift 2
;;
--user=?*)
user=${1#--user=}
shift
;;
--force)
force="force"
shift
;;
[-+][0-9]*)
nice="nice -n $1"
shift
;;
*) echo $"$0: Usage: daemon [+/-nicelevel] {program}"
return 1;;
esac
done

# Save basename.
[ -z "$gotbase" ] && base=${1##*/}

# See if it's already running. Look *only* at the pid file.
if [ -f /var/run/${base}.pid ]; then
local line p
read line < /var/run/${base}.pid
for p in $line ; do
[ -z "${p//[0-9]/}" -a -d "/proc/$p" ] && pid="$pid $p"
done
fi

[ -n "${pid:-}" -a -z "${force:-}" ] && return

# make sure it doesn't core dump anywhere unless requested
ulimit -S -c ${DAEMON_COREFILE_LIMIT:-0} >/dev/null 2>&1

# if they set NICELEVEL in /etc/sysconfig/foo, honor it
[ -n "$NICELEVEL" ] && nice="nice -n $NICELEVEL"

# Echo daemon
[ "${BOOTUP:-}" = "verbose" -a -z "$LSB" ] && echo -n " $base"

# And start it up.
if [ -z "$user" ]; then
$nice initlog $INITLOG_ARGS -c "$*"
else
$nice initlog $INITLOG_ARGS -c "runuser -s /bin/bash - $user -c
\"$*\""
fi
[ "$?" -eq 0 ] && success $"$base startup" || failure $"$base startup"
}

# A function to stop a program.
killproc() {
RC=0
# Test syntax.
if [ "$#" -eq 0 ]; then
echo $"Usage: killproc {program} [signal]"
return 1
fi

notset=0
# check for second arg to be kill level
if [ -n "$2" ]; then
killlevel=$2
else
notset=1
killlevel="-9"
fi

# Save basename.
base=${1##*/}

# Find pid.
pid=
if [ -f /var/run/${base}.pid ]; then
local line p
read line < /var/run/${base}.pid
for p in $line ; do
[ -z "${p//[0-9]/}" -a -d "/proc/$p" ] && pid="$pid $p"
done
fi
if [ -z "$pid" ]; then
pid=`pidof -o $$ -o $PPID -o %PPID -x $1 || \
pidof -o $$ -o $PPID -o %PPID -x $base`
fi

# Kill it.
if [ -n "${pid:-}" ] ; then
[ "$BOOTUP" = "verbose" -a -z "$LSB" ] && echo -n
"$base "
if [ "$notset" -eq "1" ] ; then
if checkpid $pid 2>&1; then
# TERM first, then KILL if not dead
kill -TERM $pid >/dev/null 2>&1
usleep 100000
if checkpid $pid && sleep 1 &&
checkpid $pid && sleep 3 &&
checkpid $pid ; then
kill -KILL $pid >/dev/null 2>&1
usleep 100000
fi
fi
checkpid $pid
RC=$?
[ "$RC" -eq 0 ] && failure $"$base shutdown" || success $"$base
shutdown"
RC=$((! $RC))
# use specified level only
else
if checkpid $pid; then
kill $killlevel $pid >/dev/null 2>&1
RC=$?
[ "$RC" -eq 0 ] && success $"$base $killlevel" || failure $"$base
$killlevel"
fi
fi
else
failure $"$base shutdown"
RC=1
fi

# Remove pid file if any.
if [ "$notset" = "1" ]; then
rm -f /var/run/$base.pid
fi
return $RC
}

# A function to find the pid of a program. Looks *only* at the pidfile
pidfileofproc() {
local base=${1##*/}

# Test syntax.
if [ "$#" = 0 ] ; then
echo $"Usage: pidfileofproc {program}"
return 1
fi

# First try "/var/run/*.pid" files
if [ -f /var/run/$base.pid ] ; then
local line p pid=
read line < /var/run/$base.pid
for p in $line ; do
[ -z "${p//[0-9]/}" -a -d /proc/$p ] && pid="$pid $p"
done
if [ -n "$pid" ]; then
echo $pid
return 0
fi
fi
}

# A function to find the pid of a program.
pidofproc() {
base=${1##*/}

# Test syntax.
if [ "$#" = 0 ]; then
echo $"Usage: pidofproc {program}"
return 1
fi

# First try "/var/run/*.pid" files
if [ -f /var/run/$base.pid ]; then
local line p pid=
read line < /var/run/$base.pid
for p in $line ; do
[ -z "${p//[0-9]/}" -a -d /proc/$p ] && pid="$pid $p"
done
if [ -n "$pid" ]; then
echo $pid
return 0
fi
fi
pidof -o $$ -o $PPID -o %PPID -x $1 || \
pidof -o $$ -o $PPID -o %PPID -x $base
}

status() {
local base=${1##*/}
local pid

# Test syntax.
if [ "$#" = 0 ] ; then
echo $"Usage: status {program}"
return 1
fi

# First try "pidof"
pid=`pidof -o $$ -o $PPID -o %PPID -x $1 || \
pidof -o $$ -o $PPID -o %PPID -x ${base}`
if [ -n "$pid" ]; then
echo $"${base} (pid $pid) is running..."
return 0
fi

# Next try "/var/run/*.pid" files
if [ -f /var/run/${base}.pid ] ; then
read pid < /var/run/${base}.pid
if [ -n "$pid" ]; then
echo $"${base} dead but pid file exists"
return 1
fi
fi
# See if /var/lock/subsys/${base} exists
if [ -f /var/lock/subsys/${base} ]; then
echo $"${base} dead but subsys locked"
return 2
fi
echo $"${base} is stopped"
return 3
}

echo_success() {
[ "$BOOTUP" = "color" ] && $MOVE_TO_COL
echo -n "[ "
[ "$BOOTUP" = "color" ] && $SETCOLOR_SUCCESS
echo -n $"OK"
[ "$BOOTUP" = "color" ] && $SETCOLOR_NORMAL
echo -n " ]"
echo -ne "\r"
return 0
}

echo_failure() {
[ "$BOOTUP" = "color" ] && $MOVE_TO_COL
echo -n "["
[ "$BOOTUP" = "color" ] && $SETCOLOR_FAILURE
echo -n $"FAILED"
[ "$BOOTUP" = "color" ] && $SETCOLOR_NORMAL
echo -n "]"
echo -ne "\r"
return 1
}

echo_passed() {
[ "$BOOTUP" = "color" ] && $MOVE_TO_COL
echo -n "["
[ "$BOOTUP" = "color" ] && $SETCOLOR_WARNING
echo -n $"PASSED"
[ "$BOOTUP" = "color" ] && $SETCOLOR_NORMAL
echo -n "]"
echo -ne "\r"
return 1
}

echo_warning() {
[ "$BOOTUP" = "color" ] && $MOVE_TO_COL
echo -n "["
[ "$BOOTUP" = "color" ] && $SETCOLOR_WARNING
echo -n $"WARNING"
[ "$BOOTUP" = "color" ] && $SETCOLOR_NORMAL
echo -n "]"
echo -ne "\r"
return 1
}

# Inform the graphical boot of our current state
update_boot_stage() {
if [ "$GRAPHICAL" = "yes" -a -x /usr/bin/rhgb-client ]; then
/usr/bin/rhgb-client --update="$1"
fi
return 0
}

# Log that something succeeded
success() {
if [ -z "${IN_INITLOG:-}" ]; then
initlog $INITLOG_ARGS -n $0 -s "$1" -e 1
else
# silly hack to avoid EPIPE killing rc.sysinit
trap "" SIGPIPE
echo "$INITLOG_ARGS -n $0 -s \"$1\" -e 1" >&21
trap - SIGPIPE
fi
[ "$BOOTUP" != "verbose" -a -z "$LSB" ] && echo_success
return 0
}

# Log that something failed
failure() {
rc=$?
if [ -z "${IN_INITLOG:-}" ]; then
initlog $INITLOG_ARGS -n $0 -s "$1" -e 2
else
trap "" SIGPIPE
echo "$INITLOG_ARGS -n $0 -s \"$1\" -e 2" >&21
trap - SIGPIPE
fi
[ "$BOOTUP" != "verbose" -a -z "$LSB" ] && echo_failure
[ -x /usr/bin/rhgb-client ] && /usr/bin/rhgb-client --details=yes
return $rc
}

# Log that something passed, but may have had errors. Useful for fsck
passed() {
rc=$?
if [ -z "${IN_INITLOG:-}" ]; then
initlog $INITLOG_ARGS -n $0 -s "$1" -e 1
else
trap "" SIGPIPE
echo "$INITLOG_ARGS -n $0 -s \"$1\" -e 1" >&21
trap - SIGPIPE
fi
[ "$BOOTUP" != "verbose" -a -z "$LSB" ] && echo_passed
return $rc
}

# Log a warning
warning() {
rc=$?
if [ -z "${IN_INITLOG:-}" ]; then
initlog $INITLOG_ARGS -n $0 -s "$1" -e 1
else
trap "" SIGPIPE
echo "$INITLOG_ARGS -n $0 -s \"$1\" -e 1" >&21
trap - SIGPIPE
fi
[ "$BOOTUP" != "verbose" -a -z "$LSB" ] && echo_warning
return $rc
}

# Run some action. Log its output.
action() {
STRING=$1
echo -n "$STRING "
if [ "${RHGB_STARTED}" != "" -a -w /etc/rhgb/temp/rhgb-console ];
then
echo -n "$STRING " > /etc/rhgb/temp/rhgb-console
fi
shift
initlog $INITLOG_ARGS -c "$*" && success $"$STRING" || failure
$"$STRING"
rc=$?
echo
if [ "${RHGB_STARTED}" != "" -a -w /etc/rhgb/temp/rhgb-console ];
then
if [ "$rc" = "0" ]; then
echo_success > /etc/rhgb/temp/rhgb-console
else
echo_failure > /etc/rhgb/temp/rhgb-console
[ -x /usr/bin/rhgb-client ] && /usr/bin/rhgb-client --details=yes
fi
echo
fi
return $rc
}

# returns OK if $1 contains $2
strstr() {
[ "${1#*$2*}" = "$1" ] && return 1
return 0
}

# Confirm whether we really want to run this service
confirm() {
[ -x /usr/bin/rhgb-client ] && /usr/bin/rhgb-client --details=yes
while : ; do
echo -n $"Start service $1 (Y)es/(N)o/(C)ontinue? [Y] "
read answer
if strstr $"yY" "$answer" || [ "$answer" = "" ] ; then
return 0
elif strstr $"cC" "$answer" ; then
rm -f /var/run/confirm
[ -x /usr/bin/rhgb-client ] && /usr/bin/rhgb-client --details=no
return 2
elif strstr $"nN" "$answer" ; then
return 1
fi
done
}

# Source networking configuration.
[ -f /etc/sysconfig/network ] && . /etc/sysconfig/network
+ '[' -f /etc/sysconfig/network ']'
+ . /etc/sysconfig/network
NETWORKING=yes
++ NETWORKING=yes
GATEWAY=67.15.70.1
++ GATEWAY=67.15.70.1
GATEWAYDEV=eth0
++ GATEWAYDEV=eth0
HOSTNAME=tennisplayer.net
++ HOSTNAME=tennisplayer.net
FORWARD_IPV4=yes
++ FORWARD_IPV4=yes

# Source sendmail configureation.
if [ -f /etc/sysconfig/sendmail ] ; then
. /etc/sysconfig/sendmail
else
DAEMON=no
QUEUE=1h
fi
+ '[' -f /etc/sysconfig/sendmail ']'
+ . /etc/sysconfig/sendmail
DAEMON=yes
++ DAEMON=yes
QUEUE=1h
++ QUEUE=1h
[ -z "$SMQUEUE" ] && SMQUEUE="$QUEUE"
+ '[' -z '' ']'
+ SMQUEUE=1h
[ -z "$SMQUEUE" ] && SMQUEUE=1h
+ '[' -z 1h ']'

# Check that networking is up.
[ "${NETWORKING}" = "no" ] && exit 0
+ '[' yes = no ']'

[ -f /usr/sbin/sendmail ] || exit 0
+ '[' -f /usr/sbin/sendmail ']'

RETVAL=0
+ RETVAL=0
prog="sendmail"
+ prog=sendmail

start() {
# Start daemons.

echo -n $"Starting $prog: "
if test -x /usr/bin/make -a -f /etc/mail/Makefile ; then
make all -C /etc/mail -s > /dev/null
else
for i in virtusertable access domaintable mailertable ; do
if [ -f /etc/mail/$i ] ; then
makemap hash /etc/mail/$i < /etc/mail/$i
fi
done
fi
/usr/bin/newaliases > /dev/null 2>&1
daemon /usr/sbin/sendmail $([ "x$DAEMON" = xyes ] && echo -bd) \
$([ -n "$QUEUE" ] && echo -q$QUEUE) $SENDMAIL_OPTARG
RETVAL=$?
echo
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/sendmail

if ! test -f /var/run/sm-client.pid ; then
echo -n $"Starting sm-client: "
touch /var/run/sm-client.pid
chown smmsp:smmsp /var/run/sm-client.pid
if [ -x /usr/bin/selinuxenabled ] && /usr/bin/selinuxenabled; then
/sbin/restorecon /var/run/sm-client.pid
fi
daemon --check sm-client /usr/sbin/sendmail -L sm-msp-queue -Ac \
-q $SMQUEUE $SENDMAIL_OPTARG
RETVAL=$?
echo
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/sm-client
fi

return $RETVAL
}

reload() {
# Stop daemons.
echo -n $"reloading $prog: "
/usr/bin/newaliases > /dev/null 2>&1
if [ -x /usr/bin/make -a -f /etc/mail/Makefile ]; then
make all -C /etc/mail -s > /dev/null
else
for i in virtusertable access domaintable mailertable ; do
if [ -f /etc/mail/$i ] ; then
makemap hash /etc/mail/$i < /etc/mail/$i
fi
done
fi
daemon /usr/sbin/sendmail $([ "x$DAEMON" = xyes ] && echo -bd) \
$([ -n "$QUEUE" ] && echo -q$QUEUE)
RETVAL=$?
killproc sendmail -HUP
RETVAL=$?
echo
if [ $RETVAL -eq 0 -a -f /var/run/sm-client.pid ]; then
echo -n $"reloading sm-client: "
killproc sm-client -HUP
RETVAL=$?
echo
fi
return $RETVAL
}

stop() {
# Stop daemons.
echo -n $"Shutting down $prog: "
killproc sendmail
RETVAL=$?
echo
[ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/sendmail
if test -f /var/run/sm-client.pid ; then
echo -n $"Shutting down sm-client: "
killproc sm-client
RETVAL=$?
echo
[ $RETVAL -eq 0 ] && rm -f /var/run/sm-client.pid
[ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/sm-client
fi
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
reload)
reload
RETVAL=$?
;;
restart)
stop
start
RETVAL=$?
;;
condrestart)
if [ -f /var/lock/subsys/sendmail ]; then
stop
start
RETVAL=$?
fi
;;
status)
status sendmail
RETVAL=$?
;;
*)
echo $"Usage: $0 {start|stop|restart|condrestart|status}"
exit 1
esac
+ case "$1" in
+ start
+ echo -n 'Starting sendmail: '
Starting sendmail: + test -x /usr/bin/make -a -f /etc/mail/Makefile
+ make all -C /etc/mail -s
+ /usr/bin/newaliases
[ "x$DAEMON" = xyes ] && echo -bd
++ '[' xyes = xyes ']'
++ echo -bd
[ -n "$QUEUE" ] && echo -q$QUEUE
++ '[' -n 1h ']'
++ echo -q1h
+ daemon /usr/sbin/sendmail -bd -q1h
+ local gotbase= force=
+ local base= user= nice= bg= pid=
+ nicelevel=0
+ '[' /usr/sbin/sendmail '!=' /usr/sbin/sendmail ']'
+ '[' -z '' ']'
+ base=sendmail
+ '[' -f /var/run/sendmail.pid ']'
+ '[' -n '' -a -z '' ']'
+ ulimit -S -c 0
+ '[' -n '' ']'
+ '[' color = verbose -a -z '' ']'
+ '[' -z '' ']'
+ initlog -q -c '/usr/sbin/sendmail -bd -q1h'
+ '[' 0 -eq 0 ']'
+ success 'sendmail startup'
+ '[' -z '' ']'
+ initlog -q -n /etc/init.d/sendmail -s 'sendmail startup' -e 1
+ '[' color '!=' verbose -a -z '' ']'
+ echo_success
+ '[' color = color ']'
+ echo -en '\033[60G'
+ echo -n '[ '
[ + '[' color = color ']'
+ echo -en '\033[0;32m'
+ echo -n OK
OK+ '[' color = color ']'
+ echo -en '\033[0;39m'
+ echo -n ' ]'
]+ echo -ne '\r'

+ return 0
+ return 0
+ RETVAL=0
+ echo

+ '[' 0 -eq 0 ']'
+ touch /var/lock/subsys/sendmail
+ test -f /var/run/sm-client.pid
+ return 0

exit $RETVAL
+ exit 0

  Réponse avec citation
Vieux 31/10/2006, 08h20   #4
Andrzej Adam Filip
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: "flush queue mode requires no recipient"

manishie@gmail.com writes:

> yes thanks, i've already seen that post, but it didn't .
>
> 1)
> <root>/etc/init.d/sendmail start
> Starting sendmail: [ OK ]
> Starting sm-client: sendmail: fatal: flush queue mode requires no
> recipient
> [FAILED]
> 2)sh -vx /etc/init.d/sendmail start
> #!/bin/bash
> #
> # sendmail This shell script takes care of starting and stopping
> # sendmail.
> #
> [...]
> start() {
> # Start daemons.
> [...]
> if ! test -f /var/run/sm-client.pid ; then
> echo -n $"Starting sm-client: "
> touch /var/run/sm-client.pid
> chown smmsp:smmsp /var/run/sm-client.pid
> if [ -x /usr/bin/selinuxenabled ] && /usr/bin/selinuxenabled; then
> /sbin/restorecon /var/run/sm-client.pid
> fi
> daemon --check sm-client /usr/sbin/sendmail -L sm-msp-queue -Ac \
> -q $SMQUEUE $SENDMAIL_OPTARG
> RETVAL=$?
> echo
> [ $RETVAL -eq 0 ] && touch /var/lock/subsys/sm-client
> fi
>
> return $RETVAL
> }
> [...]
> + test -f /var/run/sm-client.pid
> + return 0
>
> exit $RETVAL
> + exit 0


In the debug output you posted the script have not even tried to start
sm-sendmail because /var/run/sm-client.pid (file that should contain pid
of running sm-sendmail process) has been present.

Most likely to get more meaningful debug output you should run
/etc/init.d/sendmail stop
before running
sh -vx /etc/init.d/sendmail start

BTW do you use submit.cf generated from Red Hat provided submit.mc?
Red Hat uses "non standard" location of the pid file and non standard
premissions requiring "" from sendmail startup script
(touch ...; chown ... )

It has caused some (different) problems in the past.

--
[pl2en: Andrew] Andrzej Adam Filip : anfi@priv.onet.pl : anfi@xl.wp.pl
  Réponse avec citation
Vieux 01/11/2006, 05h31   #5
manishie@gmail.com
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: "flush queue mode requires no recipient"

Andrzej,

thanks for your ! i figured it out. for some reason, there was a
symbolic link in my system so that when sendmail was called, it was
actually running postfix. not sure why, because i did run the
redhat-switch-mail program to change the system to sendmail. so
postfix was running instead, with all the sendmail switches!

thanks again...

mkm

Andrzej Adam Filip wrote:

> In the debug output you posted the script have not even tried to start
> sm-sendmail because /var/run/sm-client.pid (file that should contain pid
> of running sm-sendmail process) has been present.
>
> Most likely to get more meaningful debug output you should run
> /etc/init.d/sendmail stop
> before running
> sh -vx /etc/init.d/sendmail start
>
> BTW do you use submit.cf generated from Red Hat provided submit.mc?
> Red Hat uses "non standard" location of the pid file and non standard
> premissions requiring "" from sendmail startup script
> (touch ...; chown ... )
>
> It has caused some (different) problems in the past.
>
> --
> [pl2en: Andrew] Andrzej Adam Filip : anfi@priv.onet.pl : anfi@xl.wp.pl


  Réponse avec citation
Vieux 01/11/2006, 10h04   #6
Andrzej Adam Filip
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: "flush queue mode requires no recipient"

manishie@gmail.com writes:
> [...]
> Andrzej,
>
> thanks for your ! i figured it out. for some reason, there was a
> symbolic link in my system so that when sendmail was called, it was
> actually running postfix. not sure why, because i did run the
> redhat-switch-mail program to change the system to sendmail. so
> postfix was running instead, with all the sendmail switches!
>
> thanks again...


You have not been first to be hit by "problems" caused by starting
"sendmail look alike" by sendmail-8.12+ startup scripts.

Once (a few years ago) I installed a fresh system expecting sendmail as
usual I getting something else (exim). I detected it when I tried to
use sendmail's advanced debugging command line switches :-)

--
[pl2en: Andrew] Andrzej Adam Filip : anfi@priv.onet.pl : anfi@xl.wp.pl
  Réponse avec citation
Réponse


Outils de la discussion

Règles de messages
Vous ne pouvez pas créer de nouvelles discussions
Vous ne pouvez pas envoyer des réponses
Vous ne pouvez pas envoyer des pièces jointes
Vous ne pouvez pas modifier vos messages

Les balises BB sont activées : oui
Les smileys sont activés : oui
La balise [IMG] est activée : oui
Le code HTML peut être employé : non
Trackbacks are oui
Pingbacks are oui
Refbacks are oui


Fuseau horaire GMT +1. Il est actuellement 19h53.


Édité par : vBulletin® version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0 RC5 Tous droits réservés.
Version française #16 par l'association vBulletin francophone
PHWinfo est un site Éducation Sans Frontières ©2000-2008
Ad Management by RedTyger
©Tous droits réservés par les parties respectives
Page generated in 0,26458 seconds with 14 queries