On Tue, Apr 23, 2024 at 09:42:26AM +0100, Stuart Henderson wrote:
> On 2024/04/22 23:26, Zé Loff wrote:
> > 
> > Hi all
> > 
> > After upgrading an amd64 machine to 7.5-stable, influxdb fails to start,
> > saying:
> > 
> > 2024-04-22T22:07:42.599907Z     info    Welcome to InfluxDB {"log_id": "0oiySb1l000", "version": "2.7.3", "commit": "none", "build_date": "2024-04-22T22:07:42Z", "log_level": "info"}
> > 2024-04-22T22:07:42.601348Z     error   Failed opening bolt {"log_id": "0oiySb1l000", "error": "function not implemented"}
> > 
> > Starting with a clean /var/influxdb doesn't help, nor does doing it as
> > root (which also starts with a clean slate, at /root/.influxdbv2).
> > Removing and reinstalling the package didn't help either.
> > 
> > Has anyone else seen the same thing and/or has any advice?
> > 
> > Thanks in advance
> > 
> > -- 
> >  
> > 
> 
> OpenBSD was changed so that syscalls can only be made by libc. However
> some software (especially software written in Go) still relies on being
> able to call syscalls directly from the main program and this will no
> longer run on OpenBSD.
> 
> One of the go modules used by influxdb is an old version of bbolt.
> This problem is fixed in an update to bbolt, but even the most recent
> influxdb release (2.7.6) still uses an old bbolt from before the fix.
> 
> Some other modules may have a problem too (influxdb uses
> modernc.org/sqlite which definitely used syscall in some use cases; I'm
> unsure if that got fixed or whether influxdb's use of it triggers those
> cases).
> 
> I'm not too familiar with influxdb but it seems bolt/bbolt is a required
> part of it, so I think we might as well mark it broken for now, it's not
> going to magically start working unless changes are made.
> 

Thanks Stuart, and everyone else who looked into it.  I thought it'd be
syscall-related.  I'll just throw it into a VM running 7.4 for the time
being.

--