On 2021/02/17 16:37, Tom Smyth wrote:
> Hello,
>
> I have noticed fastnetmon on OpenBSDamd64 can stop after a couple of
> weeks Im trying to get more info,
> but there doesnt seem to be anyhting in /var/log/daemon or /var/log/messages
>
> in an earlier release I had modified /etc/rc.d/fastnetmon (because of
> a directory that was not being created at start up (which has been
> since corrected by Stuart@ (thanks) but I think the mg created
> backup fastnetmon~ may have caused me issues then
>
> I noticed the following in insecurity
> that Services that should be running but aren't:
> /usr/sbin/rcctl: ${cached_svc_is_special_fastnetmon~}: bad substitution
> /usr/sbin/rcctl: set: cached_svc_is_special_fastnetmon~: is not an identifier
> /usr/sbin/rcctl: ${cached_svc_is_base_fastnetmon~}: bad substitution
> /usr/sbin/rcctl: set: cached_svc_is_base_fastnetmon~: is not an identifier
> /usr/sbin/rcctl: ${cached_svc_is_meta_fastnetmon~}: bad substitution
> /usr/sbin/rcctl: set: cached_svc_is_meta_fastnetmon~: is not an identifier
>
> im presuming this is because /etc/rc.d/fastnetmon~ backup file was
> in /etc/rc.d/fastnemon
Yes that is the reason. The daily script uses "rcctl ls failed" which
runs through all /etc/rc.d files.
> does anyone have an idea why the fastnetmon would suddenly stop
> working (the machine had plenty of ram, (perhaps newsyslog) ?
> anyway I have deleted /etc/rc.d/fastnetmon~ and we will take it from there
I would guess probably crashing due to a bug (segfault or something).
There are a few issues open on
https://github.com/pavel-odintsov/fastnetmon/issues
relating to crashes. Some have workarounds e.g.
https://github.com/pavel-odintsov/fastnetmon/issues/890#issuecomment-734857957
but not really fixed, others not at all.
Even if fixed though, the port is at a bit of an impasse. Newer
fastnetmon versions want to build with a specific version of boost, a
specific version of gcc, a specific version of openssl, etc and at least
for some of these it's hard to disable. It might be possible to get
working but it will need someone who is fairly committed to wanting to
use it specifically on OpenBSD with a bunch of time.
Realistically the approach with a highest chance of working is probably
to run a newer version on Linux and, if crashes still occur, work with
upstream to debug it.
