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

Corrupt netflow database #999

Closed
oparoz opened this issue Jun 8, 2016 · 5 comments
Closed

Corrupt netflow database #999

oparoz opened this issue Jun 8, 2016 · 5 comments

Comments

@oparoz
Copy link
Contributor

oparoz commented Jun 8, 2016

This is what I get after a restart on 16.1.16

Jun  8 12:13:59 Empyrion flowd_aggregate.py: flowd aggregate died with message Traceback (most recent call last):   File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 145, in run     aggregate_flowd(do_vacuum)   File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 85, in aggregate_flowd     stream_agg_object.cleanup(do_vacuum)   File "/usr/local/opnsense/scripts/netflow/lib/aggregate.py", line 281, in cleanup     self._update_cur.execute('vacuum') DatabaseError: database disk image is malformed
@AdSchellevis
Copy link
Member

just to be sure, your not using a memory disk? and did the machine restart normally or was there a crash?

@oparoz
Copy link
Contributor Author

oparoz commented Jun 8, 2016

  1. I'm not using a memory disk, but I'm using the RAM disk feature which puts /var and /tmp in RAM
  2. The machine has restarted normally

@AdSchellevis
Copy link
Member

We should add some additional help text, ram disk is usually not a very good idea to store large amounts of data. I will add it to the help text for "Capture local".

@oparoz
Copy link
Contributor Author

oparoz commented Jun 8, 2016

OK. I'll disable it and re-enable it once /var is moved out of the RAM disk then.

@oparoz
Copy link
Contributor Author

oparoz commented Jun 8, 2016

But there may still be a bug in the script which makes a backup of the netflow DB every hour.

fichtner pushed a commit that referenced this issue Jun 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants