I am new to Mongodb. I'm running a Mongodb 3.6 services on Openshift.
I found that it keeps generated something looks like backup in the folder /var/lib/mongodb/data/.snapshot.
It's not small in size. But, I can't remove it. Does anyone have any idea?
It turns out that it's due to the snapshot created by NetApp. We need to re-configure the snapshot policy.
Related
I am trying to connect mongodb data to neo4j.
I tried with this code "CALL apoc.mongodb.get('mongodb://localhost:27017','test','test',{name:'testDocument'})" in Neo4j.
But I get an error as
There is no procedure with the name apoc.mongodb.get registered for this database instance. Please ensure you've spelled the procedure name correctly and that the procedure is properly deployed.
I had added APOC jar files in Neo4j plugins and I gone through this link http://indexoutofrange.com/Neo4jStoredProceduresWindows/
still Iam unable to connect.
can someone please explain what shall i do to get this started.
Thanks
In addition to copying the APOC jar file to $NEO4J_HOME/plugins you'll also need to copy the mongo specific jar files into $NEO4J_HOME/plugins. For example:
mvn dependency:copy-dependencies
cp target/dependency/mongodb*.jar target/dependency/bson*.jar $NEO4J_HOME/plugins/
More information available in the docs here
I know this was made 5 years ago but this is for anyone else (like myself) who's looking for an answer.
The URI should look something like this:
CALL apoc.mongo.find("mongodb://localhost:port/databaseName.collectionName")
Help is requested to delete a database I have created in TYPO3 setup.
I have installed XAMPP in Ubuntu 16.04 and configured it correctly and it runs. Now I was in the process of configuring TYPO3 in XAMPP using this very good guide.
After creating the "typo3cms" database, the next stage asked for a user name and password. I think I was supposed to put in my Ubuntu username and password, but erroneously I put in a new username and password and got the error of not being able to connect to my database.
I tried to go back to the previous stage of creating a database, which I can't because it already exists. But then I cannot go forward anymore. I have no idea where the database resides so that I can delete it and recreate it. I have tried uninstalling typo3 and reinstalling it. I have tried to google the problem without success.
Short of purging xampp completely and starting from scratch, is there a way I can delete the typo3cms database I have created?
It sounds like you are so early in the install process that you can start over (by removing all files and doing the install from the beginning).
Alternatively you should be able to remove typo3conf/LocalConfiguration.php and make sure that FIRST_INSTALL exists in document root (this is an empty file used to indicate that TYPO3 is doing the first install, it gets removed after - and you can use touch FIRST_INSTALL in terminal to create the file). Or if you prefer a completely manual approach, manually edit the typo3conf/LocalConfiguration.php file to correct or remove the database credentials and then resume the install.
I have been following the instructions on
https://docs.adobe.com/docs/en/aem/6-1/deploy/upgrade.html
I reached "Once the upgrade is finished, the AEM homepage will be shown."
However, all I get is "an HTTP 503 status for all requests except for those under http:///system/console", exactly as described at the NOTE under this step.
The problem is that I always get this error, not only during the upgrade, but also after the upgrade is finished!
The error.log states:
11.11.2015 12:38:29.888 *ERROR* [qtp231586654-77] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
11.11.2015 12:38:29.888 *ERROR* [qtp231586654-77] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.
Any help is highly appreciated.
We've encountered this once:
There were issues with diskspace (the disk was simply full), make sure you have an adequate amount of space available.
There could be two possible reasons:
Some of the bundles are not active.
Lucene is corrupt and hence not able to start
Possible fix is:
Bring your bundles back to active, if it is not active.
Stop your instance. go to crx-quickstart\repository\index and delete index folder.
Restart the instance (This will regenerate Lucene indexes fully).
Quick fix:
Stop the AEM instance.
Go to folder crx-quickstart\repository\ remove folder index
Start the AEM.
Everything should working fine. (It's working for me)
Check the permissions under crx-quickstart\repository\ after you deleted the index.
For me it had nothing to do with the segmentstore or the index or any unsatisfied bundles. Instead, it was the datastore.
The permissions for the datastore directory didn’t allow the user running aem to access it. The datastore directory is configured in org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.
This error really should reveal its root cause a little bit more easily. I’m sure it was somewhere in the logs, though…
I have started installing mongoDB, got struck like anything.
I can understand the mongoDB is not running even though it shows like mongo auto and a log file. I have deleted almost all the folders and i ran almost all the commands i have seen on net.
I need the commands which removes the mongodb completely from my system.I cannot understand what's happening with the mongodb.
Finally I have decided to remove it completely(not even a single instance of mongo).
provide me the best commands which might help me.
Perhaps this might help for Mongo 3.0
https://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/
and for Mongo 2.6
https://docs.mongodb.org/v2.6/tutorial/install-mongodb-on-ubuntu/
At the bottom of the page are instructions to remove all files.
This method of copying used to work for me. I created a Visual Studio 2010 installer project. I stopped the MongoDB service on my machine and copied my database files (*.ns, *.1, *.2, *.3 and *.4) into the installation. Then I would copy the files during the install to the db directory and start the MongoDB service.
That used to work until I had to add db renaming as an installer feature. now the files rename and copy and show up in mongovue, but the list of collections is blank. What is going on?
Any help would be greatly appreciated. Thanks!
MongoDB uses Journaling by default with 2.0. So this problem can happen when mongodb has data in journal by latency. You check journal latency so you can stop mongo instance after all journal committed. Here is documantation.
But i strongly recommend you to use mongodump / mongorestore for this job.