From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: sendmail-bugs@sendmail.org, linux-kernel@vger.kernel.org
Subject: [Fwd: [Fwd: sendmail fails to deliver mail with attachments in /var/spool/mqueue]]
Date: Fri, 10 Nov 2000 13:33:08 -0700 [thread overview]
Message-ID: <3A0C5B84.BB850FA3@timpanogas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 176 bytes --]
Claus,
Richard appears to have found a problem while sending a 45MB file to me
with 8.11.10. I guess it's time for you to join the thread. Please
review attached.
Jeff
[-- Attachment #2: Type: message/rfc822, Size: 2895 bytes --]
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: "Jeff V. Merkey" <jmerkey@timpanogas.org>, linux-kernel@vger.kernel.org
Subject: Re: [Fwd: sendmail fails to deliver mail with attachments in /var/spool/mqueue]
Date: Fri, 10 Nov 2000 15:07:46 -0500 (EST)
Message-ID: <Pine.LNX.3.95.1001110150021.5941A-100000@chaos.analogic.com>
On Fri, 10 Nov 2000, Andrea Arcangeli wrote:
> On Fri, Nov 10, 2000 at 12:34:40PM -0700, Jeff V. Merkey wrote:
> >
> > Andrea,
> >
> > All done. It's already setup this way.
>
> Ok. So please now show a tcpdump trace during the `sendmail -q` so we can see
> what's going wrong in the TCP connection to the smtp server:
>
> tcpdump port smtp
>
> Andrea
I tried to send Jeff a 45 Megabyte file. It is still in the queue.
FLAGS UID PID PPID PRI NI SIZE RSS WCHAN STA TTY TIME COMMAND
[SNIPPED...]
140 0 82 1 9 0 840 100 do_select S ?
0:00 /usr/sbin/rpc.pcnfsd /var/spool/lpd
140 0 86 1 8 0 1744 364 do_select S ?
0:00 sendmail: accepting connections
40 0 5742 1 16 0 1812 136 wait_for_tc S ? 0:01
sendmail: ./eAAJm8V05731 vger.timpanogas.org.: client DATA 354
It isn't a TCP/IP stack problem. It may be a memory problem. Every time
sendmail spawns a child to send the file data, it crashes. That's
why the file never gets sent!
This is how /proc/meminfo looks right after it crashes. There has
been a lot of swapping going on.
total: used: free: shared: buffers: cached:
Mem: 328114176 38932480 289181696 0 2293760 27115520
Swap: 139821056 10014720 129806336
MemTotal: 320424 kB
MemFree: 282404 kB
MemShared: 0 kB
Buffers: 2240 kB
Cached: 26484 kB
Active: 5576 kB
Inact_dirty: 18348 kB
Inact_clean: 4800 kB
Inact_target: 332 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 320424 kB
LowFree: 282400 kB
SwapTotal: 136544 kB
SwapFree: 126764 kB
Cheers,
Dick Johnson
Penguin : Linux version 2.4.0 on an i686 machine (799.54 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
reply other threads:[~2000-11-10 20:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A0C5B84.BB850FA3@timpanogas.org \
--to=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sendmail-bugs@sendmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox