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

Reply via email to