Did you run sa-update or install rules manually? 99% sure that is the issue.
Regards,
KAM
On May 1, 2015 2:34:57 PM EDT, Forrest those.li...@gmail.com wrote:
Upgrading from a simple 3.4.0 installation, 3.4.1 refuses to start,
with
this error:
Starting spamd: child process [3723] exited or
Upgrading from a simple 3.4.0 installation, 3.4.1 refuses to start, with
this error:
Starting spamd: child process [3723] exited or timed out without signaling
production of a PID file: exit 255 at /usr/local/perl/bin/spamd line 2986.
Am 01.05.2015 um 20:34 schrieb Forrest:
Upgrading from a simple 3.4.0 installation, 3.4.1 refuses to start, with
this error:
Starting spamd: child process [3723] exited or timed out without signaling
production of a PID file: exit 255 at /usr/local/perl/bin/spamd line 2986.
On 2015-05-01 20:34, Forrest wrote:
Upgrading from a simple 3.4.0 installation, 3.4.1 refuses to start, with
this error:
Starting spamd: child process [3723] exited or timed out without signaling
production of a PID file:
exit 255 at /usr/local/perl/bin/spamd line 2986.
I've seen this
Downgrading to 3.4.0 fixed the problem. So, this is definitely a bug.
Just not certain where it is yet. I don't have time to go digging at
the moment. Anyone else have this?
Am 01.05.2015 um 20:39 schrieb Forrest:
Downgrading to 3.4.0 fixed the problem. So, this is definitely a bug.
Just not certain where it is yet. I don't have time to go digging at
the moment. Anyone else have this?
jesus christ provide informations about your environemt
On 1 May 2015, at 14:34, Forrest wrote:
Upgrading from a simple 3.4.0 installation, 3.4.1 refuses to start,
with this error:
Starting spamd: child process [3723] exited or timed out without
signaling production of a PID file: exit 255 at
/usr/local/perl/bin/spamd line 2986.
