sending datagram to 10.1.1.93:53 failed (on startup)

[bongo]

whenever rebooting OPNsense (running on a pc x86 hardware), i get a few lines of
"sending datagram to 10.1.1.93:53 failed: Invalid argument".

since i updated to OPNsense 22.7.6-amd64, this message is now repeaded for a few pages instead of just a few lines.
where does this message come from? can this just be ignored?

10.1.1.x is one of my local networks behind OPNsense and 10.1.1.93 is within it's dynamic DHCP range, but there's no device with this IP address. so i really wonder what OPNsense tries to do...

[franco]

Unbound trying to contact this server perhaps? Can you publish your /etc/resov.conf or grep for 10.1.1.93 in /conf/config.xml:

# grep 10.1.1.93 /conf/config.xml


Cheers,
Franco

[bongo]

hi franco

it really helps if you know where to look for ;-)

/etc/resov.conf
contains nothing suspicious, but in
/conf/config.xml
i found this IP in the list, defined as targets for netflow
(<targets>10.1.1.93:53,127.0.0.1:2056</targets>).

i can't remember that i have ever used netflow (don't really know what to do with it), so i have no idea how this came in. after deleting this IP from the config, the issue is gone.
so i think that's fine now ;-)

but as i can see now lots of other messages instead, there are two errors shown:

Error in early script 'templates'
and
Error in start script 'c-icap'

are these messages expected or do i need to change anything to get rid of those errors?

thanx very much for your help!

[franco]

Can you also post the errors preceding these messages? The parent script just says it errored out but doesn't know why.


Cheers,
Franco

[bongo]

sorry for sending not enough infos!

Generating configuration configd socket missing (@/var/run/configd.socket)
>>> Error in early script 'templates'

and

c_icap already running? (pid=78301).
>>> Error in start script 'c-icap'

[franco]

First issue is basically https://github.com/opnsense/core/pull/6012 but we wanted to see if we could fix it from the other side so it hasn't been included yet. There is nothing that goes wrong because of this error from what information we have gathered so far.

For clamav error this is actually a failsafe for proper service start on boot. The error happens because we want to "start" clamav in case it wasn't already started. The FreeBSD rc framework, however, sees this as an error and prints that message. Yet the service runs fine.


Cheers,
Franco

[bongo]

ok, so this means that everything is fine, right?

THANK YOU VERY MUCH!!!

[franco]

Yes.

For your original issue port 53 had me scratching my head for NetFlow use... Maybe it was a cut+paste error during configuration.


Cheers,
Franco

[bongo]

hm. i did all my config in the web gui and i can't remember to ever have used netflow.
...but at least it's fixed now ;-)