FreeBSD port dropping plugin support

firewalz · Post by **firewalz** » Mon Dec 31, 2007 9:34 am

The FreeBSD port has been updated to version 8.7a, however they have dropped support for the plugin architecture. This will seriously hose my prod systems, plugins are one of the resons I use Cacti. I guess Ill have to 1) not upgrade, 2) recompile and restore everything by hand, or 3) switch to something else like Cricket or Nagios

from /usr/ports/UPDATING...

"Plugin support is dropped again and will not revive anymore in the port.
A reason for that is the patch is unofficial and there are long time lags
between a new cacti version released and time when the patch is
adapted."

N3NCY · Post by **N3NCY** » Mon Dec 31, 2007 1:31 pm

I have been using FreeBSD for Cacti for 2+ years now.
The funny thing is that I only realized that there was a port about a month ago.
I have no intentions of ever using the port or package since the source code of Cacti + Plugin Architecture + Spine (Cactid Poller) work on FreeBSD easily.

Howie · Post by **Howie** » Mon Dec 31, 2007 4:03 pm

firewalz wrote:The FreeBSD port has been updated to version 8.7a, however they have dropped support for the plugin architecture. This will seriously hose my prod systems, plugins are one of the resons I use Cacti. I guess Ill have to 1) not upgrade, 2) recompile and restore everything by hand, or 3) switch to something else like Cricket or Nagios

There *is* no recompiling!

You can install apache, mysqld, rrdtool and net-snmp from ports, which are the painful parts. Installing Cacti itself is 5 minutes: download, unzip, edit config.php, alter permissions for rra/ log/

For PIA, copy the appropriate files-0.8.x folder from the pia download over the top of it all.

firewalz · Post by **firewalz** » Mon Dec 31, 2007 10:03 pm

I’m not sure were the default install lives, but the ports tend to sometimes place things in different directories than if you manually install. Keeping the dependencies up to date is not a big deal, I just not sure if Ill need to tar the current dir up, install the latest version, than copy the appropriate files back to the new location, or if it will use the existing dir and keep the historic info, etc.

As far as using ports vs. manually. I know there are pluses and minuses for both, but Ill save that debate for another forum:)...I just wanted folks who do rely on ports and use cacti to know, I think it’s a big deal and PIA is what makes Cacti really convenient and useful.

Howie · Post by **Howie** » Tue Jan 01, 2008 8:13 am

What I did in the same situation (I wanted to track 0.8.7 before it was released), was tar up /usr/local/share/cacti (which is where the port installs), then pkg_deinstall cacti, then untar it back into the same place. From memory, all the apache config stays there, because you put it in by hand, as does the mysql database. It never hurts to do a backup and mysqldump first though of course

At that stage, you have the current cacti untethered from ports, and you can upgrade according to the source-based instructions in the cacti docs. It's possible to do in between poller cycles if you have 5 minute polling and you have read the instructions carefully.

N3NCY · Post by **N3NCY** » Wed Jan 02, 2008 7:59 pm

It's possible to do in between poller cycles

Howie: You are truly a maniac!

Your title in the forum is:
"Cacti Guru User"

It should say:
"Cacti Maniac!"

I like your style!

Howie · Post by **Howie** » Wed Jan 02, 2008 8:15 pm

N3NCY wrote:
It's possible to do in between poller cycles
Howie: You are truly a maniac!

Your title in the forum is:
"Cacti Guru User"

It should say:
"Cacti Maniac!"

I like your style!

LOL! I didn't mean without stopping the poller cron job - bad things could happen then. Just that you can usually do it losing only one, or even no polls. As long as you trust your backups (just in case), it can be a single command-line: move old cacti out of the way, unpack new one, copy old config.php, move old rra, chown, done. Using mv rather than cp makes it near-enough instant.

zgamer · Post by **zgamer** » Thu Jan 17, 2008 8:49 pm

Been using FreeBSD in a vmware install and have been downloading the source to compile when needing a newer version. I'm still sticking with the 0.8.6 tree for the production system though.

eecue · Post by **eecue** » Sun Jun 22, 2008 5:09 pm

At some point it would be nice if cacti would add the plugin architecture to the codebase. For many years I have used a combination of ports and manual installs for various apps. Recently I've been trying to install everything via ports. The main benefit for this is that I run portaudit nightly and I instantly know if any of my installed software is vulnerable to exploit.

So yeah, if the plugin architecture could be introduced into the tree that would be awesome.

Post by **TheWitness** » Fri Aug 21, 2009 7:16 am

We have this planned. We simply have to get it out. We are coordinating better now. We all have full time jobs...

TheWitness

Sirup · Post by **Sirup** » Mon May 10, 2010 8:34 am

TheWitness wrote:We have this planned. We simply have to get it out. We are coordinating better now. We all have full time jobs...

TheWitness

Still would be great, if the PIA would be part of cacti.

Ran into the same problem today, upgraded cacti from ports (0.8.7e4 to 0.8.7.e5) and plugin configuration was gone...

Post by **TheWitness** » Mon May 10, 2010 12:00 pm

We discussed this in the developers meeting this weekend and there was one pivotal holdout.

TheWitness

Sirup · Post by **Sirup** » Tue May 11, 2010 1:43 am

Sounds nice, thanks!

Cacti

FreeBSD port dropping plugin support

FreeBSD port dropping plugin support

Re: FreeBSD port dropping plugin support

Who is online