Thanks Chris! Didn’t notice the folder permissions/ownership on the /opt/surgemail directory were different. Modified that and it’s syncing Still popping up with an occasional error about renaming files, but the error is that they don’t exist.. so I think that’s just because it’s still syncing. I’ll let the sync complete and then worry about it if it’s still an issue.
-- Regards, Tim Otto Information Technology, System Administrator Crocker Client Support Hours (EST): Mon - Fri 8am-8pm Telephone: Springfield 413-475-1000 Northampton 413-387-1000 Email: support@crocker.com Web: http://www.crocker.com/index.php/support This e-mail and any attachments to it contain confidential business information intended solely for recipients. If you have received this e-mail in error, please do not forward or distribute it. Please notify the sender and delete this message immediately from your computer.
From: Support ChrisP <surgemail-support@netwinsite.com> Sent: Monday, February 11, 2019 4:27 PM To: surgemail-list@netwin.co.nz Subject: Re: [SurgeMail List] Mirror Configuration Fails
Check file protections,
ls -ald /opt
ls -ald /opt/surgemail
ls -ald /opt/surgemail/XXXX.XXX
and/or test manually:
sudo mail
touch /opt/surgemail/xxxxxx.xx/test.txt
Ownership should be user 'mail' and match /usr/local/surgemail folder and contents
Also examine mirror.log and mirrorin.log and mail.log on the slave to see if it's saying anything useful :-).
ChrisP.
On Tuesday 12/02/2019 at 9:43 am, Tim Otto wrote:
We are attempting to migrate our existing on-premise surgemail server to AWS and would like to do so via mirroring. So far we have the new slave surgemail server spun up with the same version of surgemail as our primary server installed. The mirroring settings have been added to surgemail.ini on both servers, tellmail has been reloaded, and I can telnet between the two servers on port 110 without issue, yet files aren’t syncing properly. The issue is effecting all domains/files it tries to sync, so I’ve masked the customer domain. Otherwise the error reported under mirroring in “tellmail status” is as follows: LastErr: -ERR store failed ndbOpen sz=19373 (/opt/surgemail/XXXX.XXX/uh/vi/duke/mdir/new/u28950 Namely “-Err store failed ndbOpen” is always consistent. Any suggestions on what else to check or why this isn’t working? -- Regards, Tim Otto Information Technology, System Administrator Crocker Client Support Hours (EST): Mon - Fri 8am-8pm Telephone: Springfield [ Image ] 413-654-1000 Greenfield [ Image ] 413-475-1000 Northampton [ Image ] 413-387-1000 Email: support@crocker.com Web: http://www.crocker.com/index.php/support This e-mail and any attachments to it contain confidential business information intended solely for recipients. If you have received this e-mail in error, please do not forward or distribute it. Please notify the sender and delete this message immediately from your computer.
We are attempting to migrate our existing on-premise surgemail server to AWS and would like to do so via mirroring. So far we have the new slave surgemail server spun up with the same version of surgemail as our primary server installed. The mirroring settings have been added to surgemail.ini on both servers, tellmail has been reloaded, and I can telnet between the two servers on port 110 without issue, yet files aren’t syncing properly. The issue is effecting all domains/files it tries to sync, so I’ve masked the customer domain. Otherwise the error reported under mirroring in “tellmail status” is as follows: LastErr: -ERR store failed ndbOpen sz=19373 (/opt/surgemail/XXXX.XXX/uh/vi/duke/mdir/new/u28950
Namely “-Err store failed ndbOpen” is always consistent. Any suggestions on what else to check or why this isn’t working?
-- Regards, Tim Otto Information Technology, System Administrator Crocker Client Support Hours (EST): Mon - Fri 8am-8pm Telephone: Springfield [ Image ] 413-654-1000 Greenfield [ Image ] 413-475-1000 Northampton [ Image ] 413-387-1000 Email: support@crocker.com Web: http://www.crocker.com/index.php/support This e-mail and any attachments to it contain confidential business information intended solely for recipients. If you have received this e-mail in error, please do not forward or distribute it. Please notify the sender and delete this message immediately from your computer.
Last Message | Next Message