Flowview Plugin: Errors on service start.

[GingerConker]

Hiya, apologies if this is the wrong place to post about this.

I have been trying to get the Flowview plugin to work on my Cacti server.
I have gone through this process multiple times in terms of trying to install the plugin.
This time the errors are the worst they have been with them turning off the plugin as soon as I have started the Flow Capture service.

I have tried to google the errors but have not found anything that relates to Cacti and the Plugin.
I have attached images of the errors I receive in the Cacti.log file

I would appreciate it if anyone could give me a hand or point me in the right direction to resolve these errors please.

Server specs:
OS: Ubuntu 18.04
PHP: 8.1.9
MariaDB: 10.1.48
Cacti: 1.2.22
Flowview: 3.3
(Please let me know if i missed anything out that could be helpful)

[TheWitness]

Are you running the latest develop release of FlowView. What device and what flow version?

[GingerConker]

Flowview is running the v3.3 release from 25 Sep 2021, with the Development branch version of flow_collecter.php and flowview_devices.php for the PHP fixes.

The device is a Sophos UTM 9.

I am having trouble finding the Flow Version, if you are referring to whether it is using IPFIX or NetFlow it uses IPFIX. If not then the most I have to go on is in one of the errors it refers to process_fv10.
As I have not been able to find any documentation that refers to Flow Version for Sophos UTM 9.

[TheWitness]

The flow capture service should detect the version just fine.

[TheWitness]

We could code around these errors, but it would be better to know the reason for them. See if the unit supports v5. That collector is super stable (as it's simple). Also, grab the latest development branch. There have been many fixes since the release.

[GingerConker]

I have updated the plugin to use the Development branch.
I have included the errors that happen on start up.

Apologies
I don't know how to change the plugin to try V5
I also don't know where the Service would show the version the device is using.

[TheWitness]

Contact the vendor, otherwise, to fix it, we will have to do an online debugging session, and I pretty much only do such things on the weekends and evenings EDT.

[GingerConker]

Thank you for your time.

I will do a longer investigation to see if the device can support V5 and see if that fixes the problem.
Unfortunately due to our time zone differences the debugging session would not be possible.

[TheWitness]

What time zone are you in? I would like to spend more time debugging, it's just that there is only so much time in a day, and time goes faster as you ripen/age.

[GingerConker]

Currently UTC +3:00

[TheWitness]

Some somewhere in eastern Europe or the heartland of the globe?

[GingerConker]

Yes, operating out of Finland.

[TheWitness]

You are not that far off then. I get up early, and could do a morning session. But right now, I'm contemplating a long drive to help my brother-in-law with his serious/terminal illness. So, it's a bad time.

[TheWitness]

Most devices offer a v5 option. Just let us know.

[GingerConker]

Apologies, for the delayed reply.

From what I could find the Sophos UTM does use v5.

However I was asked to blow away the VM and reinstall everything. Latest Cacti version and development Flowview.
This time around sticking to php7.4
This main issue of the plugin not working on start up has not reappeared.

However a few errors are still present. I have attached a screen shot.
When the Flow Capture service runs, it seems to be working fine except for filling the error log with the following/variations:
FLOWVIEW Flow: Unnatural end of packet at position 1640. Bad header length

After commenting out the section in flow_collector.php to prevent the log file from being filled with the message.
It continues to work for a short amount of time between 5 to 10 minutes then fills the log with the messages in the screenshot.

Sorry, I know you wanted to have a look at the initial issue.