Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After looking into how to prepare my LAMP server for production use, one of the things I saw that was suggested was to use Bastille Hardening. It seems that v3.2.1 is not functioning properly and is missing an API folder. The errors that I receive are the same as described in this link:

This is the error that starts the problems:

Error message: Can't locate Bastille/ in @INC

Judging by the bugs reported on SF, it's a common problem. Does anyone know a fix to this or are there some alternatives that I can use to help secure my server for production use? Would using an earlier version help?

I was also planning on running the following after Bastille:

share|improve this question
how did you install Bastille? Is it 64 or 32 bit CentOS? – warren Apr 5 '11 at 18:05
CentOS i386 15char – Nick Apr 5 '11 at 22:43
up vote 0 down vote accepted

Yeah, the RPM seems to be missing some needed .pm files - I was able to find the file and edit the bastille script to have the right "use lib" statements to get it, but then it failed to find some other necessary bits and pieces.

The source tarball, from here seems to work though. I'm on a Centos 5.5 x86_64 system.

share|improve this answer
Will this work on Centos 5.5 i386? – Nick Apr 5 '11 at 22:47
I don't have a means to test that, but I expect it will. – malcolmpdx Apr 5 '11 at 23:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.