perl-FCGI, perl-CGI::FAST

[faris]

I'm trying to install smokeping on a client's Plesk-based server.
It requires a large number of helper apps and modules be installed, along with some perl modules including perl-FCGI and perl-CGI::FAST (plus perl-CGI which is already installed, of course)

Is there any danger of this CGI/CGI::FAST stuff screwing up Plesk's CGI/php-fcgi stuff? As far as I can make out, it won't. But I thought it would be sensible to ask here in case anybody knows better.

[prupert]

http://repos.jethrocarr.com offers a yum channel with SmokePing packaged including dependencies if combined with EPEL.

Code: Select all

# download repo file (for EL6)
wget http://repos.jethrocarr.com/config/centos/6/amberdms-c6-public.repo

# enable only the -os repo, others can be disabled
vim amberdms-c6-public.repo

# move to your yum.repos.d
mv amberdms-c6-public.repo /etc/yum.repos.d/

# Install the SmokePing package (and perl-FCGI for the web interface)
yum install smokeping perl-FCGI

# configure the hell out of it
# see http://oss.oetiker.ch/smokeping/doc/smokeping_examples.en.html
vim /etc/smokeping/config

# secure the web interface (restrict on IP and/or add password auth)
vim /etc/httpd/conf.d/smokeping.conf

# Start the beast
service smokeping start

# also automatically on boot
chkconfig smokeping on

We use separate systems for SmokePing installations. I never mix things like these on Plesk hosting servers and I wouldn't recommend it, but it might work. Use at your own risk, YMMV, yadayada...

Tip: if you've got your master running, you can invest some time into setting up a second machine with SmokePing in a different network as 'slave', see http://oss.oetiker.ch/smokeping/doc/smo ... ve.en.html

[faris]

Thank you. That looks like a potential time saver. But as you say, should be on a separate server.

It is when it says thing like "and perl-FCGI for the web interface" that my warning bells start ringing in terms of potential Plesk problems. Plesk already provides and configures Perl-CGI, and now we are somehow, in some mysterious and unknown way, adding FCGI. Ugh!

The install script for the smokeping source code allows any missing modules to be compiled via CPAN and *seems* to put them in a specific directory, out of the normal Perl path. I'm wondering if that's actually the safest option.

Unfortunately there's only one way to find out (without going to the trouble of creating a test VPS), and it isn't really reversible!