X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=115-188-8-176-adsl.sparkbb.co.nz;
X-Received: from [192.168.1.66] (115-188-8-176-adsl.sparkbb.co.nz [115.188.8.176])
by netwin.co.nz (SurgeMail 7.3p) with ESMTP (TLS) id 8259617-1391920
for <surgemail-list@netwin.co.nz>; Mon, 11 Feb 2019 23:04:55 +0000
X-Return-Path: surgemail-support
Subject: Re: [SurgeMail List] Mirror Configuration Fails
To: surgemail-list@netwin.co.nz
References: <5c61e886.e29.4e83d700.78aa8c77@netwin.co.nz>
<BN6PR1401MB19544749A07B3C70214D54D980640@BN6PR1401MB1954.namprd14.prod.outlook.com>
From: Surgemail Support
Message-ID: <943afb58-d95c-08a9-7693-33e8335221a0@netwinsite.com>
Date: Tue, 12 Feb 2019 12:04:48 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <BN6PR1401MB19544749A07B3C70214D54D980640@BN6PR1401MB1954.namprd14.prod.outlook.com>
Content-Language: en-US
X-Authenticated-User: surgemail-support
X-Rcpt-To: <surgemail-list@netwin.co.nz>
X-SpamDetect: : 0.000000
X-Info: aspam skipped due to (g_smite_skip_relay)
X-Encryption: SSL encrypted
X-IP-stats: Incoming Last 0, First 4, in=243, out=0, spam=0 ip=115.188.8.176
List-Unsubscribe: <mailto:surgemail-list-leave@netwin.co.nz?subject=unsubscribe>
X-Mailing-List: surgemail-list@netwin.co.nz
List-ID: <surgemail-list@netwin.co.nz>
Precedence: bulk
Reply-To: surgemail-list@netwin.co.nz
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
On 12/02/2019 11:32 AM, Tim Otto wrote:
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.
Yup, those errors are usually fine.
chrisP.
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
Content-Transfer-Encoding: base64
Content-ID: <part1.DD4FC54C.7A0F97BE@netwinsite.com>
Content-Disposition: inline;
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.