Hi all!
I've installed mailman on a RH 6.2 machine. The POP3 server in that machine works perfectly, the messages I send to the mailing lists are logged in the logs/post file. But, no mail goes to the list members.
I've been checking my /etc/aliases file, among other things, and everything seems to be in its place, so I don't know where to look anymore.
Any help, please!!
thanks very much
On Oct 26, 2000 at 12:53, Rodrigo Moya wrote:
I've installed mailman on a RH 6.2 machine. The POP3 server in that machine works perfectly, the messages I send to the mailing lists are logged in the logs/post file. But, no mail goes to the list members.
POP3? SMTP would be what you want to check.
Some guesses...
Check mailman's crontab. The queue runner should be a cron job, AIUI.
-- Satya. <URL:http://satya.virtualave.net/> US-bound grad students! For pre-apps, see <URL:http://quickapps.cjb.net/> Due to circumstances beyond our control, we regret to inform you that circumstances are beyond our control. --Paul Benoit
On Oct 26, 2000 at 12:53, Rodrigo Moya wrote:
I've installed mailman on a RH 6.2 machine. The POP3 server in that machine works perfectly, the messages I send to the mailing lists are logged in the logs/post file. But, no mail goes to the list members.
POP3? SMTP would be what you want to check.
Some guesses...
Check mailman's crontab. The queue runner should be a cron job, AIUI.
it seems ok. The qrunner binary is set to be executed every minute (at least this is what "crontab -u mailman -l" says.
And no /etc/cron.{allow,deny} exists, so mailman should be allowed to run cron jobs.
And "tail -f logs/qrunner" shows 2 log messages every minute. So, everything related to cron seems to work.
But still, list members don't get any message from the lists.
What else could be?
cheers
Rodrigo,
We seem to be having similar problems, and no one is really making any good guesses. One weird thing that I noticed is that if I kill all current qrunners, and remove all locks:
killall qrunner; rm ~mailman/locks/*then a new qrunner will pop up in a minute (from cron). If I watch it in top:
top -qUmailmanIt uses a little CPU for a minute or two, and then slowly dies off to 0% CPU usage. It never does anything that I can see, and runs for a very long time.
Could I have a corrupted msg that is hanging qrunner? The biggest file in qfiles is about 6k, so it's not a size issue...
- HWARNING: 'killall' may work very differently on various unix flavors. Don't do that on a Solaris box!
On Oct 26, 2000 at 12:53, Rodrigo Moya wrote:
I've installed mailman on a RH 6.2 machine. The POP3 server in that machine works perfectly, the messages I send to the mailing lists are logged in the logs/post file. But, no mail goes to the list members.
POP3? SMTP would be what you want to check.
Some guesses...
Check mailman's crontab. The queue runner should be a cron job, AIUI.
it seems ok. The qrunner binary is set to be executed every minute (at least this is what "crontab -u mailman -l" says.
And no /etc/cron.{allow,deny} exists, so mailman should be allowed to run cron jobs.
And "tail -f logs/qrunner" shows 2 log messages every minute. So, everything related to cron seems to work.
But still, list members don't get any message from the lists.
What else could be?
cheers
Harold Paulson Sierra Web Design haroldp@sierraweb.com http://www.sierraweb.com VOICE: 775.833.9500 FAX: 810.314.1517
Have either of you checked other logs, like error?
Can either of you run qrunner under something like truss or strace? (on Solaris, truss python ~mailman/cron/qrunner will run qrunner once under system-call tracing, so you can see what it's doing)
Running python -v ~mailman/cron/qrunner might be worth a try too
Harold Paulson wrote:
Rodrigo,
We seem to be having similar problems, and no one is really making any good guesses. One weird thing that I noticed is that if I kill all current qrunners, and remove all locks:
killall qrunner; rm ~mailman/locks/*then a new qrunner will pop up in a minute (from cron). If I watch it in top:
top -qUmailmanIt uses a little CPU for a minute or two, and then slowly dies off to 0% CPU usage. It never does anything that I can see, and runs for a very long time.
Could I have a corrupted msg that is hanging qrunner? The biggest file in qfiles is about 6k, so it's not a size issue...
- HWARNING: 'killall' may work very differently on various unix flavors. Don't do that on a Solaris box!
On Oct 26, 2000 at 12:53, Rodrigo Moya wrote:
I've installed mailman on a RH 6.2 machine. The POP3 server in that machine works perfectly, the messages I send to the mailing lists are logged in the logs/post file. But, no mail goes to the list members.
POP3? SMTP would be what you want to check.
Some guesses...
Check mailman's crontab. The queue runner should be a cron job, AIUI.
it seems ok. The qrunner binary is set to be executed every minute (at least this is what "crontab -u mailman -l" says.
And no /etc/cron.{allow,deny} exists, so mailman should be allowed to run cron jobs.
And "tail -f logs/qrunner" shows 2 log messages every minute. So, everything related to cron seems to work.
But still, list members don't get any message from the lists.
What else could be?
cheers
Harold Paulson Sierra Web Design haroldp@sierraweb.com http://www.sierraweb.com VOICE: 775.833.9500 FAX: 810.314.1517
Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users
Dan,
Thanks much for responding. Any help, even just pointing me in new directions to look, is very much appreciated.
Have either of you checked other logs, like error?
Yes. Nothing gets sent to error, in my case.
Can either of you run qrunner under something like truss or strace? (on Solaris, truss python ~mailman/cron/qrunner will run qrunner once under system-call tracing, so you can see what it's doing)
reading the man page for 'ktrace' now...
Running python -v ~mailman/cron/qrunner might be worth a try too
The first time I tried running python -v, it hung after doing something with "MultiLogger.py", like this:
http://mail.sierraweb.com/test.txtI killed that and tried again a bit later, and it seemed to get farther, with this output:
http://mail.sierraweb.com/test2.txtand it looks hung at that point, or still in the debugger or something? Nothing really jumps out at me in the output, but I'm not a python programmer.
- HHarold Paulson wrote:
Rodrigo,
We seem to be having similar problems, and no one is really making any good guesses. One weird thing that I noticed is that if I kill all current qrunners, and remove all locks:
killall qrunner; rm ~mailman/locks/*then a new qrunner will pop up in a minute (from cron). If I watch it in top:
top -qUmailmanIt uses a little CPU for a minute or two, and then slowly dies off to 0% CPU usage. It never does anything that I can see, and runs for a very long time.
Could I have a corrupted msg that is hanging qrunner? The biggest file in qfiles is about 6k, so it's not a size issue...
- HWARNING: 'killall' may work very differently on various unix flavors. Don't do that on a Solaris box!
On Oct 26, 2000 at 12:53, Rodrigo Moya wrote:
I've installed mailman on a RH 6.2 machine. The POP3 server in that machine works perfectly, the messages I send to the mailing lists are logged in the logs/post file. But, no mail goes to the list members.
POP3? SMTP would be what you want to check.
Some guesses...
Check mailman's crontab. The queue runner should be a cron job, AIUI.
it seems ok. The qrunner binary is set to be executed every minute (at least this is what "crontab -u mailman -l" says.
And no /etc/cron.{allow,deny} exists, so mailman should be allowed to run cron jobs.
And "tail -f logs/qrunner" shows 2 log messages every minute. So, everything related to cron seems to work.
But still, list members don't get any message from the lists.
What else could be?
cheers
Harold Paulson Sierra Web Design haroldp@sierraweb.com http://www.sierraweb.com VOICE: 775.833.9500 FAX: 810.314.1517
Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users
Harold Paulson Sierra Web Design haroldp@sierraweb.com http://www.sierraweb.com VOICE: 775.833.9500 FAX: 810.314.1517
Have either of you checked other logs, like error?
/var/log/maillog shows this:
Oct 26 15:47:00 www sendmail[9366]: PAA09366: to=<mdeza@tesora.com>, delay=00:00:00, mailer=esmtp, stat=queued
several times, one for each member of the list. stat=queued? Does this have something to do with the SMTP config?
/var/log/cron:
mailman (10/27-22:07:00-14628) CMD (/usr/bin/python -S /usr/share/mailman/cron/qrunner) mailman (10/27-22:08:01-14630) CMD (/usr/bin/python -S /usr/share/mailman/cron/qrunner) mailman (10/27-22:09:00-14633) CMD (/usr/bin/python -S /usr/share/mailman/cron/qrunner)
Can either of you run qrunner under something like truss or strace? (on Solaris, truss python ~mailman/cron/qrunner will run qrunner once under system-call tracing, so you can see what it's doing)
Running python -v ~mailman/cron/qrunner might be worth a try too
in my case, it seems normal, isn't it?
=============================== ... [losts of import .... removed] import Mailman.Bouncers.BouncerAPI # precompiled from /usr/share/mailman/Mailman/Bouncers/BouncerAPI.pyc # /usr/share/mailman/Mailman/Logging/MultiLogger.pyc matches /usr/share/mailman/Mailman/Logging/MultiLogger.py import Mailman.Logging.MultiLogger # precompiled from /usr/share/mailman/Mailman/Logging/MultiLogger.pyc # cleanup __main__ # cleanup[1] paths # cleanup[1] cPickle # cleanup[1] math # cleanup[1] crypt # cleanup[1] strop # cleanup[1] site # cleanup[1] copy_reg # cleanup[1] cStringIO # cleanup[1] mimetools # cleanup[1] exceptions # cleanup[1] posix # cleanup[1] signal # cleanup[1] Mailman.Archiver.Archiver # cleanup[1] tempfile # cleanup[1] pcre # cleanup[1] Mailman # cleanup[1] Mailman.MailList # cleanup[1] Mailman.Archiver # cleanup[1] Mailman.Autoresponder # cleanup[1] Mailman.Version # cleanup[1] Mailman.Deliverer # cleanup[1] Mailman.htmlformat # cleanup[1] Mailman.Handlers # cleanup[1] Mailman.Defaults # cleanup[1] Mailman.LockFile # cleanup[1] Mailman.MailCommandHandler # cleanup[1] shutil # cleanup[1] Mailman.Logging # cleanup[1] Mailman.Logging.StampedLogger # cleanup[1] Mailman.GatewayManager # cleanup[1] Mailman.ListAdmin # cleanup[1] Mailman.pythonlib # cleanup[1] Mailman.Logging.MultiLogger # cleanup[1] Mailman.Bouncer # cleanup[1] Mailman.Logging.Logger # cleanup[1] errno # cleanup[1] Mailman.HTMLFormatter # cleanup[1] Mailman.Digester # cleanup[1] Mailman.Bouncers # cleanup[1] Mailman.Logging.Utils # cleanup[1] Mailman.SecurityManager # cleanup[1] Mailman.Mailbox # cleanup[1] Mailman.Logging.Syslog # cleanup[1] socket # cleanup[1] mailbox # cleanup[1] rfc822 # cleanup[1] Mailman.Crypt # cleanup[1] Mailman.Handlers.HandlerAPI # cleanup[1] Mailman.pythonlib.StringIO # cleanup[1] Mailman.Cookie # cleanup[1] Mailman.Message # cleanup[1] Mailman.Bouncers.BouncerAPI # cleanup[1] marshal # cleanup[1] traceback # cleanup[1] Mailman.pythonlib.rfc822 # cleanup[1] sha # cleanup[1] Mailman.Utils # cleanup[1] regsub # cleanup[1] regex # cleanup[1] types # cleanup[1] random # cleanup[1] time # cleanup[1] linecache # cleanup[1] urlparse # cleanup[1] re # cleanup[1] Mailman.Errors # cleanup[1] Mailman.mm_cfg # cleanup[1] whrandom # cleanup[1] string # cleanup[2] os # cleanup[2] os.path # cleanup[2] UserDict # cleanup[2] stat # cleanup[2] posixpath # cleanup sys # cleanup __builtin__ # cleanup ints: 2 unfreed ints in 1 out of 4 blocks # cleanup floats
========================================================
cheers
participants (4)
-
Dan Mick -
Harold Paulson -
Rodrigo Moya -
Satya