RE: issues with email migration
This morning, I tried adding this to rc.conf and moved my link for /www from local to the nfs . rpc_lockd_enable=YES rpc_statd_enable=YES and I experienced the same issues I had before. It would seem that postfix and other assorted mail programs have no issue with accessing /mail on an nfs share but everything residing in /www don't seem to like it at all. I have no choice but to leave this as it is and set up a similar arrangement on my new server. Thank you to everyone who responded. -Original Message- From: Tim Judd [mailto:taj...@gmail.com] Sent: Saturday, October 31, 2009 10:51 AM To: da...@farmington.k12.mo.us Cc: freebsd-questions@freebsd.org Subject: Re: issues with email migration On 10/31/09, da...@farmington.k12.mo.us da...@farmington.k12.mo.us wrote: only one issue with that. The server in question is an emc clereon(sorry not at work to look at the specifics) and at this point the only access I have to it is a web interface and am unable to access a command line. Also a stupid question my plan is to set up another server to access the nfs share to provide better email service. would this impact it in any way? snip replies Not if file locking and the daemons take care of everything like they should. Remember, file locking is mandatory for some things, especially mbox files, password files, or anything else that requires exclusive access to a file. If two systems try to access the same locked file, the 2nd will be told it won't be able to get an exclusive lock, because the 1st already has it locked. You're on the right track. Keep it going. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: issues with email migration
On 11/2/09, David Patton da...@farmington.k12.mo.us wrote: This morning, I tried adding this to rc.conf and moved my link for /www from local to the nfs . rpc_lockd_enable=YES rpc_statd_enable=YES Adding them alone just tells the system at startup to start these. and I experienced the same issues I had before. It would seem that postfix and other assorted mail programs have no issue with accessing /mail on an nfs share but everything residing in /www don't seem to like it at all. Did you start statd and lockd by hand before trying the /www again? I have no choice but to leave this as it is and set up a similar arrangement on my new server. Thank you to everyone who responded. -Original Message- From: Tim Judd [mailto:taj...@gmail.com] Sent: Saturday, October 31, 2009 10:51 AM To: da...@farmington.k12.mo.us Cc: freebsd-questions@freebsd.org Subject: Re: issues with email migration On 10/31/09, da...@farmington.k12.mo.us da...@farmington.k12.mo.us wrote: only one issue with that. The server in question is an emc clereon(sorry not at work to look at the specifics) and at this point the only access I have to it is a web interface and am unable to access a command line. Also a stupid question my plan is to set up another server to access the nfs share to provide better email service. would this impact it in any way? snip replies Not if file locking and the daemons take care of everything like they should. Remember, file locking is mandatory for some things, especially mbox files, password files, or anything else that requires exclusive access to a file. If two systems try to access the same locked file, the 2nd will be told it won't be able to get an exclusive lock, because the 1st already has it locked. You're on the right track. Keep it going. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: issues with email migration
Yes sir, I added them to the rc.conf, changed the links to point where I wanted them and rebooted, same issues. I cant waste anymore time with what I wanted to do. I will leave /mail on the nfs share and just build a new server. I have 2 days and hopefully I will keep my job. Wish me luck... -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Tim Judd Sent: Monday, November 02, 2009 10:10 AM To: David Patton Cc: freebsd-questions@freebsd.org Subject: Re: issues with email migration On 11/2/09, David Patton da...@farmington.k12.mo.us wrote: This morning, I tried adding this to rc.conf and moved my link for /www from local to the nfs . rpc_lockd_enable=YES rpc_statd_enable=YES Adding them alone just tells the system at startup to start these. and I experienced the same issues I had before. It would seem that postfix and other assorted mail programs have no issue with accessing /mail on an nfs share but everything residing in /www don't seem to like it at all. Did you start statd and lockd by hand before trying the /www again? I have no choice but to leave this as it is and set up a similar arrangement on my new server. Thank you to everyone who responded. -Original Message- From: Tim Judd [mailto:taj...@gmail.com] Sent: Saturday, October 31, 2009 10:51 AM To: da...@farmington.k12.mo.us Cc: freebsd-questions@freebsd.org Subject: Re: issues with email migration On 10/31/09, da...@farmington.k12.mo.us da...@farmington.k12.mo.us wrote: only one issue with that. The server in question is an emc clereon(sorry not at work to look at the specifics) and at this point the only access I have to it is a web interface and am unable to access a command line. Also a stupid question my plan is to set up another server to access the nfs share to provide better email service. would this impact it in any way? snip replies Not if file locking and the daemons take care of everything like they should. Remember, file locking is mandatory for some things, especially mbox files, password files, or anything else that requires exclusive access to a file. If two systems try to access the same locked file, the 2nd will be told it won't be able to get an exclusive lock, because the 1st already has it locked. You're on the right track. Keep it going. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: issues with email migration
only one issue with that. The server in question is an emc clereon(sorry not at work to look at the specifics) and at this point the only access I have to it is a web interface and am unable to access a command line. Also a stupid question my plan is to set up another server to access the nfs share to provide better email service. would this impact it in any way? thank you again On 10/30/09, usleepl...@gmail.com usleepl...@gmail.com wrote: Hi David, On Fri, Oct 30, 2009 at 1:59 PM, David Patton da...@farmington.k12.mo.uswrote: 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: issues with email migration
On 10/31/09, da...@farmington.k12.mo.us da...@farmington.k12.mo.us wrote: only one issue with that. The server in question is an emc clereon(sorry not at work to look at the specifics) and at this point the only access I have to it is a web interface and am unable to access a command line. Also a stupid question my plan is to set up another server to access the nfs share to provide better email service. would this impact it in any way? snip replies Not if file locking and the daemons take care of everything like they should. Remember, file locking is mandatory for some things, especially mbox files, password files, or anything else that requires exclusive access to a file. If two systems try to access the same locked file, the 2nd will be told it won't be able to get an exclusive lock, because the 1st already has it locked. You're on the right track. Keep it going. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: issues with email migration
Hi David, On Fri, Oct 30, 2009 at 1:59 PM, David Patton da...@farmington.k12.mo.uswrote: 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 kind regards, usleep ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: issues with email migration
On 10/30/09, usleepl...@gmail.com usleepl...@gmail.com wrote: Hi David, On Fri, Oct 30, 2009 at 1:59 PM, David Patton da...@farmington.k12.mo.uswrote: 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
