You must be registered to access the binaries download page. Go to How to Access Aspire , to check the Aspire Registration process.
> mongo MongoDB shell version: 4.0.4 connecting to: test > |
Error
If a "NETWORK Failed to connect to 127.0.0.1:27017" error occurs, then it is not running.
Start it by executing:
For Windows:
Open a terminal and CD to your MongoDB installation folder and execute:
C:\Program Files\MongoDB\Server\4.0\bin> mongod |
For Linux:
$ sudo service mongod start |
You need to specify a cluster Id, we recommend to replace the dev in the settings.xml with your unique cluster id
<!-- By default all Aspire servers start in their own cluster. To make servers work together, set a common cluster id across multiple instances that are connected to a common zooKeeper instance and database provider (for example "dev" or "prod") --> <clusterId>dev</clusterId> |
If you encounter Parsing Error: org.xml.sax.SAXParseException: Content is not allowed in prolog This error is caused by the presence of a byte-order mark (BOM) at the start of your XML file. You can see the BOM using "od -c <filename>". Remove the BOM by copying and pasting the entire file contents to a new file in a text editor (since the BOM does not copy to the clipboard). |
You may also need to edit the settings if you are running MongoDB on a separate machine.
First, make sure you have access to the internet so that Aspire can download components from our Maven repository.
To start Aspire, follow these steps:
> aspire.bat |
Linux
$ aspire.sh |
OS X (this command must be executed from Aspire home directory)
$ bin/aspire.sh |
Error
If you are unable to start Aspire and an error occurs, try accessing a URL via the browser and logging in with your registered username/password. For example:
For details on using the Aspire Content Source Management page, please refer to Admin UI Audit Logs.
Congratulations! You have completed the 20-minute quick start.
Or, go to the Aspire console window (where you started Aspire with "bin\startup") and