Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - michelvankessel

#1
did some investigation. When I run the command manually I see the following error

root@firewall:/var/db/aliastables # /usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py
Traceback (most recent call last):
  File "/usr/local/opnsense/scripts/filter/update_tables.py", line 131, in <module>
    alias_content = alias.resolve()
  File "/usr/local/opnsense/scripts/filter/lib/alias.py", line 241, in resolve
    self._resolve_content = self._resolve_content.union(self._dnsResolver.collect().addresses())
  File "/usr/local/opnsense/scripts/filter/lib/__init__.py", line 134, in collect
    asyncio.run(self.request_ittr(loop))
  File "/usr/local/lib/python3.8/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/local/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "/usr/local/opnsense/scripts/filter/lib/__init__.py", line 97, in request_ittr
    dnsResolver = Resolver()
  File "/usr/local/lib/python3.8/site-packages/dns/resolver.py", line 734, in __init__
    self.read_resolv_conf(filename)
  File "/usr/local/lib/python3.8/site-packages/dns/resolver.py", line 826, in read_resolv_conf
    raise NoResolverConfiguration
dns.resolver.NoResolverConfiguration: Resolver configuration could not be read or specified no nameservers.

I noticed I didn't have any resolver configured under system > settings > general, after adding the local firewall IP as DNS resolver, it worked!

#2
Hi,

Just noticed NEW aliases are not working. Any ideas how to solve this?

The following message is visible

Script action failed with Command '/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py ' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 478, in execute subprocess.check_call(script_command, env=self.config_environment, shell=True, File "/usr/local/lib/python3.8/subprocess.py", line 364, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '/usr/local/bin/flock -n -E 0 -o /tmp/filter_update_tables.lock /usr/local/opnsense/scripts/filter/update_tables.py ' returned non-zero exit status 1.
#3
20.1 Legacy Series / Re: 20.1.4 - ntopng
July 04, 2020, 12:56:57 PM
I can confirm, after upgrade to 20.1.8 CPU load is way better.
#4
20.1 Legacy Series / Re: 20.1.4 - ntopng
June 17, 2020, 04:21:24 PM
Quote from: mimugmail on June 15, 2020, 06:13:16 PM
Upstream patch is available, couple of weeks to go

Thank you for the update!
#5
20.1 Legacy Series / Re: 20.1.4 - ntopng
June 15, 2020, 05:57:04 PM
fyi - 20.1.7 same issue.
#6
20.1 Legacy Series / Re: 20.1.4 - ntopng
May 09, 2020, 08:47:00 PM
reinstalled ntopng and redis and now running 20.1.6.

but also with clean install and  "opnsense-revert -r 20.1.3 ntopng" I keep getting similar errors and the process ends

2020-05-09T20:44:12   kernel: pid 99966 (ntopng), uid 288: exited on signal 11
2020-05-09T20:40:31   kernel: -> pid: 99966 ppid: 1 p_pax: 0xa50<SEGVGUARD,ASLR,NOSHLIBRANDOM,NODISALLOWMAP32BIT>
2020-05-09T20:40:31   kernel: [HBSD SEGVGUARD] [ntopng (99966)] Suspension expired.

Does anyone know what I am doing wrong?
#7
20.1 Legacy Series / Re: 20.1.4 - ntopng
April 25, 2020, 06:36:46 PM
I did a revert.. ntopng starts, but fails after a few minutes and I get the following in the logs

2020-04-25T18:22:12kernel: pid 29452 (ntopng), uid 288: exited on signal 1120
20-04-25T18:20:47kernel: -> pid: 29452 ppid: 1 p_pax:0xa50<SEGVGUARD,ASLR,NOSHLIBRANDOM,NODISALLOWMAP32BIT>
2020-04-25T18:20:47kernel: [HBSD SEGVGUARD] [ntopng (29452)] Suspension expired.

running 20.1.5 and reverted using "opnsense-revert -r 20.1.3 ntopng"

any ideas?
many thanks for your help