-
Notifications
You must be signed in to change notification settings - Fork 10
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
CMDPHP Column with field id 34 Does not exist for V4 flow template #138
Comments
What hardware vendor and device type is this? What is the streams flowview version (v9 or IPFIX)? We have been making heavy changes to the plugin. You might also want to consider downloading a fresh copy. |
Edit the listener, and then go to the Templates tab and take a screen grab and upload it. |
I'll be committing a change shortly. You might want to grab that and do an upgrade too. I'll post here once it's done. |
I suspect you have a protocol filter in place. Let me verify that this is working. |
Grab the latest copy and of the plugin and then let's see what other errors are going on. Note that in Template 256, there is no Flow ID: 45, but there is for Template 258. The reason that we are glad you are here is that we are trying to identify the minimal subset of Field ID's that constitute a full 'common' schema, and your Template 256 for that Cisco device tells us something new. |
Sorry, I don’t quite understand what I need to do and how to select this Template |
Download a fresh copy of the plugin, then: php -q flowview_upgrade.php --forcever=3.3
systemctl restart flow-capture |
The protocol errors should go away afterwards. You may see some errors when you update the plugin, but they should be transient. |
Take a fresh pull and those 'Column with field id' warnings should go away. |
Did you not update to the latest develop? Field 34 is no long required. You will have to restart flow-capture though... |
Closing this one. If you still get those errors (not the 34 but the other ones), open a new ticket. |
Ope, I know what the other issue is now. Stop using your own DNS and use local DNS for the moment. I have to fix some buggy code there. I'll open the ticket separately. |
New bug here: #141 |
These kinds of errors still pop up quite often.
The text was updated successfully, but these errors were encountered: