If you restart apache it should make sites go offline for a split second it will likely not even be noticed. On occasion this is needed, but you can also restart apache gracefully which makes sure active tasks get completed before it restarts itself. So yes it will effect things, but unless apache ...
Thanks for your reply. On the version of Plesk I am using (10.1.1) the Firewall can only be managed through the Container and it is only possible to edit a number of predefined items, I cannot create a new rule for Port 3306. As I said in my previous post, up until the point I enabled the firewall ...
I was a bit surprised to find qmail-scanner related eroor messages in Apache's /var/log/httpd/error_log getservbyname failed for tcp at /var/qmail/bin/qmail-scanner-queue.pl line 2985 udp connect: nobody listening at /var/qmail/bin/qmail-scanner-queue.pl line 2985 Note that these messages are not t...
We recommend mail server administrators to *not* use the SORBS RBL for black listing. We also suggest an update to the ART qmail-scanner/SpamAssassin packages that disables the RCVD_IN_SORBS_* tests.
This is what ClamAV detects (looked up in the quarantine folder): tail <quarantinedmessagefile> ###################### LogWatch End ######################### *** Qmail-Scanner Quarantine Envelope Details Begin *** X-Qmail-Scanner-Mail-From: "root@<hostname>" via <hostname> X-Qmail-Scanner-...
We use monitoring scripts that periodically perform some simple greps with line counts in the mail logs. In our integrated monitoring setup (using Zenoss) we have set up RRD graphs, thresholds and notifications.
We're seeing legit messages getting blocked by ClamAV because of a hit on ASL.MalwareBlacklist. Using the ASL.MalwareBlacklist rules ClamAV will block messages matching a regexp on the message body containing a URI with an IP address or domain from the ASL.MalwareBlacklist database. Because of that,...
How do I temporarily disable qmail-scanner? This is because of the "clamdscan: corrupt or unknown clamd scanner error or memory/resource/perms problem - exit status 512/2" error I'm getting, while unable to fix it with "chown qscand:qscand /var/log/clamav/clamd.log; qmail-scanner-reco...
MySQL 5 from the centosplus channel should be running perfectly fine on your CentOS 4 box with Plesk 8.1. That is, I see no reason why it wouldn't since both Plesk and CentOS support the upgrade.