Atomicorp

@chrismcb did you restart the box too?

Hi Mike, Thanks for the background, looking at the docs you've pointed me to, I can see a couple of errors, the instructions refer to: service stop iptables which as far as I am concerned on Centos here should be service iptables stop Same for the service asl-firewall equivalents. Anyway stopping ip...

I have followed the instructions at: https://www.atomicorp.com/wiki/index.php/ASL_firewall#Per_Port_ACLs to allow certain IPs to connect to MySQL on 3306 but I am still unable to make connections to MySQL from the allowed IPs The firewall contains rules for the IPs listed in the file /etc/asl/firewa...

Also experiencing this on two servers, error in ossec.log is: 2014/01/07 09:17:33 ossec-testrule: INFO: Reading decoder file etc/decoder.xml. 2014/01/07 09:17:33 ossec-testrule: INFO: Reading decoder file etc/decoders.d/01-asl-decoder.xml. 2014/01/07 09:17:33 ossec-testrule: INFO: Reading decoder fi...

Thanks,

breun+1

Just wanted to check, I've disabled rootcheck using the process described above several times now. Is it not permanent?

That sounds like the I/O bus may just be overloaded (rootcheck is doing reads). What kind of RAID is this? (RAID 5, RAID 1, RAID 10) And what kind of I/O does the RAID normally experience? Thanks for the detailed reply, I'll not clog up the forum with too much unnecessary detail - I've added lspci ...

Drive has checked out ok, and RAID is all running correctly according to DC engineer.

Still getting high load and unresponsive services directly related to rootcheck, am going to open a ticket I think as this needs proper investigation.

I have a server with a failing drive which seems to be causing problems when the ossec rootcheck process kicks in. Load goes up and services start becoming inaccessible after about an hour. I put this down to some of the checks that rootcheck is running and under normal circumstances would be quite ...

I've just picked a nasty scab having forgotten about this qmail-scanner issue completely. Stupid, stupid idiot that I am. I have three servers all now running 11.0.9 with all the latest MU applied. On the first server I noticed that qmail-scanner wasn't running as I'd received a few odd phishing mai...

Yup!

Thank breun, I know this was a requirement for 5.3 but it seems strange that the setting is left out of the Plesk php.ini if it is so important, unless they suppress this in their own use of the binary? Just wanted to see if anyone had encountered similar or if it would cause problems (or be overwri...

Just had a wierd issue on a server upgraded from 9.5.4 to 11.0.9 recently. Am using Atomic Scanner which runs a job overnight to calculate the amount of spam and ham etc with /var/asl/bin/data-generate.php and due to the date.timezone setting missing from the Plesk PHP config this cronjob generated ...

Right so yes it looks like an automatically installed MU triggered this whole mess. I did manage to fix it with the excellent advice on this thread. Specifically making the component switch to postfix and then back to qmail. Reinstalling qmail-scanner this morning has resolved the problem (aside fro...

Just been bitten by this bug but it wasn't after an upgrade or anything. This machine was installed with 10.4. The machine is running ASL, spamdyke and spamassassin. One of the users reported a higher amount of spam than normal getting through. I thought qmail-scanner was running but looking at one ...