Re: What is /var/qmail/queue/pid for?
Thus said Dave Sill on Wed, 03 Nov 1999 13:34:20 EST: > >... At any rate, it looks like things have calmed down on the list > >server and I am wondering if I should just delete all those pid files as > >I'm beginning to wonder if they are mistakes made by qmail-queue when it > >couldn't complete it's tasks due to permission problems. > > qmail-send will delete them after they're 36 hours old. Dave, I just looked and sure enough, they were gone. Thanks for all the help. My next project will be to make an RPM from scratch of this beast... I know there are already some out there but I would like to have a go at it myself. It looks like qmail is very machine specific and there are certain tricks to get it to where it is relocatable. Andy -- +== Andy == TiK: garbaglio ==+ |Linux is about freedom of choice| +== http://www.xmission.com/~bradipo/ ===+
Re: What is /var/qmail/queue/pid for?
Andy Bradford <[EMAIL PROTECTED]> wrote: >... At any rate, it looks like things have calmed down on the list >server and I am wondering if I should just delete all those pid files as >I'm beginning to wonder if they are mistakes made by qmail-queue when it >couldn't complete it's tasks due to permission problems. qmail-send will delete them after they're 36 hours old. -Dave
Re: What is /var/qmail/queue/pid for?
Thus said Dave Sill on Tue, 02 Nov 1999 13:45:20 EST: > The files under queue/pid are empty. qmail-queue moves them to > queue/mess before writing the message to the file. This is all > documented in INTERNALS in the build directory: Thanks for quoting that for me... I could have read that myself had I known where to look. :) Sometimes finding the documentation is the hardest pard... At any rate, it looks like things have calmed down on the list server and I am wondering if I should just delete all those pid files as I'm beginning to wonder if they are mistakes made by qmail-queue when it couldn't complete it's tasks due to permission problems. Andy -- +== Andy == TiK: garbaglio ==+ |Linux is about freedom of choice| +== http://www.xmission.com/~bradipo/ ===+
Re: What is /var/qmail/queue/pid for?
Andy Bradford <[EMAIL PROTECTED]> wrote: >I see, so even if trigger isn't there it will check the queue and send out >the mail therein. Which doesn't help if nothing is in the queue. Right on both counts. >... I do know that all the files in queue/pid are 0 byte files though. >Does this matter or are they simply a tracking mechanism? The files under queue/pid are empty. qmail-queue moves them to queue/mess before writing the message to the file. This is all documented in INTERNALS in the build directory: 3. How messages enter the queue To add a message to the queue, qmail-queue first creates a file in a separate directory, pid/, with a unique name. The filesystem assigns that file a unique inode number. qmail-queue looks at that number, say 457. By the guarantee above, message 457 must be in state S1. qmail-queue renames pid/whatever as mess/457, moving to S2. It writes the message to mess/457. It then creates intd/457, moving to S3, and writes the envelope information to intd/457. Finally qmail-queue creates a new link, todo/457, for intd/457, moving to S4. At that instant the message has been successfully queued, and qmail-queue leaves it for further handling by qmail-send. qmail-queue starts a 24-hour timer before touching any files, and commits suicide if the timer expires. -Dave
Re: What is /var/qmail/queue/pid for?
Thus said Dave Sill on Tue, 02 Nov 1999 13:32:55 EST: > >Hmm, well if it puts messages in there then it looks as if I have lost a > >lot of messages. Each file is 0 bytes in length and there are about 1 > >of them. Probably no way I can recover these... There were messages in > >/var/log/mail about qmail-queue not being able to write them. I wonder if > >it was unable to write them to queue/pid as well. At any rate, the problem > >was that the "trigger" pipe was not there. After I recreated that with > >mkfifo all seemed to return to normal. So, what is the purpose of the > >named pipe? > > I don't think that a missing trigger would cause your problems. > qmail-queue uses trigger to tell qmail-send that there's a new message > in the queue. If trigger is fubared, qmail-send doesn't see new > messages until it makes it's regular 20-minute rounds. I see, so even if trigger isn't there it will check the queue and send out the mail therein. Which doesn't help if nothing is in the queue. > Did you run qmail-lint, "make check", both, or neither? This is on a machine at work and so I haven't had the chance to check it yet. I do know that all the files in queue/pid are 0 byte files though. Does this matter or are they simply a tracking mechanism? Andy -- +== Andy == TiK: garbaglio ==+ |Linux is about freedom of choice| +== http://www.xmission.com/~bradipo/ ===+
Re: What is /var/qmail/queue/pid for?
Andy Bradford <[EMAIL PROTECTED]> wrote: >Thus said Dave Sill on Tue, 02 Nov 1999 10:23:11 EST: > >> qmail-queue puts messages in queue/pid before moving them to >> queue/mess. If messages are staying in queue/pid, they're not being >> queued successfully. You should be seeing error messages when >> qmail-queue is run, e.g., from qmail-inject. Try running Russ Nelson's >> qmail-lint and "make check" from the qmail build directory. > >Hmm, well if it puts messages in there then it looks as if I have lost a >lot of messages. Each file is 0 bytes in length and there are about 1 >of them. Probably no way I can recover these... There were messages in >/var/log/mail about qmail-queue not being able to write them. I wonder if >it was unable to write them to queue/pid as well. At any rate, the problem >was that the "trigger" pipe was not there. After I recreated that with >mkfifo all seemed to return to normal. So, what is the purpose of the >named pipe? I don't think that a missing trigger would cause your problems. qmail-queue uses trigger to tell qmail-send that there's a new message in the queue. If trigger is fubared, qmail-send doesn't see new messages until it makes it's regular 20-minute rounds. Did you run qmail-lint, "make check", both, or neither? -Dave
Re: What is /var/qmail/queue/pid for?
Thus said Dave Sill on Tue, 02 Nov 1999 10:23:11 EST: > qmail-queue puts messages in queue/pid before moving them to > queue/mess. If messages are staying in queue/pid, they're not being > queued successfully. You should be seeing error messages when > qmail-queue is run, e.g., from qmail-inject. Try running Russ Nelson's > qmail-lint and "make check" from the qmail build directory. Hmm, well if it puts messages in there then it looks as if I have lost a lot of messages. Each file is 0 bytes in length and there are about 1 of them. Probably no way I can recover these... There were messages in /var/log/mail about qmail-queue not being able to write them. I wonder if it was unable to write them to queue/pid as well. At any rate, the problem was that the "trigger" pipe was not there. After I recreated that with mkfifo all seemed to return to normal. So, what is the purpose of the named pipe? Andy -- +== Andy == TiK: garbaglio ==+ |Linux is about freedom of choice| +== http://www.xmission.com/~bradipo/ ===+
Re: What is /var/qmail/queue/pid for?
Andy Bradford <[EMAIL PROTECTED]> wrote: >I have a server that does not seem to want to send out any email. If I >start and stop the qmail daemons it will will send out bounced messages but >it doesn't send out any email that should be directed to mailing lists. >All the aliases are in place... There are hundreds of files in >/var/qmail/queue/pid and I think that they are related somehow... qmail-queue puts messages in queue/pid before moving them to queue/mess. If messages are staying in queue/pid, they're not being queued successfully. You should be seeing error messages when qmail-queue is run, e.g., from qmail-inject. Try running Russ Nelson's qmail-lint and "make check" from the qmail build directory. -Dave
