[mongodb-3.2.6-1-armv7h] Seems to be broken

[marbi]

Minimal config file:

$this->bbcode_second_pass_code('', 'dbpath = /var/lib/mongodb
logpath = /var/log/mongodb/mongod.log
logappend = true')

$this->bbcode_second_pass_code('', '
2016-05-03T13:33:31.835+0200 I CONTROL [main]
2016-05-03T13:33:31.835+0200 W CONTROL [main] 32-bit servers don't have journaling enabled by default. Please use --journal if you want durability.
2016-05-03T13:33:31.835+0200 I CONTROL [main]
2016-05-03T13:33:31.880+0200 I CONTROL [initandlisten] MongoDB starting : pid=23667 port=27017 dbpath=/data/db 32-bit host=raspberrypi2
2016-05-03T13:33:31.880+0200 I CONTROL [initandlisten] db version v3.2.6
2016-05-03T13:33:31.880+0200 I CONTROL [initandlisten] git version: 05552b562c7a0b3143a729aaa0838e558dc49b25
2016-05-03T13:33:31.880+0200 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016
2016-05-03T13:33:31.880+0200 I CONTROL [initandlisten] allocator: system
2016-05-03T13:33:31.880+0200 I CONTROL [initandlisten] modules: none
2016-05-03T13:33:31.880+0200 I CONTROL [initandlisten] build environment:
2016-05-03T13:33:31.881+0200 I CONTROL [initandlisten] distarch: arm
2016-05-03T13:33:31.881+0200 I CONTROL [initandlisten] target_arch: arm
2016-05-03T13:33:31.881+0200 I CONTROL [initandlisten] options: { storage: { engine: "mmapv1" } }
2016-05-03T13:33:32.026+0200 I STORAGE [initandlisten] exception in initAndListen: 18656 Cannot start server with an unknown storage engine: mmapv1, terminating
2016-05-03T13:33:32.027+0200 I CONTROL [initandlisten] dbexit: rc: 100
')

[glitcher]

I can confirm that the same happens for mongodb 3.2.6-1-armv6h

After the mongodb update to 3.2.6-1 the daemon won't start on any of my machines, it always exit with the following error
$this->bbcode_second_pass_code('', '2016-05-04T08:19:21.752+0000 I CONTROL [initandlisten] options: { config: "/etc/mongodb.conf", net: { bindIp: "127.0.0.1" }, storage: { dbPath: "/var/lib/mongodb", engine: "mmapv1" }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log", quiet: true } }
2016-05-04T08:19:21.963+0000 I STORAGE [initandlisten] exception in initAndListen: 18656 Cannot start server with an unknown storage engine: mmapv1, terminating
2016-05-04T08:19:21.963+0000 I CONTROL [initandlisten] dbexit: rc: 100
')

if i remove the storageEngine config from /etc/mongodb.conf it seems to automatic detect the storage engine but it will still fail
$this->bbcode_second_pass_code('', '2016-05-04T08:25:42.471+0000 I CONTROL [initandlisten] options: { config: "/etc/mongodb.conf", net: { bindIp: "127.0.0.1" }, storage: { dbPath: "/var/lib/mongodb" }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log", quiet: true } }
2016-05-04T08:25:42.653+0000 I - [initandlisten] Detected data files in /var/lib/mongodb created by the 'mmapv1' storage engine, so setting the active storage engine to 'mmapv1'.
2016-05-04T08:25:42.655+0000 I STORAGE [initandlisten] exception in initAndListen: 18656 Cannot start server with an unknown storage engine: mmapv1, terminating
2016-05-04T08:25:42.655+0000 I CONTROL [initandlisten] dbexit: rc: 100
')

Any possible solutions? I assume it must be a general thing as i get the same error on 2 machines that i am using.

Opened a thread in armv6 subforum as well do not know if it is worth it viewtopic.php?f=59&t=10238

[TPXP]

I have the same problem on my ARMv7 board, which is caused by a change in storage engines. In short, 3.2 introduced wiredTiger, which is now the default storage engine and replaces mmapv1. However, as we run a 32-bit build, wiredTiger is not available. Therefore, we have to stick to mmapv1.

Normally, mmapv1 is included in 32-bit builds (which is the one we use). However, 3.2.5 decided to drop mmapv1 from default non-x86 builds, as shown in this commit. By default, MongoDB enables mmapv1 if the architecture is an x86 target, which is not the case of our ARM board. Consequently, MongoDB ends up with no storage engine being compiled in, and fails to start.

It is possible to force MongoDB to include mmapv1 in our builds through a scons flag, but this was not added when switching to 3.2.5. I have opened a pull request to fix it.

[CreativeWolf]

Hi @TPXP

Thank you for the quick response. Been trying to get MongoDB on my Pine64 and same issue.

Now that your PR has been merged, please let me know what I'd have to do, to get the changed version installed.

Appreciate your help!

Thanks

[TPXP]

The pull request was indeed merged, and the package was build correctly as shown in the build log. Now we just have to wait for the built package to make its way to the mirrors, which may take up to a few hours.

Just run "pacman -Syu", and it will propose you the updated package as soon as it is available.

EDIT : It should be OK now.

[CreativeWolf]

@TPXP Thank you! Will wait for it! =)