Qmail-lspawn stops

[Aziraphel]

Hello all

I have installed qmail 1.03 on a Mac OS X.2.8.

I have no HFS+ partition so I set the concurrencylocal to 1 to avoid locks.

Since I installed the latest security update from Apple, I have a problem. the qmail-lspawn owned by the root is ok but the child owned by a user sometimes simply stops.

A ps -aux reads it int the 'U' state.

My question on this forum (for I have many questions! ) is how can a qmail-lspawn be blocked? Is there a lock I can control/touch/delete so that he goes on his work?
If not, is there a way to kill him? I tried from the kill -HUP to the kill -TERM, but no effect...

Is this problem caused by the lack of HFS+?

If anybody has an answer, it would be great.

Aziraphel

 

[thedaver]

I can't speak to MAC OS anything, but I think it might be incorrect that qmail-* is owned by 'root'. Generally DJB has avoided having 'root' own much of anything in qmail except for good reason. Check your install guide.

Hosting Solutions for Home or Business.

http://www.surfinbox.com/hosting/

 

[Aziraphel]

I checked this but it's correct. I followed the LWQ web site to install Qmail and it reads that usually the qmail-lspawn is running as user root.

If it can help, I used qmail-remove to remove a blocked message from the queue and it appeared that it makes the qmail-lspawn process end.

By the way, is there any way to make qmail-lspawn more verbose in the log?

 

[thedaver]

You should go find the queuerepair utility - not part of DJB's suite I don't believe. My suspicion is that your queue is mangled in some small way.

No idea about the logging

Hosting Solutions for Home or Business.

http://www.surfinbox.com/hosting/

 

[Aziraphel]

Thanks for the idea, alas I already tried the queue-fix utility, with no result.
Anyway, I'll purge the queue, move it and create a new one as soon as I can. Maybe queue-fix can't detect a problem and to create a new queue can solve it...

 

[Aziraphel]

I moved the queue and created a new one with queue-fix but it didn't sort out the problem.

Actually, I think the problem isn't with qmail-lspawn but rather with qmail-local which I suspect not to say its father its job is done, so that lspawn just wait and nothing can wake it up.

I'll inverstigate in this way. I'm afraid to have to read sources and there's a lot of time I didn't read C...

If someone has another idea before I go on my live with aspirin and C bible, (s)he'll be my savior!

 

[thedaver]

qmail-local definitely requires GUI/UID to be specific. Also, you may find that an error in a .qmail-default script can contaminate your processing. It sounds like you've got data being stuck in a black hole and not making it to the next pipe.

Internet Directory

http://dir.surfinbox.com/dir.php/Top

 

[Aziraphel]

About GUI/UID, I never paid attention to the readproctitle but there's an error "setuidgid: qmaill unknown account".
I know this error was here before, but as all was right, I never had a look at this.

I tested the setuidgid command with several accounts ('root', admin account, user account, 'nobody') and the only error I produce is "unable to setgid: permission denied"
A 'cat /etc/passwd | grep qmaill' command reads that qmaill user exists. qmaill also exists in NetInfo (Mac specific).

If this could be solve, maybe would I have more infos in log??

Anyway, I gave a look to the different .qmail files, everything seems right.

Stranger, the blocked mails are all mails with several recipient. There is no blocked mail with only one recipient.
I have a '.qmail-personnel' alias to mail to everyone in the office, each mail sent to this adress blocks. I have a lot of qmail-lspawn waiting and the mail is delivered to several but not all recipients.

Maybe a lock on the message file? I tried to 'touch' it with no effect...

 

[thedaver]

I think you should review the installation steps for qmail from here and make sure that every perm, user, and chown are set per these specs...

http://www.pipeline.com.au/staff/mbowe/isp/webmail-server.htm#QMAIL

Also, what is the content of the .qmail-personnel? It should begin with a pipe "|" character.



Internet Directory

http://dir.surfinbox.com/dir.php/Top

 

[Aziraphel]

I'll check this website.

About the .qmail-personnel, it doesn't begin with a pipe character, it is just a list of the persons with an ampersand to ask for a redirection. So this file is just something like :
&user1
&user2
...
&usern

 

[thedaver]

That's allowed too!

Internet Directory

http://dir.surfinbox.com/dir.php/Top