Ubuntu
pyzor package

[apport] pyzor crashed with IOError in run()

Bug #115853 reported by glenstewart on 2007-05-20

26

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	pyzor (Ubuntu)	Invalid	Undecided	Unassigned
	spamassassin (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

Binary package hint: pyzor

This has happened twice now, since updating to Spamassassin 3.2.0

ProblemType: Crash
Architecture: amd64
Date: Sun May 20 07:45:22 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/pyzor
InterpreterPath: /usr/bin/python2.5
Package: pyzor 1:0.4.0+cvs20030201-6.1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/pyzor report
ProcCwd: /root
ProcEnviron:
PATH=/usr/bin:/bin:/usr/local/bin
SHELL=/bin/sh
LANG=C
LANGUAGE=en
PythonArgs: ['/usr/bin/pyzor', 'report']
SourcePackage: pyzor
Uname: Linux server 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux

Revision history for this message

glenstewart (glen-stewart) wrote on 2007-05-20:

#1

Dependencies.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (9.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (618 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (700 bytes, text/plain; charset="utf-8")

Revision history for this message

Scott Kitterman (kitterman) wrote on 2007-05-22:

#2

Since the error is a broken pipe:

IOError: [Errno 32] Broken pipe

Not sure which package is responsible.

Revision history for this message

Rich Johnson (nixternal) wrote on 2007-05-28:

#3

Hey there,

I just tried reproducing this and was unable to. I have tried it both with pyzord running and not running. My 2 main spam collectors are bogo and spamassassin. I used the --mbox filter with the report, whitelist,

Changed in pyzor:
status:	Unconfirmed → Needs Info

Revision history for this message

Rich Johnson (nixternal) wrote on 2007-05-28:

#4

argh! Sorry about that...well I used all of the pyzor flags successfully. Is there something I should try and do in order to duplicate this problem? Thank you for the report.

Revision history for this message

glenstewart (glen-stewart) wrote on 2007-05-28:

#5

What I've been seeing, is that I can trigger the pyzor crash simply by logging out of KDE, and coming back in again. I did it just now. But when I tried it a second time (since reboot), there was no reported crash.

I'm wondering two things: 1). is there some process that's hanging around until I log out, which gets killed, or 2). was there an original crash that is stuck in the crash handler's memory, and it just won't purge.

I use spamassassin and its reporting feature quite often. Maybe the hanging process is brought to life after a report. I'll try to keep an eye on it and update this bug report when I have more detail.

Revision history for this message

glenstewart (glen-stewart) wrote on 2007-05-31:

#6

pyzor.png Edit (88.4 KiB, image/png)

The problem remains - it appears to be pyzor's reporting mechanism that is crashing, but the process itself isn't in the process list. Attached is the latest bug report detail that seemed relevant.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2007-09-21:

#7

[Expired for pyzor (Ubuntu) because there has been no activity for 60 days.]

Revision history for this message

Scott Kitterman (kitterman) wrote on 2007-10-01:

#8

spamassassin (3.2.3-0ubuntu1) gutsy; urgency=low

  * New upstream release (LP: #147729)
    - Among other changes, correct pyzor processing (LP: #146217)
      (LP: #115853)

-- Scott Kitterman <email address hidden> Mon, 01 Oct 2007 12:20:15 -0400

Changed in spamassassin:
status:	New → Fix Released

Revision history for this message

david.bonnet84 (david-bonnet84) wrote on 2008-04-24:

#9

ubuntu hardy 8.04

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.