I need to install VSE for Linux 1.9.0 for our customer on Ubuntu 12.04.02 x86 servers. Since the OS is a requirement from our side, we can't switch it and also can't choose the Virus Scanner because that is a requirement from our customer.
I did the following steps multiple times on a fresh installed (and upgraded) server (12.04.03) and on our test systems (12.04.02).
I installed the VSE 220.127.116.11822 eval version as it's described in the installation manual.
No major issues or error messages, except of the compiling failure of the onaccess scanner, but that isn't that big of a deal, and will be solved.
The biggest problem appears after installing software packages that need libraries of some sort.
The first problems started when we tried to update our software on the test system and it crashed the system completely. You can't execute any command after that or even restart the server. The OS didn't boot after that.
I created a VM with a fresh Ubuntu Installation, installed nothing but SSHd and did the whole thing again.
After installation of the gnome desktop (just for testing purpose!!!!) the same problems appeared again and the system was dead.
Soooo... I'm pretty helpless at the moment and I can't wrap my head around the fact that McAfee VSE destroys any Ubuntu 12.04 installation by default.
If anyone can help me with that issue, that'll be great!
Message was edited by: david.wingcon on 9/4/13 5:04:03 AM CDT
In the manual there a bit about copying pam_unix.so and pam_nologin.so to a folder called pam32lib
Did you do these steps?
Sorry ignore that question. I've just re-read your post and that step is for 64bit systems.
Message was edited by: Tristan on 04/09/13 11:35:19 IST
That is only for 64bit (x86_64) installations. At least that's what the description says.
Before you begin
If you are installing VirusScan Enterprise for Linux on a 64‐bit Ubuntu system, ensure that
you perform these steps before installation:
I did a normal 32bit (i686) installation.
I took to long to answer. It stays, no harm done.
Message was edited by: david.wingcon on 9/4/13 6:51:21 AM CDT
Sooo, after some testing I found a rather nasty workaround for this issue.
Activate McAfee again
Why on earth does someone develope something f*cked up like that?