On Tue, Aug 07, 2001 at 12:04:50PM +1200, Jason Haar wrote:
> We have exactly the same issue here. Exchange goes down. Mail backs up on
> Qmail servers. Exchange comes back up. USERS ARE TOLD ITS WORKING AGAIN.
> Users then wonder why it takes up to 2 hours for queued mail to get to them.
> USERS
Jason Haar <[EMAIL PROTECTED]> wrote:
>It is absolutely necessary.
Why can't you just run qmail-tcpok and send qmail-send an ALRM?
-Dave
On Tue, Aug 07, 2001 at 12:05:12PM +1200, Jason Haar allegedly wrote:
> On Mon, Aug 06, 2001 at 02:16:00PM +0200, Peter van Dijk wrote:
> > On Mon, Aug 06, 2001 at 01:07:36PM +0100, Richard Underwood wrote:
> > > When the exchange server comes back up, I kick the qmail-send
> > > process to get
On Mon, Aug 06, 2001 at 02:16:00PM +0200, Peter van Dijk wrote:
> On Mon, Aug 06, 2001 at 01:07:36PM +0100, Richard Underwood wrote:
> > When the exchange server comes back up, I kick the qmail-send
> > process to get it to deliver the queue. At this point I should be able to go
> > off and do
On Mon, Aug 06, 2001 at 10:02:10PM +0200, Pavel Kankovsky wrote:
> On Mon, 6 Aug 2001, Peter van Dijk wrote:
>
> > Why are you kicking qmail-send? That should never be necessary in a
> > production environment.
>
> Apparently, your "production environment" does not involve situations when
> you
On Mon, 6 Aug 2001, Peter van Dijk wrote:
> Why are you kicking qmail-send? That should never be necessary in a
> production environment.
Apparently, your "production environment" does not involve situations when
you need to convince qmail-send to retry some of the queued messages
quickly in ord
ead, you'll see that it's about qmail-remote processes
hanging on Linux.
The argument was started because I described multiple connections to
a site as an "issue". I could have ignored the replies telling me that "it
wasn't an issue" as flame-bait, but ha
On Mon, Aug 06, 2001 at 02:17:22PM +0100, Richard Underwood allegedly wrote:
> > And if you don't like this behaviour: write a patch (or find one), or
> > stop using qmail. Nobody is forcing you to use qmail.
> >
> Perhaps, but using this list to tell people (often quite forcefully)
> that
> From: Peter van Dijk [mailto:[EMAIL PROTECTED]]
> On Mon, Aug 06, 2001 at 01:07:36PM +0100, Richard Underwood wrote:
>
> > When the exchange server comes back up, I kick the qmail-send
> > process to get it to deliver the queue. At this point I should be able
to go
> > off and do other thin
On Mon, Aug 06, 2001 at 01:07:36PM +0100, Richard Underwood wrote:
> > From: Henning Brauer [mailto:[EMAIL PROTECTED]]
> >
> > On Mon, Aug 06, 2001 at 11:09:25AM +0100, Richard Underwood wrote:
> > > I've also noticed that if qmail tries to deliver (for example) 50
> > > messages to one host co
On Mon, Aug 06, 2001 at 01:07:36PM +0100, Richard Underwood wrote:
[snip]
> Read what I wrote again. It IS qmail's fault. One role I use qmail
> for is to accept mail which is then passed on to an exchange server on the
> same network. Here's an example of what can happen ...
>
> If t
> From: Henning Brauer [mailto:[EMAIL PROTECTED]]
>
> On Mon, Aug 06, 2001 at 11:09:25AM +0100, Richard Underwood wrote:
> > I've also noticed that if qmail tries to deliver (for example) 50
> > messages to one host concurrently, perhaps 2 will get through. The rest
will
> > be retried, but u
On Mon, Aug 06, 2001 at 11:09:25AM +0100, Richard Underwood wrote:
> I've also noticed that if qmail tries to deliver (for example) 50
> messages to one host concurrently, perhaps 2 will get through. The rest will
> be retried, but unfortunately they tend to get retried at much the same
> ti
> > try a couple of dozen connections to the same remote host
> at the same time.
> > (This is an issue in itself!)
>
> Why is this an issue? If the remote host can handle 100 inbound
> connections, you should be able to open 100 connections to
> them, inject
> your messages, and close the con
Richard Underwood writes:
> My other suspicion is that there's a chance that my one server will
> try a couple of dozen connections to the same remote host at the same time.
> (This is an issue in itself!)
Not really. It used to be an issue back in 1996 when qmail was first
introduced.
> I just looked at the server I had problems with -- 15 hung
> qmail-remotes :(
>
Not good! I peaked at 26 before I noticed.
> How did you test this patch?
> Are you saying that you were able to reliably reproduce the problem?
> I could never do this... If so, how?
>
I tested t
Hi,
I asked about qmail-remote processes hanging in read() on this list
a few days ago. It appears that this has been reported before, but no
conclusion seemed to have been made.
The problem appears to be in timeoutread() which uses select() to
prevent read() from blocking. For
Richard Underwood <[EMAIL PROTECTED]> wrote:
>
> My other suspicion is that there's a chance that my one server will
> try a couple of dozen connections to the same remote host at the same time.
> (This is an issue in itself!)
Why is this an issue? If the remote host can handle 100 inboun
On Fri, Aug 03, 2001 at 03:07:57PM +0100, Richard Underwood wrote:
> Hi,
>
> I asked about qmail-remote processes hanging in read() on this list
> a few days ago. It appears that this has been reported before, but no
> conclusion seemed to have been made.
I just looked at t
I've hit an odd problem with qmail-remote.
With one of our ISP's DNS servers set as primary, qmail-remote will hang
indefinitely on some addresses. The DNS server in question responds fine
to dig queries.
Example:
First DNS server in resolv.conf is 205.152.0.20
Run the following command: (t
> Setting an alarm is a nasty hack in my opinion, but I have to admit
> that it's something I considered.
Well, the qmail-remote connection is well and truly wedged once it's
in this state and if the select() timed out as it's meant to,
qmail-remote would exit with a delivery failure indica
> This problem's been reported before. If your OS says that an fd is
> readable via select(), then the read() should not block.
>
> As you observe though, the read is blocking so your OS is probably not
> telling the truth when it returns from the select().
>
> The archives have plenty of discus
> I've been running qmail on a number of platforms quite happily for a
> while - until now I've had no problems at all. However, I am now
> experiencing a problem with qmail-remote hanging.
> The problem I see is with qmail-remote failing to terminate when a
Hi,
I've been running qmail on a number of platforms quite happily for a
while - until now I've had no problems at all. However, I am now
experiencing a problem with qmail-remote hanging.
I'm running qmail on this server for sending mails from websites and
bulk m
Probably a misunderstood.
> > Try something like:
> >
> > [snip] /usr/local/sbin/stunnel -p /etc/stunnel.pem -N spop3 -f -l
> > /var/qmail/bin/qmail-popup -- qmail-popup [snip]
>
> No. Running stunnel not as daemon but under tcpserver is a good idea.
> Maex posted a good example script a few days
On Mon, Jul 30, 2001 at 10:16:44AM +0200, Andrea Cerrito wrote:
> mmmhhh, looks like a wrong startup script!
>
> > Here is my invocation of stunnel:
> >
> > #!/bin/sh
> > exec /usr/local/bin/softlimit -m 300 \
> > /usr/local/bin/tcpserver -v -likauni.vrona.com -H -R 0 pop3 \
> > /usr/local/sb
mmmhhh, looks like a wrong startup script!
> Here is my invocation of stunnel:
>
> #!/bin/sh
> exec /usr/local/bin/softlimit -m 300 \
> /usr/local/bin/tcpserver -v -likauni.vrona.com -H -R 0 pop3 \
> /usr/local/sbin/stunnel -p /etc/stunnel.pem \
> -l /var/qmail/bin/qmail-popup -- qmail-popup
to install the stunnel wrapper on POP3.
>
>I believe I've done everything as I should but clients cannot successfully
>retrieve e-mail. It appears that something is hanging during the
>process. The client program (Eudora) appears to be stuck trying to get e-mail.
>
>On t
Hi all,
I've been running a very stable RedHat installation with qmail for some
time now.
Recently I've tried to install the stunnel wrapper on POP3.
I believe I've done everything as I should but clients cannot successfully
retrieve e-mail. It appears that something is han
I found reference to using a -H option to disable reverse dns lookup on
tcpserver and used it. It had zero effect. Any other ideas?
Tib
On Thu, 26 Jul 2001, Tib wrote:
> But it's always been looking up hostnames.. and the ones that connect are
> successfully looked up (well I'm pretty sure th
But it's always been looking up hostnames.. and the ones that connect are
successfully looked up (well I'm pretty sure they are, when I run a
netstat they show as resolved hostnames). Plus as I said this came out of
the blue. is there a switch I can give tcpserver to test this possible
solution? W
Tib,
We had this problem when tcpserver was reverse mapping IP addresses. Maybe
you need to disable reverse lookups?
David Gartner
Tib wrote:
> So far as I have been able to find out by looking through the logs on the
> system, the qmail-smtpd daemon stopped functioning around 19:30 on the
>
So far as I have been able to find out by looking through the logs on the
system, the qmail-smtpd daemon stopped functioning around 19:30 on the
24th of july. Nothing was changed on the system to instigate this, in fact
it was a static setup for the past 3 months or so. So on to the meat of
the ma
Thanx everyone ..
Adding -HP to the tcpserver line fixed the problem.
Christian wrote:
> Hi,
> I'm a newbie to qmail and have just setup my first qmail server
>
> I'm having problems with users sending mail
> It just hangs .. trys for ages to send &
> There's no error messages returned
> Which
n Kundra wrote:
>
>>Are transactions being logged in the qmail log?
>>Sachin
>>
>>-Original Message-
>>From: Christian [mailto:[EMAIL PROTECTED]]
>>Sent: Wednesday, July 25, 2001 12:12 AM
>>To: qmail
>>Subject: Hanging
>>
>>Hi,
&
re is a CR-LF issue with some client software which is supposed to be
fixable with fixcrio
-Original Message-
From: Christian [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 25, 2001 12:12 AM
To: qmail
Subject: Hanging
Hi,
I'm a newbie to qmail and have just setup my first qm
Chirstian,
The only thing that comes to mind is to try to troubleshoot a little to see
where it's hanging. Try these commands:
(1) telnet mail.domain.com 25
(2) (after the greeting of course) mail from: [EMAIL PROTECTED]
(3) rcpt to: [EMAIL PROTECTED]
(4) data
(5) .(one period on a li
Kindly write the subject line more to the subject matter. If I search the
archives, it will be difficult to know what type of help you are asking by
the subject "hanging".
Thanks.
Kirti "Kirt" S. Bajwa
Chief Technical Officer
TIB Computer Systems, Inc.
Mountain City, TN 3
ilto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 25, 2001 12:12 AM
> To: qmail
> Subject: Hanging
>
>
> Hi,
> I'm a newbie to qmail and have just setup my first qmail server
>
> I'm having problems with users sending mail
> It just hangs .. trys for ages to
Hmm well I'm finding the logs a little confusing
now I'm using multilog in lieu of splogger
/var/log/qmail/smtpd/current shows the line
@40003b5e93e01b9ee27c tcpserver: pid 7853 from 192.168.0.1
which is most likely an email that I'm trying to send
now which is hanging
A f
Are transactions being logged in the qmail log?
Sachin
-Original Message-
From: Christian [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 25, 2001 12:12 AM
To: qmail
Subject: Hanging
Hi,
I'm a newbie to qmail and have just setup my first qmail server
I'm having problems
Hi,
I'm a newbie to qmail and have just setup my first qmail server
I'm having problems with users sending mail
It just hangs .. trys for ages to send &
There's no error messages returned
Which makes it hard to figure out what's wrong.
All the processes are running
Port 25 seems to be open .. I
On Fri, Jul 06, 2001 at 09:34:39PM -0600, Charles Cazabon wrote:
> Brian Lane <[EMAIL PROTECTED]> wrote:
> >
> > In summary, I am having problems with emails getting stuck when fetched
> > from qmail-pop3d. They are almost always attached MS Word documents. They
> > aren't necessarily long, I'v
Brian Lane <[EMAIL PROTECTED]> wrote:
>
> In summary, I am having problems with emails getting stuck when fetched
> from qmail-pop3d. They are almost always attached MS Word documents. They
> aren't necessarily long, I've got 32k messages that do it and 1M messages.
>
> I'm running on kernel
ange the MTU/MRU and
who knows what direcPC is doing as packets pass through their system. To fix
this case I move the mail to the web directory and download it using
Explorer. When we use Agent 1.8 on the lan to download messages from the
webserver it will exhibit the same 'hanging' tha
This isn't *strictly* a qmail problem, but we are running qmail and seeing
some weird behavior.
I just upgraded our firewall to Redhat 7.0 w/ 2.2.16-22 kernel running
ipchains. We *were* at 2.0.38 w/ ipfwadm. Ever since, Outlook Express
(5.50.4522.1200) hangs in sending e-mail, but only in odd mo
> tcprules should run only when you're rebuilding the rules database. It doesn't
> run for every incoming connection or anything like that.
>
> You're running some kind of non-qmail program that's running tcprules. Nothing
> in the qmail package runs it automatically; you have to run it explicit
On Tue, Aug 22, 2000 at 11:20:33AM -0400, Jeff Garvas wrote:
> I've killed radius on this machine and watched it's load jump from 1 to
> 25. tcprules seems to be running numerous times.
>
> Should tcprules be running more than once?
tcprules should run only when you're rebuilding the rules data
I take it back...
I've killed radius on this machine and watched it's load jump from 1 to
25. tcprules seems to be running numerous times.
Should tcprules be running more than once? Should it be running multiple
instances of mysqld? At the moment there are only two of these:
891 ?SN
I'm having a problem with my qmail machine. I'm hosting less than 10
virtual domains and using the web tools to let individual people
administrate their domains.
I'm using the SQL based authentication.
This machine also acts as a radius authentication server with sql based
authentication.
I
Brian Estes <[EMAIL PROTECTED]> wrote:
>
> > What is your logging configuration for qmail on that box? If you're going
> > to the syslog, that could be your problem. syslog has been known to bring
> > even large boxes to their knees with a busy qmail server. Try
> > multilog or something inst
> has anyone experienced this or anything like this
not the same...
just qmail-smtpd crashed ones with the following message in the logs:
--- from /var/log/messages ---
Jul 31 05:42:59 joshua -- MARK --
Jul 31 05:52:52 joshua kernel: Oops:
Jul 31 05:52:52 joshua kernel: CPU:0
Jul 31 05:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17 Aug 2000, at 11:21, Brian Estes wrote:
> The server hangs and is unresponseive to anything but pings
> load on the server skyrokets to 300+
> server is NOT loggin anything, in fact the server is doing nothing
> (cron can not even run)
Can "top
Brian Estes <[EMAIL PROTECTED]> wrote:
> I am having the following problem on my qmail server ...
>
> running the LATEST version of qmail 1.03
> Sun E-450 2CPU, 1G RAM
>
> The server hangs and is unresponseive to anything but pings
> load on the server skyrokets to 300+
> server is NOT loggin an
I am having the following problem on my qmail server ...
running the LATEST version of qmail 1.03
Sun E-450 2CPU, 1G RAM
The server hangs and is unresponseive to anything but pings
load on the server skyrokets to 300+
server is NOT loggin anything, in fact the server is doing nothing (cron
can n
Adam,
tcpdump | grep smtp
And look and see what is happening on the packet level.
Sean
- Original Message -
From: Adam McKenna <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 04, 2000 5:37 PM
Subject: tcpserver hanging
> Does anyone know why tcp
Does anyone know why tcpserver would do this?
It seems to be randomly hanging on incoming connections, about 1 in every 10:
Connection closed by foreign host.
adam@orbicus:~$ telnet localhost 110
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
+OK <25910.9654
pkill without the "-u 0" is the answer. My original question was why this
startup script would kill only the root owned processes.
BTW, I would be interested in a discussion of the political and theoretical
issues involved in stopping qmail outright, since, until I can figure out
why q
Mike Denka wrote, among other things:
>/usr/bin/pkill -f -u 0 qmail-smtpd
>/usr/bin/pkill -f -u 0 qmail-send
>/usr/bin/pkill -f -u 0 qmail-lspawn
>/usr/bin/pkill -f -u 0 qmail-rspawn
>/usr/bin/pkill -f -u 0 qmail-clean
>/usr/bin/pkill -f -u 0 splogge
quot;
exit 1
;;
esac
exit 0
> -Original Message-
> From: Dave Kelly [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 13, 2000 1:12 PM
> To: [EMAIL PROTECTED]
> Subject: RE: qmail hanging - best way to restart
>
>
> What does your 'qmail start' script l
mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, June 13, 2000 3:04 PM
>To: [EMAIL PROTECTED]
>Subject: qmail hanging - best way to restart
>
>
>We are having some problems with qmail hanging and no longer responding to
>POP requests or smtp requests. Restarting all qmail processes and
>
We are having some problems with qmail hanging and no longer responding to
POP requests or smtp requests. Restarting all qmail processes and
qmail-popup resolves the problem. I notice that when I stop qmail, the
/etc/init.d/qmail stop script does not stop all processes, only those whose
oved things even more (after a few hassels :))
I can try and find the docs and papaerwork - but try searching on the
mailling list archive for sparc7 and process hanging...
Best of luck
Tonino
Hi,
I had the same problem - it is Solaris 7 - it has a OS bug that keeps
the qmail-smtpd and qmail-queue processes hanging around indefinatly -
(well almost ) and this eats up memory and slows everything down - A
major pain :))
TO FIX - you cannot just upgrade to solaris 8 - you need to re
> bjv:
> What has started to happen today is that receiving mail is slow, between
> the '.' and 'ok' from qmail (got that from telnet to port 25). Even slower
> is its sending, which is about a message every 5 or 10 seconds. The other
> noticable problem is that there are thousands of qmail-queue
0.00.0 0.0 0.00.00.0 0 0
cobalt:vold(pid207)
s4 is mounted as /var/qmail. Obviously pretty busy 99%! I think this 99%
busy is a result of these qmail-queue porcess, however I am hesitant to
believe that this problem is as simple as the disk is maxing out and thus
the hanging q
ECTED] wrote:
> Hi there,
>
> I made a post the other day to ask about hanging
> qmail-smtpd processes problem I'm encountering. I'm still having
> the problem here but just found some more 'facts' about
> it, so am re-posting this problem with the new info a
Hi there,
I made a post the other day to ask about hanging
qmail-smtpd processes problem I'm encountering. I'm still having
the problem here but just found some more 'facts' about
it, so am re-posting this problem with the new info and hope
someone out there happens to know
"Md. Sifat Ullah Patwary" <[EMAIL PROTECTED]> writes:
Hi all!
Hi dude!
I found my qmail server has been hanging time to time. At hang situatin, it
receives mail from any smtp client but does not delever it to destination.
All mails are queued. I have to restart th
Hi all!
I found my qmail server has been hanging time to time. At hang situatin, it
receives mail from any smtp client but does not delever it to destination.
All mails are queued. I have to restart the machine to get life working.
qmail works nice for 2/3 days and suddenly hangs again. Even if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3 Dec 99, at 16:49, Will Harris wrote:
> > > note the strange "from" address #@[].
> >
> > It's what qmail uses for double bounces (ie. the letter bounced
> > back to envelope sender, and the bounce bounced as well).
>
> not particularly informat
Petr Novotny wrote:
> > 2 Dec 1999 16:51:48 GMT #225302 3891 <#@[]>
> > remote [EMAIL PROTECTED]
> >
> > note the strange "from" address #@[].
>
> It's what qmail uses for double bounces (ie. the letter bounced
> back to envelope sender, and the bounce bounced as well).
not particula
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3 Dec 99, at 16:17, Will Harris wrote:
> 2 Dec 1999 16:51:48 GMT #225302 3891 <#@[]>
> remote [EMAIL PROTECTED]
>
> note the strange "from" address #@[].
It's what qmail uses for double bounces (ie. the letter bounced
back to envel
Hey folks, a strange problem. when certain messages double bounce, they
end up hanging in the queue because the remote MTA where I read my mail
doesn't accept something qmail is trying to do. qmail-qread shows the
message in the queue as follows:
2 Dec 1999 16:51:48 GMT #225302
Greetings folks,
Ever since I implemented the "fixcr" addition to "smtpd", I've noticed that
over time my qmail servers accumulate a large number (several dozen) pairs
of processes: "fixcr" and "sh -c fixcr | /usr/qmail/bin/qmail-smtpd".
--
ps -alxw
Hello all and thanks in advance.
Heres my problem.
Mail seems to hang on all the clients sometime between lunch and 1:30. It
happens everyday. And it only seems to be e-mail. I can telnet to the port
locally and it seems fine. But from a remote system, no go. Any suggestions?
I have checked everyt
Your TCP/IP stack should eventually give up either due to a timer expiring
or a retry count being exceeded. If they are hanging around forever, then it
has to be a local stack bug right?
(FWIW I see lingering connections on Solaris 2.6 from time to time with
qmail-smtpd - sigh).
Regards
Wow.. ain't computers neat!
>From what I understand is that qmail-remote is waiting for the close
message? I only have 1 or 2 qmail-remote processes when I ps ax.
In any case... how do I kill a lingering tcp connection?? Sorry, I know
this is not the networking list... but I cringe at the th
On Fri, Feb 12, 1999 at 09:47:14PM +0100, Harald Hanche-Olsen wrote:
> - Paul Farber <[EMAIL PROTECTED]>:
>
> | Hello all, got a new one for qmail 1.03 users everywhere.
> |
> | I've had these connections for about a day now. qmail-qread says these
> | messages are not in the que, and qmail-qs
One of qmail's defects is that asking qmail-send to stop doesn't do
anything to also stop any qmail-remotes that may be hanging around, and
can't exit until they do so first. You'll have to manually kill them,
or wait until they go away on their own.
Notice also that those
- Paul Farber <[EMAIL PROTECTED]>:
| Hello all, got a new one for qmail 1.03 users everywhere.
|
| I've had these connections for about a day now. qmail-qread says these
| messages are not in the que, and qmail-qstat equalled the number of
| messages that qmail-qread displayed.
|
| I stopped
On Fri, Feb 12, 1999 at 03:11:58PM -0500, Paul Farber wrote:
> Hello all, got a new one for qmail 1.03 users everywhere.
>
> I've had these connections for about a day now. qmail-qread says these
> messages are not in the que, and qmail-qstat equalled the number of
> messages that qmail-qread d
Hello all, got a new one for qmail 1.03 users everywhere.
I've had these connections for about a day now. qmail-qread says these
messages are not in the que, and qmail-qstat equalled the number of
messages that qmail-qread displayed.
I stopped and restarted the qmail-smtpd daemon (im on a RH 5
83 matches
Mail list logo
