ZenPacks : Barracuda Spam Appliances : Comments

RE: Barracuda Spam Appliances

community@zenoss.org — Tue, 15 Sep 2009 14:01:55 GMT

John, there are problems with this Zenpack. I am running Zenoss 2.4.5 (stack-installed) on CentOS 5.2. When I try to test an error message that the path ending in "check_cuda" can't be found. If you modify the path to be:

"/usr/bin/perl $$ZENHOME/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda -H $devname"

then you get farther:

Executing command

/usr/bin/perl $ZENHOME/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda -H mx4.heatseeker.com

against mx4.heatseeker.com

Can't locate utils.pm in @INC (@INC contains: /usr/local/zenoss/zenoss/libexec /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda line 7.

BEGIN failed--compilation aborted at /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda line 7.

DONE in 0 seconds

What is utils.pm and how to I add it?

What are the correct paths for:

"zZenPacksPBnJSolutionsBarracudaWatcherlibexec"
check_cuda's command template,
- currently: "/usr/bin/perl $$ZENHOME/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda -H $devname"
- default: "/usr/bin/perl $$ZENHOME/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda -H $devname

Matt

RE: Barracuda Spam Appliances

community@zenoss.org — Tue, 15 Sep 2009 15:34:03 GMT

Matt,

I am not the author of this ZenPack, merely the guy who posted it. Paul Winkeler is the one who wrote this ZenPack for us. Best to post your questions in our ZenPacks Forum where you'll find many people willing to help. zenoss-zenpacks

RE: Barracuda Spam Appliances

community@zenoss.org — Tue, 22 Sep 2009 19:10:09 GMT

This zenpack makes refrences to several invalid paths. I changed the path like you did, and copied utils.pm to the proper directory. I then completely restarted Zenoss, binded the Barracuda template to my \devices\network\barracuda class, then remodeled the devices, and I am successfully using the plug in on my INBOUND devices.

RE: Barracuda Spam Appliances

community@zenoss.org — Mon, 12 Jul 2010 13:13:26 GMT

Also, it looks like this will not work with the new 4.0 firmwares.

RE: Barracuda Spam Appliances

community@zenoss.org — Mon, 12 Jul 2010 20:40:24 GMT

This plugin is still working for 4.x firmware. We use the 400 types so no idea if there are any changes for the lower ranges. The only things you need to change:

The path to the command is wrong
Remove the rate_control counters while parsing the XML message as it is no longer included
Optionally you can add cuda_oqs to monitor the outbound queue is well as this is also very important if emails are relayed to remote sites. This way you get noticed if email delivery is postponed depending on connectivity

RE: Barracuda Spam Appliances

community@zenoss.org — Tue, 13 Jul 2010 12:04:53 GMT

I am using model 400s as well. I noticed the path command is wrong which I checked. When trying to run the test against device, I receive this error:

Unable to recognise encoding of this document at /usr/lib/perl5/vendor_perl/5.10.0/XML/SAX/PurePerl/EncodingDetect.pm line 100. Document requires an element [Ln: 1, Col: 0]

All my Barracuda devices show as up, but no data is being collected and no graphs. My graph says "Missing RRD File check_cuda_iqs"

RE: Barracuda Spam Appliances

community@zenoss.org — Tue, 13 Jul 2010 12:10:05 GMT

Can you do a wget of http://your_cuda/cgi-mod/stats.cgi from your Zenoss box and check if you get a proper XML document in return. It looks like there is something wrong with the parsing of recieved response in your log.

Also remember that the Zenoss box should have the proper permissions on your Barracuda:

Basic -> Administration -> Allowed SNMP and API IP ranges

If the test command is not working, no performance statistics can be collected, that why you get check_cuda_iqs missing RRD file.

RE: Barracuda Spam Appliances

community@zenoss.org — Tue, 13 Jul 2010 15:17:12 GMT

Hmm. One says I have permission and get results, but no graph within zenoss. Another says I don't have permission to run the script. The ip of the box is set up in the Cudas to have SNMP and API permissions....hmm

This is a great plug in, I just wish it wasn't such as hassle to install from day 1.

RE: Barracuda Spam Appliances

community@zenoss.org — Tue, 13 Jul 2010 15:31:14 GMT

If you go to the Barracuda template --> data source check_cuda you can test the script against your device manually. Just enter the ip or fqdn in the "test against device" field and click on test.

The output on my instance (Zenoss Core 2.5.2 on openSUSE 11.2) outputs this:

/usr/bin/perl $ZENHOME/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda -H x.x.x.x

against x.x.x.x

CUDA-x.x.x.x OK | iqs=0;;0 oqs=0;;0 spam=97718;;0 bad=1759;;0 virus=55;;0 quarantine=106;;0 tag=146;;0 allow=7669;;0

Change the path in the command template to reflect your system. I had to change it manually because it was pointing to a non-existing location. My command template settings are:

/usr/bin/perl $$ZENHOME/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda -H $devname

You also need to adapt the script and comment out the rate_control statistics in the check_cuda script as I was getting errors on the rate control information which doesn't seem to be included in the XML response of our Barracuda's. From line 35 in check_cuda, comment out the code as shown:

#my $rate_control = 0;

# Add up the numbers for each stat for the last 24 hours.
foreach my $hour (keys(%{$barracuda->{hourly}})) {
    $spams += $barracuda->{hourly}{$hour}{spams};
    $bad_recipients += $barracuda->{hourly}->{$hour}->{bad_recipients};
    $viruses += $barracuda->{hourly}->{$hour}->{viruses};
    $quarantined += $barracuda->{hourly}->{$hour}->{quarantined};
    $tagged += $barracuda->{hourly}->{$hour}->{tagged};
    $allowed += $barracuda->{hourly}->{$hour}->{allowed};
    #$rate_control += $barracuda->{hourly}->{$hour}->{rate_control};
}

my $printStr = "CUDA-$target OK |";
$printStr .= " iqs=$barracuda->{performance}->{inbound_queue_size};;0";
$printStr .= " oqs=$barracuda->{performance}->{outbound_queue_size};;0";
$printStr .= " spam=$spams;;0 bad=$bad_recipients;;0";
$printStr .= " virus=$viruses;;0 quarantine=$quarantined;;0";
$printStr .= " tag=$tagged;;0 allow=$allowed;;0";
#$printStr .= " rate_control=$rate_control;;0";
$printStr .= "\n";

Save check_cuda and run the test against device from the template itself and verify the output with mine above.

When I do a wget of the stats page from my Zenoss box, the output should look like this:

command --> wget --no-check-certificate https://x.x.x.x/cgi-mod/stats.cgi

output file:

<?xml version="1.0" encoding="UTF-8"?>

<stats>
    <performance>
        <inbound_queue_size>0</inbound_queue_size>
        <outbound_queue_size>1</outbound_queue_size>
        <latency_seconds>4</latency_seconds>
        <last_message_minutes_ago>1</last_message_minutes_ago>
        <unique_recipients>1363</unique_recipients>
        <firmware_storage_percent_used>38</firmware_storage_percent_used>
        <mail_storage_percent_used>75</mail_storage_percent_used>
        <sys_fan_speed_rpm>4017</sys_fan_speed_rpm>
        <sys_temp_celsius>2</sys_temp_celsius>
        <cpu_fan_speed_rpm>6750</cpu_fan_speed_rpm>
        <cpu_temp_celsius>44</cpu_temp_celsius>
    </performance>
    <statistics>
        <total>
            <blocked>74587796</blocked>
            <viruses>59306</viruses>
            <quarantined>347529</quarantined>
            <tagged>181152</tagged>
            <allowed>5261864</allowed>
            <total>80646669</total>
        </total>
        <today>
            <blocked>74161</blocked>
            <viruses>32</viruses>
            <quarantined>86</quarantined>
            <tagged>116</tagged>
            <allowed>6928</allowed>
            <total>81323</total>
        </today>
        <thishour>
            <blocked>2532</blocked>
            <viruses>0</viruses>
            <quarantined>26</quarantined>
            <tagged>1</tagged>
            <allowed>243</allowed>
            <total>2802</total>
        </thishour>
    </statistics>
    <hourly>
.....

RE: Barracuda Spam Appliances

community@zenoss.org — Tue, 13 Jul 2010 15:34:50 GMT

Doing the wget and viewing the file from the Zenoss server works.

Trying to run the command through the Zenoss template gives the error

Unable to recognise encoding of this document at /usr/lib/perl5/vendor_perl/5.10.0/XML/SAX/PurePerl/EncodingDetect.pm line 100. Document requires an element [Ln: 1, Col: 0]

As I stated above. I'm going to remove this ZenPack and try fresh from scratch. Hopefully I remember all the files I have to move and paths to edit properly.

RE: Barracuda Spam Appliances

community@zenoss.org — Tue, 13 Jul 2010 15:36:46 GMT

Ok, I think somethings is wrong with Perl somewhere. Maybe update the perl modules ?

RE: Barracuda Spam Appliances

community@zenoss.org — Fri, 16 Jul 2010 12:18:53 GMT

Did a fresh install of the Zenpack. Changed the command to point to the right place, and had to move some files around since by default it was looking in the wrong location. I have it up and working.

Thanks Jelle. Did you edit your check_cuda for cuda_oqs? Where did you add this?

RE: Barracuda Spam Appliances

community@zenoss.org — Tue, 20 Jul 2010 18:26:11 GMT

Hmm. It refuses to work through Zenoss on one of my appliances.

When running it through the Zenoss template test command I get these results:

Use of uninitialized value in concatenation (.) or string at /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.PBnJSolutions.Barracuda.Watcher-1.3-py2.4.egg/ZenPacks/PBnJSolutions/Barracuda/Watcher/datasources/check_cuda line 47.

Same thing for line 48.

These 2 lines in my check_cuda file are the

$printStr .= " iqs=$barracuda->{performance}->{inbound_queue_size};;0";
$printStr .= " oqs=$barracuda->{performance}->{outbound_queue_size};;0";

So it seems like something about 0 not being initalized?

Within the the directory for the barracuda at /usr/local/zenoss/zenoss/perft/Devices/cudaname

I notice it fails to create both "check_cuda_iqs.rrd" and "check_cuda_oqs.rrd". But it does create these on the devices that work with the zenpack.

If I do the check_cuda command through the server command line, I get results without issue...

RE: Barracuda Spam Appliances

community@zenoss.org — Thu, 04 Aug 2011 17:14:06 GMT

I can't install this in version 3.1.0, has anyone else tried? I tried the MJW Barracuda Monitor, which installs but doesn't appear to work either.