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 272819-1391920
for <surgemail-list@netwin.co.nz>; Fri, 09 Mar 2018 16:01:59 +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: <A5AAE50D-E8F3-4054-9404-1A5AAAB4B9D2@ferebee.net>
Date: Fri, 9 Mar 2018 08:01:44 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0707818C-3A66-407F-943B-893EDE2F6EC1@wilkes.com>
References: <4F98124E-C7B7-46CB-8A39-05902126E75F@wilkes.com> <A5AAE50D-E8F3-4054-9404-1A5AAAB4B9D2@ferebee.net>
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=48 Friend=62 Surbl=0 Catch=0 r=0 ip=204.238.32.2
X-IP-stats: Notspam Incoming Outgoing Last 0, First 62, in=4695, out=83, 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
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.
--
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 12:44 AM, Chris Ferebee <cf@ferebee.net> wrote:
>
> John,
>
> when Ubuntu shuts down, it will send all processes a TERM signal, i. e., politely asking them to quit. After a certain length of time, it will send any remaining processes a KILL signal, forcing them to quit. If you kill -KILL SurgeMail, that’s an unclean shutdown.
>
> Presumably, SurgeMail is taking a long time to shut down, perhaps ChrisP has some ideas about that, or maybe it just has a lot on its plate? When you run
>
> # tellmail shutdown
>
> how long does it take until all SurgeMail processes exit?
>
> I don’t use Ubuntu myself, but I the shutdown is controlled by systemd, and I understand that if you set the line
>
> DefaultTimeoutStopSec=
>
> in /etc/systemd/system.conf to a higher value (e. g. 240), that will give processes more time to shutdown before they are killed. The default is 90 seconds AFAIK.
>
> Best,
> Chris
>
>
>> Am 09.03.2018 um 04:35 schrieb John Wilkes <john@wilkes.com>:
>>
>> I’ve been running 7.3c3-3 on Ubuntu 16.04. When I reboot the system I always see an error message on the SurgeMail status page:
>>
>> LAST SHUTDOWN WAS UNCLEAN :-) -- Examine logs crash*.log to establish cause
>>
>> The log files don’t give any hints about the problem that I can see.
>>
>> I am in the process of moving my server to a new location, and I’ve switched to Centos 7. I see the same error there on a fresh, brand new installation of SurgeMail 7.3c3-3 with no accounts and the default surgemail.ini file.
>>
>> I did a manual shutdown with "/etc/init.d/surgemail stop” and it shutdown cleanly.
>>
>> Any ideas how to get a clean automatic SurgeMail shutdown when I’m shutting down the system? Is this a known problem?
>>
>> --
>> John Wilkes
>> john@wilkes.com
>
>
|