User talk:Yvetteharris

Opensimulator with Windows Server 2008 R2 Install and Basic Setup

DRAFT VERSION April 10, 2012

This document has easy instructions all in one place for installing and configuring a Standalone, Opensimulator version 0.7.3.1 on Windows Server 2008 R2 64-bit machine for LAN only.

OpenSimulator now requires .NET Framework 3.5 when running under Windows.

When you run OpenSimulator on Windows 7 or Windows Server 2008 R2, it is already bundled so you can run OpenSimulator 0.7.1 out-of-the-box.

1. Start the NET services on your Win Server 2008 R2, set them to Automatic. The default services for NET are not started on the Windows Server 2008 R2.

2. Download opensim-0.7.3.1 from URL http://opensimulator.org/wiki/Download to your Download directory on your PC.

3. Extract this zip file to a new root directory on your PC using the same file name for the folder (c:\opensim-0.7.3.1).

3. From Windows, open a DOS command window.

4. Type cd c:\opensim-0.7.3.1\bin.

5. Type copy OpenSim.ini.example OpenSim.ini in the opened DOS command window and hit enter.

This configures the 3D simulator itself.

6. Type cd c:\opensim-0.7.3.1\bin\config-include.

7. Type copy StandaloneCommon.ini.example StandaloneCommon.ini

This configures the in-process data services used by the standalone configuration.

8. From Windows execute NotePad program.

9. From NotePad open c:\opensim-0.7.3.1\config-include\StandaloneCommon.ini file

10. Edit the file as follows. In the [Architecture] section of OpenSim.ini, near the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbol preceding the line so that it says: Include-Architecture = "config-include/Standalone.ini"

11. Save file and close NotePad program.

12. Return to your open DOS command window.

13. Type Opensim.32BitLaunch in the opened DOS command window and hit enter. This will start the Opensimulator for the first time. The first time you start this it will prompt you for information as indicated in the below. Be careful for the following and head the warnings for excepting defaults and when to type in something unique!

14. Region UUID: Accept the default This will generate a unique machine type address id.

15. Region Name: Make this unique - Don't leave this blank! Keep the name short like CL for Cyber Learning

16. Region Location: Accept the default This is the location of the region on the grid. In standalone mode you can safely leave these as the default (1000,1000). If you were to set up additional regions later on in Regions.ini then they would need different grid co-ordinates (e.g. 1000,1001). OpenSimulator regions can be placed anywhere on a 65536 by 65536 grid, but Hypergrid enabled regions may need special consideration for region location.

17. Internal IP Address: Accept the default In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSimulator to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address.

18. Internal port: Accept the default This address is only used internally - the External host name is the one that is actually passed to the viewer (and hence is the important one). Internal port This is the IP port for all incoming client connections. The name is a bit misleading since it will be used externally (by a Second Life viewer, for instance) as well as internally. You can make this any port you want, but it is safe to leave at the default 9000. Each region on your server must have a unique port.

Allow alternate ports:

    This is currently experimental. Please leave it at the default of False. 

External host name:

    If you leave this at the default 'SYSTEMIP' then this will become the LAN network address 

of the machine (e.g. 192.168.1.2). This is fine if you are connecting only from within your LAN. If you want to connect to it from a client on the internet, this should be the External IP Address of your router. Fully Qualified Domain Names (FQDNs) can also be used though they will be converted to a numeric IP address before being sent to the viewer.

• • • The following details are also asked in OpenSimulator 0.6.9 and earlier.***

Master Avatar UUID:

    This is a legacy OpenSimulator feature and can be left at the default of 

00000000-0000-0000-0000-000000000000. Later on, you may want to change this to your own avatar's UUID in Regions.ini if you have problems editing terrain. Master Avatar first name This is an alternative way of specifying the master avatar by avatar name rather than UUID. If you press enter here then both this field and the last name field will be left blank. Accepting the blank default is fine - this can always be changed later in Regions.ini file.

Master Avatar last name: The last name of the master avatar.

Master Avatar sandbox password: The password of the master avatar.

Estate:

    In OpenSimulator 0.7 and later, OpenSimulator will ask you to assign each region to an estate

during the setup process.

Estate owner first name:

If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process. Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.

See Configuring Regions for more information about the Regions.ini file that these questions generate.

If you want to create a user other than the estate manager, then in the server console type:

create user

This will ask you a series of questions for creating a user (such as first name,

last name and password).

Estate owner last name:

Password:

Email:

User ID: accepted default 101a6fbc-81ce-4655-a76b-d10588e1c1bc

Region (KSUID) #:

04/07/2012

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Logging into your new Sim*****************************

Modify your Viewer properties and add this:

Connecting to OpenSimulator

To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:

Client on same machine as OpenSim: -loginuri http://127.0.0.1:9000

Client on same LAN as OpenSim: -loginuri http://lan_ip:9000

Client on different machine or internet: -loginuri http://external_ip:9000

Then enter the user name and password you set up in the previous step and your new user should login.

Be aware of loopback problems when Running viewer & server(s) on the same machine (LAN) by using the "external" configuration. (You might notice endless waiting for region handshake.) See also troubleshoot hints. If you're having Connectivity problems, be sure to read the Network

Configuration Page. This is important if you see Region handshake issue.

• • • • • • • • • • • • • • • • • • • • Setting up Robust***************

Step 1: Set up a ROBUST services instance

1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.

2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.

3. Start up Robust.exe. mono Robust.exe (Linux, BSD, Mac OS X)

or Robust.exe (Windows)

If you don't see any errors (in red) on the console then you can move on to the next step.

4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.

create user

This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.

Step 2: Configure an OpenSim.exe to use the ROBUST services

In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.

However, instead of using and configuring the file config-include/StandaloneCommon.ini, a simulator connecting to a grid needs to use and configure the config-include/GridCommon.ini file, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.

The steps for both these operations are as follows.

1. Copy bin/OpenSim.ini.example to OpenSim.ini

2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that one of the following lines is uncommented:

Include-Architecture = "config-include/Grid.ini" (in OpenSimulator 0.7.1 and later)

or Include-Grid = "config-include/Grid.ini" (in OpenSimulator 0.7.0.2 and earlier)

The others should remain commented.

3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.

4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting

AssetServerURI = "http://192.168.1.2:8003"

5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the Configuring Regions page.

If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,

21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000

21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours

6. Login with a client. Your client startup line will look something like -loginuri http://192.168.1.2:8002

The loginuri needs to be the address to the login service. In standalone mode, this was the same address as the region simulator and the port was 9000 by default. However, in grid mode it will be the address to login service hosted on the ROBUST instance. In this case, the address will be 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.

7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).

Attaching your sim to someone else's grid

To set up the region server (i.e., OpenSim.exe) to connect to an external grid, follow the Configuration#Step 2: Configure an OpenSim.exe to use the ROBUST services instructions above.

The grid will have already provided with the required services. In step 2 you will need to use the provided URLs for their services.

In your bin/Regions.ini file (or other region config file) you will also need to set the grid co-ordinates to your regions provided from the grid operator. See Configuring Regions for more information.

Running an OpenSimulator standalone or grid installation with Hypergrid enabled

Hypergrid is an emerging architecture supported by OpenSimulator that allows a user with an account on one standalone or grid to visit other Hypergrid-enabled standalones or grids, and for users from those grids to visit the home grid. This does not require the two installations to share a central set of data services (assets, inventory, etc.). Please see Installing and Running Hypergrid for more details.

Further notes

Troubleshooting

See Troubleshooting

Running OpenSimulator 0.6.7 and onwards in 64 bit Windows

As of OpenSimulator 0.6.7, the default physics engine for OpenSimulator was changed to the ODE engine. This is because ODE is by far the most advanced physics engine plugin currently in OpenSimulator. Unfortunately, it has the drawback in that its library is not compilable under 64-bit in Windows.

Therefore, in order to launch the region simulator, 64-bit Windows users may need to run:

OpenSim.32BitLaunch.exe

instead of: OpenSim.exe

An alternative is to use the basicphysics engine instead or one of the other alternative physics engines bundled with OpenSim, though all these are far less functional than the ODE plugin.

Note About Mono

This only applies for Mono before 2.6. More recent versions of Mono have better thread handling. For more information, see ThreadPool_Deadlocks at the mono-project website.

If you're using mono, you should increase the value of the mono environment variable MONO_THREADS_PER_CPU from its default of 5 to some number that works for your sim. The exact number depends on many factors including: the number of CPUs in your machine, what else you use that machine for, how many regions you have in your sim, how many of them are adjacent, how many scripts you have, and how many avatars you expect to serve at the same time. As a reference, Wright Plaza in OSGrid, which is running as a single region on a sim and routinely hosts meetings with 20 avatars, uses the value 125.

If this number is too low, the operation of your sim will start to break in all sorts of different ways. A common symptom is the freezing of all activity upon login of a new avatar. Other symptoms are a lot more subtle.

For example: $ export MONO_THREADS_PER_CPU=125

Increasing the stack reserve level when using OpenDynamicsEngine on *nix

If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command; ulimit -s 262144 Or, run the opensim-ode.sh to start up OpenSimulator.

Firewalls

Some operation systems or distributions run their own firewall by default. If you can't access to OpenSimulator from remote client, you'll need to check their settings. See Firewall Settings for details.

Legacy Configuration Information

These are some pages containing some legacy configuration information of unknown accuracy.

OpenSim 0.6.6 legacy configuration information

Additional Optional Configuration Tasks

Further configure OpenSimulator

If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See Configuring Simulator Parameters for more details.

Set up a second region to run on the same simulator

See Configuring Regions.

Run Multiple Standalone Instances of OpenSimulator on the Same Server

For each subsequent instance of OpenSim, change the 'http_listener_port' in OpenSim.ini to the value excluding 9000, and 'InternalPort' in Regions.ini to the value excluding 9000. Also, make sure your regions are using different ports, as explained in Configuring Regions.

Load region content

You can load content onto regions by using the load oar command. To load individual OAR files into each region, use the 'change region [regionname]' command and then 'load oar [oar-location]'.

OpenSim.exe command line options

OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See OpenSim.exe Command Line Options for more details.

Script engine

OpenSimulator supports multiple script engines. See ScriptEngines for details. If you don't know what this means then the default script engine will be fine. In fact, recent versions of OpenSimulator only ship with one script engine, the XEngine.

Permissions Configuration

OpenSimulator has a quite elaborate set of permissions. See Permissions (Server) for details. By default, permissions are active on region simulators.

Logging

By default, OpenSimulator logs information to a file called OpenSim.log in the bin directory. See Logging for details on how to further configure this if required.

Configuration of region modules IRCBridgeModule Freeswitch Module Offline Messaging Profile Enabling Groups

Configuration of Web Server and Pages

OpenSimulator contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.

External Files 

Internally Generated

Where to go from here Upgrading to MySQL from SQLite. Server Commands for creating users and controlling the system. Fix the bent knees bug: FAQ#Why are my knees bent when I stand idle.3F

References OpenOffice draw file for OpenSimulator standalone diagram OpenOffice draw file for OpenSimulator grid diagram

Category: Configuration