On Jan 27, 2009, at 7:00 AM, gil.shi...@gmail.com wrote:
On Jan 26, 8:40 pm, Philip Semanchuk <phi...@semanchuk.com> wrote:
On Jan 26, 2009, at 1:13 PM, gil.shi...@gmail.com wrote:
Hi All,
I'm running a program that is acting as a nice interface to sybase'
replication server. The program is using the cherrypy web service
for
the GUI. The process is crashing every few days with no reason. In
the
log I can see INFO and DEBUG (No ERROR) log lines and I do not get
any
TraceBack python's message. This program is running on solaris 9
machine.
Where can I see or what can I do in order to find out what causes
the
process to crash?
I have tried simulating a "traceBack" message and I could see this
traceback message in one of the log files I'm using. When the
process
crashes without my help, I don't have a clue.
Let me know if you need any other info
Although Python isn't immune to fatal errors like you describe, I'd
immediately suspect a 3rd-party module instead, esp. one written in C
or C++. Are you using anything like that?
No I do not.
But you're using CherryPy, aren't you? And as Tim Golden pointed out,
you're probably using another 3rd party lib to talk to Sybase. ISTR
that CherryPy is written in pure Python but if you have a database
adapter lib it probably isn't.
Is there a way to monitor who had "killed" my process?
That's more of a Solaris question than a Python one, and I don't know
much about Solaris. Is there a system log where Solaris records when &
why it has killed errant processes?
--
http://mail.python.org/mailman/listinfo/python-list
