torrus-devel — discontinued

[torrus-devel] Discontinuing torrus-devel mailing list

[Stanislav S. <ssi...@gm...>]

hi all,

I'm going to discontinue this mailing list, and if you are not
subscribed to torrus-users, please do so:

https://lists.sourceforge.net/lists/listinfo/torrus-users

The traffic is so low that it doesn't make sense to maintain a
separate list for developers.

cheers,
stanislav

[torrus-devel] F5 BigIP support

[Stanislav S. <ssi...@ya...>]

if anyone has F5 BigIP LTM boxes in use, I started developing the new discovery and templates for them:
https://github.com/ssinyagin/torrus-newfeatures/tree/F5_v10

additional testing and bug reports will be appreciated.

Re: [torrus-devel] snmp returning numeric values as string

[tim <ti...@ha...>]

Hi Stan,

On 10.08.2012 10:07 AM, Stanislav Sinyagin wrote:
> in this particular error, it looks like you don't send a proper OID in the snmp request.
> 
> As for textual returned values, this might be a problem, I guess it won't work out of the box, and needs some tweaking.
> 
> one of examples is the Cisco QoS plugin which implements its own SNMP collector.

Many thanks for your fast reply.  Indeed, I missed a part in the OIDs.

Cheers,
	Tim

Re: [torrus-devel] snmp returning numeric values as string

[Stanislav S. <ssi...@ya...>]

hi Tim,

in this particular error, it looks like you don't send a proper OID in the snmp request.

As for textual returned values, this might be a problem, I guess it won't work out of the box, and needs some tweaking.

one of examples is the Cisco QoS plugin which implements its own SNMP collector.

cheers,
stan







>________________________________
> From: tim <ti...@ha...>
>To: "tor...@li..." <tor...@li...> 
>Sent: Friday, August 10, 2012 8:59 AM
>Subject: [torrus-devel] snmp returning numeric values as string
> 
>Hi there,
>
>I'm trying to write a plugin for torrus (AOCtech, EDFA).
>
>But snmp is returning numeric values encapsulated in strings, e.g.:
>
>.1.3.6.1.4.1.5875.88.2.9.2.1.1.5.0 "27.0"
>
>
>torrus does not like this and says:
>
>[10-Aug-2012 08:50:10*] Cannot create SNMP request: The OBJECT
>IDENTIFIER value "edfaCaseTemperature" is expected in dotted decimal
>notation
>
>Is there an eays way to deal with this?
>
>Thanks,
>    Tim
>
>------------------------------------------------------------------------------
>Live Security Virtual Conference
>Exclusive live event will cover all the ways today's security and 
>threat landscape has changed and how IT managers can respond. Discussions 
>will include endpoint security, mobile security and the latest in malware 
>threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>_______________________________________________
>torrus-devel mailing list
>tor...@li...
>https://lists.sourceforge.net/lists/listinfo/torrus-devel
>
>
>

[torrus-devel] snmp returning numeric values as string

[tim <ti...@ha...>]

Hi there,

I'm trying to write a plugin for torrus (AOCtech, EDFA).

But snmp is returning numeric values encapsulated in strings, e.g.:

.1.3.6.1.4.1.5875.88.2.9.2.1.1.5.0 "27.0"


torrus does not like this and says:

[10-Aug-2012 08:50:10*] Cannot create SNMP request: The OBJECT
IDENTIFIER value "edfaCaseTemperature" is expected in dotted decimal
notation

Is there an eays way to deal with this?

Thanks,
	Tim

Re: [torrus-devel] New plugin: tp-rrdfit for RRD adjustments

[Marc H. <mh+...@zu...>]

On Sun, Jun 24, 2012 at 12:28:24PM -0700, Stanislav Sinyagin wrote:
> the plugin should work with any Torrus version -- definitely 1.0.8 should be fine.
> But keep in mind that something may go wrong and it's better to make a backup before running it.
> Also your positive or negative feedback will be appreciated :)

I have a test VM running Debian unstable with torrus 2.03, which I
would snapshot in due course. It will be next weekend before I'll be
doing this since Debian work is a priority this week - our freeze is
pending.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062

Re: [torrus-devel] New plugin: tp-rrdfit for RRD adjustments

[Stanislav S. <ssi...@ya...>]

the plugin should work with any Torrus version -- definitely 1.0.8 should be fine.
But keep in mind that something may go wrong and it's better to make a backup before running it.
Also your positive or negative feedback will be appreciated :)




>________________________________
> From: Marc Haber <mh+...@zu...>
>To: "tor...@li..." <tor...@li...> 
>Sent: Sunday, June 24, 2012 8:47 PM
>Subject: Re: [torrus-devel] New plugin: tp-rrdfit for RRD adjustments
> 
>On Fri, Jun 22, 2012 at 05:29:49AM -0700, Stanislav Sinyagin wrote:
>> I uploaded a new plugin to Github. It still needs a bit more thorough testing:
>> https://github.com/ssinyagin/torrus-newfeatures/tree/master/plugins/rrdfit
>
>can this be fitted into an existing torrus installation, or is it
>necessary to do a full rebuild?
>
>

Re: [torrus-devel] New plugin: tp-rrdfit for RRD adjustments

[Marc H. <mh+...@zu...>]

On Fri, Jun 22, 2012 at 05:29:49AM -0700, Stanislav Sinyagin wrote:
> I uploaded a new plugin to Github. It still needs a bit more thorough testing:
> https://github.com/ssinyagin/torrus-newfeatures/tree/master/plugins/rrdfit

can this be fitted into an existing torrus installation, or is it
necessary to do a full rebuild?

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062

[torrus-devel] New plugin: tp-rrdfit for RRD adjustments

[Stanislav S. <ssi...@ya...>]

hi,

I uploaded a new plugin to Github. It still needs a bit more thorough testing:
https://github.com/ssinyagin/torrus-newfeatures/tree/master/plugins/rrdfit

It depends on RRD::Tweak Perl module which is going to appear at CPAN in few hours:
https://github.com/ssinyagin/perl-rrd-tweak

The plugin adds a new utility, "torrus rrdfit", and it reads all RRD files and compares their structure with the one defined in Torrus config. Then if needed, it adjusts the RRD structure and saves the file. The old copy is saved in a backup file. 


So, with this you can easily extend your historic RRD files to hold more data, for example. 

Use with care and make sure you have a backup :)

This work is sponsored by Cablecom.ch and Nexellent.ch


cheers,
stan

[torrus-devel] Job: Perl developer

[Stanislav S. <ssi...@ya...>]

I've got a potential work package which I would like to outsource to another developer. If you are or you know a good Perl developer, please send me the contacts.

The new candidate would develop new discovery modules for Torrus, and also do a bunch of other software integration work.

Please send contact details and CV to: ssi...@k-...


cheers,
stan

[torrus-devel] Make the init script more robust

[Marc H. <mh+...@zu...>]

expr does return a non-zero exit code if the result of the calculation
is zero. This is undesireable in the init script when it's running
with set -e

Suggesting the following patch.

Greetings
Marc

--- /etc/init.d/torrus-common   2012-05-14 23:00:52.592035975 +0200
+++ torrus-common       2012-05-14 22:50:59.584021778 +0200
@@ -202,7 +202,7 @@
   while test $killed -gt 0 -a $kc -gt 0; do
     log_action_cont_msg "sleep"
     /bin/sleep $TORRUS_KILL_SLEEP
-    kc=$(expr $kc - 1) || true
+    kc=$(expr $kc - 1)
     for tuple in ${tokill}; do
       eval ${tuple}
       pidfile="${piddir}/${d}.${t}.pid"
@@ -210,7 +210,7 @@
        log_action_cont_msg "TERM ${d} (${t})"
        killproc -p "${pidfile}" $d TERM
       else
-        killed=$(expr $killed - 1) || true
+        killed=$(expr $killed - 1)
       fi
     done
   done

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062

[torrus-devel] Reorganizing the Web UI

[Stanislav S. <ssi...@ya...>]

hi,

I'm planning to do a dramatic re-factoring of the Web front-end. Most probably I'll make the 2.02 release before that :)

The plan is as follows:

-- remove the support for mod_perl. As BerkeleyDB is too sensitive to its process environment, FastCGI does a much better job, and is proven to be stable and widely supported.

-- De-couple RRD graph renderer from the rest of the renderer process. I don't know yet how to organize it in the best way. The general problem is that RRDtool depends on external graphical libraries, and some versions of those libraries cause the BDB corruption. So, the RRD graph image generator should go into a separate process. It would get all the RRD::graph parameters in a JSON object and return the results in another JSON object.


I didn't yet decide how to organize that in the best way. Probably Plack would be a good option.


any input will be appreciated.

cheers,
stan

Re: [torrus-devel] [PATCH] new discovery parameter RFC2863_IF_MIB::sort-by-ifindex

[Stanislav S. <ssi...@ya...>]

Thanks, added with modifications:
https://github.com/ssinyagin/torrus-newfeatures/commit/125441185a380104537bd96cbbb503c5e8448ba3

Just to follow the common logic, the parameter with a value "yes" should deviate the behavior from default. So, I renamed the parameter to "sort-by-name" :)

Also note the paramEnabled and paramDisabled methods -- they are much safer than `eq "yes"`





>________________________________
> From: Bernhard Schmidt <be...@bi...>
>To: tor...@li... 
>Sent: Tuesday, March 13, 2012 8:07 PM
>Subject: [torrus-devel] [PATCH] new discovery parameter RFC2863_IF_MIB::sort-by-ifindex
> 
>devdiscover autogenerates precedence values by calculating 10000-$ifidx.
>While this shows good results on devices with fixed configuration, it leads
>to chaos where interfaces can come and go (i.e. subinterfaces, SVI,
>modular linecards).
>
>Setting the new parameter RFC2863_IF_MIB::sort-by-ifindex to "no" drops
>the precedence values.
>---
>src/doc/snmpdiscovery.pod.in                     |    6 ++++++
>src/perllib/Torrus/DevDiscover/RFC2863_IF_MIB.pm |    7 +++++--
>2 files changed, 11 insertions(+), 2 deletions(-)
>
>diff --git a/src/doc/snmpdiscovery.pod.in b/src/doc/snmpdiscovery.pod.in
>index c56c466..cfcb16b 100644
>--- a/src/doc/snmpdiscovery.pod.in
>+++ b/src/doc/snmpdiscovery.pod.in
>@@ -598,6 +598,12 @@ C<RFC2863_IF_MIB::ifindex-map-hint>. This parameter can change the
>reference table for nodeid. Valid values are:
>C<ifDescr>, C<ifName>, C<ifAlias>, C<ifIndex>.
>
>+=item * C<RFC2863_IF_MIB::sort-by-ifindex>
>+
>+Optional. By default, interfaces are ordered by their ifindex, which can
>+lead to not being ordered at all on devices where interfaces can come
>+and go. Setting this to C<no> drops the auto-generated I<precedence>
>+values and makes Torrus sort the interfaces alphabetically.
>
>=item * C<RFC2863_IF_MIB::noout>
>
>diff --git a/src/perllib/Torrus/DevDiscover/RFC2863_IF_MIB.pm b/src/perllib/Torrus/DevDiscover/RFC2863_IF_MIB.pm
>index d53d279..4468b0a 100644
>--- a/src/perllib/Torrus/DevDiscover/RFC2863_IF_MIB.pm
>+++ b/src/perllib/Torrus/DevDiscover/RFC2863_IF_MIB.pm
>@@ -576,8 +576,11 @@ sub buildConfig
>             $interface->{'param'}{'interface-comment'} = $comment;
>         }
>
>-        # Order the interfaces by ifIndex, not by interface name
>-        $interface->{'param'}{'precedence'} = sprintf('%d', 100000-$ifIndex);
>+        if( $devdetails->param('RFC2863_IF_MIB::sort-by-ifindex') eq 'no' )
>+        {
>+            # Order the interfaces by ifIndex, not by interface name
>+            $interface->{'param'}{'precedence'} = sprintf('%d', 100000-$ifIndex);
>+        }
>
>         $interface->{'param'}{'devdiscover-nodetype'} =
>             'RFC2863_IF_MIB::interface';
>-- 
>1.7.2.5
>
>
>------------------------------------------------------------------------------
>Keep Your Developer Skills Current with LearnDevNow!
>The most comprehensive online learning library for Microsoft developers
>is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>Metro Style Apps, more. Free future releases when you subscribe now!
>http://p.sf.net/sfu/learndevnow-d2d
>_______________________________________________
>torrus-devel mailing list
>tor...@li...
>https://lists.sourceforge.net/lists/listinfo/torrus-devel
>
>
>

[torrus-devel] [PATCH] new discovery parameter RFC2863_IF_MIB::sort-by-ifindex

[Bernhard S. <be...@bi...>]

devdiscover autogenerates precedence values by calculating 10000-$ifidx.
While this shows good results on devices with fixed configuration, it leads
to chaos where interfaces can come and go (i.e. subinterfaces, SVI,
modular linecards).

Setting the new parameter RFC2863_IF_MIB::sort-by-ifindex to "no" drops
the precedence values.
---
 src/doc/snmpdiscovery.pod.in                     |    6 ++++++
 src/perllib/Torrus/DevDiscover/RFC2863_IF_MIB.pm |    7 +++++--
 2 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/src/doc/snmpdiscovery.pod.in b/src/doc/snmpdiscovery.pod.in
index c56c466..cfcb16b 100644
--- a/src/doc/snmpdiscovery.pod.in
+++ b/src/doc/snmpdiscovery.pod.in
@@ -598,6 +598,12 @@ C<RFC2863_IF_MIB::ifindex-map-hint>. This parameter can change the
 reference table for nodeid. Valid values are:
 C<ifDescr>, C<ifName>, C<ifAlias>, C<ifIndex>.
 
+=item * C<RFC2863_IF_MIB::sort-by-ifindex>
+
+Optional. By default, interfaces are ordered by their ifindex, which can
+lead to not being ordered at all on devices where interfaces can come
+and go. Setting this to C<no> drops the auto-generated I<precedence>
+values and makes Torrus sort the interfaces alphabetically.
 
 =item * C<RFC2863_IF_MIB::noout>
 
diff --git a/src/perllib/Torrus/DevDiscover/RFC2863_IF_MIB.pm b/src/perllib/Torrus/DevDiscover/RFC2863_IF_MIB.pm
index d53d279..4468b0a 100644
--- a/src/perllib/Torrus/DevDiscover/RFC2863_IF_MIB.pm
+++ b/src/perllib/Torrus/DevDiscover/RFC2863_IF_MIB.pm
@@ -576,8 +576,11 @@ sub buildConfig
             $interface->{'param'}{'interface-comment'} = $comment;
         }
 
-        # Order the interfaces by ifIndex, not by interface name
-        $interface->{'param'}{'precedence'} = sprintf('%d', 100000-$ifIndex);
+        if( $devdetails->param('RFC2863_IF_MIB::sort-by-ifindex') eq 'no' )
+        {
+            # Order the interfaces by ifIndex, not by interface name
+            $interface->{'param'}{'precedence'} = sprintf('%d', 100000-$ifIndex);
+        }
 
         $interface->{'param'}{'devdiscover-nodetype'} =
             'RFC2863_IF_MIB::interface';
-- 
1.7.2.5

Re: [torrus-devel] [torrus-users] Torrus host unreachable

[Stanislav S. <ssi...@ya...>]

hi Plamen,

$Torrus::Collector::SNMP::unreachableRetryDelay = 10;
this means that once the device is unreachable, the collector will wait 10 minutes before trying to reach it again. You can decrease that to zero, then the collector will try to access the device every 5 minutes.









>________________________________
> From: Plamen Vasilev <pl...@in...>
>To: tor...@li... 
>Sent: Friday, February 10, 2012 10:46 AM
>Subject: [torrus-users] Torrus host unreachable
> 
>Hi,
>
>I have the same issue as http://sourceforge.net/mailarchive/message.php?msg_id=27936160
>
>I use torrus to collect SNMP data in mysql database, but when I try to force one host to be unreachable for 5-6 minutes using "iptables" and remove the rule i didn't get any data for about 20-25 minutes.
>I have tested the connectivity with command line "snmpget" command and I Have access, but torrus doesn't collect data.
>
>I use standard command line torrus configuration and in my /etc/torrus/conf/torrus-siteconfig.pl I have the following :
>
>@Torrus::Global::xmlAlwaysIncludeFirst = ( 'defaults.xml', 'site-global.xml' );
>
>%Torrus::Global::treeConfig =
>    (
>     'main' => {
>         'description' => 'The main tree',
>         'info'        => 'some tree',
>         'xmlfiles' => [qw(routers.xml)],
>         'run' => { 'collector' => 1, 'monitor' => 0 } }
>     );
>
># Customizable look in the HTML page top
># $Torrus::Renderer::companyName = 'Your company name';
># $Torrus::Renderer::companyURL = 'http://torrus.sf.net';
># $Torrus::Renderer::siteInfo = `hostname`;
>
>
>push (@Torrus::Collector::loadModules, 'Torrus::Collector::ExternalStorage');
>$Torrus::SQL::connections{'Default'}{'dsn'} =
>      'DBI:mysql:database=xxxxx';
>$Torrus::SQL::connections{'Default'}{'username'} = 'xxxx';
>$Torrus::SQL::connections{'Default'}{'password'} = 'xxxx';
>
>$Torrus::Collector::SNMP::unreachableRetryDelay = 10;
>$Torrus::Collector::SNMP::mapsExpireCheckPeriod = 10;
>
>
>and in a part of /etc/torrus/xmlconfig/routers.xml
>
>      <param name="show-recursive" value="yes"/>
>      <param name="snmp-check-sysuptime" value="yes"/>
>      <param name="snmp-community" value="xxxxxxxx"/>
>      <param name="snmp-host" value="xxxxxxxxxx"/>
>      <param name="snmp-ipversion" value="4"/>
>      <param name="snmp-port" value="161"/>
>      <param name="snmp-retries" value="2"/>
>      <param name="snmp-timeout" value="10"/>
>      <param name="snmp-transport" value="udp"/>
>      <param name="snmp-version" value="2c"/>
>
>Any idea how can I fix the 20 minutes hole in collecting data ?
>------------------------------------------------------------------------------
>Virtualization & Cloud Management Using Capacity Planning
>Cloud computing makes use of virtualization - but cloud computing 
>also focuses on allowing computing to be delivered as a service.
>http://www.accelacomm.com/jaw/sfnl/114/51521223/
>_______________________________________________
>torrus-users mailing list
>tor...@li...
>https://lists.sourceforge.net/lists/listinfo/torrus-users
>
>
>

[torrus-devel] SNMP discovery refactored

[Stanislav S. <ssi...@ya...>]

hi,

as of now, the following methods are deprecated in SNMP discovery modules:
storeSnmpVars(), hasOID(), snmpVar(), getSnmpIndices().

Instead, the new method $dd->walkSnmpTable()  should be used.

I've already updated the IF-MIB discovery, and soon more discovery modules will be updated.

At the moment the new code is available at
https://github.com/ssinyagin/torrus-newfeatures

and after some testing, will be pushed to the development snapshot on Sourceforge.


cheers,
stan

[torrus-devel] Syslog logging

[Stanislav S. <ssi...@ya...>]

hi all,

In the recent commits at 

https://github.com/ssinyagin/torrus-newfeatures

I've implemented the Syslog logging, and now collector and monitor use Syslog by default.

The default facility is "local0".

The old log rotation upon SIGHUP is removed, as it was causing crashes in the collector. 


Your testing will be appreciated.

The old behavior, except for SIGHUP, can be restored by
$Torrus::Collector::useSyslog = 0;
$Torrus::Monitor::useSyslog = 0;



cheers,
stan

Re: [torrus-devel] Torrus 2.01 in Debian experimental

[Stanislav S. <ssi...@ya...>]

yeah, because the root cause is unknown, and the issue is difficult to reproduce.
I actually tried to force this behavior by sending HTTP GET requests every few seconds, but it didn't help.
The effect was visible only when someone leaves the browser open for several days, and the DB crashed after 3-7 days only.

I had Ubuntu on my server, and Nenad used Debian. so, probably Nenad has a bit more relevant information :)





>________________________________
>From: Bernhard Schmidt <be...@bi...>
>To: Stanislav Sinyagin <ssi...@ya...>
>Cc: "tor...@li..." <tor...@li...>
>Sent: Monday, November 7, 2011 7:36 AM
>Subject: Re: [torrus-devel] Torrus 2.01 in Debian experimental
>
>Am 06.11.2011 21:25, schrieb Stanislav Sinyagin:
>
>Hello Stanislav,
>
>> thanks a lot, this is great to hear indeed.
>>
>> Do you know if this issue has been tracked down?
>> http://goo.gl/r62Ub
>
>Not that I know of, but we don't have a formal bugreport about that in 
>the Debian BTS either.
>
>Best Regards,
>Bernhard
>
>
>

Re: [torrus-devel] Torrus 2.01 in Debian experimental

[Bernhard S. <be...@bi...>]

Am 06.11.2011 21:25, schrieb Stanislav Sinyagin:

Hello Stanislav,

> thanks a lot, this is great to hear indeed.
>
> Do you know if this issue has been tracked down?
> http://goo.gl/r62Ub

Not that I know of, but we don't have a formal bugreport about that in 
the Debian BTS either.

Best Regards,
Bernhard

Re: [torrus-devel] Torrus 2.01 in Debian experimental

[Stanislav S. <ssi...@ya...>]

  
hi Bernhard,

thanks a lot, this is great to hear indeed.

Do you know if this issue has been tracked down?
http://sourceforge.net/mailarchive/forum.php?thread_name=1317756245.82584.YahooMailNeo%40web39313.mail.mud.yahoo.com&forum_name=torrus-users

In summary, with the Debian and Ubuntu pre-requisite packages, the 
renderer eventually spoils the database, and it needs recovery.
The problem is hard to reproduce, and it pops out when someone leaves a browser window open for few days.

I guess it's something to do with the pango or cairo libraries, it seems like one of them corrupts the memory during the graph rendering.
With the following library versions, it appears to work fine:
https://github.com/oetiker/sdbs/blob/master/build_rrdtool-1.4.5.sh


cheers,
stan





>________________________________
>From: Bernhard Schmidt <be...@bi...>
>To: "tor...@li..." <tor...@li...>
>Sent: Sunday, November 6, 2011 7:00 PM
>Subject: [torrus-devel] Torrus 2.01 in Debian experimental
>
>Hello,
>
>with the great support and sponsorship of Marc Haber I've prepared a
>Torrus 2.01 package for Debian that has just been uploaded to
>experimental. It should be available on a mirror next to you really soon.
>
>If you run Debian testing/unstable with Torrus I'd love your feedback on
>this. Debian stable (squeeze) does not work out of the box because of an
>unsatisfied dependency on db-util for database upgrade purposes. If you
>need to test on Squeeze drop me a note, I'll build a local package for
>you without this code-path.
>
>Best Regards,
>Bernhard
>
>------------------------------------------------------------------------------
>RSA(R) Conference 2012
>Save $700 by Nov 18
>Register now
>http://p.sf.net/sfu/rsa-sfdev2dev1
>_______________________________________________
>torrus-devel mailing list
>tor...@li...
>https://lists.sourceforge.net/lists/listinfo/torrus-devel
>
>
>

[torrus-devel] Torrus 2.01 in Debian experimental

[Bernhard S. <be...@bi...>]

Hello,

with the great support and sponsorship of Marc Haber I've prepared a
Torrus 2.01 package for Debian that has just been uploaded to
experimental. It should be available on a mirror next to you really soon.

If you run Debian testing/unstable with Torrus I'd love your feedback on
this. Debian stable (squeeze) does not work out of the box because of an
unsatisfied dependency on db-util for database upgrade purposes. If you
need to test on Squeeze drop me a note, I'll build a local package for
you without this code-path.

Best Regards,
Bernhard

[torrus-devel] Perl warnings handling

[Stanislav S. <ssi...@ya...>]

hi all,

in the new development snapshot (torrus-2.02dev.tar.gz), Perl warnings are enabled in all discovery modules. Also lots of obvious warning issues have been fixed.


Your help in testing will be appreciated (tested quite well on Cisco hardware already).

thanks,
stan

Re: [torrus-devel] 1.0.10 release candidate

[Stanislav S. <ssi...@ya...>]

________________________________
>From: Jon Nistor <ni...@sn...>
>Maybe call the release 1.1 or what are the plans for that?


actually now is the right time for a 1.1 release, as there's stuff which is 

brand new (RPC calls, SNMP reachability graphs, etc).


Also I think to simplify the numbering, and do 1.01, 1.02, etc.  


Then it also simplifies the plugin versioning: a plugin would have a version 

of 1.02.01, and that would mean it's compatible with torrus-1.02.

[torrus-devel] 1.0.10 release candidate

[Stanislav S. <ssi...@ya...>]

hi all,

I'm going to publish the torrus-1.0.10 release very soon. There's a bunch of new features, mainly sponsored by Cablecom, and the system is running stable since a few weeks.

If there's any urgency that I should be aware of before pushing the release, please let me know.

cheers,
s.

[torrus-devel] Temporization of alarms

[Grégoire G. <gre...@pr...>]

Hello !

Is there a way to temporize alarms in Torrus?
I explain:
I want an alarm to be rise up (mail sent) only after 3 measures out of the limit instead of 1 measure out of the limit.

I know I can script something to check the 2 old values in the RRD but I would to know if there is another way.

Sincerely

Gregoire

-----------------------------------------------------
Practeo SA - Ingénierie informatique

Galland Grégoire
Network Engineer

Rue de la Gare 2 - CH-1030 Bussigny - Suisse

Tél:

 +41 21 706 13 38

Fax :

 +41 21 706 13 31

Email:

 gre...@pr...<mailto:gre...@pr...>

Web:

 www.practeo.ch<http://www.practeo.ch/>