Your message dated Mon, 17 Mar 2008 00:17:14 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#305368: fixed in p3scan 2:2.3.2-1
has caused the Debian Bug report #305368,
regarding p3scan should clean up /var/spool/p3scan/children/ before starting up
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
305368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=305368
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: p3scan
Version: 2.1-2 (sarge)
Consider this sequence of events...
1. Linuxbox running p3scan crashes because of power failure.
2. Some files are left in /var/spool/p3scan/children/
3. Box reboots...
4. p3scan seems to work fine for a while
5. p3scan re-uses a pid which was left as a dirname in the spool dir
6. p3scan crashes unexpectedly because it seems it can't handle so an
unexpected event...
Some logs from this morning:
p3scan[1282]: Session done (Clean Exit). Mails: 0 Bytes: 0
p3scan[1283]: Connection from 192.168.xx.244:2021
p3scan[1283]: Real-server adress is xx.84.240.98:110
p3scan[1283]: USER 'xxxxxxx'
p3scan[1283]: Session done (Clean Exit). Mails: 0 Bytes: 0
p3scan[1294]: Connection from 192.168.xx.248:49294
p3scan[1294]: Real-server adress is xx.46.243.2:110
p3scan[1295]: Connection from 192.168.xx.248:49295
p3scan[1295]: Real-server adress is xx.46.243.2:110
p3scan[1296]: Connection from 192.168.xx.248:49296
p3scan[1296]: Real-server adress is xx.247.60.79:110
p3scan[1297]: Connection from 192.168.xx.248:49297
p3scan[1297]: Real-server adress is xx.239.177.240:110
p3scan[1298]: Connection from 192.168.xx.248:49298
p3scan[1298]: Real-server adress is xx.46.243.2:110
p3scan[1294]: USER 'xxxxxx3'
p3scan[1295]: USER 'xxxxxx3'
p3scan[1296]: USER '[EMAIL PROTECTED]'
p3scan[1296]: Session done (Clean Exit). Mails: 0 Bytes: 0
p3scan[1297]: USER '[EMAIL PROTECTED]'
p3scan[1298]: USER 'xxxxxx3'
p3scan[1299]: File Error! Could not erase
/var/spool/p3scan/children/1299/p3scan.SB49fU.dir
p3scan[1299]: Exiting now...
p3scan[896]: File Error! Could not erase
/var/spool/p3scan/children/1299/p3scan.SB49fU.dir
p3scan[896]: Exiting now...
p3scan[1295]: Session done (Clean Exit). Mails: 0 Bytes: 0
p3scan[1298]: Session done (Clean Exit). Mails: 0 Bytes: 0
p3scan[1294]: Session done (Clean Exit). Mails: 0 Bytes: 0
p3scan[1297]: Session done (Clean Exit). Mails: 0 Bytes: 0
Now all p3scan processes are gone, and the users in the office behind
this mailgateway start complaining they can't read mail... :)
Looking in /var/spool/p3scan/children shows there are some directories
left from earlier p3scan processes. The 19-04 11:08 are left after the
p3scan crash which the above logs show. The others are older and those
with drwx------ are from before p3scan 2.1-1.
vuurkorf.2 /var/spool/p3scan/children# ll
total 7
drwxr-x--- 2 p3scan p3scan 48 Apr 19 11:08 1294 <- crash
drwxr-x--- 2 p3scan p3scan 48 Apr 19 11:08 1295 this
drwxr-x--- 2 p3scan p3scan 48 Apr 19 11:09 1297 morning
drwxr-x--- 2 p3scan p3scan 48 Apr 19 11:09 1298
drwx------ 3 p3scan p3scan 88 Feb 3 19:10 1299 <- clash [EMAIL PROTECTED]@
drwx------ 2 p3scan p3scan 80 Oct 6 2004 18503
drwxr-x--- 2 p3scan p3scan 48 Apr 19 17:40 2661 <- running
drwxr-x--- 2 p3scan p3scan 48 Apr 19 17:40 2662 now!
drwxr-x--- 2 p3scan p3scan 48 Apr 19 17:40 2663
drwxr-x--- 2 p3scan p3scan 48 Apr 19 17:40 2664
drwx------ 2 p3scan p3scan 80 Oct 26 19:20 310 <- old ones
drwx------ 2 p3scan p3scan 80 Oct 26 19:21 311
drwx------ 2 p3scan p3scan 80 Sep 14 2004 945
drwx------ 2 p3scan p3scan 80 Sep 14 2004 969
I guess they're left there because of power failure. (sigh) This box
only runs iptables, p3scan and postfix, and the above shows clearly
there was a p3scan process with pid 1299, which clashed with a new
p3scan with pid 1299.
p3scan should clean up files in the spool dir when starting up, because
they have no meaning anymore at that time, and on busy p3scan boxes,
these clashes because of pid-reuse will happen.
For today: I stopped p3scan, rm-rf-ed the contents of
/var/spool/p3scan/children/, and started p3scan again.
Hans van Kranenburg
The Netherlands
--- End Message ---
--- Begin Message ---
Source: p3scan
Source-Version: 2:2.3.2-1
We believe that the bug you reported is fixed in the latest version of
p3scan, which is due to be installed in the Debian FTP archive:
p3scan_2.3.2-1.diff.gz
to pool/main/p/p3scan/p3scan_2.3.2-1.diff.gz
p3scan_2.3.2-1.dsc
to pool/main/p/p3scan/p3scan_2.3.2-1.dsc
p3scan_2.3.2-1_i386.deb
to pool/main/p/p3scan/p3scan_2.3.2-1_i386.deb
p3scan_2.3.2.orig.tar.gz
to pool/main/p/p3scan/p3scan_2.3.2.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mats Rynge <[EMAIL PROTECTED]> (supplier of updated p3scan package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 11 Mar 2008 20:43:20 -0600
Source: p3scan
Binary: p3scan
Architecture: source i386
Version: 2:2.3.2-1
Distribution: unstable
Urgency: low
Maintainer: Mats Rynge <[EMAIL PROTECTED]>
Changed-By: Mats Rynge <[EMAIL PROTECTED]>
Description:
p3scan - transparent POP3-proxy with virus- and spam-scanning
Closes: 305368 333628 355340 363313 390247 469763
Changes:
p3scan (2:2.3.2-1) unstable; urgency=low
.
* New upstream release (closes: #355340)
* Added LSB info to init.d script (closes: #469763)
* Changed logic in init.d script to allow for checking if the daemon is
already running.
* /var/spool/p3scan/children is now cleaned on startup (closes: #305368)
* PID file is now cleaned up correctly on initial failures (closes: #333628))
* Fixed clamdscan information in README.Debian (closes: #363313)
* Update copyright file to include OpenSSL exception
* Added new dependency: libssl-dev
* Updated standards version to 3.7.3
* Fixed chown syntax in postinst
* Fixed spelling mistake in package description (closes: #390247)
Files:
cead2ed8312fe0fc1a39e75bfe01c3e8 579 mail optional p3scan_2.3.2-1.dsc
9f8decc7d4701228788e3c8717096ca0 321684 mail optional p3scan_2.3.2.orig.tar.gz
537d3020e012e640c2c1a6a3a4765b10 8272 mail optional p3scan_2.3.2-1.diff.gz
3cba018fb77a1602b89faa33c8f52235 181198 mail optional p3scan_2.3.2-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH3bXk9cFp3aBpFaMRAl7CAJ9CtkNl6kANMjPvEF/qTGYVDUHleQCggJKq
ifw5WVjVHaHKJqhbCvr4JIQ=
=sKun
-----END PGP SIGNATURE-----
--- End Message ---
