| Table of Contents |
|---|
Installation issues
MongoDB doesn't install
| Table of Contents |
|---|
Installation issues
MongoDB doesn't install
This is usually caused by an incorrect "/opt/infinite-install/conf/infinite.configuration.properties". Note the install may take up to 30 minutes to fail out if it is waiting for other components to start.
...
I upgraded MongoDB to 2.4 and everything stopped working!
MongoDB introduced lots of breaking changes between 2.3 and 2.4. Although it is desirable to use MongoDB 2.4 for new installations, older installations should remain at 2.2.3 for the moment (until I can come up with instructions for upgrading clusters). If you have already installed 2.4 and are running into problems like "ERROR: error upgrading config database to v4 :: caused by :: newer version 4 of mongo config metadata is required, current version is 3, need to run mongos with --upgrade", then don't panic: it is easy to return to the old version:Downgrade back as described below, and then follow the instructions for upgrading.
- yum -y downgrade mongo-10gen-2.2.0-mongodb_1; yum -y downgrade mongo-10gen-server-2.2.0-mongodb_1;
- (If you were previously running 2.2.0 and just want to get everything back the way it was!)
- (If you were previously running 2.2.0 and just want to get everything back the way it was!)
- OR:
- yum -y downgrade mongo-10gen-2.2.3-mongodb_1; yum -y downgrade mongo-10gen-server-2.2.3-mongodb_1;
- (If you were previously running 2.2.3 or are feeling adventurous)
...
I upgraded MongoDB to 2.6 and everything stopped working!
We are not currently compatible with 2.6 (they've changed a few startup scripts) - downgrade back to 2.4 (or whatever version you were stably running - see above) and restart everythingDowngrade back as described above, and then follow the instructions for upgrading.
Installation via "yum" no longer works!
...
Yum returns the error "Package does not match intended download. Suggestion: run yum --enablerepo=<reponame> clean metadata"
...
Elasticsearch fails to start, "The stack size specified is too small, Specify at least 160k"
This happens if Java7 is the default - eg "/usr/java/default" is a symbolic link that points (likely via /usr/java/latest) to something like "/usr/java/jre1.7.0_13". Unfortunately a number of Infinit.e components, including elasticsearch 0.19, are not currently compatbile with Java 7.
...
It is also possible that this could be caused by restarting the DB without restarting the interface engine (eg the error "can't call something : /127.0.0.1:27017/social" from the "ping/ping" trick) - if so simply restart all the interface engines.
...
Harvesting
My source won't harvest
SourcesSource Editor GUI, use the "test" button to see if anything is returned. (This also returns more verbose errors in some cases).
Use the source monitor (<root>/InfiniteSourceMonitor.html), or the Sources Source Editor GUI, or one of the REST calls "config/source/get", "config/source/user". "config/source/good".
Check out the harvest object of the source object:
- If the "harvest_status" is "in_progress", then either the harvest is ongoing or (less likely) the harvester has shut down uncleanly while the harvest was ongoing. In the first case, the harvested documents should be available soon. In the latter (less likely) case, you may need to wait for a day
- If "harvestBadSource" is set to true, then the source has been disabled due to source-level errors: it is probably not working.
- If "isApproved" is set to false, then either the source has been automatically disabled
- If "harvest_status" is "error" (or even "success" but no documents have been harvested): check the "harvest_message", it is possible that some non-fatal error due to source misconfiguration is occurring.
- If the "harvest" object does not exist
...
I published a source and it just vanished!
Earlier versions of the Source Editor had a nasty tendency to do this if the JSON was invalid, but this has been fixed as of the June 2013 release (together with the addition of a built-in JSON validator and many other goodies).
...
The "admin.email" and "admin.password" parameters in the central "/opt/infinite-install/config/infinite.configuration.properties" are only read on install. To change the email addresses and passwords of any users post install, use the People tab of the Manager webapp.
I changed the configuration in one of the properties files in /opt/infinite-home/config and later the change was overwritten
...