Received-SPF: pass (Last token {mx} (res=PASS)) client-ip=204.238.32.2; envelope-from=<john@wilkes.com>; x-ip-name=mx.wilkes.com;
X-Received: from wilkes.com (mx.wilkes.com [204.238.32.2])
by netwin.co.nz (SurgeMail 7.3h) with ESMTP id 276387-1391920
for <surgemail-list@netwin.co.nz>; Fri, 09 Mar 2018 18:00:31 +0000
X-Return-Path: john
X-Default-Received-SPF: pass (skip=forwardok (res=PASS));
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [SurgeMail List] unclean shutdown
From: John Wilkes
In-Reply-To: <DBB4E323-4678-40DC-AD28-9B8DA6E7B26F@wilkes.com>
Date: Fri, 9 Mar 2018 10:00:23 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2370E45-6EE9-4342-A7C5-CEC78EABB91B@wilkes.com>
References: <cb742a3e-a53a-c776-5c0b-f8f40cef3985@easent.net> <DBB4E323-4678-40DC-AD28-9B8DA6E7B26F@wilkes.com>
To: surgemail-list@netwin.co.nz
X-Mailer: Apple Mail (2.3124)
X-X-Authenticated-User: john@wilkes.com
X-Originating-IP: 204.238.32.2
X-Country: code=US country="United States" ip=204.238.32.2
X-Rcpt-To: <surgemail-list@netwin.co.nz>
X-SpamDetect: ****: 4.2 sd=4.2 lv=0.00 nok=3/0 m=2 nf=7 Exact 0.04(X-myrbl:Color=white) 0.90(X-Phrase:isspam) 0.77(X-Verify-Helo:-ERR) 0.39(X-Country:States) 0.44(X-LangGuess:English) 0.52(spfpass) 0.49(X-NotAscii:utf) Saned 5.0 Sval 4.2 bsan 5.0 Moved 5.0->4.2 Sval 4.2
X-NotAscii: charset=utf-8
X-LangGuess: English
X-Probe: +OK skipped, known ip address
X-Phrase: IsSpam score=1.00
X-Verify-Helo: -ERR missmatch: wilkes.com->204.238.32.2->mx.wilkes.com
X-MyRbl: Color=White Age=62 Spam=0 Notspam=1 Stars=0 Good=49 Friend=62 Surbl=0 Catch=0 r=0 ip=204.238.32.2
X-IP-stats: Notspam Incoming Outgoing Last 0, First 62, in=4907, out=86, spam=0 Known=true ip=204.238.32.2
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
“can’t find” not “can find”
--
John Wilkes
john@wilkes.com
My life has been a series of tragedies and
triumphs, but I wouldn’t have it any other way.
> On Mar 9, 2018, at 9:42 AM, John Wilkes <john@wilkes.com> wrote:
>
> The default, standard system shutdown kills the main surgemail process but not the swatch process? That probably explains why I can find any obviously useful information about the error in the SurgeMail crash log file.
>
> Question for SurgeMail support: Can this be fixed in a future SurgeMail release?
>
> --
> John Wilkes
> john@wilkes.com
>
> “Learn the rules like a pro, so you can
> break them like an artist.” -- Pablo Picasso
>
>
>
>> On Mar 9, 2018, at 8:07 AM, Ed <ed@easent.net> wrote:
>>
>> If you look for the "swatch" process after you kill the main surge process and then kill it you won't get that error.
>>
>> We've been running on linux for years and never get that error when we kill the "swatch" process after the rest of it.
>>
>> --Ed
>>
>> On 03/09/2018 11:01 AM, John Wilkes wrote:
>>> Both “tellmail shutdown” and "/etc/init.d/surgemail stop” finish quickly. The init.d/surgemail method takes a little longer because the script has a 9 second delay at the end to give the SurgeMail process some time to stop cleanly.
>>> I see the same problem on a new Centos 7 installation, so it is not unique to Ubuntu. With Centos, the system shutdown process waits 5 minutes for surgemail to shutdown before giving up. I always see the “unclean “ message in SurgeMail status after rebooting, unless I manually stop SurgeMail before shutting down the system.
>>
>> --
>> -----------------------------------------------------------
>> EAS Enterprises LLC
>> World Class Web and Email Hosting Solutions
>> IPv6 ready today for your needs of tomorrow!
>> Ask us about dual-stacking your site
>> www.easent.net
>>
>
|