Panic, unhandled command "buildinfo" for collection "admin.$cmd" about ferretdb HOT 3 OPEN

According to https://www.mongodb.com/docs/drivers/java/sync/current/compatibility/, Java driver 3.4 supports MongoDB 3.4 at most. FerretDB is compatible with MongoDB 5.0+. More specifically, MongoDB 3.6 introduced a new type of wire protocol message OP_MSG that we implement; we mainly don't support older message types. I don't think there is an easy way for us to support that version, sorry.

That being said, becoming compatible with Unifi Controllers is something we are interested in, so let's keep that issue open.

from ferretdb.

Hi, I think I've managed to do some steps regarding this issue.

NixOS unifi module, by default, uses the 5.14.23 version of the controller. The newer versions of the controller support the more up-to-date versions of the protocol:

UniFi Network Application 7.5 and newer requires MongoDB 3.6 and Java 17.
Version 7.5 till 8.0 supports up to MongoDB 4.4.
Version 8.1 and newer supports up to MongoDB 7.0.

I've tested FerretDB compatibility against the latest Unifi controller version by using services.unifi.unifiPackage = unifi8 and have managed to properly pair my access point, and do basic configuration with no issues.

I started working on modifying the NixOS module to optionally allow specifying the database URL, although I'm still not sure how to handle creation of system.properties file. It seems to me that both the file and it's parent data directory are mutable and can be modified by the service. It seems to take all of the user-set parameters, change the order, and set additional ones like reporter-uuid, or uuid.

from ferretdb.

I just stumbled into the same problem whilst testing ferretdb together with the unifi controller.

from ferretdb.