Re: /var/spool/qmailscan/tmp and /var/spool/qmailscan/working

Christian Lerrahn <[email protected]>
Newsgroups gmane.mail.qmail.scanner
Message-ID <20070922222411.2dfab8d9@localhost>
On Sat, 22 Sep 2007 10:31:27 +0200
Salvatore Toribio <[email protected]> wrote:

> At 17:09 +1000 22-09-2007, Christian Lerrahn wrote:
> >Hi,
> >I have the problem that on my server it has happened before that
> >because of an unfortunate setup /var ran out of space and the
> >qmail processes stopped. Now I have the impression that when I made
> >space and restarted the qmail services, some of the files
> >in /var/spool/qmailscan/tmp and /var/spool/qmailscan/working seemed
> >to not be processed any more and stayed there forever. I assume that
> >these are just copies of email in the queue and I could safely
> >delete them but before I end up losing plenty of email, I wanted to
> >make sure. Can I safely purge these 2 directories without risking
> >data loss? If not, is there a simple way of recovering emails that
> >are stuck in there?
> >
> 
> Hi
> 
> You should stop qmail and wait until all the active connections are 
> close properly, then you can safely remove purge those directories, 
> and restart qmail.

I did as told but see a lot of errors of the sort

X-Qmail-Scanner-1.25st:[mail119046351171828276] Unable to open pipe
to /var/qmail/bin/qmail-queue [65] (#4.3.0) -
X-Qmail-Scanner-1.25st:[mail119046351171828276] Unable to close pipe
to /var/qmail/bin/qmail-queue [65] (#4.3.0) - Illegal seek

now. Is this a result of me purging the directories? The strange thing
is that even if I undo it and these files are there and have correct
permissions, I still get the error message.

Cheers,
Christian

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.