Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i just try to install netqmail-1.0.5 on my experimental mail server, following the instruction from life with qmail website. i followed every step carefully and everything was ok until i started running qmail, and the readproctitle service error said :
"...multilog: fatal: unable to open directory /var/log/qmail: access denied?multilog: fatal: unable to open directory /var/log/qmail/smtpd: access denied?multilog: fatal: unable to open directory /var/log/qmail: access denied?multilog:..."
i checked with inst_check tool available from lwq and everything's fine.
The directories /var/log/qmail and /var/log/qmail/smtpd both have 755 permission and qmaill.root as the owner. when i ran qmailctl stat, the result was :
/service/qmail-send: up (pid 6766) 1964 seconds
/service/qmail-send/log: up (pid 10719) 0 seconds
/service/qmail-smtpd: up (pid 6768) 1964 seconds
/service/qmail-smtpd/log: up (pid 10718) 0 seconds
messages in queue: 0
messages in queue but not yet preprocessed: 0
running the service from the directory directly (eg. "run" from /service/qmail-smtpd/log) will yield similar result :
multilog: fatal: unable to open directory /var/log/qmail/smtpd: access denied
i've tried to find the answer for hours but couldn't find anything helpful. does anybody have experience with this kind of problem ? tia
1) Run the commands ps -ef and post the output here for us to see. This will show us what qmail processes are running and if they look correct.
2) Now run...
svc -d /service/*
svc -d /service/*/log
and then run ps -ef and post the output here for us to see. This will show us what is left running after qmail is stopped. You shoudl not see any qmail processes running in the output. if you do, then we really need to see what *IS* running.
3) Now run...
svc -u /service/*
svc -u /service/*/log
To start your qmail up again.
4) Now run /var/qmail/bin/qmail-showctl and post the output here for us to see. It's going to be a lot of info. That's OK. Just be sure to include everything and please try to avoid censoring the output. You won't be opening up any security holes by showing us this information. This will show us how you've got qmail configured and if you might have missed anything.
5) Now post the contents of your qmail-smtpd/run scritps here. This will show us if you've got all the commands written out correctly in this file.
This may seem like a lot of information to post, but it will save time because these are the common things to look for when this kind of problem happens.
* output of qmail-showctl command :
qmail home directory: /var/qmail.
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 120.
subdirectory split: 23.
user ids: 7790, 7791, 7792, 0, 7793, 7794, 7795, 7796.
group ids: 2108, 2107.
badmailfrom: (Default.) Any MAIL FROM is allowed.
bouncefrom: (Default.) Bounce user name is MAILER-DAEMON.
bouncehost: (Default.) Bounce host name is kingsford.local.
concurrencylocal: (Default.) Local concurrency is 10.
concurrencyremote: (Default.) Remote concurrency is 20.
databytes: (Default.) SMTP DATA limit is 0 bytes.
defaultdomain: Default domain name is kingsford.local.
defaulthost: (Default.) Default host name is kingsford.local.
doublebouncehost: (Default.) 2B recipient host: kingsford.local.
doublebounceto: (Default.) 2B recipient user: postmaster.
envnoathost: (Default.) Presumed domain name is kingsford.local.
helohost: (Default.) SMTP client HELO host name is kingsford.local.
idhost: (Default.) Message-ID host name is kingsford.local.
localiphost: (Default.) Local IP address becomes kingsford.local.
locals: Messages for kingsford.local are delivered locally.
me: My name is kingsford.local.
percenthack: (Default.) The percent hack is not allowed.
plusdomain: Plus domain name is kingsford.local.
qmqpservers: (Default.) No QMQP servers.
queuelifetime: (Default.) Message lifetime in the queue is 604800 seconds.
rcpthosts: SMTP clients may send messages to recipients at kingsford.local.
morercpthosts: (Default.) No effect.
morercpthosts.cdb: (Default.) No effect.
smtpgreeting: (Default.) SMTP greeting: 220 kingsford.local.
smtproutes: (Default.) No artificial SMTP routes.
timeoutconnect: (Default.) SMTP client connection timeout is 60 seconds.
timeoutremote: (Default.) SMTP client data timeout is 1200 seconds.
timeoutsmtpd: (Default.) SMTP server data timeout is 1200 seconds.
virtualdomains: (Default.) No virtual domains.
defaultdelivery: I have no idea what this file does.
concurrencyincoming: I have no idea what this file does.
* and lastly, content of /var/qmail/supervise/qmail-smtpd/run :
You may also want to check the permissions on those directories. The run files should be chmod 755 and owned by root.
You'll notice in the first set of ps output, there are 2 defunct processes showing up. These are your logging processes that aren't working. This is evident by your qmailctl stat command that shows the logging processes are up for only zero seconds. But in the second set of ps output, the defunct processes are being stopped, which is good. But I'm curious... do the defunct processes show up again when you start qmail again?