did not save device on Listener tab after restart Mysql

General discussion about Plugins for Cacti

Moderators: Developers, Moderators

Post Reply
trungmv
Cacti User
Posts: 87
Joined: Wed Feb 15, 2012 10:32 pm

did not save device on Listener tab after restart Mysql

Post by trungmv »

My system: CentOS 5.x
Cacti version: 0.8.8
Spine: 0.8.8a
Flowview: 1.1
Mysql version : 5.5.28

After each restart mysql i lost my device that i have had add on previously.
Is this the bug of this version?
Any one can help this?

Many thanks
verruckt
Posts: 7
Joined: Wed Apr 03, 2013 1:17 pm

Re: did not save device on Listener tab after restart Mysql

Post by verruckt »

Hi everyone. My very first post in that forum.

Identical problem.
CentOS 6.4
Cacti 0.8.8a
FlowView 1.1
mysql Ver 14.14 Distrib 5.1.67
I have 8 listeners for FlowView listening on 8 different ports.

Code: Select all

[root@blah ~]# service flow-capture start
NOTE: Starting Flow Tools
NOTE: Launching flow-capture as '/usr/bin/flow-capture -S5 -V5 -z 0 -n 287 -e 576 -N 0 -w /var/flow-tools/ALLIANT_FR 0/172.22.0.3/9997'
NOTE: Launching flow-capture as '/usr/bin/flow-capture -S5 -V5 -z 0 -n 287 -e 576 -N 0 -w /var/flow-tools/ALLIANT_IR 0/172.23.0.3/9992'
NOTE: Launching flow-capture as '/usr/bin/flow-capture -S5 -V5 -z 0 -n 287 -e 576 -N 0 -w /var/flow-tools/ALLIANT_LA 0/172.18.0.3/9993'
NOTE: Launching flow-capture as '/usr/bin/flow-capture -S5 -V5 -z 0 -n 287 -e 576 -N 0 -w /var/flow-tools/ALLIANT_SC 0/172.20.0.3/9996'
NOTE: Launching flow-capture as '/usr/bin/flow-capture -S5 -V5 -z 0 -n 287 -e 576 -N 0 -w /var/flow-tools/ALLIANT_SDOG 0/172.24.0.3/9991'
NOTE: Launching flow-capture as '/usr/bin/flow-capture -S5 -V5 -z 0 -n 287 -e 576 -N 0 -w /var/flow-tools/ALLIANT_SDPR 0/172.16.0.3/9995'
NOTE: Launching flow-capture as '/usr/bin/flow-capture -S5 -V5 -z 0 -n 287 -e 576 -N 0 -w /var/flow-tools/ALLIANT_SFLS 0/172.21.0.3/9998'
NOTE: Launching flow-capture as '/usr/bin/flow-capture -S5 -V5 -z 0 -n 287 -e 576 -N 0 -w /var/flow-tools/ALLIANT_SFBA 0/172.19.0.3/9994'
After a reboot non of the listeners is there and I have to recreate all of them and of course the service cannot start automatically even:

Code: Select all

[root@blah ~]# chkconfig flow-capture on
[root@blah ~]# chkconfig --list | grep flow
flow-capture    0:off   1:off   2:on    3:on    4:on    5:on    6:off
It is pain to create all these each time after I have to reboot. For instance: kernel upgrade, memory or hdd failure and have to shut the machine for maintenance.

Do you have any solution? Am I making a mistake somewhere?

Danke

PS I'm running SELINUX enforced and too me a while until I found out why plugins don't show up and any FlowView doesn't show anything even when it is writing in the flow directory. The key is SELINUX and it has to be changed in both locations with -R parameter of course. Once you change the parent directory, all other will be created with the parent permission unless otherwise stated:

Code: Select all

[root@blah var]# ls -Z /usr/share/cacti/plugins
drwxr-xr-x. root root unconfined_u:object_r:httpd_cache_t:s0 flowview

Code: Select all

[root@blah var]# ls -lZ
drwxr-xr-x. flow-tools flow-tools system_u:object_r:httpd_sys_content_t:s0 flow-tools
Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests