Spamd error - 127.0.0.1:783 already in use

Follow-up

Well. It's been some time now and no idea's or help from anyone.

I have since found that spamd was appearing as perl, so I had to Kill perl before I could properly start Spamd.

But I still have problems with Spamd stalling at boot-up and now with our data centre suffering from UPS failures my server goes off-line and I can't get it back up until I explain to them that they need to kill spamd to allow it to startup properly.
 
Well perl itself doesn't run. You may have a perl script that runs at boot time. You need to examine what starts at boot time.

and I can't get it back up until I explain to them that they need to kill spamd to allow it to startup properly.

That should not prevent your server from starting and at least allowing you to connect via ssh. Make sure sshd starts right after iptables and the network. This should allow you to at least ssh in.
 
Back
Top