| Git Clone URL: | https://aur.archlinux.org/mongodb-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | mongodb-bin |
| Description: | A high-performance, open source, schema-free document-oriented database |
| Upstream URL: | https://www.mongodb.com/ |
| Keywords: | database document-oriented mongo mongod mongodb mongos |
| Licenses: | SSPL-1.0 |
| Conflicts: | mongodb, mongodb-shell-bin |
| Provides: | mongodb |
| Submitter: | ali.molaei |
| Maintainer: | ali.molaei (rafaelff) |
| Last Packager: | ali.molaei |
| Votes: | 89 |
| Popularity: | 1.35 |
| First Submitted: | 2019-01-28 09:01 (UTC) |
| Last Updated: | 2024-04-05 16:13 (UTC) |
MongoDB supports better validation error messages from version 5+ but it seems that it doesn't work when installing MongoDB through this package, when using $jsonSchema validation with big schema it's hard to identify the root cause of the problem.
What do you think is the cause of this?
@aplund: There is the 4.4.x seriers, provided by mongodb44-bin package.
My bad. That's an ARMv8 processor. But that particular instruction requires ARMv8.1.
Is there another binary that supports ARMv8 without the .1 extensions?
My bad. That's an ARMv8 processor. But that particular instruction requires ARMv8.1.
That ARM CPU implementer and part number indicates a Cortex A73, which is a 32 bit ARMv7 part.
I'm getting SIGILL on the aarch64 version 5.0.2. This is the place where it dies:
Dump of assembler code for function _ZNSt6locale5_Impl19_M_remove_referenceEv:
[...]
=> 0x00000055749c9a80 <+16>: ldaddal w1, w1, [x0]
The cpu I'm using hast /proc/cpuinfo showing the cores with:
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd09
CPU revision : 2
Not sure which target the binary is compiled for. But perhaps it doesn't cover my cpu.
Thanks a lot @ali.molaei , now I got it to work fine with the data! I had to first set compatibility to 4.4, while having MongoDB 4.4 running, then I uninstalled it, installed 5.0 and set the compatibility to 5.0, and it all works fine now.
Sorry for the false negative, so my CPU is able to work with the current MongoDB version.
@diogobaeder and also take a backup if you have important data on your mongodb database before doing any upgrades etc
@diogobaeder Looks like you don't have a binary problem, version 5 is running fine for you, but it cannot migrate your database from version 4.2 to 5.0 because of some incompatibility
{"t":{"$date":"2021-08-16T23:40:11.582-03:00"},"s":"F", "c":"CONTROL", "id":20573, "ctx":"initandlisten","msg":"Wrong mongod version","attr":{"error":"UPGRADE PROBLEM: Found an invalid featureCompatibilityVersion document (ERROR: Location4926900: Invalid featureCompatibilityVersion document in admin.system.version: { _id: \"featureCompatibilityVersion\", version: \"4.2\" }. See https://docs.mongodb.com/master/release-notes/4.4-compatibility/#feature-compatibility. :: caused by :: Invalid value for featureCompatibilityVersiondocument in admin.system.version, found 4.2, expected '4.4' or '4.9' or '5.0. See https://docs.mongodb.com/master/release-notes/4.4-compatibility/#feature-compatibility.). If the current featureCompatibilityVersion is below 4.4, see the documentation on upgrading at https://docs.mongodb.com/master/release-notes/4.4/#upgrade-procedures."}}
Invalid value for featureCompatibilityVersiondocument in admin.system.version, found 4.2, expected '4.4' or '4.9' or '5.0.
Take a look at this link: https://docs.mongodb.com/master/release-notes/4.4/#upgrade-procedures
https://docs.mongodb.com/master/release-notes/4.4-compatibility/#feature-compatibility
Hi @rafaelff, thanks for the help! Here's my log for today: http://codepad.org/f7qhQl5i
Pinned Comments
ali.molaei commented on 2021-07-28 14:29 (UTC)
If you get core dumps on version 5, read this: https://jira.mongodb.org/browse/SERVER-58648