> btw: how does postgrey crash? Would be helpful to have the error here > for reference.
I don't have much data on that. Because of this problem, we now restart postgrey after the logrotation. However this doesn't work out good in all situations, sometimes a crashed(?) postgrey instance remains active, resulting in: mail.warn.0:Dec 11 06:26:04 mailserver postgrey[29576]: 2007/12/11-06:26:02 Pid_file already exists for running process (29577)... aborting at line 261 in file /usr/share/perl5/Net/Server.pm mail.warn.0:Dec 16 06:26:17 mailserver postgrey[5804]: 2007/12/16-06:26:02 Can't connect to TCP port 60000 on 127.0.0.1 [Address already in use] at line 88 in file /usr/share/perl5/Net/Server/Proto/TCP.pm mail.warn.0:Dec 16 06:26:18 mailserver postgrey[5809]: 2007/12/16-06:26:05 Can't connect to TCP port 60000 on 127.0.0.1 [Address already in use] at line 88 in file /usr/share/perl5/Net/Server/Proto/TCP.pm The restart is executed using /etc/init.d/postgres stop; sleep 5; /etc/init.d/postgres start; -- crashes when syslog is not available https://bugs.launchpad.net/bugs/69895 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
