Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!proxad.net!feeder1-2.proxad.net!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.009 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; '32-bit': 0.09; 'downtime': 0.09; 'mess': 0.09; 'report,': 0.09; 'restarted': 0.09; 'testing,': 0.09; 'cc:addr:python-list': 0.11; 'python': 0.11; 'jan': 0.12; '2.7.2': 0.16; '6th': 0.16; 'break-word;': 0.16; 'crashed': 0.16; 'dump': 0.16; 'reproduce': 0.16; 'space;': 0.16; 'wing': 0.16; 'word-wrap:': 0.16; 'helvetica;': 0.16; 'wrote:': 0.18; 'looked': 0.18; 'app': 0.19; 'thanks.': 0.20; 'cc:addr:python.org': 0.22; ' In-Reply-To: <7FF67692-9F7B-4EE1-AD9F-83DAC545A78A@mac.com> Date: Tue, 13 Jan 2015 08:05:17 -0900 References: <7FF67692-9F7B-4EE1-AD9F-83DAC545A78A@mac.com> To: William Ray Wing X-Mailer: Apple Mail (2.1878.6) Cc: python-list X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 200 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1421168721 news.xs4all.nl 2952 [2001:888:2000:d::a6]:39978 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:83708 --Apple-Mail=_5030D23A-AA41-4699-8815-3B7073B506AB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Jan 13, 2015, at 6:27 AM, William Ray Wing wrote: >=20 >> On Jan 9, 2015, at 12:40 PM, Israel Brewster = wrote: >>=20 >> I have a long-running python/CherryPy Web App server process that I = am running on Mac OS X 10.8.5. Python 2.7.2 running in 32-bit mode (for = now, I have the code in place to change over to 64 bit, but need to = schedule the downtime to do it). On the 6th of this month, during normal = operation from what I can tell, and after around 33 days of trouble-free = uptime, the python process crashed with a SIGABRT. I restarted the = process, and everything looked good again until yesterday, when it again = crashed with a SIGABRT. The crash dump the system gave me doesn't tell = me much, other than that it looks like python is calling some C function = when it crashes. I've attached the crash report, in case it can mean = something more to someone else. >>=20 >> Can anyone give me some hints as to how to track down the cause of = this crash? It's especially problematic since I can't mess with the live = server for testing, and it is quite a while between crashes, making it = difficult, if not impossible, to reproduce in testing. Thanks. >> ----------------------------------------------- >> Israel Brewster >> Systems Analyst II >> Ravn Alaska >> 5245 Airport Industrial Rd >> Fairbanks, AK 99709 >> (907) 450-7293 >> ----------------------------------------------- >=20 >=20 > Can you run the application in an IDE? Yes - I run it through Wing during development. I don't think that would = be such a good option for my production machine, however. If it gets = really bad I'll consider it though - that should at least tell me where = it is crashing. >=20 > -Bill ----------------------------------------------- Israel Brewster Systems Analyst II Ravn Alaska 5245 Airport Industrial Rd Fairbanks, AK 99709 (907) 450-7293 ----------------------------------------------- --Apple-Mail=_5030D23A-AA41-4699-8815-3B7073B506AB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On Jan = 13, 2015, at 6:27 AM, William Ray Wing <wrw@mac.com> wrote:


On = Jan 9, 2015, at 12:40 PM, Israel Brewster <israel@ravnalaska.net> wrote:

I have a = long-running python/CherryPy Web App server process that I am running on = Mac OS X 10.8.5. Python 2.7.2 running in 32-bit mode (for now, I have = the code in place to change over to 64 bit, but need to schedule the = downtime to do it). On the 6th of this month, during normal operation = from what I can tell, and after around 33 days of trouble-free uptime, = the python process crashed with a SIGABRT. I restarted the process, and = everything looked good again until yesterday, when it again crashed with = a SIGABRT. The crash dump the system gave me doesn't tell me much, other = than that it looks like python is calling some C function when it = crashes. I've attached the crash report, in case it can mean something = more to someone else.

Can anyone give me some hints as to how to track down the = cause of this crash? It's especially problematic since I can't mess with = the live server for testing, and it is quite a while between crashes, = making it difficult, if not impossible, to reproduce in testing. = Thanks.
-----------------------------------------------
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
-----------------------------------------------
<= /div>

Can you run = the application in an = IDE?

Yes - I run it through = Wing during development. I don't think that would be such a good option = for my production machine, however. If it gets really bad I'll consider = it though - that should at least tell me where it is = crashing.


-Bill

-----------------------------------------------
Israel = Brewster
Systems = Analyst II
Ravn = Alaska
5245 = Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
-----------------------------------------------
<= div>
= --Apple-Mail=_5030D23A-AA41-4699-8815-3B7073B506AB--