Date: Fri, 30 Oct 2009 17:59:50 -0600 From: Tim Judd <tajudd@gmail.com> To: usleepless@gmail.com Cc: David Patton <david@farmington.k12.mo.us>, freebsd-questions@freebsd.org Subject: Re: issues with email migration Message-ID: <ade45ae90910301659m56c7dc32uc756fae0a340b1c5@mail.gmail.com> In-Reply-To: <c39ec84c0910300635n505644f9ye573562ef7b187c5@mail.gmail.com> References: <20091030130054.589B39860E4@mail.farmington.k12.mo.us> <c39ec84c0910300635n505644f9ye573562ef7b187c5@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/30/09, usleepless@gmail.com <usleepless@gmail.com> wrote: > Hi David, > > On Fri, Oct 30, 2009 at 1:59 PM, David Patton > <david@farmington.k12.mo.us>wrote: > >> This morning I moved the contents from the server over to an NFS share. >> >> >> >> This is a freebsd 6.2 server running postfix, courier-imap and >> squirrelmail. >> I used rsync to move the data for /www and /mail over to the nfs share. >> After I made the changed to fstab and rebooted, every thing came up and >> email seemed to be faster but in fact it wasn't. Once I realized that >> there >> was an issue, I changed the link back for the /www directory to the >> original >> location and left the link for /mail pointing to the nfs share. I found >> from >> a search to try newaliaies and the restart postfix but that didn't work. >> >> >> >> Maillog: >> >> Oct 30 06:11:38 bonnie postfix/smtpd[1337]: fatal: shared-lock database >> /www/mailman/data/aliases.db for open: Operation not supported >> >> Oct 30 06:11:39 bonnie postfix/master[889]: warning: process >> /usr/local/libexec/postfix/smtpd pid 1337 exit status 1 >> >> Oct 30 06:11:39 bonnie postfix/master[889]: warning: >> /usr/local/libexec/postfix/smtpd: bad command startup - throttling >> >> >> >> Message: >> >> Oct 30 06:00:27 bonnie postfix/smtpd[1177]: fatal: shared-lock database >> /www/mailman/data/aliases.db for open: Operation not supported >> >> Oct 30 06:01:28 bonnie postfix/smtpd[1184]: fatal: shared-lock database >> /www/mailman/data/aliases.db for open: Operation not supported >> >> Oct 30 06:02:29 bonnie postfix/smtpd[1192]: fatal: shared-lock database >> /www/mailman/data/aliases.db for open: Operation not supported >> >> Oct 30 06:03:30 bonnie postfix/smtpd[1218]: fatal: shared-lock database >> /www/mailman/data/aliases.db for open: Operation not supported >> >> Oct 30 06:04:31 bonnie postfix/smtpd[1235]: fatal: shared-lock database >> /www/mailman/data/aliases.db for open: Operation not supported >> >> Oct 30 06:05:32 bonnie postfix/smtpd[1256]: fatal: shared-lock database >> /www/mailman/data/aliases.db for open: Operation not supported >> >> Oct 30 06:06:33 bonnie postfix/smtpd[1270]: fatal: shared-lock database >> /www/mailman/data/aliases.db for open: Operation not supported >> >> Oct 30 06:07:34 bonnie postfix/smtpd[1296]: fatal: shared-lock database >> /www/mailman/data/aliases.db for open: Operation not supported >> >> Oct 30 06:08:35 bonnie postfix/smtpd[1307]: fatal: shared-lock database >> /www/mailman/data/aliases.db for open: Operation not supported >> > > although i am certainly not an expert regarding email issues nor NFS, but > could it be that the NFS server needs to support "lockd" and "statd" ? > > i have this in my /etc/rc.conf: > > rpc_lockd_enable="YES" > rpc_statd_enable="YES" On both the server and client. File locking is not supported without these two daemons running. I run diskless clients and I need to support file locking, for when you edit the passwd file with vipw and the like. Please enable the above on both the server and client, start them, then try again.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ade45ae90910301659m56c7dc32uc756fae0a340b1c5>