On Thursday, Jan 29, 2004, at 09:37 US/Mountain, Jeff Ross wrote:
I hate to keep replying to my own messages. Really :-)
On Friday, Jan 23, 2004, at 07:56 US/Mountain, Jeff Ross wrote:
Howdy!
I upgraded my mail server a while back to from an old PI with 32 megs of ram to a Pentium Pro with 128 megs of ram.
[EMAIL PROTECTED] $ tmda-pending -V
TMDA/1.0 "Cannonade" (Python/2.3.2 on OpenBSD-3.4-i386-Intel_Pentium_Pro_-GenuineIntel-_686- class,_256KB_L2_cache-32bit-ELF)
Yesterday I noticed that I had one python process taking up a huge chunk of my system. A little digging showed it to be tmda-ofmipd.
load averages: 0.58, 0.28, 0.20 07:23:31
52 processes: 1 running, 51 idle
CPU states: 0.3% user, 0.0% nice, 0.0% system, 0.0% interrupt, 99.7% idle
Memory: Real: 47M/63M act/tot Free: 58M Swap: 58M/256M used/tot
PID USERNAME PRI NICE SIZE RES STATE WAIT TIME CPU COMMAND
10799 root 2 0 51M 40M sleep poll 1:17 0.00% python
9418 root 10 0 100K 188K sleep nanosl 0:51 0.00% svscan
22796 dnscache 2 0 1416K 1428K idle poll 0:35 0.00% dnscache
[EMAIL PROTECTED] $ ps -wwwaux | grep [p]ython
tofmipd 10799 0.0 31.0 52140 40476 ?? I 9:15AM 1:16.86 python /usr/local/src/tmda/bin/tmda-ofmipd -f -p heinlein.openvistas.net:8025 -R pop3://heinlein.openvistas.net
I am running tmda-ofmipd under daemontools, using the run script that Tim posted some time back.
[EMAIL PROTECTED] $ cat /service/tmda-ofmipd/run #!/bin/sh #start tmda-ofmipd exec > /dev/null 2> /dev/null exec /usr/local/src/tmda/bin/tmda-ofmipd -f \ -p heinlein.openvistas.net:8025 \ -R pop3://heinlein.openvistas.net
I put tmda-ofmipd under daemontools to autostart it on reboot. Attempting to call it from rc.local was failing with an env error, although once the system was up I could start it from the command line with no problem.
I don't remember seeing this type system usage on the old box. Anyone else out there with the same sort of scenario?
Thanks,
Jeff
-- Jeff Ross Open Vistas Networking, Inc. http://www.openvistas.net
I'm finally getting back to this "quirk". If I do not run tmda-ofmipd under daemontools, it doesn't have such a large memory footprint.
If I start it out of rc.local, using this command:
/usr/local/bin/python /usr/local/src/tmda/bin/tmda-ofmipd \ -p heinlein.openvistas.net:8025 \ -R pop3://heinlein.openvistas.net
I see this message printed to the console.
********************************************************************** WARNING: The security implications and risks of running /usr/local/src/tmda/bin/tmda-ofmipd in "seteuid" mode have not been fully evaluated. If you are uncomfortable with this, quit now and instead run /usr/local/src/tmda/bin/tmda-ofmipd under your non-privileged TMDA user account. **********************************************************************
The process also shows up when I do a ps -wwwaux, so it would appear to be running.
However, it will not allow e-mail to be sent, failing each time with an authentication error.
When I kill the process started from rc.local and use the exact same command to start it from the command line, all works as it should.
I added the fullpath to python in the rc.local command thinking to get past the env error I mentioned above. And that seems to have worked, although, again, tmda-ofmipd didn't.
In my own attempt to debug this, I added the -d switch to the command in rc.local and rebooted. I then got the message displayed to the console that tmda-ofmipd was using the pop3 auth method, and that tmda-ofmipd was listening on port 8025. However, dashing back up the stairs out of that cold basement where the servers live and sending a test message didn't print any more messages to the console, but it didn't work, either, again, failing with the same authentication > error.
At this point I'm pretty clueless, and could use some better debugging hints. I would much prefer to start tmda-ofmipd from daemontools, since that gives me the full range of its commands and the autostart on a system reboot. But, the 51M size seems a bit extreme since it forces my 128M server into swap.
If I can't use daemontools, I really need to be able to start tmda-ofmipd from rc.local. I can't always count on being here if the UPS can't bridge an outage and the mail server shuts down to start up tmda-ofmipd from the command line when the power comes back.
I suppose I could hack up a cron job to check every minute or so if tmda-ofmipd is running, and if it isn't to start it. I'll keep that as a last resort :-)
Sorry for the length of these messages, but I'm trying to be complete.
Jeff -- Jeff Ross Open Vistas Networking, Inc. http://www.openvistas.net
This morning I had a power outage that the UPS (and it is a big sucker) couldn't bridge. When the power came back on-line every thing booted and started okay except for the tmda-ofmipd daemon running on my mail server. Calls started coming in almost immediately ;-)
Worse, I'd been watching the daemon's memory usage grow over the uptime of the mail server. Yesterday when I looked, tmda-ofmipd was using 27MB, and that was only 4 days after the last reboot.
I'd really appreciate it if anyone else out there running tmda-ofmipd and OpenBSD could let me know if this sort of memory usage is what you are getting as well.
Better would be some pointer to a methodology to see why such a simple daemon should be using so much of my system.
And best yet would be debugging suggestions/patches to make tmda-ofmipd run under daemontools without forcing my system into swap. So, when I'm out in the morning for coffee and the power goes out, I don't return home to find an answering machine full of customer complaints that mail will not go out. ;-)
Thanks yet again for wading through all of the previous (but unanswered) e-mails I've sent as a part of this thread...
Jeff -- Jeff Ross Open Vistas Networking, Inc. http://www.openvistas.net _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
