Bug#629610: exim4: misleading (?) "failed" message after paniclog warning
On Thu, Jun 09, 2011 at 07:35:52PM -0700, Ross Boylan wrote: > Just to be sure I understand: the failure message is in error, and exim > should be functioning normally, right? Correct. A purely cosmetic side effect of the lsb init script functions. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things."Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#629610: exim4: misleading (?) "failed" message after paniclog warning
On Thu, 2011-06-09 at 21:23 +0200, Marc Haber wrote: > tags #629610 confirmed > end > > On Tue, Jun 07, 2011 at 09:01:10PM -0700, Ross Boylan wrote: > > > > # /etc/init.d/exim4 restart > > Stopping MTA for restart: exim4_listener. > > Restarting MTA: exim4. > > ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system > > possibly broken ... failed! > > > > > > I read the "... failed!" as meaning that the non-zero paniclog has > > caused the restart to fail. > > Affirmative. our fault. log_failure_msg has started to add the "... > failed" in some recent versions. Just to be sure I understand: the failure message is in error, and exim should be functioning normally, right? Thanks. Ross > > While we're at it, lsb's cheangelog for 3.2-17 says > "log_{success,failure,warning}_msg suck, please don't use them for > Debian scripts.", so we should probably re-work the init script anyway. > > Greetings > Marc > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#629610: exim4: misleading (?) "failed" message after paniclog warning
tags #629610 confirmed end On Tue, Jun 07, 2011 at 09:01:10PM -0700, Ross Boylan wrote: > > # /etc/init.d/exim4 restart > Stopping MTA for restart: exim4_listener. > Restarting MTA: exim4. > ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system > possibly broken ... failed! > > > I read the "... failed!" as meaning that the non-zero paniclog has > caused the restart to fail. Affirmative. our fault. log_failure_msg has started to add the "... failed" in some recent versions. While we're at it, lsb's cheangelog for 3.2-17 says "log_{success,failure,warning}_msg suck, please don't use them for Debian scripts.", so we should probably re-work the init script anyway. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things."Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#629610: exim4: misleading (?) "failed" message after paniclog warning
# date; EX4DEBUG=1 /etc/init.d/exim4 restart Thu Jun 9 09:51:22 PDT 2011 now debugging /etc/init.d/exim4 restart + LANG=C + export LANG + QUEUERUNNER=combined + QUEUEINTERVAL=30m + UPEX4OPTS= + PIDFILE=/var/run/exim4/exim.pid + QRPIDFILE=/var/run/exim4/eximqr.pid + [ -f /etc/default/exim4 ] + . /etc/default/exim4 + EX4DEF_VERSION= + QUEUERUNNER=combined + QUEUEINTERVAL=30m + COMMONOPTIONS= + QUEUERUNNEROPTIONS= + QFLAGS= + SMTPLISTENEROPTIONS= + [ -f /etc/inetd.conf ] + DAEMON=/usr/sbin/exim4 + NAME=exim4 + log_daemon_msg Stopping MTA for restart + [ -z Stopping MTA for restart ] + log_daemon_msg_pre Stopping MTA for restart + : + [ -z ] + echo -n Stopping MTA for restart: Stopping MTA for restart:+ return + upex4conf + UPEX4CONF=update-exim4.conf + OLDIFS= + IFS=: + [ -x /usr/local/sbin/update-exim4.conf ] + [ -x /usr/local/bin/update-exim4.conf ] + [ -x /usr/sbin/update-exim4.conf ] + IFS= + /usr/sbin/update-exim4.conf + return 0 + isconfigvalid + /usr/sbin/exim4 -bV + stop_exim + [ -f /var/run/exim4/eximqr.pid ] + [ -f /var/run/exim4/exim.pid ] + killproc -p /var/run/exim4/exim.pid /usr/sbin/exim4 + local pidfile sig status base i name_param is_term_sig + pidfile= + name_param= + is_term_sig=no + OPTIND=1 + getopts p: opt + pidfile=/var/run/exim4/exim.pid + getopts p: opt + shift 2 + base=exim4 + [ ! /var/run/exim4/exim.pid ] + name_param=--pidfile /var/run/exim4/exim.pid + echo + sed -e s/^-\(.*\)/\1/ + sig= + echo + sed -e s/^SIG\(.*\)/\1/ + sig= + [ -z -o = 15 -o = TERM ] + is_term_sig=yes + status=0 + [ ! yes = yes ] + /sbin/start-stop-daemon --stop --quiet --oknodo --pidfile /var/run/exim4/exim.pid + [ 0 = 1 ] + [ 0 = 0 -a yes = yes -a /var/run/exim4/exim.pid ] + pidofproc -p /var/run/exim4/exim.pid /usr/sbin/exim4 + local pidfile line i pids= status specified pid + pidfile= + specified= + OPTIND=1 + getopts p: opt + pidfile=/var/run/exim4/exim.pid + specified=1 + getopts p: opt + shift 2 + base=exim4 + [ ! 1 ] + [ -n /var/run/exim4/exim.pid -a -r /var/run/exim4/exim.pid ] + read pid + [ -n 5906 ] + kill -0 5906 + + ps 5906 + return 1 + rm -f /var/run/exim4/exim.pid + return 0 + log_progress_msg exim4_listener + [ -z exim4_listener ] + echo -n exim4_listener exim4_listener+ log_end_msg 0 + [ -z 0 ] + retval=0 + log_end_msg_pre 0 + : + log_use_fancy_output + TPUT=/usr/bin/tput + EXPR=/usr/bin/expr + [ -t 1 ] + [ xdumb != x ] + [ xdumb != xdumb ] + FANCYTTY=0 + false + RED= + YELLOW= + NORMAL= + [ 0 -eq 0 ] + echo . . + log_end_msg_post 0 + : + return 0 + sleep 2 + log_daemon_msg Restarting MTA + [ -z Restarting MTA ] + log_daemon_msg_pre Restarting MTA + : + [ -z ] + echo -n Restarting MTA: Restarting MTA:+ return + start_exim + [ -e /var/run/exim4 ] + start_daemon -p /var/run/exim4/exim.pid /usr/sbin/exim4 -bd -q30m + local force nice pidfile exec i args + force=0 + nice=0 + pidfile=/dev/null + OPTIND=1 + getopts fn:p: opt + pidfile=/var/run/exim4/exim.pid + getopts fn:p: opt + shift 2 + [ /usr/sbin/exim4 = -- ] + exec=/usr/sbin/exim4 + shift + args=--start --nicelevel 0 --quiet --oknodo + [ 0 = 1 ] + [ /var/run/exim4/exim.pid ] + /sbin/start-stop-daemon --start --nicelevel 0 --quiet --oknodo --chdir /etc/bacula --exec /usr/sbin/exim4 --oknodo --pidfile /var/run/exim4/exim.pid -- -bd -q30m + log_progress_msg exim4 + [ -z exim4 ] + echo -n exim4 exim4+ log_end_msg 0 + [ -z 0 ] + retval=0 + log_end_msg_pre 0 + : + log_use_fancy_output + TPUT=/usr/bin/tput + EXPR=/usr/bin/expr + [ -t 1 ] + [ xdumb != x ] + [ xdumb != xdumb ] + FANCYTTY=0 + false + RED= + YELLOW= + NORMAL= + [ 0 -eq 0 ] + echo . . + log_end_msg_post 0 + : + return 0 + warn_paniclog + [ -s /var/log/exim4/paniclog ] + [ -z ] + log_failure_msg ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly broken + [ -n ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly broken ] + log_begin_msg ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly broken ... + [ -z ALERT: ] + echo -n ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly broken ... ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly broken ...+ log_end_msg 1 + [ -z 1 ] + retval=1 + log_end_msg_pre 1 + : + log_use_fancy_output + TPUT=/usr/bin/tput + EXPR=/usr/bin/expr + [ -t 1 ] + [ xdumb != x ] + [ xdumb != xdumb ] + FANCYTTY=0 + false + RED= + YELLOW= + NORMAL= + [ 1 -eq 0 ] + [ 1 -eq 255 ] + /bin/echo -e failed! failed! + log_end_msg_post 1 + : + return 1 + true + exit 0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#629610: exim4: misleading (?) "failed" message after paniclog warning
On Tue, Jun 07, 2011 at 09:01:10PM -0700, Ross Boylan wrote: > > # /etc/init.d/exim4 restart > Stopping MTA for restart: exim4_listener. > Restarting MTA: exim4. > ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system > possibly broken ... failed! > > > I read the "... failed!" as meaning that the non-zero paniclog has > caused the restart to fail. Please set EX4DEBUG=1 and submit the output. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things."Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#629610: exim4: misleading (?) "failed" message after paniclog warning
Package: exim4 Version: 4.72-6 Severity: normal # /etc/init.d/exim4 restart Stopping MTA for restart: exim4_listener. Restarting MTA: exim4. ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly broken ... failed! I read the "... failed!" as meaning that the non-zero paniclog has caused the restart to fail. However, netstat -nlp indicates that exim is running and listening on port 25, as expected. The "failed" message seems inappropriate in this setting. If it actually means something else is broken, it should indicate what. My paniclog does have stuff in it, and I have some mail that is currently undeliverable because my local cyrus is not running. This is on a virtual machine that had lenny installed and has been dist-upgraded to squeeze. I have fiddled a bit with the config files so I can get mail out of the box. -- Package-specific info: Exim version 4.72 #1 built 31-Jan-2011 18:42:28 Copyright (c) University of Cambridge, 1995 - 2007 Berkeley DB: Berkeley DB 4.8.30: (April 9, 2010) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 GnuTLS compile-time version: 2.8.6 GnuTLS runtime version: 2.8.6 Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to generate # exim configuration macros for the configuration file. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='internet' dc_other_hostnames='vm-lenny.kvm.lan' dc_local_interfaces='' dc_readhost='' dc_relay_domains='markov.biostat.ucsf.edu' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='' CFILEMODE='644' dc_use_split_config='true' dc_hide_mailname='' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' mailname:vm-lenny.kvm.lan -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages exim4 depends on: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii exim4-base4.72-6 support files for all Exim MTA (v4 ii exim4-daemon-light4.72-6 lightweight Exim MTA (v4) daemon exim4 recommends no packages. exim4 suggests no packages. -- debconf information: exim4/drec: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org