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

Latest Dev version, process are not registered inside DB Table processes, so can't stop them #226

Open
arno-st opened this issue Jan 6, 2025 · 1 comment

Comments

@arno-st
Copy link
Contributor

arno-st commented Jan 6, 2025

I have an issue with flow capture:
Each listener should be registered inside the DB of cacti on the table 'processes'. If I read the code right.
That's the reference when you do a flow-capture.service stop or restart.
It look into the DB and take the pid to kill it.

But on the current version the processes table is empty, and every time I do a restart, or a stop/start I have a bunch of new flow_collector.php, but since the socket is used by the old process nothing is working anymore.
I have to kill every flow_collector by hand then I can do a restart.

I didn't find anyway where this table is populated!

@arno-st
Copy link
Contributor Author

arno-st commented Jan 6, 2025

Oups actually they are registered.

But when try to stop flow-capture, only the flowview master is removed from the DB

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

1 participant