Oups... I missed something in log file. I noticed these lines, when 
restarting the service monitorix :

Sun May 11 19:12:56 2014 - Starting Monitorix version 3.5.1 (pid 29323).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.

So, it seems that there is an issue with iptables...

I've flushed all iptables rules before restarting moniorix. Here is my 
current iptables-save:
# Generated by iptables-save v1.4.14 on Sun May 11 19:19:29 2014
*filter
:INPUT ACCEPT [14280:3233466]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [15671:7622215]
:monitorix_IN_0 - [0:0]
:monitorix_IN_1 - [0:0]
:monitorix_IN_2 - [0:0]
:monitorix_IN_3 - [0:0]
:monitorix_IN_4 - [0:0]
:monitorix_IN_5 - [0:0]
:monitorix_IN_6 - [0:0]
:monitorix_IN_7 - [0:0]
:monitorix_IN_8 - [0:0]
:monitorix_OUT_1 - [0:0]
COMMIT
# Completed on Sun May 11 19:19:29 2014
# Generated by iptables-save v1.4.14 on Sun May 11 19:19:29 2014
*mangle
:PREROUTING ACCEPT [14684:3330780]
:INPUT ACCEPT [14684:3330780]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [16077:7726550]
:POSTROUTING ACCEPT [16077:7726550]
COMMIT
# Completed on Sun May 11 19:19:29 2014
# Generated by iptables-save v1.4.14 on Sun May 11 19:19:29 2014
*nat
:PREROUTING ACCEPT [420:21840]
:POSTROUTING ACCEPT [39:2514]
:OUTPUT ACCEPT [39:2514]
COMMIT


Le 2014-05-11 16:54, jf a écrit :
> Hi,
> 
> Sorry for this long, long, long delay. I've been very busy for other
> matters...
> 
> I upgraded to version 3.5.1, and the issue is still present.
> 
> I see nothing revelant in /var/log/monitorix :
> Use of uninitialized value $pnum in string ne at
> /usr/lib/monitorix/port.pm line 507.
> readline() on closed filehandle IN at /usr/lib/monitorix/int.pm line
> 826.
> readline() on closed filehandle IN at /usr/lib/monitorix/fs.pm line 
> 716.
> Use of uninitialized value $write_cnt in addition (+) at
> /usr/lib/monitorix/fs.pm line 763.
> Use of uninitialized value $write_sec in addition (+) at
> /usr/lib/monitorix/fs.pm line 764.
> Use of uninitialized value $read_sec in addition (+) at
> /usr/lib/monitorix/fs.pm line 764.
> readline() on closed filehandle IN at /usr/lib/monitorix/fs.pm line 
> 716.
> Use of uninitialized value $write_cnt in addition (+) at
> /usr/lib/monitorix/fs.pm line 763.
> Use of uninitialized value $write_sec in addition (+) at
> /usr/lib/monitorix/fs.pm line 764.
> Use of uninitialized value $read_sec in addition (+) at
> /usr/lib/monitorix/fs.pm line 764.
> 
> About firewall, yes, I have some basic iptables rules, and I noticed
> that my script deleted all rules before applying my own ones. So, it
> deleted some rules added by Monitorix.
> Now, I restarted monitorix, and its rules reappeared :
> 
> # iptables-save
> ...
> :monitorix_IN_0 - [0:0]
> :monitorix_IN_1 - [0:0]
> :monitorix_IN_2 - [0:0]
> :monitorix_IN_3 - [0:0]
> :monitorix_IN_4 - [0:0]
> :monitorix_IN_5 - [0:0]
> :monitorix_IN_6 - [0:0]
> :monitorix_IN_7 - [0:0]
> :monitorix_IN_8 - [0:0]
> :monitorix_OUT_1 - [0:0]
> ...
> 
> But, after more than 1/2 hour, the port graphs are still empty (they
> seem to be generated, but show now traffic on ports, even if I'm sure
> there is some traffic on these ports).
> 
> Any ideas?
> 
> Thanks!
> 
> 
> 
> Le 2014-03-15 19:13, Jordi Sanfeliu a écrit :
>> Hi,
>> 
>> I have 'iptables' with version 'v1.4.19.1' here on a Fedora 20 and all
>> is working fine, so we should look into another direction.
>> 
>> Can you, please, check if there is some firewall running in your 
>> system
>> that could flush out the Monitorix iptables rules?.
>> 
>> Also, can you check in '/var/log/monitorix' file to see if there are
>> any
>> messages that can give us some clue?
>> 
>> Thanks.
>> 
>> ---
>> Jordi Sanfeliu
>> FIBRANET Network Services Provider
>> http://www.fibranet.cat
>> 
>> 
>> A 2014-03-15 14:10, jf escrigué:
>>> Iptables version 1.4.14 is installed.
>>> 
>>> Thanks!
>>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and
>> their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/13534_NeoTech
>> _______________________________________________
>> Monitorix-general mailing list
>> Monitorix-general@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/monitorix-general
> 
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find 
> out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Monitorix-general mailing list
> Monitorix-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monitorix-general

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Monitorix-general mailing list
Monitorix-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/monitorix-general

Reply via email to