| 1 |
Probably a stale pid file. |
| 2 |
|
| 3 |
1) Stop the daemon, disable any cron jobs and access to the website |
| 4 |
2) Check <mailmanroot>/locks/, it should be empty. If not... |
| 5 |
3) delete all files, except the .keep. |
| 6 |
4) Re-enable cron jobs and website access, restart the daemon. |
| 7 |
|
| 8 |
jbw |
| 9 |
|
| 10 |
Christian Parpart wrote: |
| 11 |
|
| 12 |
> Joby Walker said: |
| 13 |
> |
| 14 |
>>Christian, |
| 15 |
>> |
| 16 |
>>Have you tried manually running check_perms? Have you checked the |
| 17 |
>>mailman logs? |
| 18 |
> |
| 19 |
> |
| 20 |
> I've invoked check_perms several times. even check_db. |
| 21 |
> |
| 22 |
> |
| 23 |
>>The mailman logs are pretty good, I usually find some |
| 24 |
>>important info on why mailman misbehaves for me. |
| 25 |
> |
| 26 |
> |
| 27 |
> in file /usr/local/logs/qrunner: |
| 28 |
> [...] |
| 29 |
> Jun 21 17:48:10 2004 (3953) ArchRunner qrunner started. |
| 30 |
> Jun 21 17:48:10 2004 (3954) BounceRunner qrunner started. |
| 31 |
> Jun 21 17:48:10 2004 (3956) IncomingRunner qrunner started. |
| 32 |
> Jun 21 17:48:10 2004 (3957) NewsRunner qrunner started. |
| 33 |
> Jun 21 17:48:10 2004 (3955) CommandRunner qrunner started. |
| 34 |
> Jun 21 17:48:11 2004 (3959) VirginRunner qrunner started. |
| 35 |
> Jun 21 17:48:11 2004 (3960) RetryRunner qrunner started. |
| 36 |
> Jun 21 17:48:11 2004 (3958) OutgoingRunner qrunner started. |
| 37 |
> Jun 21 17:48:11 2004 (3951) Master qrunner detected subprocess exit |
| 38 |
> (pid: 3958, sig: 11, sts: None, class: OutgoingRunner, slice: 1/1) |
| 39 |
> [restarting] |
| 40 |
> [...lots.of.repititions...] |
| 41 |
> Jun 21 17:48:13 2004 (3972) OutgoingRunner qrunner started. |
| 42 |
> Jun 21 17:48:14 2004 (3951) Master qrunner detected subprocess exit |
| 43 |
> (pid: 3972, sig: 11, sts: None, class: OutgoingRunner, slice: 1/1) |
| 44 |
> [restarting] |
| 45 |
> Jun 21 17:48:14 2004 (3951) Qrunner OutgoingRunner reached maximum restart |
| 46 |
> limit of 10, not restarting. |
| 47 |
> |
| 48 |
> But which so called 'subprocess' exited? |
| 49 |
> And - more important - why? |
| 50 |
> |
| 51 |
> /usr/local/mailman/log/error seems untouched since Jun 10 20:05:01 2004. |
| 52 |
> |
| 53 |
> It must be anything regarding to the SMTP sending mechanism in / |
| 54 |
> or related to mailman. But sending mails via squirrelmail works |
| 55 |
> fine, so this (I guess) can't be really the reason. |
| 56 |
> |
| 57 |
> Thanks in advance, |
| 58 |
> Christian Parpart. |
| 59 |
> |
| 60 |
> |
| 61 |
> |
| 62 |
>>Christian Parpart wrote: |
| 63 |
>> |
| 64 |
>>>Hi all, |
| 65 |
>>> |
| 66 |
>>>I recently updated my postfix and mailman resulting into some mailman |
| 67 |
>>>issues, |
| 68 |
>>>that is, I can send mails to the mailinglists it serves, they get |
| 69 |
>>>archived, |
| 70 |
>>>but they won't be sent out to the subscribers. Why? |
| 71 |
>>> |
| 72 |
>>>I already look into postfix' main.cf and the Mailman/Default.py for some |
| 73 |
>>>changes, but nothing special found. |
| 74 |
>>> |
| 75 |
>>>Also, the mailman ebuild seems to have some problems, it creates the |
| 76 |
>>>.keep |
| 77 |
>>>files, and then executes bin/check_perms which interprets even those |
| 78 |
>>>files as |
| 79 |
>>>directories what - of course - results into an error while emerging. |
| 80 |
>>> |
| 81 |
>>>I inserted an |
| 82 |
>>> |
| 83 |
>>>find . -type d -name .keep -exec rm -f {} \; |
| 84 |
>>> |
| 85 |
>>>above the check_perms command line in this ebuild. |
| 86 |
>>> |
| 87 |
>>>Thanks in advance, |
| 88 |
>>>Christian Parpart. |
| 89 |
>> |
| 90 |
>> |
| 91 |
> |
| 92 |
> |
Archives