Installing Bugzilla on a CentOS cPanel VPS

This article is designed to hopefully assist someone not have to go over the same troubles as I experienced installing the latest stable Bugzilla onto my cPanel server. To say it gave me a headache is an understatement.

To begin with everything went smoothly. It was all good. I followed the instructions for the Bugzilla installation, and ran the various perl scripts, which said I needed to install some additional modules to make Bugzilla work. That was no problem, so I thought, because I had CPAN installed and set up.

Most of the modules went on OK, and everything looked good. But then I started receiving e-mails from users of another site written in perl that resides on the server. They were getting Internal Server Errors galore. Premature end of script headers. Oh joy.

So I went on the hunt for what could be going on. I ran the perl script manually for the site that was complaining. It borked with some file or other that couldn’t be found in the @INC path. That’s odd, because it was working before I tried installing the JSON::RPC module from CPAN. I ran the Bugzilla ‘’ script again and now that borked with files missing from @INC.

What the?

I tried using CPAN to install the missing modules that the script was now complaining about. One went on, then CPAN itself stopped working! Now I was really confused.

I did some googling around, discovered some fairly useful information to put things back and got CPAN up and running again. I can’t give specifics of this because it really depends on what you did prior to getting here as to what you’ll need to look for. Hopefully though you read this BEFORE you bork your CPAN install 🙂

Long story short, I have two Perl binaries on my system, compiled with different @INC paths.


I discovered it quite by accident. One was in /usr/bin/perl – the other was /usr/local/bin/perl. Running from the command line was using /usr/local/bin/perl, but web scripts (and the script) were coded to use /usr/bin/perl.

At this point in time I have renamed the /usr/bin/perl version to /usr/bin/perl.sav and softlinked to /usr/local/bin/perl since all my CPANing and tweaking was done with the /usr/local/bin/perl variant (which used a /usr/local/ prefix to its @INC path).

This seems to have fixed Bugzilla, and kept the other site happy too. I’ve yet to test whether it’s broken cPanel now though!

Author: Steve Brown

Steve is a paramedic in Victoria, Australia who is also an ex-IT Consultant and currently uses all manner of MacOS software in his everyday life. So he usually tends to write about his experiences with that. But sometimes he'll write about medical, political or other stuff that might (or might not!) be of interest

1 thought on “Installing Bugzilla on a CentOS cPanel VPS”

  1. Just a quick NOOB question:

    Exactly when/where do you configure perl’s location in Bugzilla?

    I’m going to try and install Bugzilla for the first time on my own VPS. Hope I don’t mess things up too bad 🙂

    PS: Thanks for this tip (I’m sure it will help)

Leave a Reply

Your email address will not be published. Required fields are marked *