Dependencies

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
(Windows: reconsidered: considering running in mono or in grid-mode, it is better specifying a port than application...)
(moved firewall issues to Firewall Settings)
Line 17: Line 17:
 
Depending on your installation, you may have to run the program as administrator(right click -> 'Run as administrator'). It will pop up a window asking permission, select "Allow".
 
Depending on your installation, you may have to run the program as administrator(right click -> 'Run as administrator'). It will pop up a window asking permission, select "Allow".
  
 
 
'''''Windows Firewall'''''
 
 
On Server 2008, Vista or Windows 7, you'll need to configure the "Windows Firewall with Advanced Security" to enable access from the viewers on another machines. Here's what you can do:
 
 
#Click Start and then click Control Panel. In the Control Panel, click System and Security and then click Administrative Tools. In Administrative Tools, double-click Windows Firewall with Advanced Security. Or you can even direct access by typing "WF.msc" in the Run textbox in the start menu.
 
#Select Inbound Rules in the left pane and click New Rule under Inbound Rules in the Actions Pane. The New Inbound Rule Wizard will launch.
 
#First on '''Rule Type''' screen, select '''Port'''. Click Next to continue.
 
#On '''Protocol and Ports''' screen, select '''TCP''', then select '''Specific local ports:''' and fill in the value '''9000''' (if standalone mode; If grid mode, it will be '''8002'''). Click Next to continue.
 
#On '''Action''' screen, select '''Allow the connection'''. Click Next to continue.
 
#On '''Profile''' screen, leave it as is and click Next to continue.
 
#On '''Name''' screen, give the rule a name and any description. Click Finish to create the rule.
 
#Repeat 2-7 step above to create the same rule for '''UDP''' as well.
 
 
 
'''''McAfee Security'''''
 
 
McAfee Security does not allow applications to listen on ports not explicitly specified. You have two options: 1) disable firewall protection all together, 2) enable <tt>OpenSim.exe</tt> to be able to open ports.
 
 
Disable Firewall - Open McAfee SecurityCenter. Select "Internet &amp; Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Here you can select "Off".
 
 
Enable <tt>OpenSim.exe</tt> to Open Ports - Open McAfee SecurityCenter. Select "Internet &amp; Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Select the "Advanced..." button. This will pop up a new window.
 
 
In the new window, on the left side, select "Program Permissions." In the middle on the right side of the window, select the "Add Allowed Program" button. Use the browser that pops up to find the OpenSim executable and select it.
 
 
Finally, select "OK" and exit the McAfee SecurityCenter window.
 
  
 
= Linux  =
 
= Linux  =

Revision as of 05:13, 11 May 2011

In addition to the OpenSim code itself, certain other packages need to be installed on different platforms in order to get OpenSim binaries to run.

As well as the information on this page (which should be expanded), you may find more information on dependencies in Build Instructions though this will also contain dependencies required only for building. This are also more hints in Troubleshooting


Contents

Windows

OpenSim now requires .NET Framework 3.5 when running under Windows. If you run OpenSimulator on Windows 7 or Windows Server 2008 R2, it is already bundled so you can run OpenSim 0.7.1 out-of-the-box. On Windows Vista, Windows Server 2008, Windows Server 2003 or Windows XP, you'll need to upgrade it to 3.5(or later, but NET Framework 4.0 not officially supported by OpenSim yet), downloading from Microsoft .NET Framework Download Page@.NET Framework Developer Center. Note that prior versions of Windows(ex. NT or 2000) are NOT supported.

If you run on Windows XP ensure it is updated to at least Service Pack 2 (SP2).

Double-click or execute on command prompt:

  • 32-bit version of Windows: OpenSim.exe
  • 64-bit version of Windows: OpenSim.32BitLaunch.exe

Depending on your installation, you may have to run the program as administrator(right click -> 'Run as administrator'). It will pop up a window asking permission, select "Allow".


Linux

OpenSimulator requires Mono 2.4.3 or later.

Ubuntu

sudo apt-get install nant mono-gmcs libmono-microsoft8.0-cil \
     libmono-system-runtime2.0-cil libgdiplus libmono-i18n2.0-cil libmono-oracle2.0-cil

Nant is required if you need to build OpenSim.

RHEL, Fedora, CentOS or Any Other RedHat-based Distributions

First, run "yum info mono-core" to see the version of the mono packages in the core repository for your distribution. If it shows 2.4.3 or later, proceed to #Installing from Core Repository. If not, skip to #Installing from Mono Repository. Note that the current version you can get from yum repository for some distributions is lower than requirement (ex. 1.2.4 on CentOS). Unlike Ubuntu, RedHat-based distributions should be always conservative, therefore it is natural that they don't so often update their repository. What you can do to manage this problem is to add an extra repository for mono.

Installing from Core Repository

Just type:

sudo yum install  mono-core mono-data-sqlite mono-extras libgdiplus

It will also install dependent modules. After that you can launch OpenSim.exe with mono out-of-the-box.

Installing from Mono Repository

This procedure is tested on CentOS 5.5 & 5.6 box with OpenSim 0.7.1.

Go to yum config file folder and create new one for mono.

cd /etc/yum.repos.d
sudo vi mono.repo

And then in mono.repo :

[mono]
name = novell-mono
baseurl=http://ftp.novell.com/pub/mono/download-stable/RHEL_5/
enabled=1
gpgcheck=0

Now, you can yum install the later version of mono from this repository. Additional note that make sure all of mono packages are i386(not IA64 build). If your box is 32bit, don't care and you can even install properly without ".i386" suffix.

sudo yum install mono-addon-core.i386 mono-addon-data.i386 mono-addon-data-sqlite.i386  \
      mono-addon-extras.i386 mono-addon-web.i386 mono-addon-winforms.i386 mono-addon-libgdiplus0.i386

Yum will install mono into /opt/novell/mono, so you can create a symbolic link to /usr/bin :

sudo ln -s /opt/novell/mono/bin/mono /usr/bin/mono

After that, you should be able to launch OpenSim.exe without any errors.


Mac OS X

All you have to do is to fetch Mono Runtime package from Mono Download Page and install it.


Locales and Regional Settings

OpenSimulator will only work properly when you run it with an English locale or regional setting. With other settings than English, you are likely to see a variety of issues, ranging from misbehaving scripts to crashes.

Linux

In Linux, you can easily use the standard "C" locale just for running OpenSim.exe, as explained in Troubleshooting#ScriptEngine Issues:

env LANG=C mono OpenSim.exe

For information about changing your locale in a more general way, see Troubleshooting#Locales Issues

Windows

If you are not using an English regional setting in Windows by default, then there is not a solution as easy as for Linux, unfortunately. I did it with an additional user account that I created just for OpenSim in which I set the regional setting to "English (US)". I run OpenSim.exe from my normal user account with "Run as..." (or check "Run with different credentials" in a shortcut's advanced properties) and specify the OpenSim account as the one to be used.


Additional Resources

OSGrid Technical Support Forum with many installation tutorials:  osgrid.org/forums/viewforum.php

MONO Project:  www.mono-project.com/Main_Page

Personal tools
General
About This Wiki