OpenVASsd complains about undefined symbol "nvtpref_id" right after starting

The error seen is:

# /usr/local/sbin/openvassd --foreground
/usr/local/sbin/openvassd: symbol lookup error: /usr/local/sbin/openvassd: undefined symbol: nvtpref_id

No compile errors at all.

GVM Versions

gsad:

8515731d3 2019-03-11 | Merge gsa-8.0 into master (HEAD -> master, origin/master, origin/HEAD)

Greenbone Security Assistant 9.0+alpha~git-8515731d3-master
GIT revision 8515731d3-master
Copyright (C) 2010-2016 Greenbone Networks GmbH
License GPLv2+: GNU GPL version 2 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

gvmd:

593f6784 2019-03-19 | Merge pull request #426 from mattmundell/flag-nvti-cache-update-later (HEAD -> master, origin/master, origin/HEAD)

Greenbone Vulnerability Manager 9.0+alpha~git-593f6784-master
GIT revision 593f6784-master
Manager DB revision 207
Copyright (C) 2010-2017 Greenbone Networks GmbH
License GPLv2+: GNU GPL version 2 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

openvassd:

358a3ec 2019-03-21 | Merge pull request #285 from kroosec/mainloop-timeout (HEAD -> master, origin/master, origin/HEAD)


gvm-libs:

507ff3a3 2019-03-22 | Free unused heap memory after hosts creation and deduplication. (HEAD -> master, origin/master, origin/HEAD)

gvm-tools:

f1d4302 2019-03-13 | Merge pull request #181 from jjnicola/cache-check-gmp (HEAD -> master, origin/master, origin/HEAD)

node:

v11.12.0

redis-server:

Redis server v=5.0.3 sha=00000000:0 malloc=jemalloc-5.1.0 bits=64 build=355ed63f25401f51

Environment

Operating system:

Linux gvm10 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux
Debian testing (buster/sid)

Installation method / source:

source installation, git checkout

I’m quoting myself:

Please note that the github master branches are development versions not officially released and where all the development is happening. Such versions might show unexpected behavior or could even break/be in a temporary unusable state at any time.

For productive use it is strongly suggested to stay with the official announced source code releases in About the Greenbone Community Edition category - Greenbone Community Edition - Greenbone Community Forum.

If you want to contribute to the development of those you probably need to dig into such issues on your own and could consider to contribute at the issue trackers of github: Greenbone · GitHub

As no help for such development versions should be given in this community portal i’m closing this thread.

Please switch to the stable branches as advised or try again in a few days / with a fresh git checkout of all branches.