crash on windows server 2003 sp2

[scribebox]

Faulting application SABnzbd.exe, version 0.4.5.0, faulting module python25.dll, version 0.0.0.0, fault address 0x000728f5.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

ANY IDEAS?

[shypike]

None.
I'm not claiming that SABnzbd is faultless, but this type of error is extremely rare
in any Python application and totally uninformative about the cause.
Could be anything, SABnzbd coding error, Python run-time errors, defective memory etc. etc.

Without more information about what SABnzbd was doing at the time
(preferably logfiles) and above all a reproducing scenario, it's a hopeless quest.

[scribebox]

The application, C:\Program Files\SABnzbd\SABnzbd.exe, generated an application error The error occurred on 12/11/2008 @ 10:25:12.307 The exception generated was c0000005 at address 1E082047 (PYTHON25!PyList_Append)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

drwatson, ill drag out some log files

[scribebox]

Yea, its crashed four times in the last two days...... im going to look around in the logfiles... see if i can match up the event log timestamp... see what was going on....

[shypike]

The SABnzbd logfiles are the most useful. The Windows event-logs are mostly uninformative.

[scribebox]

not a lot is going on during the crashes on the logfiles... if anything... just normal downloading, im going to clear out, and wait for it to crash again, and pull the log / eventviewer...

has sabnzbd been tested on a windows server 2003 environment? wonder if i would be better off running it in a vm session.

-scribebox

[shypike]

I have used it myself for all my downloading for a year, 0 problems.
Ran it as a service (requires some tweaking).
A friend of mine still uses in on Server2003, never hear complaints.

Half a year ago I switched to Ubuntu-server.

[scribebox]

The application, C:\Program Files\SABnzbd\SABnzbd.exe, generated an application error The error occurred on 12/15/2008 @ 16:38:58.775 The exception generated was c0000005 at address 1E0728F8 (PYTHON25!PyFuture_FromAST)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


gah, this time the entire server went down unexpectedly.

YAY... im working remotely, ill post logs once i get access.

[scribebox]

i moved sabnzbd's working folders off of my 2tb raid5 array, and set them on my 500GB temporary store, and it looks like that cleared it up.. it seemed that sabnzbd would crash on the repair process...

ill post more info as i find out.

-scribe

[scribebox]

http://www.speedfile.org/999698 here are the log files from after the crash, the password to the archive is password123456 here is what event viewer is showing.

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 12/21/2008
Time: 11:19:21 PM
User: N/A
Computer: SCRIBESERVER
Description:
Faulting application SABnzbd.exe, version 0.4.6.0, faulting module python25.dll, version 0.0.0.0, fault address 0x00064f7d.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74  Applicat
0008: 69 6f 6e 20 46 61 69 6c  ion Fail
0010: 75 72 65 20 20 53 41 42  ure  SAB
0018: 6e 7a 62 64 2e 65 78 65  nzbd.exe
0020: 20 30 2e 34 2e 36 2e 30    0.4.6.0
0028: 20 69 6e 20 70 79 74 68    in pyth
0030: 6f 6e 32 35 2e 64 6c 6c  on25.dll
0038: 20 30 2e 30 2e 30 2e 30    0.0.0.0
0040: 20 61 74 20 6f 66 66 73    at offs
0048: 65 74 20 30 30 30 36 34  et 00064
0050: 66 37 64                  f7d   

[shypike]

Thanks for sending the info.
Unfortunately, the data is inconclusive.
SABnzbd was downloading.

BTW, the last log entry is 2008-12-17.
When did the crash occur?
How long was it running?

[q-silver]

Hello all,

I am seeing this same error but on XP SP3 so perhaps I can help.  I am using 0.4.7.  Except in my case it reports:

Faulting application sabnzbd.exe, version 0.4.6.0, faulting module python25.dll, version 0.0.0.0, fault address 0x00082488.

I have looked through the logs but there do not seem to be any obvious problems.

The first time that I used sabnxbd it ran for a number of hours before crashing my computer (I discoverd the problem when I went back to check the computer and found that it had rebooted).

I checked the config and started the program at 01:13 and the windows log showed that it died at 01:23:01.  The last log entry was for 01:23:00.

I then updated to 0.4.7 (I was on 0.4.6 before) and ran again at 01:32:14.  This time it looks like it ran untill  02:13:39.  Windows shows 02:13:42.

When the program restarted it looks like it started unrarring.  It may well have been trying to unrar the time before too but I do not know.

I have tried moving the temp space to another drive as was suggested above but can not without clearing my queue.

Would it help if I send logs?  Anything else I can try?

Thanks

[switch]

A full application exit is something that is hard for us to debug as it really shouldn't be happening. When something goes wrong with our code the error is handled cleanly by python. However in this case something is going wrong with python itself.

I'm not sure the logs will be much use, the only thing I can recommend trying is installing the c++ redistributable package in case you have some dll's missing.

[q-silver]

Ok, Thanks.  I assume that you mean: Microsoft Visual C++ 2005 Redistributable Package (x86).  I have just installed and will try again and let you know.

Are there debug tools for Python or a Python logging tool that I might try?

Thanks

[q-silver]

I installed the redist package and started at 23:00. Crashed at 23:15.

Perhaps a newer version of Python?

This is really too bad...  The software looks great.  I only wish that I could use it.