On Friday, Mar 5, 2004, at 18:33 US/Mountain, Jason R. Mastaler wrote:
You've been running tmda-ofmipd for a great long while without any problems, and suddenly it started consuming more ram.
This is a good point, Jason.
What changed in your configuration (OS, hardware, qmail patches, etc) between when it was running fine, and when it was not? Has your tmda-ofmipd configuration changed at all? What kind of authentication are you using for tmda-ofmipd? Is this the same type of authentication that you've always done?
OS--upgraded to OpenBSD 3.4 -current as of Jan 4, 2004. 3.5 -beta is just out now, I'll try upgrading to that as soon as the make release process completes on my build machine.
Hardware--at the same time as the OS upgrade I upgraded the hardware as well. I went from a 48MB 90MHz Pentium with 1 GB ide drive to a 128 MB 200MHz Pentium Pro with 2 2GB scsi2 drives.
I built this system from scratch, installed the OS, rebuilt all the binaries to allow for the a.out to ELF OpenBSD switch, and let it run for nearly a week before I stopped incoming mail on the old machine, tarred up all user information, transferred it to the new server, untarred it, and moved the ethernet cable from old to new. The mail system was down for just a little over an hour early one Sunday morning.
No patches at all to qmail, either before or after.
Tmda-ofmipd--Until I switched tmda-ofmipd over to run under daemontools, I've never been able to get it to automatically start at boot time, even before the system upgrade. I described that whole process before, but in a nutshell, I first tried just calling it from rc.local, which would fail with an env not found error. I then tried adding the full path to python in front of the path to tmda-ofmipd. Tmda-ofmipd would then apparently start at boot, but it would not accept any outgoing mail. If I started tmda-ofmipd from the command-line after the system was up, tmda-ofmipd would work, but that's when I noticed the ever escalating memory use.
Before the Python upgrade to 2.3.3, running tmda-ofmipd under daemontools would use a tremendous amount of ram. My 128 MB machine would be using 50+ MB of swap, with another 50+ being used by tmda-ofmipd immediately after boot. After the Python upgrade, I was able to put tmda-ofmipd back under daemontools. I get 4 MB memory usage at boot, and for the first day or so, then it'll jump to 13MB, and then a short time later, jump to 24MB. Sometime after that it will quit accepting mail.
Running under daemontools at least gives me automatic start at boot, even though I do not have full control of the daemon; i.e. I can't stop or restart it with svc commands. Running it from the cli after the system is up also works, but I still have the same escalating memory and eventual failure problem with the added inconvenience of having to be here when the system reboots.
I've always used POP3 authentication for tmda-ofmipd, both before and after the problem.
If it's a hardware problem, it is specific to tmda-ofmipd. Every other process on the server is running within what I expect to be normal memory usage patterns. If it is OpenBSD 3.4 specific, again, tmda-ofmipd seems to be the sole problem.
I will try to upgrade to 3.5 -beta over the weekend, but if anyone has any other ideas before then, please let me know.
Thanks!
Jeff
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
-- Jeff Ross Open Vistas Networking, Inc. http://www.openvistas.net _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
