Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flowview dosen't kill flow process when disabled, or flow-capture.service is stoped #227

Open
arno-st opened this issue Jan 30, 2025 · 2 comments

Comments

@arno-st
Copy link
Contributor

arno-st commented Jan 30, 2025

Since I have some trouble with flowview at midnight, I decide to disable the plug in.
But still i get this error once in a while in cacti.og:
30/01/2025 07:16:07 - CMDPHP SQL Backtrace: (/plugins/flowview/flow_collector.php[812]:process_fv10(), /plugins/flowview/flow_collector.php[1685]:flowview_db_execute(), /plugins/flowview/database.php[70]:db_execute(), /lib/database.php[420]:db_execute_prepared()) 30/01/2025 07:16:07 - CMDPHP ERROR: A DB Exec Failed!, Error: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ' 0, 0, 'spr-itunes', '', 166, '2025-01-30 07:16:06.0', '2025-01-30 07:16:06.0...' at line 1 30/01/2025 07:16:07 - CMDPHP PHP ERROR WARNING Backtrace: (/plugins/flowview/flow_collector.php[812]:process_fv10(), /plugins/flowview/flow_collector.php[1605]:unpack(), CactiErrorHandler()) 30/01/2025 07:16:07 - ERROR PHP WARNING in Plugin 'flowview': unpack(): Type N: not enough input, need 4, have 1 in file: /usr/share/cacti/plugins/flowview/flow_collector.php on line: 1605
That only do half of the work, So I try to stop flow capture, but even after I did a 'systemctl stop flow-capture.service', all my flow_collector are still running and I have to kill them manualy.

What can I do ?

@TheWitness
Copy link
Member

Post screen shots of your templates. It's likely that we are misprocessing one of them.

@arno-st
Copy link
Contributor Author

arno-st commented Jan 30, 2025

Here it is:

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants