Troubleshooting

 

Home

 

Download

 

News

 

Support

 

Admin

 

Dev

 

Screen Shots

 

Grid List

 

Bugs

Languages:

English    Français    日本語

This page gives any system-specific configuration settings that may be useful, and advice for problems that might be encountered.

General tips

If OpenSimulator does startup to a point where you can type commands in the region console, then you can find out what your current configuration is by using the "config get" and "config save" commands as detailed at Server Commands (and by typing help on the console). This can be useful for eliminating a bad configuration when diagnosing some issues.

Also make sure that you are running the correct versions of the .NET runtime and database. See the Configuration#Database for notes about database versions, and you must use .NET 3.5 or later. .NET 2.0 doesn't have a System.Core. If you are using Windows .NET, simply download the 3.5 or 4 Update. If you are using Mono, you'll need to update your mono version.

System-specific configuration

CentOS 5 (64bit)

If you are running Mono 2.2 compiled from source on CentOS 5.2 64bit (not sure if it applies to other scenarios as well), you need to take these steps:

sudo yum install libgdiplus
sudo yum install libexif
sudo ln -s /usr/lib64/libgdiplus.so.0 /usr/lib64/libgdiplus.so
ldconfig

That finally enabled me to run OpenSimulator without errors, and even connect to other grids.

Gentoo

some Mono dependency & latest Mono itself may use "~x86" masked packages (assuming x86 is your platform, change may be made to reflect your ex:"~amd64" for 64bits). You could check for USE parameter with:

ACCEPT_KEYWORDS="~x86" emerge -vp subversion nant mono libgdiplus

Then install with:

ACCEPT_KEYWORDS="~x86" emerge subversion nant mono libgdiplus

N.B: The ACCEPT_KEYWORDS="~x86" can be set in Gentoo /etc/make.conf file, but that turn up all the emerges in testing/unstable, using it at the begining of emerge command line use it only for current emerge process

Mac OS X

If you get errors about the 2.0 framework not being supported, you may need to update your pkg-config path. For example, you can set this in ~/.bash_profile:

export PKG_CONFIG_PATH="/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}"

Errors and fixes

MySQL connection errors after about 6-8 hours

MySQL has a timeout which drops the connection after 28,800 seconds (8 hours) of inactivity, which will probably result in failure to login after the User server has been sitting idle for an extended period. If you have this problem, increase the timeout to something larger, like 604800 (1 week) or 31536000 (1 year). From the mysql console, type:

set global wait_timeout=604800;

System.DllNotFoundException: gdiplus.dll

First, check to make sure that libgdiplus.so is known to the dynamic linker:

/sbin/ldconfig -p | grep libgdiplus

If nothing is found, make sure that the directory libgdiplus.so exists in is either in your LD_LIBRARY_PATH environment variable or listed in a *.conf file (e.g., gdiplus.conf) in /etc/ld.so.conf.d/. Then run ldconfig to update the cache. Then it should be able to find the library.

You may still have the above error, however, since libgdiplus also depends on other dynamic libraries, and if they fail to load, libgdiplus will fail. To test for this, run OpenSimulator with debugging information turned on:

MONO_LOG_LEVEL=debug mono OpenSim.exe

On Mac OS X - check the following file exists... /opt/local/lib/libgdiplus.dylib if it does then as root user edit the file /opt/local/etc/mono/config and add the line

<dllmap dll="gdiplus.dll" target="/opt/local/lib/libgdiplus.dylib" os="!windows"/>

Migrating Opensim / MySQL database from Windows to Linux

MySql.Data.MySqlClient.MySqlException: Table 'opensim.UserAccounts' doesn't exist

Environment: Opensim Server 0.7.0.2 behind Linux Ubuntu 8.0.4 with mono 2.8 and MySQL 5.0 installed.

When you migrates a Opensim 0.7 database working with MySQL 5.0 on Windows to Linux, when logging a user in Opensim server, you may receive the following exception in the Opensim server console:

 03:11:10 - [LLOGIN SERVICE]: Exception processing login for (user_name): MySql.Data.MySqlClient.MySqlException: Table 'opensim.UserAccounts' doesn't exist
at MySql.Data.MySqlClient.MySqlStream.OpenPacket () [0x00000] in <filename unknown>:0
at MySql.Data.MySqlClient.NativeDriver.ReadResult (System.UInt64& affectedRows, System.Int64& lastInsertId) [0x00000] in <filename unknown>:0
at MySql.Data.MySqlClient.MySqlDataReader.GetResultSet () [0x00000] in <filename unknown>:0
at MySql.Data.MySqlClient.MySqlDataReader.NextResult () [0x00000] in <filename unknown>:0    at MySql.Data.MySqlClient.MySqlStream.OpenPacket () [0x00000] in <filename unknown>:0
at MySql.Data.MySqlClient.NativeDriver.ReadResult (System.UInt64& affectedRows, System.Int64& lastInsertId) [0x00000] in <filename unknown>:0
at MySql.Data.MySqlClient.MySqlDataReader.GetResultSet () [0x00000] in <filename unknown>:0
at MySql.Data.MySqlClient.MySqlDataReader.NextResult () [0x00000] in <filename unknown>:0

On the client, you also receive the following error:

Login Failed
Error generating Login Response

This exception is caused by the way MySQL store the table names. On a Windows MySQL server, the table names are not case sensitive, but all tables in MySQL Linux are case sensitive by default, so when OpenSimulator will find them in the database with names in first capital letters, it can not find it.

One solution would be to change the names of the tables required by opensim (ALTER TABLE's), but the cleanest solution is changing MySQL config, checking the option “lower_case_sensitive = 1” in the file "/etc/mysql/my.cnf", section [mysqld].

# sudo nano /etc/mysql/my.cnf

..........................
[mysqld]
..........................
lower_case_sensitive=1
..........................

This makes MySQL translate to lowercase the table names automatically. After restarting MySQL server and OpenSim, the tables are loaded without problems.

Warning: don’t try to clear the table migration to force opensim re-migrate your database, because it will provoke a blight on your database.

Errors from incomplete data migrations

This can happen during version upgrades if for some reason a database migration fails when there is a change in the way OpenSimulator stores data.

You may see errors on the OpenSimulator console like:

 [LLOGIN SERVICE]: Exception processing login for [username]: MySql.Data.MySqlClient.MySqlException: Table 'opensim.UserAccounts' doesn't exist
 at MySql.Data.MySqlClient.MySqlStream.OpenPacket () [0x00000] 
 at MySql.Data.MySqlClient.NativeDriver.ReadResult (System.UInt64& affectedRows, System.Int64& lastInsertId) [0x00000] 
 at MySql.Data.MySqlClient.MySqlDataReader.GetResultSet () [0x00000] 
 at MySql.Data.MySqlClient.MySqlDataReader.NextResult () [0x00000]    at MySql.Data.MySqlClient.MySqlStream.OpenPacket () [0x00000] 
 at MySql.Data.MySqlClient.NativeDriver.ReadResult (System.UInt64& affectedRows, System.Int64& lastInsertId) [0x00000] 
 at MySql.Data.MySqlClient.MySqlDataReader.GetResultSet () [0x00000] 
 at MySql.Data.MySqlClient.MySqlDataReader.NextResult () [0x00000] 

In this case the 'users' table had not been migrated to the 'UserAccounts' table which OpenSimulator was expecting, also resulting in the viewerside error:

 Login Failed
Error generating Login Response

I solved by fixing the filesystem permissions that were causing the migration to fail (on my Linux box '/var/lib/mysql/...' had got itself messed up), then dropping the 'migration' table and running the server again (from the [non-critical] migration warnings encountered there was probably a more precise way to do this, but I was fully backed up so I did it quick-and-dirty). Other than loosing terrain data refs. and current shape/clothing/attachment data (easily restored in-sim) all was now good for me.

When installing mono or libgdiplus0 you may get dependency missing libexif.so.9

This was noticed on Centos5 but may occur on other systems, download ftp://rpmfind.net/linux/conectiva/snapshot/i386/RPMS.extra/libexif9-0.5.12-47547cl.i386.rpm and install problem solved. You will now be able to install mono (as long as nothing else goes wrong )

The assembly mscorlib.dll was not found or could not be loaded

This indicates that you are missing one of the mscor libs that comes with nant. This is easily solved by getting NAnt, which comes with both versions 1.0 and 2.0 of the required lib.

apt-get install nant

External Program Failed: /usr/lib/pkgconfig/../../lib/mono/2.0/gmcs.exe

This is quickly fixed by retrieving mono-gmcs.

apt-get install mono-gmcs

The type or namespace name JScript does not exist in the namespace Microsoft

Note that it says JScript over and over again. Hint perhaps?

apt-get install mono-mjs libmono-microsoft8.0-cil

On Fedora and OpenSUSE, the needed package is "mono-jscript".

The type or namespace name Tcp does not exist in the namespace System.Runtime.Remoting.Channels

This one is taken care of with a quick install:

apt-get install libmono-system-runtime2.0-cil

Missing: libopenjpeg-libsl-2.1.2.0-x86_64.so

You are probably on a 64-bit linux machine and may need to follow these instructions:

• Installing and running on x86-64

error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file

If you start with a base Debian system as we did at the top of the page, but instead of using the apt version of mono you use the installer from their website, then you may encounter this issue.

After getting the .bin file from http://www.mono-project.com/Downloads, and executing it as per its instructions, upon finishing, you may find that if you try to run `mono --version` you are presented with this message. This one means you need to install libglib2.0-0.

apt-get install libglib2.0-0

The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file.

This one seems to be fixed by retrieving the apt version of nant.

apt-get install nant

This can also be due to pkg-config not being able to locate the mono.pc file. Adding the directory containing this file to the environment variable PKG_CONFIG_PATH may solve this.

Networking and config issues

See also the wiki page:

• Network Settings
• Firewall Settings
• Configuration

You are able to log in, but not connect to a Region from a remote client

Look in your OpenSimulator/bin/Regions folder:

1. Try 0.0.0.0 for the InternalAddress in your Regions.ini file.
2. ExternalHostName=127.0.0.1 will be needed to change its name to the asscssable DNS name such as "opensim.example-host.com" or "71.6.131.152" (your public accessable ip)

If you still have the same problem, it might be a firewall issue. Check if your firewall is active and configure it. See Firewall Settings for detailed instructions.

I get a timeout during region handshake

• Do you have the correct IP in your Regions\* config files? This must be accessible from the viewer machine.
• Do you have multiple interfaces on the server running OpenSim? OpenSimulator will not bind outgoing UDP packets to a specific IP, its default IP to reach you will be what the Region answers UDP with. If you have configured the region for another IP you will get a timeout during connect.

I cannot connect to my OpenSimulator

• See Connecting or Firewall Settings

My viewer keeps getting disconnected or avatar movement is very poor (rubberbanding, lag, etc.)

Broadly speaking, this occurs either because

1. The viewer is overloaded
2. The simulator has some issue or is overloaded
3. The network connection from viewer to server has insufficient bandwidth, very high latency or significant packet loss.

The easiest way to diagnose the first is to connect to similar regions on other grids with the same viewer and see if the same problems occur.

Simulator problems are harder to diagnose purely from the viewer-side, though one can look at client side monitoring to gain some insight as to whether the simulator is overloaded or has other issues.

The network connection can also be hard to test without the co-operation of the operators of both the server and the viewer. If one does have the co-operation of both, then one can use an external program such as lperf in UDP mode to run some basic tests on the connection. iperf is available for Windows, Mac and Linux. If these UDP tests show high jitter (high deviation from the average connection latency) or significant packet loss then this will cause problems for the viewer connection to the simulator.

Building OpenSimulator

I can't find any build files or solution files

• If you're on Windows, run

runprebuild.bat

• on Linux/Mac/FreeBSD, run

runprebuild.sh

VS2005 won't open the .sln file

• Try running VS2005 C#. You are probably running VS2005 C++. This is a C# project.

Running OpenSimulator

Running OpenSim.exe from a Cygwin shell has access denied for some dll's

• Do a 'cd bin' followed by 'chmod a+x *' to make all dll files executable.

How to do a clean rebuild? (e.g. after 'APPLICATION EXCEPTION DETECTED' after rebuild with updated source)

When you build from source, then update the source, rebuild and try to run, you get strange runtime exceptions like that:

 APPLICATION EXCEPTION DETECTED: System.UnhandledExceptionEventArgs
 Exception: System.MissingMethodException

When you build the source, it's 'compiled' into runnable files called 'dlls' or Dynamic Link Libraries. These have the extension .dll and are added to your local installation, and are not governed by source control. When we change where these dlls are created, the 'old' ones, from previous builds, will still be there. This will cause the program to try and load these old dlls, with unexpected results.

Usually, any of these remedies should fix the problem:

• Do a 'nant clean' if you're using Nant then rebuild and run.
• Remove all OpenSim.*.dll (only files that starts with "OpenSim." and ends in ".dll", like "OpenSim.Framework.dll") recursively from your installation directory. This is what "nant clean" does above. Finally, rebuild and run.
• Do a clean checkout, build that from scratch, then copy over all data files (*.db, *.ini) from your old installation, rebuild and run.

If all else fails, join #opensim on freenode, or send an email to the opensim-users mailing list.

OpenSim.exe console input is scrambled when run with mono on Windows

This is because OpenSimulator uses modified console which emulates cursor control and context help. It is intended to use on _nix console, so if you use it in dos console, it occurs.

Try starting like that. It will use "basic" console without additional features.

mono OpenSim.exe -console=basic

Exceptions on the Console

This is a list of Exceptions that you may see on the console, what they mean, and if they are a problem.

System.DllNotFoundException: lib32/libopenjpeg-dotnet-2.1.3.0-dotnet-1-i686

Please note: openjpeg-dotnet should now be built using the code in the libopenmetaverse project (from where this library comes). The version in opensim-libs is old and will no longer work.

You are on FreeBSD, and the libopenjpeg-dotnet needs some changes to work on your system

• Goto page http://opensimulator.org/mantis/view.php?id=5916
• Download the two FreeBSD-specific patches (opensim-freebsd-patch-OpenMetaverseDllConfig and opensim-freebsd-patch-opj_malloc)

git clone git://opensimulator.org/git/opensim-libs
cd opensim-libs/libomv-0.7.0/openjpeg-dotnet
patch libopenjpeg/opj_malloc.h /path/to/downloaded/opensim-freebsd-patch-opj_malloc
gmake
cp -p libopenjpeg-dotnet-2.1.3.0-dotnet-1.so /opensim/installation/directory/bin/
cd /opensim/installation/directory/bin
patch OpenMetaverse.dll.config /path/to/downloaded/opensim-freebsd-patch-OpenMetaverseDllConfig

System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so

You are on Linux, and the native lib libopenjpeg-libsl-2.1.2.0.so is not compatible with your system for one of the following reasons:

• You have an old processor (libopenjpeg has been compiled with optimizations)
• You are running in 64bit mode (none of the native libs are built for 64bit)

You can rebuild your own libopenjpeg from source, or run in a compatible environment. You can do this by:

git clone git://opensimulator.org/git/opensim-libs
cd opensim-libs/openjpeg-libsl/
make
# (on FreeBSD, use gmake instead of make, but you probably want to use the libopenjpeg-mono fix instead.

then copy libopenjpeg-libsl-2.1.2.0.so into OpenSimulator bin-folder.

System.NullReferenceException at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion

Your first startup of OpenSimulator has failed for example due to giving non existent domain name when prompted for region external host name. This causes only partial initialization. You need to delete bin folder, do svn update, rebuild and purge database to resolve this issue.

Exception: System.NotImplementedException: The requested feature is not implemented.

If your exception starts as follows:

 at (wrapper managed-to-native) System.Threading.Interlocked:Add (int&,int)
 at System.Threading.ReaderWriterLockSlim.TryEnterReadLock (Int32 millisecondsTimeout) [0x000e3] in

You probably unwittingly passed the option --optimize=-all to mono. The problem is that Mono compiles in an "optimized" version of the System.Threading.Interlocked class's methods; these optimizations are done using raw assembler for your architecture (automatically detected at build time). When you pass --optimize=-all, the runtime detects that these functions are optimized, and disables them. So the next time a class tries to call these functions, the runtime finds that there is no native implementation of the methods! This affects almost all synchronization primitives System.Threading. Since OpenSimulator relies heavily on threading and locking mechanisms, we can't do without this functionality. Perhaps a future Mono version will allow you to pass --optimize=-all, and provide an unoptimized implementation (e.g. pthreads), rather than throwing an exception.

If you're looking to debug a low level problem with mono (such as an error in native code), passing --optimize=-all is not the way to go about it. Instead, set the environment variable MONO_LOG_LEVEL=debug and run your program with the --debug switch passed to mono. You can also run mono under gdb, just like any other process.

Command error: System.IO.FileNotFoundException: Could not load file or assembly 'System.Core, Version=3.5.0.0, culture=neutral,PublicKeyToken=b77a5c561934e089' or one of its dependencies.

A missing System.Core indicates that you are using an old version of the .NET Runtime.

You must use .NET 3.5 or later. .NET 2.0 doesn't have a System.Core. If you are using Windows .NET, simply download the 3.5 or 4 Update. If you are using Mono, you'll need to update your mono version.

Scene Issues

Disappearing prims due to duplicate UUID's

Generally this problem occurs when a save-xml/load-xml file is loaded into the same sim without using the -newUID switch to generate new UUID's for the objects. See Server Commands for detailed information. (load-xml <filename> -newUID). But if this does not work, the other way is to shift-copy your build and drag it up into the air.. then delete the one in the air, (which is actually the copy). This will generate new UID's on all your prims.. you can now leave that build, and load your original load-xml file in another region.

Why are my knees bent when I stand idle?

This seems to be a result of the ODE Physics Engine on 64 bit systems. A fix is to edit OpenSim.ini and change the following line:

• av_capsule_standup_tensor_linux = 550000

to

• av_capsule_standup_tensor_linux = 1700000

Note that this line of code is under the [ODEPhysicsSettings] section of the OpenSim.ini file.

My avatar appears to keep twitching and will occasionally fly off without me being able to stop it

This is often due to an extremely overburdened computer or network issues (e.g. a connection to the simulator with too low bandwidth or too high latency).

Executing "show queues" from the console will list the number of UDP packets that had to be resent to client. If this number of a high percentage of the total packets sent out (e.g. around 10% or higher) then you likely have one of these two issues.

Unfortunately, the only fix is to improve the client computer or fix the network issues. Network issues can be many and diverse, from the bandwidth available to the server to issues with some home wifi routers not delivering data packets in a timely manner.

Inventory Issues

when I create a new skin and shape, the thing goes bonkers creating new assets constantly

you have not configured an asset cache

you need to configure either the cenome cache or the flotsam cache

without an asset cache, temporary assets can't be held which means they are continously rerequested

copy either config-include/CenomeMemoryAssetCache.ini.example, or the relevant flotsam file, to .ini edit and set it up for your needs then check GridCommon.ini or StandaloneCommon.ini uncomment the line for that cache

(standalone defaults to cenome grid to flotsam)

Map issues

I have problems with viewing the worldmap

• This may happen when running OpenSimulator on a Linux server, both in grid or standalone mode.
• Symptoms: when opening the worldmap window in the SL-viewer, the sims are not displayed grahically in the worldmap, the server console shows some error related to openjpeg, the current session freezes...
• Reason: your svn source trunk does not have the correct (or whatever...) libopenjpeg-libsl library.
• Other reason: the file "defaultstripe.png" does not exists in the same OpenSimulator folder, or is corrupted.
• Solution: get the newest code from opensim-libs, follow instruction for libopenjpeg-mono or libopenjpeg-libsl depending on your error messages.
• Recompile & restart OpenSimulator

Grid Mode

I start the sim and it doesn't connect to any grid

When OpenSimulator is first started, it needs configuration.

• See Configuration.

My grid works fine with one user but when two users login in the same time both get stuck

• Make sure you have export MONO_THREADS_PER_CPU="100" in your environment

After ~20 minutes my region starts to take 100% cpu and region(s) hang

• If you have mono 1.9.1 or lower upgrade to mono 2.2.

Hypergrid

After starting OpenSimulator with Hypergrid enabled my inventory wont load!

• If you're running in grid mode, first check your OpenSim.ini to make sure that the dns names or addresses for your grid servers are accessible to both you and the public.
• Check the XML config files for your UGAIM servers to make sure that everything is running off of a publicly accessible IP address.
  • If this is the case and you have to change your UGAIM addresses you will need to run a few quick and dirty SQL queries on your database in order to update your grid's user accounts so that they now point to the new IP addresses of your UGAIM.

Log into your sql server and change over to the database for your grid. The following will update your user's home inventory and asset URIs after changing the addresses of your UGAIM services in the XML configuration files.

     update users set userInventoryURI="http://new.UGAIM.address:8004" where userInventoryURI = "http://old.UGAIM.address:8004";

     update users set userAssetURI="http://new.UGAIM.address:8003" where userAssetURI = "http://old.UGAIM.address:8003";

• If you're running in standalone mode... - Anyone familiar with standalone want to fill this in? -

Physics Issues

Problems using OpenDynamicsEngine (ODE) 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 edit opensim.sh changing ulimit there and run it to start up OpenSimulator.

Exception and loss of ode physics (System.EntryPointNotFoundException: dSpaceLockQuery)

The following error is usually caused by using the wrong version of libode:

First try searching your filesystem to see if you have other copies of the ode physics engine:

find / -name "libode.so"

Then make sure you have the latest version.

ScriptEngine Issues

Whilst loading an OAR or starting up the simulator, it crashes with a StackOverflowException

This can occur if a thread converting a script from LSL to C# runs out of room on the stack. It particularly effects Windows 64-bit servers, though not the same servers running OpenSim.32BitLaunch.exe or Mono servers (32 or 64-bit).

If you want to see the failing script, set

   <logger name="OpenSim.Region.ScriptEngine.XEngine">
     <level value="DEBUG"/>
   </logger>

instead of INFO at the bottom of OpenSim.exe.config.

To fix this issue, increase the ThreadStackSize from 262144 in the [XEngine] section of OpenSim.ini.

Got "Primitive: Error compiling script: unknown char: . error" when compiling script

When trying to compile a script ( using DotNetEngine or XEngine ) you could have this error :

And on the console :

This happens on linux when your locales are not set to default ( "C" ).

• You could refer to Mantis #2088 and Mantis #2015 for a workaround to run opensim.

env LANG=C mono --debug OpenSim.exe

• You could also change your locale setup. Here is what I use in my '.bash_profile' :

export LC_ALL=C
export LANG=C

I know it's a ugly way to setup locales on a linux box, but it works fine on my Linux From Scratch box.

Rq: I saw Melanie has corrected some parts of the source code a few weeks ago to avoid such problems.

Get "Primitive: Error compiling script: ApplicationName='gmcs', ..." when compiling script

When trying to compile a script ( using DotNetEngine or XEngine ) you have an error something like :

Other features include "Touch" being disabled on the right click menu wheel.

You might have a broken mono install (i.e. discovered as mono but not gmcs installed on a Ubuntu 8.10 Intrepid machine.)

Check mono-gmcs (sudo apt-get install mono-gmcs) is correctly installed.

Get "gmcs: Cannot find the specified file" when compiling script

Just install "mono-gmcs" package on your system. See Dependencies for details.

Locale Issues

Modern OpenSimulator (post 0.7.3) should properly set the en_US locale for all data saving, which is necessary for cross simulator compatibility. However, if you are encountering issues with large amounts of corrupt data you may want to try setting your machine local to en_US and submitting a bug report.

Appearance Issues

See Appearance Troubleshooting.