Messages

@rainerle thanks for the tip!  i'll have to try it next time.

I guess call it a lack of understanding on my part.  I don't know much about the innerworkings of opnsense, thought maybe this was a bug since i was seeing the same thing as emiletenhagen.  Sorry  :-[

Checked today and still see the file name to long message.  Running 19.7.3.  Is anyone else seeing this? 

Code Select Expand

root@firewall:~ # /usr/local/opnsense/scripts/filter/lib/geoip.py
/usr/local/opnsense/scripts/filter/lib/geoip.py:
    Copyright (c) 2016-2019 Ad Schellevis <ad@opnsense.org>
    All rights reserved.

    Redistribution and use in source and binary forms, with or without
    modification, are permitted provided that the following conditions are met:

    1. Redistributions of source code must retain the above copyright notice,
     this list of conditions and the following disclaimer.

    2. Redistributions in binary form must reproduce the above copyright
     notice, this list of conditions and the following disclaimer in the
     documentation and/or other materials provided with the distribution.

    THIS SOFTWARE IS PROVIDED AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
    INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
    AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
    AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
    OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
    SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
    INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
    CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
    ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
    POSSIBILITY OF SUCH DAMAGE.

    --------------------------------------------------------------------------------------
    download maxmind GeoLite2 Free database into easy to use alias files [<COUNTRY>-<PROTO>] located
    in /usr/local/share/GeoIP/alias
: File name too long
/usr/local/opnsense/scripts/filter/lib/geoip.py: import: not found
/usr/local/opnsense/scripts/filter/lib/geoip.py: import: not found
/usr/local/opnsense/scripts/filter/lib/geoip.py: import: not found
/usr/local/opnsense/scripts/filter/lib/geoip.py: import: not found
/usr/local/opnsense/scripts/filter/lib/geoip.py: import: not found
/usr/local/opnsense/scripts/filter/lib/geoip.py: import: not found
/usr/local/opnsense/scripts/filter/lib/geoip.py: import: not found
/usr/local/opnsense/scripts/filter/lib/geoip.py: 38: Syntax error: "(" unexpected


When I run the command, nothing happens.  I let it sit for 10 15 minutes and if I press Ctrl C, this is the output

Code Select Expand

Traceback (most recent call last):
  File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 224, in <module>
    Main()
  File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 136, in __init__
    self.run()
  File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 179, in run
    time.sleep(0.5)
KeyboardInterrupt


Thanks :)  I'll try flushing stats and see what happens.  Will keep you posted.

Upgraded to 19.7.3 and did a "Repair Netflow Data" but still no go.  Output from flowd_aggregate.py --console:

Code Select Expand


  File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 224, in <module>
    Main()
  File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 136, in __init__
    self.run()
  File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 160, in run
    aggregate_flowd(self.config, do_vacuum)
  File "/usr/local/opnsense/scripts/netflow/flowd_aggregate.py", line 80, in aggregate_flowd
    stream_agg_object.add(copy.copy(flow_record))
  File "/usr/local/opnsense/scripts/netflow/lib/aggregates/ports.py", line 71, in add
    super(FlowDstPortTotals, self).add(flow)
  File "/usr/local/opnsense/scripts/netflow/lib/aggregates/__init__.py", line 185, in add
    self._update_cur.execute(self._update_stmt, flow)


I'm thinking mine might just be plain broke and a reinstall will fix it.  Is there anything else I can try before attempting a reinstall?

How do I start the service from the console window?  When I run the command

Code Select Expand

/usr/local/opnsense/scripts/netflow/flowd_aggregate.py --console

the output is similar to what spetrillo posted previously.  I'm wondering if I should be running a different command?  thanks

@AdSchellevis, Unfortunately no luck.  The service stopped again.  Is there anything else I can try or provide in terms of logs?  I'm not against performing a fresh install to fix the problem but if this is a bug, I would not mind help trying to fix it.

@spetrillo, did you have any luck with the patch? 

Thanks AdSchellevis.  I ran the same command and got a similar result as spetrillo.  I've applied the patch and did a repair Netflow from the web GUI.  Will keep an eye on it and see if the service continues to stop or not.

Seeing the same thing here.  As a test, I did a fresh install of OPNsense in a VM and the flowd_aggregate has been running for days.  I'm wondering if it is something with my config. 

Hi emiletenhagen

I see the same thing about the file name being too long when I ran geoip.py script

My issue reported in this thread about data not showing seems to have been resolved by running the Repair Netflow Data a second time.  However, I am seeing the service stop by itself as reported in the thread from my previous post so something else is going on.  Will keep an eye on the other thread.   Thanks bartjsmit!

I agree.  Checked today and found the flowd_aggregate service stopped.  Also seeing similar errors.  Not sure what could be going on.

Hi Taomyn,  I think dropped inbound connections are logged by default.  When opening the Live Log, I see connection attempts from the Internet and I did not create any rules for inbound traffic.

Update to this, it might be fixed.  Per this thread, https://forum.opnsense.org/index.php?topic=13711.0 , I re-ran Repair Netflow Data again today after seeing the service was stopped, and reports seem to be working again.  Going to keep an eye on it for the next few days to be sure.