|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: 'table has changed' problems
From: Rob O'Connor (robo
amazon.co.uk)Date: Tue Oct 24 2000 - 04:14:07 CDT
- Next message: Karen Ellrick: "Double message mystery"
- Previous message: Ralf Hildebrandt: "Re: Header Stripping"
- In reply to: Wietse Venema: "Re: 'table has changed' problems"
- Next in thread: Ralf Hildebrandt: "Re: 'table has changed' problems"
- Reply: Rob O'Connor: "Re: 'table has changed' problems"
- Reply: Ralf Hildebrandt: "Re: 'table has changed' problems"
- Reply: Wietse Venema: "Re: 'table has changed' problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Wietse - I'm using Berkeley DB files as a table. I'll give the postalias
& mv thing a try - but may switch to dbm format tables as I've found other
sites here which are using this without apparent problems.
Thanks,
Rob.
Wietse Venema wrote:
> Rob O'Connor:
> > Hi - seen mention of this recently but it doesn't seem to be a problem
> > for most people. With postfix-1991231-pl08 on Solaris 2.7 in 64 bit mode
> > we get these in syslog when the aliases file is changed (i..e when the
> > file is written) and before newaliases is run:
> >
> > Oct 23 09:28:55 cyclone.amazon.co.uk postfix/local[12643]: table has
> > changed --
> > exiting
> > Oct 23 09:28:55 cyclone.amazon.co.uk postfix/local[12642]: table has
> > changed --
> > exiting
> > Oct 23 09:28:55 cyclone.amazon.co.uk postfix/local[12654]: table has
> > changed --
> > exiting
>
> This is intended behavior - the Postfix local delivery agent detects
> that some table has changed, and terminates so that a new process
> reads the fresh data.
>
> > Now in this window it seems that all aliases are forgotten - not good as
> > we can receive maybe 10 messages in a second so we can suffer quite a
> > few bounces.
>
> What kind of table are you using? Some people reported this with
> Berkeley DB files (file.db).
>
> IF that is the problem, THEN the solution is to rename the table
> after it is created with postmap or postalias:
>
> postalias /etc/mail/aliases.proto && \
> mv /etc/mail/aliases.proto.db /etc/mail/aliases.db
>
> This should not be needed for DBM tables, though (file.pag, file.dir).
>
> > Does it really require stopping and restarting postfix or is there a
> > fix? sendmail doesn't suffer from this problem so I was surprised when I
> > saw it happening.
>
> Perhaps sendmail uses the DBM tables (aliases.pag and aliases.dir).
>
> Please respond to this message.
>
> Wietse
- Next message: Karen Ellrick: "Double message mystery"
- Previous message: Ralf Hildebrandt: "Re: Header Stripping"
- In reply to: Wietse Venema: "Re: 'table has changed' problems"
- Next in thread: Ralf Hildebrandt: "Re: 'table has changed' problems"
- Reply: Rob O'Connor: "Re: 'table has changed' problems"
- Reply: Ralf Hildebrandt: "Re: 'table has changed' problems"
- Reply: Wietse Venema: "Re: 'table has changed' problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]