You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2010/03/01 17:57:30 UTC
[Bug 6351] Pyzor plugin fails with "check failed: no response" even
though pyzor seems to work okay
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6351
erik@logtenberg.eu changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |erik@logtenberg.eu
--- Comment #1 from erik@logtenberg.eu 2010-03-01 16:57:28 UTC ---
Additional information:
I strace'd spamc using -f to follow the pyzor-fork. In the trace I see SA
opening a temporary file in /tmp and writing the mail to it, then starting
pyzor and feeding it the tempfile. Pyzor starts fine, reads its configuration
file(s) (especially the servers file, which in my case is the only relevant
configuration file), and then starts reading the tempfile.
Very shortly after finishing reading the tempfile, pyzor quits, and SA reports
the "exit 1" status. I can't figure out by looking at the strace what went
wrong, but maybe someone else has a clue. This is the strace, starting with the
final "read", which is Pyzor reading the tempfile, and ending with the "write"
where SA echo's the debug message:
[pid 29868] read(0, "AADrDAAA7AwAAO0MAADuDAAA7wwA\nAPA"..., 4096) = 4096
[pid 29868] read(0, "AAOEPAADiDwAA\n4w8AAOQPAADlDwAA5g"..., 4096) = 3682
[pid 29868] close(4) = 0
[pid 29868] munmap(0x7f2adb25b000, 4096) = 0
[pid 29868] close(3) = 0
[pid 29868] rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x3003e0f0f0},
{0x300570b2b0, [], SA_RESTORER, 0x3003e0f0f0}, 8) = 0
[pid 29868] rt_sigaction(SIGALRM, {SIG_DFL, [], SA_RESTORER, 0x3003e0f0f0},
{0x300570b2b0, [], SA_RESTORER, 0x3003e0f0f0}, 8) = 0
[pid 29868] exit_group(1) = ?
Process 29868 detached
[pid 29867] <... read resumed> "", 4096) = 0
[pid 29867] close(5) = 0
[pid 29867] rt_sigaction(SIGHUP, {SIG_IGN, [], SA_RESTORER, 0x3003e0f0f0},
{0x7f36e599be80, [], SA_RESTORER, 0x3003e0f0f0}, 8) = 0
[pid 29867] rt_sigaction(SIGINT, {SIG_IGN, [], SA_RESTORER, 0x3003e0f0f0},
{0x7f36e599be80, [], SA_RESTORER, 0x3003e0f0f0}, 8) = 0
[pid 29867] rt_sigaction(SIGQUIT, {SIG_IGN, [], SA_RESTORER, 0x3003e0f0f0},
{SIG_DFL, [], 0}, 8) = 0
[pid 29867] wait4(29868, [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], 0, NULL) =
29868
[pid 29867] --- SIGCHLD (Child exited) @ 0 (0) ---
[pid 29867] rt_sigaction(SIGHUP, {0x7f36e599be80, [], SA_RESTORER,
0x3003e0f0f0}, NULL, 8) = 0
[pid 29867] rt_sigaction(SIGINT, {0x7f36e599be80, [], SA_RESTORER,
0x3003e0f0f0}, NULL, 8) = 0
[pid 29867] rt_sigaction(SIGQUIT, {SIG_DFL, [], SA_RESTORER, 0x3003e0f0f0},
NULL, 8) = 0
[pid 29867] gettimeofday({1267461624, 844985}, NULL) = 0
[pid 29867] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2917, ...}) =
0
[pid 29867] gettimeofday({1267461624, 845364}, NULL) = 0
[pid 29867] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2917, ...}) =
0
[pid 29867] stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2917, ...}) =
0
[pid 29867] write(2, "mrt 1 17:40:24.845 [29867] dbg:"..., 65mrt 1
17:40:24.845 [29867] dbg: pyzor: [29868] finished: exit 1
Please note that 29867 is SA and 29868 is pyzor.
It seems that pyzor hasn't even contacted the server yet, apparently something
went wrong before that. However I don't know what - as I said in my previous
post: when I start pyzor manually with the same arguments and using the same
user id, it works fine.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.