• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2482
  • Last Modified:

Qmail - qmail-inject: fatal: qq trouble creating files in queue

I've been able to get qmail to start, after seeing multiple errors like "/var/qmail/bin/qmail-smtpd: access denied"

Now I'm getting these errors:

"Nov 21 08:29:59 websmtp01 qmail: 1195662599.309783 alert: unable to opendir info            /0, sleeping..."

and when I try to send a test message

"qmail-inject: fatal: qq trouble creating files in queue"

Any ideas if something happened to the permissions?
0
JWeb Admin
Asked:
JWeb Admin
  • 4
  • 2
1 Solution
 
JWeb AdminAuthor Commented:
Maybe this helps as well, I installed qmHandle, and when trying to force send the messages, it says:

"websmtp01# /usr/local/bin/qmHandle -a
Qmail isn't running, can't send messages!"

Is another process binding to the smtp port?  This is what I get when I do a ps aux  grep qmail:

root     573  0.0  0.0   352   220  p0  R+   10:04AM   0:00.00 grep qmail
qmaild   470  0.0  0.1  1220   612 con- I     9:57AM   0:00.00 /usr/local/bin/t
qmails   472  0.0  0.1  1276   712 con- I     9:57AM   0:00.01 qmail-send
qmaill   479  0.0  0.1  1216   692 con- I     9:57AM   0:00.00 splogger qmail
root     480  0.0  0.1  1232   624 con- I     9:57AM   0:00.00 qmail-lspawn ./M
qmailr   481  0.0  0.1  1228   620 con- I     9:57AM   0:00.00 qmail-rspawn
qmailq   482  0.0  0.1  1212   656 con- I     9:57AM   0:00.00 qmail-clean
0
 
nagehmaiCommented:
Your queue ownership should look like:
/var/qmail/queue        owned by qmailq:qmail

Inside the /var/qmail/queue the following directories should be owned by qmails:qmail:
bounce  info local remote

These ones should be owned by qmailq:qmail:
intd lock mess pid todo

All the numbered queue directories within these should have the same ownership as their parents.
If you figure your perms on all the individual queue files are fubar, I recommend downloading and running the Python script queue-repair which can be found here: http://pyropus.ca/software/queue-repair/ 
It will rip through your queue directory and fix any busted perms and ownership.
0
 
JWeb AdminAuthor Commented:
What about the error I'm getting that says qmail isnt' running?  Are all the services that need to be active, active?
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
JWeb AdminAuthor Commented:
All of those folders are owned properly.
0
 
nagehmaiCommented:
Can you make sure your suid bit is set on /var/qmail/bin/qmail-queue  ( or /var/qmail/bin/qmail-scanner-queue.pl if you're using that).

Perms on these files should look like:
-rws--x--x  qmailq qmail    qmail-queue

or

-rwsr-xr-x qscand qscand   qmail-scanner-queue.pl
0
 
JWeb AdminAuthor Commented:
Yes they are all correct - I'm going to rebuild this machine and install a different OS with a newer install of Qmail - thanks for your help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now