[Monitorix-general] Network port traffic not working

[jf]

Hi,

I've been using Monitorix for some times. Everything was working well
under Debian6.

But since I updated to Debian7, the graphs from "Network port traffic"
do not show anything anymore.
I read in the documentation that the command "iptables" must be
available, and it is (I'm using iptables as a firewall).

iptables show the following lines (iptables -L) :
Chain monitorix_IN_0 (0 references)
target prot opt source destination

Chain monitorix_IN_1 (0 references)
target prot opt source destination

Chain monitorix_IN_2 (0 references)
target prot opt source

Can you help me to make these graphs work again?

Thanks in advance!

[Jordi Sanfeliu]

Hi,

Perhaps there is some new incompatibility with the 'iptables' version in
Debian 7. What version you have there?
Thanks.

---
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat


A 2014-03-15 09:54, jf escrigué:
> Hi,
>
> I've been using Monitorix for some times. Everything was working well
> under Debian6.
>
> But since I updated to Debian7, the graphs from "Network port traffic"
> do not show anything anymore.
> I read in the documentation that the command "iptables" must be
> available, and it is (I'm using iptables as a firewall).
>
> iptables show the following lines (iptables -L) :
> Chain monitorix_IN_0 (0 references)
> target prot opt source destination
>
> Chain monitorix_IN_1 (0 references)
> target prot opt source destination
>
> Chain monitorix_IN_2 (0 references)
> target prot opt source
>
> Can you help me to make these graphs work again?
>
> Thanks in advance!
>

[jf]

Iptables version 1.4.14 is installed.

Thanks!

Le 2014-03-15 13:37, Jordi Sanfeliu a écrit :
> Hi,
>
> Perhaps there is some new incompatibility with the 'iptables' version
> in
> Debian 7. What version you have there?
> Thanks.
>
> ---
> Jordi Sanfeliu
> FIBRANET Network Services Provider
> http://www.fibranet.cat
>
>
> A 2014-03-15 09:54, jf escrigué:
>> Hi,
>>
>> I've been using Monitorix for some times. Everything was working well
>> under Debian6.
>>
>> But since I updated to Debian7, the graphs from "Network port traffic"
>> do not show anything anymore.
>> I read in the documentation that the command "iptables" must be
>> available, and it is (I'm using iptables as a firewall).
>>
>> iptables show the following lines (iptables -L) :
>> Chain monitorix_IN_0 (0 references)
>> target prot opt source destination
>>
>> Chain monitorix_IN_1 (0 references)
>> target prot opt source destination
>>
>> Chain monitorix_IN_2 (0 references)
>> target prot opt source
>>
>> Can you help me to make these graphs work again?
>>
>> Thanks in advance!
>>
>
>
> ------------------------------------------------------------------------------
> 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-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monitorix-general

[Jordi Sanfeliu]

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!
>

[jf]

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-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monitorix-general

[jf]

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-***@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-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monitorix-general

[Jordi Sanfeliu]

On 05/11/2014 05:20 PM, jf wrote:
> 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...

Make sure you have not saved any Monitorix iptables rules.


>
> 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]

Remove these Monitorix rules, please.
Regards.

--
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat

[Jordi Sanfeliu]

Hi,

On 05/11/2014 04:54 PM, jf wrote:
> 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.

Can you, please, specify which OS have you there?
Also, can you paste the <port> block of your configuration file?


> 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.

Can you paste the <fs> block of your configuration file?


>
> 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]
> ...

Do not save the Monitorix rules, they are created and removed
automatically everytime you start and stop Monitorix.


>
> 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?
>

# iptables -nxvL INPUT

should say you the current traffic accounting for each port in the INPUT
chain.


> Thanks!
>

Let me know.
Regards.

--
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat

[jf]

Le 2014-05-13 18:36, Jordi Sanfeliu a écrit :

> Can you, please, specify which OS have you there?

Debian 7.4
Linux vps 2.6.32-042stab085.20 #1 SMP Fri Mar 21 19:07:05 MSK 2014
x86_64 GNU/Linux

> Also, can you paste the <port> block of your configuration file?
<port>
max = 9
rule = 24000
list = 25, 15167, 80, 22, 110, 139, 3306, 53, 143
<desc>
25 = SMTP, tcp, in, 0, 1000
15167 = CJDNS, udp, in/out, 0, 1000
80 = HTTP, tcp, in, 0, 1000
22 = SSH, tcp, in, 0, 1000
110 = POP3, tcp, in, 0, 1000
139 = NETBIOS, tcp, in, 0, 1000
3306 = MYSQL, tcp, in, 0, 1000
53 = DNS, udp, in, 0, 1000
143 = IMAP, tcp, in, 0, 1000
</desc>
graphs_per_row = 3
</port>

I simply replaced the entry for the FTP by another one for CJDNS.

> Can you paste the <fs> block of your configuration file?
<fs>
<list>
0 = /, swap
</list>
<desc>
</desc>
<devmap>
</devmap>
rigid = 2, 0, 2, 0
limit = 100, 1000, 100, 1000
<alerts>
rootfs_enabled = n
rootfs_timeintvl = 3600
rootfs_threshold = 100
rootfs_script = /path/to/script.sh
</alerts>
</fs>

All values are default values
I suppose that the errors about fs come from this "/path/to/script.sh".
To which file should I make it point? But FS is not very important to
me, for now.


>> # 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]
>> ...
>
> Do not save the Monitorix rules, they are created and removed
> automatically everytime you start and stop Monitorix.

No, these rules are not saved and restored with my script, I just wanted
to show you that they are correctly created when I start monitorix. I
should have used iptables -L instead of iptables-save, I guess :-)

> # iptables -nxvL INPUT
>
> should say you the current traffic accounting for each port in the
> INPUT
> chain.
The output shows no lines about monitorix rules...

>
> Let me know.
> Regards.

Thanks for your help!

[Jordi Sanfeliu]

On 05/13/2014 10:08 PM, jf wrote:
[...]
> Debian 7.4
> Linux vps 2.6.32-042stab085.20 #1 SMP Fri Mar 21 19:07:05 MSK 2014
> x86_64 GNU/Linux

Ok thanks. Since I'm unable to reproduce your problems in the 'ports'
graphs, I'll try to make a fresh install of a Debian 7.4 during this
weekend.

I'll keep you informed.


>
>> Also, can you paste the <port> block of your configuration file?
> <port>
> max = 9
> rule = 24000
> list = 25, 15167, 80, 22, 110, 139, 3306, 53, 143
> <desc>
> 25 = SMTP, tcp, in, 0, 1000
> 15167 = CJDNS, udp, in/out, 0, 1000
> 80 = HTTP, tcp, in, 0, 1000
> 22 = SSH, tcp, in, 0, 1000
> 110 = POP3, tcp, in, 0, 1000
> 139 = NETBIOS, tcp, in, 0, 1000
> 3306 = MYSQL, tcp, in, 0, 1000
> 53 = DNS, udp, in, 0, 1000
> 143 = IMAP, tcp, in, 0, 1000
> </desc>
> graphs_per_row = 3
> </port>
>
> I simply replaced the entry for the FTP by another one for CJDNS.

This looks good to me.


>
>> Can you paste the <fs> block of your configuration file?
> <fs>
> <list>
> 0 = /, swap
> </list>
> <desc>
> </desc>
> <devmap>
> </devmap>
> rigid = 2, 0, 2, 0
> limit = 100, 1000, 100, 1000
> <alerts>
> rootfs_enabled = n
> rootfs_timeintvl = 3600
> rootfs_threshold = 100
> rootfs_script = /path/to/script.sh
> </alerts>
> </fs>
>
> All values are default values
> I suppose that the errors about fs come from this "/path/to/script.sh".
> To which file should I make it point? But FS is not very important to
> me, for now.

No, the alert where there is the 'rootfs_script' option is disabled. So
that's not the cause of these error messages.

I think that the cause of them is that your system doesn't has enabled
a swap device. If so, please, remove it from the list '0'.


>> # iptables -nxvL INPUT
>>
>> should say you the current traffic accounting for each port in the
>> INPUT
>> chain.
> The output shows no lines about monitorix rules...
>

If that command doesn't show you the Monitorix iptables rules, then it
means that either Monitorix is not running or another application
(possibly a firewall) has flushed out the Monitorix rules.

Regards.

--
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat

[jf]

Hi,

I know this is an old thread, but the issue is still there, and I don't
know what to do.

I also noticed that the graphs under "eth0 Network traffic and usage" do
not work any more, but I'm sure they were working before.

I don't if I mentionned it, but I'm running on a OpenVZ based VPS. Could
this issue be caused by a missing kernel module on the host node?
What should I ask/mention to my provider in order to have some more
information?

Jordi, were you able to find any thing relevant?

Thanks for your help!

Le 2014-05-16 12:26, Jordi Sanfeliu a écrit :
> On 05/13/2014 10:08 PM, jf wrote:
> [...]
>> Debian 7.4
>> Linux vps 2.6.32-042stab085.20 #1 SMP Fri Mar 21 19:07:05 MSK 2014
>> x86_64 GNU/Linux
>
> Ok thanks. Since I'm unable to reproduce your problems in the 'ports'
> graphs, I'll try to make a fresh install of a Debian 7.4 during this
> weekend.
>
> I'll keep you informed.
>
>
>>
>>> Also, can you paste the <port> block of your configuration file?
>> <port>
>> max = 9
>> rule = 24000
>> list = 25, 15167, 80, 22, 110, 139, 3306, 53, 143
>> <desc>
>> 25 = SMTP, tcp, in, 0, 1000
>> 15167 = CJDNS, udp, in/out, 0, 1000
>> 80 = HTTP, tcp, in, 0, 1000
>> 22 = SSH, tcp, in, 0, 1000
>> 110 = POP3, tcp, in, 0, 1000
>> 139 = NETBIOS, tcp, in, 0, 1000
>> 3306 = MYSQL, tcp, in, 0, 1000
>> 53 = DNS, udp, in, 0, 1000
>> 143 = IMAP, tcp, in, 0, 1000
>> </desc>
>> graphs_per_row = 3
>> </port>
>>
>> I simply replaced the entry for the FTP by another one for CJDNS.
>
> This looks good to me.
>
>
>>
>>> Can you paste the <fs> block of your configuration file?
>> <fs>
>> <list>
>> 0 = /, swap
>> </list>
>> <desc>
>> </desc>
>> <devmap>
>> </devmap>
>> rigid = 2, 0, 2, 0
>> limit = 100, 1000, 100, 1000
>> <alerts>
>> rootfs_enabled = n
>> rootfs_timeintvl = 3600
>> rootfs_threshold = 100
>> rootfs_script = /path/to/script.sh
>> </alerts>
>> </fs>
>>
>> All values are default values
>> I suppose that the errors about fs come from this
>> "/path/to/script.sh".
>> To which file should I make it point? But FS is not very important to
>> me, for now.
>
> No, the alert where there is the 'rootfs_script' option is disabled. So
> that's not the cause of these error messages.
>
> I think that the cause of them is that your system doesn't has enabled
> a swap device. If so, please, remove it from the list '0'.
>
>
>>> # iptables -nxvL INPUT
>>>
>>> should say you the current traffic accounting for each port in the
>>> INPUT
>>> chain.
>> The output shows no lines about monitorix rules...
>>
>
> If that command doesn't show you the Monitorix iptables rules, then it
> means that either Monitorix is not running or another application
> (possibly a firewall) has flushed out the Monitorix rules.
>
> Regards.
>
> --
> Jordi Sanfeliu
> FIBRANET Network Services Provider
> http://www.fibranet.cat
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Monitorix-general mailing list
> Monitorix-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monitorix-general

[Jordi Sanfeliu]

Hi,

I've been checking the old messages on this thread and they all were
related on problems in iptables and the network ports traffic. You are
now asking about problems in the network interface graph, so unless I
missed something, this is new.

Whatever, make sure that your network interface name 'eth0' has not
changed in any of the last system updates. Use the command 'ifconfig' to
see the current name and compare it with that you have defined in
'monitorix.conf'. If so, change it accordingly and restart Monitorix.

If that's not the case, make sure that your current network interface
appears in '/proc/net/dev', which is from where Monitorix collects
statistical data.

Let me know.
Regards.


On 06/17/2014 08:19 PM, jf wrote:
> Hi,
>
> I know this is an old thread, but the issue is still there, and I don't
> know what to do.
>
> I also noticed that the graphs under "eth0 Network traffic and usage" do
> not work any more, but I'm sure they were working before.
>
> I don't if I mentionned it, but I'm running on a OpenVZ based VPS. Could
> this issue be caused by a missing kernel module on the host node?
> What should I ask/mention to my provider in order to have some more
> information?
>
> Jordi, were you able to find any thing relevant?
>
> Thanks for your help!
>
> Le 2014-05-16 12:26, Jordi Sanfeliu a écrit :
>> On 05/13/2014 10:08 PM, jf wrote:
>> [...]
>>> Debian 7.4
>>> Linux vps 2.6.32-042stab085.20 #1 SMP Fri Mar 21 19:07:05 MSK 2014
>>> x86_64 GNU/Linux
>>
>> Ok thanks. Since I'm unable to reproduce your problems in the 'ports'
>> graphs, I'll try to make a fresh install of a Debian 7.4 during this
>> weekend.
>>
>> I'll keep you informed.
>>
>>
>>>
>>>> Also, can you paste the <port> block of your configuration file?
>>> <port>
>>> max = 9
>>> rule = 24000
>>> list = 25, 15167, 80, 22, 110, 139, 3306, 53, 143
>>> <desc>
>>> 25 = SMTP, tcp, in, 0, 1000
>>> 15167 = CJDNS, udp, in/out, 0, 1000
>>> 80 = HTTP, tcp, in, 0, 1000
>>> 22 = SSH, tcp, in, 0, 1000
>>> 110 = POP3, tcp, in, 0, 1000
>>> 139 = NETBIOS, tcp, in, 0, 1000
>>> 3306 = MYSQL, tcp, in, 0, 1000
>>> 53 = DNS, udp, in, 0, 1000
>>> 143 = IMAP, tcp, in, 0, 1000
>>> </desc>
>>> graphs_per_row = 3
>>> </port>
>>>
>>> I simply replaced the entry for the FTP by another one for CJDNS.
>>
>> This looks good to me.
>>
>>
>>>
>>>> Can you paste the <fs> block of your configuration file?
>>> <fs>
>>> <list>
>>> 0 = /, swap
>>> </list>
>>> <desc>
>>> </desc>
>>> <devmap>
>>> </devmap>
>>> rigid = 2, 0, 2, 0
>>> limit = 100, 1000, 100, 1000
>>> <alerts>
>>> rootfs_enabled = n
>>> rootfs_timeintvl = 3600
>>> rootfs_threshold = 100
>>> rootfs_script = /path/to/script.sh
>>> </alerts>
>>> </fs>
>>>
>>> All values are default values
>>> I suppose that the errors about fs come from this
>>> "/path/to/script.sh".
>>> To which file should I make it point? But FS is not very important to
>>> me, for now.
>>
>> No, the alert where there is the 'rootfs_script' option is disabled. So
>> that's not the cause of these error messages.
>>
>> I think that the cause of them is that your system doesn't has enabled
>> a swap device. If so, please, remove it from the list '0'.
>>
>>
>>>> # iptables -nxvL INPUT
>>>>
>>>> should say you the current traffic accounting for each port in the
>>>> INPUT
>>>> chain.
>>> The output shows no lines about monitorix rules...
>>>
>>
>> If that command doesn't show you the Monitorix iptables rules, then it
>> means that either Monitorix is not running or another application
>> (possibly a firewall) has flushed out the Monitorix rules.
>>
>> Regards.
>>
>> --
>> Jordi Sanfeliu
>> FIBRANET Network Services Provider
>> http://www.fibranet.cat
>>

--
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat

[Wijatmoko U. Prayitno]

On Thu, 19 Jun 2014 10:23:06 +0200
Jordi Sanfeliu <***@fibranet.cat> wrote:

> Whatever, make sure that your network interface name
> 'eth0' has not changed in any of the last system
> updates. Use the command 'ifconfig' to see the current
> name and compare it with that you have defined in
> 'monitorix.conf'.
openVZ VPS use "venet0" as default ethernet interface.

> On 06/17/2014 08:19 PM, jf wrote:
> > I don't if I mentionned it, but I'm running on a
> > OpenVZ based VPS. Could this issue be caused by a
> > missing kernel module on the host node? What should
> > I ask/mention to my provider in order to have some
> > more information?
> >
if you doubt or unsure, run "ifconfig" as Jordi said.

[jf]

Sorry for the confision! You were right, the issue with the network
usage was caused by an error in the configuration file (eth0 in place of
venet0). This one is resolved!

But the issue with the graph "port traffic" is still there.

Le 2014-06-19 11:05, Wijatmoko U. Prayitno a écrit :
> On Thu, 19 Jun 2014 10:23:06 +0200
> Jordi Sanfeliu <***@fibranet.cat> wrote:
>
>> Whatever, make sure that your network interface name
>> 'eth0' has not changed in any of the last system
>> updates. Use the command 'ifconfig' to see the current
>> name and compare it with that you have defined in
>> 'monitorix.conf'.
> openVZ VPS use "venet0" as default ethernet interface.
>
>> On 06/17/2014 08:19 PM, jf wrote:
>> > I don't if I mentionned it, but I'm running on a
>> > OpenVZ based VPS. Could this issue be caused by a
>> > missing kernel module on the host node? What should
>> > I ask/mention to my provider in order to have some
>> > more information?
>> >
> if you doubt or unsure, run "ifconfig" as Jordi said.
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk
> Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Monitorix-general mailing list
> Monitorix-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monitorix-general

[Jordi Sanfeliu]

Hi,

I'm sorry, I'm a bit lost with all this. Can you, please, comment what
issue is that?

Thanks.


On 06/22/2014 07:56 PM, jf wrote:
>
> But the issue with the graph "port traffic" is still there.
>

--
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat