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 254177-1391920
for <surgemail-list@netwin.co.nz>; Fri, 09 Mar 2018 03:35:25 +0000
X-Return-Path: john
X-Default-Received-SPF: pass (skip=forwardok (res=PASS));
From: John Wilkes
Content-Transfer-Encoding: quoted-printable
Date: Thu, 8 Mar 2018 19:35:12 -0800
Subject: [SurgeMail List] unclean shutdown
To: surgemail-list@netwin.co.nz
Message-Id: <4F98124E-C7B7-46CB-8A39-05902126E75F@wilkes.com>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
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=44 Friend=58 Surbl=0 Catch=0 r=0 ip=204.238.32.2
X-IP-stats: Notspam Incoming Outgoing Last 0, First 62, in=4462, out=80, 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
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
One of the advantages of being disorderly is that
I am constantly making interesting discoveries.
|