Atomicorp

Yes, I managed to figure that out. Unfortunately, the PCI scanning folks are not understanding that. I have to go item by item that failed and document each version installed and explain to them that it is a false positive and why because they can't see the patches / backports. This is absurd. If t...

I'm seriously curious what kind of software would still need this. Do you run something custom that you can't touch? Fact 1: Some clients don't know the requirements for the code they're running. Fact 2: Some clients are running code that hasn't been updated in years. Fact 3: Some servers are runni...

How is an open transparent conversation of exactly the timeframe to support it "not clear". In the sense that there is no determined timeframe yet, as far as I know. Please don't mistake my comments for bashing the Atomic PHP packages or something, we use them on a lot of servers and we l...

Well, we went with the Atomic 5.3 because I prefer them and in another post Scott reassured us that he'd keep his 5.3 going for as long as possible/practical (as long as there was demand for it of course) with backports etc. I'd have stuck to the EL6 versions otherwise. Picking a date out of the ai...

faris wrote:I want 5.3 as long as possible.

You could consider using EL5's php53* or EL6's php* RPM packages. EL5 is supported until March 2017, but sadly a lot of extensions are not packaged for php53*. EL6 is supported until November 2020.

A temporary workaround that you could cron is:
This command removes the useless zero-byte files, but doesn't really fix the log rotation.

Still no solution for the logrotate bug in atop. It has different manifestations on EL5 and EL6 by the way. On EL5 you get weird christmas tree of zero-byte files: # ls -l /var/log/atop total 9176 -rw------- 1 root root 0 Dec 30 04:26 atop_20121125 -rw------- 1 root root 0 Dec 30 04:26 atop_20121125...

KirkM wrote:Forgive me if I don't hold my breath waiting for Parallels to do that any time soon.

Have you reported this incompatibility with Plesk and a OS they support to Parallels? In my experience they do tend to solve these things.

We've reverted to qmail-scanner-2.08-5, because 2.10-8 seems too buggy. Apart from the issues mentioned above we've also had problems with fresh installations of 2.10-8 not generating qmail-scanner-queue.pl at all.

Where is that spf2 package from? I don't find spf2 in the repositories we use on CentOS 6.

They should be blocked in the firewall.

I opened a ticket with Pyzor to ask about the default timeout: https://sourceforge.net/apps/trac/pyzor/ticket/165

Sounds like you encountered the same issue as mist_firefly: https://www.atomicorp.com/forum/viewtop ... =12&t=6461

Sounds like this might fix your problem: http://www.atomicorp.com/forum/viewtopi ... 212#p32212

I don't think the updates are directly causing your problem, but we don't know yet for sure. I'd start by determining what your problem actually is. Is the server under high load? If so, can you find out what process is causing high load?