Snapshot 20091209 postscreen failure
in [Postfix]
|
From: "Len Conrad" on 17 Dec 2009 12:39 I did the usual freebsd upgrade postfix stop make make reinstall ( with setenv FORCE_PKG_REGISTER ) postfix start mx1# postconf mail_version mail_version = 2.7-20091209 ========================================================================== dnsblog unix - - n - 0 dnsblog smtp inet n - - - 1 postscreen smtpd pass - - - - 200 smtpd #smtp inet n - n - 1000 smtpd runs as above gives: Dec 17 11:28:38 mx1 postfix/master[4857]: daemon started -- version 2.7-20091209, configuration /usr/local/etc/postfix then no other errors until immediately: Dec 17 11:28:40 mx1 postfix/master[4857]: warning: process /usr/local/libexec/postfix/postscreen pid 4867 exit status 1 Dec 17 11:28:40 mx1 postfix/master[4857]: warning: /usr/local/libexec/postfix/postscreen: bad command startup -- throttling I tried -v on the postscreen master.cf line, but got no more log lines. If comment the first three lines, uncomment the 4th, postfix stop/start postfix works. btw, after postfix upgrades, it seems that I have to postmap all the .map files or postfix chokes. thanks Len
From: Wietse Venema on 17 Dec 2009 12:48 Len Conrad: > > I did the usual freebsd upgrade > > postfix stop > > make > make reinstall ( with setenv FORCE_PKG_REGISTER ) > > postfix start > > > > mx1# postconf mail_version > mail_version = 2.7-20091209 > > > ========================================================================== > dnsblog unix - - n - 0 dnsblog > smtp inet n - - - 1 postscreen > smtpd pass - - - - 200 smtpd > #smtp inet n - n - 1000 smtpd > > runs as above gives: > > Dec 17 11:28:38 mx1 postfix/master[4857]: daemon started -- version 2.7-20091209, configuration /usr/local/etc/postfix > > then no other errors until immediately: > > Dec 17 11:28:40 mx1 postfix/master[4857]: warning: process /usr/local/libexec/postfix/postscreen pid 4867 exit status 1 > > Dec 17 11:28:40 mx1 postfix/master[4857]: warning: /usr/local/libexec/postfix/postscreen: bad command startup -- throttling postscreen will also log "fatal: reason for exit status 1". If your syslog daemon sends "FATAL" and "WARNING" logs to different files, then consider using a configuration that keeps those records together. Wietse > I tried -v on the postscreen master.cf line, but got no more log lines. > > If comment the first three lines, uncomment the 4th, postfix stop/start postfix works. > > btw, after postfix upgrades, it seems that I have to postmap all the .map files or postfix chokes. > > thanks > Len > > >
From: "Len Conrad" on 17 Dec 2009 12:54 ---------- Original Message ---------------------------------- From: wietse(a)porcupine.org (Wietse Venema) Date: Thu, 17 Dec 2009 12:48:37 -0500 (EST) >Len Conrad: >> >> I did the usual freebsd upgrade >> >> postfix stop >> >> make >> make reinstall ( with setenv FORCE_PKG_REGISTER ) >> >> postfix start >> >> >> >> mx1# postconf mail_version >> mail_version = 2.7-20091209 >> >> >> ========================================================================== >> dnsblog unix - - n - 0 dnsblog >> smtp inet n - - - 1 postscreen >> smtpd pass - - - - 200 smtpd >> #smtp inet n - n - 1000 smtpd >> >> runs as above gives: >> >> Dec 17 11:28:38 mx1 postfix/master[4857]: daemon started -- version 2.7-20091209, configuration /usr/local/etc/postfix >> >> then no other errors until immediately: >> >> Dec 17 11:28:40 mx1 postfix/master[4857]: warning: process /usr/local/libexec/postfix/postscreen pid 4867 exit status 1 >> >> Dec 17 11:28:40 mx1 postfix/master[4857]: warning: /usr/local/libexec/postfix/postscreen: bad command startup -- throttling > >postscreen will also log "fatal: reason for exit status 1". > >If your syslog daemon sends "FATAL" and "WARNING" logs to different >files, then consider using a configuration that keeps those records >together. > > Wietse here ya go Dec 17 11:28:39 mx1 postfix/postscreen[4867]: fatal: open database /var/db/postfix/ps_cache.db: Invalid argument Len
From: Victor Duchovni on 17 Dec 2009 13:16 On Thu, Dec 17, 2009 at 06:54:37PM +0100, Len Conrad wrote: > Dec 17 11:28:39 mx1 postfix/postscreen[4867]: fatal: open database /var/db/postfix/ps_cache.db: Invalid argument Did you switch from btree to hash or vice-versa? Delete the cache and start from scratch... -- Viktor. Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the "Reply-To" header. To unsubscribe from the postfix-users list, visit http://www.postfix.org/lists.html or click the link below: <mailto:majordomo(a)postfix.org?body=unsubscribe%20postfix-users> If my response solves your problem, the best way to thank me is to not send an "it worked, thanks" follow-up. If you must respond, please put "It worked, thanks" in the "Subject" so I can delete these quickly.
From: Wietse Venema on 17 Dec 2009 13:19
Len Conrad: > Dec 17 11:28:39 mx1 postfix/postscreen[4867]: fatal: open database /var/db/postfix/ps_cache.db: Invalid argument > You switched Berkeley DB versions, or you switched btree/hash types. Delete the file, and try again. Wietse |