On Tue, Jul 31, 2001 at 03:22:42PM +, [EMAIL PROTECTED] wrote:
>
> Hi!!!
>
> I've been running my Qmail server for 7 months now, without any problems what so
>ever!!
>
Glad to hear it.
> But yesterday it stopped sending any outgouing mail. Incoming still works fine
>
> I tried a rest
I think i know what is wrong...
here is the output of svstat /service/*:
(i ran this as an unpriveleged user)
=
svstat /service/*
/service/log: unable to open supervise/ok: access denied
/service/qmail-pop3d: unable to open supervise/ok: access denied
/service/qmail-send: una
On Sun, Jul 15, 2001 at 04:47:00PM -0500, David Dahl wrote:
> This is in /var/log/messages and syslog
> [...]
> i'm not sure what all of this means...
That looks like a report from Mandrake's security manager (I assume that's
what you're running on that box).
Check the output of:
svstat
At 16:47 15.07.2001 -0500, David Dahl wrote:
>This is in /var/log/messages and syslog
>
>Jul 13 04:01:19 mckenna : Security Warning: There is modifications for
>port listening on your machine :
>Jul 13 04:01:19 mckenna : - Opened ports : tcp0 0
>*:ndmp *:*
This is in /var/log/messages and syslog
Jul 13 04:01:19 mckenna : Security Warning: There is modifications
for port listening on your machine :
Jul 13 04:01:19 mckenna : - Opened ports : tcp0 0
*:ndmp *:* LISTEN 26231/perl
Jul 13 04:01:19
yes, it is
check your logs, probably a process controlled by supervise isn't running
properly.. Iv'e got the problem, that supervise write's it's error
messages only to tty1. try to run svscan from commandline without
backgrounding it, and check the output
At 14:35 15.07.2001 -0500, David Dah
Godamnit. I hate replying to myself. I had checked the logs... but only
briefly I guess, or the process was happy for a bit? I dunno. But when I
looked at them again later (AFTER sending pointless mail to the list of
course), qmail-send's log was going nuts. Turns out I failed to properly
kill qma
On Wed, Mar 21, 2001 at 03:22:32PM -, Iain Morrison wrote:
> The logging for Qmail is set to use multilog for both qmail-smtp and the
> qmail-send programs. Only trouble is that supervise is not able to start
> them for some reason so all logging goes to the console.
[snip...]
> Any ideas?
Uwe Ohse writes:
> On Wed, Feb 07, 2001 at 11:57:34AM -0500, Peter Brezny wrote:
>
> > I'd like to run supervise, but i would prefer the logging still take place
> > in /var/log/maillog.
>
> you are mistaken.
Nonsense. Of course he prefers that the logging still take place in
/var/log/m
On Wed, Feb 07, 2001 at 11:57:34AM -0500, Peter Brezny wrote:
> I'd like to run supervise, but i would prefer the logging still take place
> in /var/log/maillog.
you are mistaken.
> For example, could i just leave my /var/qmail/rc file as is and omit the
> portions regarding multilog in the
Dennis <[EMAIL PROTECTED]> wrote:
> Anyone know why I might be getting this error ?
>
> supervise: fatal: unable to acquire qmail-smtpd/supervise/lock: temporary
> failure
> supervise: fatal: unable to acquire log/supervise/lock: temporary failure
This normally means you've already got another s
Just go into the affected Directories and delete those lock Files manually.
Because UFS Solaris is a bit laggy in I/O this Problem occurs when you
stop and start your qmail Programs too fast!
--
Michael Maier / http://www.shell-provider.net
Fish Flowers wrote:
> I've gotten qmail to compile, and
, December 29, 2000 8:15
AMTo: Tim HunterCc: QmailSubject: RE:
supervise
Here's the error
messages I'm getting.
supervise: fatal:
unable to acquire qmail-send/supervise/lock: temporary failuresupervise:
fatal: unable to acquire log/supervise/lock: temporary failuresupervise
temporary failure
-Original Message-From: Tim Hunter
[mailto:[EMAIL PROTECTED]]Sent: Friday, December 29, 2000 10:47
AMTo: QmailSubject: RE: supervise
Supervise is
designed to "superivse" a program and keep it running if it dies for any
reason.
I
ry failure
-Original Message-From: Tim Hunter
[mailto:[EMAIL PROTECTED]]Sent: Friday, December 29, 2000 10:47
AMTo: QmailSubject: RE: supervise
Supervise is
designed to "superivse" a program and keep it running if it dies for any
reason.
I seriously doubt
that supervise
Supervise is
designed to "superivse" a program and keep it running if it dies for any
reason.
I seriously doubt
that supervise is the root of your problems.
Perhaps you can post
to the list the troubles you are having, along with relevant logs and we
can help you work through them.
-
This sounds right to me. Whenvever I had this problem it is because
supervise and related processes had never shut down properly.
ps aux | grep {supervise|svscan|qmail}
kill -9 them all
David
> How do the scripts start your daemontools?
>
> Kill all supervise and svscan process. Check the perm
18, 2000 12:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Supervise error - URGENT
>
>
> Greg Kopp wrote:
> >
> > I would appreciate some help here.
> >
> > I am running qmail as describe in LWQ. I have been running it
> successfully
> > for over 7 mont
Greg Kopp wrote:
>
> I would appreciate some help here.
>
> I am running qmail as describe in LWQ. I have been running it successfully
> for over 7 months with no problem (plus vpopmail, I might add)
>
> When I came in this morning, the server was running very slow for no
> apparent reason. Aft
On Fri, Aug 25, 2000 at 10:37:39PM -0700, Rogue Eagle wrote:
[Re: nameless file taking up space]
> As I mentioned above, everything is fine now, but I'd
> still like to know why this happens.
On Unix, when a file has no links left (i.e., no names point to it),
the inode is not deleted until the l
>This usually means the port it is trying to access is already in use. If
>inetd is running at the same time, edit /etc/inetd.conf and make sure that
>the pop3 client in there has been commented out.
Well, pop3 client is commented out in inetd.conf
As i said there is no problem running the skript
On Tue, Aug 08, 2000 at 04:36:21PM +0200, Manuel Gisbert wrote:
> The supervise process doesn't recognize my pop3d starting up.
>
> After starting "supervise /var/qmail/supervise/qmail-pop3" i get multiple
> error messages
> tcpserver: fatal: unable to bind: address already used
> as superv
hi,
At 16:36 08.08.00 +0200, you wrote:
>Just joining this list a couple of minutes ago, i already got
>my first serious problem.
>
>I installed
>qmail 1.03
>vpopmail 4.8.7
>ucspi-tcp-0.88
>and
>daemontools-0.70
>
>to setup an qmail/vpopmail mailserver
>according to the tutorial "life with qmail"
> After starting "supervise /var/qmail/supervise/qmail-pop3" i get multiple
> error messages
> tcpserver: fatal: unable to bind: address already used
> as supervise repeatedly starts the tcpserver.
This usually means the port it is trying to access is already in use. If
inetd is running at
Dave, et al,
Thanks for the help. I let a linebreak get into my shell script. I've
spent so much time in GUI-land that I still get stuck in the muck
sometimes.
After fixing that, and doing a qmail restart, I checked my running
services. I have the following qmail related in my list:
svscan
su
[EMAIL PROTECTED] wrote:
>[root@samurai /root]# /var/qmail/rc: default: command not found
Oops, you never mentioned that little detail. :-) Your rc script is
wrong.
-Dave
J!M writes:
> [root@samurai /root]# /var/qmail/rc: default: command not found
What does your /var/qmail/rc look like?
paul
I think we've almost got it golden...
Dave Sill Wrote:
>
> Owners/groups/modes are a mess, but I don't think that's your
> problem. Kill off all the processes, then do:
>
> rm -r /var/qmail/supervise/*/supervise
> rm -r /var/qmail/supervise/*/log/supervise
> chown -R root:qmail /var/qmail
[EMAIL PROTECTED] wrote:
>/var/qmail/supervise:
>total 8
>drwxrwxrwx4 qmaill nofiles 4096 Jul 3 00:42 qmail-send
>drwxrwxrwx4 qmaill nofiles 4096 Jul 3 00:42 qmail-smtpd
>
>/var/qmail/supervise/qmail-send:
>total 12
>drwxrwxrwx3 qmaill nofiles 4096 Jul 3 00:42
> [EMAIL PROTECTED] wrote:
>
> >Still having the service lock problem -- thanks Dave, I've followed your
> >suggestions here:
> You mean "supervise"? You should see four: one each for qmail-send,
> qmail-smtpd, and two for "log"--the logs associated with them.
Yes "supervise" - Only two entries
[EMAIL PROTECTED] wrote:
>Still having the service lock problem -- thanks Dave, I've followed
>your suggestions here:
>
>>The general approach to fixing this problem is:
>>
>> 1) Stop all qmail-related processes including svscan, supervises,
>> anything running as a "qmail" user, qmail-send,
Carlo Manuali <[EMAIL PROTECTED]> wrote:
>How can i do qmail supervise?
http://Web.InfoAve.Net/~dsill/lwq.html#installation
-Dave
> Carlo Manuali (Wed 17.0500-09:02):
>
> I've installed the qmail daemontools, but the svsscan don't work propertly.
> I've followed the instruction at http://cr.yp.to/daemontools/svscan.html
> but what i have to do after insert the line csh -cf 'svscan /service &' in
the '&' has to be at the en
On Tue, Apr 18, 2000 at 01:25:51AM -0400, lluisma wrote:
> Hi all,
>
> I have this entry for qmail-pop3d which is under supervise:
> #!/bin/sh
>
> exec env - PATH="/var/qmail/bin:$PATH" \
> tcpserver 0 110 /var/qmail/bin/qmail-popup host.name.gov \
> /bin/checkpassword /var/qmail/bin/qmail-pop3d
Dave Sill <[EMAIL PROTECTED]> wrote:
>
> The script should check to make sure the cd succeeded, e.g.:
[...]
> Sorry about that: that's a basic shell programming error.
What about doing a `set -e` at the beginning of the scripts? That way they'll
stop if they hit any error.
Charles
--
---
[EMAIL PROTECTED] wrote:
>We took down one of our servers and replaced the hard drive with
>something much larger. Another guy was working on it, so I don't
>exactly know right now what procedure was used to do this. But...
>When he brought the server back up, we noticed (understatement) that
>
Peter Janett wrote:
> I have been installing Qmail on a new Solaris box. I have gone through the
Solaris 7? or 8?
What C compiler?
Show me your PATH.
I was able to make it to work on 7 but not on 8.
>
> install instructions at:
> http://Web.InfoAve.Net/~dsill/lwq.html#installation
>
> I insta
Ah, Ha! Doh. Oops.
drwxr-xr-x 17 root root 4096 Mar 29 07:59 /
drwxr-xr-x 18 root root 4096 Apr 3 04:06 /var
drw-r--r-- 11 root qmail 4096 Apr 3 05:00 /var/qmail
drwxr-xr-x 2 root qmail 4096 Apr 3 04:12 /var/qmail/bin
sooo...
chmod 755 /var/qmail
That was the answer I needed. Thank you so m
[EMAIL PROTECTED] wrote:
>I tried to telnet to port 25, then checked
>/var/log/qmail/smtpd/current, and it says
>biglongnumber tcpserver: warning: dropping connection, unable to run
>/var/qmail/bin/qmail-smtpd: access denied
>permissions on it are:
>-rwxr-xr-x 1 root qmail 26108 Apr 3 04:12 qmail
On Tue, 29 Feb 2000, you wrote:
> Not normal. Sounds like you did "cd /var/qmail; svscan" instead of "cd
> /var/qmail/supervise; svscan".
>
> Kill off all the qmail/supervise/svscan processes, delete the
> supervise directories from everywhere but /var/qmail/supervise, check
> your startup scrip
Tom Reinertson <[EMAIL PROTECTED]> wrote:
>$ ls alias/supervise/
>control lock ok status
>
>
>Is this normal, or did I screw something up somewhere?
Not normal. Sounds like you did "cd /var/qmail; svscan" instead of "cd
/var/qmail/supervise; svscan".
Kill off all the qmail/supervise/svscan
Bill Rogers <[EMAIL PROTECTED]> wrote:
>Using the straight script out of LWQ a: script stop
>will kill smtpd and pop3 supervise, but not the underlying
>tcpserver and then restarting doesn't work becasue the port
>is bound.
>
>Here's the run files:
>#!/bin/sh
>QMAILDUID=`id -u qmaild`
>NOFILESGID
Bill Rogers writes:
> Here's the run files:
> #!/bin/sh
> QMAILDUID=`id -u qmaild`
> NOFILESGID=`id -g qmaild`
> exec /usr/local/bin/softlimit -m 200 \
> /usr/local/bin/tcpserver -v -p -x /etc/tcprules.d/qmail-smtpd.cdb \
> -u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-s
Jennifer Tippens <[EMAIL PROTECTED]> wrote:
>I started qmail manually:
>/etc/rc.d/init.d/qmail start
>
>I checked my processes and I have 2 svscan and 4 supervise, 2 multilog,
>and 1 tcpserver, qmail-send, qmail-lspawn, qmail-rspawn, qmail-clean.
You should only have one svscan.
>I get the mess
Robert Wojciechowski Jr. wrote/schrieb/scribsit:
> My question is, do I have to start the two supervise processes (one for SVC,
> and one for SVC/log) with svscan, or can I do it manually? I want to be
> able to restart the services, take down supervise for that service, etc
> without having to w
A Curtin <[EMAIL PROTECTED]> wrote:
>What's the best way to kill supervise/tcpserver/qmail processes for
>system shutdown?
"svc -dx" is the way to go.
>Do the supervise lock directories need clearing up manually, or what?
No, daemontools should take care of them.
-Dave
On Sun, Oct 10, 1999 at 02:07:32PM -0400, Subba Rao wrote:
> I do have the /var/supervise directory.
> The subdirectories are,
>
> qmail
> qmail/send
> qmail/smtpd
>
> I have changed the following program names to their current names.
> setuser - setuidgid
> accustamp - tai64n
> cyclog - muli
I do have the /var/supervise directory.
The subdirectories are,
qmail
qmail/send
qmail/smtpd
I have changed the following program names to their current names.
setuser - setuidgid
accustamp - tai64n
cyclog - mulitlog
Subba Rao
[EMAIL PROTECTED]
==
On Sun, Oct 10, 1999 at 01:29:01PM -0400, Subba Rao wrote:
>
> I am using the startup script from David Sill's LWQ document.
> When I execute this script, I get the following:
>
>
> root@caesar:/etc/rc.d# ./rc.qmail start
> Starting qmail: qmail-send qmail-smtpdsupervise: usage: supervise dir
>
: [EMAIL PROTECTED]
Subject: Re: Supervise and qmail/tcpserver
"Robert Wojciechowski Jr." <[EMAIL PROTECTED]> wrote:
>> # svc -dx /var/supervise/qmail/qmail-smtpd
>
>doesn't kill the tcpserver process, but supervise does die. Why?
Don't know. Trace the superv
[EMAIL PROTECTED] writes:
> Frank D. Cringle wrote
>
> > Here's an extract from 'pstree -c' on a machine running qmail with
> > daemontools-0.61:
> ...
> What is "svscan"?
>
> I didn't see that in my copy of daemontools.
Which version?
--
Frank Cringle, [EMAIL PROTECTED]
voice: (+49 2
Frank D. Cringle wrote
> Here's an extract from 'pstree -c' on a machine running qmail with
> daemontools-0.61:
>
> |-svscan-+-supervise---tcpserver
> ||-supervise---multilog
> ||-supervise---qmail-send-+-qmail-clean
> |||-qmai
Dave Sill wrote:
> [EMAIL PROTECTED] wrote:
>
> >Would there be any reason not to use supervise for qmail-start?
>
> I can't think of a good reason not to.
>
> >I notice that much documentation (I'm still working on merging
> >the various sources of documentation and resolving apparent
> >conf
"Petr Novotny" <[EMAIL PROTECTED]> writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 7 Oct 99, at 9:47, Timothy L. Mayo wrote:
> > Note: you will NOT find qmail-start in your process list after it
> > completes. qmail start launches 3 other daemons and then replaces itself
> > wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7 Oct 99, at 9:47, Timothy L. Mayo wrote:
> Note: you will NOT find qmail-start in your process list after it
> completes. qmail start launches 3 other daemons and then replaces itself
> with the qmail-send process. It is the qmail-send process N
"Petr Novotny" <[EMAIL PROTECTED]> wrote:
>On 7 Oct 99, at 9:09, Dave Sill wrote:
>
>> I can't think of a good reason not to [run qmail-start under
>> supervise].
>
>Um, like, qmail-start only spawns a few daemons and then goes
>away, doesn't it?
No, not exactly. It starts a few daemons then ex
Petr Novotny writes:
> Um, like, qmail-start only spawns a few daemons and then goes
> away, doesn't it? Definitely I can't see it running around my
> machine. Therefore you can't supervise it - supervise works on
> daemons, not on daemon-spawners.
qmail-start execs (not forks) qmail-send.
Misleading. supervise can control any process with does not daemonize
itself or put itself in the background. Here are the contents of my
/var/qmail/rc script which specifically uses supervise. Other examples
can be found as well.
=== start of /var/qmail/rc
#! /bin/sh
# Usin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7 Oct 99, at 9:09, Dave Sill wrote:
> >Would there be any reason not to use supervise for qmail-start?
>
> I can't think of a good reason not to.
Um, like, qmail-start only spawns a few daemons and then goes
away, doesn't it? Definitely I can't
"Robert Wojciechowski Jr." <[EMAIL PROTECTED]> wrote:
>> # svc -dx /var/supervise/qmail/qmail-smtpd
>
>doesn't kill the tcpserver process, but supervise does die. Why?
Don't know. Trace the supervise process with your OS's system call
tracer to see where/why it's dying.
-Dave
[EMAIL PROTECTED] wrote:
>Would there be any reason not to use supervise for qmail-start?
I can't think of a good reason not to.
>I notice that much documentation (I'm still working on merging
>the various sources of documentation and resolving apparent
>conflicts)
Differences aren't necessari
Matthew Harrell <[EMAIL PROTECTED]> wrote:
>:
>: 2. Check out Dan's new daemontools-0.60 package and see if
>:
>: ftp://koobera.math.uic.edu/www/daemontools/fghack.html
>:
>:works for you.
>
>Will do. Looks like I'm way out of date since I'm only using 0.53.
No, 0.60 just came out to
:
: 1. Check if you can prevent your syslogd from daemonizing; see the manpage.
Got it. That didn't even occur to me when I was looking at it.
: 2. Check out Dan's new daemontools-0.60 package and see if
:
: ftp://koobera.math.uic.edu/www/daemontools/fghack.html
:
:works for you.
Matthew Harrell wrote:
> created the directory /var/run/syslog and ran
>
> supervise /var/run/syslog /usr/sbin/syslogd
>
> An instance starts up but then I get a whole screen full of
>
> syslogd: Already running.
Did you check to see if syslogd was already started from system startup
scri
On Wed, 25 Aug 1999, Matthew Harrell wrote:
> created the directory /var/run/syslog and ran
>
> supervise /var/run/syslog /usr/sbin/syslogd
Syslogd puts itself in the background. Supervise then thinks the syslogd
died and starts another. Use the -n switch of syslogd to avoid
auto-backgroundin
John Conover writes:
> Does supervise(1) provide any protection against unauthorized root
> access for a network program that faults, say, from a buffer overflow?
No. Supervise is a substitute for ad-hoc methods for communicating
with daemons.
--
-russ nelson <[EMAIL PROTECTED]> http://cryn
On Mon, Apr 12, 1999 at 05:37:34PM -, John Conover wrote:
> Does supervise(1) provide any protection against unauthorized root
> access for a network program that faults, say, from a buffer overflow?
Supervise just restarts programs AFAIK. How would you design a
program where a parent proces
- Claudio Neves <[EMAIL PROTECTED]>:
| Hello,
|
| I know this was discussed here already, but I'm getting trouble when giving
| svc -h /var/run/qmail . Here is what I've put on my /etc/rc.d/rc.local:
|
| csh -cf '/usr/local/bin/supervise /var/run/qmail /var/qmail/rc &'
|
| And I have the follo
On Wed, Feb 03, 1999 at 11:28:34AM -0700, John Gonzalez/netMDC admin wrote:
> I'm wondering if anyone here is running the above combination?
>
> I have qmaild running under tcpserver at the time, but now our machine has
> become busy enough that the pop3 service is looping (in inetd) and want to
69 matches
Mail list logo
