From: ghe on 11 Sep 2009 19:49 I don't understand this line from today's logwatch report: 308 *Warning: Database file needs update I looked and didn't find it in the mail logs, but logwatch is saying it was found 308 times. Google led me to a number of pages that denied me access and a CVS server that didn't make sense. Anybody understand this message? If it's postfix, which database needs updating, and how do I do it? If it's logwatch, please tell me, and I apologize for wasting your time... -- Glenn English ghe(a)slsware.com
From: Mike Cappella on 11 Sep 2009 19:51 On 9/11/09 4:48 PM, ghe wrote: > I don't understand this line from today's logwatch report: > > 308 *Warning: Database file needs update > This message appears when you have a map file that requires postmap'ing to bring the db file up to date relative to the source file. Look at the log messages to see which file is not up to date and run postmap on that file. > I looked and didn't find it in the mail logs, but logwatch is saying it > was found 308 times. Google led me to a number of pages that denied me > access and a CVS server that didn't make sense. Anybody understand this > message? > > If it's postfix, which database needs updating, and how do I do it? If > it's logwatch, please tell me, and I apologize for wasting your time... > -- Mike
From: ghe on 11 Sep 2009 20:06 On Sep 11, 2009, at 5:51 PM, Mike Cappella wrote: >> I don't understand this line from today's logwatch report: >> >> 308 *Warning: Database file needs update >> > > This message appears when you have a map file that requires > postmap'ing to bring the db file up to date relative to the source > file. Look at the log messages to see which file is not up to date > and run postmap on that file. Thank's Mike. I found a mention of virtual with google, but since I couldn't find the message in /var/log/mail*, I couldn't figure it out. Also since I didn't find it, I just re-postmapped 'em all. -- Glenn English ghe(a)slsware.com
From: Wietse Venema on 11 Sep 2009 20:18 ghe: > > On Sep 11, 2009, at 5:51 PM, Mike Cappella wrote: > > >> I don't understand this line from today's logwatch report: > >> > >> 308 *Warning: Database file needs update > >> > > > > This message appears when you have a map file that requires > > postmap'ing to bring the db file up to date relative to the source > > file. Look at the log messages to see which file is not up to date > > and run postmap on that file. > > Thank's Mike. I found a mention of virtual with google, but since I > couldn't find the message in /var/log/mail*, I couldn't figure it out. > > Also since I didn't find it, I just re-postmapped 'em all. Postfix includes the name of the file that is out-of-date: warning: database /etc/postfix/access.db is older than source file /etc/postfix/access This is logged when the output file has not been updated withing 100s after the input file was modified. Wietse
From: Sahil Tandon on 11 Sep 2009 20:25 On Fri, 11 Sep 2009, ghe wrote: > On Sep 11, 2009, at 5:51 PM, Mike Cappella wrote: > >>> I don't understand this line from today's logwatch report: >>> >>> 308 *Warning: Database file needs update >>> >> >> This message appears when you have a map file that requires >> postmap'ing to bring the db file up to date relative to the source >> file. Look at the log messages to see which file is not up to date >> and run postmap on that file. > > Thank's Mike. I found a mention of virtual with google, but since I > couldn't find the message in /var/log/mail*, I couldn't figure it out. You were looking for the wrong error in the Postfix logs. What you posted earlier was generated by logwatch. In Postfix: /* * Warn if the source file is newer than the indexed file, except when * the source file changed only seconds ago. */ if ((dict_flags & DICT_FLAG_LOCK) != 0 && stat(path, &st) == 0 && st.st_mtime > dict_db->dict.mtime && st.st_mtime < time((time_t *) 0) - 100) msg_warn("database %s is older than source file %s", db_path, path); Try searching your Postfix logs for 'older than source file'. -- Sahil Tandon <sahil(a)tandon.net>
|
Next
|
Last
Pages: 1 2 3 Prev: NDR status written to headers rather than body? Next: question about policy daemon time limit |