Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: Sprint 4.1.2
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Chapter:Data
-
HD-Enabler:Orion
Description
Responsible:
Bitergia team
Description:
Installing Orion Context Broker in a VM image (CentOS63) returns the following error:
MongoGlobal.cpp[111]: Database Startup Error (cannot connect to mongo - doing 100 retries with a 1000 microsecond interval)
The problem is that the image doesn't have enough space for mongodb. The guide doesn't state any information regarding the space requirements, and it should be added in order to avoid this error. In this case, with 5GB wasn't enough.
A solution to this problem is to enable smallFiles in mongodb configuration file.
Tested GE(s):
Orion Context Broker
Environment:
FIWARE Lab
Instance:
Image Name: CentOS-6.3init
Flavor: m1.small
Alberto Martín
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-tech-help
Activity
Second choice. I've created a new instance of the image CentOS-6.3init. The procedure was the following:
- Create a new instance CentOS-6.3init with flavor m1.small (actually the biggest flavor I can choose).
- Added testbed-fi-ware.repo and mongodb.repo
- Installed the packages needed as described in the guide using yum (including contextBroker)
- Updated pcre package in order to avoid mongodb crash
- Start mongodb with: service mongod start (with OK response)
- Start contextBroker. At this point is where we get the error explained above.
- Adding smallFiles=true into /etc/mongod.conf and restarting mongodb allows us to start contextBroker without any issues.
MongoDB installation (and knowledge) is out of the scope of Orion documentation. We don't explain how to install or configure MongoDB (10gen documenation is pretty well for that), in the same way we don't explain how to install or configure the CentOS base operating system in which Orion runs. Moreover, it could even happen that you don't need either manage MongoDB at all if you have access to some MongoDB endpoint (outside the host were Orion is installed) such as the ones provided by MongoLab (https://mongolab.com/).
Having said that, one of the benefits of using the orion-psb-image-Rx.y VM image is that you get Orion CB with a MongoDB "out-of-the-box" to be used, lowering your need to know how MongoDB is installed or work in general.
In order to fully understand the case, which installation option did you follow, please?