Re: Another MacOS problem Launching after reboot

2007-11-09 Thread Vince Administration


On Nov 9, 2007, at 5:31 PM, Sahil Tandon wrote:



On Nov 9, 2007, at 3:04 PM, Vince Admin Account wrote:


First, policyd-weight is working EXTREMELY well.
I am running it in daemon mode. The only problem is starting it  
automatically after a reboot.
I created a launchd plist  and launchd does start the polw daemon,  
but on one of the machines (the busy one) it does not connect
properly to the DNS server, causing all the DNS lookups to fail.  
Manually restarting polw makes everything work.


To be clear, you are not having this problem on any other OSX  
machine on which you are also starting policyd-weight via launchd?
Ok, we have two servers. One is a test server with almost no traffic,  
except tests, the other our actual server which processes lots of  
messages:  About 30,000/day.
My conjecture, which may be totally wrong, is that on the test server  
there is ample time for the DNS service to start before test messages  
reach it, whereas on the
real server the first child is spawned almost immediately. (Yes logs  
below with my comments separated by  lines). And to complicate,  
or simplify, the problem did occur on the test server the first  two  
times
but now it seems to start correctly. On the main server, it seems to  
have this problem every time.




My conjecture is that MacOS is starting it too early in the boot  
process, before the DNS service is completely established.
So I need to determine either how to have MacOS start it later or  
have policyd-weight check to see if the DNS is working before
starting (and perhaps sleep a bit before continuing -- like  
freshclam)


Starting with a reboot:
-

Nov  6 21:19:23 localhost postfix/master[58]: daemon started --  
version 2.1.5
Nov  6 21:19:38 mail postfix/policyd-weight[318]: policyd-weight  
0.1.14 beta-5 starte
d and daemonized. conf:/usr/local/etc/policyd-weight.conf; GID:82 82  
EGID:82 82 UID:82 EUID:82; taint mode: 0\n

Nov  6 21:19:38 mail postfix/policyd-weight[319]: cache spawned\n
Nov  6 21:19:39 mail postfix/qmgr[80]: 1C40E2098337:  
from=<[EMAIL PROTECTED]>, size=43

78, nrcpt=1 (queue active)
Nov  6 21:19:39 mail postfix/qmgr[80]: 4D38D20982CF:  
from=<[EMAIL PROTECTED]

om>, size=1116, nrcpt=1 (queue active)
Nov  6 21:19:39 mail postfix/smtpd[329]: connect from  
mail2.uits.uconn.edu[137.99.25.

204]
Nov  6 21:19:39 mail postfix/qmgr[80]: 651AE20982D3:  
from=<[EMAIL PROTECTED]>, size

=12284, nrcpt=1 (queue active)
Nov  6 21:19:39 mail postfix/smtpd[282]: warning: 190.156.81.221:  
hostname dynamic-ip

-19015681221.cable.net.co verification failed: Host not found
Nov  6 21:19:39 mail postfix/smtpd[282]: connect from unknown 
[190.156.81.221]
Nov  6 21:19:39 mail postfix/smtpd[282]: lost connection after  
CONNECT from unknown[1

90.156.81.221]
Nov  6 21:19:39 mail postfix/smtpd[282]: disconnect from unknown 
[190.156.81.221]
Nov  6 21:19:39 mail postfix/smtpd[282]: connect from  
125-24-140-137.adsl.totbb.net[1

25.24.140.137]
Nov  6 21:19:39 mail postfix/policyd-weight[333]: child: spawned\n
Nov  6 21:19:39 mail postfix/qmgr[80]: 8FE8720982F9:  
from=<[EMAIL PROTECTED]>, siz

e=77940, nrcpt=1 (queue active)
#
Now the first call to policyd-weight gives the message:
#
Nov  6 21:19:39 mail postfix/policyd-weight[333]: decided  
action=PREPEND X-policyd-we
ight: passed - too many local DNS-errors in bl.spamcop.net lookups;  
delay: 0s\n

#
and every other call gives the same message with different lookups:  
(only policyd-weight messages included here:)


Nov  6 21:19:40 mail postfix/policyd-weight[333]: decided  
action=DUNNO multirecipient-mail - already accepted by previous  
query; delay: 0s\n
Nov  6 21:19:50 mail postfix/policyd-weight[333]: decided  
action=PREPEND X-policyd-weight: passed - too many local DNS-errors  
in bl.spamcop.net lookups; delay: 0s\n
Nov  6 21:19:52 mail postfix/policyd-weight[333]: decided  
action=PREPEND X-policyd-weight: passed - too many local DNS-errors  
in bl.spamcop.net lookups; delay: 0s\n
Nov  6 21:20:44 mail postfix/policyd-weight[333]: decided  
action=PREPEND X-policyd-weight: passed - too many local DNS-errors  
in ix.dnsbl.manitu.net lookups; delay: 0s\n
Nov  6 21:20:46 mail postfix/policyd-weight[333]: decided  
action=DUNNO NULL (<>) Sender; delay: 0s\n
Nov  6 21:24:38 mail postfix/policyd-weight[333]: decided  
action=PREPEND X-policyd-weight: passed - too many local DNS-errors  
in ix.dnsbl.manitu.net lookups; delay: 0s\n
Nov  6 21:25:21 mail postfix/policyd-weight[333]: decided  
action=PREPEND X-policyd-weight: passed - too many local DNS-errors  
in ix.dnsbl.manitu.net lookups; delay: 0s\n

Nov  6 21:27:42 mail postfix/policyd-weight[816]: child: spawned\n
Nov  6 21:27:42 mail postfix/policyd-weight[816]: decided  
action=PREPEND X-policyd-weight: passed - too many local DNS-errors  
in bl.spamcop.net lookups; delay: 0s\n
Nov  6 21:28:15 mail postfix/policyd-weight[333]: decided  
action=PREPEND X-policyd-weight: passed - too many local DNS-error

Re: Another MacOS problem Launching after reboot

2007-11-09 Thread Sahil Tandon


On Nov 9, 2007, at 3:04 PM, Vince Admin Account wrote:


First, policyd-weight is working EXTREMELY well.
I am running it in daemon mode. The only problem is starting it  
automatically after a reboot.
I created a launchd plist  and launchd does start the polw daemon,  
but on one of the machines (the busy one) it does not connect
properly to the DNS server, causing all the DNS lookups to fail.  
Manually restarting polw makes everything work.


To be clear, you are not having this problem on any other OSX machine  
on which you are also starting policyd-weight via launchd?


My conjecture is that MacOS is starting it too early in the boot  
process, before the DNS service is completely established.
So I need to determine either how to have MacOS start it later or  
have policyd-weight check to see if the DNS is working before

starting (and perhaps sleep a bit before continuing -- like freshclam)


Unfortunately, there does not appear to be any way to feed  
dependencies to launchd -- Apple considers this a feature.  But I do  
not know if your problem stems from boot order or something specific  
to your machine -- especially if everything is working fine on your  
other OSX boxes.



Can anyone help?


Show logs.


Policyd-weight Mailinglist - http://www.policyd-weight.org/


Re: Another MacOS problem Launching after reboot

2007-11-09 Thread Robert Felber
On Fri, Nov 09, 2007 at 03:04:01PM -0500, Vince Admin Account wrote:
> First, policyd-weight is working EXTREMELY well.
> I am running it in daemon mode. The only problem is starting it automatically 
> after a reboot.
> I created a launchd plist  and launchd does start the polw daemon, but on one 
> of the machines (the busy one) it does not 
> connect
> properly to the DNS server, causing all the DNS lookups to fail. Manually 
> restarting polw makes everything work.

grep '(warn|err|main)' /var/log/maillog does give what?
(also, do you see other signs of unusual log activity aside of warn, err?)


-- 
Robert Felber (PGP: 896CF30B)
Munich, Germany


Policyd-weight Mailinglist - http://www.policyd-weight.org/