Robert Felber schrieb:
On Tue, Jun 12, 2007 at 01:29:17PM +0200, Til Obes wrote:
Robert Felber schrieb:
First, grep your Logs for errors, warnings related to policyd-weight.
Start:
policyd-weight 0.1.14 beta-5 started and daemonized. conf:/etc/postfix/policyd-weight.conf; GID:114 114
EGID:114 114 UID:106 EUID:106; taint mode: 0
Timestamp? PIDs?
Jun 6 18:25:06 mailhost postfix/policyd-weight[8504]: policyd-weight 0.1.14
beta-5 started and daemonized. conf:/etc/postfix/policyd-weight.conf;
GID:114 114 EGID:114 114 UID:106 EUID:106; taint mode: 0
I only found some warnings:
warning: master: could not open policyd-weight.conf: No such file or directory
warning: child: could not open policyd-weight.conf: No such file or directory
Timestamp? PIDs?
Shouldn't lead to a crash, though. I expect it to be not related to the
startup line.
Forget them, it seems they were from testing today ....
Old logs dont show them ....
Don't you handle the -f parameter on all positions correctly?
-f is only handled at one position. -f sets global $conf (pathname).
Are there any other signs of troubles, like a mass of "child spawned" short
before the master crashed? The only way the master can crash is, that it
raises perl errors, which are logged. If they are not logged then something
else is deeply messed up (the master is in a while(1) loop, thus cannot exit
quietly, only on error).
Are you using daemon-tools or something else?
No i'm just starting it from commandline.
And i dont see any related error msgs in syslog :(
It just dies and a child is left.
So i wrote a script, which checks it, but thats not the final solution ...
Regards Til
____________________________________________________________
Policyd-weight Mailinglist - http://www.policyd-weight.org/
