Can't start qmail daemons
I am trying to set up qmail as my MTA. In order to test it I am running the command: sh -cf '/var/qmail/rc ' The contents of the rc script are as follows: #!/bin/sh exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start ./Mailbox splogger qmail when I do a ps -aux, none of the 4 qmail daemons that should be running have been started and I get the following message in /var/log/mail: Dec 2 10:57:41 hwlab qmail: 956930303.302345 alert: cannot start: qmail-send is already running What is happening here? Why does it think that qmail-send (qmails daemon) is already running? Any suggestions as to how I can fix this would be appreciated. Paul
RE: Can't start qmail daemons
I tried ps -axww | grep qmail without luck. Something is happening however since when I try: echo to: paul | /var/qmail/bin/qmail-inject syslog shows the message as successfully delivered. However the user paul does not receive the mail (paul owns his home directory and it is not group or world writeable). My OS is Caldera linux (2.0.35). Paul -Original Message- From: Vince Vielhaber [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 02, 1999 12:04 PM To: Paul Charsley Cc: [EMAIL PROTECTED] Subject: RE: Can't start qmail daemons On 01-Dec-99 Paul Charsley wrote: I am trying to set up qmail as my MTA. In order to test it I am running the command: sh -cf '/var/qmail/rc ' The contents of the rc script are as follows: #!/bin/sh exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start ./Mailbox splogger qmail when I do a ps -aux, none of the 4 qmail daemons that should be running have been started and I get the following message in /var/log/mail: Dec 2 10:57:41 hwlab qmail: 956930303.302345 alert: cannot start: qmail-send is already running What is happening here? Why does it think that qmail-send (qmails daemon) is already running? Any suggestions as to how I can fix this would be appreciated. Try ps -axww | grep qmail and see if you see it. Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h Have you seen http://www.pop4.net? Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com ==
Can't start: unable to read controls { was: Re: deffered delivery instead of bouncing it back}
Thanks for the comments but the directory is world readable. With root as owner of the same. Could permissions be the problem? Should it be root: qmail? I have root:root for all the files under controls. - Original Message - From: Russell Nelson [EMAIL PROTECTED] To: Medha Sabharwal [EMAIL PROTECTED] Cc: qmail mailing list [EMAIL PROTECTED] Sent: Sunday, November 14, 1999 11:00 PM Subject: Re: deffered delivery instead of bouncing it back Medha Sabharwal writes: I did my first installation of qmail today. The installation went through like a charm and I can now send mails locally. I was doing the tests as per TEST.deliver and was testing a bounce back mail. Because of no aliases a bounced mailed went into deffered mode. I updated the aliases file for root, postmaster and mailer-daemon. Now I have a problem. My qmail won't start. Check the permissions on /var/qmail/control/*. They should be world-readable. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | Government schools are so 521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
Re: Can't start: unable to read controls { was: Re: deffered delivery instead of bouncing it back}
The program instcheck is reporting permission errors on /var/qmail/alias.
The permission right now is 644. Any clues as to what should be the exact
permissions? Also is there a place which tells you the permissions of the
files and directories. I see different ownership*some for root and some for
qmail* under the bin directory.
Thanks for all the help.
- Original Message -
From: Medha Sabharwal [EMAIL PROTECTED]
To: qmail mailing list [EMAIL PROTECTED]
Sent: Sunday, November 14, 1999 10:16 PM
Subject: Can't start: unable to read controls { was: Re: deffered delivery
instead of bouncing it back}
Thanks for the comments but the directory is world readable. With root as
owner of the same. Could permissions be the problem? Should it be root:
qmail? I have root:root for all the files under controls.
- Original Message -
From: Russell Nelson [EMAIL PROTECTED]
To: Medha Sabharwal [EMAIL PROTECTED]
Cc: qmail mailing list [EMAIL PROTECTED]
Sent: Sunday, November 14, 1999 11:00 PM
Subject: Re: deffered delivery instead of bouncing it back
Medha Sabharwal writes:
I did my first installation of qmail today. The installation went
through
like a charm and I can now send mails locally. I was doing the tests
as
per
TEST.deliver and was testing a bounce back mail. Because of no
aliases
a
bounced mailed went into deffered mode. I updated the aliases file
for
root,
postmaster and mailer-daemon. Now I have a problem. My qmail won't
start.
Check the permissions on /var/qmail/control/*. They should be
world-readable.
--
-russ nelson [EMAIL PROTECTED] http://russnelson.com
Crynwr sells support for free software | PGPok | Government schools are
so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank
amateur
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them.
Homeschool!
Re: can't start
At 10:24 PM 9/5/99 Jim Lippard wrote: Try "setuidgid", not "setguid". Ok.. that worked, but it opened up a whole host of other errors.. so back to work I go. james
Re: can't start
At 07:09 AM 9/6/99 magnus wrote: I would try to install daemontools, as the HOWTO, and lwq advises. The daemontools package includes setuser or setguid, depending on version of daemontools. I have already installed daemontools, and checked it with: date | ./tai64n | ./tai64nlocal date | sh -c './multilog t e 21' | ./tai64nlocal and my output was: 1999-09-05 22:23:21.323922500 Sun Sep 5 22:23:21 PDT 1999 1999-09-05 22:26:13.056125500 Sun Sep 5 22:26:13 PDT 1999 I notice that in my /usr/local/bin directory, I don't see setguid, but I do see a setuidgid. Should there be a setguid in that directory? james
Re: can't start
Try "setuidgid", not "setguid". Jim Lippard [EMAIL PROTECTED] http://www.discord.org/ Unsolicited bulk email charge: $500/message. Don't send me any. PGP Fingerprint: 0C1F FE18 D311 1792 5EA8 43C8 7AD2 B485 DE75 841C On Mon, 6 Sep 1999, Magnus Bodin wrote: On Sun, 5 Sep 1999, James wrote: In the life with qmail, his qmail script also has "setuser".. if I replace all setuser's with "setguid" will this fix my problem? Well, that didn't fix it.. I get this error now: ./qmail: setguid: command not found Is there anything else I can try? I would try to install daemontools, as the HOWTO, and lwq advises. The daemontools package includes setuser or setguid, depending on version of daemontools. http://pobox.com/~djb/daemontools.html -- magnus -- MOST useless 1998 * http://x42.com/
Re: can't start
On Sun, Sep 05, 1999 at 10:27:03PM +0100, James wrote: At 07:09 AM 9/6/99 magnus wrote: I would try to install daemontools, as the HOWTO, and lwq advises. The daemontools package includes setuser or setguid, depending on version of daemontools. I have already installed daemontools, and checked it with: [...] I notice that in my /usr/local/bin directory, I don't see setguid, but I do see a setuidgid. Should there be a setguid in that directory? Sorry. I should have written setuidgid. Either download the OLD version of daemontools and use the instructions in HOWTO and/or life with qmail, or "reread" the documentation with the changes mentioned here in mind: http://qmail.x42.com/koobera/www/daemontools/upgrade.html (my qmail.org-mirror, couldn't get hold of djb:s site at the time) -- magnus -- MOST useless 1998 * http://x42.com/
Re: can't start
In the life with qmail, his qmail script also has "setuser".. if I replace all setuser's with "setguid" will this fix my problem? Well, that didn't fix it.. I get this error now: ./qmail: setguid: command not found Is there anything else I can try? james
Re: can't start
On Sun, 5 Sep 1999, James wrote: In the life with qmail, his qmail script also has "setuser".. if I replace all setuser's with "setguid" will this fix my problem? Well, that didn't fix it.. I get this error now: ./qmail: setguid: command not found Is there anything else I can try? I would try to install daemontools, as the HOWTO, and lwq advises. The daemontools package includes setuser or setguid, depending on version of daemontools. http://pobox.com/~djb/daemontools.html -- magnus -- MOST useless 1998 * http://x42.com/
Re: can't start
At 09:14 PM 9/5/99 Pat wrote: Well, it looks like you got daemontool 6 where setuser was replaced with setguid and other oddities. I got bitten by that as well. As has been mentioned a couple of times, most of the HOWTOs haven't caught up to the newest daemontools. You might want to consult the nifty Life with Qmail and see if that helps out any: http://web.infoave.net/~dsill/lwq.html In the life with qmail, his qmail script also has "setuser".. if I replace all setuser's with "setguid" will this fix my problem? I went to the correct directory this time to start qmail, and it tried to start, but it hit the line in the script "setuser" and quit. I'll go and change all the "setuser" text I can find. james
Re: can't start
James had the thought that... Now, after having gone through the installation steps, qmail was running on my system, until I rebooted. I thought I had placed the proper script in the proper startup file, but I guess I haven't. But for starters, I don't know how to even START qmail manually. I tried going into the qmail install directory and typed: qmail start Well, if you did indeed put the startup scripts in the right place you would want to do this: /etc/rc.d/init.d/qmail start (at least on redhat systems) but I got this error: bash: qmail: command not found Which would make sense if you were in /usr/local/src/qmail or whatever since the startup scripts don't live there. So then I went to the /var/qmail/bin directory, but got the same error. How do I get qmail to start again? It was running before I rebooted. I'll also mention that I couldn't get the step for rblsmtpd (http://www.flounder.net/qmail/qmail-howto.html#10b) to work.. the "setuser" was a command that my system didn't understand. Could this cause a problem? Well, it looks like you got daemontool 6 where setuser was replaced with setguid and other oddities. I got bitten by that as well. As has been mentioned a couple of times, most of the HOWTOs haven't caught up to the newest daemontools. You might want to consult the nifty Life with Qmail and see if that helps out any: http://web.infoave.net/~dsill/lwq.html Pat -- Patrick Berry --- Code Creation --- Freestyle Interactive --- 415.778.0610 http://www.freestyleinteractive.com
can't start
I'm using Red Hat Mandrake 6.0, and I've gone through the Adam McKenna steps (http://www.flounder.net/qmail/qmail-howto.html) for installing qmail. Before this qmail installation, I was able to use sendmail just fine, except I had problems getting the virtual email setup to work, so I've decided to use qmail. Now, after having gone through the installation steps, qmail was running on my system, until I rebooted. I thought I had placed the proper script in the proper startup file, but I guess I haven't. But for starters, I don't know how to even START qmail manually. I tried going into the qmail install directory and typed: qmail start but I got this error: bash: qmail: command not found So then I went to the /var/qmail/bin directory, but got the same error. How do I get qmail to start again? It was running before I rebooted. I'll also mention that I couldn't get the step for rblsmtpd (http://www.flounder.net/qmail/qmail-howto.html#10b) to work.. the "setuser" was a command that my system didn't understand. Could this cause a problem? Thanks for any help. james
Re: can't start
Ok.. now I have tried to clean up as much as possible, and I have to issue this command to start qmail: ./qmail start and when I do, I get this: Starting qmail: qmail-sendsupervise: usage: supervise dir qmail-smtpdsupervise: usage: supervise dir . Does this mean I am getting a supervise error or something? Or are things sort of working ok? james
