I updated our Ubuntu VM running pritunl server to Ubuntu Noble Numbat 24.04. Pritunl was not starting and I could not locate the service, and so I attempted to reinstall it.
According to the compatibility matrix here, it is not sure MongoDB 7.0 will be ported on ubuntu 24.04.
Any chance to migrate pritunl server on MongoDB 8.0 which is already supported ?
Pritunl will already support MongoDB 8, the PyMongo library has also been refactored to the latest v4 release. This will further improve compatibility with future MongoDB releases. Currently there are no MongoDB releases for 24.04.
Is the Pritunl package in the unstable repo only there because of the MongoDB issue, or does it have other stability issues? Keeping it out because of that also kind of hinders a setup that runs Pritunl on 24.04 but a separate database server on 22.04 (or any other distro). There’s also the Docker container route.
I personally use the Percona build of MongoDB, as they tend to have much wider support for different Ubuntu releases and MongoDB versions.
It’s in the unstable repository because there is another issue with DNS search domains introduced in that release. If it were moved to stable it would cause problems with all the distributions. A new release can’t be done currently because the pyMongo v4 refactoring hasn’t been fully tested.
I’ve never tested Percona but many of the MongoDB API compabiltle database are missing capped collections and tailable cursors. This is used for the inter-host messaging and events in Pritunl.
I did test the Pritunl 24.04 build and MongoDB 22.04 build on Ubuntu 24.04 and there were no issues. Below is the commands to install Pritunl on Ubuntu 24.04.
I’m a little confused. You said the build in the unstable repo has an “issue with DNS search domains introduced in that release”, but then you said you did a test with that build on Ubuntu 24.04 and there were no issues. Do you mean there were no issues outside of that DNS search domain issue? I ended up installing Pritunl unstable on Ubuntu 24.04 with Percona MongoDB 5 (we’re upgrading from a older machine, so minimizing the version changes right now), and my initial basic tests seemed fine (web interface worked and I could connect via OpenVPN and properly route traffic). I’m not sure how the DNS search domain issue might affect it.
A quick note on the Percona builds. From my understanding, they are not just “API compatible” builds. They are actually based on the MongoDB source code with some enterprise related enhancements.
Yes there is no issues other than the DNS search domain. This option is labeled DNS Search Domain in the server settings, this option will not work on that release.