http://opensimulator.org/api.php?action=feedcontributions&feedformat=atom&user=Dale+Mahalko 2026-05-26T19:40:09Z User contributions MediaWiki 1.19.9 http://opensimulator.org/wiki/Physics 2010-04-04T09:37:34Z

<p>Dale Mahalko: what collision geometry is, how modern game engines make use of it, and how Second Life doesn't. OpenSim could allow it.</p> <hr /> <div>__NOTOC__<br /> {{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> By default, Open Simulator uses an extremely simple physics engine which only allows you to stand on the ground. All objects using the basic physics engine appear to be phantom, and the only way to make them act as solids is to use some other more sophisticated physics engine, such as the [[Open Dynamics Engine]].<br /> <br /> Note that physics processing is one of the biggest sources of region simulator lag. If you use a better engine to make objects appear to be solid, you will most likely want to isolate the region simulator and physics engine on its own physical hardware so that lag in the physics engine does not also slow down your asset and inventory servers.<br /> <br /> == The role of the physics engine ==<br /> One of the primary functions of the simulator is to provide an experience that approximates real life. This typically requires making the objects in the 3D world appear to be solid and ''real''.<br /> <br /> As far as the simulator database engine is concerned, it simply knows the positions of objects in the simulated 3D space and knows the references to textures for each surface of the objects. The database engine does not know anything about gravity, pushes, or collisions.<br /> <br /> It is technically possible to connect to a simulator without a physics engine, but the avatars would appear to float in space without gravity and can pass through any object including other avatars, and move in any direction to the coordinate limits of the simulated space.<br /> <br /> The primary task of the physics engine is to move objects affected by forces and to resolve collisions. Collisions occur when two physical objects collide or are simply touching each other.<br /> <br /> Most objects in the simulator are pinned in space and do not move. They do not normally require any physics processing time. However, when a physical moving object collides with a pinned object, the pinned object is temporarily treated as if it were physical and collisions are calculated against it. Since it cannot move, the only resolving forces are applied to the movable object.<br /> <br /> In certain unresolvable situations (described below) a physical moving object causing continuous high simulator load may be defensively changed by the simulator into a nonphysical or phantom object, so that the simulator does not become stuck in a continuous high-load state.<br /> <br /> == Gravity and the ground ==<br /> <br /> The single biggest force in the simulator is gravity, which causes physical objects to move downward (Z axis in the 3D coordinate system), typically following Earth-based experience of accelerating to a terminal falling velocity of 9.81 meters per second.<br /> <br /> There is also a deformable plane surface in each sim which is the lowest point any object can descend. We call this the ground or the ''surface patch''. If the ground did not exist, physical objects in the simulator would simply fall to the lowest possible Z axis coordinate value of zero and simply stop, apparantly suspended above/in nothingness. This is outside our normal experience so we have the ground in the simulator to make the simulated world seem more like real life.<br /> <br /> When objects affected by gravity collide with the ground in the simulator, the physics engine resolves the collision by pushing back on the colliding object, causing it to rise up out of the ground against the force of gravity. If the forces are treated as springs, and the object is elastic while the ground is hard and resilient, the simulator can apply an opposite upward force equal to the downward force to cause a fast moving object to &quot;bounce&quot; upward again.<br /> <br /> As mentioned above, the default basic physics engine included with Open Simulator only resolves collisions with the ground, and makes no attempt to make object primitives appear to be solid. As a result, a basic install of Open Simulator will tend to have a mostly flat world layout following the ground surface because that is the only place where people can walk around in a realistic looking manner. Walking around in the second floor of a house made from primitives suspended in midair above the ground for example is not possible.<br /> <br /> == Holes, gaps, and simulator lag ==<br /> The most basic form of collision resolving involves two objects which are overlapping, due to forces having caused them to move towards each other in previous calculation phases. Once the objects are overlapping, the goal of the physics engine is to apply forces so that the objects move in such a manner that they no longer overlap.<br /> <br /> For two simple solid objects this involves merely pushing the objects apart so that they are further away from each other.<br /> <br /> But the collision resolving task is much harder if there are holes in one object or the other. Rather than merely pushing the objects apart, the ideal goal would be to push the objects towards the open spaces within each other. This is where the math becomes incredibly difficult for complex or ''tortured'' primitives, and even for certain simple objects such as hollow spheres.<br /> <br /> Due to the linking of objects in a simulator, and linked sets of objects being allowed to become physical, even simple linked objects made from non-hollow primitives may combine to form 3D shapes that contain holes and interior spaces that are difficult or impossible for the physics engine to resolve. <br /> <br /> In the past, the early Second Life simulators using the Havok 1.0 physics engine were often attacked by lag-causing objects with collisions that could not be resolved. A large number of these objects would cause a simulator to drag to a standstill.<br /> <br /> The upgraded Havok 4.0 engine in Second Life will attempt to work with holes in objects at first, but if the collisions can not be resolved in a reasonably short amount of time, the engine will revert to treating the objects as solid and cause the objects to separate until they do not touch. The Havok 4.0 engine goes further if that does not work, and will render one or more objects phantom to stop the objects from causing further unresolvable physics engine lag.<br /> <br /> Free open source engines may not provide the same collision resolving features as the commercial Havok engine.<br /> <br /> == Collision geometry ==<br /> In most modern game engines, physical objects are often constructed from two very different shapes. There is the visible shape of an object which may be very complex and detailed. And there is a second invisible shape that is often very simple, used by the physics engine to calculate collisions. This allows the physics engine to conserve processing power while still making the 3D environment appear complex and detailed.<br /> <br /> Second Life in its current form does not allow content creators to make use of collision geometry separate from primitives. Instead the exact shape of the primitive or linkset is always its collision geometry, which leads to unnecessary complexity in the physics processing.<br /> <br /> Open Simulator tends to follow the standards originally set by Second Life. While Open Simulator could allow for the use of separate simple collision geometry for complex objects, it would do so against the standards of Second Life, and the collision geometry would not be usable when an avatar and its objects move directly from an Open Simulator grid to the Second Life grid.</div>

Dale Mahalko http://opensimulator.org/wiki/Physics 2010-04-04T09:20:15Z

<p>Dale Mahalko: the problem of holes, gaps, slots, tortured prims, and linksets in causing physics engine lag and dragging sims to a standstill</p> <hr /> <div>__NOTOC__<br /> {{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> By default, Open Simulator uses an extremely simple physics engine which only allows you to stand on the ground. All objects using the basic physics engine appear to be phantom, and the only way to make them act as solids is to use some other more sophisticated physics engine, such as the [[Open Dynamics Engine]].<br /> <br /> Note that physics processing is one of the biggest sources of region simulator lag. If you use a better engine to make objects appear to be solid, you will most likely want to isolate the region simulator and physics engine on its own physical hardware so that lag in the physics engine does not also slow down your asset and inventory servers.<br /> <br /> == The role of the physics engine ==<br /> One of the primary functions of the simulator is to provide an experience that approximates real life. This typically requires making the objects in the 3D world appear to be solid and ''real''.<br /> <br /> As far as the simulator database engine is concerned, it simply knows the positions of objects in the simulated 3D space and knows the references to textures for each surface of the objects. The database engine does not know anything about gravity, pushes, or collisions.<br /> <br /> It is technically possible to connect to a simulator without a physics engine, but the avatars would appear to float in space without gravity and can pass through any object including other avatars, and move in any direction to the coordinate limits of the simulated space.<br /> <br /> The primary task of the physics engine is to move objects affected by forces and to resolve collisions. Collisions occur when two physical objects collide or are simply touching each other.<br /> <br /> Most objects in the simulator are pinned in space and do not move. They do not normally require any physics processing time. However, when a physical moving object collides with a pinned object, the pinned object is temporarily treated as if it were physical and collisions are calculated against it. Since it cannot move, the only resolving forces are applied to the movable object.<br /> <br /> In certain unresolvable situations (described below) a physical moving object causing continuous high simulator load may be defensively changed by the simulator into a nonphysical or phantom object, so that the simulator does not become stuck in a continuous high-load state.<br /> <br /> == Gravity and the ground ==<br /> <br /> The single biggest force in the simulator is gravity, which causes physical objects to move downward (Z axis in the 3D coordinate system), typically following Earth-based experience of accelerating to a terminal falling velocity of 9.81 meters per second.<br /> <br /> There is also a deformable plane surface in each sim which is the lowest point any object can descend. We call this the ground or the ''surface patch''. If the ground did not exist, physical objects in the simulator would simply fall to the lowest possible Z axis coordinate value of zero and simply stop, apparantly suspended above/in nothingness. This is outside our normal experience so we have the ground in the simulator to make the simulated world seem more like real life.<br /> <br /> When objects affected by gravity collide with the ground in the simulator, the physics engine resolves the collision by pushing back on the colliding object, causing it to rise up out of the ground against the force of gravity. If the forces are treated as springs, and the object is elastic while the ground is hard and resilient, the simulator can apply an opposite upward force equal to the downward force to cause a fast moving object to &quot;bounce&quot; upward again.<br /> <br /> As mentioned above, the default basic physics engine included with Open Simulator only resolves collisions with the ground, and makes no attempt to make object primitives appear to be solid. As a result, a basic install of Open Simulator will tend to have a mostly flat world layout following the ground surface because that is the only place where people can walk around in a realistic looking manner. Walking around in the second floor of a house made from primitives suspended in midair above the ground for example is not possible.<br /> <br /> == Holes, gaps, and simulator lag ==<br /> The most basic form of collision resolving involves two objects which are overlapping, due to forces having caused them to move towards each other in previous calculation phases. Once the objects are overlapping, the goal of the physics engine is to apply forces so that the objects move in such a manner that they no longer overlap.<br /> <br /> For two simple solid objects this involves merely pushing the objects apart so that they are further away from each other.<br /> <br /> But the collision resolving task is much harder if there are holes in one object or the other. Rather than merely pushing the objects apart, the ideal goal would be to push the objects towards the open spaces within each other. This is where the math becomes incredibly difficult for complex or ''tortured'' primitives, and even for certain simple objects such as hollow spheres.<br /> <br /> Due to the linking of objects in a simulator, and linked sets of objects being allowed to become physical, even simple linked objects made from non-hollow primitives may combine to form 3D shapes that contain holes and interior spaces that are difficult or impossible for the physics engine to resolve. <br /> <br /> In the past, the early Second Life simulators using the Havok 1.0 physics engine were often attacked by lag-causing objects with collisions that could not be resolved. A large number of these objects would cause a simulator to drag to a standstill.<br /> <br /> The upgraded Havok 4.0 engine in Second Life will attempt to work with holes in objects at first, but if the collisions can not be resolved in a reasonably short amount of time, the engine will revert to treating the objects as solid and cause the objects to separate until they do not touch. The Havok 4.0 engine goes further if that does not work, and will render one or more objects phantom to stop the objects from causing further unresolvable physics engine lag.<br /> <br /> Free open source engines may not provide the same collision resolving features as the commercial Havok engine.</div>

Dale Mahalko http://opensimulator.org/wiki/Physics 2010-04-04T08:50:00Z

<p>Dale Mahalko: more about how collisions work. objects causing continuous high resolver load can be defensively turned phantom by some physics engines</p> <hr /> <div>__NOTOC__<br /> {{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> By default, Open Simulator uses an extremely simple physics engine which only allows you to stand on the ground. All objects using the basic physics engine appear to be phantom, and the only way to make them act as solids is to use some other more sophisticated physics engine, such as the [[Open Dynamics Engine]].<br /> <br /> Note that physics processing is one of the biggest sources of region simulator lag. If you use a better engine to make objects appear to be solid, you will most likely want to isolate the region simulator and physics engine on its own physical hardware so that lag in the physics engine does not also slow down your asset and inventory servers.<br /> <br /> == The role of the physics engine ==<br /> One of the primary functions of the simulator is to provide an experience that approximates real life. This typically requires making the objects in the 3D world appear to be solid and ''real''.<br /> <br /> As far as the simulator database engine is concerned, it simply knows the positions of objects in the simulated 3D space and knows the references to textures for each surface of the objects. The database engine does not know anything about gravity, pushes, or collisions.<br /> <br /> It is technically possible to connect to a simulator without a physics engine, but the avatars would appear to float in space without gravity and can pass through any object including other avatars, and move in any direction to the coordinate limits of the simulated space.<br /> <br /> The primary task of the physics engine is to move objects affected by forces and to resolve collisions. Collisions occur when two physical objects collide or are simply touching each other.<br /> <br /> Most objects in the simulator are pinned in space and do not move. They do not normally require any physics processing time. However, when a physical moving object collides with a pinned object, the pinned object is temporarily treated as if it were physical and collisions are calculated against it. Since it cannot move, the only resolving forces are applied to the movable object.<br /> <br /> In certain unresolvable situations (described below) a physical moving object causing continuous high simulator load may be defensively changed by the simulator into a nonphysical or phantom object, so that the simulator does not become stuck in a continuous high-load state.<br /> <br /> == Gravity and the ground ==<br /> <br /> The single biggest force in the simulator is gravity, which causes physical objects to move downward (Z axis in the 3D coordinate system), typically following Earth-based experience of accelerating to a terminal falling velocity of 9.81 meters per second.<br /> <br /> There is also a deformable plane surface in each sim which is the lowest point any object can descend. We call this the ground or the ''surface patch''. If the ground did not exist, physical objects in the simulator would simply fall to the lowest possible Z axis coordinate value of zero and simply stop, apparantly suspended above/in nothingness. This is outside our normal experience so we have the ground in the simulator to make the simulated world seem more like real life.<br /> <br /> When objects affected by gravity collide with the ground in the simulator, the physics engine resolves the collision by pushing back on the colliding object, causing it to rise up out of the ground against the force of gravity. If the forces are treated as springs, and the object is elastic while the ground is hard and resilient, the simulator can apply an opposite upward force equal to the downward force to cause a fast moving object to &quot;bounce&quot; upward again.<br /> <br /> As mentioned above, the default basic physics engine included with Open Simulator only resolves collisions with the ground, and makes no attempt to make object primitives appear to be solid. As a result, a basic install of Open Simulator will tend to have a mostly flat world layout following the ground surface because that is the only place where people can walk around in a realistic looking manner. Walking around in the second floor of a house made from primitives suspended in midair above the ground for example is not possible.</div>

Dale Mahalko http://opensimulator.org/wiki/Physics 2010-04-04T08:34:08Z

<p>Dale Mahalko: Flesh out this important but empty article: OpenSim resolves against the ground only by default. Role of physics engine vs simulator db engine. Importance of gravity and the surface patch in realism.</p> <hr /> <div>__NOTOC__<br /> {{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> By default, Open Simulator uses an extremely simple physics engine which only allows you to stand on the ground. All objects using the basic physics engine appear to be phantom, and the only way to make them act as solids is to use some other more sophisticated physics engine, such as the [[Open Dynamics Engine]].<br /> <br /> Note that physics processing is one of the biggest sources of region simulator lag. If you use a better engine to make objects appear to be solid, you will most likely want to isolate the region simulator and physics engine on its own physical hardware so that lag in the physics engine does not also slow down your asset and inventory servers.<br /> <br /> == The role of the physics engine ==<br /> One of the primary functions of the simulator is to provide an experience that approximates real life. This typically requires making the objects in the 3D world appear to be solid and ''real''.<br /> <br /> As far as the simulator database engine is concerned, it simply knows the positions of objects in the simulated 3D space and knows the references to textures for each surface of the objects. The database engine does not know anything about gravity, pushes, or collisions.<br /> <br /> It is technically possible to connect to a simulator without a physics engine, but the avatars would appear to float in space without gravity and can pass through any object including other avatars, and move in any direction to the coordinate limits of the simulated space.<br /> <br /> == Gravity and the ground ==<br /> The primary task of the physics engine is to move objects affected by forces and to resolve collisions. Collisions occur when two physical objects collide or are simply touching each other.<br /> <br /> The single biggest force in the simulator is gravity, which causes physical objects to move downward (Z axis in the 3D coordinate system), typically following Earth-based experience of accelerating to a terminal falling velocity of 9.81 meters per second.<br /> <br /> There is also a deformable plane surface in each sim which is the lowest point any object can descend. We call this the ground or the ''surface patch''. If the ground did not exist, physical objects in the simulator would simply fall to the lowest possible Z axis coordinate value of zero and simply stop, apparantly suspended above/in nothingness. This is outside our normal experience so we have the ground in the simulator to make the simulated world seem more like real life.<br /> <br /> When objects affected by gravity collide with the ground in the simulator, the physics engine resolves the collision by pushing back on the colliding object, causing it to rise up out of the ground against the force of gravity. If the forces are treated as springs, and the object is elastic while the ground is hard and resilient, the simulator can apply an opposite upward force equal to the downward force to cause a fast moving object to &quot;bounce&quot; upward again.<br /> <br /> As mentioned above, the default basic physics engine included with Open Simulator only resolves collisions with the ground, and makes no attempt to make object primitives appear to be solid. As a result, a basic install of Open Simulator will tend to have a mostly flat world layout following the ground surface because that is the only place where people can walk around in a realistic looking manner. Walking around in the second floor of a house made from primitives suspended in midair above the ground for example is not possible.</div>

Dale Mahalko http://opensimulator.org/wiki/Troubleshooting 2010-04-04T06:08:17Z

<p>Dale Mahalko: /* Get &quot;Primitive: Error compiling script: ApplicationName='gmcs', ...&quot; when compiling script */ error formatting</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> This page gives any system-specific configuration settings that may be useful, and advice for problems that might be encountered.<br /> __TOC__<br /> {{clear}}<br /> [[Category:Users]]<br /> <br /> == System-specific configuration ==<br /> === CentOS 5 ===<br /> <br /> To install mono and nant, you can use the &quot;Linux Installer for x86&quot; found at http://www.mono-project.com/Downloads.<br /> <br /> SVN can be installed by:<br /> <br /> yum install subversion<br /> <br /> Mono defaults to installing into &lt;tt&gt;/opt&lt;/tt&gt;, so you may have to add this path to your environment variables, for example, in your &lt;tt&gt;~/.bashrc&lt;/tt&gt;:<br /> <br /> export PATH=&quot;/opt/mono-1.2.5/bin:$PATH&quot;<br /> export PKG_CONFIG_PATH=&quot;/opt/mono-1.2.5/lib/pkgconfig:$PKG_CONFIG_PATH&quot;<br /> export MANPATH=&quot;/opt/mono-1.2.5/share/man:$MANPATH&quot;<br /> export LD_LIBRARY_PATH=&quot;/opt/mono-1.2.5/lib:$LD_LIBRARY_PATH&quot;<br /> <br /> After changing &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt;, you should update the dynamic linker cache:<br /> <br /> ldconfig<br /> <br /> You may still encounter the &quot;The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file.&quot; error listed below. In that case, this may fix this:<br /> <br /> yum install glib<br /> <br /> If you are running a firewall as well (i.e., if &lt;tt&gt;iptables -L&lt;/tt&gt; shows a list of ACCEPT and REJECT rules), you'll have to open the necessary ports if you want to access the sim from other machines. For standalone mode:<br /> <br /> iptables -I RH-Firewall-1-INPUT -p tcp --dport 9000 -j ACCEPT<br /> iptables -I RH-Firewall-1-INPUT -p udp --dport 9000 -j ACCEPT<br /> <br /> 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:<br /> sudo yum install libgdiplus<br /> sudo yum install libexif<br /> sudo ln -s /usr/lib64/libgdiplus.so.0 /usr/lib64/libgdiplus.so<br /> ldconfig<br /> <br /> That finally enabled me to run OpenSim without errors, and even connect to other grids.<br /> <br /> === Debian 4.0r0 ===<br /> <br /> If you set your system to use unstable sources, and then install some packages listed below, everything should just work. To use unstable sources, modify your &lt;tt&gt;/etc/apt/sources.list&lt;/tt&gt; file, replacing 'etch' or 'stable' with 'unstable':<br /> <br /> deb ftp://ftp.debian.org/debian/ unstable main<br /> deb-src ftp://ftp.debian.org/debian/ unstable main<br /> <br /> Then update your packages to the new versions:<br /> <br /> apt-get update<br /> apt-get dist-upgrade<br /> <br /> This will probably change a large number of packages, and may break things.<br /> In my experience, however, if you do not use unstable sources then the packages are not up to date enough, and you run into version issues, which lead to two DllNotFoundException errors below appearing in the console output: gdiplus.dll and libopenjpeg-libsl-2.1.2.0.so.<br /> <br /> Once the sources are updated, we need to install the necessary packages to be able to build OpenSim:<br /> <br /> apt-get install subversion mono nant mono-gmcs mono-mjs libmono-microsoft8.0-cil libmono-system-runtime2.0-cil<br /> <br /> If any of these packages are missing, you'll probably encounter one of the errors listed below. However, with these packages, OpenSim should build cleanly.<br /> <br /> Please note: If you are using mysql as storage on unstable you may get the following error:-<br /> <br /> Exception: System.NotSupportedException: CodePage 1252 not supported<br /> at System.Text.Encoding.GetEncoding (Int32 codePage) [0x00000] <br /> <br /> To get it to work, try installing the libmono-i18n2.0-cil package<br /> <br /> apt-get install libmono-i18n2.0-cil<br /> <br /> === Gentoo ===<br /> some Mono dependency &amp; latest Mono itself may use &quot;~x86&quot; masked packages (assuming x86 is your platform, change may be made to reflect your ex:&quot;~amd64&quot; for 64bits). You could check for USE parameter with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge -vp subversion nant mono libgdiplus<br /> <br /> Then install with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge subversion nant mono libgdiplus<br /> <br /> N.B: The ACCEPT_KEYWORDS=&quot;~x86&quot; 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<br /> <br /> === Mac OS X ===<br /> This assumes you're using the universal binary for mono from the [http://www.mono-project.com/ Mono Project] site.<br /> <br /> If you are using OS X 10.4, you should also install X11 from the OS X install CDs.<br /> In OS X 10.5, this is not required.<br /> <br /> If you get errors about the 2.0 framework not being supported, you may need to update your &lt;tt&gt;pkg-config&lt;/tt&gt; path.<br /> I set this in &lt;tt&gt;~/.bash_profile&lt;/tt&gt;:<br /> export PKG_CONFIG_PATH=&quot;/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}&quot;<br /> <br /> == Errors and fixes ==<br /> <br /> === Build workarounds due to non-functionality or bugs: ===<br /> <br /> ==== Disappearing prims due to duplicate UID's ====<br /> 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. This switch is documented in the [[Running#General OpenSim server commands|general server commands]] section. (&lt;nowiki&gt;load-xml &lt;filename&gt; -newUID&lt;/nowiki&gt;). 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.<br /> <br /> ==== Linked objects not scaling/editing properly ====<br /> From Mantis [[http://opensimulator.org/mantis/view.php?id=135 # 135]] and [[http://opensimulator.org/mantis/view.php?id=223 # 223]]: &lt;br /&gt;<br /> Linked objects: while linking/unlinking objects seems to work fine, the editing of single prims inside a linked object doesn't work correctly. You have to check the box &quot;Edit linked parts&quot;, then you can select a single prim and edit it, but in most cases the changes in size- and/or postion-parameters are not accepted and revert immediately to the original ones. It is not completely reproducible, as it may work in some single case though.&lt;br /&gt;<br /> '''Workaround:''' unlink the whole object, make the changes, and relink the whole thing again. &lt;br /&gt; ''note:'' re-scaling unlinked objects in grid mode seems to work better than in standalone. <br /> <br /> &lt;hr&gt;<br /> <br /> === Exception and loss of ode physics (System.EntryPointNotFoundException: dSpaceLockQuery) ===<br /> <br /> The following error is usually caused by using the wrong version of ''libode'':<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [SCENE] [02-01 22:20:40] System.EntryPointNotFoundException: dSpaceLockQuery<br /> :at (wrapper managed-to-native) Ode.NET.d:SpaceLockQuery (intptr)<br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.waitForSpaceUnlock (IntPtr space) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter.AvatarGeomAndBodyCreation (Single npositionX, Single npositionY, Single npositionZ, Single tensor) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter..ctor (System.String avName, OpenSim.Region.Physics.OdePlugin.OdeScene parent_scene, OpenSim.Region.Physics.Manager.PhysicsVector pos) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.AddAvatar (System.String avName, OpenSim.Region.Physics.Manager.PhysicsVector position) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.AddToPhysicalScene () [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.MakeRootAgent (LLVector3 pos, Boolean isFlying) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.Scene.AgentCrossing (UInt64 regionHandle, LLUUID agentID, LLVector3 position, Boolean isFlying) [0x00000]<br /> |}<br /> <br /> First try searching your filesystem to see if you have other copies of the ode physics engine:<br /> find / -name &quot;libode.so&quot;<br /> Then make sure you have the latest version.<br /> <br /> === MySQL connection errors after about 6-8 hours ===<br /> <br /> 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:<br /> <br /> set global wait_timeout=604800;<br /> <br /> === System.DllNotFoundException: gdiplus.dll ===<br /> <br /> First, check to make sure that &lt;tt&gt;libgdiplus.so&lt;/tt&gt; is known to the dynamic linker:<br /> <br /> /sbin/ldconfig -p | grep libgdiplus<br /> <br /> If nothing is found, make sure that the directory libgdiplus.so exists in is either in your &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt; environment variable or listed in a *.conf file (e.g., gdiplus.conf) in /etc/ld.so.conf.d/. Then run &lt;tt&gt;ldconfig&lt;/tt&gt; to update the cache. Then it should be able to find the library.<br /> <br /> 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 OpenSim with debugging information turned on:<br /> <br /> MONO_LOG_LEVEL=debug mono OpenSim.exe<br /> <br /> {It may show errors loading other libraries, like &lt;tt&gt;libexif.so.9&lt;/tt&gt;. In that case, linking to an existing version of the offending library may work:<br /> <br /> ln -s libexif.so.12 libexif.so.9<br /> <br /> 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 <br /> and add the line <br /> &lt;dllmap dll=&quot;gdiplus.dll&quot; target=&quot;/opt/local/lib/libgdiplus.dylib&quot; os=&quot;!windows&quot;/&gt;<br /> <br /> ''(Is there a cleaner solution than this?)''} **see below for alternative/cleaner fix**<br /> <br /> == When installing mono or libgdiplus0 you may get dependency missing libexif.so.9 == <br /> <br /> 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 )<br /> <br /> === The assembly mscorlib.dll was not found or could not be loaded ===<br /> <br /> 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.<br /> <br /> apt-get install nant<br /> <br /> === External Program Failed: /usr/lib/pkgconfig/../../lib/mono/2.0/gmcs.exe === <br /> <br /> This is quickly fixed by retrieving mono-gmcs.<br /> <br /> apt-get install mono-gmcs<br /> <br /> === The type or namespace name JScript does not exist in the namespace Microsoft ===<br /> <br /> Note that it says JScript over and over again. Hint perhaps?<br /> <br /> apt-get install mono-mjs libmono-microsoft8.0-cil<br /> <br /> On Fedora and OpenSUSE, the needed package is &quot;mono-jscript&quot;.<br /> <br /> === The type or namespace name Tcp does not exist in the namespace System.Runtime.Remoting.Channels ===<br /> <br /> This one is taken care of with a quick install:<br /> <br /> apt-get install libmono-system-runtime2.0-cil<br /> <br /> === Missing: libopenjpeg-libsl-2.1.2.0-x86_64.so ===<br /> <br /> You are probably on a 64-bit linux machine and may need to follow these instructions:<br /> <br /> * [[Installing_and_running_on_x86-64 |Installing and running on x86-64 ]]<br /> <br /> === error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file ===<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> apt-get install libglib2.0-0<br /> <br /> === The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file. ===<br /> <br /> This one seems to be fixed by retrieving the apt version of nant.<br /> <br /> apt-get install nant<br /> <br /> This can also be due to &lt;tt&gt;pkg-config&lt;/tt&gt; not being able to locate the &lt;tt&gt;mono.pc&lt;/tt&gt; file. Adding the directory containing this file to the environment variable &lt;tt&gt;PKG_CONFIG_PATH&lt;/tt&gt; may solve this.<br /> <br /> == Networking and config issues ==<br /> <br /> See also the wiki page:<br /> * [[Running]]<br /> <br /> === You are able to log in, but not connect to a Region from a remote client ===<br /> <br /> Look in your OpenSimulator/bin/Regions folder <br /> # Try '''0.0.0.0''' for the internal_ip_address in your region.xml(default.xml) file.&lt;br&gt;(you'll have one of these files for each region you have created)<br /> # '''external_host_name=&quot;127.0.0.1&quot;''' will need to be changed to the accessable DNS name such as &quot;opensim.example-host.com&quot; or &quot;71.6.131.152&quot; (your public accessable ip)<br /> <br /> ==Building OpenSim==<br /> ===I can't find any build files or solution files===<br /> * If you're on Windows, run<br /> runprebuild.bat<br /> * on Linux/Mac/FreeBSD, run <br /> runprebuild.sh<br /> <br /> === VS2005 won't open the .sln file ===<br /> * Try running VS2005 C#. You are probably running VS2005 C++. This is a C# project.<br /> <br /> ==Running OpenSim==<br /> === Running OpenSim.exe from a Cygwin shell has access denied for some dll's ===<br /> * Do a '&lt;tt&gt;cd bin&lt;/tt&gt;' followed by '&lt;tt&gt;chmod a+x *&lt;/tt&gt;' to make all dll files executable.<br /> ===I cannot start my sim===<br /> * See [[Configuration]]<br /> <br /> ==Something Has Gone Wrong!==<br /> === I get errors concerning 'owner_uuid' when starting up my grid after updating from svn beyond r3254 ===<br /> When updating to recent revisions after r3254, we are now using the unused owner_uuid. There are some grids whose mysql tables were created during a time when this field was inadvertently removed from the .sql script that initializes the regions table. Logging in to your mysql instance and executing this SQL query to add the missing owner_uuid should solve this issue:<br /> alter table `regions` add column `owner_uuid` varchar(36) default '00000000-0000-0000-0000-000000000000' not null, comment 'Rev.2';<br /> The punctuation around regions and owner_uuid is &quot;grave accent&quot;. The punctuation around the default value and the comment is the single quote. The &quot;grave accent&quot; is the one generally to the left of the One button, under the tilde and the single-quote, is, well, underneath the double quote. I think this matters to mysql.<br /> <br /> === I get errors concerning 'State' when starting up my grid after updating from svn beyond r3786 ===<br /> After r3786, a new 'State' field has been added to the 'primshapes' table on SQLite. This field is used to persist trees and grass.<br /> You may have an empty region at startup, because OpenSim does not find this 'State' field and does not know what to do.<br /> The best is to use SQLiteBrowser or another SQLite table editor (download it at [http://sqlitebrowser.sourceforge.net/ http://sqlitebrowser.sourceforge.net/]) to create the missing field:<br /> alter table primshapes add column State integer default 0<br /> Just launch SQLiteBrowser, use File/Open database, then browse to OpenSim.db file and open it. Then, go to the &quot;Execute SQL&quot; tab, copy/paste the command above in the &quot;SQL string&quot; textbox, then hit the &quot;Execute query&quot; button.<br /> <br /> === I get a timeout during region handshake ===<br /> * Do you have the correct IP in your Regions\* config files?<br /> * Do you have multiple interfaces on the server running OpenSim? OpenSim 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.<br /> <br /> === I cannot connect to my OpenSim ===<br /> * See [[OpenSim: Connecting]]<br /> <br /> ===I can connect but cannot move===<br /> If the client connects but the avatar can only spin in place and not move, then the sim is not correctly configured. It completed the initial login function, but packets are not being exchanged between the client and the sim, probably due to a network configuration error on the sim.<br /> * See [[OpenSim: Configuration]]<br /> <br /> === From time to time my Avatar seems to get stuck ===<br /> Right now there is a bottle neck when syncing prims off to the database. This will cause small (5 - 10 second) apparent hangs of the Avatar, but it will recover fine once the data is synced. It is a known issue based on legacy architecture of some of the data storage code. We hope this will be removed soon.<br /> <br /> === I have problems with viewing the worldmap ===<br /> * This may happen when running OpenSim on a Linux server, both in grid or standalone mode.<br /> * 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...<br /> * Reason: your svn source trunk does not have the correct (or whatever...) &lt;tt&gt;libopenjpeg-libsl&lt;/tt&gt; library.<br /> * Other reason: the file &quot;defaultstripe.png&quot; does not exists in the same OpenSim folder, or is corrupted.<br /> * Solution: get the newest code from libsecondlife (&lt;tt&gt;svn co svn://opensecondlife.org/libsl/trunk&lt;/tt&gt;), '&lt;tt&gt;make&lt;/tt&gt;' manually in the subdir &lt;tt&gt;openjpeg-libsl&lt;/tt&gt;, and copy the resulting &lt;tt&gt;libopenjpeg-libsl-2.1.2.0.so&lt;/tt&gt; into your OpenSim &lt;tt&gt;bin&lt;/tt&gt; subdir, overwriting the existing one.<br /> * Recompile &amp; restart OpenSim<br /> <br /> ==Exceptions on the Console==<br /> This is a list of Exceptions that you may see on the console, what they mean, and if they are a problem.<br /> <br /> ===System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so===<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> Failed generating terrain map: System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so<br /> : at (wrapper managed-to-native) OpenJPEGNet.OpenJPEG:LibslAllocDecoded OpenJPEGNet.OpenJPEG/LibslImage&amp;)<br /> : at OpenJPEGNet.OpenJPEG.Encode (System.Byte[] decoded, Int32 width, Int32 height, Int32 components, Boolean lossless) [0x00000]<br /> :at OpenJPEGNet.OpenJPEG.EncodeFromImage (System.Drawing.Bitmap bitmap, Boolean lossless) [0x00000]<br /> :at OpenSim.Region.Terrain.TerrainEngine.ExportJpegImage (System.String gradientmap) [0x00000]<br /> |}<br /> <br /> 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:<br /> * You have an old processor (libopenjpeg has been compiled with optimizations)<br /> * You are running in 64bit mode (none of the native libs are built for 64bit)<br /> <br /> You can rebuild your own libopenjpeg from source, or run in a compatible environment.<br /> You can do this by:<br /> svn co svn://openmv.org/libsl/libopenmetaverse/trunk libsl<br /> cd libsl/openjpeg-libsl/<br /> make<br /> <br /> then copy libopenjpeg-libsl-2.1.2.0.so into OpenSim bin-folder.<br /> <br /> === System.NullReferenceException at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion ===<br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [LOGIN END]: XMLRPC Login failed, System.NullReferenceException: Object reference not set to an instance of an object<br /> :at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion (OpenSim.Framework.RegionInfo regionInfo, OpenSim.Framework.UserProfileData user, OpenSim.Framework.Communications.LoginResponse response) [0x00000] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:293<br /> :at OpenSim.Region.Communications.Local.LocalLoginService.CustomiseResponse (OpenSim.Framework.Communications.LoginResponse response, OpenSim.Framework.UserProfileData theUser, System.String startLocationRequest) [0x00520] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:253<br /> :at OpenSim.Framework.Communications.LoginService.XmlRpcLoginMethod (Nwc.XmlRpc.XmlRpcRequest request) [0x00369] in /home/sim/svn/opensim/OpenSim/Framework/Communications/LoginService.cs:252<br /> |}<br /> <br /> Your first startup of OpenSim 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.<br /> <br /> ==Grid Mode==<br /> Note: Grid Mode isn't officially supported yet. As such, you are pretty much on your own if you are trying to get OpenSim up and running in Grid Mode.<br /> <br /> === I start the sim and it doesn't connect to any grid ===<br /> <br /> When OpenSim is first started, it needs configuration.<br /> <br /> * See [[OpenSim: Configuration]].<br /> <br /> === I start the OpenSim.Grid.UserServer.exe and it gives an error===<br /> If this error is access denied for &lt;tt&gt;username@localhost&lt;/tt&gt;, the mysql database is not set up.<br /> It will print some text and wait for input - either an enter to accept a default value, or another value you can supply.<br /> * See [[OpenSim: Configuration]].<br /> <br /> === I want to run my own Local Grid but one or more servers fail to start===<br /> * Be sure that you're able to start &lt;tt&gt;OpenSim.exe&lt;/tt&gt; alone, in Standalone mode, and to be able to login.<br /> * Start the servers in the correct UGAS order and answer the questions as recommended (see [[OpenSim: Configuration]]).<br /> * Set all the external URI's to the correct IP: 127.0.0.1 if running on your local machine, or aaa.bbb.ccc.ddd if running on a remote server.<br /> * Check again all the &lt;tt&gt;*.xml&lt;/tt&gt; configuration files for any wrong settings or typing errors...!<br /> * Don't forget to connect with your SL-viewer to port 8002 (Grid User-Server) instead of 9000 (Standalone OpenSim-Server).<br /> * Delete all &lt;tt&gt;*.xml&lt;/tt&gt; and &lt;tt&gt;*.yap&lt;/tt&gt; files in the &lt;tt&gt;bin&lt;/tt&gt; directory if you want to run a full reconfiguration again.<br /> <br /> === I get a bunch of asset not found errors, while connected to a online grid, and my inventory doesn't seem to work right===<br /> *Make sure your opensim.ini has ' asset_database = &quot;grid&quot; ' otherwise it will not work correctly.<br /> <br /> === My grid works fine with one user but when two users login in the same time both get stuck ===<br /> * Make sure you have export MONO_THREADS_PER_CPU=&quot;100&quot; in your environment<br /> <br /> === After ~20 minutes my region starts to take 100% cpu and region(s) hang ===<br /> * If you have mono 1.9.1 or lower upgrade to mono 2.2.<br /> <br /> ==Hypergrid==<br /> ===After starting OpenSim with Hypergrid enabled my inventory wont load!===<br /> *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.<br /> *Check the XML config files for your UGAIM servers to make sure that everything is running off of a publicly accessible IP address.<br /> **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.<br /> <br /> 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.<br /> <br /> &lt;div align = center&gt;&lt;B&gt;!!!!WARNING!!!! - Be smart! Always make a backup of your databases before making any changes to OpenSim! - !!!!WARNING!!!!&lt;/b&gt;&lt;/div&gt;<br /> &lt;pre&gt;<br /> update users set userInventoryURI=&quot;http://new.UGAIM.address:8004&quot; where userInventoryURI = &quot;http://old.UGAIM.address:8004&quot;;<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> update users set userAssetURI=&quot;http://new.UGAIM.address:8003&quot; where userAssetURI = &quot;http://old.UGAIM.address:8003&quot;;<br /> &lt;/pre&gt;<br /> *If you're running in standalone mode... - Anyone familiar with standalone want to fill this in? -<br /> [[Category:Users]]<br /> <br /> == ScriptEngine Issues ==<br /> === Got &quot;Primitive: Error compiling script: unknown char: . error&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you could have this error :<br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> Primitive: Error compiling script:<br /> unknown char: .<br /> |}<br /> <br /> And on the console :<br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Unloading script&lt;br&gt;<br /> 11:06:37 - Exception in MaintenanceLoopThread. Thread will recover after 5 sec throttle. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.<br /> :at System.Collections.Generic.Dictionary`2[OpenSim.Region.ScriptEngine.Interfaces.IEventReceiver, OpenSim.Region.ScriptEngine.Shared.Api.Plugins.Dataserver].get_Item (IEventReceiver key) [0x00000]<br /> :at OpenSim.Region.ScriptEngine.Shared.Api.AsyncCommandManager.RemoveScript (IEventReceiver engine, UInt32 localID, UUID itemID) [0x00000]<br /> :at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager._StopScript (UInt32 localID, UUID itemID) [0x00000]<br /> :at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager.DoScriptLoadUnload () [0x00000]<br /> :at OpenSim.Region.ScriptEngine.DotNetEngine.MaintenanceThread.MaintenanceLoop () [0x00000]<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Loading script&lt;br&gt;<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: ScriptManager StartScript: localID: 720001, itemID: 88c9d28c-6004-4609-a707-717190de044a&lt;br&gt;<br /> 11:06:37 - [Compiler]: Compiled new assembly for fad15951-f9aa-493f-be68-2aaf5ff8a3c9&lt;br&gt;<br /> 11:06:37 - [SCRIPT]: Compiled assetID fad15951-f9aa-493f-be68-2aaf5ff8a3c9: ScriptEngines/a83150da-1ab1-11dd-89fb-0014853ee9da/CommonCompiler_compiled_fad15951-f9aa-493f-be68-2aaf5ff8a3c9.dll&lt;br&gt;<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: AppDomain Loading: OpenSim.Region.ScriptEngine.Shared, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null<br /> |}<br /> <br /> This happens on '''linux''' when your locales are not set to default ( &quot;C&quot; ).<br /> * You could refer to [http://opensimulator.org/mantis/view.php?id=2088 Mantis #2088] and [http://opensimulator.org/mantis/view.php?id=2015 Mantis #2015] for a workaround to run opensim.<br /> &lt;pre&gt;<br /> env LANG=C mono --debug OpenSim.exe<br /> &lt;/pre&gt;<br /> * You could also change your locale setup. Here is what I use in my '.bash_profile' :<br /> &lt;pre&gt;<br /> export LC_ALL=C<br /> export LANG=C<br /> &lt;/pre&gt;<br /> I know it's a ugly way to setup locales on a linux box, but it works fine on my '''Linux From Scratch''' box.<br /> <br /> '''Rq''': I saw Melanie has corrected some parts of the source code a few weeks ago to avoid such problems.<br /> <br /> === Get &quot;Primitive: Error compiling script: ApplicationName='gmcs', ...&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you have an error something like :<br /> <br /> {| width=&quot;100%&quot;<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> Primitive: Error compiling script:&lt;br&gt;<br /> ApplicationName='gmcs', CommandLine='/target:library /debug+ /optimize- /out:<br /> :&quot;ScriptEngines/430c29d0-c5c6-11dd-ad8b-0800200c9a66/CommonCompiler_compiled_fbe5e682-afae-4f1a-805b-0125031101f7.dll&quot; <br /> :/r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.dll&quot;<br /> :/r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.Api.Runtime.dll&quot; -- <br /> :&quot;/tmp/11b81aac/594d02ce.0.cs&quot; ', CurrentDirectory=''<br /> |}<br /> <br /> Other features include &quot;Touch&quot; being disabled on the right click menu wheel.<br /> <br /> You might have a broken mono install (i.e. discovered as mono but not gmcs installed on a Ubuntu 8.10 Intrepid machine.)<br /> <br /> Check mono-gmcs (sudo apt-get install mono-gmcs) is correctly installed.<br /> <br /> == Locales Issues ==<br /> Well, some of us, OpenSim users, ran into random crash of the OpenSim Region server in grid mode ... <br /> <br /> I have made many tests to find a solution about that problem.<br /> <br /> I first ran into this problem with OpenSIM SVN.6660 ... Even if I have no users connected, my OpenSim region server randomly crash ( after 1 hour, or 5 hours, ... ).<br /> <br /> My first idea was to upgrade to the latest SVN release, no chance, same problem. So I made a test with a previous SVN release ( SVN.6575 ) which is running fine on another server ( same OS, same parameters, same mono release, ... ) : No chance, same problem.<br /> <br /> Then, I tried to play with locales, recompile the '''screen''' unix command line utility I use to run my servers, ... No chance again.<br /> <br /> So, I checked the memory usage on my Server, and I discovered that with the last SVN release, the amount of memory needed to run OpenSim server in multi-region/grid mode increased :) ... So, I have tuned my MySQL server to use less memory. Was better, but my OpenSim region server still randomly crash ( but could stay alive longer than before ).<br /> <br /> Then, trying to play with the '''screen''' command line options ... And all my tests shows that the '''--debug''' option impact the stability of the server.<br /> <br /> Initially, I used such command line to run OpenSim :<br /> &lt;pre&gt;<br /> /screen -S Region-service -d -m --debug mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> Without the '''--debug''' option, everything seems to be more stable.<br /> <br /> About locales, if you read mantis and threads in opensim-dev / opensim-users, you know that there are issues on system that are not &quot;en_US&quot; or &quot;C&quot; local compliant.<br /> <br /> I have re-setup my server to be full &quot;en_US.UTF8&quot;.<br /> <br /> On my Ubuntu 8.0.4 server :<br /> &lt;pre&gt;<br /> # cat /etc/default/locale<br /> LANG=&quot;en_US.UTF-8&quot;<br /> <br /> # cat /var/lib/locales/supported.d/local<br /> fr_FR.UTF-8 UTF-8<br /> en_US.UTF-8 UTF-8<br /> <br /> # cat /etc/environment<br /> PATH=&quot;/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games&quot;<br /> LANG=&quot;en_US&quot;<br /> LANGUAGE=&quot;en_US&quot;<br /> &lt;/pre&gt;<br /> And maybe you should need :<br /> &lt;pre&gt;<br /> # sudo dpkg-reconfigure locales<br /> &lt;/pre&gt;<br /> <br /> So, the resulting '''screen''' command line options should be :<br /> &lt;pre&gt;<br /> screen -S Region-service -d -m -U mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> This allow me to run OpenSim SVN.6575 without crash during more than 48 hours, and also SVN.6735 ... <br /> <br /> Hope those informations could help peoples.<br /> <br /> Just for your information : <br /> <br /> Here is my '''OpenSim Startup script''' :<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> echo &quot;User-Service...&quot;<br /> /usr/local/bin/screen -S User-service -d -m -U mono OpenSim.Grid.UserServer.exe<br /> sleep 5<br /> echo &quot;Grid-Service...&quot;<br /> /usr/local/bin/screen -S Grid-service -d -m -U mono OpenSim.Grid.GridServer.exe<br /> sleep 5<br /> echo &quot;Asset-Service...&quot;<br /> /usr/local/bin/screen -S Asset-service -d -m -U mono OpenSim.Grid.AssetServer.exe<br /> sleep 10<br /> echo &quot;Inventory-Service...&quot;<br /> /usr/local/bin/screen -S Inventory-service -d -m -U mono OpenSim.Grid.InventoryServer.exe<br /> sleep 5<br /> echo &quot;Region-Service...&quot;<br /> /usr/local/bin/screen -S Region-service -d -m -U mono OpenSim.exe<br /> sleep 5<br /> echo &quot; &quot;<br /> echo &quot; &quot;<br /> /usr/local/bin/screen -list<br /> &lt;/pre&gt;<br /> <br /> Here is also a small script that give you a menu to connect to the '''screen(s)''' sessions :<br /> &lt;pre&gt;<br /> #!/usr/bin/perl<br /> <br /> use strict;<br /> use Term::Menu;<br /> <br /> my $EXIT = 1;<br /> <br /> my $MainTitle = &quot;+-----------------------------------------------------+\n&quot;;<br /> $MainTitle .= &quot;| Connexion SCREEN aux Serveurs OPENSIM |\n&quot;;<br /> $MainTitle .= &quot;| |\n&quot;;<br /> $MainTitle .= &quot;| ( Type CTRL+A+D to exit the Screen Console. ) |\n&quot;;<br /> $MainTitle .= &quot;+-----------------------------------------------------+\n&quot;;<br /> <br /> while ( $EXIT == 1 )<br /> {<br /> <br /> system(&quot;screen -list | grep service &gt; /tmp/osg.services&quot;);<br /> my %LIST = ();<br /> open(IN, &quot;/tmp/osg.services&quot;);<br /> while ( my $i = &lt;IN&gt; )<br /> {<br /> chomp($i);<br /> <br /> $i =~ s/\./#/g;<br /> $i =~ s/\-service\t/#/g;<br /> $i =~ s/\t//g;<br /> $i =~ s/\(//g;<br /> $i =~ s/\)//g;<br /> <br /> my @STATUS = split(/#/, $i);<br /> $LIST{$STATUS[1]} = $STATUS[2];<br /> }<br /> close(IN);<br /> <br /> my %LIST2 = ();<br /> my @indices = ('User', 'Grid', 'Asset', 'Inventory', 'Region');<br /> <br /> foreach my $key ( @indices )<br /> {<br /> # print &quot;$key --&gt; $LIST{$key}\n&quot;;<br /> if ( $LIST{$key} =~ /Attached/ )<br /> {<br /> $LIST2{$key} = &quot;[X]&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{$key} = &quot;[ ]&quot;;<br /> }<br /> }<br /> <br /> if ( $LIST{'User'} =~ /Attached/ )<br /> {<br /> $LIST2{'USER'} = &quot;X&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{'USER'} = &quot;-&quot;;<br /> }<br /> <br /> system ('clear');<br /> my $prompt = new Term::Menu (<br /> spaces =&gt; 3,<br /> aftertext =&gt; &quot;\nChoisir une option : &quot;,<br /> beforetext =&gt; ${MainTitle},<br /> delim =&gt; &quot;. &quot;,<br /> );<br /> <br /> my $SEP = &quot; &quot;;<br /> <br /> my $answer = $prompt-&gt;menu(<br /> osg_user =&gt; [&quot;OpenSim User Server $SEP$LIST2{'User'}&quot;, '1'],<br /> osg_grid =&gt; [&quot;OpenSim Grid Server $SEP$LIST2{'Grid'}&quot;, '2'],<br /> osg_asset =&gt; [&quot;OpenSim Asset Server $SEP$LIST2{'Asset'}&quot;, '3'],<br /> osg_inventory =&gt; [&quot;OpenSim Inventory Server $SEP$LIST2{'Inventory'}&quot;, '4'],<br /> osg_region =&gt; [&quot;OpenSim Region Server $SEP$LIST2{'Region'}\n&quot;, '5'],<br /> osg_shutdown =&gt; [&quot;Shutdown Servers (Manual)&quot;,'6'],<br /> osg_shutdown2 =&gt; [&quot;Shutdown Servers (Hard)\n&quot;,'7'],<br /> quit =&gt; [&quot;Quitter&quot;, 'q'],<br /> );<br /> <br /> if ( &quot;${answer}&quot; eq &quot;quit&quot; )<br /> {<br /> $EXIT = 0;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_user&quot; )<br /> {<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_grid&quot; )<br /> {<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_asset&quot; )<br /> {<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_inventory&quot; )<br /> {<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_region&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown2&quot; )<br /> {<br /> # system(&quot;/OPENSIM/shutdownGrid.py&quot;);<br /> system(&quot;screen -S Region-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Inventory-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Asset-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Grid-service -r -m -X quit&quot;);<br /> system(&quot;screen -S User-service -r -m -X quit&quot;);<br /> $EXIT = 0;<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Regards, <br /> Ursula Matova.</div>

Dale Mahalko http://opensimulator.org/wiki/Troubleshooting 2010-04-04T06:03:09Z

<p>Dale Mahalko: /* Got &quot;Primitive: Error compiling script: unknown char: . error&quot; when compiling script */ reformat error messages to fit on page</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> This page gives any system-specific configuration settings that may be useful, and advice for problems that might be encountered.<br /> __TOC__<br /> {{clear}}<br /> [[Category:Users]]<br /> <br /> == System-specific configuration ==<br /> === CentOS 5 ===<br /> <br /> To install mono and nant, you can use the &quot;Linux Installer for x86&quot; found at http://www.mono-project.com/Downloads.<br /> <br /> SVN can be installed by:<br /> <br /> yum install subversion<br /> <br /> Mono defaults to installing into &lt;tt&gt;/opt&lt;/tt&gt;, so you may have to add this path to your environment variables, for example, in your &lt;tt&gt;~/.bashrc&lt;/tt&gt;:<br /> <br /> export PATH=&quot;/opt/mono-1.2.5/bin:$PATH&quot;<br /> export PKG_CONFIG_PATH=&quot;/opt/mono-1.2.5/lib/pkgconfig:$PKG_CONFIG_PATH&quot;<br /> export MANPATH=&quot;/opt/mono-1.2.5/share/man:$MANPATH&quot;<br /> export LD_LIBRARY_PATH=&quot;/opt/mono-1.2.5/lib:$LD_LIBRARY_PATH&quot;<br /> <br /> After changing &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt;, you should update the dynamic linker cache:<br /> <br /> ldconfig<br /> <br /> You may still encounter the &quot;The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file.&quot; error listed below. In that case, this may fix this:<br /> <br /> yum install glib<br /> <br /> If you are running a firewall as well (i.e., if &lt;tt&gt;iptables -L&lt;/tt&gt; shows a list of ACCEPT and REJECT rules), you'll have to open the necessary ports if you want to access the sim from other machines. For standalone mode:<br /> <br /> iptables -I RH-Firewall-1-INPUT -p tcp --dport 9000 -j ACCEPT<br /> iptables -I RH-Firewall-1-INPUT -p udp --dport 9000 -j ACCEPT<br /> <br /> 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:<br /> sudo yum install libgdiplus<br /> sudo yum install libexif<br /> sudo ln -s /usr/lib64/libgdiplus.so.0 /usr/lib64/libgdiplus.so<br /> ldconfig<br /> <br /> That finally enabled me to run OpenSim without errors, and even connect to other grids.<br /> <br /> === Debian 4.0r0 ===<br /> <br /> If you set your system to use unstable sources, and then install some packages listed below, everything should just work. To use unstable sources, modify your &lt;tt&gt;/etc/apt/sources.list&lt;/tt&gt; file, replacing 'etch' or 'stable' with 'unstable':<br /> <br /> deb ftp://ftp.debian.org/debian/ unstable main<br /> deb-src ftp://ftp.debian.org/debian/ unstable main<br /> <br /> Then update your packages to the new versions:<br /> <br /> apt-get update<br /> apt-get dist-upgrade<br /> <br /> This will probably change a large number of packages, and may break things.<br /> In my experience, however, if you do not use unstable sources then the packages are not up to date enough, and you run into version issues, which lead to two DllNotFoundException errors below appearing in the console output: gdiplus.dll and libopenjpeg-libsl-2.1.2.0.so.<br /> <br /> Once the sources are updated, we need to install the necessary packages to be able to build OpenSim:<br /> <br /> apt-get install subversion mono nant mono-gmcs mono-mjs libmono-microsoft8.0-cil libmono-system-runtime2.0-cil<br /> <br /> If any of these packages are missing, you'll probably encounter one of the errors listed below. However, with these packages, OpenSim should build cleanly.<br /> <br /> Please note: If you are using mysql as storage on unstable you may get the following error:-<br /> <br /> Exception: System.NotSupportedException: CodePage 1252 not supported<br /> at System.Text.Encoding.GetEncoding (Int32 codePage) [0x00000] <br /> <br /> To get it to work, try installing the libmono-i18n2.0-cil package<br /> <br /> apt-get install libmono-i18n2.0-cil<br /> <br /> === Gentoo ===<br /> some Mono dependency &amp; latest Mono itself may use &quot;~x86&quot; masked packages (assuming x86 is your platform, change may be made to reflect your ex:&quot;~amd64&quot; for 64bits). You could check for USE parameter with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge -vp subversion nant mono libgdiplus<br /> <br /> Then install with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge subversion nant mono libgdiplus<br /> <br /> N.B: The ACCEPT_KEYWORDS=&quot;~x86&quot; 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<br /> <br /> === Mac OS X ===<br /> This assumes you're using the universal binary for mono from the [http://www.mono-project.com/ Mono Project] site.<br /> <br /> If you are using OS X 10.4, you should also install X11 from the OS X install CDs.<br /> In OS X 10.5, this is not required.<br /> <br /> If you get errors about the 2.0 framework not being supported, you may need to update your &lt;tt&gt;pkg-config&lt;/tt&gt; path.<br /> I set this in &lt;tt&gt;~/.bash_profile&lt;/tt&gt;:<br /> export PKG_CONFIG_PATH=&quot;/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}&quot;<br /> <br /> == Errors and fixes ==<br /> <br /> === Build workarounds due to non-functionality or bugs: ===<br /> <br /> ==== Disappearing prims due to duplicate UID's ====<br /> 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. This switch is documented in the [[Running#General OpenSim server commands|general server commands]] section. (&lt;nowiki&gt;load-xml &lt;filename&gt; -newUID&lt;/nowiki&gt;). 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.<br /> <br /> ==== Linked objects not scaling/editing properly ====<br /> From Mantis [[http://opensimulator.org/mantis/view.php?id=135 # 135]] and [[http://opensimulator.org/mantis/view.php?id=223 # 223]]: &lt;br /&gt;<br /> Linked objects: while linking/unlinking objects seems to work fine, the editing of single prims inside a linked object doesn't work correctly. You have to check the box &quot;Edit linked parts&quot;, then you can select a single prim and edit it, but in most cases the changes in size- and/or postion-parameters are not accepted and revert immediately to the original ones. It is not completely reproducible, as it may work in some single case though.&lt;br /&gt;<br /> '''Workaround:''' unlink the whole object, make the changes, and relink the whole thing again. &lt;br /&gt; ''note:'' re-scaling unlinked objects in grid mode seems to work better than in standalone. <br /> <br /> &lt;hr&gt;<br /> <br /> === Exception and loss of ode physics (System.EntryPointNotFoundException: dSpaceLockQuery) ===<br /> <br /> The following error is usually caused by using the wrong version of ''libode'':<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [SCENE] [02-01 22:20:40] System.EntryPointNotFoundException: dSpaceLockQuery<br /> :at (wrapper managed-to-native) Ode.NET.d:SpaceLockQuery (intptr)<br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.waitForSpaceUnlock (IntPtr space) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter.AvatarGeomAndBodyCreation (Single npositionX, Single npositionY, Single npositionZ, Single tensor) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter..ctor (System.String avName, OpenSim.Region.Physics.OdePlugin.OdeScene parent_scene, OpenSim.Region.Physics.Manager.PhysicsVector pos) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.AddAvatar (System.String avName, OpenSim.Region.Physics.Manager.PhysicsVector position) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.AddToPhysicalScene () [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.MakeRootAgent (LLVector3 pos, Boolean isFlying) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.Scene.AgentCrossing (UInt64 regionHandle, LLUUID agentID, LLVector3 position, Boolean isFlying) [0x00000]<br /> |}<br /> <br /> First try searching your filesystem to see if you have other copies of the ode physics engine:<br /> find / -name &quot;libode.so&quot;<br /> Then make sure you have the latest version.<br /> <br /> === MySQL connection errors after about 6-8 hours ===<br /> <br /> 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:<br /> <br /> set global wait_timeout=604800;<br /> <br /> === System.DllNotFoundException: gdiplus.dll ===<br /> <br /> First, check to make sure that &lt;tt&gt;libgdiplus.so&lt;/tt&gt; is known to the dynamic linker:<br /> <br /> /sbin/ldconfig -p | grep libgdiplus<br /> <br /> If nothing is found, make sure that the directory libgdiplus.so exists in is either in your &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt; environment variable or listed in a *.conf file (e.g., gdiplus.conf) in /etc/ld.so.conf.d/. Then run &lt;tt&gt;ldconfig&lt;/tt&gt; to update the cache. Then it should be able to find the library.<br /> <br /> 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 OpenSim with debugging information turned on:<br /> <br /> MONO_LOG_LEVEL=debug mono OpenSim.exe<br /> <br /> {It may show errors loading other libraries, like &lt;tt&gt;libexif.so.9&lt;/tt&gt;. In that case, linking to an existing version of the offending library may work:<br /> <br /> ln -s libexif.so.12 libexif.so.9<br /> <br /> 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 <br /> and add the line <br /> &lt;dllmap dll=&quot;gdiplus.dll&quot; target=&quot;/opt/local/lib/libgdiplus.dylib&quot; os=&quot;!windows&quot;/&gt;<br /> <br /> ''(Is there a cleaner solution than this?)''} **see below for alternative/cleaner fix**<br /> <br /> == When installing mono or libgdiplus0 you may get dependency missing libexif.so.9 == <br /> <br /> 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 )<br /> <br /> === The assembly mscorlib.dll was not found or could not be loaded ===<br /> <br /> 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.<br /> <br /> apt-get install nant<br /> <br /> === External Program Failed: /usr/lib/pkgconfig/../../lib/mono/2.0/gmcs.exe === <br /> <br /> This is quickly fixed by retrieving mono-gmcs.<br /> <br /> apt-get install mono-gmcs<br /> <br /> === The type or namespace name JScript does not exist in the namespace Microsoft ===<br /> <br /> Note that it says JScript over and over again. Hint perhaps?<br /> <br /> apt-get install mono-mjs libmono-microsoft8.0-cil<br /> <br /> On Fedora and OpenSUSE, the needed package is &quot;mono-jscript&quot;.<br /> <br /> === The type or namespace name Tcp does not exist in the namespace System.Runtime.Remoting.Channels ===<br /> <br /> This one is taken care of with a quick install:<br /> <br /> apt-get install libmono-system-runtime2.0-cil<br /> <br /> === Missing: libopenjpeg-libsl-2.1.2.0-x86_64.so ===<br /> <br /> You are probably on a 64-bit linux machine and may need to follow these instructions:<br /> <br /> * [[Installing_and_running_on_x86-64 |Installing and running on x86-64 ]]<br /> <br /> === error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file ===<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> apt-get install libglib2.0-0<br /> <br /> === The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file. ===<br /> <br /> This one seems to be fixed by retrieving the apt version of nant.<br /> <br /> apt-get install nant<br /> <br /> This can also be due to &lt;tt&gt;pkg-config&lt;/tt&gt; not being able to locate the &lt;tt&gt;mono.pc&lt;/tt&gt; file. Adding the directory containing this file to the environment variable &lt;tt&gt;PKG_CONFIG_PATH&lt;/tt&gt; may solve this.<br /> <br /> == Networking and config issues ==<br /> <br /> See also the wiki page:<br /> * [[Running]]<br /> <br /> === You are able to log in, but not connect to a Region from a remote client ===<br /> <br /> Look in your OpenSimulator/bin/Regions folder <br /> # Try '''0.0.0.0''' for the internal_ip_address in your region.xml(default.xml) file.&lt;br&gt;(you'll have one of these files for each region you have created)<br /> # '''external_host_name=&quot;127.0.0.1&quot;''' will need to be changed to the accessable DNS name such as &quot;opensim.example-host.com&quot; or &quot;71.6.131.152&quot; (your public accessable ip)<br /> <br /> ==Building OpenSim==<br /> ===I can't find any build files or solution files===<br /> * If you're on Windows, run<br /> runprebuild.bat<br /> * on Linux/Mac/FreeBSD, run <br /> runprebuild.sh<br /> <br /> === VS2005 won't open the .sln file ===<br /> * Try running VS2005 C#. You are probably running VS2005 C++. This is a C# project.<br /> <br /> ==Running OpenSim==<br /> === Running OpenSim.exe from a Cygwin shell has access denied for some dll's ===<br /> * Do a '&lt;tt&gt;cd bin&lt;/tt&gt;' followed by '&lt;tt&gt;chmod a+x *&lt;/tt&gt;' to make all dll files executable.<br /> ===I cannot start my sim===<br /> * See [[Configuration]]<br /> <br /> ==Something Has Gone Wrong!==<br /> === I get errors concerning 'owner_uuid' when starting up my grid after updating from svn beyond r3254 ===<br /> When updating to recent revisions after r3254, we are now using the unused owner_uuid. There are some grids whose mysql tables were created during a time when this field was inadvertently removed from the .sql script that initializes the regions table. Logging in to your mysql instance and executing this SQL query to add the missing owner_uuid should solve this issue:<br /> alter table `regions` add column `owner_uuid` varchar(36) default '00000000-0000-0000-0000-000000000000' not null, comment 'Rev.2';<br /> The punctuation around regions and owner_uuid is &quot;grave accent&quot;. The punctuation around the default value and the comment is the single quote. The &quot;grave accent&quot; is the one generally to the left of the One button, under the tilde and the single-quote, is, well, underneath the double quote. I think this matters to mysql.<br /> <br /> === I get errors concerning 'State' when starting up my grid after updating from svn beyond r3786 ===<br /> After r3786, a new 'State' field has been added to the 'primshapes' table on SQLite. This field is used to persist trees and grass.<br /> You may have an empty region at startup, because OpenSim does not find this 'State' field and does not know what to do.<br /> The best is to use SQLiteBrowser or another SQLite table editor (download it at [http://sqlitebrowser.sourceforge.net/ http://sqlitebrowser.sourceforge.net/]) to create the missing field:<br /> alter table primshapes add column State integer default 0<br /> Just launch SQLiteBrowser, use File/Open database, then browse to OpenSim.db file and open it. Then, go to the &quot;Execute SQL&quot; tab, copy/paste the command above in the &quot;SQL string&quot; textbox, then hit the &quot;Execute query&quot; button.<br /> <br /> === I get a timeout during region handshake ===<br /> * Do you have the correct IP in your Regions\* config files?<br /> * Do you have multiple interfaces on the server running OpenSim? OpenSim 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.<br /> <br /> === I cannot connect to my OpenSim ===<br /> * See [[OpenSim: Connecting]]<br /> <br /> ===I can connect but cannot move===<br /> If the client connects but the avatar can only spin in place and not move, then the sim is not correctly configured. It completed the initial login function, but packets are not being exchanged between the client and the sim, probably due to a network configuration error on the sim.<br /> * See [[OpenSim: Configuration]]<br /> <br /> === From time to time my Avatar seems to get stuck ===<br /> Right now there is a bottle neck when syncing prims off to the database. This will cause small (5 - 10 second) apparent hangs of the Avatar, but it will recover fine once the data is synced. It is a known issue based on legacy architecture of some of the data storage code. We hope this will be removed soon.<br /> <br /> === I have problems with viewing the worldmap ===<br /> * This may happen when running OpenSim on a Linux server, both in grid or standalone mode.<br /> * 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...<br /> * Reason: your svn source trunk does not have the correct (or whatever...) &lt;tt&gt;libopenjpeg-libsl&lt;/tt&gt; library.<br /> * Other reason: the file &quot;defaultstripe.png&quot; does not exists in the same OpenSim folder, or is corrupted.<br /> * Solution: get the newest code from libsecondlife (&lt;tt&gt;svn co svn://opensecondlife.org/libsl/trunk&lt;/tt&gt;), '&lt;tt&gt;make&lt;/tt&gt;' manually in the subdir &lt;tt&gt;openjpeg-libsl&lt;/tt&gt;, and copy the resulting &lt;tt&gt;libopenjpeg-libsl-2.1.2.0.so&lt;/tt&gt; into your OpenSim &lt;tt&gt;bin&lt;/tt&gt; subdir, overwriting the existing one.<br /> * Recompile &amp; restart OpenSim<br /> <br /> ==Exceptions on the Console==<br /> This is a list of Exceptions that you may see on the console, what they mean, and if they are a problem.<br /> <br /> ===System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so===<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> Failed generating terrain map: System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so<br /> : at (wrapper managed-to-native) OpenJPEGNet.OpenJPEG:LibslAllocDecoded OpenJPEGNet.OpenJPEG/LibslImage&amp;)<br /> : at OpenJPEGNet.OpenJPEG.Encode (System.Byte[] decoded, Int32 width, Int32 height, Int32 components, Boolean lossless) [0x00000]<br /> :at OpenJPEGNet.OpenJPEG.EncodeFromImage (System.Drawing.Bitmap bitmap, Boolean lossless) [0x00000]<br /> :at OpenSim.Region.Terrain.TerrainEngine.ExportJpegImage (System.String gradientmap) [0x00000]<br /> |}<br /> <br /> 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:<br /> * You have an old processor (libopenjpeg has been compiled with optimizations)<br /> * You are running in 64bit mode (none of the native libs are built for 64bit)<br /> <br /> You can rebuild your own libopenjpeg from source, or run in a compatible environment.<br /> You can do this by:<br /> svn co svn://openmv.org/libsl/libopenmetaverse/trunk libsl<br /> cd libsl/openjpeg-libsl/<br /> make<br /> <br /> then copy libopenjpeg-libsl-2.1.2.0.so into OpenSim bin-folder.<br /> <br /> === System.NullReferenceException at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion ===<br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [LOGIN END]: XMLRPC Login failed, System.NullReferenceException: Object reference not set to an instance of an object<br /> :at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion (OpenSim.Framework.RegionInfo regionInfo, OpenSim.Framework.UserProfileData user, OpenSim.Framework.Communications.LoginResponse response) [0x00000] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:293<br /> :at OpenSim.Region.Communications.Local.LocalLoginService.CustomiseResponse (OpenSim.Framework.Communications.LoginResponse response, OpenSim.Framework.UserProfileData theUser, System.String startLocationRequest) [0x00520] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:253<br /> :at OpenSim.Framework.Communications.LoginService.XmlRpcLoginMethod (Nwc.XmlRpc.XmlRpcRequest request) [0x00369] in /home/sim/svn/opensim/OpenSim/Framework/Communications/LoginService.cs:252<br /> |}<br /> <br /> Your first startup of OpenSim 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.<br /> <br /> ==Grid Mode==<br /> Note: Grid Mode isn't officially supported yet. As such, you are pretty much on your own if you are trying to get OpenSim up and running in Grid Mode.<br /> <br /> === I start the sim and it doesn't connect to any grid ===<br /> <br /> When OpenSim is first started, it needs configuration.<br /> <br /> * See [[OpenSim: Configuration]].<br /> <br /> === I start the OpenSim.Grid.UserServer.exe and it gives an error===<br /> If this error is access denied for &lt;tt&gt;username@localhost&lt;/tt&gt;, the mysql database is not set up.<br /> It will print some text and wait for input - either an enter to accept a default value, or another value you can supply.<br /> * See [[OpenSim: Configuration]].<br /> <br /> === I want to run my own Local Grid but one or more servers fail to start===<br /> * Be sure that you're able to start &lt;tt&gt;OpenSim.exe&lt;/tt&gt; alone, in Standalone mode, and to be able to login.<br /> * Start the servers in the correct UGAS order and answer the questions as recommended (see [[OpenSim: Configuration]]).<br /> * Set all the external URI's to the correct IP: 127.0.0.1 if running on your local machine, or aaa.bbb.ccc.ddd if running on a remote server.<br /> * Check again all the &lt;tt&gt;*.xml&lt;/tt&gt; configuration files for any wrong settings or typing errors...!<br /> * Don't forget to connect with your SL-viewer to port 8002 (Grid User-Server) instead of 9000 (Standalone OpenSim-Server).<br /> * Delete all &lt;tt&gt;*.xml&lt;/tt&gt; and &lt;tt&gt;*.yap&lt;/tt&gt; files in the &lt;tt&gt;bin&lt;/tt&gt; directory if you want to run a full reconfiguration again.<br /> <br /> === I get a bunch of asset not found errors, while connected to a online grid, and my inventory doesn't seem to work right===<br /> *Make sure your opensim.ini has ' asset_database = &quot;grid&quot; ' otherwise it will not work correctly.<br /> <br /> === My grid works fine with one user but when two users login in the same time both get stuck ===<br /> * Make sure you have export MONO_THREADS_PER_CPU=&quot;100&quot; in your environment<br /> <br /> === After ~20 minutes my region starts to take 100% cpu and region(s) hang ===<br /> * If you have mono 1.9.1 or lower upgrade to mono 2.2.<br /> <br /> ==Hypergrid==<br /> ===After starting OpenSim with Hypergrid enabled my inventory wont load!===<br /> *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.<br /> *Check the XML config files for your UGAIM servers to make sure that everything is running off of a publicly accessible IP address.<br /> **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.<br /> <br /> 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.<br /> <br /> &lt;div align = center&gt;&lt;B&gt;!!!!WARNING!!!! - Be smart! Always make a backup of your databases before making any changes to OpenSim! - !!!!WARNING!!!!&lt;/b&gt;&lt;/div&gt;<br /> &lt;pre&gt;<br /> update users set userInventoryURI=&quot;http://new.UGAIM.address:8004&quot; where userInventoryURI = &quot;http://old.UGAIM.address:8004&quot;;<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> update users set userAssetURI=&quot;http://new.UGAIM.address:8003&quot; where userAssetURI = &quot;http://old.UGAIM.address:8003&quot;;<br /> &lt;/pre&gt;<br /> *If you're running in standalone mode... - Anyone familiar with standalone want to fill this in? -<br /> [[Category:Users]]<br /> <br /> == ScriptEngine Issues ==<br /> === Got &quot;Primitive: Error compiling script: unknown char: . error&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you could have this error :<br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> Primitive: Error compiling script:<br /> unknown char: .<br /> |}<br /> <br /> And on the console :<br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Unloading script&lt;br&gt;<br /> 11:06:37 - Exception in MaintenanceLoopThread. Thread will recover after 5 sec throttle. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.<br /> :at System.Collections.Generic.Dictionary`2[OpenSim.Region.ScriptEngine.Interfaces.IEventReceiver, OpenSim.Region.ScriptEngine.Shared.Api.Plugins.Dataserver].get_Item (IEventReceiver key) [0x00000]<br /> :at OpenSim.Region.ScriptEngine.Shared.Api.AsyncCommandManager.RemoveScript (IEventReceiver engine, UInt32 localID, UUID itemID) [0x00000]<br /> :at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager._StopScript (UInt32 localID, UUID itemID) [0x00000]<br /> :at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager.DoScriptLoadUnload () [0x00000]<br /> :at OpenSim.Region.ScriptEngine.DotNetEngine.MaintenanceThread.MaintenanceLoop () [0x00000]<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Loading script&lt;br&gt;<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: ScriptManager StartScript: localID: 720001, itemID: 88c9d28c-6004-4609-a707-717190de044a&lt;br&gt;<br /> 11:06:37 - [Compiler]: Compiled new assembly for fad15951-f9aa-493f-be68-2aaf5ff8a3c9&lt;br&gt;<br /> 11:06:37 - [SCRIPT]: Compiled assetID fad15951-f9aa-493f-be68-2aaf5ff8a3c9: ScriptEngines/a83150da-1ab1-11dd-89fb-0014853ee9da/CommonCompiler_compiled_fad15951-f9aa-493f-be68-2aaf5ff8a3c9.dll&lt;br&gt;<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: AppDomain Loading: OpenSim.Region.ScriptEngine.Shared, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null<br /> |}<br /> <br /> This happens on '''linux''' when your locales are not set to default ( &quot;C&quot; ).<br /> * You could refer to [http://opensimulator.org/mantis/view.php?id=2088 Mantis #2088] and [http://opensimulator.org/mantis/view.php?id=2015 Mantis #2015] for a workaround to run opensim.<br /> &lt;pre&gt;<br /> env LANG=C mono --debug OpenSim.exe<br /> &lt;/pre&gt;<br /> * You could also change your locale setup. Here is what I use in my '.bash_profile' :<br /> &lt;pre&gt;<br /> export LC_ALL=C<br /> export LANG=C<br /> &lt;/pre&gt;<br /> I know it's a ugly way to setup locales on a linux box, but it works fine on my '''Linux From Scratch''' box.<br /> <br /> '''Rq''': I saw Melanie has corrected some parts of the source code a few weeks ago to avoid such problems.<br /> <br /> === Get &quot;Primitive: Error compiling script: ApplicationName='gmcs', ...&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you have an error something like :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> ApplicationName='gmcs', CommandLine='/target:library /debug+ /optimize- /out:<br /> &quot;ScriptEngines/430c29d0-c5c6-11dd-ad8b-0800200c9a66/CommonCompiler_compiled_fbe5e682-afae-4f1a-805b-0125031101f7.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.Api.Runtime.dll&quot; -- <br /> &quot;/tmp/11b81aac/594d02ce.0.cs&quot; ', CurrentDirectory=''<br /> &lt;/pre&gt;<br /> <br /> Other features include &quot;Touch&quot; being disabled on the right click menu wheel.<br /> <br /> You might have a broken mono install (i.e. discovered as mono but not gmcs installed on a Ubuntu 8.10 Intrepid machine.)<br /> <br /> Check mono-gmcs (sudo apt-get install mono-gmcs) is correctly installed.<br /> <br /> == Locales Issues ==<br /> Well, some of us, OpenSim users, ran into random crash of the OpenSim Region server in grid mode ... <br /> <br /> I have made many tests to find a solution about that problem.<br /> <br /> I first ran into this problem with OpenSIM SVN.6660 ... Even if I have no users connected, my OpenSim region server randomly crash ( after 1 hour, or 5 hours, ... ).<br /> <br /> My first idea was to upgrade to the latest SVN release, no chance, same problem. So I made a test with a previous SVN release ( SVN.6575 ) which is running fine on another server ( same OS, same parameters, same mono release, ... ) : No chance, same problem.<br /> <br /> Then, I tried to play with locales, recompile the '''screen''' unix command line utility I use to run my servers, ... No chance again.<br /> <br /> So, I checked the memory usage on my Server, and I discovered that with the last SVN release, the amount of memory needed to run OpenSim server in multi-region/grid mode increased :) ... So, I have tuned my MySQL server to use less memory. Was better, but my OpenSim region server still randomly crash ( but could stay alive longer than before ).<br /> <br /> Then, trying to play with the '''screen''' command line options ... And all my tests shows that the '''--debug''' option impact the stability of the server.<br /> <br /> Initially, I used such command line to run OpenSim :<br /> &lt;pre&gt;<br /> /screen -S Region-service -d -m --debug mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> Without the '''--debug''' option, everything seems to be more stable.<br /> <br /> About locales, if you read mantis and threads in opensim-dev / opensim-users, you know that there are issues on system that are not &quot;en_US&quot; or &quot;C&quot; local compliant.<br /> <br /> I have re-setup my server to be full &quot;en_US.UTF8&quot;.<br /> <br /> On my Ubuntu 8.0.4 server :<br /> &lt;pre&gt;<br /> # cat /etc/default/locale<br /> LANG=&quot;en_US.UTF-8&quot;<br /> <br /> # cat /var/lib/locales/supported.d/local<br /> fr_FR.UTF-8 UTF-8<br /> en_US.UTF-8 UTF-8<br /> <br /> # cat /etc/environment<br /> PATH=&quot;/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games&quot;<br /> LANG=&quot;en_US&quot;<br /> LANGUAGE=&quot;en_US&quot;<br /> &lt;/pre&gt;<br /> And maybe you should need :<br /> &lt;pre&gt;<br /> # sudo dpkg-reconfigure locales<br /> &lt;/pre&gt;<br /> <br /> So, the resulting '''screen''' command line options should be :<br /> &lt;pre&gt;<br /> screen -S Region-service -d -m -U mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> This allow me to run OpenSim SVN.6575 without crash during more than 48 hours, and also SVN.6735 ... <br /> <br /> Hope those informations could help peoples.<br /> <br /> Just for your information : <br /> <br /> Here is my '''OpenSim Startup script''' :<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> echo &quot;User-Service...&quot;<br /> /usr/local/bin/screen -S User-service -d -m -U mono OpenSim.Grid.UserServer.exe<br /> sleep 5<br /> echo &quot;Grid-Service...&quot;<br /> /usr/local/bin/screen -S Grid-service -d -m -U mono OpenSim.Grid.GridServer.exe<br /> sleep 5<br /> echo &quot;Asset-Service...&quot;<br /> /usr/local/bin/screen -S Asset-service -d -m -U mono OpenSim.Grid.AssetServer.exe<br /> sleep 10<br /> echo &quot;Inventory-Service...&quot;<br /> /usr/local/bin/screen -S Inventory-service -d -m -U mono OpenSim.Grid.InventoryServer.exe<br /> sleep 5<br /> echo &quot;Region-Service...&quot;<br /> /usr/local/bin/screen -S Region-service -d -m -U mono OpenSim.exe<br /> sleep 5<br /> echo &quot; &quot;<br /> echo &quot; &quot;<br /> /usr/local/bin/screen -list<br /> &lt;/pre&gt;<br /> <br /> Here is also a small script that give you a menu to connect to the '''screen(s)''' sessions :<br /> &lt;pre&gt;<br /> #!/usr/bin/perl<br /> <br /> use strict;<br /> use Term::Menu;<br /> <br /> my $EXIT = 1;<br /> <br /> my $MainTitle = &quot;+-----------------------------------------------------+\n&quot;;<br /> $MainTitle .= &quot;| Connexion SCREEN aux Serveurs OPENSIM |\n&quot;;<br /> $MainTitle .= &quot;| |\n&quot;;<br /> $MainTitle .= &quot;| ( Type CTRL+A+D to exit the Screen Console. ) |\n&quot;;<br /> $MainTitle .= &quot;+-----------------------------------------------------+\n&quot;;<br /> <br /> while ( $EXIT == 1 )<br /> {<br /> <br /> system(&quot;screen -list | grep service &gt; /tmp/osg.services&quot;);<br /> my %LIST = ();<br /> open(IN, &quot;/tmp/osg.services&quot;);<br /> while ( my $i = &lt;IN&gt; )<br /> {<br /> chomp($i);<br /> <br /> $i =~ s/\./#/g;<br /> $i =~ s/\-service\t/#/g;<br /> $i =~ s/\t//g;<br /> $i =~ s/\(//g;<br /> $i =~ s/\)//g;<br /> <br /> my @STATUS = split(/#/, $i);<br /> $LIST{$STATUS[1]} = $STATUS[2];<br /> }<br /> close(IN);<br /> <br /> my %LIST2 = ();<br /> my @indices = ('User', 'Grid', 'Asset', 'Inventory', 'Region');<br /> <br /> foreach my $key ( @indices )<br /> {<br /> # print &quot;$key --&gt; $LIST{$key}\n&quot;;<br /> if ( $LIST{$key} =~ /Attached/ )<br /> {<br /> $LIST2{$key} = &quot;[X]&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{$key} = &quot;[ ]&quot;;<br /> }<br /> }<br /> <br /> if ( $LIST{'User'} =~ /Attached/ )<br /> {<br /> $LIST2{'USER'} = &quot;X&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{'USER'} = &quot;-&quot;;<br /> }<br /> <br /> system ('clear');<br /> my $prompt = new Term::Menu (<br /> spaces =&gt; 3,<br /> aftertext =&gt; &quot;\nChoisir une option : &quot;,<br /> beforetext =&gt; ${MainTitle},<br /> delim =&gt; &quot;. &quot;,<br /> );<br /> <br /> my $SEP = &quot; &quot;;<br /> <br /> my $answer = $prompt-&gt;menu(<br /> osg_user =&gt; [&quot;OpenSim User Server $SEP$LIST2{'User'}&quot;, '1'],<br /> osg_grid =&gt; [&quot;OpenSim Grid Server $SEP$LIST2{'Grid'}&quot;, '2'],<br /> osg_asset =&gt; [&quot;OpenSim Asset Server $SEP$LIST2{'Asset'}&quot;, '3'],<br /> osg_inventory =&gt; [&quot;OpenSim Inventory Server $SEP$LIST2{'Inventory'}&quot;, '4'],<br /> osg_region =&gt; [&quot;OpenSim Region Server $SEP$LIST2{'Region'}\n&quot;, '5'],<br /> osg_shutdown =&gt; [&quot;Shutdown Servers (Manual)&quot;,'6'],<br /> osg_shutdown2 =&gt; [&quot;Shutdown Servers (Hard)\n&quot;,'7'],<br /> quit =&gt; [&quot;Quitter&quot;, 'q'],<br /> );<br /> <br /> if ( &quot;${answer}&quot; eq &quot;quit&quot; )<br /> {<br /> $EXIT = 0;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_user&quot; )<br /> {<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_grid&quot; )<br /> {<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_asset&quot; )<br /> {<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_inventory&quot; )<br /> {<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_region&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown2&quot; )<br /> {<br /> # system(&quot;/OPENSIM/shutdownGrid.py&quot;);<br /> system(&quot;screen -S Region-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Inventory-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Asset-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Grid-service -r -m -X quit&quot;);<br /> system(&quot;screen -S User-service -r -m -X quit&quot;);<br /> $EXIT = 0;<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Regards, <br /> Ursula Matova.</div>

Dale Mahalko http://opensimulator.org/wiki/Troubleshooting 2010-04-04T05:54:55Z

<p>Dale Mahalko: /* System.NullReferenceException at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion */ ditto</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> This page gives any system-specific configuration settings that may be useful, and advice for problems that might be encountered.<br /> __TOC__<br /> {{clear}}<br /> [[Category:Users]]<br /> <br /> == System-specific configuration ==<br /> === CentOS 5 ===<br /> <br /> To install mono and nant, you can use the &quot;Linux Installer for x86&quot; found at http://www.mono-project.com/Downloads.<br /> <br /> SVN can be installed by:<br /> <br /> yum install subversion<br /> <br /> Mono defaults to installing into &lt;tt&gt;/opt&lt;/tt&gt;, so you may have to add this path to your environment variables, for example, in your &lt;tt&gt;~/.bashrc&lt;/tt&gt;:<br /> <br /> export PATH=&quot;/opt/mono-1.2.5/bin:$PATH&quot;<br /> export PKG_CONFIG_PATH=&quot;/opt/mono-1.2.5/lib/pkgconfig:$PKG_CONFIG_PATH&quot;<br /> export MANPATH=&quot;/opt/mono-1.2.5/share/man:$MANPATH&quot;<br /> export LD_LIBRARY_PATH=&quot;/opt/mono-1.2.5/lib:$LD_LIBRARY_PATH&quot;<br /> <br /> After changing &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt;, you should update the dynamic linker cache:<br /> <br /> ldconfig<br /> <br /> You may still encounter the &quot;The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file.&quot; error listed below. In that case, this may fix this:<br /> <br /> yum install glib<br /> <br /> If you are running a firewall as well (i.e., if &lt;tt&gt;iptables -L&lt;/tt&gt; shows a list of ACCEPT and REJECT rules), you'll have to open the necessary ports if you want to access the sim from other machines. For standalone mode:<br /> <br /> iptables -I RH-Firewall-1-INPUT -p tcp --dport 9000 -j ACCEPT<br /> iptables -I RH-Firewall-1-INPUT -p udp --dport 9000 -j ACCEPT<br /> <br /> 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:<br /> sudo yum install libgdiplus<br /> sudo yum install libexif<br /> sudo ln -s /usr/lib64/libgdiplus.so.0 /usr/lib64/libgdiplus.so<br /> ldconfig<br /> <br /> That finally enabled me to run OpenSim without errors, and even connect to other grids.<br /> <br /> === Debian 4.0r0 ===<br /> <br /> If you set your system to use unstable sources, and then install some packages listed below, everything should just work. To use unstable sources, modify your &lt;tt&gt;/etc/apt/sources.list&lt;/tt&gt; file, replacing 'etch' or 'stable' with 'unstable':<br /> <br /> deb ftp://ftp.debian.org/debian/ unstable main<br /> deb-src ftp://ftp.debian.org/debian/ unstable main<br /> <br /> Then update your packages to the new versions:<br /> <br /> apt-get update<br /> apt-get dist-upgrade<br /> <br /> This will probably change a large number of packages, and may break things.<br /> In my experience, however, if you do not use unstable sources then the packages are not up to date enough, and you run into version issues, which lead to two DllNotFoundException errors below appearing in the console output: gdiplus.dll and libopenjpeg-libsl-2.1.2.0.so.<br /> <br /> Once the sources are updated, we need to install the necessary packages to be able to build OpenSim:<br /> <br /> apt-get install subversion mono nant mono-gmcs mono-mjs libmono-microsoft8.0-cil libmono-system-runtime2.0-cil<br /> <br /> If any of these packages are missing, you'll probably encounter one of the errors listed below. However, with these packages, OpenSim should build cleanly.<br /> <br /> Please note: If you are using mysql as storage on unstable you may get the following error:-<br /> <br /> Exception: System.NotSupportedException: CodePage 1252 not supported<br /> at System.Text.Encoding.GetEncoding (Int32 codePage) [0x00000] <br /> <br /> To get it to work, try installing the libmono-i18n2.0-cil package<br /> <br /> apt-get install libmono-i18n2.0-cil<br /> <br /> === Gentoo ===<br /> some Mono dependency &amp; latest Mono itself may use &quot;~x86&quot; masked packages (assuming x86 is your platform, change may be made to reflect your ex:&quot;~amd64&quot; for 64bits). You could check for USE parameter with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge -vp subversion nant mono libgdiplus<br /> <br /> Then install with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge subversion nant mono libgdiplus<br /> <br /> N.B: The ACCEPT_KEYWORDS=&quot;~x86&quot; 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<br /> <br /> === Mac OS X ===<br /> This assumes you're using the universal binary for mono from the [http://www.mono-project.com/ Mono Project] site.<br /> <br /> If you are using OS X 10.4, you should also install X11 from the OS X install CDs.<br /> In OS X 10.5, this is not required.<br /> <br /> If you get errors about the 2.0 framework not being supported, you may need to update your &lt;tt&gt;pkg-config&lt;/tt&gt; path.<br /> I set this in &lt;tt&gt;~/.bash_profile&lt;/tt&gt;:<br /> export PKG_CONFIG_PATH=&quot;/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}&quot;<br /> <br /> == Errors and fixes ==<br /> <br /> === Build workarounds due to non-functionality or bugs: ===<br /> <br /> ==== Disappearing prims due to duplicate UID's ====<br /> 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. This switch is documented in the [[Running#General OpenSim server commands|general server commands]] section. (&lt;nowiki&gt;load-xml &lt;filename&gt; -newUID&lt;/nowiki&gt;). 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.<br /> <br /> ==== Linked objects not scaling/editing properly ====<br /> From Mantis [[http://opensimulator.org/mantis/view.php?id=135 # 135]] and [[http://opensimulator.org/mantis/view.php?id=223 # 223]]: &lt;br /&gt;<br /> Linked objects: while linking/unlinking objects seems to work fine, the editing of single prims inside a linked object doesn't work correctly. You have to check the box &quot;Edit linked parts&quot;, then you can select a single prim and edit it, but in most cases the changes in size- and/or postion-parameters are not accepted and revert immediately to the original ones. It is not completely reproducible, as it may work in some single case though.&lt;br /&gt;<br /> '''Workaround:''' unlink the whole object, make the changes, and relink the whole thing again. &lt;br /&gt; ''note:'' re-scaling unlinked objects in grid mode seems to work better than in standalone. <br /> <br /> &lt;hr&gt;<br /> <br /> === Exception and loss of ode physics (System.EntryPointNotFoundException: dSpaceLockQuery) ===<br /> <br /> The following error is usually caused by using the wrong version of ''libode'':<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [SCENE] [02-01 22:20:40] System.EntryPointNotFoundException: dSpaceLockQuery<br /> :at (wrapper managed-to-native) Ode.NET.d:SpaceLockQuery (intptr)<br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.waitForSpaceUnlock (IntPtr space) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter.AvatarGeomAndBodyCreation (Single npositionX, Single npositionY, Single npositionZ, Single tensor) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter..ctor (System.String avName, OpenSim.Region.Physics.OdePlugin.OdeScene parent_scene, OpenSim.Region.Physics.Manager.PhysicsVector pos) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.AddAvatar (System.String avName, OpenSim.Region.Physics.Manager.PhysicsVector position) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.AddToPhysicalScene () [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.MakeRootAgent (LLVector3 pos, Boolean isFlying) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.Scene.AgentCrossing (UInt64 regionHandle, LLUUID agentID, LLVector3 position, Boolean isFlying) [0x00000]<br /> |}<br /> <br /> First try searching your filesystem to see if you have other copies of the ode physics engine:<br /> find / -name &quot;libode.so&quot;<br /> Then make sure you have the latest version.<br /> <br /> === MySQL connection errors after about 6-8 hours ===<br /> <br /> 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:<br /> <br /> set global wait_timeout=604800;<br /> <br /> === System.DllNotFoundException: gdiplus.dll ===<br /> <br /> First, check to make sure that &lt;tt&gt;libgdiplus.so&lt;/tt&gt; is known to the dynamic linker:<br /> <br /> /sbin/ldconfig -p | grep libgdiplus<br /> <br /> If nothing is found, make sure that the directory libgdiplus.so exists in is either in your &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt; environment variable or listed in a *.conf file (e.g., gdiplus.conf) in /etc/ld.so.conf.d/. Then run &lt;tt&gt;ldconfig&lt;/tt&gt; to update the cache. Then it should be able to find the library.<br /> <br /> 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 OpenSim with debugging information turned on:<br /> <br /> MONO_LOG_LEVEL=debug mono OpenSim.exe<br /> <br /> {It may show errors loading other libraries, like &lt;tt&gt;libexif.so.9&lt;/tt&gt;. In that case, linking to an existing version of the offending library may work:<br /> <br /> ln -s libexif.so.12 libexif.so.9<br /> <br /> 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 <br /> and add the line <br /> &lt;dllmap dll=&quot;gdiplus.dll&quot; target=&quot;/opt/local/lib/libgdiplus.dylib&quot; os=&quot;!windows&quot;/&gt;<br /> <br /> ''(Is there a cleaner solution than this?)''} **see below for alternative/cleaner fix**<br /> <br /> == When installing mono or libgdiplus0 you may get dependency missing libexif.so.9 == <br /> <br /> 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 )<br /> <br /> === The assembly mscorlib.dll was not found or could not be loaded ===<br /> <br /> 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.<br /> <br /> apt-get install nant<br /> <br /> === External Program Failed: /usr/lib/pkgconfig/../../lib/mono/2.0/gmcs.exe === <br /> <br /> This is quickly fixed by retrieving mono-gmcs.<br /> <br /> apt-get install mono-gmcs<br /> <br /> === The type or namespace name JScript does not exist in the namespace Microsoft ===<br /> <br /> Note that it says JScript over and over again. Hint perhaps?<br /> <br /> apt-get install mono-mjs libmono-microsoft8.0-cil<br /> <br /> On Fedora and OpenSUSE, the needed package is &quot;mono-jscript&quot;.<br /> <br /> === The type or namespace name Tcp does not exist in the namespace System.Runtime.Remoting.Channels ===<br /> <br /> This one is taken care of with a quick install:<br /> <br /> apt-get install libmono-system-runtime2.0-cil<br /> <br /> === Missing: libopenjpeg-libsl-2.1.2.0-x86_64.so ===<br /> <br /> You are probably on a 64-bit linux machine and may need to follow these instructions:<br /> <br /> * [[Installing_and_running_on_x86-64 |Installing and running on x86-64 ]]<br /> <br /> === error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file ===<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> apt-get install libglib2.0-0<br /> <br /> === The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file. ===<br /> <br /> This one seems to be fixed by retrieving the apt version of nant.<br /> <br /> apt-get install nant<br /> <br /> This can also be due to &lt;tt&gt;pkg-config&lt;/tt&gt; not being able to locate the &lt;tt&gt;mono.pc&lt;/tt&gt; file. Adding the directory containing this file to the environment variable &lt;tt&gt;PKG_CONFIG_PATH&lt;/tt&gt; may solve this.<br /> <br /> == Networking and config issues ==<br /> <br /> See also the wiki page:<br /> * [[Running]]<br /> <br /> === You are able to log in, but not connect to a Region from a remote client ===<br /> <br /> Look in your OpenSimulator/bin/Regions folder <br /> # Try '''0.0.0.0''' for the internal_ip_address in your region.xml(default.xml) file.&lt;br&gt;(you'll have one of these files for each region you have created)<br /> # '''external_host_name=&quot;127.0.0.1&quot;''' will need to be changed to the accessable DNS name such as &quot;opensim.example-host.com&quot; or &quot;71.6.131.152&quot; (your public accessable ip)<br /> <br /> ==Building OpenSim==<br /> ===I can't find any build files or solution files===<br /> * If you're on Windows, run<br /> runprebuild.bat<br /> * on Linux/Mac/FreeBSD, run <br /> runprebuild.sh<br /> <br /> === VS2005 won't open the .sln file ===<br /> * Try running VS2005 C#. You are probably running VS2005 C++. This is a C# project.<br /> <br /> ==Running OpenSim==<br /> === Running OpenSim.exe from a Cygwin shell has access denied for some dll's ===<br /> * Do a '&lt;tt&gt;cd bin&lt;/tt&gt;' followed by '&lt;tt&gt;chmod a+x *&lt;/tt&gt;' to make all dll files executable.<br /> ===I cannot start my sim===<br /> * See [[Configuration]]<br /> <br /> ==Something Has Gone Wrong!==<br /> === I get errors concerning 'owner_uuid' when starting up my grid after updating from svn beyond r3254 ===<br /> When updating to recent revisions after r3254, we are now using the unused owner_uuid. There are some grids whose mysql tables were created during a time when this field was inadvertently removed from the .sql script that initializes the regions table. Logging in to your mysql instance and executing this SQL query to add the missing owner_uuid should solve this issue:<br /> alter table `regions` add column `owner_uuid` varchar(36) default '00000000-0000-0000-0000-000000000000' not null, comment 'Rev.2';<br /> The punctuation around regions and owner_uuid is &quot;grave accent&quot;. The punctuation around the default value and the comment is the single quote. The &quot;grave accent&quot; is the one generally to the left of the One button, under the tilde and the single-quote, is, well, underneath the double quote. I think this matters to mysql.<br /> <br /> === I get errors concerning 'State' when starting up my grid after updating from svn beyond r3786 ===<br /> After r3786, a new 'State' field has been added to the 'primshapes' table on SQLite. This field is used to persist trees and grass.<br /> You may have an empty region at startup, because OpenSim does not find this 'State' field and does not know what to do.<br /> The best is to use SQLiteBrowser or another SQLite table editor (download it at [http://sqlitebrowser.sourceforge.net/ http://sqlitebrowser.sourceforge.net/]) to create the missing field:<br /> alter table primshapes add column State integer default 0<br /> Just launch SQLiteBrowser, use File/Open database, then browse to OpenSim.db file and open it. Then, go to the &quot;Execute SQL&quot; tab, copy/paste the command above in the &quot;SQL string&quot; textbox, then hit the &quot;Execute query&quot; button.<br /> <br /> === I get a timeout during region handshake ===<br /> * Do you have the correct IP in your Regions\* config files?<br /> * Do you have multiple interfaces on the server running OpenSim? OpenSim 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.<br /> <br /> === I cannot connect to my OpenSim ===<br /> * See [[OpenSim: Connecting]]<br /> <br /> ===I can connect but cannot move===<br /> If the client connects but the avatar can only spin in place and not move, then the sim is not correctly configured. It completed the initial login function, but packets are not being exchanged between the client and the sim, probably due to a network configuration error on the sim.<br /> * See [[OpenSim: Configuration]]<br /> <br /> === From time to time my Avatar seems to get stuck ===<br /> Right now there is a bottle neck when syncing prims off to the database. This will cause small (5 - 10 second) apparent hangs of the Avatar, but it will recover fine once the data is synced. It is a known issue based on legacy architecture of some of the data storage code. We hope this will be removed soon.<br /> <br /> === I have problems with viewing the worldmap ===<br /> * This may happen when running OpenSim on a Linux server, both in grid or standalone mode.<br /> * 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...<br /> * Reason: your svn source trunk does not have the correct (or whatever...) &lt;tt&gt;libopenjpeg-libsl&lt;/tt&gt; library.<br /> * Other reason: the file &quot;defaultstripe.png&quot; does not exists in the same OpenSim folder, or is corrupted.<br /> * Solution: get the newest code from libsecondlife (&lt;tt&gt;svn co svn://opensecondlife.org/libsl/trunk&lt;/tt&gt;), '&lt;tt&gt;make&lt;/tt&gt;' manually in the subdir &lt;tt&gt;openjpeg-libsl&lt;/tt&gt;, and copy the resulting &lt;tt&gt;libopenjpeg-libsl-2.1.2.0.so&lt;/tt&gt; into your OpenSim &lt;tt&gt;bin&lt;/tt&gt; subdir, overwriting the existing one.<br /> * Recompile &amp; restart OpenSim<br /> <br /> ==Exceptions on the Console==<br /> This is a list of Exceptions that you may see on the console, what they mean, and if they are a problem.<br /> <br /> ===System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so===<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> Failed generating terrain map: System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so<br /> : at (wrapper managed-to-native) OpenJPEGNet.OpenJPEG:LibslAllocDecoded OpenJPEGNet.OpenJPEG/LibslImage&amp;)<br /> : at OpenJPEGNet.OpenJPEG.Encode (System.Byte[] decoded, Int32 width, Int32 height, Int32 components, Boolean lossless) [0x00000]<br /> :at OpenJPEGNet.OpenJPEG.EncodeFromImage (System.Drawing.Bitmap bitmap, Boolean lossless) [0x00000]<br /> :at OpenSim.Region.Terrain.TerrainEngine.ExportJpegImage (System.String gradientmap) [0x00000]<br /> |}<br /> <br /> 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:<br /> * You have an old processor (libopenjpeg has been compiled with optimizations)<br /> * You are running in 64bit mode (none of the native libs are built for 64bit)<br /> <br /> You can rebuild your own libopenjpeg from source, or run in a compatible environment.<br /> You can do this by:<br /> svn co svn://openmv.org/libsl/libopenmetaverse/trunk libsl<br /> cd libsl/openjpeg-libsl/<br /> make<br /> <br /> then copy libopenjpeg-libsl-2.1.2.0.so into OpenSim bin-folder.<br /> <br /> === System.NullReferenceException at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion ===<br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [LOGIN END]: XMLRPC Login failed, System.NullReferenceException: Object reference not set to an instance of an object<br /> :at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion (OpenSim.Framework.RegionInfo regionInfo, OpenSim.Framework.UserProfileData user, OpenSim.Framework.Communications.LoginResponse response) [0x00000] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:293<br /> :at OpenSim.Region.Communications.Local.LocalLoginService.CustomiseResponse (OpenSim.Framework.Communications.LoginResponse response, OpenSim.Framework.UserProfileData theUser, System.String startLocationRequest) [0x00520] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:253<br /> :at OpenSim.Framework.Communications.LoginService.XmlRpcLoginMethod (Nwc.XmlRpc.XmlRpcRequest request) [0x00369] in /home/sim/svn/opensim/OpenSim/Framework/Communications/LoginService.cs:252<br /> |}<br /> <br /> Your first startup of OpenSim 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.<br /> <br /> ==Grid Mode==<br /> Note: Grid Mode isn't officially supported yet. As such, you are pretty much on your own if you are trying to get OpenSim up and running in Grid Mode.<br /> <br /> === I start the sim and it doesn't connect to any grid ===<br /> <br /> When OpenSim is first started, it needs configuration.<br /> <br /> * See [[OpenSim: Configuration]].<br /> <br /> === I start the OpenSim.Grid.UserServer.exe and it gives an error===<br /> If this error is access denied for &lt;tt&gt;username@localhost&lt;/tt&gt;, the mysql database is not set up.<br /> It will print some text and wait for input - either an enter to accept a default value, or another value you can supply.<br /> * See [[OpenSim: Configuration]].<br /> <br /> === I want to run my own Local Grid but one or more servers fail to start===<br /> * Be sure that you're able to start &lt;tt&gt;OpenSim.exe&lt;/tt&gt; alone, in Standalone mode, and to be able to login.<br /> * Start the servers in the correct UGAS order and answer the questions as recommended (see [[OpenSim: Configuration]]).<br /> * Set all the external URI's to the correct IP: 127.0.0.1 if running on your local machine, or aaa.bbb.ccc.ddd if running on a remote server.<br /> * Check again all the &lt;tt&gt;*.xml&lt;/tt&gt; configuration files for any wrong settings or typing errors...!<br /> * Don't forget to connect with your SL-viewer to port 8002 (Grid User-Server) instead of 9000 (Standalone OpenSim-Server).<br /> * Delete all &lt;tt&gt;*.xml&lt;/tt&gt; and &lt;tt&gt;*.yap&lt;/tt&gt; files in the &lt;tt&gt;bin&lt;/tt&gt; directory if you want to run a full reconfiguration again.<br /> <br /> === I get a bunch of asset not found errors, while connected to a online grid, and my inventory doesn't seem to work right===<br /> *Make sure your opensim.ini has ' asset_database = &quot;grid&quot; ' otherwise it will not work correctly.<br /> <br /> === My grid works fine with one user but when two users login in the same time both get stuck ===<br /> * Make sure you have export MONO_THREADS_PER_CPU=&quot;100&quot; in your environment<br /> <br /> === After ~20 minutes my region starts to take 100% cpu and region(s) hang ===<br /> * If you have mono 1.9.1 or lower upgrade to mono 2.2.<br /> <br /> ==Hypergrid==<br /> ===After starting OpenSim with Hypergrid enabled my inventory wont load!===<br /> *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.<br /> *Check the XML config files for your UGAIM servers to make sure that everything is running off of a publicly accessible IP address.<br /> **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.<br /> <br /> 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.<br /> <br /> &lt;div align = center&gt;&lt;B&gt;!!!!WARNING!!!! - Be smart! Always make a backup of your databases before making any changes to OpenSim! - !!!!WARNING!!!!&lt;/b&gt;&lt;/div&gt;<br /> &lt;pre&gt;<br /> update users set userInventoryURI=&quot;http://new.UGAIM.address:8004&quot; where userInventoryURI = &quot;http://old.UGAIM.address:8004&quot;;<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> update users set userAssetURI=&quot;http://new.UGAIM.address:8003&quot; where userAssetURI = &quot;http://old.UGAIM.address:8003&quot;;<br /> &lt;/pre&gt;<br /> *If you're running in standalone mode... - Anyone familiar with standalone want to fill this in? -<br /> [[Category:Users]]<br /> <br /> == ScriptEngine Issues ==<br /> === Got &quot;Primitive: Error compiling script: unknown char: . error&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you could have this error :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> unknown char: .<br /> &lt;/pre&gt;<br /> And on the console :<br /> &lt;pre&gt;<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Unloading script<br /> 11:06:37 - Exception in MaintenanceLoopThread. Thread will recover after 5 sec throttle. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.<br /> at System.Collections.Generic.Dictionary`2[OpenSim.Region.ScriptEngine.Interfaces.IEventReceiver,OpenSim.Region.ScriptEngine.Shared.Api.Plugins.Dataserver].get_Item (IEventReceiver key) [0x00000]<br /> at OpenSim.Region.ScriptEngine.Shared.Api.AsyncCommandManager.RemoveScript (IEventReceiver engine, UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager._StopScript (UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager.DoScriptLoadUnload () [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.MaintenanceThread.MaintenanceLoop () [0x00000]<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Loading script<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: ScriptManager StartScript: localID: 720001, itemID: 88c9d28c-6004-4609-a707-717190de044a<br /> 11:06:37 - [Compiler]: Compiled new assembly for fad15951-f9aa-493f-be68-2aaf5ff8a3c9<br /> 11:06:37 - [SCRIPT]: Compiled assetID fad15951-f9aa-493f-be68-2aaf5ff8a3c9: ScriptEngines/a83150da-1ab1-11dd-89fb-0014853ee9da/CommonCompiler_compiled_fad15951-f9aa-493f-be68-2aaf5ff8a3c9.dll<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: AppDomain Loading: OpenSim.Region.ScriptEngine.Shared, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null<br /> &lt;/pre&gt;<br /> This happens on '''linux''' when your locales are not set to default ( &quot;C&quot; ).<br /> * You could refer to [http://opensimulator.org/mantis/view.php?id=2088 Mantis #2088] and [http://opensimulator.org/mantis/view.php?id=2015 Mantis #2015] for a workaround to run opensim.<br /> &lt;pre&gt;<br /> env LANG=C mono --debug OpenSim.exe<br /> &lt;/pre&gt;<br /> * You could also change your locale setup. Here is what I use in my '.bash_profile' :<br /> &lt;pre&gt;<br /> export LC_ALL=C<br /> export LANG=C<br /> &lt;/pre&gt;<br /> I know it's a ugly way to setup locales on a linux box, but it works fine on my '''Linux From Scratch''' box.<br /> <br /> '''Rq''': I saw Melanie has corrected some parts of the source code a few weeks ago to avoid such problems.<br /> <br /> === Get &quot;Primitive: Error compiling script: ApplicationName='gmcs', ...&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you have an error something like :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> ApplicationName='gmcs', CommandLine='/target:library /debug+ /optimize- /out:<br /> &quot;ScriptEngines/430c29d0-c5c6-11dd-ad8b-0800200c9a66/CommonCompiler_compiled_fbe5e682-afae-4f1a-805b-0125031101f7.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.Api.Runtime.dll&quot; -- <br /> &quot;/tmp/11b81aac/594d02ce.0.cs&quot; ', CurrentDirectory=''<br /> &lt;/pre&gt;<br /> <br /> Other features include &quot;Touch&quot; being disabled on the right click menu wheel.<br /> <br /> You might have a broken mono install (i.e. discovered as mono but not gmcs installed on a Ubuntu 8.10 Intrepid machine.)<br /> <br /> Check mono-gmcs (sudo apt-get install mono-gmcs) is correctly installed.<br /> <br /> == Locales Issues ==<br /> Well, some of us, OpenSim users, ran into random crash of the OpenSim Region server in grid mode ... <br /> <br /> I have made many tests to find a solution about that problem.<br /> <br /> I first ran into this problem with OpenSIM SVN.6660 ... Even if I have no users connected, my OpenSim region server randomly crash ( after 1 hour, or 5 hours, ... ).<br /> <br /> My first idea was to upgrade to the latest SVN release, no chance, same problem. So I made a test with a previous SVN release ( SVN.6575 ) which is running fine on another server ( same OS, same parameters, same mono release, ... ) : No chance, same problem.<br /> <br /> Then, I tried to play with locales, recompile the '''screen''' unix command line utility I use to run my servers, ... No chance again.<br /> <br /> So, I checked the memory usage on my Server, and I discovered that with the last SVN release, the amount of memory needed to run OpenSim server in multi-region/grid mode increased :) ... So, I have tuned my MySQL server to use less memory. Was better, but my OpenSim region server still randomly crash ( but could stay alive longer than before ).<br /> <br /> Then, trying to play with the '''screen''' command line options ... And all my tests shows that the '''--debug''' option impact the stability of the server.<br /> <br /> Initially, I used such command line to run OpenSim :<br /> &lt;pre&gt;<br /> /screen -S Region-service -d -m --debug mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> Without the '''--debug''' option, everything seems to be more stable.<br /> <br /> About locales, if you read mantis and threads in opensim-dev / opensim-users, you know that there are issues on system that are not &quot;en_US&quot; or &quot;C&quot; local compliant.<br /> <br /> I have re-setup my server to be full &quot;en_US.UTF8&quot;.<br /> <br /> On my Ubuntu 8.0.4 server :<br /> &lt;pre&gt;<br /> # cat /etc/default/locale<br /> LANG=&quot;en_US.UTF-8&quot;<br /> <br /> # cat /var/lib/locales/supported.d/local<br /> fr_FR.UTF-8 UTF-8<br /> en_US.UTF-8 UTF-8<br /> <br /> # cat /etc/environment<br /> PATH=&quot;/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games&quot;<br /> LANG=&quot;en_US&quot;<br /> LANGUAGE=&quot;en_US&quot;<br /> &lt;/pre&gt;<br /> And maybe you should need :<br /> &lt;pre&gt;<br /> # sudo dpkg-reconfigure locales<br /> &lt;/pre&gt;<br /> <br /> So, the resulting '''screen''' command line options should be :<br /> &lt;pre&gt;<br /> screen -S Region-service -d -m -U mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> This allow me to run OpenSim SVN.6575 without crash during more than 48 hours, and also SVN.6735 ... <br /> <br /> Hope those informations could help peoples.<br /> <br /> Just for your information : <br /> <br /> Here is my '''OpenSim Startup script''' :<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> echo &quot;User-Service...&quot;<br /> /usr/local/bin/screen -S User-service -d -m -U mono OpenSim.Grid.UserServer.exe<br /> sleep 5<br /> echo &quot;Grid-Service...&quot;<br /> /usr/local/bin/screen -S Grid-service -d -m -U mono OpenSim.Grid.GridServer.exe<br /> sleep 5<br /> echo &quot;Asset-Service...&quot;<br /> /usr/local/bin/screen -S Asset-service -d -m -U mono OpenSim.Grid.AssetServer.exe<br /> sleep 10<br /> echo &quot;Inventory-Service...&quot;<br /> /usr/local/bin/screen -S Inventory-service -d -m -U mono OpenSim.Grid.InventoryServer.exe<br /> sleep 5<br /> echo &quot;Region-Service...&quot;<br /> /usr/local/bin/screen -S Region-service -d -m -U mono OpenSim.exe<br /> sleep 5<br /> echo &quot; &quot;<br /> echo &quot; &quot;<br /> /usr/local/bin/screen -list<br /> &lt;/pre&gt;<br /> <br /> Here is also a small script that give you a menu to connect to the '''screen(s)''' sessions :<br /> &lt;pre&gt;<br /> #!/usr/bin/perl<br /> <br /> use strict;<br /> use Term::Menu;<br /> <br /> my $EXIT = 1;<br /> <br /> my $MainTitle = &quot;+-----------------------------------------------------+\n&quot;;<br /> $MainTitle .= &quot;| Connexion SCREEN aux Serveurs OPENSIM |\n&quot;;<br /> $MainTitle .= &quot;| |\n&quot;;<br /> $MainTitle .= &quot;| ( Type CTRL+A+D to exit the Screen Console. ) |\n&quot;;<br /> $MainTitle .= &quot;+-----------------------------------------------------+\n&quot;;<br /> <br /> while ( $EXIT == 1 )<br /> {<br /> <br /> system(&quot;screen -list | grep service &gt; /tmp/osg.services&quot;);<br /> my %LIST = ();<br /> open(IN, &quot;/tmp/osg.services&quot;);<br /> while ( my $i = &lt;IN&gt; )<br /> {<br /> chomp($i);<br /> <br /> $i =~ s/\./#/g;<br /> $i =~ s/\-service\t/#/g;<br /> $i =~ s/\t//g;<br /> $i =~ s/\(//g;<br /> $i =~ s/\)//g;<br /> <br /> my @STATUS = split(/#/, $i);<br /> $LIST{$STATUS[1]} = $STATUS[2];<br /> }<br /> close(IN);<br /> <br /> my %LIST2 = ();<br /> my @indices = ('User', 'Grid', 'Asset', 'Inventory', 'Region');<br /> <br /> foreach my $key ( @indices )<br /> {<br /> # print &quot;$key --&gt; $LIST{$key}\n&quot;;<br /> if ( $LIST{$key} =~ /Attached/ )<br /> {<br /> $LIST2{$key} = &quot;[X]&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{$key} = &quot;[ ]&quot;;<br /> }<br /> }<br /> <br /> if ( $LIST{'User'} =~ /Attached/ )<br /> {<br /> $LIST2{'USER'} = &quot;X&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{'USER'} = &quot;-&quot;;<br /> }<br /> <br /> system ('clear');<br /> my $prompt = new Term::Menu (<br /> spaces =&gt; 3,<br /> aftertext =&gt; &quot;\nChoisir une option : &quot;,<br /> beforetext =&gt; ${MainTitle},<br /> delim =&gt; &quot;. &quot;,<br /> );<br /> <br /> my $SEP = &quot; &quot;;<br /> <br /> my $answer = $prompt-&gt;menu(<br /> osg_user =&gt; [&quot;OpenSim User Server $SEP$LIST2{'User'}&quot;, '1'],<br /> osg_grid =&gt; [&quot;OpenSim Grid Server $SEP$LIST2{'Grid'}&quot;, '2'],<br /> osg_asset =&gt; [&quot;OpenSim Asset Server $SEP$LIST2{'Asset'}&quot;, '3'],<br /> osg_inventory =&gt; [&quot;OpenSim Inventory Server $SEP$LIST2{'Inventory'}&quot;, '4'],<br /> osg_region =&gt; [&quot;OpenSim Region Server $SEP$LIST2{'Region'}\n&quot;, '5'],<br /> osg_shutdown =&gt; [&quot;Shutdown Servers (Manual)&quot;,'6'],<br /> osg_shutdown2 =&gt; [&quot;Shutdown Servers (Hard)\n&quot;,'7'],<br /> quit =&gt; [&quot;Quitter&quot;, 'q'],<br /> );<br /> <br /> if ( &quot;${answer}&quot; eq &quot;quit&quot; )<br /> {<br /> $EXIT = 0;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_user&quot; )<br /> {<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_grid&quot; )<br /> {<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_asset&quot; )<br /> {<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_inventory&quot; )<br /> {<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_region&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown2&quot; )<br /> {<br /> # system(&quot;/OPENSIM/shutdownGrid.py&quot;);<br /> system(&quot;screen -S Region-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Inventory-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Asset-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Grid-service -r -m -X quit&quot;);<br /> system(&quot;screen -S User-service -r -m -X quit&quot;);<br /> $EXIT = 0;<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Regards, <br /> Ursula Matova.</div>

Dale Mahalko http://opensimulator.org/wiki/Troubleshooting 2010-04-04T05:52:56Z

<p>Dale Mahalko: /* System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so */ reformat error message so it doesn't run off right side of page</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> This page gives any system-specific configuration settings that may be useful, and advice for problems that might be encountered.<br /> __TOC__<br /> {{clear}}<br /> [[Category:Users]]<br /> <br /> == System-specific configuration ==<br /> === CentOS 5 ===<br /> <br /> To install mono and nant, you can use the &quot;Linux Installer for x86&quot; found at http://www.mono-project.com/Downloads.<br /> <br /> SVN can be installed by:<br /> <br /> yum install subversion<br /> <br /> Mono defaults to installing into &lt;tt&gt;/opt&lt;/tt&gt;, so you may have to add this path to your environment variables, for example, in your &lt;tt&gt;~/.bashrc&lt;/tt&gt;:<br /> <br /> export PATH=&quot;/opt/mono-1.2.5/bin:$PATH&quot;<br /> export PKG_CONFIG_PATH=&quot;/opt/mono-1.2.5/lib/pkgconfig:$PKG_CONFIG_PATH&quot;<br /> export MANPATH=&quot;/opt/mono-1.2.5/share/man:$MANPATH&quot;<br /> export LD_LIBRARY_PATH=&quot;/opt/mono-1.2.5/lib:$LD_LIBRARY_PATH&quot;<br /> <br /> After changing &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt;, you should update the dynamic linker cache:<br /> <br /> ldconfig<br /> <br /> You may still encounter the &quot;The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file.&quot; error listed below. In that case, this may fix this:<br /> <br /> yum install glib<br /> <br /> If you are running a firewall as well (i.e., if &lt;tt&gt;iptables -L&lt;/tt&gt; shows a list of ACCEPT and REJECT rules), you'll have to open the necessary ports if you want to access the sim from other machines. For standalone mode:<br /> <br /> iptables -I RH-Firewall-1-INPUT -p tcp --dport 9000 -j ACCEPT<br /> iptables -I RH-Firewall-1-INPUT -p udp --dport 9000 -j ACCEPT<br /> <br /> 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:<br /> sudo yum install libgdiplus<br /> sudo yum install libexif<br /> sudo ln -s /usr/lib64/libgdiplus.so.0 /usr/lib64/libgdiplus.so<br /> ldconfig<br /> <br /> That finally enabled me to run OpenSim without errors, and even connect to other grids.<br /> <br /> === Debian 4.0r0 ===<br /> <br /> If you set your system to use unstable sources, and then install some packages listed below, everything should just work. To use unstable sources, modify your &lt;tt&gt;/etc/apt/sources.list&lt;/tt&gt; file, replacing 'etch' or 'stable' with 'unstable':<br /> <br /> deb ftp://ftp.debian.org/debian/ unstable main<br /> deb-src ftp://ftp.debian.org/debian/ unstable main<br /> <br /> Then update your packages to the new versions:<br /> <br /> apt-get update<br /> apt-get dist-upgrade<br /> <br /> This will probably change a large number of packages, and may break things.<br /> In my experience, however, if you do not use unstable sources then the packages are not up to date enough, and you run into version issues, which lead to two DllNotFoundException errors below appearing in the console output: gdiplus.dll and libopenjpeg-libsl-2.1.2.0.so.<br /> <br /> Once the sources are updated, we need to install the necessary packages to be able to build OpenSim:<br /> <br /> apt-get install subversion mono nant mono-gmcs mono-mjs libmono-microsoft8.0-cil libmono-system-runtime2.0-cil<br /> <br /> If any of these packages are missing, you'll probably encounter one of the errors listed below. However, with these packages, OpenSim should build cleanly.<br /> <br /> Please note: If you are using mysql as storage on unstable you may get the following error:-<br /> <br /> Exception: System.NotSupportedException: CodePage 1252 not supported<br /> at System.Text.Encoding.GetEncoding (Int32 codePage) [0x00000] <br /> <br /> To get it to work, try installing the libmono-i18n2.0-cil package<br /> <br /> apt-get install libmono-i18n2.0-cil<br /> <br /> === Gentoo ===<br /> some Mono dependency &amp; latest Mono itself may use &quot;~x86&quot; masked packages (assuming x86 is your platform, change may be made to reflect your ex:&quot;~amd64&quot; for 64bits). You could check for USE parameter with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge -vp subversion nant mono libgdiplus<br /> <br /> Then install with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge subversion nant mono libgdiplus<br /> <br /> N.B: The ACCEPT_KEYWORDS=&quot;~x86&quot; 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<br /> <br /> === Mac OS X ===<br /> This assumes you're using the universal binary for mono from the [http://www.mono-project.com/ Mono Project] site.<br /> <br /> If you are using OS X 10.4, you should also install X11 from the OS X install CDs.<br /> In OS X 10.5, this is not required.<br /> <br /> If you get errors about the 2.0 framework not being supported, you may need to update your &lt;tt&gt;pkg-config&lt;/tt&gt; path.<br /> I set this in &lt;tt&gt;~/.bash_profile&lt;/tt&gt;:<br /> export PKG_CONFIG_PATH=&quot;/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}&quot;<br /> <br /> == Errors and fixes ==<br /> <br /> === Build workarounds due to non-functionality or bugs: ===<br /> <br /> ==== Disappearing prims due to duplicate UID's ====<br /> 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. This switch is documented in the [[Running#General OpenSim server commands|general server commands]] section. (&lt;nowiki&gt;load-xml &lt;filename&gt; -newUID&lt;/nowiki&gt;). 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.<br /> <br /> ==== Linked objects not scaling/editing properly ====<br /> From Mantis [[http://opensimulator.org/mantis/view.php?id=135 # 135]] and [[http://opensimulator.org/mantis/view.php?id=223 # 223]]: &lt;br /&gt;<br /> Linked objects: while linking/unlinking objects seems to work fine, the editing of single prims inside a linked object doesn't work correctly. You have to check the box &quot;Edit linked parts&quot;, then you can select a single prim and edit it, but in most cases the changes in size- and/or postion-parameters are not accepted and revert immediately to the original ones. It is not completely reproducible, as it may work in some single case though.&lt;br /&gt;<br /> '''Workaround:''' unlink the whole object, make the changes, and relink the whole thing again. &lt;br /&gt; ''note:'' re-scaling unlinked objects in grid mode seems to work better than in standalone. <br /> <br /> &lt;hr&gt;<br /> <br /> === Exception and loss of ode physics (System.EntryPointNotFoundException: dSpaceLockQuery) ===<br /> <br /> The following error is usually caused by using the wrong version of ''libode'':<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [SCENE] [02-01 22:20:40] System.EntryPointNotFoundException: dSpaceLockQuery<br /> :at (wrapper managed-to-native) Ode.NET.d:SpaceLockQuery (intptr)<br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.waitForSpaceUnlock (IntPtr space) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter.AvatarGeomAndBodyCreation (Single npositionX, Single npositionY, Single npositionZ, Single tensor) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter..ctor (System.String avName, OpenSim.Region.Physics.OdePlugin.OdeScene parent_scene, OpenSim.Region.Physics.Manager.PhysicsVector pos) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.AddAvatar (System.String avName, OpenSim.Region.Physics.Manager.PhysicsVector position) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.AddToPhysicalScene () [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.MakeRootAgent (LLVector3 pos, Boolean isFlying) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.Scene.AgentCrossing (UInt64 regionHandle, LLUUID agentID, LLVector3 position, Boolean isFlying) [0x00000]<br /> |}<br /> <br /> First try searching your filesystem to see if you have other copies of the ode physics engine:<br /> find / -name &quot;libode.so&quot;<br /> Then make sure you have the latest version.<br /> <br /> === MySQL connection errors after about 6-8 hours ===<br /> <br /> 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:<br /> <br /> set global wait_timeout=604800;<br /> <br /> === System.DllNotFoundException: gdiplus.dll ===<br /> <br /> First, check to make sure that &lt;tt&gt;libgdiplus.so&lt;/tt&gt; is known to the dynamic linker:<br /> <br /> /sbin/ldconfig -p | grep libgdiplus<br /> <br /> If nothing is found, make sure that the directory libgdiplus.so exists in is either in your &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt; environment variable or listed in a *.conf file (e.g., gdiplus.conf) in /etc/ld.so.conf.d/. Then run &lt;tt&gt;ldconfig&lt;/tt&gt; to update the cache. Then it should be able to find the library.<br /> <br /> 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 OpenSim with debugging information turned on:<br /> <br /> MONO_LOG_LEVEL=debug mono OpenSim.exe<br /> <br /> {It may show errors loading other libraries, like &lt;tt&gt;libexif.so.9&lt;/tt&gt;. In that case, linking to an existing version of the offending library may work:<br /> <br /> ln -s libexif.so.12 libexif.so.9<br /> <br /> 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 <br /> and add the line <br /> &lt;dllmap dll=&quot;gdiplus.dll&quot; target=&quot;/opt/local/lib/libgdiplus.dylib&quot; os=&quot;!windows&quot;/&gt;<br /> <br /> ''(Is there a cleaner solution than this?)''} **see below for alternative/cleaner fix**<br /> <br /> == When installing mono or libgdiplus0 you may get dependency missing libexif.so.9 == <br /> <br /> 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 )<br /> <br /> === The assembly mscorlib.dll was not found or could not be loaded ===<br /> <br /> 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.<br /> <br /> apt-get install nant<br /> <br /> === External Program Failed: /usr/lib/pkgconfig/../../lib/mono/2.0/gmcs.exe === <br /> <br /> This is quickly fixed by retrieving mono-gmcs.<br /> <br /> apt-get install mono-gmcs<br /> <br /> === The type or namespace name JScript does not exist in the namespace Microsoft ===<br /> <br /> Note that it says JScript over and over again. Hint perhaps?<br /> <br /> apt-get install mono-mjs libmono-microsoft8.0-cil<br /> <br /> On Fedora and OpenSUSE, the needed package is &quot;mono-jscript&quot;.<br /> <br /> === The type or namespace name Tcp does not exist in the namespace System.Runtime.Remoting.Channels ===<br /> <br /> This one is taken care of with a quick install:<br /> <br /> apt-get install libmono-system-runtime2.0-cil<br /> <br /> === Missing: libopenjpeg-libsl-2.1.2.0-x86_64.so ===<br /> <br /> You are probably on a 64-bit linux machine and may need to follow these instructions:<br /> <br /> * [[Installing_and_running_on_x86-64 |Installing and running on x86-64 ]]<br /> <br /> === error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file ===<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> apt-get install libglib2.0-0<br /> <br /> === The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file. ===<br /> <br /> This one seems to be fixed by retrieving the apt version of nant.<br /> <br /> apt-get install nant<br /> <br /> This can also be due to &lt;tt&gt;pkg-config&lt;/tt&gt; not being able to locate the &lt;tt&gt;mono.pc&lt;/tt&gt; file. Adding the directory containing this file to the environment variable &lt;tt&gt;PKG_CONFIG_PATH&lt;/tt&gt; may solve this.<br /> <br /> == Networking and config issues ==<br /> <br /> See also the wiki page:<br /> * [[Running]]<br /> <br /> === You are able to log in, but not connect to a Region from a remote client ===<br /> <br /> Look in your OpenSimulator/bin/Regions folder <br /> # Try '''0.0.0.0''' for the internal_ip_address in your region.xml(default.xml) file.&lt;br&gt;(you'll have one of these files for each region you have created)<br /> # '''external_host_name=&quot;127.0.0.1&quot;''' will need to be changed to the accessable DNS name such as &quot;opensim.example-host.com&quot; or &quot;71.6.131.152&quot; (your public accessable ip)<br /> <br /> ==Building OpenSim==<br /> ===I can't find any build files or solution files===<br /> * If you're on Windows, run<br /> runprebuild.bat<br /> * on Linux/Mac/FreeBSD, run <br /> runprebuild.sh<br /> <br /> === VS2005 won't open the .sln file ===<br /> * Try running VS2005 C#. You are probably running VS2005 C++. This is a C# project.<br /> <br /> ==Running OpenSim==<br /> === Running OpenSim.exe from a Cygwin shell has access denied for some dll's ===<br /> * Do a '&lt;tt&gt;cd bin&lt;/tt&gt;' followed by '&lt;tt&gt;chmod a+x *&lt;/tt&gt;' to make all dll files executable.<br /> ===I cannot start my sim===<br /> * See [[Configuration]]<br /> <br /> ==Something Has Gone Wrong!==<br /> === I get errors concerning 'owner_uuid' when starting up my grid after updating from svn beyond r3254 ===<br /> When updating to recent revisions after r3254, we are now using the unused owner_uuid. There are some grids whose mysql tables were created during a time when this field was inadvertently removed from the .sql script that initializes the regions table. Logging in to your mysql instance and executing this SQL query to add the missing owner_uuid should solve this issue:<br /> alter table `regions` add column `owner_uuid` varchar(36) default '00000000-0000-0000-0000-000000000000' not null, comment 'Rev.2';<br /> The punctuation around regions and owner_uuid is &quot;grave accent&quot;. The punctuation around the default value and the comment is the single quote. The &quot;grave accent&quot; is the one generally to the left of the One button, under the tilde and the single-quote, is, well, underneath the double quote. I think this matters to mysql.<br /> <br /> === I get errors concerning 'State' when starting up my grid after updating from svn beyond r3786 ===<br /> After r3786, a new 'State' field has been added to the 'primshapes' table on SQLite. This field is used to persist trees and grass.<br /> You may have an empty region at startup, because OpenSim does not find this 'State' field and does not know what to do.<br /> The best is to use SQLiteBrowser or another SQLite table editor (download it at [http://sqlitebrowser.sourceforge.net/ http://sqlitebrowser.sourceforge.net/]) to create the missing field:<br /> alter table primshapes add column State integer default 0<br /> Just launch SQLiteBrowser, use File/Open database, then browse to OpenSim.db file and open it. Then, go to the &quot;Execute SQL&quot; tab, copy/paste the command above in the &quot;SQL string&quot; textbox, then hit the &quot;Execute query&quot; button.<br /> <br /> === I get a timeout during region handshake ===<br /> * Do you have the correct IP in your Regions\* config files?<br /> * Do you have multiple interfaces on the server running OpenSim? OpenSim 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.<br /> <br /> === I cannot connect to my OpenSim ===<br /> * See [[OpenSim: Connecting]]<br /> <br /> ===I can connect but cannot move===<br /> If the client connects but the avatar can only spin in place and not move, then the sim is not correctly configured. It completed the initial login function, but packets are not being exchanged between the client and the sim, probably due to a network configuration error on the sim.<br /> * See [[OpenSim: Configuration]]<br /> <br /> === From time to time my Avatar seems to get stuck ===<br /> Right now there is a bottle neck when syncing prims off to the database. This will cause small (5 - 10 second) apparent hangs of the Avatar, but it will recover fine once the data is synced. It is a known issue based on legacy architecture of some of the data storage code. We hope this will be removed soon.<br /> <br /> === I have problems with viewing the worldmap ===<br /> * This may happen when running OpenSim on a Linux server, both in grid or standalone mode.<br /> * 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...<br /> * Reason: your svn source trunk does not have the correct (or whatever...) &lt;tt&gt;libopenjpeg-libsl&lt;/tt&gt; library.<br /> * Other reason: the file &quot;defaultstripe.png&quot; does not exists in the same OpenSim folder, or is corrupted.<br /> * Solution: get the newest code from libsecondlife (&lt;tt&gt;svn co svn://opensecondlife.org/libsl/trunk&lt;/tt&gt;), '&lt;tt&gt;make&lt;/tt&gt;' manually in the subdir &lt;tt&gt;openjpeg-libsl&lt;/tt&gt;, and copy the resulting &lt;tt&gt;libopenjpeg-libsl-2.1.2.0.so&lt;/tt&gt; into your OpenSim &lt;tt&gt;bin&lt;/tt&gt; subdir, overwriting the existing one.<br /> * Recompile &amp; restart OpenSim<br /> <br /> ==Exceptions on the Console==<br /> This is a list of Exceptions that you may see on the console, what they mean, and if they are a problem.<br /> <br /> ===System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so===<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> Failed generating terrain map: System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so<br /> : at (wrapper managed-to-native) OpenJPEGNet.OpenJPEG:LibslAllocDecoded OpenJPEGNet.OpenJPEG/LibslImage&amp;)<br /> : at OpenJPEGNet.OpenJPEG.Encode (System.Byte[] decoded, Int32 width, Int32 height, Int32 components, Boolean lossless) [0x00000]<br /> :at OpenJPEGNet.OpenJPEG.EncodeFromImage (System.Drawing.Bitmap bitmap, Boolean lossless) [0x00000]<br /> :at OpenSim.Region.Terrain.TerrainEngine.ExportJpegImage (System.String gradientmap) [0x00000]<br /> |}<br /> <br /> 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:<br /> * You have an old processor (libopenjpeg has been compiled with optimizations)<br /> * You are running in 64bit mode (none of the native libs are built for 64bit)<br /> <br /> You can rebuild your own libopenjpeg from source, or run in a compatible environment.<br /> You can do this by:<br /> svn co svn://openmv.org/libsl/libopenmetaverse/trunk libsl<br /> cd libsl/openjpeg-libsl/<br /> make<br /> <br /> then copy libopenjpeg-libsl-2.1.2.0.so into OpenSim bin-folder.<br /> <br /> === System.NullReferenceException at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion ===<br /> [LOGIN END]: XMLRPC Login failed, System.NullReferenceException: Object reference not set to an instance of an object<br /> at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion (OpenSim.Framework.RegionInfo regionInfo, OpenSim.Framework.UserProfileData user, OpenSim.Framework.Communications.LoginResponse response) [0x00000] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:293<br /> at OpenSim.Region.Communications.Local.LocalLoginService.CustomiseResponse (OpenSim.Framework.Communications.LoginResponse response, OpenSim.Framework.UserProfileData theUser, System.String startLocationRequest) [0x00520] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:253<br /> at OpenSim.Framework.Communications.LoginService.XmlRpcLoginMethod (Nwc.XmlRpc.XmlRpcRequest request) [0x00369] in /home/sim/svn/opensim/OpenSim/Framework/Communications/LoginService.cs:252<br /> <br /> Your first startup of OpenSim 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.<br /> <br /> ==Grid Mode==<br /> Note: Grid Mode isn't officially supported yet. As such, you are pretty much on your own if you are trying to get OpenSim up and running in Grid Mode.<br /> <br /> === I start the sim and it doesn't connect to any grid ===<br /> <br /> When OpenSim is first started, it needs configuration.<br /> <br /> * See [[OpenSim: Configuration]].<br /> <br /> === I start the OpenSim.Grid.UserServer.exe and it gives an error===<br /> If this error is access denied for &lt;tt&gt;username@localhost&lt;/tt&gt;, the mysql database is not set up.<br /> It will print some text and wait for input - either an enter to accept a default value, or another value you can supply.<br /> * See [[OpenSim: Configuration]].<br /> <br /> === I want to run my own Local Grid but one or more servers fail to start===<br /> * Be sure that you're able to start &lt;tt&gt;OpenSim.exe&lt;/tt&gt; alone, in Standalone mode, and to be able to login.<br /> * Start the servers in the correct UGAS order and answer the questions as recommended (see [[OpenSim: Configuration]]).<br /> * Set all the external URI's to the correct IP: 127.0.0.1 if running on your local machine, or aaa.bbb.ccc.ddd if running on a remote server.<br /> * Check again all the &lt;tt&gt;*.xml&lt;/tt&gt; configuration files for any wrong settings or typing errors...!<br /> * Don't forget to connect with your SL-viewer to port 8002 (Grid User-Server) instead of 9000 (Standalone OpenSim-Server).<br /> * Delete all &lt;tt&gt;*.xml&lt;/tt&gt; and &lt;tt&gt;*.yap&lt;/tt&gt; files in the &lt;tt&gt;bin&lt;/tt&gt; directory if you want to run a full reconfiguration again.<br /> <br /> === I get a bunch of asset not found errors, while connected to a online grid, and my inventory doesn't seem to work right===<br /> *Make sure your opensim.ini has ' asset_database = &quot;grid&quot; ' otherwise it will not work correctly.<br /> <br /> === My grid works fine with one user but when two users login in the same time both get stuck ===<br /> * Make sure you have export MONO_THREADS_PER_CPU=&quot;100&quot; in your environment<br /> <br /> === After ~20 minutes my region starts to take 100% cpu and region(s) hang ===<br /> * If you have mono 1.9.1 or lower upgrade to mono 2.2.<br /> <br /> ==Hypergrid==<br /> ===After starting OpenSim with Hypergrid enabled my inventory wont load!===<br /> *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.<br /> *Check the XML config files for your UGAIM servers to make sure that everything is running off of a publicly accessible IP address.<br /> **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.<br /> <br /> 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.<br /> <br /> &lt;div align = center&gt;&lt;B&gt;!!!!WARNING!!!! - Be smart! Always make a backup of your databases before making any changes to OpenSim! - !!!!WARNING!!!!&lt;/b&gt;&lt;/div&gt;<br /> &lt;pre&gt;<br /> update users set userInventoryURI=&quot;http://new.UGAIM.address:8004&quot; where userInventoryURI = &quot;http://old.UGAIM.address:8004&quot;;<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> update users set userAssetURI=&quot;http://new.UGAIM.address:8003&quot; where userAssetURI = &quot;http://old.UGAIM.address:8003&quot;;<br /> &lt;/pre&gt;<br /> *If you're running in standalone mode... - Anyone familiar with standalone want to fill this in? -<br /> [[Category:Users]]<br /> <br /> == ScriptEngine Issues ==<br /> === Got &quot;Primitive: Error compiling script: unknown char: . error&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you could have this error :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> unknown char: .<br /> &lt;/pre&gt;<br /> And on the console :<br /> &lt;pre&gt;<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Unloading script<br /> 11:06:37 - Exception in MaintenanceLoopThread. Thread will recover after 5 sec throttle. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.<br /> at System.Collections.Generic.Dictionary`2[OpenSim.Region.ScriptEngine.Interfaces.IEventReceiver,OpenSim.Region.ScriptEngine.Shared.Api.Plugins.Dataserver].get_Item (IEventReceiver key) [0x00000]<br /> at OpenSim.Region.ScriptEngine.Shared.Api.AsyncCommandManager.RemoveScript (IEventReceiver engine, UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager._StopScript (UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager.DoScriptLoadUnload () [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.MaintenanceThread.MaintenanceLoop () [0x00000]<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Loading script<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: ScriptManager StartScript: localID: 720001, itemID: 88c9d28c-6004-4609-a707-717190de044a<br /> 11:06:37 - [Compiler]: Compiled new assembly for fad15951-f9aa-493f-be68-2aaf5ff8a3c9<br /> 11:06:37 - [SCRIPT]: Compiled assetID fad15951-f9aa-493f-be68-2aaf5ff8a3c9: ScriptEngines/a83150da-1ab1-11dd-89fb-0014853ee9da/CommonCompiler_compiled_fad15951-f9aa-493f-be68-2aaf5ff8a3c9.dll<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: AppDomain Loading: OpenSim.Region.ScriptEngine.Shared, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null<br /> &lt;/pre&gt;<br /> This happens on '''linux''' when your locales are not set to default ( &quot;C&quot; ).<br /> * You could refer to [http://opensimulator.org/mantis/view.php?id=2088 Mantis #2088] and [http://opensimulator.org/mantis/view.php?id=2015 Mantis #2015] for a workaround to run opensim.<br /> &lt;pre&gt;<br /> env LANG=C mono --debug OpenSim.exe<br /> &lt;/pre&gt;<br /> * You could also change your locale setup. Here is what I use in my '.bash_profile' :<br /> &lt;pre&gt;<br /> export LC_ALL=C<br /> export LANG=C<br /> &lt;/pre&gt;<br /> I know it's a ugly way to setup locales on a linux box, but it works fine on my '''Linux From Scratch''' box.<br /> <br /> '''Rq''': I saw Melanie has corrected some parts of the source code a few weeks ago to avoid such problems.<br /> <br /> === Get &quot;Primitive: Error compiling script: ApplicationName='gmcs', ...&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you have an error something like :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> ApplicationName='gmcs', CommandLine='/target:library /debug+ /optimize- /out:<br /> &quot;ScriptEngines/430c29d0-c5c6-11dd-ad8b-0800200c9a66/CommonCompiler_compiled_fbe5e682-afae-4f1a-805b-0125031101f7.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.Api.Runtime.dll&quot; -- <br /> &quot;/tmp/11b81aac/594d02ce.0.cs&quot; ', CurrentDirectory=''<br /> &lt;/pre&gt;<br /> <br /> Other features include &quot;Touch&quot; being disabled on the right click menu wheel.<br /> <br /> You might have a broken mono install (i.e. discovered as mono but not gmcs installed on a Ubuntu 8.10 Intrepid machine.)<br /> <br /> Check mono-gmcs (sudo apt-get install mono-gmcs) is correctly installed.<br /> <br /> == Locales Issues ==<br /> Well, some of us, OpenSim users, ran into random crash of the OpenSim Region server in grid mode ... <br /> <br /> I have made many tests to find a solution about that problem.<br /> <br /> I first ran into this problem with OpenSIM SVN.6660 ... Even if I have no users connected, my OpenSim region server randomly crash ( after 1 hour, or 5 hours, ... ).<br /> <br /> My first idea was to upgrade to the latest SVN release, no chance, same problem. So I made a test with a previous SVN release ( SVN.6575 ) which is running fine on another server ( same OS, same parameters, same mono release, ... ) : No chance, same problem.<br /> <br /> Then, I tried to play with locales, recompile the '''screen''' unix command line utility I use to run my servers, ... No chance again.<br /> <br /> So, I checked the memory usage on my Server, and I discovered that with the last SVN release, the amount of memory needed to run OpenSim server in multi-region/grid mode increased :) ... So, I have tuned my MySQL server to use less memory. Was better, but my OpenSim region server still randomly crash ( but could stay alive longer than before ).<br /> <br /> Then, trying to play with the '''screen''' command line options ... And all my tests shows that the '''--debug''' option impact the stability of the server.<br /> <br /> Initially, I used such command line to run OpenSim :<br /> &lt;pre&gt;<br /> /screen -S Region-service -d -m --debug mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> Without the '''--debug''' option, everything seems to be more stable.<br /> <br /> About locales, if you read mantis and threads in opensim-dev / opensim-users, you know that there are issues on system that are not &quot;en_US&quot; or &quot;C&quot; local compliant.<br /> <br /> I have re-setup my server to be full &quot;en_US.UTF8&quot;.<br /> <br /> On my Ubuntu 8.0.4 server :<br /> &lt;pre&gt;<br /> # cat /etc/default/locale<br /> LANG=&quot;en_US.UTF-8&quot;<br /> <br /> # cat /var/lib/locales/supported.d/local<br /> fr_FR.UTF-8 UTF-8<br /> en_US.UTF-8 UTF-8<br /> <br /> # cat /etc/environment<br /> PATH=&quot;/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games&quot;<br /> LANG=&quot;en_US&quot;<br /> LANGUAGE=&quot;en_US&quot;<br /> &lt;/pre&gt;<br /> And maybe you should need :<br /> &lt;pre&gt;<br /> # sudo dpkg-reconfigure locales<br /> &lt;/pre&gt;<br /> <br /> So, the resulting '''screen''' command line options should be :<br /> &lt;pre&gt;<br /> screen -S Region-service -d -m -U mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> This allow me to run OpenSim SVN.6575 without crash during more than 48 hours, and also SVN.6735 ... <br /> <br /> Hope those informations could help peoples.<br /> <br /> Just for your information : <br /> <br /> Here is my '''OpenSim Startup script''' :<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> echo &quot;User-Service...&quot;<br /> /usr/local/bin/screen -S User-service -d -m -U mono OpenSim.Grid.UserServer.exe<br /> sleep 5<br /> echo &quot;Grid-Service...&quot;<br /> /usr/local/bin/screen -S Grid-service -d -m -U mono OpenSim.Grid.GridServer.exe<br /> sleep 5<br /> echo &quot;Asset-Service...&quot;<br /> /usr/local/bin/screen -S Asset-service -d -m -U mono OpenSim.Grid.AssetServer.exe<br /> sleep 10<br /> echo &quot;Inventory-Service...&quot;<br /> /usr/local/bin/screen -S Inventory-service -d -m -U mono OpenSim.Grid.InventoryServer.exe<br /> sleep 5<br /> echo &quot;Region-Service...&quot;<br /> /usr/local/bin/screen -S Region-service -d -m -U mono OpenSim.exe<br /> sleep 5<br /> echo &quot; &quot;<br /> echo &quot; &quot;<br /> /usr/local/bin/screen -list<br /> &lt;/pre&gt;<br /> <br /> Here is also a small script that give you a menu to connect to the '''screen(s)''' sessions :<br /> &lt;pre&gt;<br /> #!/usr/bin/perl<br /> <br /> use strict;<br /> use Term::Menu;<br /> <br /> my $EXIT = 1;<br /> <br /> my $MainTitle = &quot;+-----------------------------------------------------+\n&quot;;<br /> $MainTitle .= &quot;| Connexion SCREEN aux Serveurs OPENSIM |\n&quot;;<br /> $MainTitle .= &quot;| |\n&quot;;<br /> $MainTitle .= &quot;| ( Type CTRL+A+D to exit the Screen Console. ) |\n&quot;;<br /> $MainTitle .= &quot;+-----------------------------------------------------+\n&quot;;<br /> <br /> while ( $EXIT == 1 )<br /> {<br /> <br /> system(&quot;screen -list | grep service &gt; /tmp/osg.services&quot;);<br /> my %LIST = ();<br /> open(IN, &quot;/tmp/osg.services&quot;);<br /> while ( my $i = &lt;IN&gt; )<br /> {<br /> chomp($i);<br /> <br /> $i =~ s/\./#/g;<br /> $i =~ s/\-service\t/#/g;<br /> $i =~ s/\t//g;<br /> $i =~ s/\(//g;<br /> $i =~ s/\)//g;<br /> <br /> my @STATUS = split(/#/, $i);<br /> $LIST{$STATUS[1]} = $STATUS[2];<br /> }<br /> close(IN);<br /> <br /> my %LIST2 = ();<br /> my @indices = ('User', 'Grid', 'Asset', 'Inventory', 'Region');<br /> <br /> foreach my $key ( @indices )<br /> {<br /> # print &quot;$key --&gt; $LIST{$key}\n&quot;;<br /> if ( $LIST{$key} =~ /Attached/ )<br /> {<br /> $LIST2{$key} = &quot;[X]&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{$key} = &quot;[ ]&quot;;<br /> }<br /> }<br /> <br /> if ( $LIST{'User'} =~ /Attached/ )<br /> {<br /> $LIST2{'USER'} = &quot;X&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{'USER'} = &quot;-&quot;;<br /> }<br /> <br /> system ('clear');<br /> my $prompt = new Term::Menu (<br /> spaces =&gt; 3,<br /> aftertext =&gt; &quot;\nChoisir une option : &quot;,<br /> beforetext =&gt; ${MainTitle},<br /> delim =&gt; &quot;. &quot;,<br /> );<br /> <br /> my $SEP = &quot; &quot;;<br /> <br /> my $answer = $prompt-&gt;menu(<br /> osg_user =&gt; [&quot;OpenSim User Server $SEP$LIST2{'User'}&quot;, '1'],<br /> osg_grid =&gt; [&quot;OpenSim Grid Server $SEP$LIST2{'Grid'}&quot;, '2'],<br /> osg_asset =&gt; [&quot;OpenSim Asset Server $SEP$LIST2{'Asset'}&quot;, '3'],<br /> osg_inventory =&gt; [&quot;OpenSim Inventory Server $SEP$LIST2{'Inventory'}&quot;, '4'],<br /> osg_region =&gt; [&quot;OpenSim Region Server $SEP$LIST2{'Region'}\n&quot;, '5'],<br /> osg_shutdown =&gt; [&quot;Shutdown Servers (Manual)&quot;,'6'],<br /> osg_shutdown2 =&gt; [&quot;Shutdown Servers (Hard)\n&quot;,'7'],<br /> quit =&gt; [&quot;Quitter&quot;, 'q'],<br /> );<br /> <br /> if ( &quot;${answer}&quot; eq &quot;quit&quot; )<br /> {<br /> $EXIT = 0;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_user&quot; )<br /> {<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_grid&quot; )<br /> {<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_asset&quot; )<br /> {<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_inventory&quot; )<br /> {<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_region&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown2&quot; )<br /> {<br /> # system(&quot;/OPENSIM/shutdownGrid.py&quot;);<br /> system(&quot;screen -S Region-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Inventory-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Asset-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Grid-service -r -m -X quit&quot;);<br /> system(&quot;screen -S User-service -r -m -X quit&quot;);<br /> $EXIT = 0;<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Regards, <br /> Ursula Matova.</div>

Dale Mahalko http://opensimulator.org/wiki/Troubleshooting 2010-04-04T05:49:20Z

<p>Dale Mahalko: /* I can't find any build files or solution files */ formatting</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> This page gives any system-specific configuration settings that may be useful, and advice for problems that might be encountered.<br /> __TOC__<br /> {{clear}}<br /> [[Category:Users]]<br /> <br /> == System-specific configuration ==<br /> === CentOS 5 ===<br /> <br /> To install mono and nant, you can use the &quot;Linux Installer for x86&quot; found at http://www.mono-project.com/Downloads.<br /> <br /> SVN can be installed by:<br /> <br /> yum install subversion<br /> <br /> Mono defaults to installing into &lt;tt&gt;/opt&lt;/tt&gt;, so you may have to add this path to your environment variables, for example, in your &lt;tt&gt;~/.bashrc&lt;/tt&gt;:<br /> <br /> export PATH=&quot;/opt/mono-1.2.5/bin:$PATH&quot;<br /> export PKG_CONFIG_PATH=&quot;/opt/mono-1.2.5/lib/pkgconfig:$PKG_CONFIG_PATH&quot;<br /> export MANPATH=&quot;/opt/mono-1.2.5/share/man:$MANPATH&quot;<br /> export LD_LIBRARY_PATH=&quot;/opt/mono-1.2.5/lib:$LD_LIBRARY_PATH&quot;<br /> <br /> After changing &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt;, you should update the dynamic linker cache:<br /> <br /> ldconfig<br /> <br /> You may still encounter the &quot;The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file.&quot; error listed below. In that case, this may fix this:<br /> <br /> yum install glib<br /> <br /> If you are running a firewall as well (i.e., if &lt;tt&gt;iptables -L&lt;/tt&gt; shows a list of ACCEPT and REJECT rules), you'll have to open the necessary ports if you want to access the sim from other machines. For standalone mode:<br /> <br /> iptables -I RH-Firewall-1-INPUT -p tcp --dport 9000 -j ACCEPT<br /> iptables -I RH-Firewall-1-INPUT -p udp --dport 9000 -j ACCEPT<br /> <br /> 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:<br /> sudo yum install libgdiplus<br /> sudo yum install libexif<br /> sudo ln -s /usr/lib64/libgdiplus.so.0 /usr/lib64/libgdiplus.so<br /> ldconfig<br /> <br /> That finally enabled me to run OpenSim without errors, and even connect to other grids.<br /> <br /> === Debian 4.0r0 ===<br /> <br /> If you set your system to use unstable sources, and then install some packages listed below, everything should just work. To use unstable sources, modify your &lt;tt&gt;/etc/apt/sources.list&lt;/tt&gt; file, replacing 'etch' or 'stable' with 'unstable':<br /> <br /> deb ftp://ftp.debian.org/debian/ unstable main<br /> deb-src ftp://ftp.debian.org/debian/ unstable main<br /> <br /> Then update your packages to the new versions:<br /> <br /> apt-get update<br /> apt-get dist-upgrade<br /> <br /> This will probably change a large number of packages, and may break things.<br /> In my experience, however, if you do not use unstable sources then the packages are not up to date enough, and you run into version issues, which lead to two DllNotFoundException errors below appearing in the console output: gdiplus.dll and libopenjpeg-libsl-2.1.2.0.so.<br /> <br /> Once the sources are updated, we need to install the necessary packages to be able to build OpenSim:<br /> <br /> apt-get install subversion mono nant mono-gmcs mono-mjs libmono-microsoft8.0-cil libmono-system-runtime2.0-cil<br /> <br /> If any of these packages are missing, you'll probably encounter one of the errors listed below. However, with these packages, OpenSim should build cleanly.<br /> <br /> Please note: If you are using mysql as storage on unstable you may get the following error:-<br /> <br /> Exception: System.NotSupportedException: CodePage 1252 not supported<br /> at System.Text.Encoding.GetEncoding (Int32 codePage) [0x00000] <br /> <br /> To get it to work, try installing the libmono-i18n2.0-cil package<br /> <br /> apt-get install libmono-i18n2.0-cil<br /> <br /> === Gentoo ===<br /> some Mono dependency &amp; latest Mono itself may use &quot;~x86&quot; masked packages (assuming x86 is your platform, change may be made to reflect your ex:&quot;~amd64&quot; for 64bits). You could check for USE parameter with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge -vp subversion nant mono libgdiplus<br /> <br /> Then install with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge subversion nant mono libgdiplus<br /> <br /> N.B: The ACCEPT_KEYWORDS=&quot;~x86&quot; 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<br /> <br /> === Mac OS X ===<br /> This assumes you're using the universal binary for mono from the [http://www.mono-project.com/ Mono Project] site.<br /> <br /> If you are using OS X 10.4, you should also install X11 from the OS X install CDs.<br /> In OS X 10.5, this is not required.<br /> <br /> If you get errors about the 2.0 framework not being supported, you may need to update your &lt;tt&gt;pkg-config&lt;/tt&gt; path.<br /> I set this in &lt;tt&gt;~/.bash_profile&lt;/tt&gt;:<br /> export PKG_CONFIG_PATH=&quot;/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}&quot;<br /> <br /> == Errors and fixes ==<br /> <br /> === Build workarounds due to non-functionality or bugs: ===<br /> <br /> ==== Disappearing prims due to duplicate UID's ====<br /> 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. This switch is documented in the [[Running#General OpenSim server commands|general server commands]] section. (&lt;nowiki&gt;load-xml &lt;filename&gt; -newUID&lt;/nowiki&gt;). 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.<br /> <br /> ==== Linked objects not scaling/editing properly ====<br /> From Mantis [[http://opensimulator.org/mantis/view.php?id=135 # 135]] and [[http://opensimulator.org/mantis/view.php?id=223 # 223]]: &lt;br /&gt;<br /> Linked objects: while linking/unlinking objects seems to work fine, the editing of single prims inside a linked object doesn't work correctly. You have to check the box &quot;Edit linked parts&quot;, then you can select a single prim and edit it, but in most cases the changes in size- and/or postion-parameters are not accepted and revert immediately to the original ones. It is not completely reproducible, as it may work in some single case though.&lt;br /&gt;<br /> '''Workaround:''' unlink the whole object, make the changes, and relink the whole thing again. &lt;br /&gt; ''note:'' re-scaling unlinked objects in grid mode seems to work better than in standalone. <br /> <br /> &lt;hr&gt;<br /> <br /> === Exception and loss of ode physics (System.EntryPointNotFoundException: dSpaceLockQuery) ===<br /> <br /> The following error is usually caused by using the wrong version of ''libode'':<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [SCENE] [02-01 22:20:40] System.EntryPointNotFoundException: dSpaceLockQuery<br /> :at (wrapper managed-to-native) Ode.NET.d:SpaceLockQuery (intptr)<br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.waitForSpaceUnlock (IntPtr space) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter.AvatarGeomAndBodyCreation (Single npositionX, Single npositionY, Single npositionZ, Single tensor) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter..ctor (System.String avName, OpenSim.Region.Physics.OdePlugin.OdeScene parent_scene, OpenSim.Region.Physics.Manager.PhysicsVector pos) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.AddAvatar (System.String avName, OpenSim.Region.Physics.Manager.PhysicsVector position) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.AddToPhysicalScene () [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.MakeRootAgent (LLVector3 pos, Boolean isFlying) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.Scene.AgentCrossing (UInt64 regionHandle, LLUUID agentID, LLVector3 position, Boolean isFlying) [0x00000]<br /> |}<br /> <br /> First try searching your filesystem to see if you have other copies of the ode physics engine:<br /> find / -name &quot;libode.so&quot;<br /> Then make sure you have the latest version.<br /> <br /> === MySQL connection errors after about 6-8 hours ===<br /> <br /> 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:<br /> <br /> set global wait_timeout=604800;<br /> <br /> === System.DllNotFoundException: gdiplus.dll ===<br /> <br /> First, check to make sure that &lt;tt&gt;libgdiplus.so&lt;/tt&gt; is known to the dynamic linker:<br /> <br /> /sbin/ldconfig -p | grep libgdiplus<br /> <br /> If nothing is found, make sure that the directory libgdiplus.so exists in is either in your &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt; environment variable or listed in a *.conf file (e.g., gdiplus.conf) in /etc/ld.so.conf.d/. Then run &lt;tt&gt;ldconfig&lt;/tt&gt; to update the cache. Then it should be able to find the library.<br /> <br /> 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 OpenSim with debugging information turned on:<br /> <br /> MONO_LOG_LEVEL=debug mono OpenSim.exe<br /> <br /> {It may show errors loading other libraries, like &lt;tt&gt;libexif.so.9&lt;/tt&gt;. In that case, linking to an existing version of the offending library may work:<br /> <br /> ln -s libexif.so.12 libexif.so.9<br /> <br /> 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 <br /> and add the line <br /> &lt;dllmap dll=&quot;gdiplus.dll&quot; target=&quot;/opt/local/lib/libgdiplus.dylib&quot; os=&quot;!windows&quot;/&gt;<br /> <br /> ''(Is there a cleaner solution than this?)''} **see below for alternative/cleaner fix**<br /> <br /> == When installing mono or libgdiplus0 you may get dependency missing libexif.so.9 == <br /> <br /> 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 )<br /> <br /> === The assembly mscorlib.dll was not found or could not be loaded ===<br /> <br /> 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.<br /> <br /> apt-get install nant<br /> <br /> === External Program Failed: /usr/lib/pkgconfig/../../lib/mono/2.0/gmcs.exe === <br /> <br /> This is quickly fixed by retrieving mono-gmcs.<br /> <br /> apt-get install mono-gmcs<br /> <br /> === The type or namespace name JScript does not exist in the namespace Microsoft ===<br /> <br /> Note that it says JScript over and over again. Hint perhaps?<br /> <br /> apt-get install mono-mjs libmono-microsoft8.0-cil<br /> <br /> On Fedora and OpenSUSE, the needed package is &quot;mono-jscript&quot;.<br /> <br /> === The type or namespace name Tcp does not exist in the namespace System.Runtime.Remoting.Channels ===<br /> <br /> This one is taken care of with a quick install:<br /> <br /> apt-get install libmono-system-runtime2.0-cil<br /> <br /> === Missing: libopenjpeg-libsl-2.1.2.0-x86_64.so ===<br /> <br /> You are probably on a 64-bit linux machine and may need to follow these instructions:<br /> <br /> * [[Installing_and_running_on_x86-64 |Installing and running on x86-64 ]]<br /> <br /> === error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file ===<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> apt-get install libglib2.0-0<br /> <br /> === The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file. ===<br /> <br /> This one seems to be fixed by retrieving the apt version of nant.<br /> <br /> apt-get install nant<br /> <br /> This can also be due to &lt;tt&gt;pkg-config&lt;/tt&gt; not being able to locate the &lt;tt&gt;mono.pc&lt;/tt&gt; file. Adding the directory containing this file to the environment variable &lt;tt&gt;PKG_CONFIG_PATH&lt;/tt&gt; may solve this.<br /> <br /> == Networking and config issues ==<br /> <br /> See also the wiki page:<br /> * [[Running]]<br /> <br /> === You are able to log in, but not connect to a Region from a remote client ===<br /> <br /> Look in your OpenSimulator/bin/Regions folder <br /> # Try '''0.0.0.0''' for the internal_ip_address in your region.xml(default.xml) file.&lt;br&gt;(you'll have one of these files for each region you have created)<br /> # '''external_host_name=&quot;127.0.0.1&quot;''' will need to be changed to the accessable DNS name such as &quot;opensim.example-host.com&quot; or &quot;71.6.131.152&quot; (your public accessable ip)<br /> <br /> ==Building OpenSim==<br /> ===I can't find any build files or solution files===<br /> * If you're on Windows, run<br /> runprebuild.bat<br /> * on Linux/Mac/FreeBSD, run <br /> runprebuild.sh<br /> <br /> === VS2005 won't open the .sln file ===<br /> * Try running VS2005 C#. You are probably running VS2005 C++. This is a C# project.<br /> <br /> ==Running OpenSim==<br /> === Running OpenSim.exe from a Cygwin shell has access denied for some dll's ===<br /> * Do a '&lt;tt&gt;cd bin&lt;/tt&gt;' followed by '&lt;tt&gt;chmod a+x *&lt;/tt&gt;' to make all dll files executable.<br /> ===I cannot start my sim===<br /> * See [[Configuration]]<br /> <br /> ==Something Has Gone Wrong!==<br /> === I get errors concerning 'owner_uuid' when starting up my grid after updating from svn beyond r3254 ===<br /> When updating to recent revisions after r3254, we are now using the unused owner_uuid. There are some grids whose mysql tables were created during a time when this field was inadvertently removed from the .sql script that initializes the regions table. Logging in to your mysql instance and executing this SQL query to add the missing owner_uuid should solve this issue:<br /> alter table `regions` add column `owner_uuid` varchar(36) default '00000000-0000-0000-0000-000000000000' not null, comment 'Rev.2';<br /> The punctuation around regions and owner_uuid is &quot;grave accent&quot;. The punctuation around the default value and the comment is the single quote. The &quot;grave accent&quot; is the one generally to the left of the One button, under the tilde and the single-quote, is, well, underneath the double quote. I think this matters to mysql.<br /> <br /> === I get errors concerning 'State' when starting up my grid after updating from svn beyond r3786 ===<br /> After r3786, a new 'State' field has been added to the 'primshapes' table on SQLite. This field is used to persist trees and grass.<br /> You may have an empty region at startup, because OpenSim does not find this 'State' field and does not know what to do.<br /> The best is to use SQLiteBrowser or another SQLite table editor (download it at [http://sqlitebrowser.sourceforge.net/ http://sqlitebrowser.sourceforge.net/]) to create the missing field:<br /> alter table primshapes add column State integer default 0<br /> Just launch SQLiteBrowser, use File/Open database, then browse to OpenSim.db file and open it. Then, go to the &quot;Execute SQL&quot; tab, copy/paste the command above in the &quot;SQL string&quot; textbox, then hit the &quot;Execute query&quot; button.<br /> <br /> === I get a timeout during region handshake ===<br /> * Do you have the correct IP in your Regions\* config files?<br /> * Do you have multiple interfaces on the server running OpenSim? OpenSim 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.<br /> <br /> === I cannot connect to my OpenSim ===<br /> * See [[OpenSim: Connecting]]<br /> <br /> ===I can connect but cannot move===<br /> If the client connects but the avatar can only spin in place and not move, then the sim is not correctly configured. It completed the initial login function, but packets are not being exchanged between the client and the sim, probably due to a network configuration error on the sim.<br /> * See [[OpenSim: Configuration]]<br /> <br /> === From time to time my Avatar seems to get stuck ===<br /> Right now there is a bottle neck when syncing prims off to the database. This will cause small (5 - 10 second) apparent hangs of the Avatar, but it will recover fine once the data is synced. It is a known issue based on legacy architecture of some of the data storage code. We hope this will be removed soon.<br /> <br /> === I have problems with viewing the worldmap ===<br /> * This may happen when running OpenSim on a Linux server, both in grid or standalone mode.<br /> * 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...<br /> * Reason: your svn source trunk does not have the correct (or whatever...) &lt;tt&gt;libopenjpeg-libsl&lt;/tt&gt; library.<br /> * Other reason: the file &quot;defaultstripe.png&quot; does not exists in the same OpenSim folder, or is corrupted.<br /> * Solution: get the newest code from libsecondlife (&lt;tt&gt;svn co svn://opensecondlife.org/libsl/trunk&lt;/tt&gt;), '&lt;tt&gt;make&lt;/tt&gt;' manually in the subdir &lt;tt&gt;openjpeg-libsl&lt;/tt&gt;, and copy the resulting &lt;tt&gt;libopenjpeg-libsl-2.1.2.0.so&lt;/tt&gt; into your OpenSim &lt;tt&gt;bin&lt;/tt&gt; subdir, overwriting the existing one.<br /> * Recompile &amp; restart OpenSim<br /> <br /> ==Exceptions on the Console==<br /> This is a list of Exceptions that you may see on the console, what they mean, and if they are a problem.<br /> <br /> ===System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so===<br /> Failed generating terrain map: System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so<br /> at (wrapper managed-to-native) OpenJPEGNet.OpenJPEG:LibslAllocDecoded OpenJPEGNet.OpenJPEG/LibslImage&amp;)<br /> at OpenJPEGNet.OpenJPEG.Encode (System.Byte[] decoded, Int32 width, Int32 height, Int32 components, Boolean lossless) [0x00000]<br /> at OpenJPEGNet.OpenJPEG.EncodeFromImage (System.Drawing.Bitmap bitmap, Boolean lossless) [0x00000]<br /> at OpenSim.Region.Terrain.TerrainEngine.ExportJpegImage (System.String gradientmap) [0x00000]<br /> <br /> 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:<br /> * You have an old processor (libopenjpeg has been compiled with optimizations)<br /> * You are running in 64bit mode (none of the native libs are built for 64bit)<br /> <br /> You can rebuild your own libopenjpeg from source, or run in a compatible environment.<br /> You can do this by:<br /> svn co svn://openmv.org/libsl/libopenmetaverse/trunk libsl<br /> cd libsl/openjpeg-libsl/<br /> make<br /> <br /> then copy libopenjpeg-libsl-2.1.2.0.so into OpenSim bin-folder.<br /> <br /> === System.NullReferenceException at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion ===<br /> [LOGIN END]: XMLRPC Login failed, System.NullReferenceException: Object reference not set to an instance of an object<br /> at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion (OpenSim.Framework.RegionInfo regionInfo, OpenSim.Framework.UserProfileData user, OpenSim.Framework.Communications.LoginResponse response) [0x00000] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:293<br /> at OpenSim.Region.Communications.Local.LocalLoginService.CustomiseResponse (OpenSim.Framework.Communications.LoginResponse response, OpenSim.Framework.UserProfileData theUser, System.String startLocationRequest) [0x00520] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:253<br /> at OpenSim.Framework.Communications.LoginService.XmlRpcLoginMethod (Nwc.XmlRpc.XmlRpcRequest request) [0x00369] in /home/sim/svn/opensim/OpenSim/Framework/Communications/LoginService.cs:252<br /> <br /> Your first startup of OpenSim 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.<br /> <br /> ==Grid Mode==<br /> Note: Grid Mode isn't officially supported yet. As such, you are pretty much on your own if you are trying to get OpenSim up and running in Grid Mode.<br /> <br /> === I start the sim and it doesn't connect to any grid ===<br /> <br /> When OpenSim is first started, it needs configuration.<br /> <br /> * See [[OpenSim: Configuration]].<br /> <br /> === I start the OpenSim.Grid.UserServer.exe and it gives an error===<br /> If this error is access denied for &lt;tt&gt;username@localhost&lt;/tt&gt;, the mysql database is not set up.<br /> It will print some text and wait for input - either an enter to accept a default value, or another value you can supply.<br /> * See [[OpenSim: Configuration]].<br /> <br /> === I want to run my own Local Grid but one or more servers fail to start===<br /> * Be sure that you're able to start &lt;tt&gt;OpenSim.exe&lt;/tt&gt; alone, in Standalone mode, and to be able to login.<br /> * Start the servers in the correct UGAS order and answer the questions as recommended (see [[OpenSim: Configuration]]).<br /> * Set all the external URI's to the correct IP: 127.0.0.1 if running on your local machine, or aaa.bbb.ccc.ddd if running on a remote server.<br /> * Check again all the &lt;tt&gt;*.xml&lt;/tt&gt; configuration files for any wrong settings or typing errors...!<br /> * Don't forget to connect with your SL-viewer to port 8002 (Grid User-Server) instead of 9000 (Standalone OpenSim-Server).<br /> * Delete all &lt;tt&gt;*.xml&lt;/tt&gt; and &lt;tt&gt;*.yap&lt;/tt&gt; files in the &lt;tt&gt;bin&lt;/tt&gt; directory if you want to run a full reconfiguration again.<br /> <br /> === I get a bunch of asset not found errors, while connected to a online grid, and my inventory doesn't seem to work right===<br /> *Make sure your opensim.ini has ' asset_database = &quot;grid&quot; ' otherwise it will not work correctly.<br /> <br /> === My grid works fine with one user but when two users login in the same time both get stuck ===<br /> * Make sure you have export MONO_THREADS_PER_CPU=&quot;100&quot; in your environment<br /> <br /> === After ~20 minutes my region starts to take 100% cpu and region(s) hang ===<br /> * If you have mono 1.9.1 or lower upgrade to mono 2.2.<br /> <br /> ==Hypergrid==<br /> ===After starting OpenSim with Hypergrid enabled my inventory wont load!===<br /> *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.<br /> *Check the XML config files for your UGAIM servers to make sure that everything is running off of a publicly accessible IP address.<br /> **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.<br /> <br /> 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.<br /> <br /> &lt;div align = center&gt;&lt;B&gt;!!!!WARNING!!!! - Be smart! Always make a backup of your databases before making any changes to OpenSim! - !!!!WARNING!!!!&lt;/b&gt;&lt;/div&gt;<br /> &lt;pre&gt;<br /> update users set userInventoryURI=&quot;http://new.UGAIM.address:8004&quot; where userInventoryURI = &quot;http://old.UGAIM.address:8004&quot;;<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> update users set userAssetURI=&quot;http://new.UGAIM.address:8003&quot; where userAssetURI = &quot;http://old.UGAIM.address:8003&quot;;<br /> &lt;/pre&gt;<br /> *If you're running in standalone mode... - Anyone familiar with standalone want to fill this in? -<br /> [[Category:Users]]<br /> <br /> == ScriptEngine Issues ==<br /> === Got &quot;Primitive: Error compiling script: unknown char: . error&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you could have this error :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> unknown char: .<br /> &lt;/pre&gt;<br /> And on the console :<br /> &lt;pre&gt;<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Unloading script<br /> 11:06:37 - Exception in MaintenanceLoopThread. Thread will recover after 5 sec throttle. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.<br /> at System.Collections.Generic.Dictionary`2[OpenSim.Region.ScriptEngine.Interfaces.IEventReceiver,OpenSim.Region.ScriptEngine.Shared.Api.Plugins.Dataserver].get_Item (IEventReceiver key) [0x00000]<br /> at OpenSim.Region.ScriptEngine.Shared.Api.AsyncCommandManager.RemoveScript (IEventReceiver engine, UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager._StopScript (UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager.DoScriptLoadUnload () [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.MaintenanceThread.MaintenanceLoop () [0x00000]<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Loading script<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: ScriptManager StartScript: localID: 720001, itemID: 88c9d28c-6004-4609-a707-717190de044a<br /> 11:06:37 - [Compiler]: Compiled new assembly for fad15951-f9aa-493f-be68-2aaf5ff8a3c9<br /> 11:06:37 - [SCRIPT]: Compiled assetID fad15951-f9aa-493f-be68-2aaf5ff8a3c9: ScriptEngines/a83150da-1ab1-11dd-89fb-0014853ee9da/CommonCompiler_compiled_fad15951-f9aa-493f-be68-2aaf5ff8a3c9.dll<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: AppDomain Loading: OpenSim.Region.ScriptEngine.Shared, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null<br /> &lt;/pre&gt;<br /> This happens on '''linux''' when your locales are not set to default ( &quot;C&quot; ).<br /> * You could refer to [http://opensimulator.org/mantis/view.php?id=2088 Mantis #2088] and [http://opensimulator.org/mantis/view.php?id=2015 Mantis #2015] for a workaround to run opensim.<br /> &lt;pre&gt;<br /> env LANG=C mono --debug OpenSim.exe<br /> &lt;/pre&gt;<br /> * You could also change your locale setup. Here is what I use in my '.bash_profile' :<br /> &lt;pre&gt;<br /> export LC_ALL=C<br /> export LANG=C<br /> &lt;/pre&gt;<br /> I know it's a ugly way to setup locales on a linux box, but it works fine on my '''Linux From Scratch''' box.<br /> <br /> '''Rq''': I saw Melanie has corrected some parts of the source code a few weeks ago to avoid such problems.<br /> <br /> === Get &quot;Primitive: Error compiling script: ApplicationName='gmcs', ...&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you have an error something like :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> ApplicationName='gmcs', CommandLine='/target:library /debug+ /optimize- /out:<br /> &quot;ScriptEngines/430c29d0-c5c6-11dd-ad8b-0800200c9a66/CommonCompiler_compiled_fbe5e682-afae-4f1a-805b-0125031101f7.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.Api.Runtime.dll&quot; -- <br /> &quot;/tmp/11b81aac/594d02ce.0.cs&quot; ', CurrentDirectory=''<br /> &lt;/pre&gt;<br /> <br /> Other features include &quot;Touch&quot; being disabled on the right click menu wheel.<br /> <br /> You might have a broken mono install (i.e. discovered as mono but not gmcs installed on a Ubuntu 8.10 Intrepid machine.)<br /> <br /> Check mono-gmcs (sudo apt-get install mono-gmcs) is correctly installed.<br /> <br /> == Locales Issues ==<br /> Well, some of us, OpenSim users, ran into random crash of the OpenSim Region server in grid mode ... <br /> <br /> I have made many tests to find a solution about that problem.<br /> <br /> I first ran into this problem with OpenSIM SVN.6660 ... Even if I have no users connected, my OpenSim region server randomly crash ( after 1 hour, or 5 hours, ... ).<br /> <br /> My first idea was to upgrade to the latest SVN release, no chance, same problem. So I made a test with a previous SVN release ( SVN.6575 ) which is running fine on another server ( same OS, same parameters, same mono release, ... ) : No chance, same problem.<br /> <br /> Then, I tried to play with locales, recompile the '''screen''' unix command line utility I use to run my servers, ... No chance again.<br /> <br /> So, I checked the memory usage on my Server, and I discovered that with the last SVN release, the amount of memory needed to run OpenSim server in multi-region/grid mode increased :) ... So, I have tuned my MySQL server to use less memory. Was better, but my OpenSim region server still randomly crash ( but could stay alive longer than before ).<br /> <br /> Then, trying to play with the '''screen''' command line options ... And all my tests shows that the '''--debug''' option impact the stability of the server.<br /> <br /> Initially, I used such command line to run OpenSim :<br /> &lt;pre&gt;<br /> /screen -S Region-service -d -m --debug mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> Without the '''--debug''' option, everything seems to be more stable.<br /> <br /> About locales, if you read mantis and threads in opensim-dev / opensim-users, you know that there are issues on system that are not &quot;en_US&quot; or &quot;C&quot; local compliant.<br /> <br /> I have re-setup my server to be full &quot;en_US.UTF8&quot;.<br /> <br /> On my Ubuntu 8.0.4 server :<br /> &lt;pre&gt;<br /> # cat /etc/default/locale<br /> LANG=&quot;en_US.UTF-8&quot;<br /> <br /> # cat /var/lib/locales/supported.d/local<br /> fr_FR.UTF-8 UTF-8<br /> en_US.UTF-8 UTF-8<br /> <br /> # cat /etc/environment<br /> PATH=&quot;/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games&quot;<br /> LANG=&quot;en_US&quot;<br /> LANGUAGE=&quot;en_US&quot;<br /> &lt;/pre&gt;<br /> And maybe you should need :<br /> &lt;pre&gt;<br /> # sudo dpkg-reconfigure locales<br /> &lt;/pre&gt;<br /> <br /> So, the resulting '''screen''' command line options should be :<br /> &lt;pre&gt;<br /> screen -S Region-service -d -m -U mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> This allow me to run OpenSim SVN.6575 without crash during more than 48 hours, and also SVN.6735 ... <br /> <br /> Hope those informations could help peoples.<br /> <br /> Just for your information : <br /> <br /> Here is my '''OpenSim Startup script''' :<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> echo &quot;User-Service...&quot;<br /> /usr/local/bin/screen -S User-service -d -m -U mono OpenSim.Grid.UserServer.exe<br /> sleep 5<br /> echo &quot;Grid-Service...&quot;<br /> /usr/local/bin/screen -S Grid-service -d -m -U mono OpenSim.Grid.GridServer.exe<br /> sleep 5<br /> echo &quot;Asset-Service...&quot;<br /> /usr/local/bin/screen -S Asset-service -d -m -U mono OpenSim.Grid.AssetServer.exe<br /> sleep 10<br /> echo &quot;Inventory-Service...&quot;<br /> /usr/local/bin/screen -S Inventory-service -d -m -U mono OpenSim.Grid.InventoryServer.exe<br /> sleep 5<br /> echo &quot;Region-Service...&quot;<br /> /usr/local/bin/screen -S Region-service -d -m -U mono OpenSim.exe<br /> sleep 5<br /> echo &quot; &quot;<br /> echo &quot; &quot;<br /> /usr/local/bin/screen -list<br /> &lt;/pre&gt;<br /> <br /> Here is also a small script that give you a menu to connect to the '''screen(s)''' sessions :<br /> &lt;pre&gt;<br /> #!/usr/bin/perl<br /> <br /> use strict;<br /> use Term::Menu;<br /> <br /> my $EXIT = 1;<br /> <br /> my $MainTitle = &quot;+-----------------------------------------------------+\n&quot;;<br /> $MainTitle .= &quot;| Connexion SCREEN aux Serveurs OPENSIM |\n&quot;;<br /> $MainTitle .= &quot;| |\n&quot;;<br /> $MainTitle .= &quot;| ( Type CTRL+A+D to exit the Screen Console. ) |\n&quot;;<br /> $MainTitle .= &quot;+-----------------------------------------------------+\n&quot;;<br /> <br /> while ( $EXIT == 1 )<br /> {<br /> <br /> system(&quot;screen -list | grep service &gt; /tmp/osg.services&quot;);<br /> my %LIST = ();<br /> open(IN, &quot;/tmp/osg.services&quot;);<br /> while ( my $i = &lt;IN&gt; )<br /> {<br /> chomp($i);<br /> <br /> $i =~ s/\./#/g;<br /> $i =~ s/\-service\t/#/g;<br /> $i =~ s/\t//g;<br /> $i =~ s/\(//g;<br /> $i =~ s/\)//g;<br /> <br /> my @STATUS = split(/#/, $i);<br /> $LIST{$STATUS[1]} = $STATUS[2];<br /> }<br /> close(IN);<br /> <br /> my %LIST2 = ();<br /> my @indices = ('User', 'Grid', 'Asset', 'Inventory', 'Region');<br /> <br /> foreach my $key ( @indices )<br /> {<br /> # print &quot;$key --&gt; $LIST{$key}\n&quot;;<br /> if ( $LIST{$key} =~ /Attached/ )<br /> {<br /> $LIST2{$key} = &quot;[X]&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{$key} = &quot;[ ]&quot;;<br /> }<br /> }<br /> <br /> if ( $LIST{'User'} =~ /Attached/ )<br /> {<br /> $LIST2{'USER'} = &quot;X&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{'USER'} = &quot;-&quot;;<br /> }<br /> <br /> system ('clear');<br /> my $prompt = new Term::Menu (<br /> spaces =&gt; 3,<br /> aftertext =&gt; &quot;\nChoisir une option : &quot;,<br /> beforetext =&gt; ${MainTitle},<br /> delim =&gt; &quot;. &quot;,<br /> );<br /> <br /> my $SEP = &quot; &quot;;<br /> <br /> my $answer = $prompt-&gt;menu(<br /> osg_user =&gt; [&quot;OpenSim User Server $SEP$LIST2{'User'}&quot;, '1'],<br /> osg_grid =&gt; [&quot;OpenSim Grid Server $SEP$LIST2{'Grid'}&quot;, '2'],<br /> osg_asset =&gt; [&quot;OpenSim Asset Server $SEP$LIST2{'Asset'}&quot;, '3'],<br /> osg_inventory =&gt; [&quot;OpenSim Inventory Server $SEP$LIST2{'Inventory'}&quot;, '4'],<br /> osg_region =&gt; [&quot;OpenSim Region Server $SEP$LIST2{'Region'}\n&quot;, '5'],<br /> osg_shutdown =&gt; [&quot;Shutdown Servers (Manual)&quot;,'6'],<br /> osg_shutdown2 =&gt; [&quot;Shutdown Servers (Hard)\n&quot;,'7'],<br /> quit =&gt; [&quot;Quitter&quot;, 'q'],<br /> );<br /> <br /> if ( &quot;${answer}&quot; eq &quot;quit&quot; )<br /> {<br /> $EXIT = 0;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_user&quot; )<br /> {<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_grid&quot; )<br /> {<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_asset&quot; )<br /> {<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_inventory&quot; )<br /> {<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_region&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown2&quot; )<br /> {<br /> # system(&quot;/OPENSIM/shutdownGrid.py&quot;);<br /> system(&quot;screen -S Region-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Inventory-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Asset-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Grid-service -r -m -X quit&quot;);<br /> system(&quot;screen -S User-service -r -m -X quit&quot;);<br /> $EXIT = 0;<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Regards, <br /> Ursula Matova.</div>

Dale Mahalko http://opensimulator.org/wiki/Troubleshooting 2010-04-04T05:47:39Z

<p>Dale Mahalko: /* Networking and config issues */ page doesn't exist, link instead to Running. Fix page formatting.</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> This page gives any system-specific configuration settings that may be useful, and advice for problems that might be encountered.<br /> __TOC__<br /> {{clear}}<br /> [[Category:Users]]<br /> <br /> == System-specific configuration ==<br /> === CentOS 5 ===<br /> <br /> To install mono and nant, you can use the &quot;Linux Installer for x86&quot; found at http://www.mono-project.com/Downloads.<br /> <br /> SVN can be installed by:<br /> <br /> yum install subversion<br /> <br /> Mono defaults to installing into &lt;tt&gt;/opt&lt;/tt&gt;, so you may have to add this path to your environment variables, for example, in your &lt;tt&gt;~/.bashrc&lt;/tt&gt;:<br /> <br /> export PATH=&quot;/opt/mono-1.2.5/bin:$PATH&quot;<br /> export PKG_CONFIG_PATH=&quot;/opt/mono-1.2.5/lib/pkgconfig:$PKG_CONFIG_PATH&quot;<br /> export MANPATH=&quot;/opt/mono-1.2.5/share/man:$MANPATH&quot;<br /> export LD_LIBRARY_PATH=&quot;/opt/mono-1.2.5/lib:$LD_LIBRARY_PATH&quot;<br /> <br /> After changing &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt;, you should update the dynamic linker cache:<br /> <br /> ldconfig<br /> <br /> You may still encounter the &quot;The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file.&quot; error listed below. In that case, this may fix this:<br /> <br /> yum install glib<br /> <br /> If you are running a firewall as well (i.e., if &lt;tt&gt;iptables -L&lt;/tt&gt; shows a list of ACCEPT and REJECT rules), you'll have to open the necessary ports if you want to access the sim from other machines. For standalone mode:<br /> <br /> iptables -I RH-Firewall-1-INPUT -p tcp --dport 9000 -j ACCEPT<br /> iptables -I RH-Firewall-1-INPUT -p udp --dport 9000 -j ACCEPT<br /> <br /> 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:<br /> sudo yum install libgdiplus<br /> sudo yum install libexif<br /> sudo ln -s /usr/lib64/libgdiplus.so.0 /usr/lib64/libgdiplus.so<br /> ldconfig<br /> <br /> That finally enabled me to run OpenSim without errors, and even connect to other grids.<br /> <br /> === Debian 4.0r0 ===<br /> <br /> If you set your system to use unstable sources, and then install some packages listed below, everything should just work. To use unstable sources, modify your &lt;tt&gt;/etc/apt/sources.list&lt;/tt&gt; file, replacing 'etch' or 'stable' with 'unstable':<br /> <br /> deb ftp://ftp.debian.org/debian/ unstable main<br /> deb-src ftp://ftp.debian.org/debian/ unstable main<br /> <br /> Then update your packages to the new versions:<br /> <br /> apt-get update<br /> apt-get dist-upgrade<br /> <br /> This will probably change a large number of packages, and may break things.<br /> In my experience, however, if you do not use unstable sources then the packages are not up to date enough, and you run into version issues, which lead to two DllNotFoundException errors below appearing in the console output: gdiplus.dll and libopenjpeg-libsl-2.1.2.0.so.<br /> <br /> Once the sources are updated, we need to install the necessary packages to be able to build OpenSim:<br /> <br /> apt-get install subversion mono nant mono-gmcs mono-mjs libmono-microsoft8.0-cil libmono-system-runtime2.0-cil<br /> <br /> If any of these packages are missing, you'll probably encounter one of the errors listed below. However, with these packages, OpenSim should build cleanly.<br /> <br /> Please note: If you are using mysql as storage on unstable you may get the following error:-<br /> <br /> Exception: System.NotSupportedException: CodePage 1252 not supported<br /> at System.Text.Encoding.GetEncoding (Int32 codePage) [0x00000] <br /> <br /> To get it to work, try installing the libmono-i18n2.0-cil package<br /> <br /> apt-get install libmono-i18n2.0-cil<br /> <br /> === Gentoo ===<br /> some Mono dependency &amp; latest Mono itself may use &quot;~x86&quot; masked packages (assuming x86 is your platform, change may be made to reflect your ex:&quot;~amd64&quot; for 64bits). You could check for USE parameter with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge -vp subversion nant mono libgdiplus<br /> <br /> Then install with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge subversion nant mono libgdiplus<br /> <br /> N.B: The ACCEPT_KEYWORDS=&quot;~x86&quot; 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<br /> <br /> === Mac OS X ===<br /> This assumes you're using the universal binary for mono from the [http://www.mono-project.com/ Mono Project] site.<br /> <br /> If you are using OS X 10.4, you should also install X11 from the OS X install CDs.<br /> In OS X 10.5, this is not required.<br /> <br /> If you get errors about the 2.0 framework not being supported, you may need to update your &lt;tt&gt;pkg-config&lt;/tt&gt; path.<br /> I set this in &lt;tt&gt;~/.bash_profile&lt;/tt&gt;:<br /> export PKG_CONFIG_PATH=&quot;/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}&quot;<br /> <br /> == Errors and fixes ==<br /> <br /> === Build workarounds due to non-functionality or bugs: ===<br /> <br /> ==== Disappearing prims due to duplicate UID's ====<br /> 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. This switch is documented in the [[Running#General OpenSim server commands|general server commands]] section. (&lt;nowiki&gt;load-xml &lt;filename&gt; -newUID&lt;/nowiki&gt;). 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.<br /> <br /> ==== Linked objects not scaling/editing properly ====<br /> From Mantis [[http://opensimulator.org/mantis/view.php?id=135 # 135]] and [[http://opensimulator.org/mantis/view.php?id=223 # 223]]: &lt;br /&gt;<br /> Linked objects: while linking/unlinking objects seems to work fine, the editing of single prims inside a linked object doesn't work correctly. You have to check the box &quot;Edit linked parts&quot;, then you can select a single prim and edit it, but in most cases the changes in size- and/or postion-parameters are not accepted and revert immediately to the original ones. It is not completely reproducible, as it may work in some single case though.&lt;br /&gt;<br /> '''Workaround:''' unlink the whole object, make the changes, and relink the whole thing again. &lt;br /&gt; ''note:'' re-scaling unlinked objects in grid mode seems to work better than in standalone. <br /> <br /> &lt;hr&gt;<br /> <br /> === Exception and loss of ode physics (System.EntryPointNotFoundException: dSpaceLockQuery) ===<br /> <br /> The following error is usually caused by using the wrong version of ''libode'':<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [SCENE] [02-01 22:20:40] System.EntryPointNotFoundException: dSpaceLockQuery<br /> :at (wrapper managed-to-native) Ode.NET.d:SpaceLockQuery (intptr)<br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.waitForSpaceUnlock (IntPtr space) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter.AvatarGeomAndBodyCreation (Single npositionX, Single npositionY, Single npositionZ, Single tensor) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter..ctor (System.String avName, OpenSim.Region.Physics.OdePlugin.OdeScene parent_scene, OpenSim.Region.Physics.Manager.PhysicsVector pos) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.AddAvatar (System.String avName, OpenSim.Region.Physics.Manager.PhysicsVector position) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.AddToPhysicalScene () [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.MakeRootAgent (LLVector3 pos, Boolean isFlying) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.Scene.AgentCrossing (UInt64 regionHandle, LLUUID agentID, LLVector3 position, Boolean isFlying) [0x00000]<br /> |}<br /> <br /> First try searching your filesystem to see if you have other copies of the ode physics engine:<br /> find / -name &quot;libode.so&quot;<br /> Then make sure you have the latest version.<br /> <br /> === MySQL connection errors after about 6-8 hours ===<br /> <br /> 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:<br /> <br /> set global wait_timeout=604800;<br /> <br /> === System.DllNotFoundException: gdiplus.dll ===<br /> <br /> First, check to make sure that &lt;tt&gt;libgdiplus.so&lt;/tt&gt; is known to the dynamic linker:<br /> <br /> /sbin/ldconfig -p | grep libgdiplus<br /> <br /> If nothing is found, make sure that the directory libgdiplus.so exists in is either in your &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt; environment variable or listed in a *.conf file (e.g., gdiplus.conf) in /etc/ld.so.conf.d/. Then run &lt;tt&gt;ldconfig&lt;/tt&gt; to update the cache. Then it should be able to find the library.<br /> <br /> 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 OpenSim with debugging information turned on:<br /> <br /> MONO_LOG_LEVEL=debug mono OpenSim.exe<br /> <br /> {It may show errors loading other libraries, like &lt;tt&gt;libexif.so.9&lt;/tt&gt;. In that case, linking to an existing version of the offending library may work:<br /> <br /> ln -s libexif.so.12 libexif.so.9<br /> <br /> 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 <br /> and add the line <br /> &lt;dllmap dll=&quot;gdiplus.dll&quot; target=&quot;/opt/local/lib/libgdiplus.dylib&quot; os=&quot;!windows&quot;/&gt;<br /> <br /> ''(Is there a cleaner solution than this?)''} **see below for alternative/cleaner fix**<br /> <br /> == When installing mono or libgdiplus0 you may get dependency missing libexif.so.9 == <br /> <br /> 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 )<br /> <br /> === The assembly mscorlib.dll was not found or could not be loaded ===<br /> <br /> 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.<br /> <br /> apt-get install nant<br /> <br /> === External Program Failed: /usr/lib/pkgconfig/../../lib/mono/2.0/gmcs.exe === <br /> <br /> This is quickly fixed by retrieving mono-gmcs.<br /> <br /> apt-get install mono-gmcs<br /> <br /> === The type or namespace name JScript does not exist in the namespace Microsoft ===<br /> <br /> Note that it says JScript over and over again. Hint perhaps?<br /> <br /> apt-get install mono-mjs libmono-microsoft8.0-cil<br /> <br /> On Fedora and OpenSUSE, the needed package is &quot;mono-jscript&quot;.<br /> <br /> === The type or namespace name Tcp does not exist in the namespace System.Runtime.Remoting.Channels ===<br /> <br /> This one is taken care of with a quick install:<br /> <br /> apt-get install libmono-system-runtime2.0-cil<br /> <br /> === Missing: libopenjpeg-libsl-2.1.2.0-x86_64.so ===<br /> <br /> You are probably on a 64-bit linux machine and may need to follow these instructions:<br /> <br /> * [[Installing_and_running_on_x86-64 |Installing and running on x86-64 ]]<br /> <br /> === error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file ===<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> apt-get install libglib2.0-0<br /> <br /> === The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file. ===<br /> <br /> This one seems to be fixed by retrieving the apt version of nant.<br /> <br /> apt-get install nant<br /> <br /> This can also be due to &lt;tt&gt;pkg-config&lt;/tt&gt; not being able to locate the &lt;tt&gt;mono.pc&lt;/tt&gt; file. Adding the directory containing this file to the environment variable &lt;tt&gt;PKG_CONFIG_PATH&lt;/tt&gt; may solve this.<br /> <br /> == Networking and config issues ==<br /> <br /> See also the wiki page:<br /> * [[Running]]<br /> <br /> === You are able to log in, but not connect to a Region from a remote client ===<br /> <br /> Look in your OpenSimulator/bin/Regions folder <br /> # Try '''0.0.0.0''' for the internal_ip_address in your region.xml(default.xml) file.&lt;br&gt;(you'll have one of these files for each region you have created)<br /> # '''external_host_name=&quot;127.0.0.1&quot;''' will need to be changed to the accessable DNS name such as &quot;opensim.example-host.com&quot; or &quot;71.6.131.152&quot; (your public accessable ip)<br /> <br /> ==Building OpenSim==<br /> ===I can't find any build files or solution files===<br /> * If you're on Windows, run &lt;tt&gt;runprebuild.bat&lt;/tt&gt; - on Linux/Mac/FreeBSD, run &lt;tt&gt;runprebuild.sh&lt;/tt&gt;<br /> === VS2005 won't open the .sln file ===<br /> * Try running VS2005 C#. You are probably running VS2005 C++. This is a C# project.<br /> <br /> ==Running OpenSim==<br /> === Running OpenSim.exe from a Cygwin shell has access denied for some dll's ===<br /> * Do a '&lt;tt&gt;cd bin&lt;/tt&gt;' followed by '&lt;tt&gt;chmod a+x *&lt;/tt&gt;' to make all dll files executable.<br /> ===I cannot start my sim===<br /> * See [[Configuration]]<br /> <br /> ==Something Has Gone Wrong!==<br /> === I get errors concerning 'owner_uuid' when starting up my grid after updating from svn beyond r3254 ===<br /> When updating to recent revisions after r3254, we are now using the unused owner_uuid. There are some grids whose mysql tables were created during a time when this field was inadvertently removed from the .sql script that initializes the regions table. Logging in to your mysql instance and executing this SQL query to add the missing owner_uuid should solve this issue:<br /> alter table `regions` add column `owner_uuid` varchar(36) default '00000000-0000-0000-0000-000000000000' not null, comment 'Rev.2';<br /> The punctuation around regions and owner_uuid is &quot;grave accent&quot;. The punctuation around the default value and the comment is the single quote. The &quot;grave accent&quot; is the one generally to the left of the One button, under the tilde and the single-quote, is, well, underneath the double quote. I think this matters to mysql.<br /> <br /> === I get errors concerning 'State' when starting up my grid after updating from svn beyond r3786 ===<br /> After r3786, a new 'State' field has been added to the 'primshapes' table on SQLite. This field is used to persist trees and grass.<br /> You may have an empty region at startup, because OpenSim does not find this 'State' field and does not know what to do.<br /> The best is to use SQLiteBrowser or another SQLite table editor (download it at [http://sqlitebrowser.sourceforge.net/ http://sqlitebrowser.sourceforge.net/]) to create the missing field:<br /> alter table primshapes add column State integer default 0<br /> Just launch SQLiteBrowser, use File/Open database, then browse to OpenSim.db file and open it. Then, go to the &quot;Execute SQL&quot; tab, copy/paste the command above in the &quot;SQL string&quot; textbox, then hit the &quot;Execute query&quot; button.<br /> <br /> === I get a timeout during region handshake ===<br /> * Do you have the correct IP in your Regions\* config files?<br /> * Do you have multiple interfaces on the server running OpenSim? OpenSim 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.<br /> <br /> === I cannot connect to my OpenSim ===<br /> * See [[OpenSim: Connecting]]<br /> <br /> ===I can connect but cannot move===<br /> If the client connects but the avatar can only spin in place and not move, then the sim is not correctly configured. It completed the initial login function, but packets are not being exchanged between the client and the sim, probably due to a network configuration error on the sim.<br /> * See [[OpenSim: Configuration]]<br /> <br /> === From time to time my Avatar seems to get stuck ===<br /> Right now there is a bottle neck when syncing prims off to the database. This will cause small (5 - 10 second) apparent hangs of the Avatar, but it will recover fine once the data is synced. It is a known issue based on legacy architecture of some of the data storage code. We hope this will be removed soon.<br /> <br /> === I have problems with viewing the worldmap ===<br /> * This may happen when running OpenSim on a Linux server, both in grid or standalone mode.<br /> * 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...<br /> * Reason: your svn source trunk does not have the correct (or whatever...) &lt;tt&gt;libopenjpeg-libsl&lt;/tt&gt; library.<br /> * Other reason: the file &quot;defaultstripe.png&quot; does not exists in the same OpenSim folder, or is corrupted.<br /> * Solution: get the newest code from libsecondlife (&lt;tt&gt;svn co svn://opensecondlife.org/libsl/trunk&lt;/tt&gt;), '&lt;tt&gt;make&lt;/tt&gt;' manually in the subdir &lt;tt&gt;openjpeg-libsl&lt;/tt&gt;, and copy the resulting &lt;tt&gt;libopenjpeg-libsl-2.1.2.0.so&lt;/tt&gt; into your OpenSim &lt;tt&gt;bin&lt;/tt&gt; subdir, overwriting the existing one.<br /> * Recompile &amp; restart OpenSim<br /> <br /> ==Exceptions on the Console==<br /> This is a list of Exceptions that you may see on the console, what they mean, and if they are a problem.<br /> <br /> ===System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so===<br /> Failed generating terrain map: System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so<br /> at (wrapper managed-to-native) OpenJPEGNet.OpenJPEG:LibslAllocDecoded OpenJPEGNet.OpenJPEG/LibslImage&amp;)<br /> at OpenJPEGNet.OpenJPEG.Encode (System.Byte[] decoded, Int32 width, Int32 height, Int32 components, Boolean lossless) [0x00000]<br /> at OpenJPEGNet.OpenJPEG.EncodeFromImage (System.Drawing.Bitmap bitmap, Boolean lossless) [0x00000]<br /> at OpenSim.Region.Terrain.TerrainEngine.ExportJpegImage (System.String gradientmap) [0x00000]<br /> <br /> 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:<br /> * You have an old processor (libopenjpeg has been compiled with optimizations)<br /> * You are running in 64bit mode (none of the native libs are built for 64bit)<br /> <br /> You can rebuild your own libopenjpeg from source, or run in a compatible environment.<br /> You can do this by:<br /> svn co svn://openmv.org/libsl/libopenmetaverse/trunk libsl<br /> cd libsl/openjpeg-libsl/<br /> make<br /> <br /> then copy libopenjpeg-libsl-2.1.2.0.so into OpenSim bin-folder.<br /> <br /> === System.NullReferenceException at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion ===<br /> [LOGIN END]: XMLRPC Login failed, System.NullReferenceException: Object reference not set to an instance of an object<br /> at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion (OpenSim.Framework.RegionInfo regionInfo, OpenSim.Framework.UserProfileData user, OpenSim.Framework.Communications.LoginResponse response) [0x00000] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:293<br /> at OpenSim.Region.Communications.Local.LocalLoginService.CustomiseResponse (OpenSim.Framework.Communications.LoginResponse response, OpenSim.Framework.UserProfileData theUser, System.String startLocationRequest) [0x00520] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:253<br /> at OpenSim.Framework.Communications.LoginService.XmlRpcLoginMethod (Nwc.XmlRpc.XmlRpcRequest request) [0x00369] in /home/sim/svn/opensim/OpenSim/Framework/Communications/LoginService.cs:252<br /> <br /> Your first startup of OpenSim 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.<br /> <br /> ==Grid Mode==<br /> Note: Grid Mode isn't officially supported yet. As such, you are pretty much on your own if you are trying to get OpenSim up and running in Grid Mode.<br /> <br /> === I start the sim and it doesn't connect to any grid ===<br /> <br /> When OpenSim is first started, it needs configuration.<br /> <br /> * See [[OpenSim: Configuration]].<br /> <br /> === I start the OpenSim.Grid.UserServer.exe and it gives an error===<br /> If this error is access denied for &lt;tt&gt;username@localhost&lt;/tt&gt;, the mysql database is not set up.<br /> It will print some text and wait for input - either an enter to accept a default value, or another value you can supply.<br /> * See [[OpenSim: Configuration]].<br /> <br /> === I want to run my own Local Grid but one or more servers fail to start===<br /> * Be sure that you're able to start &lt;tt&gt;OpenSim.exe&lt;/tt&gt; alone, in Standalone mode, and to be able to login.<br /> * Start the servers in the correct UGAS order and answer the questions as recommended (see [[OpenSim: Configuration]]).<br /> * Set all the external URI's to the correct IP: 127.0.0.1 if running on your local machine, or aaa.bbb.ccc.ddd if running on a remote server.<br /> * Check again all the &lt;tt&gt;*.xml&lt;/tt&gt; configuration files for any wrong settings or typing errors...!<br /> * Don't forget to connect with your SL-viewer to port 8002 (Grid User-Server) instead of 9000 (Standalone OpenSim-Server).<br /> * Delete all &lt;tt&gt;*.xml&lt;/tt&gt; and &lt;tt&gt;*.yap&lt;/tt&gt; files in the &lt;tt&gt;bin&lt;/tt&gt; directory if you want to run a full reconfiguration again.<br /> <br /> === I get a bunch of asset not found errors, while connected to a online grid, and my inventory doesn't seem to work right===<br /> *Make sure your opensim.ini has ' asset_database = &quot;grid&quot; ' otherwise it will not work correctly.<br /> <br /> === My grid works fine with one user but when two users login in the same time both get stuck ===<br /> * Make sure you have export MONO_THREADS_PER_CPU=&quot;100&quot; in your environment<br /> <br /> === After ~20 minutes my region starts to take 100% cpu and region(s) hang ===<br /> * If you have mono 1.9.1 or lower upgrade to mono 2.2.<br /> <br /> ==Hypergrid==<br /> ===After starting OpenSim with Hypergrid enabled my inventory wont load!===<br /> *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.<br /> *Check the XML config files for your UGAIM servers to make sure that everything is running off of a publicly accessible IP address.<br /> **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.<br /> <br /> 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.<br /> <br /> &lt;div align = center&gt;&lt;B&gt;!!!!WARNING!!!! - Be smart! Always make a backup of your databases before making any changes to OpenSim! - !!!!WARNING!!!!&lt;/b&gt;&lt;/div&gt;<br /> &lt;pre&gt;<br /> update users set userInventoryURI=&quot;http://new.UGAIM.address:8004&quot; where userInventoryURI = &quot;http://old.UGAIM.address:8004&quot;;<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> update users set userAssetURI=&quot;http://new.UGAIM.address:8003&quot; where userAssetURI = &quot;http://old.UGAIM.address:8003&quot;;<br /> &lt;/pre&gt;<br /> *If you're running in standalone mode... - Anyone familiar with standalone want to fill this in? -<br /> [[Category:Users]]<br /> <br /> == ScriptEngine Issues ==<br /> === Got &quot;Primitive: Error compiling script: unknown char: . error&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you could have this error :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> unknown char: .<br /> &lt;/pre&gt;<br /> And on the console :<br /> &lt;pre&gt;<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Unloading script<br /> 11:06:37 - Exception in MaintenanceLoopThread. Thread will recover after 5 sec throttle. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.<br /> at System.Collections.Generic.Dictionary`2[OpenSim.Region.ScriptEngine.Interfaces.IEventReceiver,OpenSim.Region.ScriptEngine.Shared.Api.Plugins.Dataserver].get_Item (IEventReceiver key) [0x00000]<br /> at OpenSim.Region.ScriptEngine.Shared.Api.AsyncCommandManager.RemoveScript (IEventReceiver engine, UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager._StopScript (UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager.DoScriptLoadUnload () [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.MaintenanceThread.MaintenanceLoop () [0x00000]<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Loading script<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: ScriptManager StartScript: localID: 720001, itemID: 88c9d28c-6004-4609-a707-717190de044a<br /> 11:06:37 - [Compiler]: Compiled new assembly for fad15951-f9aa-493f-be68-2aaf5ff8a3c9<br /> 11:06:37 - [SCRIPT]: Compiled assetID fad15951-f9aa-493f-be68-2aaf5ff8a3c9: ScriptEngines/a83150da-1ab1-11dd-89fb-0014853ee9da/CommonCompiler_compiled_fad15951-f9aa-493f-be68-2aaf5ff8a3c9.dll<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: AppDomain Loading: OpenSim.Region.ScriptEngine.Shared, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null<br /> &lt;/pre&gt;<br /> This happens on '''linux''' when your locales are not set to default ( &quot;C&quot; ).<br /> * You could refer to [http://opensimulator.org/mantis/view.php?id=2088 Mantis #2088] and [http://opensimulator.org/mantis/view.php?id=2015 Mantis #2015] for a workaround to run opensim.<br /> &lt;pre&gt;<br /> env LANG=C mono --debug OpenSim.exe<br /> &lt;/pre&gt;<br /> * You could also change your locale setup. Here is what I use in my '.bash_profile' :<br /> &lt;pre&gt;<br /> export LC_ALL=C<br /> export LANG=C<br /> &lt;/pre&gt;<br /> I know it's a ugly way to setup locales on a linux box, but it works fine on my '''Linux From Scratch''' box.<br /> <br /> '''Rq''': I saw Melanie has corrected some parts of the source code a few weeks ago to avoid such problems.<br /> <br /> === Get &quot;Primitive: Error compiling script: ApplicationName='gmcs', ...&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you have an error something like :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> ApplicationName='gmcs', CommandLine='/target:library /debug+ /optimize- /out:<br /> &quot;ScriptEngines/430c29d0-c5c6-11dd-ad8b-0800200c9a66/CommonCompiler_compiled_fbe5e682-afae-4f1a-805b-0125031101f7.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.Api.Runtime.dll&quot; -- <br /> &quot;/tmp/11b81aac/594d02ce.0.cs&quot; ', CurrentDirectory=''<br /> &lt;/pre&gt;<br /> <br /> Other features include &quot;Touch&quot; being disabled on the right click menu wheel.<br /> <br /> You might have a broken mono install (i.e. discovered as mono but not gmcs installed on a Ubuntu 8.10 Intrepid machine.)<br /> <br /> Check mono-gmcs (sudo apt-get install mono-gmcs) is correctly installed.<br /> <br /> == Locales Issues ==<br /> Well, some of us, OpenSim users, ran into random crash of the OpenSim Region server in grid mode ... <br /> <br /> I have made many tests to find a solution about that problem.<br /> <br /> I first ran into this problem with OpenSIM SVN.6660 ... Even if I have no users connected, my OpenSim region server randomly crash ( after 1 hour, or 5 hours, ... ).<br /> <br /> My first idea was to upgrade to the latest SVN release, no chance, same problem. So I made a test with a previous SVN release ( SVN.6575 ) which is running fine on another server ( same OS, same parameters, same mono release, ... ) : No chance, same problem.<br /> <br /> Then, I tried to play with locales, recompile the '''screen''' unix command line utility I use to run my servers, ... No chance again.<br /> <br /> So, I checked the memory usage on my Server, and I discovered that with the last SVN release, the amount of memory needed to run OpenSim server in multi-region/grid mode increased :) ... So, I have tuned my MySQL server to use less memory. Was better, but my OpenSim region server still randomly crash ( but could stay alive longer than before ).<br /> <br /> Then, trying to play with the '''screen''' command line options ... And all my tests shows that the '''--debug''' option impact the stability of the server.<br /> <br /> Initially, I used such command line to run OpenSim :<br /> &lt;pre&gt;<br /> /screen -S Region-service -d -m --debug mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> Without the '''--debug''' option, everything seems to be more stable.<br /> <br /> About locales, if you read mantis and threads in opensim-dev / opensim-users, you know that there are issues on system that are not &quot;en_US&quot; or &quot;C&quot; local compliant.<br /> <br /> I have re-setup my server to be full &quot;en_US.UTF8&quot;.<br /> <br /> On my Ubuntu 8.0.4 server :<br /> &lt;pre&gt;<br /> # cat /etc/default/locale<br /> LANG=&quot;en_US.UTF-8&quot;<br /> <br /> # cat /var/lib/locales/supported.d/local<br /> fr_FR.UTF-8 UTF-8<br /> en_US.UTF-8 UTF-8<br /> <br /> # cat /etc/environment<br /> PATH=&quot;/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games&quot;<br /> LANG=&quot;en_US&quot;<br /> LANGUAGE=&quot;en_US&quot;<br /> &lt;/pre&gt;<br /> And maybe you should need :<br /> &lt;pre&gt;<br /> # sudo dpkg-reconfigure locales<br /> &lt;/pre&gt;<br /> <br /> So, the resulting '''screen''' command line options should be :<br /> &lt;pre&gt;<br /> screen -S Region-service -d -m -U mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> This allow me to run OpenSim SVN.6575 without crash during more than 48 hours, and also SVN.6735 ... <br /> <br /> Hope those informations could help peoples.<br /> <br /> Just for your information : <br /> <br /> Here is my '''OpenSim Startup script''' :<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> echo &quot;User-Service...&quot;<br /> /usr/local/bin/screen -S User-service -d -m -U mono OpenSim.Grid.UserServer.exe<br /> sleep 5<br /> echo &quot;Grid-Service...&quot;<br /> /usr/local/bin/screen -S Grid-service -d -m -U mono OpenSim.Grid.GridServer.exe<br /> sleep 5<br /> echo &quot;Asset-Service...&quot;<br /> /usr/local/bin/screen -S Asset-service -d -m -U mono OpenSim.Grid.AssetServer.exe<br /> sleep 10<br /> echo &quot;Inventory-Service...&quot;<br /> /usr/local/bin/screen -S Inventory-service -d -m -U mono OpenSim.Grid.InventoryServer.exe<br /> sleep 5<br /> echo &quot;Region-Service...&quot;<br /> /usr/local/bin/screen -S Region-service -d -m -U mono OpenSim.exe<br /> sleep 5<br /> echo &quot; &quot;<br /> echo &quot; &quot;<br /> /usr/local/bin/screen -list<br /> &lt;/pre&gt;<br /> <br /> Here is also a small script that give you a menu to connect to the '''screen(s)''' sessions :<br /> &lt;pre&gt;<br /> #!/usr/bin/perl<br /> <br /> use strict;<br /> use Term::Menu;<br /> <br /> my $EXIT = 1;<br /> <br /> my $MainTitle = &quot;+-----------------------------------------------------+\n&quot;;<br /> $MainTitle .= &quot;| Connexion SCREEN aux Serveurs OPENSIM |\n&quot;;<br /> $MainTitle .= &quot;| |\n&quot;;<br /> $MainTitle .= &quot;| ( Type CTRL+A+D to exit the Screen Console. ) |\n&quot;;<br /> $MainTitle .= &quot;+-----------------------------------------------------+\n&quot;;<br /> <br /> while ( $EXIT == 1 )<br /> {<br /> <br /> system(&quot;screen -list | grep service &gt; /tmp/osg.services&quot;);<br /> my %LIST = ();<br /> open(IN, &quot;/tmp/osg.services&quot;);<br /> while ( my $i = &lt;IN&gt; )<br /> {<br /> chomp($i);<br /> <br /> $i =~ s/\./#/g;<br /> $i =~ s/\-service\t/#/g;<br /> $i =~ s/\t//g;<br /> $i =~ s/\(//g;<br /> $i =~ s/\)//g;<br /> <br /> my @STATUS = split(/#/, $i);<br /> $LIST{$STATUS[1]} = $STATUS[2];<br /> }<br /> close(IN);<br /> <br /> my %LIST2 = ();<br /> my @indices = ('User', 'Grid', 'Asset', 'Inventory', 'Region');<br /> <br /> foreach my $key ( @indices )<br /> {<br /> # print &quot;$key --&gt; $LIST{$key}\n&quot;;<br /> if ( $LIST{$key} =~ /Attached/ )<br /> {<br /> $LIST2{$key} = &quot;[X]&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{$key} = &quot;[ ]&quot;;<br /> }<br /> }<br /> <br /> if ( $LIST{'User'} =~ /Attached/ )<br /> {<br /> $LIST2{'USER'} = &quot;X&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{'USER'} = &quot;-&quot;;<br /> }<br /> <br /> system ('clear');<br /> my $prompt = new Term::Menu (<br /> spaces =&gt; 3,<br /> aftertext =&gt; &quot;\nChoisir une option : &quot;,<br /> beforetext =&gt; ${MainTitle},<br /> delim =&gt; &quot;. &quot;,<br /> );<br /> <br /> my $SEP = &quot; &quot;;<br /> <br /> my $answer = $prompt-&gt;menu(<br /> osg_user =&gt; [&quot;OpenSim User Server $SEP$LIST2{'User'}&quot;, '1'],<br /> osg_grid =&gt; [&quot;OpenSim Grid Server $SEP$LIST2{'Grid'}&quot;, '2'],<br /> osg_asset =&gt; [&quot;OpenSim Asset Server $SEP$LIST2{'Asset'}&quot;, '3'],<br /> osg_inventory =&gt; [&quot;OpenSim Inventory Server $SEP$LIST2{'Inventory'}&quot;, '4'],<br /> osg_region =&gt; [&quot;OpenSim Region Server $SEP$LIST2{'Region'}\n&quot;, '5'],<br /> osg_shutdown =&gt; [&quot;Shutdown Servers (Manual)&quot;,'6'],<br /> osg_shutdown2 =&gt; [&quot;Shutdown Servers (Hard)\n&quot;,'7'],<br /> quit =&gt; [&quot;Quitter&quot;, 'q'],<br /> );<br /> <br /> if ( &quot;${answer}&quot; eq &quot;quit&quot; )<br /> {<br /> $EXIT = 0;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_user&quot; )<br /> {<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_grid&quot; )<br /> {<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_asset&quot; )<br /> {<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_inventory&quot; )<br /> {<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_region&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown2&quot; )<br /> {<br /> # system(&quot;/OPENSIM/shutdownGrid.py&quot;);<br /> system(&quot;screen -S Region-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Inventory-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Asset-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Grid-service -r -m -X quit&quot;);<br /> system(&quot;screen -S User-service -r -m -X quit&quot;);<br /> $EXIT = 0;<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Regards, <br /> Ursula Matova.</div>

Dale Mahalko http://opensimulator.org/wiki/Troubleshooting 2010-04-04T05:41:11Z

<p>Dale Mahalko: /* Missing: libopenjpeg-libsl-2.1.2.0-x86_64.so */ reformat layout</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> This page gives any system-specific configuration settings that may be useful, and advice for problems that might be encountered.<br /> __TOC__<br /> {{clear}}<br /> [[Category:Users]]<br /> <br /> == System-specific configuration ==<br /> === CentOS 5 ===<br /> <br /> To install mono and nant, you can use the &quot;Linux Installer for x86&quot; found at http://www.mono-project.com/Downloads.<br /> <br /> SVN can be installed by:<br /> <br /> yum install subversion<br /> <br /> Mono defaults to installing into &lt;tt&gt;/opt&lt;/tt&gt;, so you may have to add this path to your environment variables, for example, in your &lt;tt&gt;~/.bashrc&lt;/tt&gt;:<br /> <br /> export PATH=&quot;/opt/mono-1.2.5/bin:$PATH&quot;<br /> export PKG_CONFIG_PATH=&quot;/opt/mono-1.2.5/lib/pkgconfig:$PKG_CONFIG_PATH&quot;<br /> export MANPATH=&quot;/opt/mono-1.2.5/share/man:$MANPATH&quot;<br /> export LD_LIBRARY_PATH=&quot;/opt/mono-1.2.5/lib:$LD_LIBRARY_PATH&quot;<br /> <br /> After changing &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt;, you should update the dynamic linker cache:<br /> <br /> ldconfig<br /> <br /> You may still encounter the &quot;The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file.&quot; error listed below. In that case, this may fix this:<br /> <br /> yum install glib<br /> <br /> If you are running a firewall as well (i.e., if &lt;tt&gt;iptables -L&lt;/tt&gt; shows a list of ACCEPT and REJECT rules), you'll have to open the necessary ports if you want to access the sim from other machines. For standalone mode:<br /> <br /> iptables -I RH-Firewall-1-INPUT -p tcp --dport 9000 -j ACCEPT<br /> iptables -I RH-Firewall-1-INPUT -p udp --dport 9000 -j ACCEPT<br /> <br /> 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:<br /> sudo yum install libgdiplus<br /> sudo yum install libexif<br /> sudo ln -s /usr/lib64/libgdiplus.so.0 /usr/lib64/libgdiplus.so<br /> ldconfig<br /> <br /> That finally enabled me to run OpenSim without errors, and even connect to other grids.<br /> <br /> === Debian 4.0r0 ===<br /> <br /> If you set your system to use unstable sources, and then install some packages listed below, everything should just work. To use unstable sources, modify your &lt;tt&gt;/etc/apt/sources.list&lt;/tt&gt; file, replacing 'etch' or 'stable' with 'unstable':<br /> <br /> deb ftp://ftp.debian.org/debian/ unstable main<br /> deb-src ftp://ftp.debian.org/debian/ unstable main<br /> <br /> Then update your packages to the new versions:<br /> <br /> apt-get update<br /> apt-get dist-upgrade<br /> <br /> This will probably change a large number of packages, and may break things.<br /> In my experience, however, if you do not use unstable sources then the packages are not up to date enough, and you run into version issues, which lead to two DllNotFoundException errors below appearing in the console output: gdiplus.dll and libopenjpeg-libsl-2.1.2.0.so.<br /> <br /> Once the sources are updated, we need to install the necessary packages to be able to build OpenSim:<br /> <br /> apt-get install subversion mono nant mono-gmcs mono-mjs libmono-microsoft8.0-cil libmono-system-runtime2.0-cil<br /> <br /> If any of these packages are missing, you'll probably encounter one of the errors listed below. However, with these packages, OpenSim should build cleanly.<br /> <br /> Please note: If you are using mysql as storage on unstable you may get the following error:-<br /> <br /> Exception: System.NotSupportedException: CodePage 1252 not supported<br /> at System.Text.Encoding.GetEncoding (Int32 codePage) [0x00000] <br /> <br /> To get it to work, try installing the libmono-i18n2.0-cil package<br /> <br /> apt-get install libmono-i18n2.0-cil<br /> <br /> === Gentoo ===<br /> some Mono dependency &amp; latest Mono itself may use &quot;~x86&quot; masked packages (assuming x86 is your platform, change may be made to reflect your ex:&quot;~amd64&quot; for 64bits). You could check for USE parameter with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge -vp subversion nant mono libgdiplus<br /> <br /> Then install with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge subversion nant mono libgdiplus<br /> <br /> N.B: The ACCEPT_KEYWORDS=&quot;~x86&quot; 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<br /> <br /> === Mac OS X ===<br /> This assumes you're using the universal binary for mono from the [http://www.mono-project.com/ Mono Project] site.<br /> <br /> If you are using OS X 10.4, you should also install X11 from the OS X install CDs.<br /> In OS X 10.5, this is not required.<br /> <br /> If you get errors about the 2.0 framework not being supported, you may need to update your &lt;tt&gt;pkg-config&lt;/tt&gt; path.<br /> I set this in &lt;tt&gt;~/.bash_profile&lt;/tt&gt;:<br /> export PKG_CONFIG_PATH=&quot;/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}&quot;<br /> <br /> == Errors and fixes ==<br /> <br /> === Build workarounds due to non-functionality or bugs: ===<br /> <br /> ==== Disappearing prims due to duplicate UID's ====<br /> 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. This switch is documented in the [[Running#General OpenSim server commands|general server commands]] section. (&lt;nowiki&gt;load-xml &lt;filename&gt; -newUID&lt;/nowiki&gt;). 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.<br /> <br /> ==== Linked objects not scaling/editing properly ====<br /> From Mantis [[http://opensimulator.org/mantis/view.php?id=135 # 135]] and [[http://opensimulator.org/mantis/view.php?id=223 # 223]]: &lt;br /&gt;<br /> Linked objects: while linking/unlinking objects seems to work fine, the editing of single prims inside a linked object doesn't work correctly. You have to check the box &quot;Edit linked parts&quot;, then you can select a single prim and edit it, but in most cases the changes in size- and/or postion-parameters are not accepted and revert immediately to the original ones. It is not completely reproducible, as it may work in some single case though.&lt;br /&gt;<br /> '''Workaround:''' unlink the whole object, make the changes, and relink the whole thing again. &lt;br /&gt; ''note:'' re-scaling unlinked objects in grid mode seems to work better than in standalone. <br /> <br /> &lt;hr&gt;<br /> <br /> === Exception and loss of ode physics (System.EntryPointNotFoundException: dSpaceLockQuery) ===<br /> <br /> The following error is usually caused by using the wrong version of ''libode'':<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [SCENE] [02-01 22:20:40] System.EntryPointNotFoundException: dSpaceLockQuery<br /> :at (wrapper managed-to-native) Ode.NET.d:SpaceLockQuery (intptr)<br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.waitForSpaceUnlock (IntPtr space) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter.AvatarGeomAndBodyCreation (Single npositionX, Single npositionY, Single npositionZ, Single tensor) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter..ctor (System.String avName, OpenSim.Region.Physics.OdePlugin.OdeScene parent_scene, OpenSim.Region.Physics.Manager.PhysicsVector pos) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.AddAvatar (System.String avName, OpenSim.Region.Physics.Manager.PhysicsVector position) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.AddToPhysicalScene () [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.MakeRootAgent (LLVector3 pos, Boolean isFlying) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.Scene.AgentCrossing (UInt64 regionHandle, LLUUID agentID, LLVector3 position, Boolean isFlying) [0x00000]<br /> |}<br /> <br /> First try searching your filesystem to see if you have other copies of the ode physics engine:<br /> find / -name &quot;libode.so&quot;<br /> Then make sure you have the latest version.<br /> <br /> === MySQL connection errors after about 6-8 hours ===<br /> <br /> 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:<br /> <br /> set global wait_timeout=604800;<br /> <br /> === System.DllNotFoundException: gdiplus.dll ===<br /> <br /> First, check to make sure that &lt;tt&gt;libgdiplus.so&lt;/tt&gt; is known to the dynamic linker:<br /> <br /> /sbin/ldconfig -p | grep libgdiplus<br /> <br /> If nothing is found, make sure that the directory libgdiplus.so exists in is either in your &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt; environment variable or listed in a *.conf file (e.g., gdiplus.conf) in /etc/ld.so.conf.d/. Then run &lt;tt&gt;ldconfig&lt;/tt&gt; to update the cache. Then it should be able to find the library.<br /> <br /> 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 OpenSim with debugging information turned on:<br /> <br /> MONO_LOG_LEVEL=debug mono OpenSim.exe<br /> <br /> {It may show errors loading other libraries, like &lt;tt&gt;libexif.so.9&lt;/tt&gt;. In that case, linking to an existing version of the offending library may work:<br /> <br /> ln -s libexif.so.12 libexif.so.9<br /> <br /> 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 <br /> and add the line <br /> &lt;dllmap dll=&quot;gdiplus.dll&quot; target=&quot;/opt/local/lib/libgdiplus.dylib&quot; os=&quot;!windows&quot;/&gt;<br /> <br /> ''(Is there a cleaner solution than this?)''} **see below for alternative/cleaner fix**<br /> <br /> == When installing mono or libgdiplus0 you may get dependency missing libexif.so.9 == <br /> <br /> 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 )<br /> <br /> === The assembly mscorlib.dll was not found or could not be loaded ===<br /> <br /> 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.<br /> <br /> apt-get install nant<br /> <br /> === External Program Failed: /usr/lib/pkgconfig/../../lib/mono/2.0/gmcs.exe === <br /> <br /> This is quickly fixed by retrieving mono-gmcs.<br /> <br /> apt-get install mono-gmcs<br /> <br /> === The type or namespace name JScript does not exist in the namespace Microsoft ===<br /> <br /> Note that it says JScript over and over again. Hint perhaps?<br /> <br /> apt-get install mono-mjs libmono-microsoft8.0-cil<br /> <br /> On Fedora and OpenSUSE, the needed package is &quot;mono-jscript&quot;.<br /> <br /> === The type or namespace name Tcp does not exist in the namespace System.Runtime.Remoting.Channels ===<br /> <br /> This one is taken care of with a quick install:<br /> <br /> apt-get install libmono-system-runtime2.0-cil<br /> <br /> === Missing: libopenjpeg-libsl-2.1.2.0-x86_64.so ===<br /> <br /> You are probably on a 64-bit linux machine and may need to follow these instructions:<br /> <br /> * [[Installing_and_running_on_x86-64 |Installing and running on x86-64 ]]<br /> <br /> === error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file ===<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> apt-get install libglib2.0-0<br /> <br /> === The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file. ===<br /> <br /> This one seems to be fixed by retrieving the apt version of nant.<br /> <br /> apt-get install nant<br /> <br /> This can also be due to &lt;tt&gt;pkg-config&lt;/tt&gt; not being able to locate the &lt;tt&gt;mono.pc&lt;/tt&gt; file. Adding the directory containing this file to the environment variable &lt;tt&gt;PKG_CONFIG_PATH&lt;/tt&gt; may solve this.<br /> <br /> == Networking and config issues ==<br /> [[OpenSim:Running |See Running section]]<br /> <br /> === You are able to log in, but not connect to a Region from a remote client ===<br /> <br /> Look in your OpenSimulator/bin/Regions folder <br /> 1) Try 0.0.0.0 for the internal_ip_address in your region.xml(default.xml) file<br /> (you'll have one of those files *per* region you've created)<br /> 2) external_host_name=&quot;127.0.0.1&quot; will need to be changed to the accessable DNS name<br /> such as &quot;opensim.example-host.com&quot; or &quot;71.6.131.152&quot; (your public accessable ip)<br /> <br /> ==Building OpenSim==<br /> ===I can't find any build files or solution files===<br /> * If you're on Windows, run &lt;tt&gt;runprebuild.bat&lt;/tt&gt; - on Linux/Mac/FreeBSD, run &lt;tt&gt;runprebuild.sh&lt;/tt&gt;<br /> === VS2005 won't open the .sln file ===<br /> * Try running VS2005 C#. You are probably running VS2005 C++. This is a C# project.<br /> <br /> ==Running OpenSim==<br /> === Running OpenSim.exe from a Cygwin shell has access denied for some dll's ===<br /> * Do a '&lt;tt&gt;cd bin&lt;/tt&gt;' followed by '&lt;tt&gt;chmod a+x *&lt;/tt&gt;' to make all dll files executable.<br /> ===I cannot start my sim===<br /> * See [[Configuration]]<br /> <br /> ==Something Has Gone Wrong!==<br /> === I get errors concerning 'owner_uuid' when starting up my grid after updating from svn beyond r3254 ===<br /> When updating to recent revisions after r3254, we are now using the unused owner_uuid. There are some grids whose mysql tables were created during a time when this field was inadvertently removed from the .sql script that initializes the regions table. Logging in to your mysql instance and executing this SQL query to add the missing owner_uuid should solve this issue:<br /> alter table `regions` add column `owner_uuid` varchar(36) default '00000000-0000-0000-0000-000000000000' not null, comment 'Rev.2';<br /> The punctuation around regions and owner_uuid is &quot;grave accent&quot;. The punctuation around the default value and the comment is the single quote. The &quot;grave accent&quot; is the one generally to the left of the One button, under the tilde and the single-quote, is, well, underneath the double quote. I think this matters to mysql.<br /> <br /> === I get errors concerning 'State' when starting up my grid after updating from svn beyond r3786 ===<br /> After r3786, a new 'State' field has been added to the 'primshapes' table on SQLite. This field is used to persist trees and grass.<br /> You may have an empty region at startup, because OpenSim does not find this 'State' field and does not know what to do.<br /> The best is to use SQLiteBrowser or another SQLite table editor (download it at [http://sqlitebrowser.sourceforge.net/ http://sqlitebrowser.sourceforge.net/]) to create the missing field:<br /> alter table primshapes add column State integer default 0<br /> Just launch SQLiteBrowser, use File/Open database, then browse to OpenSim.db file and open it. Then, go to the &quot;Execute SQL&quot; tab, copy/paste the command above in the &quot;SQL string&quot; textbox, then hit the &quot;Execute query&quot; button.<br /> <br /> === I get a timeout during region handshake ===<br /> * Do you have the correct IP in your Regions\* config files?<br /> * Do you have multiple interfaces on the server running OpenSim? OpenSim 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.<br /> <br /> === I cannot connect to my OpenSim ===<br /> * See [[OpenSim: Connecting]]<br /> <br /> ===I can connect but cannot move===<br /> If the client connects but the avatar can only spin in place and not move, then the sim is not correctly configured. It completed the initial login function, but packets are not being exchanged between the client and the sim, probably due to a network configuration error on the sim.<br /> * See [[OpenSim: Configuration]]<br /> <br /> === From time to time my Avatar seems to get stuck ===<br /> Right now there is a bottle neck when syncing prims off to the database. This will cause small (5 - 10 second) apparent hangs of the Avatar, but it will recover fine once the data is synced. It is a known issue based on legacy architecture of some of the data storage code. We hope this will be removed soon.<br /> <br /> === I have problems with viewing the worldmap ===<br /> * This may happen when running OpenSim on a Linux server, both in grid or standalone mode.<br /> * 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...<br /> * Reason: your svn source trunk does not have the correct (or whatever...) &lt;tt&gt;libopenjpeg-libsl&lt;/tt&gt; library.<br /> * Other reason: the file &quot;defaultstripe.png&quot; does not exists in the same OpenSim folder, or is corrupted.<br /> * Solution: get the newest code from libsecondlife (&lt;tt&gt;svn co svn://opensecondlife.org/libsl/trunk&lt;/tt&gt;), '&lt;tt&gt;make&lt;/tt&gt;' manually in the subdir &lt;tt&gt;openjpeg-libsl&lt;/tt&gt;, and copy the resulting &lt;tt&gt;libopenjpeg-libsl-2.1.2.0.so&lt;/tt&gt; into your OpenSim &lt;tt&gt;bin&lt;/tt&gt; subdir, overwriting the existing one.<br /> * Recompile &amp; restart OpenSim<br /> <br /> ==Exceptions on the Console==<br /> This is a list of Exceptions that you may see on the console, what they mean, and if they are a problem.<br /> <br /> ===System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so===<br /> Failed generating terrain map: System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so<br /> at (wrapper managed-to-native) OpenJPEGNet.OpenJPEG:LibslAllocDecoded OpenJPEGNet.OpenJPEG/LibslImage&amp;)<br /> at OpenJPEGNet.OpenJPEG.Encode (System.Byte[] decoded, Int32 width, Int32 height, Int32 components, Boolean lossless) [0x00000]<br /> at OpenJPEGNet.OpenJPEG.EncodeFromImage (System.Drawing.Bitmap bitmap, Boolean lossless) [0x00000]<br /> at OpenSim.Region.Terrain.TerrainEngine.ExportJpegImage (System.String gradientmap) [0x00000]<br /> <br /> 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:<br /> * You have an old processor (libopenjpeg has been compiled with optimizations)<br /> * You are running in 64bit mode (none of the native libs are built for 64bit)<br /> <br /> You can rebuild your own libopenjpeg from source, or run in a compatible environment.<br /> You can do this by:<br /> svn co svn://openmv.org/libsl/libopenmetaverse/trunk libsl<br /> cd libsl/openjpeg-libsl/<br /> make<br /> <br /> then copy libopenjpeg-libsl-2.1.2.0.so into OpenSim bin-folder.<br /> <br /> === System.NullReferenceException at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion ===<br /> [LOGIN END]: XMLRPC Login failed, System.NullReferenceException: Object reference not set to an instance of an object<br /> at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion (OpenSim.Framework.RegionInfo regionInfo, OpenSim.Framework.UserProfileData user, OpenSim.Framework.Communications.LoginResponse response) [0x00000] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:293<br /> at OpenSim.Region.Communications.Local.LocalLoginService.CustomiseResponse (OpenSim.Framework.Communications.LoginResponse response, OpenSim.Framework.UserProfileData theUser, System.String startLocationRequest) [0x00520] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:253<br /> at OpenSim.Framework.Communications.LoginService.XmlRpcLoginMethod (Nwc.XmlRpc.XmlRpcRequest request) [0x00369] in /home/sim/svn/opensim/OpenSim/Framework/Communications/LoginService.cs:252<br /> <br /> Your first startup of OpenSim 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.<br /> <br /> ==Grid Mode==<br /> Note: Grid Mode isn't officially supported yet. As such, you are pretty much on your own if you are trying to get OpenSim up and running in Grid Mode.<br /> <br /> === I start the sim and it doesn't connect to any grid ===<br /> <br /> When OpenSim is first started, it needs configuration.<br /> <br /> * See [[OpenSim: Configuration]].<br /> <br /> === I start the OpenSim.Grid.UserServer.exe and it gives an error===<br /> If this error is access denied for &lt;tt&gt;username@localhost&lt;/tt&gt;, the mysql database is not set up.<br /> It will print some text and wait for input - either an enter to accept a default value, or another value you can supply.<br /> * See [[OpenSim: Configuration]].<br /> <br /> === I want to run my own Local Grid but one or more servers fail to start===<br /> * Be sure that you're able to start &lt;tt&gt;OpenSim.exe&lt;/tt&gt; alone, in Standalone mode, and to be able to login.<br /> * Start the servers in the correct UGAS order and answer the questions as recommended (see [[OpenSim: Configuration]]).<br /> * Set all the external URI's to the correct IP: 127.0.0.1 if running on your local machine, or aaa.bbb.ccc.ddd if running on a remote server.<br /> * Check again all the &lt;tt&gt;*.xml&lt;/tt&gt; configuration files for any wrong settings or typing errors...!<br /> * Don't forget to connect with your SL-viewer to port 8002 (Grid User-Server) instead of 9000 (Standalone OpenSim-Server).<br /> * Delete all &lt;tt&gt;*.xml&lt;/tt&gt; and &lt;tt&gt;*.yap&lt;/tt&gt; files in the &lt;tt&gt;bin&lt;/tt&gt; directory if you want to run a full reconfiguration again.<br /> <br /> === I get a bunch of asset not found errors, while connected to a online grid, and my inventory doesn't seem to work right===<br /> *Make sure your opensim.ini has ' asset_database = &quot;grid&quot; ' otherwise it will not work correctly.<br /> <br /> === My grid works fine with one user but when two users login in the same time both get stuck ===<br /> * Make sure you have export MONO_THREADS_PER_CPU=&quot;100&quot; in your environment<br /> <br /> === After ~20 minutes my region starts to take 100% cpu and region(s) hang ===<br /> * If you have mono 1.9.1 or lower upgrade to mono 2.2.<br /> <br /> ==Hypergrid==<br /> ===After starting OpenSim with Hypergrid enabled my inventory wont load!===<br /> *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.<br /> *Check the XML config files for your UGAIM servers to make sure that everything is running off of a publicly accessible IP address.<br /> **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.<br /> <br /> 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.<br /> <br /> &lt;div align = center&gt;&lt;B&gt;!!!!WARNING!!!! - Be smart! Always make a backup of your databases before making any changes to OpenSim! - !!!!WARNING!!!!&lt;/b&gt;&lt;/div&gt;<br /> &lt;pre&gt;<br /> update users set userInventoryURI=&quot;http://new.UGAIM.address:8004&quot; where userInventoryURI = &quot;http://old.UGAIM.address:8004&quot;;<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> update users set userAssetURI=&quot;http://new.UGAIM.address:8003&quot; where userAssetURI = &quot;http://old.UGAIM.address:8003&quot;;<br /> &lt;/pre&gt;<br /> *If you're running in standalone mode... - Anyone familiar with standalone want to fill this in? -<br /> [[Category:Users]]<br /> <br /> == ScriptEngine Issues ==<br /> === Got &quot;Primitive: Error compiling script: unknown char: . error&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you could have this error :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> unknown char: .<br /> &lt;/pre&gt;<br /> And on the console :<br /> &lt;pre&gt;<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Unloading script<br /> 11:06:37 - Exception in MaintenanceLoopThread. Thread will recover after 5 sec throttle. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.<br /> at System.Collections.Generic.Dictionary`2[OpenSim.Region.ScriptEngine.Interfaces.IEventReceiver,OpenSim.Region.ScriptEngine.Shared.Api.Plugins.Dataserver].get_Item (IEventReceiver key) [0x00000]<br /> at OpenSim.Region.ScriptEngine.Shared.Api.AsyncCommandManager.RemoveScript (IEventReceiver engine, UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager._StopScript (UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager.DoScriptLoadUnload () [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.MaintenanceThread.MaintenanceLoop () [0x00000]<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Loading script<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: ScriptManager StartScript: localID: 720001, itemID: 88c9d28c-6004-4609-a707-717190de044a<br /> 11:06:37 - [Compiler]: Compiled new assembly for fad15951-f9aa-493f-be68-2aaf5ff8a3c9<br /> 11:06:37 - [SCRIPT]: Compiled assetID fad15951-f9aa-493f-be68-2aaf5ff8a3c9: ScriptEngines/a83150da-1ab1-11dd-89fb-0014853ee9da/CommonCompiler_compiled_fad15951-f9aa-493f-be68-2aaf5ff8a3c9.dll<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: AppDomain Loading: OpenSim.Region.ScriptEngine.Shared, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null<br /> &lt;/pre&gt;<br /> This happens on '''linux''' when your locales are not set to default ( &quot;C&quot; ).<br /> * You could refer to [http://opensimulator.org/mantis/view.php?id=2088 Mantis #2088] and [http://opensimulator.org/mantis/view.php?id=2015 Mantis #2015] for a workaround to run opensim.<br /> &lt;pre&gt;<br /> env LANG=C mono --debug OpenSim.exe<br /> &lt;/pre&gt;<br /> * You could also change your locale setup. Here is what I use in my '.bash_profile' :<br /> &lt;pre&gt;<br /> export LC_ALL=C<br /> export LANG=C<br /> &lt;/pre&gt;<br /> I know it's a ugly way to setup locales on a linux box, but it works fine on my '''Linux From Scratch''' box.<br /> <br /> '''Rq''': I saw Melanie has corrected some parts of the source code a few weeks ago to avoid such problems.<br /> <br /> === Get &quot;Primitive: Error compiling script: ApplicationName='gmcs', ...&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you have an error something like :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> ApplicationName='gmcs', CommandLine='/target:library /debug+ /optimize- /out:<br /> &quot;ScriptEngines/430c29d0-c5c6-11dd-ad8b-0800200c9a66/CommonCompiler_compiled_fbe5e682-afae-4f1a-805b-0125031101f7.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.Api.Runtime.dll&quot; -- <br /> &quot;/tmp/11b81aac/594d02ce.0.cs&quot; ', CurrentDirectory=''<br /> &lt;/pre&gt;<br /> <br /> Other features include &quot;Touch&quot; being disabled on the right click menu wheel.<br /> <br /> You might have a broken mono install (i.e. discovered as mono but not gmcs installed on a Ubuntu 8.10 Intrepid machine.)<br /> <br /> Check mono-gmcs (sudo apt-get install mono-gmcs) is correctly installed.<br /> <br /> == Locales Issues ==<br /> Well, some of us, OpenSim users, ran into random crash of the OpenSim Region server in grid mode ... <br /> <br /> I have made many tests to find a solution about that problem.<br /> <br /> I first ran into this problem with OpenSIM SVN.6660 ... Even if I have no users connected, my OpenSim region server randomly crash ( after 1 hour, or 5 hours, ... ).<br /> <br /> My first idea was to upgrade to the latest SVN release, no chance, same problem. So I made a test with a previous SVN release ( SVN.6575 ) which is running fine on another server ( same OS, same parameters, same mono release, ... ) : No chance, same problem.<br /> <br /> Then, I tried to play with locales, recompile the '''screen''' unix command line utility I use to run my servers, ... No chance again.<br /> <br /> So, I checked the memory usage on my Server, and I discovered that with the last SVN release, the amount of memory needed to run OpenSim server in multi-region/grid mode increased :) ... So, I have tuned my MySQL server to use less memory. Was better, but my OpenSim region server still randomly crash ( but could stay alive longer than before ).<br /> <br /> Then, trying to play with the '''screen''' command line options ... And all my tests shows that the '''--debug''' option impact the stability of the server.<br /> <br /> Initially, I used such command line to run OpenSim :<br /> &lt;pre&gt;<br /> /screen -S Region-service -d -m --debug mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> Without the '''--debug''' option, everything seems to be more stable.<br /> <br /> About locales, if you read mantis and threads in opensim-dev / opensim-users, you know that there are issues on system that are not &quot;en_US&quot; or &quot;C&quot; local compliant.<br /> <br /> I have re-setup my server to be full &quot;en_US.UTF8&quot;.<br /> <br /> On my Ubuntu 8.0.4 server :<br /> &lt;pre&gt;<br /> # cat /etc/default/locale<br /> LANG=&quot;en_US.UTF-8&quot;<br /> <br /> # cat /var/lib/locales/supported.d/local<br /> fr_FR.UTF-8 UTF-8<br /> en_US.UTF-8 UTF-8<br /> <br /> # cat /etc/environment<br /> PATH=&quot;/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games&quot;<br /> LANG=&quot;en_US&quot;<br /> LANGUAGE=&quot;en_US&quot;<br /> &lt;/pre&gt;<br /> And maybe you should need :<br /> &lt;pre&gt;<br /> # sudo dpkg-reconfigure locales<br /> &lt;/pre&gt;<br /> <br /> So, the resulting '''screen''' command line options should be :<br /> &lt;pre&gt;<br /> screen -S Region-service -d -m -U mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> This allow me to run OpenSim SVN.6575 without crash during more than 48 hours, and also SVN.6735 ... <br /> <br /> Hope those informations could help peoples.<br /> <br /> Just for your information : <br /> <br /> Here is my '''OpenSim Startup script''' :<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> echo &quot;User-Service...&quot;<br /> /usr/local/bin/screen -S User-service -d -m -U mono OpenSim.Grid.UserServer.exe<br /> sleep 5<br /> echo &quot;Grid-Service...&quot;<br /> /usr/local/bin/screen -S Grid-service -d -m -U mono OpenSim.Grid.GridServer.exe<br /> sleep 5<br /> echo &quot;Asset-Service...&quot;<br /> /usr/local/bin/screen -S Asset-service -d -m -U mono OpenSim.Grid.AssetServer.exe<br /> sleep 10<br /> echo &quot;Inventory-Service...&quot;<br /> /usr/local/bin/screen -S Inventory-service -d -m -U mono OpenSim.Grid.InventoryServer.exe<br /> sleep 5<br /> echo &quot;Region-Service...&quot;<br /> /usr/local/bin/screen -S Region-service -d -m -U mono OpenSim.exe<br /> sleep 5<br /> echo &quot; &quot;<br /> echo &quot; &quot;<br /> /usr/local/bin/screen -list<br /> &lt;/pre&gt;<br /> <br /> Here is also a small script that give you a menu to connect to the '''screen(s)''' sessions :<br /> &lt;pre&gt;<br /> #!/usr/bin/perl<br /> <br /> use strict;<br /> use Term::Menu;<br /> <br /> my $EXIT = 1;<br /> <br /> my $MainTitle = &quot;+-----------------------------------------------------+\n&quot;;<br /> $MainTitle .= &quot;| Connexion SCREEN aux Serveurs OPENSIM |\n&quot;;<br /> $MainTitle .= &quot;| |\n&quot;;<br /> $MainTitle .= &quot;| ( Type CTRL+A+D to exit the Screen Console. ) |\n&quot;;<br /> $MainTitle .= &quot;+-----------------------------------------------------+\n&quot;;<br /> <br /> while ( $EXIT == 1 )<br /> {<br /> <br /> system(&quot;screen -list | grep service &gt; /tmp/osg.services&quot;);<br /> my %LIST = ();<br /> open(IN, &quot;/tmp/osg.services&quot;);<br /> while ( my $i = &lt;IN&gt; )<br /> {<br /> chomp($i);<br /> <br /> $i =~ s/\./#/g;<br /> $i =~ s/\-service\t/#/g;<br /> $i =~ s/\t//g;<br /> $i =~ s/\(//g;<br /> $i =~ s/\)//g;<br /> <br /> my @STATUS = split(/#/, $i);<br /> $LIST{$STATUS[1]} = $STATUS[2];<br /> }<br /> close(IN);<br /> <br /> my %LIST2 = ();<br /> my @indices = ('User', 'Grid', 'Asset', 'Inventory', 'Region');<br /> <br /> foreach my $key ( @indices )<br /> {<br /> # print &quot;$key --&gt; $LIST{$key}\n&quot;;<br /> if ( $LIST{$key} =~ /Attached/ )<br /> {<br /> $LIST2{$key} = &quot;[X]&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{$key} = &quot;[ ]&quot;;<br /> }<br /> }<br /> <br /> if ( $LIST{'User'} =~ /Attached/ )<br /> {<br /> $LIST2{'USER'} = &quot;X&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{'USER'} = &quot;-&quot;;<br /> }<br /> <br /> system ('clear');<br /> my $prompt = new Term::Menu (<br /> spaces =&gt; 3,<br /> aftertext =&gt; &quot;\nChoisir une option : &quot;,<br /> beforetext =&gt; ${MainTitle},<br /> delim =&gt; &quot;. &quot;,<br /> );<br /> <br /> my $SEP = &quot; &quot;;<br /> <br /> my $answer = $prompt-&gt;menu(<br /> osg_user =&gt; [&quot;OpenSim User Server $SEP$LIST2{'User'}&quot;, '1'],<br /> osg_grid =&gt; [&quot;OpenSim Grid Server $SEP$LIST2{'Grid'}&quot;, '2'],<br /> osg_asset =&gt; [&quot;OpenSim Asset Server $SEP$LIST2{'Asset'}&quot;, '3'],<br /> osg_inventory =&gt; [&quot;OpenSim Inventory Server $SEP$LIST2{'Inventory'}&quot;, '4'],<br /> osg_region =&gt; [&quot;OpenSim Region Server $SEP$LIST2{'Region'}\n&quot;, '5'],<br /> osg_shutdown =&gt; [&quot;Shutdown Servers (Manual)&quot;,'6'],<br /> osg_shutdown2 =&gt; [&quot;Shutdown Servers (Hard)\n&quot;,'7'],<br /> quit =&gt; [&quot;Quitter&quot;, 'q'],<br /> );<br /> <br /> if ( &quot;${answer}&quot; eq &quot;quit&quot; )<br /> {<br /> $EXIT = 0;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_user&quot; )<br /> {<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_grid&quot; )<br /> {<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_asset&quot; )<br /> {<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_inventory&quot; )<br /> {<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_region&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown2&quot; )<br /> {<br /> # system(&quot;/OPENSIM/shutdownGrid.py&quot;);<br /> system(&quot;screen -S Region-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Inventory-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Asset-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Grid-service -r -m -X quit&quot;);<br /> system(&quot;screen -S User-service -r -m -X quit&quot;);<br /> $EXIT = 0;<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Regards, <br /> Ursula Matova.</div>

Dale Mahalko http://opensimulator.org/wiki/Troubleshooting 2010-04-04T05:37:58Z

<p>Dale Mahalko: /* Exception and loss of ode physics System.EntryPointNotFoundException: dSpaceLockQuery */ reformat page layout</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> This page gives any system-specific configuration settings that may be useful, and advice for problems that might be encountered.<br /> __TOC__<br /> {{clear}}<br /> [[Category:Users]]<br /> <br /> == System-specific configuration ==<br /> === CentOS 5 ===<br /> <br /> To install mono and nant, you can use the &quot;Linux Installer for x86&quot; found at http://www.mono-project.com/Downloads.<br /> <br /> SVN can be installed by:<br /> <br /> yum install subversion<br /> <br /> Mono defaults to installing into &lt;tt&gt;/opt&lt;/tt&gt;, so you may have to add this path to your environment variables, for example, in your &lt;tt&gt;~/.bashrc&lt;/tt&gt;:<br /> <br /> export PATH=&quot;/opt/mono-1.2.5/bin:$PATH&quot;<br /> export PKG_CONFIG_PATH=&quot;/opt/mono-1.2.5/lib/pkgconfig:$PKG_CONFIG_PATH&quot;<br /> export MANPATH=&quot;/opt/mono-1.2.5/share/man:$MANPATH&quot;<br /> export LD_LIBRARY_PATH=&quot;/opt/mono-1.2.5/lib:$LD_LIBRARY_PATH&quot;<br /> <br /> After changing &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt;, you should update the dynamic linker cache:<br /> <br /> ldconfig<br /> <br /> You may still encounter the &quot;The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file.&quot; error listed below. In that case, this may fix this:<br /> <br /> yum install glib<br /> <br /> If you are running a firewall as well (i.e., if &lt;tt&gt;iptables -L&lt;/tt&gt; shows a list of ACCEPT and REJECT rules), you'll have to open the necessary ports if you want to access the sim from other machines. For standalone mode:<br /> <br /> iptables -I RH-Firewall-1-INPUT -p tcp --dport 9000 -j ACCEPT<br /> iptables -I RH-Firewall-1-INPUT -p udp --dport 9000 -j ACCEPT<br /> <br /> 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:<br /> sudo yum install libgdiplus<br /> sudo yum install libexif<br /> sudo ln -s /usr/lib64/libgdiplus.so.0 /usr/lib64/libgdiplus.so<br /> ldconfig<br /> <br /> That finally enabled me to run OpenSim without errors, and even connect to other grids.<br /> <br /> === Debian 4.0r0 ===<br /> <br /> If you set your system to use unstable sources, and then install some packages listed below, everything should just work. To use unstable sources, modify your &lt;tt&gt;/etc/apt/sources.list&lt;/tt&gt; file, replacing 'etch' or 'stable' with 'unstable':<br /> <br /> deb ftp://ftp.debian.org/debian/ unstable main<br /> deb-src ftp://ftp.debian.org/debian/ unstable main<br /> <br /> Then update your packages to the new versions:<br /> <br /> apt-get update<br /> apt-get dist-upgrade<br /> <br /> This will probably change a large number of packages, and may break things.<br /> In my experience, however, if you do not use unstable sources then the packages are not up to date enough, and you run into version issues, which lead to two DllNotFoundException errors below appearing in the console output: gdiplus.dll and libopenjpeg-libsl-2.1.2.0.so.<br /> <br /> Once the sources are updated, we need to install the necessary packages to be able to build OpenSim:<br /> <br /> apt-get install subversion mono nant mono-gmcs mono-mjs libmono-microsoft8.0-cil libmono-system-runtime2.0-cil<br /> <br /> If any of these packages are missing, you'll probably encounter one of the errors listed below. However, with these packages, OpenSim should build cleanly.<br /> <br /> Please note: If you are using mysql as storage on unstable you may get the following error:-<br /> <br /> Exception: System.NotSupportedException: CodePage 1252 not supported<br /> at System.Text.Encoding.GetEncoding (Int32 codePage) [0x00000] <br /> <br /> To get it to work, try installing the libmono-i18n2.0-cil package<br /> <br /> apt-get install libmono-i18n2.0-cil<br /> <br /> === Gentoo ===<br /> some Mono dependency &amp; latest Mono itself may use &quot;~x86&quot; masked packages (assuming x86 is your platform, change may be made to reflect your ex:&quot;~amd64&quot; for 64bits). You could check for USE parameter with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge -vp subversion nant mono libgdiplus<br /> <br /> Then install with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge subversion nant mono libgdiplus<br /> <br /> N.B: The ACCEPT_KEYWORDS=&quot;~x86&quot; 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<br /> <br /> === Mac OS X ===<br /> This assumes you're using the universal binary for mono from the [http://www.mono-project.com/ Mono Project] site.<br /> <br /> If you are using OS X 10.4, you should also install X11 from the OS X install CDs.<br /> In OS X 10.5, this is not required.<br /> <br /> If you get errors about the 2.0 framework not being supported, you may need to update your &lt;tt&gt;pkg-config&lt;/tt&gt; path.<br /> I set this in &lt;tt&gt;~/.bash_profile&lt;/tt&gt;:<br /> export PKG_CONFIG_PATH=&quot;/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}&quot;<br /> <br /> == Errors and fixes ==<br /> <br /> === Build workarounds due to non-functionality or bugs: ===<br /> <br /> ==== Disappearing prims due to duplicate UID's ====<br /> 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. This switch is documented in the [[Running#General OpenSim server commands|general server commands]] section. (&lt;nowiki&gt;load-xml &lt;filename&gt; -newUID&lt;/nowiki&gt;). 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.<br /> <br /> ==== Linked objects not scaling/editing properly ====<br /> From Mantis [[http://opensimulator.org/mantis/view.php?id=135 # 135]] and [[http://opensimulator.org/mantis/view.php?id=223 # 223]]: &lt;br /&gt;<br /> Linked objects: while linking/unlinking objects seems to work fine, the editing of single prims inside a linked object doesn't work correctly. You have to check the box &quot;Edit linked parts&quot;, then you can select a single prim and edit it, but in most cases the changes in size- and/or postion-parameters are not accepted and revert immediately to the original ones. It is not completely reproducible, as it may work in some single case though.&lt;br /&gt;<br /> '''Workaround:''' unlink the whole object, make the changes, and relink the whole thing again. &lt;br /&gt; ''note:'' re-scaling unlinked objects in grid mode seems to work better than in standalone. <br /> <br /> &lt;hr&gt;<br /> <br /> === Exception and loss of ode physics (System.EntryPointNotFoundException: dSpaceLockQuery) ===<br /> <br /> The following error is usually caused by using the wrong version of ''libode'':<br /> <br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [SCENE] [02-01 22:20:40] System.EntryPointNotFoundException: dSpaceLockQuery<br /> :at (wrapper managed-to-native) Ode.NET.d:SpaceLockQuery (intptr)<br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.waitForSpaceUnlock (IntPtr space) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter.AvatarGeomAndBodyCreation (Single npositionX, Single npositionY, Single npositionZ, Single tensor) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeCharacter..ctor (System.String avName, OpenSim.Region.Physics.OdePlugin.OdeScene parent_scene, OpenSim.Region.Physics.Manager.PhysicsVector pos) [0x00000] <br /> :at OpenSim.Region.Physics.OdePlugin.OdeScene.AddAvatar (System.String avName, OpenSim.Region.Physics.Manager.PhysicsVector position) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.AddToPhysicalScene () [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.ScenePresence.MakeRootAgent (LLVector3 pos, Boolean isFlying) [0x00000] <br /> :at OpenSim.Region.Environment.Scenes.Scene.AgentCrossing (UInt64 regionHandle, LLUUID agentID, LLVector3 position, Boolean isFlying) [0x00000]<br /> |}<br /> <br /> First try searching your filesystem to see if you have other copies of the ode physics engine:<br /> find / -name &quot;libode.so&quot;<br /> Then make sure you have the latest version.<br /> <br /> === MySQL connection errors after about 6-8 hours ===<br /> <br /> 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:<br /> <br /> set global wait_timeout=604800;<br /> <br /> === System.DllNotFoundException: gdiplus.dll ===<br /> <br /> First, check to make sure that &lt;tt&gt;libgdiplus.so&lt;/tt&gt; is known to the dynamic linker:<br /> <br /> /sbin/ldconfig -p | grep libgdiplus<br /> <br /> If nothing is found, make sure that the directory libgdiplus.so exists in is either in your &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt; environment variable or listed in a *.conf file (e.g., gdiplus.conf) in /etc/ld.so.conf.d/. Then run &lt;tt&gt;ldconfig&lt;/tt&gt; to update the cache. Then it should be able to find the library.<br /> <br /> 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 OpenSim with debugging information turned on:<br /> <br /> MONO_LOG_LEVEL=debug mono OpenSim.exe<br /> <br /> {It may show errors loading other libraries, like &lt;tt&gt;libexif.so.9&lt;/tt&gt;. In that case, linking to an existing version of the offending library may work:<br /> <br /> ln -s libexif.so.12 libexif.so.9<br /> <br /> 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 <br /> and add the line <br /> &lt;dllmap dll=&quot;gdiplus.dll&quot; target=&quot;/opt/local/lib/libgdiplus.dylib&quot; os=&quot;!windows&quot;/&gt;<br /> <br /> ''(Is there a cleaner solution than this?)''} **see below for alternative/cleaner fix**<br /> <br /> == When installing mono or libgdiplus0 you may get dependency missing libexif.so.9 == <br /> <br /> 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 )<br /> <br /> === The assembly mscorlib.dll was not found or could not be loaded ===<br /> <br /> 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.<br /> <br /> apt-get install nant<br /> <br /> === External Program Failed: /usr/lib/pkgconfig/../../lib/mono/2.0/gmcs.exe === <br /> <br /> This is quickly fixed by retrieving mono-gmcs.<br /> <br /> apt-get install mono-gmcs<br /> <br /> === The type or namespace name JScript does not exist in the namespace Microsoft ===<br /> <br /> Note that it says JScript over and over again. Hint perhaps?<br /> <br /> apt-get install mono-mjs libmono-microsoft8.0-cil<br /> <br /> On Fedora and OpenSUSE, the needed package is &quot;mono-jscript&quot;.<br /> <br /> === The type or namespace name Tcp does not exist in the namespace System.Runtime.Remoting.Channels ===<br /> <br /> This one is taken care of with a quick install:<br /> <br /> apt-get install libmono-system-runtime2.0-cil<br /> <br /> === Missing: libopenjpeg-libsl-2.1.2.0-x86_64.so ===<br /> You are on 64bit linux machine and my need to follow these instructions: [[Installing_and_running_on_x86-64 |Installing and running on x86-64 ]]<br /> <br /> <br /> === error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file ===<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> apt-get install libglib2.0-0<br /> <br /> === The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file. ===<br /> <br /> This one seems to be fixed by retrieving the apt version of nant.<br /> <br /> apt-get install nant<br /> <br /> This can also be due to &lt;tt&gt;pkg-config&lt;/tt&gt; not being able to locate the &lt;tt&gt;mono.pc&lt;/tt&gt; file. Adding the directory containing this file to the environment variable &lt;tt&gt;PKG_CONFIG_PATH&lt;/tt&gt; may solve this.<br /> <br /> == Networking and config issues ==<br /> [[OpenSim:Running |See Running section]]<br /> <br /> === You are able to log in, but not connect to a Region from a remote client ===<br /> <br /> Look in your OpenSimulator/bin/Regions folder <br /> 1) Try 0.0.0.0 for the internal_ip_address in your region.xml(default.xml) file<br /> (you'll have one of those files *per* region you've created)<br /> 2) external_host_name=&quot;127.0.0.1&quot; will need to be changed to the accessable DNS name<br /> such as &quot;opensim.example-host.com&quot; or &quot;71.6.131.152&quot; (your public accessable ip)<br /> <br /> ==Building OpenSim==<br /> ===I can't find any build files or solution files===<br /> * If you're on Windows, run &lt;tt&gt;runprebuild.bat&lt;/tt&gt; - on Linux/Mac/FreeBSD, run &lt;tt&gt;runprebuild.sh&lt;/tt&gt;<br /> === VS2005 won't open the .sln file ===<br /> * Try running VS2005 C#. You are probably running VS2005 C++. This is a C# project.<br /> <br /> ==Running OpenSim==<br /> === Running OpenSim.exe from a Cygwin shell has access denied for some dll's ===<br /> * Do a '&lt;tt&gt;cd bin&lt;/tt&gt;' followed by '&lt;tt&gt;chmod a+x *&lt;/tt&gt;' to make all dll files executable.<br /> ===I cannot start my sim===<br /> * See [[Configuration]]<br /> <br /> ==Something Has Gone Wrong!==<br /> === I get errors concerning 'owner_uuid' when starting up my grid after updating from svn beyond r3254 ===<br /> When updating to recent revisions after r3254, we are now using the unused owner_uuid. There are some grids whose mysql tables were created during a time when this field was inadvertently removed from the .sql script that initializes the regions table. Logging in to your mysql instance and executing this SQL query to add the missing owner_uuid should solve this issue:<br /> alter table `regions` add column `owner_uuid` varchar(36) default '00000000-0000-0000-0000-000000000000' not null, comment 'Rev.2';<br /> The punctuation around regions and owner_uuid is &quot;grave accent&quot;. The punctuation around the default value and the comment is the single quote. The &quot;grave accent&quot; is the one generally to the left of the One button, under the tilde and the single-quote, is, well, underneath the double quote. I think this matters to mysql.<br /> <br /> === I get errors concerning 'State' when starting up my grid after updating from svn beyond r3786 ===<br /> After r3786, a new 'State' field has been added to the 'primshapes' table on SQLite. This field is used to persist trees and grass.<br /> You may have an empty region at startup, because OpenSim does not find this 'State' field and does not know what to do.<br /> The best is to use SQLiteBrowser or another SQLite table editor (download it at [http://sqlitebrowser.sourceforge.net/ http://sqlitebrowser.sourceforge.net/]) to create the missing field:<br /> alter table primshapes add column State integer default 0<br /> Just launch SQLiteBrowser, use File/Open database, then browse to OpenSim.db file and open it. Then, go to the &quot;Execute SQL&quot; tab, copy/paste the command above in the &quot;SQL string&quot; textbox, then hit the &quot;Execute query&quot; button.<br /> <br /> === I get a timeout during region handshake ===<br /> * Do you have the correct IP in your Regions\* config files?<br /> * Do you have multiple interfaces on the server running OpenSim? OpenSim 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.<br /> <br /> === I cannot connect to my OpenSim ===<br /> * See [[OpenSim: Connecting]]<br /> <br /> ===I can connect but cannot move===<br /> If the client connects but the avatar can only spin in place and not move, then the sim is not correctly configured. It completed the initial login function, but packets are not being exchanged between the client and the sim, probably due to a network configuration error on the sim.<br /> * See [[OpenSim: Configuration]]<br /> <br /> === From time to time my Avatar seems to get stuck ===<br /> Right now there is a bottle neck when syncing prims off to the database. This will cause small (5 - 10 second) apparent hangs of the Avatar, but it will recover fine once the data is synced. It is a known issue based on legacy architecture of some of the data storage code. We hope this will be removed soon.<br /> <br /> === I have problems with viewing the worldmap ===<br /> * This may happen when running OpenSim on a Linux server, both in grid or standalone mode.<br /> * 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...<br /> * Reason: your svn source trunk does not have the correct (or whatever...) &lt;tt&gt;libopenjpeg-libsl&lt;/tt&gt; library.<br /> * Other reason: the file &quot;defaultstripe.png&quot; does not exists in the same OpenSim folder, or is corrupted.<br /> * Solution: get the newest code from libsecondlife (&lt;tt&gt;svn co svn://opensecondlife.org/libsl/trunk&lt;/tt&gt;), '&lt;tt&gt;make&lt;/tt&gt;' manually in the subdir &lt;tt&gt;openjpeg-libsl&lt;/tt&gt;, and copy the resulting &lt;tt&gt;libopenjpeg-libsl-2.1.2.0.so&lt;/tt&gt; into your OpenSim &lt;tt&gt;bin&lt;/tt&gt; subdir, overwriting the existing one.<br /> * Recompile &amp; restart OpenSim<br /> <br /> ==Exceptions on the Console==<br /> This is a list of Exceptions that you may see on the console, what they mean, and if they are a problem.<br /> <br /> ===System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so===<br /> Failed generating terrain map: System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so<br /> at (wrapper managed-to-native) OpenJPEGNet.OpenJPEG:LibslAllocDecoded OpenJPEGNet.OpenJPEG/LibslImage&amp;)<br /> at OpenJPEGNet.OpenJPEG.Encode (System.Byte[] decoded, Int32 width, Int32 height, Int32 components, Boolean lossless) [0x00000]<br /> at OpenJPEGNet.OpenJPEG.EncodeFromImage (System.Drawing.Bitmap bitmap, Boolean lossless) [0x00000]<br /> at OpenSim.Region.Terrain.TerrainEngine.ExportJpegImage (System.String gradientmap) [0x00000]<br /> <br /> 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:<br /> * You have an old processor (libopenjpeg has been compiled with optimizations)<br /> * You are running in 64bit mode (none of the native libs are built for 64bit)<br /> <br /> You can rebuild your own libopenjpeg from source, or run in a compatible environment.<br /> You can do this by:<br /> svn co svn://openmv.org/libsl/libopenmetaverse/trunk libsl<br /> cd libsl/openjpeg-libsl/<br /> make<br /> <br /> then copy libopenjpeg-libsl-2.1.2.0.so into OpenSim bin-folder.<br /> <br /> === System.NullReferenceException at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion ===<br /> [LOGIN END]: XMLRPC Login failed, System.NullReferenceException: Object reference not set to an instance of an object<br /> at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion (OpenSim.Framework.RegionInfo regionInfo, OpenSim.Framework.UserProfileData user, OpenSim.Framework.Communications.LoginResponse response) [0x00000] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:293<br /> at OpenSim.Region.Communications.Local.LocalLoginService.CustomiseResponse (OpenSim.Framework.Communications.LoginResponse response, OpenSim.Framework.UserProfileData theUser, System.String startLocationRequest) [0x00520] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:253<br /> at OpenSim.Framework.Communications.LoginService.XmlRpcLoginMethod (Nwc.XmlRpc.XmlRpcRequest request) [0x00369] in /home/sim/svn/opensim/OpenSim/Framework/Communications/LoginService.cs:252<br /> <br /> Your first startup of OpenSim 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.<br /> <br /> ==Grid Mode==<br /> Note: Grid Mode isn't officially supported yet. As such, you are pretty much on your own if you are trying to get OpenSim up and running in Grid Mode.<br /> <br /> === I start the sim and it doesn't connect to any grid ===<br /> <br /> When OpenSim is first started, it needs configuration.<br /> <br /> * See [[OpenSim: Configuration]].<br /> <br /> === I start the OpenSim.Grid.UserServer.exe and it gives an error===<br /> If this error is access denied for &lt;tt&gt;username@localhost&lt;/tt&gt;, the mysql database is not set up.<br /> It will print some text and wait for input - either an enter to accept a default value, or another value you can supply.<br /> * See [[OpenSim: Configuration]].<br /> <br /> === I want to run my own Local Grid but one or more servers fail to start===<br /> * Be sure that you're able to start &lt;tt&gt;OpenSim.exe&lt;/tt&gt; alone, in Standalone mode, and to be able to login.<br /> * Start the servers in the correct UGAS order and answer the questions as recommended (see [[OpenSim: Configuration]]).<br /> * Set all the external URI's to the correct IP: 127.0.0.1 if running on your local machine, or aaa.bbb.ccc.ddd if running on a remote server.<br /> * Check again all the &lt;tt&gt;*.xml&lt;/tt&gt; configuration files for any wrong settings or typing errors...!<br /> * Don't forget to connect with your SL-viewer to port 8002 (Grid User-Server) instead of 9000 (Standalone OpenSim-Server).<br /> * Delete all &lt;tt&gt;*.xml&lt;/tt&gt; and &lt;tt&gt;*.yap&lt;/tt&gt; files in the &lt;tt&gt;bin&lt;/tt&gt; directory if you want to run a full reconfiguration again.<br /> <br /> === I get a bunch of asset not found errors, while connected to a online grid, and my inventory doesn't seem to work right===<br /> *Make sure your opensim.ini has ' asset_database = &quot;grid&quot; ' otherwise it will not work correctly.<br /> <br /> === My grid works fine with one user but when two users login in the same time both get stuck ===<br /> * Make sure you have export MONO_THREADS_PER_CPU=&quot;100&quot; in your environment<br /> <br /> === After ~20 minutes my region starts to take 100% cpu and region(s) hang ===<br /> * If you have mono 1.9.1 or lower upgrade to mono 2.2.<br /> <br /> ==Hypergrid==<br /> ===After starting OpenSim with Hypergrid enabled my inventory wont load!===<br /> *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.<br /> *Check the XML config files for your UGAIM servers to make sure that everything is running off of a publicly accessible IP address.<br /> **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.<br /> <br /> 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.<br /> <br /> &lt;div align = center&gt;&lt;B&gt;!!!!WARNING!!!! - Be smart! Always make a backup of your databases before making any changes to OpenSim! - !!!!WARNING!!!!&lt;/b&gt;&lt;/div&gt;<br /> &lt;pre&gt;<br /> update users set userInventoryURI=&quot;http://new.UGAIM.address:8004&quot; where userInventoryURI = &quot;http://old.UGAIM.address:8004&quot;;<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> update users set userAssetURI=&quot;http://new.UGAIM.address:8003&quot; where userAssetURI = &quot;http://old.UGAIM.address:8003&quot;;<br /> &lt;/pre&gt;<br /> *If you're running in standalone mode... - Anyone familiar with standalone want to fill this in? -<br /> [[Category:Users]]<br /> <br /> == ScriptEngine Issues ==<br /> === Got &quot;Primitive: Error compiling script: unknown char: . error&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you could have this error :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> unknown char: .<br /> &lt;/pre&gt;<br /> And on the console :<br /> &lt;pre&gt;<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Unloading script<br /> 11:06:37 - Exception in MaintenanceLoopThread. Thread will recover after 5 sec throttle. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.<br /> at System.Collections.Generic.Dictionary`2[OpenSim.Region.ScriptEngine.Interfaces.IEventReceiver,OpenSim.Region.ScriptEngine.Shared.Api.Plugins.Dataserver].get_Item (IEventReceiver key) [0x00000]<br /> at OpenSim.Region.ScriptEngine.Shared.Api.AsyncCommandManager.RemoveScript (IEventReceiver engine, UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager._StopScript (UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager.DoScriptLoadUnload () [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.MaintenanceThread.MaintenanceLoop () [0x00000]<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Loading script<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: ScriptManager StartScript: localID: 720001, itemID: 88c9d28c-6004-4609-a707-717190de044a<br /> 11:06:37 - [Compiler]: Compiled new assembly for fad15951-f9aa-493f-be68-2aaf5ff8a3c9<br /> 11:06:37 - [SCRIPT]: Compiled assetID fad15951-f9aa-493f-be68-2aaf5ff8a3c9: ScriptEngines/a83150da-1ab1-11dd-89fb-0014853ee9da/CommonCompiler_compiled_fad15951-f9aa-493f-be68-2aaf5ff8a3c9.dll<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: AppDomain Loading: OpenSim.Region.ScriptEngine.Shared, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null<br /> &lt;/pre&gt;<br /> This happens on '''linux''' when your locales are not set to default ( &quot;C&quot; ).<br /> * You could refer to [http://opensimulator.org/mantis/view.php?id=2088 Mantis #2088] and [http://opensimulator.org/mantis/view.php?id=2015 Mantis #2015] for a workaround to run opensim.<br /> &lt;pre&gt;<br /> env LANG=C mono --debug OpenSim.exe<br /> &lt;/pre&gt;<br /> * You could also change your locale setup. Here is what I use in my '.bash_profile' :<br /> &lt;pre&gt;<br /> export LC_ALL=C<br /> export LANG=C<br /> &lt;/pre&gt;<br /> I know it's a ugly way to setup locales on a linux box, but it works fine on my '''Linux From Scratch''' box.<br /> <br /> '''Rq''': I saw Melanie has corrected some parts of the source code a few weeks ago to avoid such problems.<br /> <br /> === Get &quot;Primitive: Error compiling script: ApplicationName='gmcs', ...&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you have an error something like :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> ApplicationName='gmcs', CommandLine='/target:library /debug+ /optimize- /out:<br /> &quot;ScriptEngines/430c29d0-c5c6-11dd-ad8b-0800200c9a66/CommonCompiler_compiled_fbe5e682-afae-4f1a-805b-0125031101f7.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.Api.Runtime.dll&quot; -- <br /> &quot;/tmp/11b81aac/594d02ce.0.cs&quot; ', CurrentDirectory=''<br /> &lt;/pre&gt;<br /> <br /> Other features include &quot;Touch&quot; being disabled on the right click menu wheel.<br /> <br /> You might have a broken mono install (i.e. discovered as mono but not gmcs installed on a Ubuntu 8.10 Intrepid machine.)<br /> <br /> Check mono-gmcs (sudo apt-get install mono-gmcs) is correctly installed.<br /> <br /> == Locales Issues ==<br /> Well, some of us, OpenSim users, ran into random crash of the OpenSim Region server in grid mode ... <br /> <br /> I have made many tests to find a solution about that problem.<br /> <br /> I first ran into this problem with OpenSIM SVN.6660 ... Even if I have no users connected, my OpenSim region server randomly crash ( after 1 hour, or 5 hours, ... ).<br /> <br /> My first idea was to upgrade to the latest SVN release, no chance, same problem. So I made a test with a previous SVN release ( SVN.6575 ) which is running fine on another server ( same OS, same parameters, same mono release, ... ) : No chance, same problem.<br /> <br /> Then, I tried to play with locales, recompile the '''screen''' unix command line utility I use to run my servers, ... No chance again.<br /> <br /> So, I checked the memory usage on my Server, and I discovered that with the last SVN release, the amount of memory needed to run OpenSim server in multi-region/grid mode increased :) ... So, I have tuned my MySQL server to use less memory. Was better, but my OpenSim region server still randomly crash ( but could stay alive longer than before ).<br /> <br /> Then, trying to play with the '''screen''' command line options ... And all my tests shows that the '''--debug''' option impact the stability of the server.<br /> <br /> Initially, I used such command line to run OpenSim :<br /> &lt;pre&gt;<br /> /screen -S Region-service -d -m --debug mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> Without the '''--debug''' option, everything seems to be more stable.<br /> <br /> About locales, if you read mantis and threads in opensim-dev / opensim-users, you know that there are issues on system that are not &quot;en_US&quot; or &quot;C&quot; local compliant.<br /> <br /> I have re-setup my server to be full &quot;en_US.UTF8&quot;.<br /> <br /> On my Ubuntu 8.0.4 server :<br /> &lt;pre&gt;<br /> # cat /etc/default/locale<br /> LANG=&quot;en_US.UTF-8&quot;<br /> <br /> # cat /var/lib/locales/supported.d/local<br /> fr_FR.UTF-8 UTF-8<br /> en_US.UTF-8 UTF-8<br /> <br /> # cat /etc/environment<br /> PATH=&quot;/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games&quot;<br /> LANG=&quot;en_US&quot;<br /> LANGUAGE=&quot;en_US&quot;<br /> &lt;/pre&gt;<br /> And maybe you should need :<br /> &lt;pre&gt;<br /> # sudo dpkg-reconfigure locales<br /> &lt;/pre&gt;<br /> <br /> So, the resulting '''screen''' command line options should be :<br /> &lt;pre&gt;<br /> screen -S Region-service -d -m -U mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> This allow me to run OpenSim SVN.6575 without crash during more than 48 hours, and also SVN.6735 ... <br /> <br /> Hope those informations could help peoples.<br /> <br /> Just for your information : <br /> <br /> Here is my '''OpenSim Startup script''' :<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> echo &quot;User-Service...&quot;<br /> /usr/local/bin/screen -S User-service -d -m -U mono OpenSim.Grid.UserServer.exe<br /> sleep 5<br /> echo &quot;Grid-Service...&quot;<br /> /usr/local/bin/screen -S Grid-service -d -m -U mono OpenSim.Grid.GridServer.exe<br /> sleep 5<br /> echo &quot;Asset-Service...&quot;<br /> /usr/local/bin/screen -S Asset-service -d -m -U mono OpenSim.Grid.AssetServer.exe<br /> sleep 10<br /> echo &quot;Inventory-Service...&quot;<br /> /usr/local/bin/screen -S Inventory-service -d -m -U mono OpenSim.Grid.InventoryServer.exe<br /> sleep 5<br /> echo &quot;Region-Service...&quot;<br /> /usr/local/bin/screen -S Region-service -d -m -U mono OpenSim.exe<br /> sleep 5<br /> echo &quot; &quot;<br /> echo &quot; &quot;<br /> /usr/local/bin/screen -list<br /> &lt;/pre&gt;<br /> <br /> Here is also a small script that give you a menu to connect to the '''screen(s)''' sessions :<br /> &lt;pre&gt;<br /> #!/usr/bin/perl<br /> <br /> use strict;<br /> use Term::Menu;<br /> <br /> my $EXIT = 1;<br /> <br /> my $MainTitle = &quot;+-----------------------------------------------------+\n&quot;;<br /> $MainTitle .= &quot;| Connexion SCREEN aux Serveurs OPENSIM |\n&quot;;<br /> $MainTitle .= &quot;| |\n&quot;;<br /> $MainTitle .= &quot;| ( Type CTRL+A+D to exit the Screen Console. ) |\n&quot;;<br /> $MainTitle .= &quot;+-----------------------------------------------------+\n&quot;;<br /> <br /> while ( $EXIT == 1 )<br /> {<br /> <br /> system(&quot;screen -list | grep service &gt; /tmp/osg.services&quot;);<br /> my %LIST = ();<br /> open(IN, &quot;/tmp/osg.services&quot;);<br /> while ( my $i = &lt;IN&gt; )<br /> {<br /> chomp($i);<br /> <br /> $i =~ s/\./#/g;<br /> $i =~ s/\-service\t/#/g;<br /> $i =~ s/\t//g;<br /> $i =~ s/\(//g;<br /> $i =~ s/\)//g;<br /> <br /> my @STATUS = split(/#/, $i);<br /> $LIST{$STATUS[1]} = $STATUS[2];<br /> }<br /> close(IN);<br /> <br /> my %LIST2 = ();<br /> my @indices = ('User', 'Grid', 'Asset', 'Inventory', 'Region');<br /> <br /> foreach my $key ( @indices )<br /> {<br /> # print &quot;$key --&gt; $LIST{$key}\n&quot;;<br /> if ( $LIST{$key} =~ /Attached/ )<br /> {<br /> $LIST2{$key} = &quot;[X]&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{$key} = &quot;[ ]&quot;;<br /> }<br /> }<br /> <br /> if ( $LIST{'User'} =~ /Attached/ )<br /> {<br /> $LIST2{'USER'} = &quot;X&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{'USER'} = &quot;-&quot;;<br /> }<br /> <br /> system ('clear');<br /> my $prompt = new Term::Menu (<br /> spaces =&gt; 3,<br /> aftertext =&gt; &quot;\nChoisir une option : &quot;,<br /> beforetext =&gt; ${MainTitle},<br /> delim =&gt; &quot;. &quot;,<br /> );<br /> <br /> my $SEP = &quot; &quot;;<br /> <br /> my $answer = $prompt-&gt;menu(<br /> osg_user =&gt; [&quot;OpenSim User Server $SEP$LIST2{'User'}&quot;, '1'],<br /> osg_grid =&gt; [&quot;OpenSim Grid Server $SEP$LIST2{'Grid'}&quot;, '2'],<br /> osg_asset =&gt; [&quot;OpenSim Asset Server $SEP$LIST2{'Asset'}&quot;, '3'],<br /> osg_inventory =&gt; [&quot;OpenSim Inventory Server $SEP$LIST2{'Inventory'}&quot;, '4'],<br /> osg_region =&gt; [&quot;OpenSim Region Server $SEP$LIST2{'Region'}\n&quot;, '5'],<br /> osg_shutdown =&gt; [&quot;Shutdown Servers (Manual)&quot;,'6'],<br /> osg_shutdown2 =&gt; [&quot;Shutdown Servers (Hard)\n&quot;,'7'],<br /> quit =&gt; [&quot;Quitter&quot;, 'q'],<br /> );<br /> <br /> if ( &quot;${answer}&quot; eq &quot;quit&quot; )<br /> {<br /> $EXIT = 0;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_user&quot; )<br /> {<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_grid&quot; )<br /> {<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_asset&quot; )<br /> {<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_inventory&quot; )<br /> {<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_region&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown2&quot; )<br /> {<br /> # system(&quot;/OPENSIM/shutdownGrid.py&quot;);<br /> system(&quot;screen -S Region-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Inventory-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Asset-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Grid-service -r -m -X quit&quot;);<br /> system(&quot;screen -S User-service -r -m -X quit&quot;);<br /> $EXIT = 0;<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Regards, <br /> Ursula Matova.</div>

Dale Mahalko http://opensimulator.org/wiki/Troubleshooting 2010-04-04T05:29:52Z

<p>Dale Mahalko: TOC and page text run together in ugly manner. Inserting {{clear}} after TOC to fix page reflow</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> This page gives any system-specific configuration settings that may be useful, and advice for problems that might be encountered.<br /> __TOC__<br /> {{clear}}<br /> [[Category:Users]]<br /> <br /> == System-specific configuration ==<br /> === CentOS 5 ===<br /> <br /> To install mono and nant, you can use the &quot;Linux Installer for x86&quot; found at http://www.mono-project.com/Downloads.<br /> <br /> SVN can be installed by:<br /> <br /> yum install subversion<br /> <br /> Mono defaults to installing into &lt;tt&gt;/opt&lt;/tt&gt;, so you may have to add this path to your environment variables, for example, in your &lt;tt&gt;~/.bashrc&lt;/tt&gt;:<br /> <br /> export PATH=&quot;/opt/mono-1.2.5/bin:$PATH&quot;<br /> export PKG_CONFIG_PATH=&quot;/opt/mono-1.2.5/lib/pkgconfig:$PKG_CONFIG_PATH&quot;<br /> export MANPATH=&quot;/opt/mono-1.2.5/share/man:$MANPATH&quot;<br /> export LD_LIBRARY_PATH=&quot;/opt/mono-1.2.5/lib:$LD_LIBRARY_PATH&quot;<br /> <br /> After changing &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt;, you should update the dynamic linker cache:<br /> <br /> ldconfig<br /> <br /> You may still encounter the &quot;The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file.&quot; error listed below. In that case, this may fix this:<br /> <br /> yum install glib<br /> <br /> If you are running a firewall as well (i.e., if &lt;tt&gt;iptables -L&lt;/tt&gt; shows a list of ACCEPT and REJECT rules), you'll have to open the necessary ports if you want to access the sim from other machines. For standalone mode:<br /> <br /> iptables -I RH-Firewall-1-INPUT -p tcp --dport 9000 -j ACCEPT<br /> iptables -I RH-Firewall-1-INPUT -p udp --dport 9000 -j ACCEPT<br /> <br /> 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:<br /> sudo yum install libgdiplus<br /> sudo yum install libexif<br /> sudo ln -s /usr/lib64/libgdiplus.so.0 /usr/lib64/libgdiplus.so<br /> ldconfig<br /> <br /> That finally enabled me to run OpenSim without errors, and even connect to other grids.<br /> <br /> === Debian 4.0r0 ===<br /> <br /> If you set your system to use unstable sources, and then install some packages listed below, everything should just work. To use unstable sources, modify your &lt;tt&gt;/etc/apt/sources.list&lt;/tt&gt; file, replacing 'etch' or 'stable' with 'unstable':<br /> <br /> deb ftp://ftp.debian.org/debian/ unstable main<br /> deb-src ftp://ftp.debian.org/debian/ unstable main<br /> <br /> Then update your packages to the new versions:<br /> <br /> apt-get update<br /> apt-get dist-upgrade<br /> <br /> This will probably change a large number of packages, and may break things.<br /> In my experience, however, if you do not use unstable sources then the packages are not up to date enough, and you run into version issues, which lead to two DllNotFoundException errors below appearing in the console output: gdiplus.dll and libopenjpeg-libsl-2.1.2.0.so.<br /> <br /> Once the sources are updated, we need to install the necessary packages to be able to build OpenSim:<br /> <br /> apt-get install subversion mono nant mono-gmcs mono-mjs libmono-microsoft8.0-cil libmono-system-runtime2.0-cil<br /> <br /> If any of these packages are missing, you'll probably encounter one of the errors listed below. However, with these packages, OpenSim should build cleanly.<br /> <br /> Please note: If you are using mysql as storage on unstable you may get the following error:-<br /> <br /> Exception: System.NotSupportedException: CodePage 1252 not supported<br /> at System.Text.Encoding.GetEncoding (Int32 codePage) [0x00000] <br /> <br /> To get it to work, try installing the libmono-i18n2.0-cil package<br /> <br /> apt-get install libmono-i18n2.0-cil<br /> <br /> === Gentoo ===<br /> some Mono dependency &amp; latest Mono itself may use &quot;~x86&quot; masked packages (assuming x86 is your platform, change may be made to reflect your ex:&quot;~amd64&quot; for 64bits). You could check for USE parameter with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge -vp subversion nant mono libgdiplus<br /> <br /> Then install with:<br /> <br /> ACCEPT_KEYWORDS=&quot;~x86&quot; emerge subversion nant mono libgdiplus<br /> <br /> N.B: The ACCEPT_KEYWORDS=&quot;~x86&quot; 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<br /> <br /> === Mac OS X ===<br /> This assumes you're using the universal binary for mono from the [http://www.mono-project.com/ Mono Project] site.<br /> <br /> If you are using OS X 10.4, you should also install X11 from the OS X install CDs.<br /> In OS X 10.5, this is not required.<br /> <br /> If you get errors about the 2.0 framework not being supported, you may need to update your &lt;tt&gt;pkg-config&lt;/tt&gt; path.<br /> I set this in &lt;tt&gt;~/.bash_profile&lt;/tt&gt;:<br /> export PKG_CONFIG_PATH=&quot;/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}&quot;<br /> <br /> == Errors and fixes ==<br /> <br /> === Build workarounds due to non-functionality or bugs: ===<br /> <br /> ==== Disappearing prims due to duplicate UID's ====<br /> 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. This switch is documented in the [[Running#General OpenSim server commands|general server commands]] section. (&lt;nowiki&gt;load-xml &lt;filename&gt; -newUID&lt;/nowiki&gt;). 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.<br /> <br /> ==== Linked objects not scaling/editing properly ====<br /> From Mantis [[http://opensimulator.org/mantis/view.php?id=135 # 135]] and [[http://opensimulator.org/mantis/view.php?id=223 # 223]]: &lt;br /&gt;<br /> Linked objects: while linking/unlinking objects seems to work fine, the editing of single prims inside a linked object doesn't work correctly. You have to check the box &quot;Edit linked parts&quot;, then you can select a single prim and edit it, but in most cases the changes in size- and/or postion-parameters are not accepted and revert immediately to the original ones. It is not completely reproducible, as it may work in some single case though.&lt;br /&gt;<br /> '''Workaround:''' unlink the whole object, make the changes, and relink the whole thing again. &lt;br /&gt; ''note:'' re-scaling unlinked objects in grid mode seems to work better than in standalone. <br /> <br /> &lt;hr&gt;<br /> <br /> === Exception and loss of ode physics System.EntryPointNotFoundException: dSpaceLockQuery ===<br /> <br /> The following is usually caused by using the wrong version of libode. First try find / -name &quot;libode.so&quot; to see if you have other copies of the ode physics engine. Then make sure you have the latest version of this.<br /> <br /> [SCENE] [02-01 22:20:40] System.EntryPointNotFoundException: dSpaceLockQuery<br /> at (wrapper managed-to-native) Ode.NET.d:SpaceLockQuery (intptr)<br /> at OpenSim.Region.Physics.OdePlugin.OdeScene.waitForSpaceUnlock (IntPtr space) [0x00000] <br /> at OpenSim.Region.Physics.OdePlugin.OdeCharacter.AvatarGeomAndBodyCreation (Single npositionX, Single npositionY, Single npositionZ, Single tensor) [0x00000] <br /> at OpenSim.Region.Physics.OdePlugin.OdeCharacter..ctor (System.String avName, OpenSim.Region.Physics.OdePlugin.OdeScene parent_scene, OpenSim.Region.Physics.Manager.PhysicsVector pos) [0x00000] <br /> at OpenSim.Region.Physics.OdePlugin.OdeScene.AddAvatar (System.String avName, OpenSim.Region.Physics.Manager.PhysicsVector position) [0x00000] <br /> at OpenSim.Region.Environment.Scenes.ScenePresence.AddToPhysicalScene () [0x00000] <br /> at OpenSim.Region.Environment.Scenes.ScenePresence.MakeRootAgent (LLVector3 pos, Boolean isFlying) [0x00000] <br /> at OpenSim.Region.Environment.Scenes.Scene.AgentCrossing (UInt64 regionHandle, LLUUID agentID, LLVector3 position, Boolean isFlying) [0x00000]<br /> === MySQL connection errors after about 6-8 hours ===<br /> <br /> 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:<br /> <br /> set global wait_timeout=604800;<br /> <br /> === System.DllNotFoundException: gdiplus.dll ===<br /> <br /> First, check to make sure that &lt;tt&gt;libgdiplus.so&lt;/tt&gt; is known to the dynamic linker:<br /> <br /> /sbin/ldconfig -p | grep libgdiplus<br /> <br /> If nothing is found, make sure that the directory libgdiplus.so exists in is either in your &lt;tt&gt;LD_LIBRARY_PATH&lt;/tt&gt; environment variable or listed in a *.conf file (e.g., gdiplus.conf) in /etc/ld.so.conf.d/. Then run &lt;tt&gt;ldconfig&lt;/tt&gt; to update the cache. Then it should be able to find the library.<br /> <br /> 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 OpenSim with debugging information turned on:<br /> <br /> MONO_LOG_LEVEL=debug mono OpenSim.exe<br /> <br /> {It may show errors loading other libraries, like &lt;tt&gt;libexif.so.9&lt;/tt&gt;. In that case, linking to an existing version of the offending library may work:<br /> <br /> ln -s libexif.so.12 libexif.so.9<br /> <br /> 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 <br /> and add the line <br /> &lt;dllmap dll=&quot;gdiplus.dll&quot; target=&quot;/opt/local/lib/libgdiplus.dylib&quot; os=&quot;!windows&quot;/&gt;<br /> <br /> ''(Is there a cleaner solution than this?)''} **see below for alternative/cleaner fix**<br /> <br /> == When installing mono or libgdiplus0 you may get dependency missing libexif.so.9 == <br /> <br /> 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 )<br /> <br /> === The assembly mscorlib.dll was not found or could not be loaded ===<br /> <br /> 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.<br /> <br /> apt-get install nant<br /> <br /> === External Program Failed: /usr/lib/pkgconfig/../../lib/mono/2.0/gmcs.exe === <br /> <br /> This is quickly fixed by retrieving mono-gmcs.<br /> <br /> apt-get install mono-gmcs<br /> <br /> === The type or namespace name JScript does not exist in the namespace Microsoft ===<br /> <br /> Note that it says JScript over and over again. Hint perhaps?<br /> <br /> apt-get install mono-mjs libmono-microsoft8.0-cil<br /> <br /> On Fedora and OpenSUSE, the needed package is &quot;mono-jscript&quot;.<br /> <br /> === The type or namespace name Tcp does not exist in the namespace System.Runtime.Remoting.Channels ===<br /> <br /> This one is taken care of with a quick install:<br /> <br /> apt-get install libmono-system-runtime2.0-cil<br /> <br /> === Missing: libopenjpeg-libsl-2.1.2.0-x86_64.so ===<br /> You are on 64bit linux machine and my need to follow these instructions: [[Installing_and_running_on_x86-64 |Installing and running on x86-64 ]]<br /> <br /> <br /> === error while loading shared libraries: libgthread-2.0.so.0: cannot open shared object file ===<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> apt-get install libglib2.0-0<br /> <br /> === The current runtime framework 'mono-2.0' is not correctly configured in the NAnt configuration file. ===<br /> <br /> This one seems to be fixed by retrieving the apt version of nant.<br /> <br /> apt-get install nant<br /> <br /> This can also be due to &lt;tt&gt;pkg-config&lt;/tt&gt; not being able to locate the &lt;tt&gt;mono.pc&lt;/tt&gt; file. Adding the directory containing this file to the environment variable &lt;tt&gt;PKG_CONFIG_PATH&lt;/tt&gt; may solve this.<br /> <br /> == Networking and config issues ==<br /> [[OpenSim:Running |See Running section]]<br /> <br /> === You are able to log in, but not connect to a Region from a remote client ===<br /> <br /> Look in your OpenSimulator/bin/Regions folder <br /> 1) Try 0.0.0.0 for the internal_ip_address in your region.xml(default.xml) file<br /> (you'll have one of those files *per* region you've created)<br /> 2) external_host_name=&quot;127.0.0.1&quot; will need to be changed to the accessable DNS name<br /> such as &quot;opensim.example-host.com&quot; or &quot;71.6.131.152&quot; (your public accessable ip)<br /> <br /> ==Building OpenSim==<br /> ===I can't find any build files or solution files===<br /> * If you're on Windows, run &lt;tt&gt;runprebuild.bat&lt;/tt&gt; - on Linux/Mac/FreeBSD, run &lt;tt&gt;runprebuild.sh&lt;/tt&gt;<br /> === VS2005 won't open the .sln file ===<br /> * Try running VS2005 C#. You are probably running VS2005 C++. This is a C# project.<br /> <br /> ==Running OpenSim==<br /> === Running OpenSim.exe from a Cygwin shell has access denied for some dll's ===<br /> * Do a '&lt;tt&gt;cd bin&lt;/tt&gt;' followed by '&lt;tt&gt;chmod a+x *&lt;/tt&gt;' to make all dll files executable.<br /> ===I cannot start my sim===<br /> * See [[Configuration]]<br /> <br /> ==Something Has Gone Wrong!==<br /> === I get errors concerning 'owner_uuid' when starting up my grid after updating from svn beyond r3254 ===<br /> When updating to recent revisions after r3254, we are now using the unused owner_uuid. There are some grids whose mysql tables were created during a time when this field was inadvertently removed from the .sql script that initializes the regions table. Logging in to your mysql instance and executing this SQL query to add the missing owner_uuid should solve this issue:<br /> alter table `regions` add column `owner_uuid` varchar(36) default '00000000-0000-0000-0000-000000000000' not null, comment 'Rev.2';<br /> The punctuation around regions and owner_uuid is &quot;grave accent&quot;. The punctuation around the default value and the comment is the single quote. The &quot;grave accent&quot; is the one generally to the left of the One button, under the tilde and the single-quote, is, well, underneath the double quote. I think this matters to mysql.<br /> <br /> === I get errors concerning 'State' when starting up my grid after updating from svn beyond r3786 ===<br /> After r3786, a new 'State' field has been added to the 'primshapes' table on SQLite. This field is used to persist trees and grass.<br /> You may have an empty region at startup, because OpenSim does not find this 'State' field and does not know what to do.<br /> The best is to use SQLiteBrowser or another SQLite table editor (download it at [http://sqlitebrowser.sourceforge.net/ http://sqlitebrowser.sourceforge.net/]) to create the missing field:<br /> alter table primshapes add column State integer default 0<br /> Just launch SQLiteBrowser, use File/Open database, then browse to OpenSim.db file and open it. Then, go to the &quot;Execute SQL&quot; tab, copy/paste the command above in the &quot;SQL string&quot; textbox, then hit the &quot;Execute query&quot; button.<br /> <br /> === I get a timeout during region handshake ===<br /> * Do you have the correct IP in your Regions\* config files?<br /> * Do you have multiple interfaces on the server running OpenSim? OpenSim 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.<br /> <br /> === I cannot connect to my OpenSim ===<br /> * See [[OpenSim: Connecting]]<br /> <br /> ===I can connect but cannot move===<br /> If the client connects but the avatar can only spin in place and not move, then the sim is not correctly configured. It completed the initial login function, but packets are not being exchanged between the client and the sim, probably due to a network configuration error on the sim.<br /> * See [[OpenSim: Configuration]]<br /> <br /> === From time to time my Avatar seems to get stuck ===<br /> Right now there is a bottle neck when syncing prims off to the database. This will cause small (5 - 10 second) apparent hangs of the Avatar, but it will recover fine once the data is synced. It is a known issue based on legacy architecture of some of the data storage code. We hope this will be removed soon.<br /> <br /> === I have problems with viewing the worldmap ===<br /> * This may happen when running OpenSim on a Linux server, both in grid or standalone mode.<br /> * 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...<br /> * Reason: your svn source trunk does not have the correct (or whatever...) &lt;tt&gt;libopenjpeg-libsl&lt;/tt&gt; library.<br /> * Other reason: the file &quot;defaultstripe.png&quot; does not exists in the same OpenSim folder, or is corrupted.<br /> * Solution: get the newest code from libsecondlife (&lt;tt&gt;svn co svn://opensecondlife.org/libsl/trunk&lt;/tt&gt;), '&lt;tt&gt;make&lt;/tt&gt;' manually in the subdir &lt;tt&gt;openjpeg-libsl&lt;/tt&gt;, and copy the resulting &lt;tt&gt;libopenjpeg-libsl-2.1.2.0.so&lt;/tt&gt; into your OpenSim &lt;tt&gt;bin&lt;/tt&gt; subdir, overwriting the existing one.<br /> * Recompile &amp; restart OpenSim<br /> <br /> ==Exceptions on the Console==<br /> This is a list of Exceptions that you may see on the console, what they mean, and if they are a problem.<br /> <br /> ===System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so===<br /> Failed generating terrain map: System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so<br /> at (wrapper managed-to-native) OpenJPEGNet.OpenJPEG:LibslAllocDecoded OpenJPEGNet.OpenJPEG/LibslImage&amp;)<br /> at OpenJPEGNet.OpenJPEG.Encode (System.Byte[] decoded, Int32 width, Int32 height, Int32 components, Boolean lossless) [0x00000]<br /> at OpenJPEGNet.OpenJPEG.EncodeFromImage (System.Drawing.Bitmap bitmap, Boolean lossless) [0x00000]<br /> at OpenSim.Region.Terrain.TerrainEngine.ExportJpegImage (System.String gradientmap) [0x00000]<br /> <br /> 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:<br /> * You have an old processor (libopenjpeg has been compiled with optimizations)<br /> * You are running in 64bit mode (none of the native libs are built for 64bit)<br /> <br /> You can rebuild your own libopenjpeg from source, or run in a compatible environment.<br /> You can do this by:<br /> svn co svn://openmv.org/libsl/libopenmetaverse/trunk libsl<br /> cd libsl/openjpeg-libsl/<br /> make<br /> <br /> then copy libopenjpeg-libsl-2.1.2.0.so into OpenSim bin-folder.<br /> <br /> === System.NullReferenceException at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion ===<br /> [LOGIN END]: XMLRPC Login failed, System.NullReferenceException: Object reference not set to an instance of an object<br /> at OpenSim.Region.Communications.Local.LocalLoginService.PrepareLoginToRegion (OpenSim.Framework.RegionInfo regionInfo, OpenSim.Framework.UserProfileData user, OpenSim.Framework.Communications.LoginResponse response) [0x00000] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:293<br /> at OpenSim.Region.Communications.Local.LocalLoginService.CustomiseResponse (OpenSim.Framework.Communications.LoginResponse response, OpenSim.Framework.UserProfileData theUser, System.String startLocationRequest) [0x00520] in /home/sim/svn/opensim/OpenSim/Region/Communications/Local/LocalLoginService.cs:253<br /> at OpenSim.Framework.Communications.LoginService.XmlRpcLoginMethod (Nwc.XmlRpc.XmlRpcRequest request) [0x00369] in /home/sim/svn/opensim/OpenSim/Framework/Communications/LoginService.cs:252<br /> <br /> Your first startup of OpenSim 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.<br /> <br /> ==Grid Mode==<br /> Note: Grid Mode isn't officially supported yet. As such, you are pretty much on your own if you are trying to get OpenSim up and running in Grid Mode.<br /> <br /> === I start the sim and it doesn't connect to any grid ===<br /> <br /> When OpenSim is first started, it needs configuration.<br /> <br /> * See [[OpenSim: Configuration]].<br /> <br /> === I start the OpenSim.Grid.UserServer.exe and it gives an error===<br /> If this error is access denied for &lt;tt&gt;username@localhost&lt;/tt&gt;, the mysql database is not set up.<br /> It will print some text and wait for input - either an enter to accept a default value, or another value you can supply.<br /> * See [[OpenSim: Configuration]].<br /> <br /> === I want to run my own Local Grid but one or more servers fail to start===<br /> * Be sure that you're able to start &lt;tt&gt;OpenSim.exe&lt;/tt&gt; alone, in Standalone mode, and to be able to login.<br /> * Start the servers in the correct UGAS order and answer the questions as recommended (see [[OpenSim: Configuration]]).<br /> * Set all the external URI's to the correct IP: 127.0.0.1 if running on your local machine, or aaa.bbb.ccc.ddd if running on a remote server.<br /> * Check again all the &lt;tt&gt;*.xml&lt;/tt&gt; configuration files for any wrong settings or typing errors...!<br /> * Don't forget to connect with your SL-viewer to port 8002 (Grid User-Server) instead of 9000 (Standalone OpenSim-Server).<br /> * Delete all &lt;tt&gt;*.xml&lt;/tt&gt; and &lt;tt&gt;*.yap&lt;/tt&gt; files in the &lt;tt&gt;bin&lt;/tt&gt; directory if you want to run a full reconfiguration again.<br /> <br /> === I get a bunch of asset not found errors, while connected to a online grid, and my inventory doesn't seem to work right===<br /> *Make sure your opensim.ini has ' asset_database = &quot;grid&quot; ' otherwise it will not work correctly.<br /> <br /> === My grid works fine with one user but when two users login in the same time both get stuck ===<br /> * Make sure you have export MONO_THREADS_PER_CPU=&quot;100&quot; in your environment<br /> <br /> === After ~20 minutes my region starts to take 100% cpu and region(s) hang ===<br /> * If you have mono 1.9.1 or lower upgrade to mono 2.2.<br /> <br /> ==Hypergrid==<br /> ===After starting OpenSim with Hypergrid enabled my inventory wont load!===<br /> *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.<br /> *Check the XML config files for your UGAIM servers to make sure that everything is running off of a publicly accessible IP address.<br /> **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.<br /> <br /> 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.<br /> <br /> &lt;div align = center&gt;&lt;B&gt;!!!!WARNING!!!! - Be smart! Always make a backup of your databases before making any changes to OpenSim! - !!!!WARNING!!!!&lt;/b&gt;&lt;/div&gt;<br /> &lt;pre&gt;<br /> update users set userInventoryURI=&quot;http://new.UGAIM.address:8004&quot; where userInventoryURI = &quot;http://old.UGAIM.address:8004&quot;;<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> update users set userAssetURI=&quot;http://new.UGAIM.address:8003&quot; where userAssetURI = &quot;http://old.UGAIM.address:8003&quot;;<br /> &lt;/pre&gt;<br /> *If you're running in standalone mode... - Anyone familiar with standalone want to fill this in? -<br /> [[Category:Users]]<br /> <br /> == ScriptEngine Issues ==<br /> === Got &quot;Primitive: Error compiling script: unknown char: . error&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you could have this error :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> unknown char: .<br /> &lt;/pre&gt;<br /> And on the console :<br /> &lt;pre&gt;<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Unloading script<br /> 11:06:37 - Exception in MaintenanceLoopThread. Thread will recover after 5 sec throttle. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.<br /> at System.Collections.Generic.Dictionary`2[OpenSim.Region.ScriptEngine.Interfaces.IEventReceiver,OpenSim.Region.ScriptEngine.Shared.Api.Plugins.Dataserver].get_Item (IEventReceiver key) [0x00000]<br /> at OpenSim.Region.ScriptEngine.Shared.Api.AsyncCommandManager.RemoveScript (IEventReceiver engine, UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager._StopScript (UInt32 localID, UUID itemID) [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.ScriptManager.DoScriptLoadUnload () [0x00000]<br /> at OpenSim.Region.ScriptEngine.DotNetEngine.MaintenanceThread.MaintenanceLoop () [0x00000]<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: Loading script<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: ScriptManager StartScript: localID: 720001, itemID: 88c9d28c-6004-4609-a707-717190de044a<br /> 11:06:37 - [Compiler]: Compiled new assembly for fad15951-f9aa-493f-be68-2aaf5ff8a3c9<br /> 11:06:37 - [SCRIPT]: Compiled assetID fad15951-f9aa-493f-be68-2aaf5ff8a3c9: ScriptEngines/a83150da-1ab1-11dd-89fb-0014853ee9da/CommonCompiler_compiled_fad15951-f9aa-493f-be68-2aaf5ff8a3c9.dll<br /> 11:06:37 - [ScriptEngine.DotNetEngine]: AppDomain Loading: OpenSim.Region.ScriptEngine.Shared, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null<br /> &lt;/pre&gt;<br /> This happens on '''linux''' when your locales are not set to default ( &quot;C&quot; ).<br /> * You could refer to [http://opensimulator.org/mantis/view.php?id=2088 Mantis #2088] and [http://opensimulator.org/mantis/view.php?id=2015 Mantis #2015] for a workaround to run opensim.<br /> &lt;pre&gt;<br /> env LANG=C mono --debug OpenSim.exe<br /> &lt;/pre&gt;<br /> * You could also change your locale setup. Here is what I use in my '.bash_profile' :<br /> &lt;pre&gt;<br /> export LC_ALL=C<br /> export LANG=C<br /> &lt;/pre&gt;<br /> I know it's a ugly way to setup locales on a linux box, but it works fine on my '''Linux From Scratch''' box.<br /> <br /> '''Rq''': I saw Melanie has corrected some parts of the source code a few weeks ago to avoid such problems.<br /> <br /> === Get &quot;Primitive: Error compiling script: ApplicationName='gmcs', ...&quot; when compiling script ===<br /> When trying to compile a script ( using DotNetEngine or XEngine ) you have an error something like :<br /> &lt;pre&gt;<br /> Primitive: Error compiling script:<br /> ApplicationName='gmcs', CommandLine='/target:library /debug+ /optimize- /out:<br /> &quot;ScriptEngines/430c29d0-c5c6-11dd-ad8b-0800200c9a66/CommonCompiler_compiled_fbe5e682-afae-4f1a-805b-0125031101f7.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.dll&quot; <br /> /r:&quot;/usr/lib/opensim/bin/OpenSim.Region.ScriptEngine.Shared.Api.Runtime.dll&quot; -- <br /> &quot;/tmp/11b81aac/594d02ce.0.cs&quot; ', CurrentDirectory=''<br /> &lt;/pre&gt;<br /> <br /> Other features include &quot;Touch&quot; being disabled on the right click menu wheel.<br /> <br /> You might have a broken mono install (i.e. discovered as mono but not gmcs installed on a Ubuntu 8.10 Intrepid machine.)<br /> <br /> Check mono-gmcs (sudo apt-get install mono-gmcs) is correctly installed.<br /> <br /> == Locales Issues ==<br /> Well, some of us, OpenSim users, ran into random crash of the OpenSim Region server in grid mode ... <br /> <br /> I have made many tests to find a solution about that problem.<br /> <br /> I first ran into this problem with OpenSIM SVN.6660 ... Even if I have no users connected, my OpenSim region server randomly crash ( after 1 hour, or 5 hours, ... ).<br /> <br /> My first idea was to upgrade to the latest SVN release, no chance, same problem. So I made a test with a previous SVN release ( SVN.6575 ) which is running fine on another server ( same OS, same parameters, same mono release, ... ) : No chance, same problem.<br /> <br /> Then, I tried to play with locales, recompile the '''screen''' unix command line utility I use to run my servers, ... No chance again.<br /> <br /> So, I checked the memory usage on my Server, and I discovered that with the last SVN release, the amount of memory needed to run OpenSim server in multi-region/grid mode increased :) ... So, I have tuned my MySQL server to use less memory. Was better, but my OpenSim region server still randomly crash ( but could stay alive longer than before ).<br /> <br /> Then, trying to play with the '''screen''' command line options ... And all my tests shows that the '''--debug''' option impact the stability of the server.<br /> <br /> Initially, I used such command line to run OpenSim :<br /> &lt;pre&gt;<br /> /screen -S Region-service -d -m --debug mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> Without the '''--debug''' option, everything seems to be more stable.<br /> <br /> About locales, if you read mantis and threads in opensim-dev / opensim-users, you know that there are issues on system that are not &quot;en_US&quot; or &quot;C&quot; local compliant.<br /> <br /> I have re-setup my server to be full &quot;en_US.UTF8&quot;.<br /> <br /> On my Ubuntu 8.0.4 server :<br /> &lt;pre&gt;<br /> # cat /etc/default/locale<br /> LANG=&quot;en_US.UTF-8&quot;<br /> <br /> # cat /var/lib/locales/supported.d/local<br /> fr_FR.UTF-8 UTF-8<br /> en_US.UTF-8 UTF-8<br /> <br /> # cat /etc/environment<br /> PATH=&quot;/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games&quot;<br /> LANG=&quot;en_US&quot;<br /> LANGUAGE=&quot;en_US&quot;<br /> &lt;/pre&gt;<br /> And maybe you should need :<br /> &lt;pre&gt;<br /> # sudo dpkg-reconfigure locales<br /> &lt;/pre&gt;<br /> <br /> So, the resulting '''screen''' command line options should be :<br /> &lt;pre&gt;<br /> screen -S Region-service -d -m -U mono OpenSim.exe<br /> &lt;/pre&gt;<br /> <br /> This allow me to run OpenSim SVN.6575 without crash during more than 48 hours, and also SVN.6735 ... <br /> <br /> Hope those informations could help peoples.<br /> <br /> Just for your information : <br /> <br /> Here is my '''OpenSim Startup script''' :<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> <br /> echo &quot;User-Service...&quot;<br /> /usr/local/bin/screen -S User-service -d -m -U mono OpenSim.Grid.UserServer.exe<br /> sleep 5<br /> echo &quot;Grid-Service...&quot;<br /> /usr/local/bin/screen -S Grid-service -d -m -U mono OpenSim.Grid.GridServer.exe<br /> sleep 5<br /> echo &quot;Asset-Service...&quot;<br /> /usr/local/bin/screen -S Asset-service -d -m -U mono OpenSim.Grid.AssetServer.exe<br /> sleep 10<br /> echo &quot;Inventory-Service...&quot;<br /> /usr/local/bin/screen -S Inventory-service -d -m -U mono OpenSim.Grid.InventoryServer.exe<br /> sleep 5<br /> echo &quot;Region-Service...&quot;<br /> /usr/local/bin/screen -S Region-service -d -m -U mono OpenSim.exe<br /> sleep 5<br /> echo &quot; &quot;<br /> echo &quot; &quot;<br /> /usr/local/bin/screen -list<br /> &lt;/pre&gt;<br /> <br /> Here is also a small script that give you a menu to connect to the '''screen(s)''' sessions :<br /> &lt;pre&gt;<br /> #!/usr/bin/perl<br /> <br /> use strict;<br /> use Term::Menu;<br /> <br /> my $EXIT = 1;<br /> <br /> my $MainTitle = &quot;+-----------------------------------------------------+\n&quot;;<br /> $MainTitle .= &quot;| Connexion SCREEN aux Serveurs OPENSIM |\n&quot;;<br /> $MainTitle .= &quot;| |\n&quot;;<br /> $MainTitle .= &quot;| ( Type CTRL+A+D to exit the Screen Console. ) |\n&quot;;<br /> $MainTitle .= &quot;+-----------------------------------------------------+\n&quot;;<br /> <br /> while ( $EXIT == 1 )<br /> {<br /> <br /> system(&quot;screen -list | grep service &gt; /tmp/osg.services&quot;);<br /> my %LIST = ();<br /> open(IN, &quot;/tmp/osg.services&quot;);<br /> while ( my $i = &lt;IN&gt; )<br /> {<br /> chomp($i);<br /> <br /> $i =~ s/\./#/g;<br /> $i =~ s/\-service\t/#/g;<br /> $i =~ s/\t//g;<br /> $i =~ s/\(//g;<br /> $i =~ s/\)//g;<br /> <br /> my @STATUS = split(/#/, $i);<br /> $LIST{$STATUS[1]} = $STATUS[2];<br /> }<br /> close(IN);<br /> <br /> my %LIST2 = ();<br /> my @indices = ('User', 'Grid', 'Asset', 'Inventory', 'Region');<br /> <br /> foreach my $key ( @indices )<br /> {<br /> # print &quot;$key --&gt; $LIST{$key}\n&quot;;<br /> if ( $LIST{$key} =~ /Attached/ )<br /> {<br /> $LIST2{$key} = &quot;[X]&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{$key} = &quot;[ ]&quot;;<br /> }<br /> }<br /> <br /> if ( $LIST{'User'} =~ /Attached/ )<br /> {<br /> $LIST2{'USER'} = &quot;X&quot;;<br /> }<br /> else<br /> {<br /> $LIST2{'USER'} = &quot;-&quot;;<br /> }<br /> <br /> system ('clear');<br /> my $prompt = new Term::Menu (<br /> spaces =&gt; 3,<br /> aftertext =&gt; &quot;\nChoisir une option : &quot;,<br /> beforetext =&gt; ${MainTitle},<br /> delim =&gt; &quot;. &quot;,<br /> );<br /> <br /> my $SEP = &quot; &quot;;<br /> <br /> my $answer = $prompt-&gt;menu(<br /> osg_user =&gt; [&quot;OpenSim User Server $SEP$LIST2{'User'}&quot;, '1'],<br /> osg_grid =&gt; [&quot;OpenSim Grid Server $SEP$LIST2{'Grid'}&quot;, '2'],<br /> osg_asset =&gt; [&quot;OpenSim Asset Server $SEP$LIST2{'Asset'}&quot;, '3'],<br /> osg_inventory =&gt; [&quot;OpenSim Inventory Server $SEP$LIST2{'Inventory'}&quot;, '4'],<br /> osg_region =&gt; [&quot;OpenSim Region Server $SEP$LIST2{'Region'}\n&quot;, '5'],<br /> osg_shutdown =&gt; [&quot;Shutdown Servers (Manual)&quot;,'6'],<br /> osg_shutdown2 =&gt; [&quot;Shutdown Servers (Hard)\n&quot;,'7'],<br /> quit =&gt; [&quot;Quitter&quot;, 'q'],<br /> );<br /> <br /> if ( &quot;${answer}&quot; eq &quot;quit&quot; )<br /> {<br /> $EXIT = 0;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_user&quot; )<br /> {<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_grid&quot; )<br /> {<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_asset&quot; )<br /> {<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_inventory&quot; )<br /> {<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_region&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown&quot; )<br /> {<br /> system(&quot;screen -d -r -S Region-service&quot;);<br /> system(&quot;screen -d -r -S Inventory-service&quot;);<br /> system(&quot;screen -d -r -S Asset-service&quot;);<br /> system(&quot;screen -d -r -S Grid-service&quot;);<br /> system(&quot;screen -d -r -S User-service&quot;);<br /> $EXIT = 1;<br /> }<br /> <br /> if ( &quot;${answer}&quot; eq &quot;osg_shutdown2&quot; )<br /> {<br /> # system(&quot;/OPENSIM/shutdownGrid.py&quot;);<br /> system(&quot;screen -S Region-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Inventory-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Asset-service -r -m -X quit&quot;);<br /> system(&quot;screen -S Grid-service -r -m -X quit&quot;);<br /> system(&quot;screen -S User-service -r -m -X quit&quot;);<br /> $EXIT = 0;<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Regards, <br /> Ursula Matova.</div>

Dale Mahalko http://opensimulator.org/wiki/Template:Clear 2010-04-04T05:23:54Z

<p>Dale Mahalko: fix page elements running all together... see http://en.wikipedia.org/wiki/Template:Clear</p> <hr /> <div>&lt;div style=&quot;clear:both;&quot;&gt;&lt;/div&gt;</div>

Dale Mahalko http://opensimulator.org/wiki/Configuration 2010-04-04T04:20:09Z

<p>Dale Mahalko: /* Running OpenSim in Standalone mode */ embolden OpenSim.ini.example / OpenSim.ini</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> ==OpenSim simulator configuration file==<br /> The region simulator configuration is managed using a file called [[OpenSim.ini]]. This file is used regardless of whether the sim is running in standalone or grid mode. This file includes some additional configuration information from the config-include/ directory. Detailed information on the options available for setttings in this file can be found [[OpenSim.ini|here]].<br /> Please note, that the name OpenSim.ini can be changed via command line arguments (see above). Also, note that the default download does not include an OpenSim.ini file, but rather provides an example file. To get started editing your ini file, please cd into opensim/bin/ and copy OpenSim.ini.example to OpenSim.ini.<br /> <br /> It is also possible to distribute the inifile settings over two files. This is useful if you want to run several OpenSim processes where most of your settings are identical but some settings differ.<br /> The master file is read first, then the inifile is read. Settings given in the inifile overrule settings given in the master file.<br /> The master file has the same format and the same keywords as the inifile, so the same documentation applies.<br /> <br /> ==Database==<br /> Opensim's supports the following database-engines:<br /> * SQLite (default - a lightweight database that comes bundled with OpenSim and can be used without requiring any extra configuration. It is mostly intended to get you up and running quickly, not for production use. A few features here (such as attachment persistence) have not yet been fully implemented.)<br /> * MySQL (fully supported). This is the recommended database for any use beyond experimentation or small standalone applications. See [[Mysql-config]] for configuration information. The OpenSim.ini.example file and other .example files will also have example MySQL configuration strings.&lt;br&gt;<br /> * MSSQL (partially supported - some recent OpenSim features may not yet be implemented)<br /> <br /> More information on database support can be found on the [[OpenSim Database support]] page.<br /> <br /> ==Standalone vs. Grid==<br /> We recommend that you first get OpenSim running in standalone mode before you attempt to connect it to a grid or run your own grid. An OpenSim configuration consists of regions (run by region simulators) and 5 core backend services (which manage users, the grid, assets, inventories, and grid-wide messaging, collectively known as UGAIM).<br /> <br /> A system running in '''standalone mode''' (that is, one with OpenSim.ini where gridmode = false) runs everything (all UGAIM services and one or more regions) in a single executable (OpenSim.exe). It is primarily suited for when a single person is using the system.<br /> <br /> In '''grid mode''', the five services ([[User Server|User]], [[Grid Server|Grid]], [[Asset Server|Asset]], [[Inventory Server|Inventory]], [[Messaging Server|Messaging]], or UGAIM) are not part of the region server. Instead, they can be run separately either on the same machine or spread out across multiple computers. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the core servers for asset, inventory and other data management. <br /> <br /> By subdividing services across separate computers, the overall grid is more tolerant of high load conditions and can support many connecting users at once. Certain situations may lag or crash a region server. By spreading services across several computers, only the one region server may be impacted but other regions on the grid will continue to operate smoothly and responsively.<br /> <br /> Splitting services across computers also allows for specialization of computing hardware for specific purposes:<br /> * The asset server often experiences the highest data transfer load and benefits the most from a fast disk subsystem. This is not so critical for other services, where memory and CPU power is the primary need.<br /> * The region server includes a physics engine which may benefit from the presence of a PCI-Express 3D card for physics acceleration, and which the asset server would not use at all.<br /> <br /> Running in grid mode is more complicated than running in standalone mode. It requires an understanding of UUID, X,Y location, server handshake passwords, estates and estate owners, and a couple of other settings. These require more care and patience to set up.<br /> <br /> If you want to run a grid of your own (either private or public) you would start the core services up before connecting a region simulator. If you want to connect your region server to a grid that someone else is running, you need only start the region server in grid mode (with the necessary security keys and location information mentioned in the last paragraph).<br /> <br /> = Running OpenSim in Standalone mode =<br /> <br /> Running OpenSim in standalone mode is relatively straightforward because '''OpenSim.ini.example''' is already set up to achieve this. All you need to do initially is copy '''OpenSim.ini.example''' to '''OpenSim.ini''' before starting OpenSim and following the rest of the command prompts. Here's the full procedure assuming that you have a binary distribution of OpenSim (if you have a source distribution then you will need to [[Build_Instructions|build]] it first).<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;Go the bin/ directory in the OpenSim distribution&lt;/li&gt;<br /> &lt;li&gt;Copy OpenSim.ini.example to OpenSim.ini&lt;/li&gt;<br /> &lt;li&gt;Start OpenSim&lt;/li&gt;<br /> Windows<br /> OpenSim.exe<br /> Or if using the ODE physics plugin under 64 bit Windows<br /> OpenSim.32BitLaunch.exe<br /> Linux<br /> mono OpenSim.exe<br /> <br /> &lt;li&gt;<br /> When you first start OpenSim in standalone mode, it will ask you several questions at the console. These will set up a single region for you. The configuration will be placed at bin/Regions/Regions.ini which you can then go and edit later on.<br /> <br /> Many of the questions have defaults. Here are some explanations of the questions asked.<br /> <br /> &lt;ul&gt;<br /> &lt;li&gt;'''New region name''' - the name for your region. Don't leave this blank!&lt;/li&gt;<br /> &lt;li&gt;'''Region UUID''' - the unique ID of your region. In pretty much all cases you will want to accept the randomly generated default in the square brackets. The only time when you wouldn't is if you were trying to set up a configuration to point to pre-existing region data. But in this case you are probably better off editing the Regions.ini file directly anyway&lt;/li&gt;<br /> &lt;li&gt;'''Region Location''' - 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). OpenSim regions can be placed anywhere on a 65536 by 65536 grid.<br /> &lt;li&gt;'''Internal IP address''' - This should always be 0.0.0.0 (0.0.0.0 means &quot;listen for connections on any interface&quot;, basically a wildcard) if you want to access this server from the internet or another server on your internal network, this should be the IP&amp;nbsp;address assigned to the OpenSim Server. You should also set up the server to Use a Static IP address, and not DHCP <br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Allow alternate ports''' - This is currently experimental. Please leave it at the default of False.&lt;/li&gt;<br /> &lt;li&gt;'''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) should also work. <br /> &lt;li&gt;'''Master Avatar UUID''' - This is a legacy OpenSim 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.&lt;/li&gt;<br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Master Avatar last name''' - The last name of the master avatar.<br /> &lt;li&gt;'''Master Avatar sandbox password''' - The password of the master avatar.<br /> <br /> Be aware of [http://osgrid.org/forums/viewtopic.php?f=5&amp;t=400&amp;start=0&amp;st=0&amp;sk=t&amp;sd=a loopback] problems when Running viewer &amp;amp; server(s) on the same machine (LAN) by using the &quot;external&quot; configuration. (&lt;u&gt;'''You might notice endless waiting for region handshake'''&lt;/u&gt;.) See also [http://opensimulator.org/wiki/Troubleshooting troubleshoot hints]. If you're having Connectivity problems. [http://opensimulator.org/wiki/Network_Settings Be sure to read the Network Configuration Page]. This is important if you see Region handshake issues&lt;/li&gt;<br /> <br /> See [[Configuring_Regions]] for information about the Regions.ini file that these questions generate.<br /> <br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt; To create a user type &lt;/li&gt;<br /> <br /> create user<br /> <br /> in the server console. This will ask you a series of questions for creating a user (such as first name, last name and password).<br /> <br /> &lt;li&gt; To connect to your new sim with your user, start up a Second Life viewer with the following command line switches: &lt;/li&gt;<br /> <br /> '''Client on same machine as OpenSim:'''<br /> -loginuri http://127.0.0.1:9000/ -loginpage http://127.0.0.1:9000/?method=login <br /> <br /> '''Client on same LAN as OpenSim:'''<br /> -loginuri http://lan_ip:9000/ -loginpage http://lan_ip:9000/?method=login <br /> <br /> '''Client on different machine or internet:'''<br /> -loginuri http://external_ip:9000/ -loginpage http://external_ip:9000/?method=login<br /> <br /> Then enter the user name and password you set up in the previous step and your new user should hopefully login.<br /> <br /> &lt;/ol&gt;<br /> <br /> = Running OpenSim in Grid mode =<br /> <br /> Running OpenSim in grid mode is considerably more complicated. Grid services need to be set up and the region simulator configuration needs to be changed to use these instead of the built-in standalone mode ones.<br /> <br /> ==Configuring the grid services==<br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [[Image:Exclamation.png|left]]<br /> NOTE: As of July 2009, the grid servers are in the process of being redesigned. <br /> Some services are now run in a common 'ROBUST' (Basic Universal Server Technology) server shell <br /> while others are still run as separate legacy servers.<br /> <br /> &lt;u&gt;'''More Details on ROBUST are Here --&amp;gt;'''&lt;/u&gt;[[ROBUST|&lt;u&gt;'''ROBUST'''&lt;/u&gt;]]&lt;u&gt;'''&amp;nbsp;&amp;lt;--&amp;nbsp; including Conversion From UGAIM To UGRM (0.6.6 -&gt; 0.6.7) and UGRM to URM (0.6.7 -&gt; 0.6.8)'''&lt;/u&gt;<br /> |}<br /> <br /> As of OpenSim 0.6.8, R.O.B.U.S.T. has connectors for the asset (A), grid (G) and inventory (I) functionality. The legacy servers are still required for user (U) and messaging (M) functionality. The steps below will get you up and running. We'll assume that your current directory is bin/ within the OpenSim distribution.<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;'''Configure the user server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.UserServer.exe&lt;/li&gt;<br /> &lt;li&gt;You will be asked a number of configuration questions. If the grid servers are all on one machine, most defaults are safe to use. The configuration is stored in the UserServer_Config.xml file which can be changed afterwards if necessary.&lt;/li&gt;<br /> &lt;li&gt;The user server will then load and display it's prompt:&lt;/li&gt;<br /> User#<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure R.O.B.U.S.T.'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Copy OpenSim.Server.ini.example to OpenSim.Server.ini. Don't forget to change ConnectionString for your database settings. (on version 0.6.6 copy OpenSim.Services.ini.example to OpenSim.Services.ini - then use OpenSim.Services instead OpenSim.Server)<br /> &lt;/li&gt;<br /> Linux<br /> bin$ cp OpenSim.Server.ini.example OpenSim.Server.ini<br /> Windows<br /> C:\OpenSim\bin&gt; copy OpenSim.Server.ini.example OpenSim.Server.ini<br /> &lt;li&gt;Start OpenSim.Server.exe&lt;/li&gt;<br /> &lt;li&gt;The server will start up it's asset, inventory and grid components and display the R.O.B.U.S.T prompt:&lt;/li&gt;<br /> R.O.B.U.S.T.#<br /> &lt;li&gt;For more information on the R.O.B.U.S.T. configuration file and more information if you are migrating from an earlier release of OpenSim, refer to [[R.O.B.U.S.T.]]&lt;/li&gt;<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure the messaging server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.MessagingServer.exe&lt;/li&gt;<br /> &lt;li&gt;Answer the configuration questions. Again, if all servers are run on the same machine, it's safe to press enter for all questions. The configuration is stored in MessagingServer_Config.xml.&lt;/li&gt;<br /> &lt;li&gt;The server will start and present you with it's prompt:&lt;/li&gt;<br /> Messaging#<br /> &lt;/ul&gt;<br /> <br /> &lt;/ol&gt; <br /> <br /> For information on running the legacy servers, particularly if you're using an older version of before 0.6.7 that doesn't contain the ROBUST framework, see [[LegacyServers]]<br /> <br /> === Summary of commands for running grid service executables ===<br /> <br /> '''&lt;u&gt;Windows&lt;/u&gt;'''<br /> cd bin<br /> OpenSim.Grid.UserServer.exe<br /> OpenSim.Server.exe<br /> OpenSim.Grid.MessagingServer.exe<br /> <br /> '''&lt;u&gt;Linux / Mac OS X&lt;/u&gt;'''<br /> cd bin<br /> mono OpenSim.Grid.UserServer.exe<br /> mono OpenSim.Server.exe<br /> mono OpenSim.Grid.MessagingServer.exe<br /> <br /> ==Configuring regions==<br /> <br /> When first run, a new OpenSim installation will ask you a series of questions to set up one region. If you want to change these settings or set up multiple regions, please see [[Configuring_Regions]]<br /> <br /> ==Configuring and Starting the region simulator==<br /> &lt;ol&gt;<br /> &lt;li&gt;Find the [Architecture] section, comment out the line that says&lt;/li&gt;<br /> Include-Standalone = &quot;config-include/Standalone.ini&quot;<br /> and uncomment the line saying <br /> Include-Grid = &quot;config-include/Grid.ini<br /> <br /> &lt;li&gt;save OpenSim.ini, and go into the config-include directory.&lt;/li&gt;<br /> &lt;li&gt;copy the following files&lt;/li&gt;<br /> GridCommon.ini.example to GridCommon.ini<br /> CenomeCache.ini.example to CenomeCache.ini<br /> FlotsamCache.ini.example to FlotsamCache.ini<br /> <br /> &lt;li&gt;Open all these files (Grid.ini, GridCommon.ini, CenomeCache.ini and FlotsamCache.ini) and edit to suit your needs&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be ready to start up your sim. The mode that OpenSim.exe starts in is normally controlled by a setting in your OpenSim.ini. It defaults to standalone mode if that setting is not specified or the file is not found. If you wish, you can force opensim to start in gridmode on the command line as follows:&lt;/li&gt;<br /> OpenSim.exe -gridmode=true<br /> or if using the ODE physics plugin under 64 bit Windows<br /> OpenSim.32BitLaunch.exe<br /> or:<br /> mono OpenSim.exe -gridmode=true<br /> if you're using Mono under Linux or Mac OSX. <br /> <br /> With any luck, everything will come up without fatal errors.<br /> <br /> If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br /> &lt;tt&gt;ulimit -s 262144&lt;/tt&gt; Or, run the opensim-ode.sh to start up OpenSimulator.<br /> <br /> &lt;li&gt;Go to the UserServer console, and type 'create user' to create a new avatar. It will prompt you for the name and password, and the X and Y of the sim that should be his home location. Use 1000 and 1000, or wherever you told your sim to live when you brought it up in standalone mode. At the console of any of these servers, you should be able to type 'help' to get a list of commands.&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be able to connect to your new grid with your secondlife client. You need to tell your client to point at the UserServer rather than directly at the sim, though:&lt;/li&gt;<br /> secondlife -loginuri http://127.0.0.1:8002/<br /> 8002 is the default port for the UserServer, and that IP address should be changed to the server you are running the UserServer on, if they are not all on the same box. Happy OpenSimming!&lt;br&gt;<br /> ''Note: if you are using Windows Vista, remember to start servers as Admin. If not it will prompt you an error in console like &quot;Error - Access denied&quot;''<br /> &lt;/ol&gt;<br /> <br /> ==Attaching your sim to someone else's grid==<br /> To set up the region server (i.e., &lt;tt&gt;OpenSim.exe&lt;/tt&gt;) to connect to an external grid, you should edit the &lt;tt&gt;OpenSim.ini&lt;/tt&gt; file in the &lt;tt&gt;bin&lt;/tt&gt; directory. In that file, there is a &lt;tt&gt;[Network]&lt;/tt&gt; section with URLs for the grid, user, and asset servers, as well as send and receive keys (for a basic level of security). The addresses and send/receive keys will vary depending on the grid you are connecting to, and the grid operator should tell you what values to use.<br /> <br /> The other file you may have to change is in your &lt;tt&gt;bin/Regions&lt;/tt&gt; directory. This is where your individual region config files are. If you only have one region, it will by default be called &lt;tt&gt;Regions.ini&lt;/tt&gt; in OpenSim 0.6.7 and later and &lt;tt&gt;regions.xml&lt;/tt&gt; in OpenSim 0.6.6 and earlier.<br /> <br /> This can be edited with any text editor. The grid owner may tell you what X and Y location you can place your sim at (you can't have multiple sims at the same location on the grid). If so, the fields you will need to change in this file are &lt;tt&gt;sim_location_x&lt;/tt&gt; and &lt;tt&gt;sim_location_y&lt;/tt&gt;. And the &lt;tt&gt;external_host_name&lt;/tt&gt; should be set to the hostname or IP address of your simulation server (i.e., the machine that is running &lt;tt&gt;OpenSim.exe&lt;/tt&gt;).<br /> A list of public grids that you can attach your sim to is at [[OpenSim: Grids]]<br /> <br /> =Further notes=<br /> <br /> ==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br /> [[Image:Exclamation.png|left]]<br /> As of OpenSim 0.6.7, the default physics engine for OpenSim was changed to the ODE engine. This is because ODE is by far the most advanced physics engine plugin currently in OpenSim. Unfortunately, it has the drawback in that it's library is not compilable under 64bit in Windows. Therefore, 64 bit Windows users may need to run <br /> <br /> OpenSim.32BitLaunch.exe<br /> <br /> instead of <br /> <br /> OpenSim.exe<br /> <br /> To launch their region simulator.<br /> <br /> 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.<br /> <br /> ==Note About Mono==<br /> 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. <br /> <br /> 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.<br /> <br /> For example: $ export MONO_THREADS_PER_CPU=125<br /> <br /> == Legacy Configuration Information ==<br /> These are some pages containing some legacy configuration information of unknown accuracy.<br /> <br /> [[OpenSim 0.6.6 legacy configuration information]]<br /> <br /> <br /> == Additional Configuration Tasks (for advanced users) ==<br /> <br /> ===OpenSim.exe command line options===<br /> OpenSim.exe has command line options which allow you to perform actions such as reading configuratio nfiles from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br /> <br /> ===Script engine===<br /> OpenSim supports multiple script engines. See [[ScriptEngines]] for details. If you don't know what this means then the default script engine will be fine.<br /> <br /> ===Permissions Configuration===<br /> OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br /> <br /> === Logging ===<br /> By default, OpenSim logs information to a file called OpenSim.log in the bin directory. See [[Logging]] for details on how to further configure this if required.<br /> <br /> === Configuration of region modules ===<br /> * [[IRCBridgeModule]]<br /> * [[Freeswitch_Module]]<br /> * [[Offline Messaging]]<br /> <br /> === Configuration of Metaverse Exchange Protocol (MXP) ===<br /> * [[Metaverse Exchange Protocol]]<br /> <br /> === Configuration of Web Server and Pages===<br /> OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br /> * [[External Files]]<br /> * [[Internally Generated]]<br /> <br /> [[Category:Configuration]]</div>

Dale Mahalko http://opensimulator.org/wiki/Configuration 2010-04-04T04:19:02Z

<p>Dale Mahalko: /* Running OpenSim in Standalone mode */ typo &quot;straitforward&quot; -&gt; &quot;straightforward&quot;</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> ==OpenSim simulator configuration file==<br /> The region simulator configuration is managed using a file called [[OpenSim.ini]]. This file is used regardless of whether the sim is running in standalone or grid mode. This file includes some additional configuration information from the config-include/ directory. Detailed information on the options available for setttings in this file can be found [[OpenSim.ini|here]].<br /> Please note, that the name OpenSim.ini can be changed via command line arguments (see above). Also, note that the default download does not include an OpenSim.ini file, but rather provides an example file. To get started editing your ini file, please cd into opensim/bin/ and copy OpenSim.ini.example to OpenSim.ini.<br /> <br /> It is also possible to distribute the inifile settings over two files. This is useful if you want to run several OpenSim processes where most of your settings are identical but some settings differ.<br /> The master file is read first, then the inifile is read. Settings given in the inifile overrule settings given in the master file.<br /> The master file has the same format and the same keywords as the inifile, so the same documentation applies.<br /> <br /> ==Database==<br /> Opensim's supports the following database-engines:<br /> * SQLite (default - a lightweight database that comes bundled with OpenSim and can be used without requiring any extra configuration. It is mostly intended to get you up and running quickly, not for production use. A few features here (such as attachment persistence) have not yet been fully implemented.)<br /> * MySQL (fully supported). This is the recommended database for any use beyond experimentation or small standalone applications. See [[Mysql-config]] for configuration information. The OpenSim.ini.example file and other .example files will also have example MySQL configuration strings.&lt;br&gt;<br /> * MSSQL (partially supported - some recent OpenSim features may not yet be implemented)<br /> <br /> More information on database support can be found on the [[OpenSim Database support]] page.<br /> <br /> ==Standalone vs. Grid==<br /> We recommend that you first get OpenSim running in standalone mode before you attempt to connect it to a grid or run your own grid. An OpenSim configuration consists of regions (run by region simulators) and 5 core backend services (which manage users, the grid, assets, inventories, and grid-wide messaging, collectively known as UGAIM).<br /> <br /> A system running in '''standalone mode''' (that is, one with OpenSim.ini where gridmode = false) runs everything (all UGAIM services and one or more regions) in a single executable (OpenSim.exe). It is primarily suited for when a single person is using the system.<br /> <br /> In '''grid mode''', the five services ([[User Server|User]], [[Grid Server|Grid]], [[Asset Server|Asset]], [[Inventory Server|Inventory]], [[Messaging Server|Messaging]], or UGAIM) are not part of the region server. Instead, they can be run separately either on the same machine or spread out across multiple computers. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the core servers for asset, inventory and other data management. <br /> <br /> By subdividing services across separate computers, the overall grid is more tolerant of high load conditions and can support many connecting users at once. Certain situations may lag or crash a region server. By spreading services across several computers, only the one region server may be impacted but other regions on the grid will continue to operate smoothly and responsively.<br /> <br /> Splitting services across computers also allows for specialization of computing hardware for specific purposes:<br /> * The asset server often experiences the highest data transfer load and benefits the most from a fast disk subsystem. This is not so critical for other services, where memory and CPU power is the primary need.<br /> * The region server includes a physics engine which may benefit from the presence of a PCI-Express 3D card for physics acceleration, and which the asset server would not use at all.<br /> <br /> Running in grid mode is more complicated than running in standalone mode. It requires an understanding of UUID, X,Y location, server handshake passwords, estates and estate owners, and a couple of other settings. These require more care and patience to set up.<br /> <br /> If you want to run a grid of your own (either private or public) you would start the core services up before connecting a region simulator. If you want to connect your region server to a grid that someone else is running, you need only start the region server in grid mode (with the necessary security keys and location information mentioned in the last paragraph).<br /> <br /> = Running OpenSim in Standalone mode =<br /> <br /> Running OpenSim in standalone mode is relatively straightforward because OpenSim.ini.example is already set up to achieve this. All you need to do initially is copy OpenSim.ini.example to OpenSim.ini before starting OpenSim and following the rest of the command prompts. Here's the full procedure assuming that you have a binary distribution of OpenSim (if you have a source distribution then you will need to [[Build_Instructions|build]] it first).<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;Go the bin/ directory in the OpenSim distribution&lt;/li&gt;<br /> &lt;li&gt;Copy OpenSim.ini.example to OpenSim.ini&lt;/li&gt;<br /> &lt;li&gt;Start OpenSim&lt;/li&gt;<br /> Windows<br /> OpenSim.exe<br /> Or if using the ODE physics plugin under 64 bit Windows<br /> OpenSim.32BitLaunch.exe<br /> Linux<br /> mono OpenSim.exe<br /> <br /> &lt;li&gt;<br /> When you first start OpenSim in standalone mode, it will ask you several questions at the console. These will set up a single region for you. The configuration will be placed at bin/Regions/Regions.ini which you can then go and edit later on.<br /> <br /> Many of the questions have defaults. Here are some explanations of the questions asked.<br /> <br /> &lt;ul&gt;<br /> &lt;li&gt;'''New region name''' - the name for your region. Don't leave this blank!&lt;/li&gt;<br /> &lt;li&gt;'''Region UUID''' - the unique ID of your region. In pretty much all cases you will want to accept the randomly generated default in the square brackets. The only time when you wouldn't is if you were trying to set up a configuration to point to pre-existing region data. But in this case you are probably better off editing the Regions.ini file directly anyway&lt;/li&gt;<br /> &lt;li&gt;'''Region Location''' - 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). OpenSim regions can be placed anywhere on a 65536 by 65536 grid.<br /> &lt;li&gt;'''Internal IP address''' - This should always be 0.0.0.0 (0.0.0.0 means &quot;listen for connections on any interface&quot;, basically a wildcard) if you want to access this server from the internet or another server on your internal network, this should be the IP&amp;nbsp;address assigned to the OpenSim Server. You should also set up the server to Use a Static IP address, and not DHCP <br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Allow alternate ports''' - This is currently experimental. Please leave it at the default of False.&lt;/li&gt;<br /> &lt;li&gt;'''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) should also work. <br /> &lt;li&gt;'''Master Avatar UUID''' - This is a legacy OpenSim 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.&lt;/li&gt;<br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Master Avatar last name''' - The last name of the master avatar.<br /> &lt;li&gt;'''Master Avatar sandbox password''' - The password of the master avatar.<br /> <br /> Be aware of [http://osgrid.org/forums/viewtopic.php?f=5&amp;t=400&amp;start=0&amp;st=0&amp;sk=t&amp;sd=a loopback] problems when Running viewer &amp;amp; server(s) on the same machine (LAN) by using the &quot;external&quot; configuration. (&lt;u&gt;'''You might notice endless waiting for region handshake'''&lt;/u&gt;.) See also [http://opensimulator.org/wiki/Troubleshooting troubleshoot hints]. If you're having Connectivity problems. [http://opensimulator.org/wiki/Network_Settings Be sure to read the Network Configuration Page]. This is important if you see Region handshake issues&lt;/li&gt;<br /> <br /> See [[Configuring_Regions]] for information about the Regions.ini file that these questions generate.<br /> <br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt; To create a user type &lt;/li&gt;<br /> <br /> create user<br /> <br /> in the server console. This will ask you a series of questions for creating a user (such as first name, last name and password).<br /> <br /> &lt;li&gt; To connect to your new sim with your user, start up a Second Life viewer with the following command line switches: &lt;/li&gt;<br /> <br /> '''Client on same machine as OpenSim:'''<br /> -loginuri http://127.0.0.1:9000/ -loginpage http://127.0.0.1:9000/?method=login <br /> <br /> '''Client on same LAN as OpenSim:'''<br /> -loginuri http://lan_ip:9000/ -loginpage http://lan_ip:9000/?method=login <br /> <br /> '''Client on different machine or internet:'''<br /> -loginuri http://external_ip:9000/ -loginpage http://external_ip:9000/?method=login<br /> <br /> Then enter the user name and password you set up in the previous step and your new user should hopefully login.<br /> <br /> &lt;/ol&gt;<br /> <br /> = Running OpenSim in Grid mode =<br /> <br /> Running OpenSim in grid mode is considerably more complicated. Grid services need to be set up and the region simulator configuration needs to be changed to use these instead of the built-in standalone mode ones.<br /> <br /> ==Configuring the grid services==<br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [[Image:Exclamation.png|left]]<br /> NOTE: As of July 2009, the grid servers are in the process of being redesigned. <br /> Some services are now run in a common 'ROBUST' (Basic Universal Server Technology) server shell <br /> while others are still run as separate legacy servers.<br /> <br /> &lt;u&gt;'''More Details on ROBUST are Here --&amp;gt;'''&lt;/u&gt;[[ROBUST|&lt;u&gt;'''ROBUST'''&lt;/u&gt;]]&lt;u&gt;'''&amp;nbsp;&amp;lt;--&amp;nbsp; including Conversion From UGAIM To UGRM (0.6.6 -&gt; 0.6.7) and UGRM to URM (0.6.7 -&gt; 0.6.8)'''&lt;/u&gt;<br /> |}<br /> <br /> As of OpenSim 0.6.8, R.O.B.U.S.T. has connectors for the asset (A), grid (G) and inventory (I) functionality. The legacy servers are still required for user (U) and messaging (M) functionality. The steps below will get you up and running. We'll assume that your current directory is bin/ within the OpenSim distribution.<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;'''Configure the user server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.UserServer.exe&lt;/li&gt;<br /> &lt;li&gt;You will be asked a number of configuration questions. If the grid servers are all on one machine, most defaults are safe to use. The configuration is stored in the UserServer_Config.xml file which can be changed afterwards if necessary.&lt;/li&gt;<br /> &lt;li&gt;The user server will then load and display it's prompt:&lt;/li&gt;<br /> User#<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure R.O.B.U.S.T.'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Copy OpenSim.Server.ini.example to OpenSim.Server.ini. Don't forget to change ConnectionString for your database settings. (on version 0.6.6 copy OpenSim.Services.ini.example to OpenSim.Services.ini - then use OpenSim.Services instead OpenSim.Server)<br /> &lt;/li&gt;<br /> Linux<br /> bin$ cp OpenSim.Server.ini.example OpenSim.Server.ini<br /> Windows<br /> C:\OpenSim\bin&gt; copy OpenSim.Server.ini.example OpenSim.Server.ini<br /> &lt;li&gt;Start OpenSim.Server.exe&lt;/li&gt;<br /> &lt;li&gt;The server will start up it's asset, inventory and grid components and display the R.O.B.U.S.T prompt:&lt;/li&gt;<br /> R.O.B.U.S.T.#<br /> &lt;li&gt;For more information on the R.O.B.U.S.T. configuration file and more information if you are migrating from an earlier release of OpenSim, refer to [[R.O.B.U.S.T.]]&lt;/li&gt;<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure the messaging server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.MessagingServer.exe&lt;/li&gt;<br /> &lt;li&gt;Answer the configuration questions. Again, if all servers are run on the same machine, it's safe to press enter for all questions. The configuration is stored in MessagingServer_Config.xml.&lt;/li&gt;<br /> &lt;li&gt;The server will start and present you with it's prompt:&lt;/li&gt;<br /> Messaging#<br /> &lt;/ul&gt;<br /> <br /> &lt;/ol&gt; <br /> <br /> For information on running the legacy servers, particularly if you're using an older version of before 0.6.7 that doesn't contain the ROBUST framework, see [[LegacyServers]]<br /> <br /> === Summary of commands for running grid service executables ===<br /> <br /> '''&lt;u&gt;Windows&lt;/u&gt;'''<br /> cd bin<br /> OpenSim.Grid.UserServer.exe<br /> OpenSim.Server.exe<br /> OpenSim.Grid.MessagingServer.exe<br /> <br /> '''&lt;u&gt;Linux / Mac OS X&lt;/u&gt;'''<br /> cd bin<br /> mono OpenSim.Grid.UserServer.exe<br /> mono OpenSim.Server.exe<br /> mono OpenSim.Grid.MessagingServer.exe<br /> <br /> ==Configuring regions==<br /> <br /> When first run, a new OpenSim installation will ask you a series of questions to set up one region. If you want to change these settings or set up multiple regions, please see [[Configuring_Regions]]<br /> <br /> ==Configuring and Starting the region simulator==<br /> &lt;ol&gt;<br /> &lt;li&gt;Find the [Architecture] section, comment out the line that says&lt;/li&gt;<br /> Include-Standalone = &quot;config-include/Standalone.ini&quot;<br /> and uncomment the line saying <br /> Include-Grid = &quot;config-include/Grid.ini<br /> <br /> &lt;li&gt;save OpenSim.ini, and go into the config-include directory.&lt;/li&gt;<br /> &lt;li&gt;copy the following files&lt;/li&gt;<br /> GridCommon.ini.example to GridCommon.ini<br /> CenomeCache.ini.example to CenomeCache.ini<br /> FlotsamCache.ini.example to FlotsamCache.ini<br /> <br /> &lt;li&gt;Open all these files (Grid.ini, GridCommon.ini, CenomeCache.ini and FlotsamCache.ini) and edit to suit your needs&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be ready to start up your sim. The mode that OpenSim.exe starts in is normally controlled by a setting in your OpenSim.ini. It defaults to standalone mode if that setting is not specified or the file is not found. If you wish, you can force opensim to start in gridmode on the command line as follows:&lt;/li&gt;<br /> OpenSim.exe -gridmode=true<br /> or if using the ODE physics plugin under 64 bit Windows<br /> OpenSim.32BitLaunch.exe<br /> or:<br /> mono OpenSim.exe -gridmode=true<br /> if you're using Mono under Linux or Mac OSX. <br /> <br /> With any luck, everything will come up without fatal errors.<br /> <br /> If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br /> &lt;tt&gt;ulimit -s 262144&lt;/tt&gt; Or, run the opensim-ode.sh to start up OpenSimulator.<br /> <br /> &lt;li&gt;Go to the UserServer console, and type 'create user' to create a new avatar. It will prompt you for the name and password, and the X and Y of the sim that should be his home location. Use 1000 and 1000, or wherever you told your sim to live when you brought it up in standalone mode. At the console of any of these servers, you should be able to type 'help' to get a list of commands.&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be able to connect to your new grid with your secondlife client. You need to tell your client to point at the UserServer rather than directly at the sim, though:&lt;/li&gt;<br /> secondlife -loginuri http://127.0.0.1:8002/<br /> 8002 is the default port for the UserServer, and that IP address should be changed to the server you are running the UserServer on, if they are not all on the same box. Happy OpenSimming!&lt;br&gt;<br /> ''Note: if you are using Windows Vista, remember to start servers as Admin. If not it will prompt you an error in console like &quot;Error - Access denied&quot;''<br /> &lt;/ol&gt;<br /> <br /> ==Attaching your sim to someone else's grid==<br /> To set up the region server (i.e., &lt;tt&gt;OpenSim.exe&lt;/tt&gt;) to connect to an external grid, you should edit the &lt;tt&gt;OpenSim.ini&lt;/tt&gt; file in the &lt;tt&gt;bin&lt;/tt&gt; directory. In that file, there is a &lt;tt&gt;[Network]&lt;/tt&gt; section with URLs for the grid, user, and asset servers, as well as send and receive keys (for a basic level of security). The addresses and send/receive keys will vary depending on the grid you are connecting to, and the grid operator should tell you what values to use.<br /> <br /> The other file you may have to change is in your &lt;tt&gt;bin/Regions&lt;/tt&gt; directory. This is where your individual region config files are. If you only have one region, it will by default be called &lt;tt&gt;Regions.ini&lt;/tt&gt; in OpenSim 0.6.7 and later and &lt;tt&gt;regions.xml&lt;/tt&gt; in OpenSim 0.6.6 and earlier.<br /> <br /> This can be edited with any text editor. The grid owner may tell you what X and Y location you can place your sim at (you can't have multiple sims at the same location on the grid). If so, the fields you will need to change in this file are &lt;tt&gt;sim_location_x&lt;/tt&gt; and &lt;tt&gt;sim_location_y&lt;/tt&gt;. And the &lt;tt&gt;external_host_name&lt;/tt&gt; should be set to the hostname or IP address of your simulation server (i.e., the machine that is running &lt;tt&gt;OpenSim.exe&lt;/tt&gt;).<br /> A list of public grids that you can attach your sim to is at [[OpenSim: Grids]]<br /> <br /> =Further notes=<br /> <br /> ==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br /> [[Image:Exclamation.png|left]]<br /> As of OpenSim 0.6.7, the default physics engine for OpenSim was changed to the ODE engine. This is because ODE is by far the most advanced physics engine plugin currently in OpenSim. Unfortunately, it has the drawback in that it's library is not compilable under 64bit in Windows. Therefore, 64 bit Windows users may need to run <br /> <br /> OpenSim.32BitLaunch.exe<br /> <br /> instead of <br /> <br /> OpenSim.exe<br /> <br /> To launch their region simulator.<br /> <br /> 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.<br /> <br /> ==Note About Mono==<br /> 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. <br /> <br /> 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.<br /> <br /> For example: $ export MONO_THREADS_PER_CPU=125<br /> <br /> == Legacy Configuration Information ==<br /> These are some pages containing some legacy configuration information of unknown accuracy.<br /> <br /> [[OpenSim 0.6.6 legacy configuration information]]<br /> <br /> <br /> == Additional Configuration Tasks (for advanced users) ==<br /> <br /> ===OpenSim.exe command line options===<br /> OpenSim.exe has command line options which allow you to perform actions such as reading configuratio nfiles from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br /> <br /> ===Script engine===<br /> OpenSim supports multiple script engines. See [[ScriptEngines]] for details. If you don't know what this means then the default script engine will be fine.<br /> <br /> ===Permissions Configuration===<br /> OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br /> <br /> === Logging ===<br /> By default, OpenSim logs information to a file called OpenSim.log in the bin directory. See [[Logging]] for details on how to further configure this if required.<br /> <br /> === Configuration of region modules ===<br /> * [[IRCBridgeModule]]<br /> * [[Freeswitch_Module]]<br /> * [[Offline Messaging]]<br /> <br /> === Configuration of Metaverse Exchange Protocol (MXP) ===<br /> * [[Metaverse Exchange Protocol]]<br /> <br /> === Configuration of Web Server and Pages===<br /> OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br /> * [[External Files]]<br /> * [[Internally Generated]]<br /> <br /> [[Category:Configuration]]</div>

Dale Mahalko http://opensimulator.org/wiki/Configuration 2010-04-04T04:16:10Z

<p>Dale Mahalko: /* Configuring the grid services */ Date the infobox on ROBUST.. was added to page in July 2009, so put that in article</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> ==OpenSim simulator configuration file==<br /> The region simulator configuration is managed using a file called [[OpenSim.ini]]. This file is used regardless of whether the sim is running in standalone or grid mode. This file includes some additional configuration information from the config-include/ directory. Detailed information on the options available for setttings in this file can be found [[OpenSim.ini|here]].<br /> Please note, that the name OpenSim.ini can be changed via command line arguments (see above). Also, note that the default download does not include an OpenSim.ini file, but rather provides an example file. To get started editing your ini file, please cd into opensim/bin/ and copy OpenSim.ini.example to OpenSim.ini.<br /> <br /> It is also possible to distribute the inifile settings over two files. This is useful if you want to run several OpenSim processes where most of your settings are identical but some settings differ.<br /> The master file is read first, then the inifile is read. Settings given in the inifile overrule settings given in the master file.<br /> The master file has the same format and the same keywords as the inifile, so the same documentation applies.<br /> <br /> ==Database==<br /> Opensim's supports the following database-engines:<br /> * SQLite (default - a lightweight database that comes bundled with OpenSim and can be used without requiring any extra configuration. It is mostly intended to get you up and running quickly, not for production use. A few features here (such as attachment persistence) have not yet been fully implemented.)<br /> * MySQL (fully supported). This is the recommended database for any use beyond experimentation or small standalone applications. See [[Mysql-config]] for configuration information. The OpenSim.ini.example file and other .example files will also have example MySQL configuration strings.&lt;br&gt;<br /> * MSSQL (partially supported - some recent OpenSim features may not yet be implemented)<br /> <br /> More information on database support can be found on the [[OpenSim Database support]] page.<br /> <br /> ==Standalone vs. Grid==<br /> We recommend that you first get OpenSim running in standalone mode before you attempt to connect it to a grid or run your own grid. An OpenSim configuration consists of regions (run by region simulators) and 5 core backend services (which manage users, the grid, assets, inventories, and grid-wide messaging, collectively known as UGAIM).<br /> <br /> A system running in '''standalone mode''' (that is, one with OpenSim.ini where gridmode = false) runs everything (all UGAIM services and one or more regions) in a single executable (OpenSim.exe). It is primarily suited for when a single person is using the system.<br /> <br /> In '''grid mode''', the five services ([[User Server|User]], [[Grid Server|Grid]], [[Asset Server|Asset]], [[Inventory Server|Inventory]], [[Messaging Server|Messaging]], or UGAIM) are not part of the region server. Instead, they can be run separately either on the same machine or spread out across multiple computers. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the core servers for asset, inventory and other data management. <br /> <br /> By subdividing services across separate computers, the overall grid is more tolerant of high load conditions and can support many connecting users at once. Certain situations may lag or crash a region server. By spreading services across several computers, only the one region server may be impacted but other regions on the grid will continue to operate smoothly and responsively.<br /> <br /> Splitting services across computers also allows for specialization of computing hardware for specific purposes:<br /> * The asset server often experiences the highest data transfer load and benefits the most from a fast disk subsystem. This is not so critical for other services, where memory and CPU power is the primary need.<br /> * The region server includes a physics engine which may benefit from the presence of a PCI-Express 3D card for physics acceleration, and which the asset server would not use at all.<br /> <br /> Running in grid mode is more complicated than running in standalone mode. It requires an understanding of UUID, X,Y location, server handshake passwords, estates and estate owners, and a couple of other settings. These require more care and patience to set up.<br /> <br /> If you want to run a grid of your own (either private or public) you would start the core services up before connecting a region simulator. If you want to connect your region server to a grid that someone else is running, you need only start the region server in grid mode (with the necessary security keys and location information mentioned in the last paragraph).<br /> <br /> = Running OpenSim in Standalone mode =<br /> <br /> Running OpenSim in standalone mode is relatively straitforward because OpenSim.ini.example is already set up to achieve this. All you need to do initially is copy OpenSim.ini.example to OpenSim.ini before starting OpenSim and following the rest of the command prompts. Here's the full procedure assuming that you have a binary distribution of OpenSim (if you have a source distribution then you will need to [[Build_Instructions|build]] it first).<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;Go the bin/ directory in the OpenSim distribution&lt;/li&gt;<br /> &lt;li&gt;Copy OpenSim.ini.example to OpenSim.ini&lt;/li&gt;<br /> &lt;li&gt;Start OpenSim&lt;/li&gt;<br /> Windows<br /> OpenSim.exe<br /> Or if using the ODE physics plugin under 64 bit Windows<br /> OpenSim.32BitLaunch.exe<br /> Linux<br /> mono OpenSim.exe<br /> <br /> &lt;li&gt;<br /> When you first start OpenSim in standalone mode, it will ask you several questions at the console. These will set up a single region for you. The configuration will be placed at bin/Regions/Regions.ini which you can then go and edit later on.<br /> <br /> Many of the questions have defaults. Here are some explanations of the questions asked.<br /> <br /> &lt;ul&gt;<br /> &lt;li&gt;'''New region name''' - the name for your region. Don't leave this blank!&lt;/li&gt;<br /> &lt;li&gt;'''Region UUID''' - the unique ID of your region. In pretty much all cases you will want to accept the randomly generated default in the square brackets. The only time when you wouldn't is if you were trying to set up a configuration to point to pre-existing region data. But in this case you are probably better off editing the Regions.ini file directly anyway&lt;/li&gt;<br /> &lt;li&gt;'''Region Location''' - 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). OpenSim regions can be placed anywhere on a 65536 by 65536 grid.<br /> &lt;li&gt;'''Internal IP address''' - This should always be 0.0.0.0 (0.0.0.0 means &quot;listen for connections on any interface&quot;, basically a wildcard) if you want to access this server from the internet or another server on your internal network, this should be the IP&amp;nbsp;address assigned to the OpenSim Server. You should also set up the server to Use a Static IP address, and not DHCP <br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Allow alternate ports''' - This is currently experimental. Please leave it at the default of False.&lt;/li&gt;<br /> &lt;li&gt;'''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) should also work. <br /> &lt;li&gt;'''Master Avatar UUID''' - This is a legacy OpenSim 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.&lt;/li&gt;<br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Master Avatar last name''' - The last name of the master avatar.<br /> &lt;li&gt;'''Master Avatar sandbox password''' - The password of the master avatar.<br /> <br /> Be aware of [http://osgrid.org/forums/viewtopic.php?f=5&amp;t=400&amp;start=0&amp;st=0&amp;sk=t&amp;sd=a loopback] problems when Running viewer &amp;amp; server(s) on the same machine (LAN) by using the &quot;external&quot; configuration. (&lt;u&gt;'''You might notice endless waiting for region handshake'''&lt;/u&gt;.) See also [http://opensimulator.org/wiki/Troubleshooting troubleshoot hints]. If you're having Connectivity problems. [http://opensimulator.org/wiki/Network_Settings Be sure to read the Network Configuration Page]. This is important if you see Region handshake issues&lt;/li&gt;<br /> <br /> See [[Configuring_Regions]] for information about the Regions.ini file that these questions generate.<br /> <br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt; To create a user type &lt;/li&gt;<br /> <br /> create user<br /> <br /> in the server console. This will ask you a series of questions for creating a user (such as first name, last name and password).<br /> <br /> &lt;li&gt; To connect to your new sim with your user, start up a Second Life viewer with the following command line switches: &lt;/li&gt;<br /> <br /> '''Client on same machine as OpenSim:'''<br /> -loginuri http://127.0.0.1:9000/ -loginpage http://127.0.0.1:9000/?method=login <br /> <br /> '''Client on same LAN as OpenSim:'''<br /> -loginuri http://lan_ip:9000/ -loginpage http://lan_ip:9000/?method=login <br /> <br /> '''Client on different machine or internet:'''<br /> -loginuri http://external_ip:9000/ -loginpage http://external_ip:9000/?method=login<br /> <br /> Then enter the user name and password you set up in the previous step and your new user should hopefully login.<br /> <br /> &lt;/ol&gt;<br /> <br /> = Running OpenSim in Grid mode =<br /> <br /> Running OpenSim in grid mode is considerably more complicated. Grid services need to be set up and the region simulator configuration needs to be changed to use these instead of the built-in standalone mode ones.<br /> <br /> ==Configuring the grid services==<br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [[Image:Exclamation.png|left]]<br /> NOTE: As of July 2009, the grid servers are in the process of being redesigned. <br /> Some services are now run in a common 'ROBUST' (Basic Universal Server Technology) server shell <br /> while others are still run as separate legacy servers.<br /> <br /> &lt;u&gt;'''More Details on ROBUST are Here --&amp;gt;'''&lt;/u&gt;[[ROBUST|&lt;u&gt;'''ROBUST'''&lt;/u&gt;]]&lt;u&gt;'''&amp;nbsp;&amp;lt;--&amp;nbsp; including Conversion From UGAIM To UGRM (0.6.6 -&gt; 0.6.7) and UGRM to URM (0.6.7 -&gt; 0.6.8)'''&lt;/u&gt;<br /> |}<br /> <br /> As of OpenSim 0.6.8, R.O.B.U.S.T. has connectors for the asset (A), grid (G) and inventory (I) functionality. The legacy servers are still required for user (U) and messaging (M) functionality. The steps below will get you up and running. We'll assume that your current directory is bin/ within the OpenSim distribution.<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;'''Configure the user server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.UserServer.exe&lt;/li&gt;<br /> &lt;li&gt;You will be asked a number of configuration questions. If the grid servers are all on one machine, most defaults are safe to use. The configuration is stored in the UserServer_Config.xml file which can be changed afterwards if necessary.&lt;/li&gt;<br /> &lt;li&gt;The user server will then load and display it's prompt:&lt;/li&gt;<br /> User#<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure R.O.B.U.S.T.'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Copy OpenSim.Server.ini.example to OpenSim.Server.ini. Don't forget to change ConnectionString for your database settings. (on version 0.6.6 copy OpenSim.Services.ini.example to OpenSim.Services.ini - then use OpenSim.Services instead OpenSim.Server)<br /> &lt;/li&gt;<br /> Linux<br /> bin$ cp OpenSim.Server.ini.example OpenSim.Server.ini<br /> Windows<br /> C:\OpenSim\bin&gt; copy OpenSim.Server.ini.example OpenSim.Server.ini<br /> &lt;li&gt;Start OpenSim.Server.exe&lt;/li&gt;<br /> &lt;li&gt;The server will start up it's asset, inventory and grid components and display the R.O.B.U.S.T prompt:&lt;/li&gt;<br /> R.O.B.U.S.T.#<br /> &lt;li&gt;For more information on the R.O.B.U.S.T. configuration file and more information if you are migrating from an earlier release of OpenSim, refer to [[R.O.B.U.S.T.]]&lt;/li&gt;<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure the messaging server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.MessagingServer.exe&lt;/li&gt;<br /> &lt;li&gt;Answer the configuration questions. Again, if all servers are run on the same machine, it's safe to press enter for all questions. The configuration is stored in MessagingServer_Config.xml.&lt;/li&gt;<br /> &lt;li&gt;The server will start and present you with it's prompt:&lt;/li&gt;<br /> Messaging#<br /> &lt;/ul&gt;<br /> <br /> &lt;/ol&gt; <br /> <br /> For information on running the legacy servers, particularly if you're using an older version of before 0.6.7 that doesn't contain the ROBUST framework, see [[LegacyServers]]<br /> <br /> === Summary of commands for running grid service executables ===<br /> <br /> '''&lt;u&gt;Windows&lt;/u&gt;'''<br /> cd bin<br /> OpenSim.Grid.UserServer.exe<br /> OpenSim.Server.exe<br /> OpenSim.Grid.MessagingServer.exe<br /> <br /> '''&lt;u&gt;Linux / Mac OS X&lt;/u&gt;'''<br /> cd bin<br /> mono OpenSim.Grid.UserServer.exe<br /> mono OpenSim.Server.exe<br /> mono OpenSim.Grid.MessagingServer.exe<br /> <br /> ==Configuring regions==<br /> <br /> When first run, a new OpenSim installation will ask you a series of questions to set up one region. If you want to change these settings or set up multiple regions, please see [[Configuring_Regions]]<br /> <br /> ==Configuring and Starting the region simulator==<br /> &lt;ol&gt;<br /> &lt;li&gt;Find the [Architecture] section, comment out the line that says&lt;/li&gt;<br /> Include-Standalone = &quot;config-include/Standalone.ini&quot;<br /> and uncomment the line saying <br /> Include-Grid = &quot;config-include/Grid.ini<br /> <br /> &lt;li&gt;save OpenSim.ini, and go into the config-include directory.&lt;/li&gt;<br /> &lt;li&gt;copy the following files&lt;/li&gt;<br /> GridCommon.ini.example to GridCommon.ini<br /> CenomeCache.ini.example to CenomeCache.ini<br /> FlotsamCache.ini.example to FlotsamCache.ini<br /> <br /> &lt;li&gt;Open all these files (Grid.ini, GridCommon.ini, CenomeCache.ini and FlotsamCache.ini) and edit to suit your needs&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be ready to start up your sim. The mode that OpenSim.exe starts in is normally controlled by a setting in your OpenSim.ini. It defaults to standalone mode if that setting is not specified or the file is not found. If you wish, you can force opensim to start in gridmode on the command line as follows:&lt;/li&gt;<br /> OpenSim.exe -gridmode=true<br /> or if using the ODE physics plugin under 64 bit Windows<br /> OpenSim.32BitLaunch.exe<br /> or:<br /> mono OpenSim.exe -gridmode=true<br /> if you're using Mono under Linux or Mac OSX. <br /> <br /> With any luck, everything will come up without fatal errors.<br /> <br /> If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br /> &lt;tt&gt;ulimit -s 262144&lt;/tt&gt; Or, run the opensim-ode.sh to start up OpenSimulator.<br /> <br /> &lt;li&gt;Go to the UserServer console, and type 'create user' to create a new avatar. It will prompt you for the name and password, and the X and Y of the sim that should be his home location. Use 1000 and 1000, or wherever you told your sim to live when you brought it up in standalone mode. At the console of any of these servers, you should be able to type 'help' to get a list of commands.&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be able to connect to your new grid with your secondlife client. You need to tell your client to point at the UserServer rather than directly at the sim, though:&lt;/li&gt;<br /> secondlife -loginuri http://127.0.0.1:8002/<br /> 8002 is the default port for the UserServer, and that IP address should be changed to the server you are running the UserServer on, if they are not all on the same box. Happy OpenSimming!&lt;br&gt;<br /> ''Note: if you are using Windows Vista, remember to start servers as Admin. If not it will prompt you an error in console like &quot;Error - Access denied&quot;''<br /> &lt;/ol&gt;<br /> <br /> ==Attaching your sim to someone else's grid==<br /> To set up the region server (i.e., &lt;tt&gt;OpenSim.exe&lt;/tt&gt;) to connect to an external grid, you should edit the &lt;tt&gt;OpenSim.ini&lt;/tt&gt; file in the &lt;tt&gt;bin&lt;/tt&gt; directory. In that file, there is a &lt;tt&gt;[Network]&lt;/tt&gt; section with URLs for the grid, user, and asset servers, as well as send and receive keys (for a basic level of security). The addresses and send/receive keys will vary depending on the grid you are connecting to, and the grid operator should tell you what values to use.<br /> <br /> The other file you may have to change is in your &lt;tt&gt;bin/Regions&lt;/tt&gt; directory. This is where your individual region config files are. If you only have one region, it will by default be called &lt;tt&gt;Regions.ini&lt;/tt&gt; in OpenSim 0.6.7 and later and &lt;tt&gt;regions.xml&lt;/tt&gt; in OpenSim 0.6.6 and earlier.<br /> <br /> This can be edited with any text editor. The grid owner may tell you what X and Y location you can place your sim at (you can't have multiple sims at the same location on the grid). If so, the fields you will need to change in this file are &lt;tt&gt;sim_location_x&lt;/tt&gt; and &lt;tt&gt;sim_location_y&lt;/tt&gt;. And the &lt;tt&gt;external_host_name&lt;/tt&gt; should be set to the hostname or IP address of your simulation server (i.e., the machine that is running &lt;tt&gt;OpenSim.exe&lt;/tt&gt;).<br /> A list of public grids that you can attach your sim to is at [[OpenSim: Grids]]<br /> <br /> =Further notes=<br /> <br /> ==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br /> [[Image:Exclamation.png|left]]<br /> As of OpenSim 0.6.7, the default physics engine for OpenSim was changed to the ODE engine. This is because ODE is by far the most advanced physics engine plugin currently in OpenSim. Unfortunately, it has the drawback in that it's library is not compilable under 64bit in Windows. Therefore, 64 bit Windows users may need to run <br /> <br /> OpenSim.32BitLaunch.exe<br /> <br /> instead of <br /> <br /> OpenSim.exe<br /> <br /> To launch their region simulator.<br /> <br /> 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.<br /> <br /> ==Note About Mono==<br /> 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. <br /> <br /> 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.<br /> <br /> For example: $ export MONO_THREADS_PER_CPU=125<br /> <br /> == Legacy Configuration Information ==<br /> These are some pages containing some legacy configuration information of unknown accuracy.<br /> <br /> [[OpenSim 0.6.6 legacy configuration information]]<br /> <br /> <br /> == Additional Configuration Tasks (for advanced users) ==<br /> <br /> ===OpenSim.exe command line options===<br /> OpenSim.exe has command line options which allow you to perform actions such as reading configuratio nfiles from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br /> <br /> ===Script engine===<br /> OpenSim supports multiple script engines. See [[ScriptEngines]] for details. If you don't know what this means then the default script engine will be fine.<br /> <br /> ===Permissions Configuration===<br /> OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br /> <br /> === Logging ===<br /> By default, OpenSim logs information to a file called OpenSim.log in the bin directory. See [[Logging]] for details on how to further configure this if required.<br /> <br /> === Configuration of region modules ===<br /> * [[IRCBridgeModule]]<br /> * [[Freeswitch_Module]]<br /> * [[Offline Messaging]]<br /> <br /> === Configuration of Metaverse Exchange Protocol (MXP) ===<br /> * [[Metaverse Exchange Protocol]]<br /> <br /> === Configuration of Web Server and Pages===<br /> OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br /> * [[External Files]]<br /> * [[Internally Generated]]<br /> <br /> [[Category:Configuration]]</div>

Dale Mahalko http://opensimulator.org/wiki/Configuration 2010-04-04T04:10:07Z

<p>Dale Mahalko: /* Configuring the grid services */ ROBUST infobox hanging off right edge of screen. switch to a wikitable</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> ==OpenSim simulator configuration file==<br /> The region simulator configuration is managed using a file called [[OpenSim.ini]]. This file is used regardless of whether the sim is running in standalone or grid mode. This file includes some additional configuration information from the config-include/ directory. Detailed information on the options available for setttings in this file can be found [[OpenSim.ini|here]].<br /> Please note, that the name OpenSim.ini can be changed via command line arguments (see above). Also, note that the default download does not include an OpenSim.ini file, but rather provides an example file. To get started editing your ini file, please cd into opensim/bin/ and copy OpenSim.ini.example to OpenSim.ini.<br /> <br /> It is also possible to distribute the inifile settings over two files. This is useful if you want to run several OpenSim processes where most of your settings are identical but some settings differ.<br /> The master file is read first, then the inifile is read. Settings given in the inifile overrule settings given in the master file.<br /> The master file has the same format and the same keywords as the inifile, so the same documentation applies.<br /> <br /> ==Database==<br /> Opensim's supports the following database-engines:<br /> * SQLite (default - a lightweight database that comes bundled with OpenSim and can be used without requiring any extra configuration. It is mostly intended to get you up and running quickly, not for production use. A few features here (such as attachment persistence) have not yet been fully implemented.)<br /> * MySQL (fully supported). This is the recommended database for any use beyond experimentation or small standalone applications. See [[Mysql-config]] for configuration information. The OpenSim.ini.example file and other .example files will also have example MySQL configuration strings.&lt;br&gt;<br /> * MSSQL (partially supported - some recent OpenSim features may not yet be implemented)<br /> <br /> More information on database support can be found on the [[OpenSim Database support]] page.<br /> <br /> ==Standalone vs. Grid==<br /> We recommend that you first get OpenSim running in standalone mode before you attempt to connect it to a grid or run your own grid. An OpenSim configuration consists of regions (run by region simulators) and 5 core backend services (which manage users, the grid, assets, inventories, and grid-wide messaging, collectively known as UGAIM).<br /> <br /> A system running in '''standalone mode''' (that is, one with OpenSim.ini where gridmode = false) runs everything (all UGAIM services and one or more regions) in a single executable (OpenSim.exe). It is primarily suited for when a single person is using the system.<br /> <br /> In '''grid mode''', the five services ([[User Server|User]], [[Grid Server|Grid]], [[Asset Server|Asset]], [[Inventory Server|Inventory]], [[Messaging Server|Messaging]], or UGAIM) are not part of the region server. Instead, they can be run separately either on the same machine or spread out across multiple computers. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the core servers for asset, inventory and other data management. <br /> <br /> By subdividing services across separate computers, the overall grid is more tolerant of high load conditions and can support many connecting users at once. Certain situations may lag or crash a region server. By spreading services across several computers, only the one region server may be impacted but other regions on the grid will continue to operate smoothly and responsively.<br /> <br /> Splitting services across computers also allows for specialization of computing hardware for specific purposes:<br /> * The asset server often experiences the highest data transfer load and benefits the most from a fast disk subsystem. This is not so critical for other services, where memory and CPU power is the primary need.<br /> * The region server includes a physics engine which may benefit from the presence of a PCI-Express 3D card for physics acceleration, and which the asset server would not use at all.<br /> <br /> Running in grid mode is more complicated than running in standalone mode. It requires an understanding of UUID, X,Y location, server handshake passwords, estates and estate owners, and a couple of other settings. These require more care and patience to set up.<br /> <br /> If you want to run a grid of your own (either private or public) you would start the core services up before connecting a region simulator. If you want to connect your region server to a grid that someone else is running, you need only start the region server in grid mode (with the necessary security keys and location information mentioned in the last paragraph).<br /> <br /> = Running OpenSim in Standalone mode =<br /> <br /> Running OpenSim in standalone mode is relatively straitforward because OpenSim.ini.example is already set up to achieve this. All you need to do initially is copy OpenSim.ini.example to OpenSim.ini before starting OpenSim and following the rest of the command prompts. Here's the full procedure assuming that you have a binary distribution of OpenSim (if you have a source distribution then you will need to [[Build_Instructions|build]] it first).<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;Go the bin/ directory in the OpenSim distribution&lt;/li&gt;<br /> &lt;li&gt;Copy OpenSim.ini.example to OpenSim.ini&lt;/li&gt;<br /> &lt;li&gt;Start OpenSim&lt;/li&gt;<br /> Windows<br /> OpenSim.exe<br /> Or if using the ODE physics plugin under 64 bit Windows<br /> OpenSim.32BitLaunch.exe<br /> Linux<br /> mono OpenSim.exe<br /> <br /> &lt;li&gt;<br /> When you first start OpenSim in standalone mode, it will ask you several questions at the console. These will set up a single region for you. The configuration will be placed at bin/Regions/Regions.ini which you can then go and edit later on.<br /> <br /> Many of the questions have defaults. Here are some explanations of the questions asked.<br /> <br /> &lt;ul&gt;<br /> &lt;li&gt;'''New region name''' - the name for your region. Don't leave this blank!&lt;/li&gt;<br /> &lt;li&gt;'''Region UUID''' - the unique ID of your region. In pretty much all cases you will want to accept the randomly generated default in the square brackets. The only time when you wouldn't is if you were trying to set up a configuration to point to pre-existing region data. But in this case you are probably better off editing the Regions.ini file directly anyway&lt;/li&gt;<br /> &lt;li&gt;'''Region Location''' - 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). OpenSim regions can be placed anywhere on a 65536 by 65536 grid.<br /> &lt;li&gt;'''Internal IP address''' - This should always be 0.0.0.0 (0.0.0.0 means &quot;listen for connections on any interface&quot;, basically a wildcard) if you want to access this server from the internet or another server on your internal network, this should be the IP&amp;nbsp;address assigned to the OpenSim Server. You should also set up the server to Use a Static IP address, and not DHCP <br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Allow alternate ports''' - This is currently experimental. Please leave it at the default of False.&lt;/li&gt;<br /> &lt;li&gt;'''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) should also work. <br /> &lt;li&gt;'''Master Avatar UUID''' - This is a legacy OpenSim 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.&lt;/li&gt;<br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Master Avatar last name''' - The last name of the master avatar.<br /> &lt;li&gt;'''Master Avatar sandbox password''' - The password of the master avatar.<br /> <br /> Be aware of [http://osgrid.org/forums/viewtopic.php?f=5&amp;t=400&amp;start=0&amp;st=0&amp;sk=t&amp;sd=a loopback] problems when Running viewer &amp;amp; server(s) on the same machine (LAN) by using the &quot;external&quot; configuration. (&lt;u&gt;'''You might notice endless waiting for region handshake'''&lt;/u&gt;.) See also [http://opensimulator.org/wiki/Troubleshooting troubleshoot hints]. If you're having Connectivity problems. [http://opensimulator.org/wiki/Network_Settings Be sure to read the Network Configuration Page]. This is important if you see Region handshake issues&lt;/li&gt;<br /> <br /> See [[Configuring_Regions]] for information about the Regions.ini file that these questions generate.<br /> <br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt; To create a user type &lt;/li&gt;<br /> <br /> create user<br /> <br /> in the server console. This will ask you a series of questions for creating a user (such as first name, last name and password).<br /> <br /> &lt;li&gt; To connect to your new sim with your user, start up a Second Life viewer with the following command line switches: &lt;/li&gt;<br /> <br /> '''Client on same machine as OpenSim:'''<br /> -loginuri http://127.0.0.1:9000/ -loginpage http://127.0.0.1:9000/?method=login <br /> <br /> '''Client on same LAN as OpenSim:'''<br /> -loginuri http://lan_ip:9000/ -loginpage http://lan_ip:9000/?method=login <br /> <br /> '''Client on different machine or internet:'''<br /> -loginuri http://external_ip:9000/ -loginpage http://external_ip:9000/?method=login<br /> <br /> Then enter the user name and password you set up in the previous step and your new user should hopefully login.<br /> <br /> &lt;/ol&gt;<br /> <br /> = Running OpenSim in Grid mode =<br /> <br /> Running OpenSim in grid mode is considerably more complicated. Grid services need to be set up and the region simulator configuration needs to be changed to use these instead of the built-in standalone mode ones.<br /> <br /> ==Configuring the grid services==<br /> {|<br /> | style=&quot;background:LavenderBlush; color:black&quot; |<br /> [[Image:Exclamation.png|left]]<br /> NOTE: The grid servers are in the process of being redesigned. <br /> Some services are now run in a common 'ROBUST' (Basic Universal Server Technology) server shell <br /> while others are still run as separate legacy servers.<br /> <br /> &lt;u&gt;'''More Details on ROBUST are Here --&amp;gt;'''&lt;/u&gt;[[ROBUST|&lt;u&gt;'''ROBUST'''&lt;/u&gt;]]&lt;u&gt;'''&amp;nbsp;&amp;lt;--&amp;nbsp; including Conversion From UGAIM To UGRM (0.6.6 -&gt; 0.6.7) and UGRM to URM (0.6.7 -&gt; 0.6.8)'''&lt;/u&gt;<br /> |}<br /> <br /> As of OpenSim 0.6.8, R.O.B.U.S.T. has connectors for the asset (A), grid (G) and inventory (I) functionality. The legacy servers are still required for user (U) and messaging (M) functionality. The steps below will get you up and running. We'll assume that your current directory is bin/ within the OpenSim distribution.<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;'''Configure the user server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.UserServer.exe&lt;/li&gt;<br /> &lt;li&gt;You will be asked a number of configuration questions. If the grid servers are all on one machine, most defaults are safe to use. The configuration is stored in the UserServer_Config.xml file which can be changed afterwards if necessary.&lt;/li&gt;<br /> &lt;li&gt;The user server will then load and display it's prompt:&lt;/li&gt;<br /> User#<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure R.O.B.U.S.T.'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Copy OpenSim.Server.ini.example to OpenSim.Server.ini. Don't forget to change ConnectionString for your database settings. (on version 0.6.6 copy OpenSim.Services.ini.example to OpenSim.Services.ini - then use OpenSim.Services instead OpenSim.Server)<br /> &lt;/li&gt;<br /> Linux<br /> bin$ cp OpenSim.Server.ini.example OpenSim.Server.ini<br /> Windows<br /> C:\OpenSim\bin&gt; copy OpenSim.Server.ini.example OpenSim.Server.ini<br /> &lt;li&gt;Start OpenSim.Server.exe&lt;/li&gt;<br /> &lt;li&gt;The server will start up it's asset, inventory and grid components and display the R.O.B.U.S.T prompt:&lt;/li&gt;<br /> R.O.B.U.S.T.#<br /> &lt;li&gt;For more information on the R.O.B.U.S.T. configuration file and more information if you are migrating from an earlier release of OpenSim, refer to [[R.O.B.U.S.T.]]&lt;/li&gt;<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure the messaging server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.MessagingServer.exe&lt;/li&gt;<br /> &lt;li&gt;Answer the configuration questions. Again, if all servers are run on the same machine, it's safe to press enter for all questions. The configuration is stored in MessagingServer_Config.xml.&lt;/li&gt;<br /> &lt;li&gt;The server will start and present you with it's prompt:&lt;/li&gt;<br /> Messaging#<br /> &lt;/ul&gt;<br /> <br /> &lt;/ol&gt; <br /> <br /> For information on running the legacy servers, particularly if you're using an older version of before 0.6.7 that doesn't contain the ROBUST framework, see [[LegacyServers]]<br /> <br /> === Summary of commands for running grid service executables ===<br /> <br /> '''&lt;u&gt;Windows&lt;/u&gt;'''<br /> cd bin<br /> OpenSim.Grid.UserServer.exe<br /> OpenSim.Server.exe<br /> OpenSim.Grid.MessagingServer.exe<br /> <br /> '''&lt;u&gt;Linux / Mac OS X&lt;/u&gt;'''<br /> cd bin<br /> mono OpenSim.Grid.UserServer.exe<br /> mono OpenSim.Server.exe<br /> mono OpenSim.Grid.MessagingServer.exe<br /> <br /> ==Configuring regions==<br /> <br /> When first run, a new OpenSim installation will ask you a series of questions to set up one region. If you want to change these settings or set up multiple regions, please see [[Configuring_Regions]]<br /> <br /> ==Configuring and Starting the region simulator==<br /> &lt;ol&gt;<br /> &lt;li&gt;Find the [Architecture] section, comment out the line that says&lt;/li&gt;<br /> Include-Standalone = &quot;config-include/Standalone.ini&quot;<br /> and uncomment the line saying <br /> Include-Grid = &quot;config-include/Grid.ini<br /> <br /> &lt;li&gt;save OpenSim.ini, and go into the config-include directory.&lt;/li&gt;<br /> &lt;li&gt;copy the following files&lt;/li&gt;<br /> GridCommon.ini.example to GridCommon.ini<br /> CenomeCache.ini.example to CenomeCache.ini<br /> FlotsamCache.ini.example to FlotsamCache.ini<br /> <br /> &lt;li&gt;Open all these files (Grid.ini, GridCommon.ini, CenomeCache.ini and FlotsamCache.ini) and edit to suit your needs&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be ready to start up your sim. The mode that OpenSim.exe starts in is normally controlled by a setting in your OpenSim.ini. It defaults to standalone mode if that setting is not specified or the file is not found. If you wish, you can force opensim to start in gridmode on the command line as follows:&lt;/li&gt;<br /> OpenSim.exe -gridmode=true<br /> or if using the ODE physics plugin under 64 bit Windows<br /> OpenSim.32BitLaunch.exe<br /> or:<br /> mono OpenSim.exe -gridmode=true<br /> if you're using Mono under Linux or Mac OSX. <br /> <br /> With any luck, everything will come up without fatal errors.<br /> <br /> If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br /> &lt;tt&gt;ulimit -s 262144&lt;/tt&gt; Or, run the opensim-ode.sh to start up OpenSimulator.<br /> <br /> &lt;li&gt;Go to the UserServer console, and type 'create user' to create a new avatar. It will prompt you for the name and password, and the X and Y of the sim that should be his home location. Use 1000 and 1000, or wherever you told your sim to live when you brought it up in standalone mode. At the console of any of these servers, you should be able to type 'help' to get a list of commands.&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be able to connect to your new grid with your secondlife client. You need to tell your client to point at the UserServer rather than directly at the sim, though:&lt;/li&gt;<br /> secondlife -loginuri http://127.0.0.1:8002/<br /> 8002 is the default port for the UserServer, and that IP address should be changed to the server you are running the UserServer on, if they are not all on the same box. Happy OpenSimming!&lt;br&gt;<br /> ''Note: if you are using Windows Vista, remember to start servers as Admin. If not it will prompt you an error in console like &quot;Error - Access denied&quot;''<br /> &lt;/ol&gt;<br /> <br /> ==Attaching your sim to someone else's grid==<br /> To set up the region server (i.e., &lt;tt&gt;OpenSim.exe&lt;/tt&gt;) to connect to an external grid, you should edit the &lt;tt&gt;OpenSim.ini&lt;/tt&gt; file in the &lt;tt&gt;bin&lt;/tt&gt; directory. In that file, there is a &lt;tt&gt;[Network]&lt;/tt&gt; section with URLs for the grid, user, and asset servers, as well as send and receive keys (for a basic level of security). The addresses and send/receive keys will vary depending on the grid you are connecting to, and the grid operator should tell you what values to use.<br /> <br /> The other file you may have to change is in your &lt;tt&gt;bin/Regions&lt;/tt&gt; directory. This is where your individual region config files are. If you only have one region, it will by default be called &lt;tt&gt;Regions.ini&lt;/tt&gt; in OpenSim 0.6.7 and later and &lt;tt&gt;regions.xml&lt;/tt&gt; in OpenSim 0.6.6 and earlier.<br /> <br /> This can be edited with any text editor. The grid owner may tell you what X and Y location you can place your sim at (you can't have multiple sims at the same location on the grid). If so, the fields you will need to change in this file are &lt;tt&gt;sim_location_x&lt;/tt&gt; and &lt;tt&gt;sim_location_y&lt;/tt&gt;. And the &lt;tt&gt;external_host_name&lt;/tt&gt; should be set to the hostname or IP address of your simulation server (i.e., the machine that is running &lt;tt&gt;OpenSim.exe&lt;/tt&gt;).<br /> A list of public grids that you can attach your sim to is at [[OpenSim: Grids]]<br /> <br /> =Further notes=<br /> <br /> ==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br /> [[Image:Exclamation.png|left]]<br /> As of OpenSim 0.6.7, the default physics engine for OpenSim was changed to the ODE engine. This is because ODE is by far the most advanced physics engine plugin currently in OpenSim. Unfortunately, it has the drawback in that it's library is not compilable under 64bit in Windows. Therefore, 64 bit Windows users may need to run <br /> <br /> OpenSim.32BitLaunch.exe<br /> <br /> instead of <br /> <br /> OpenSim.exe<br /> <br /> To launch their region simulator.<br /> <br /> 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.<br /> <br /> ==Note About Mono==<br /> 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. <br /> <br /> 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.<br /> <br /> For example: $ export MONO_THREADS_PER_CPU=125<br /> <br /> == Legacy Configuration Information ==<br /> These are some pages containing some legacy configuration information of unknown accuracy.<br /> <br /> [[OpenSim 0.6.6 legacy configuration information]]<br /> <br /> <br /> == Additional Configuration Tasks (for advanced users) ==<br /> <br /> ===OpenSim.exe command line options===<br /> OpenSim.exe has command line options which allow you to perform actions such as reading configuratio nfiles from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br /> <br /> ===Script engine===<br /> OpenSim supports multiple script engines. See [[ScriptEngines]] for details. If you don't know what this means then the default script engine will be fine.<br /> <br /> ===Permissions Configuration===<br /> OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br /> <br /> === Logging ===<br /> By default, OpenSim logs information to a file called OpenSim.log in the bin directory. See [[Logging]] for details on how to further configure this if required.<br /> <br /> === Configuration of region modules ===<br /> * [[IRCBridgeModule]]<br /> * [[Freeswitch_Module]]<br /> * [[Offline Messaging]]<br /> <br /> === Configuration of Metaverse Exchange Protocol (MXP) ===<br /> * [[Metaverse Exchange Protocol]]<br /> <br /> === Configuration of Web Server and Pages===<br /> OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br /> * [[External Files]]<br /> * [[Internally Generated]]<br /> <br /> [[Category:Configuration]]</div>

Dale Mahalko http://opensimulator.org/wiki/Configuration 2010-04-04T03:59:52Z

<p>Dale Mahalko: /* Running OpenSim in Standalone mode */ long monospaced lines hanging off edge of page, adjust formatting</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> ==OpenSim simulator configuration file==<br /> The region simulator configuration is managed using a file called [[OpenSim.ini]]. This file is used regardless of whether the sim is running in standalone or grid mode. This file includes some additional configuration information from the config-include/ directory. Detailed information on the options available for setttings in this file can be found [[OpenSim.ini|here]].<br /> Please note, that the name OpenSim.ini can be changed via command line arguments (see above). Also, note that the default download does not include an OpenSim.ini file, but rather provides an example file. To get started editing your ini file, please cd into opensim/bin/ and copy OpenSim.ini.example to OpenSim.ini.<br /> <br /> It is also possible to distribute the inifile settings over two files. This is useful if you want to run several OpenSim processes where most of your settings are identical but some settings differ.<br /> The master file is read first, then the inifile is read. Settings given in the inifile overrule settings given in the master file.<br /> The master file has the same format and the same keywords as the inifile, so the same documentation applies.<br /> <br /> ==Database==<br /> Opensim's supports the following database-engines:<br /> * SQLite (default - a lightweight database that comes bundled with OpenSim and can be used without requiring any extra configuration. It is mostly intended to get you up and running quickly, not for production use. A few features here (such as attachment persistence) have not yet been fully implemented.)<br /> * MySQL (fully supported). This is the recommended database for any use beyond experimentation or small standalone applications. See [[Mysql-config]] for configuration information. The OpenSim.ini.example file and other .example files will also have example MySQL configuration strings.&lt;br&gt;<br /> * MSSQL (partially supported - some recent OpenSim features may not yet be implemented)<br /> <br /> More information on database support can be found on the [[OpenSim Database support]] page.<br /> <br /> ==Standalone vs. Grid==<br /> We recommend that you first get OpenSim running in standalone mode before you attempt to connect it to a grid or run your own grid. An OpenSim configuration consists of regions (run by region simulators) and 5 core backend services (which manage users, the grid, assets, inventories, and grid-wide messaging, collectively known as UGAIM).<br /> <br /> A system running in '''standalone mode''' (that is, one with OpenSim.ini where gridmode = false) runs everything (all UGAIM services and one or more regions) in a single executable (OpenSim.exe). It is primarily suited for when a single person is using the system.<br /> <br /> In '''grid mode''', the five services ([[User Server|User]], [[Grid Server|Grid]], [[Asset Server|Asset]], [[Inventory Server|Inventory]], [[Messaging Server|Messaging]], or UGAIM) are not part of the region server. Instead, they can be run separately either on the same machine or spread out across multiple computers. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the core servers for asset, inventory and other data management. <br /> <br /> By subdividing services across separate computers, the overall grid is more tolerant of high load conditions and can support many connecting users at once. Certain situations may lag or crash a region server. By spreading services across several computers, only the one region server may be impacted but other regions on the grid will continue to operate smoothly and responsively.<br /> <br /> Splitting services across computers also allows for specialization of computing hardware for specific purposes:<br /> * The asset server often experiences the highest data transfer load and benefits the most from a fast disk subsystem. This is not so critical for other services, where memory and CPU power is the primary need.<br /> * The region server includes a physics engine which may benefit from the presence of a PCI-Express 3D card for physics acceleration, and which the asset server would not use at all.<br /> <br /> Running in grid mode is more complicated than running in standalone mode. It requires an understanding of UUID, X,Y location, server handshake passwords, estates and estate owners, and a couple of other settings. These require more care and patience to set up.<br /> <br /> If you want to run a grid of your own (either private or public) you would start the core services up before connecting a region simulator. If you want to connect your region server to a grid that someone else is running, you need only start the region server in grid mode (with the necessary security keys and location information mentioned in the last paragraph).<br /> <br /> = Running OpenSim in Standalone mode =<br /> <br /> Running OpenSim in standalone mode is relatively straitforward because OpenSim.ini.example is already set up to achieve this. All you need to do initially is copy OpenSim.ini.example to OpenSim.ini before starting OpenSim and following the rest of the command prompts. Here's the full procedure assuming that you have a binary distribution of OpenSim (if you have a source distribution then you will need to [[Build_Instructions|build]] it first).<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;Go the bin/ directory in the OpenSim distribution&lt;/li&gt;<br /> &lt;li&gt;Copy OpenSim.ini.example to OpenSim.ini&lt;/li&gt;<br /> &lt;li&gt;Start OpenSim&lt;/li&gt;<br /> Windows<br /> OpenSim.exe<br /> Or if using the ODE physics plugin under 64 bit Windows<br /> OpenSim.32BitLaunch.exe<br /> Linux<br /> mono OpenSim.exe<br /> <br /> &lt;li&gt;<br /> When you first start OpenSim in standalone mode, it will ask you several questions at the console. These will set up a single region for you. The configuration will be placed at bin/Regions/Regions.ini which you can then go and edit later on.<br /> <br /> Many of the questions have defaults. Here are some explanations of the questions asked.<br /> <br /> &lt;ul&gt;<br /> &lt;li&gt;'''New region name''' - the name for your region. Don't leave this blank!&lt;/li&gt;<br /> &lt;li&gt;'''Region UUID''' - the unique ID of your region. In pretty much all cases you will want to accept the randomly generated default in the square brackets. The only time when you wouldn't is if you were trying to set up a configuration to point to pre-existing region data. But in this case you are probably better off editing the Regions.ini file directly anyway&lt;/li&gt;<br /> &lt;li&gt;'''Region Location''' - 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). OpenSim regions can be placed anywhere on a 65536 by 65536 grid.<br /> &lt;li&gt;'''Internal IP address''' - This should always be 0.0.0.0 (0.0.0.0 means &quot;listen for connections on any interface&quot;, basically a wildcard) if you want to access this server from the internet or another server on your internal network, this should be the IP&amp;nbsp;address assigned to the OpenSim Server. You should also set up the server to Use a Static IP address, and not DHCP <br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Allow alternate ports''' - This is currently experimental. Please leave it at the default of False.&lt;/li&gt;<br /> &lt;li&gt;'''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) should also work. <br /> &lt;li&gt;'''Master Avatar UUID''' - This is a legacy OpenSim 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.&lt;/li&gt;<br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Master Avatar last name''' - The last name of the master avatar.<br /> &lt;li&gt;'''Master Avatar sandbox password''' - The password of the master avatar.<br /> <br /> Be aware of [http://osgrid.org/forums/viewtopic.php?f=5&amp;t=400&amp;start=0&amp;st=0&amp;sk=t&amp;sd=a loopback] problems when Running viewer &amp;amp; server(s) on the same machine (LAN) by using the &quot;external&quot; configuration. (&lt;u&gt;'''You might notice endless waiting for region handshake'''&lt;/u&gt;.) See also [http://opensimulator.org/wiki/Troubleshooting troubleshoot hints]. If you're having Connectivity problems. [http://opensimulator.org/wiki/Network_Settings Be sure to read the Network Configuration Page]. This is important if you see Region handshake issues&lt;/li&gt;<br /> <br /> See [[Configuring_Regions]] for information about the Regions.ini file that these questions generate.<br /> <br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt; To create a user type &lt;/li&gt;<br /> <br /> create user<br /> <br /> in the server console. This will ask you a series of questions for creating a user (such as first name, last name and password).<br /> <br /> &lt;li&gt; To connect to your new sim with your user, start up a Second Life viewer with the following command line switches: &lt;/li&gt;<br /> <br /> '''Client on same machine as OpenSim:'''<br /> -loginuri http://127.0.0.1:9000/ -loginpage http://127.0.0.1:9000/?method=login <br /> <br /> '''Client on same LAN as OpenSim:'''<br /> -loginuri http://lan_ip:9000/ -loginpage http://lan_ip:9000/?method=login <br /> <br /> '''Client on different machine or internet:'''<br /> -loginuri http://external_ip:9000/ -loginpage http://external_ip:9000/?method=login<br /> <br /> Then enter the user name and password you set up in the previous step and your new user should hopefully login.<br /> <br /> &lt;/ol&gt;<br /> <br /> = Running OpenSim in Grid mode =<br /> <br /> Running OpenSim in grid mode is considerably more complicated. Grid services need to be set up and the region simulator configuration needs to be changed to use these instead of the built-in standalone mode ones.<br /> <br /> ==Configuring the grid services==<br /> [[Image:Exclamation.png|left]]<br /> NOTE: The grid servers are in the process of being redesigned. <br /> Some services are now run in a common 'ROBUST' (Basic Universal Server Technology) server shell <br /> while others are still run as separate legacy servers.<br /> &lt;u&gt;'''More Details on ROBUST are Here --&amp;gt;'''&lt;/u&gt;[[ROBUST|&lt;u&gt;'''ROBUST'''&lt;/u&gt;]]&lt;u&gt;'''&amp;nbsp;&amp;lt;--&amp;nbsp; including Conversion From UGAIM To UGRM (0.6.6 -&gt; 0.6.7) and UGRM to URM (0.6.7 -&gt; 0.6.8)'''&lt;/u&gt;<br /> <br /> As of OpenSim 0.6.8, R.O.B.U.S.T. has connectors for the asset (A), grid (G) and inventory (I) functionality. The legacy servers are still required for user (U) and messaging (M) functionality. The steps below will get you up and running. We'll assume that your current directory is bin/ within the OpenSim distribution.<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;'''Configure the user server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.UserServer.exe&lt;/li&gt;<br /> &lt;li&gt;You will be asked a number of configuration questions. If the grid servers are all on one machine, most defaults are safe to use. The configuration is stored in the UserServer_Config.xml file which can be changed afterwards if necessary.&lt;/li&gt;<br /> &lt;li&gt;The user server will then load and display it's prompt:&lt;/li&gt;<br /> User#<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure R.O.B.U.S.T.'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Copy OpenSim.Server.ini.example to OpenSim.Server.ini. Don't forget to change ConnectionString for your database settings. (on version 0.6.6 copy OpenSim.Services.ini.example to OpenSim.Services.ini - then use OpenSim.Services instead OpenSim.Server)<br /> &lt;/li&gt;<br /> Linux<br /> bin$ cp OpenSim.Server.ini.example OpenSim.Server.ini<br /> Windows<br /> C:\OpenSim\bin&gt; copy OpenSim.Server.ini.example OpenSim.Server.ini<br /> &lt;li&gt;Start OpenSim.Server.exe&lt;/li&gt;<br /> &lt;li&gt;The server will start up it's asset, inventory and grid components and display the R.O.B.U.S.T prompt:&lt;/li&gt;<br /> R.O.B.U.S.T.#<br /> &lt;li&gt;For more information on the R.O.B.U.S.T. configuration file and more information if you are migrating from an earlier release of OpenSim, refer to [[R.O.B.U.S.T.]]&lt;/li&gt;<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure the messaging server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.MessagingServer.exe&lt;/li&gt;<br /> &lt;li&gt;Answer the configuration questions. Again, if all servers are run on the same machine, it's safe to press enter for all questions. The configuration is stored in MessagingServer_Config.xml.&lt;/li&gt;<br /> &lt;li&gt;The server will start and present you with it's prompt:&lt;/li&gt;<br /> Messaging#<br /> &lt;/ul&gt;<br /> <br /> &lt;/ol&gt; <br /> <br /> For information on running the legacy servers, particularly if you're using an older version of before 0.6.7 that doesn't contain the ROBUST framework, see [[LegacyServers]]<br /> <br /> === Summary of commands for running grid service executables ===<br /> <br /> '''&lt;u&gt;Windows&lt;/u&gt;'''<br /> cd bin<br /> OpenSim.Grid.UserServer.exe<br /> OpenSim.Server.exe<br /> OpenSim.Grid.MessagingServer.exe<br /> <br /> '''&lt;u&gt;Linux / Mac OS X&lt;/u&gt;'''<br /> cd bin<br /> mono OpenSim.Grid.UserServer.exe<br /> mono OpenSim.Server.exe<br /> mono OpenSim.Grid.MessagingServer.exe<br /> <br /> ==Configuring regions==<br /> <br /> When first run, a new OpenSim installation will ask you a series of questions to set up one region. If you want to change these settings or set up multiple regions, please see [[Configuring_Regions]]<br /> <br /> ==Configuring and Starting the region simulator==<br /> &lt;ol&gt;<br /> &lt;li&gt;Find the [Architecture] section, comment out the line that says&lt;/li&gt;<br /> Include-Standalone = &quot;config-include/Standalone.ini&quot;<br /> and uncomment the line saying <br /> Include-Grid = &quot;config-include/Grid.ini<br /> <br /> &lt;li&gt;save OpenSim.ini, and go into the config-include directory.&lt;/li&gt;<br /> &lt;li&gt;copy the following files&lt;/li&gt;<br /> GridCommon.ini.example to GridCommon.ini<br /> CenomeCache.ini.example to CenomeCache.ini<br /> FlotsamCache.ini.example to FlotsamCache.ini<br /> <br /> &lt;li&gt;Open all these files (Grid.ini, GridCommon.ini, CenomeCache.ini and FlotsamCache.ini) and edit to suit your needs&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be ready to start up your sim. The mode that OpenSim.exe starts in is normally controlled by a setting in your OpenSim.ini. It defaults to standalone mode if that setting is not specified or the file is not found. If you wish, you can force opensim to start in gridmode on the command line as follows:&lt;/li&gt;<br /> OpenSim.exe -gridmode=true<br /> or if using the ODE physics plugin under 64 bit Windows<br /> OpenSim.32BitLaunch.exe<br /> or:<br /> mono OpenSim.exe -gridmode=true<br /> if you're using Mono under Linux or Mac OSX. <br /> <br /> With any luck, everything will come up without fatal errors.<br /> <br /> If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br /> &lt;tt&gt;ulimit -s 262144&lt;/tt&gt; Or, run the opensim-ode.sh to start up OpenSimulator.<br /> <br /> &lt;li&gt;Go to the UserServer console, and type 'create user' to create a new avatar. It will prompt you for the name and password, and the X and Y of the sim that should be his home location. Use 1000 and 1000, or wherever you told your sim to live when you brought it up in standalone mode. At the console of any of these servers, you should be able to type 'help' to get a list of commands.&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be able to connect to your new grid with your secondlife client. You need to tell your client to point at the UserServer rather than directly at the sim, though:&lt;/li&gt;<br /> secondlife -loginuri http://127.0.0.1:8002/<br /> 8002 is the default port for the UserServer, and that IP address should be changed to the server you are running the UserServer on, if they are not all on the same box. Happy OpenSimming!&lt;br&gt;<br /> ''Note: if you are using Windows Vista, remember to start servers as Admin. If not it will prompt you an error in console like &quot;Error - Access denied&quot;''<br /> &lt;/ol&gt;<br /> <br /> ==Attaching your sim to someone else's grid==<br /> To set up the region server (i.e., &lt;tt&gt;OpenSim.exe&lt;/tt&gt;) to connect to an external grid, you should edit the &lt;tt&gt;OpenSim.ini&lt;/tt&gt; file in the &lt;tt&gt;bin&lt;/tt&gt; directory. In that file, there is a &lt;tt&gt;[Network]&lt;/tt&gt; section with URLs for the grid, user, and asset servers, as well as send and receive keys (for a basic level of security). The addresses and send/receive keys will vary depending on the grid you are connecting to, and the grid operator should tell you what values to use.<br /> <br /> The other file you may have to change is in your &lt;tt&gt;bin/Regions&lt;/tt&gt; directory. This is where your individual region config files are. If you only have one region, it will by default be called &lt;tt&gt;Regions.ini&lt;/tt&gt; in OpenSim 0.6.7 and later and &lt;tt&gt;regions.xml&lt;/tt&gt; in OpenSim 0.6.6 and earlier.<br /> <br /> This can be edited with any text editor. The grid owner may tell you what X and Y location you can place your sim at (you can't have multiple sims at the same location on the grid). If so, the fields you will need to change in this file are &lt;tt&gt;sim_location_x&lt;/tt&gt; and &lt;tt&gt;sim_location_y&lt;/tt&gt;. And the &lt;tt&gt;external_host_name&lt;/tt&gt; should be set to the hostname or IP address of your simulation server (i.e., the machine that is running &lt;tt&gt;OpenSim.exe&lt;/tt&gt;).<br /> A list of public grids that you can attach your sim to is at [[OpenSim: Grids]]<br /> <br /> =Further notes=<br /> <br /> ==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br /> [[Image:Exclamation.png|left]]<br /> As of OpenSim 0.6.7, the default physics engine for OpenSim was changed to the ODE engine. This is because ODE is by far the most advanced physics engine plugin currently in OpenSim. Unfortunately, it has the drawback in that it's library is not compilable under 64bit in Windows. Therefore, 64 bit Windows users may need to run <br /> <br /> OpenSim.32BitLaunch.exe<br /> <br /> instead of <br /> <br /> OpenSim.exe<br /> <br /> To launch their region simulator.<br /> <br /> 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.<br /> <br /> ==Note About Mono==<br /> 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. <br /> <br /> 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.<br /> <br /> For example: $ export MONO_THREADS_PER_CPU=125<br /> <br /> == Legacy Configuration Information ==<br /> These are some pages containing some legacy configuration information of unknown accuracy.<br /> <br /> [[OpenSim 0.6.6 legacy configuration information]]<br /> <br /> <br /> == Additional Configuration Tasks (for advanced users) ==<br /> <br /> ===OpenSim.exe command line options===<br /> OpenSim.exe has command line options which allow you to perform actions such as reading configuratio nfiles from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br /> <br /> ===Script engine===<br /> OpenSim supports multiple script engines. See [[ScriptEngines]] for details. If you don't know what this means then the default script engine will be fine.<br /> <br /> ===Permissions Configuration===<br /> OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br /> <br /> === Logging ===<br /> By default, OpenSim logs information to a file called OpenSim.log in the bin directory. See [[Logging]] for details on how to further configure this if required.<br /> <br /> === Configuration of region modules ===<br /> * [[IRCBridgeModule]]<br /> * [[Freeswitch_Module]]<br /> * [[Offline Messaging]]<br /> <br /> === Configuration of Metaverse Exchange Protocol (MXP) ===<br /> * [[Metaverse Exchange Protocol]]<br /> <br /> === Configuration of Web Server and Pages===<br /> OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br /> * [[External Files]]<br /> * [[Internally Generated]]<br /> <br /> [[Category:Configuration]]</div>

Dale Mahalko http://opensimulator.org/wiki/Configuration 2010-04-04T03:45:15Z

<p>Dale Mahalko: /* Standalone vs. Grid */ standalone is best for a single person doing testing. splitting services across multiple computers makes everything more tolerant of high load and also fault tolerant</p> <hr /> <div>{{Template:Quicklinks}}<br /> &lt;br /&gt;<br /> ==OpenSim simulator configuration file==<br /> The region simulator configuration is managed using a file called [[OpenSim.ini]]. This file is used regardless of whether the sim is running in standalone or grid mode. This file includes some additional configuration information from the config-include/ directory. Detailed information on the options available for setttings in this file can be found [[OpenSim.ini|here]].<br /> Please note, that the name OpenSim.ini can be changed via command line arguments (see above). Also, note that the default download does not include an OpenSim.ini file, but rather provides an example file. To get started editing your ini file, please cd into opensim/bin/ and copy OpenSim.ini.example to OpenSim.ini.<br /> <br /> It is also possible to distribute the inifile settings over two files. This is useful if you want to run several OpenSim processes where most of your settings are identical but some settings differ.<br /> The master file is read first, then the inifile is read. Settings given in the inifile overrule settings given in the master file.<br /> The master file has the same format and the same keywords as the inifile, so the same documentation applies.<br /> <br /> ==Database==<br /> Opensim's supports the following database-engines:<br /> * SQLite (default - a lightweight database that comes bundled with OpenSim and can be used without requiring any extra configuration. It is mostly intended to get you up and running quickly, not for production use. A few features here (such as attachment persistence) have not yet been fully implemented.)<br /> * MySQL (fully supported). This is the recommended database for any use beyond experimentation or small standalone applications. See [[Mysql-config]] for configuration information. The OpenSim.ini.example file and other .example files will also have example MySQL configuration strings.&lt;br&gt;<br /> * MSSQL (partially supported - some recent OpenSim features may not yet be implemented)<br /> <br /> More information on database support can be found on the [[OpenSim Database support]] page.<br /> <br /> ==Standalone vs. Grid==<br /> We recommend that you first get OpenSim running in standalone mode before you attempt to connect it to a grid or run your own grid. An OpenSim configuration consists of regions (run by region simulators) and 5 core backend services (which manage users, the grid, assets, inventories, and grid-wide messaging, collectively known as UGAIM).<br /> <br /> A system running in '''standalone mode''' (that is, one with OpenSim.ini where gridmode = false) runs everything (all UGAIM services and one or more regions) in a single executable (OpenSim.exe). It is primarily suited for when a single person is using the system.<br /> <br /> In '''grid mode''', the five services ([[User Server|User]], [[Grid Server|Grid]], [[Asset Server|Asset]], [[Inventory Server|Inventory]], [[Messaging Server|Messaging]], or UGAIM) are not part of the region server. Instead, they can be run separately either on the same machine or spread out across multiple computers. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the core servers for asset, inventory and other data management. <br /> <br /> By subdividing services across separate computers, the overall grid is more tolerant of high load conditions and can support many connecting users at once. Certain situations may lag or crash a region server. By spreading services across several computers, only the one region server may be impacted but other regions on the grid will continue to operate smoothly and responsively.<br /> <br /> Splitting services across computers also allows for specialization of computing hardware for specific purposes:<br /> * The asset server often experiences the highest data transfer load and benefits the most from a fast disk subsystem. This is not so critical for other services, where memory and CPU power is the primary need.<br /> * The region server includes a physics engine which may benefit from the presence of a PCI-Express 3D card for physics acceleration, and which the asset server would not use at all.<br /> <br /> Running in grid mode is more complicated than running in standalone mode. It requires an understanding of UUID, X,Y location, server handshake passwords, estates and estate owners, and a couple of other settings. These require more care and patience to set up.<br /> <br /> If you want to run a grid of your own (either private or public) you would start the core services up before connecting a region simulator. If you want to connect your region server to a grid that someone else is running, you need only start the region server in grid mode (with the necessary security keys and location information mentioned in the last paragraph).<br /> <br /> = Running OpenSim in Standalone mode =<br /> <br /> Running OpenSim in standalone mode is relatively straitforward because OpenSim.ini.example is already set up to achieve this. All you need to do initially is copy OpenSim.ini.example to OpenSim.ini before starting OpenSim and following the rest of the command prompts. Here's the full procedure assuming that you have a binary distribution of OpenSim (if you have a source distribution then you will need to [[Build_Instructions|build]] it first).<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;Go the bin/ directory in the OpenSim distribution&lt;/li&gt;<br /> &lt;li&gt;Copy OpenSim.ini.example to OpenSim.ini&lt;/li&gt;<br /> &lt;li&gt;Start OpenSim&lt;/li&gt;<br /> Windows<br /> OpenSim.exe<br /> or OpenSim.32BitLaunch.exe if using the ODE physics plugin under 64 bit Windows<br /> Linux<br /> mono OpenSim.exe<br /> <br /> &lt;li&gt;<br /> When you first start OpenSim in standalone mode, it will ask you several questions at the console. These will set up a single region for you. The configuration will be placed at bin/Regions/Regions.ini which you can then go and edit later on.<br /> <br /> Many of the questions have defaults. Here are some explanations of the questions asked.<br /> <br /> &lt;ul&gt;<br /> &lt;li&gt;'''New region name''' - the name for your region. Don't leave this blank!&lt;/li&gt;<br /> &lt;li&gt;'''Region UUID''' - the unique ID of your region. In pretty much all cases you will want to accept the randomly generated default in the square brackets. The only time when you wouldn't is if you were trying to set up a configuration to point to pre-existing region data. But in this case you are probably better off editing the Regions.ini file directly anyway&lt;/li&gt;<br /> &lt;li&gt;'''Region Location''' - 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). OpenSim regions can be placed anywhere on a 65536 by 65536 grid.<br /> &lt;li&gt;'''Internal IP address''' - This should always be 0.0.0.0 (0.0.0.0 means &quot;listen for connections on any interface&quot;, basically a wildcard) if you want to access this server from the internet or another server on your internal network, this should be the IP&amp;nbsp;address assigned to the OpenSim Server. You should also set up the server to Use a Static IP address, and not DHCP <br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Allow alternate ports''' - This is currently experimental. Please leave it at the default of False.&lt;/li&gt;<br /> &lt;li&gt;'''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) should also work. <br /> &lt;li&gt;'''Master Avatar UUID''' - This is a legacy OpenSim 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.&lt;/li&gt;<br /> &lt;li&gt;'''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&lt;/li&gt;<br /> &lt;li&gt;'''Master Avatar last name''' - The last name of the master avatar.<br /> &lt;li&gt;'''Master Avatar sandbox password''' - The password of the master avatar.<br /> <br /> Be aware of [http://osgrid.org/forums/viewtopic.php?f=5&amp;t=400&amp;start=0&amp;st=0&amp;sk=t&amp;sd=a loopback] problems when Running viewer &amp;amp; server(s) on the same machine (LAN) by using the &quot;external&quot; configuration. (&lt;u&gt;'''You might notice endless waiting for region handshake'''&lt;/u&gt;.) See also [http://opensimulator.org/wiki/Troubleshooting troubleshoot hints]. If you're having Connectivity problems. [http://opensimulator.org/wiki/Network_Settings Be sure to read the Network Configuration Page]. This is important if you see Region handshake issues&lt;/li&gt;<br /> <br /> See [[Configuring_Regions]] for information about the Regions.ini file that these questions generate.<br /> <br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt; To create a user type &lt;/li&gt;<br /> <br /> create user<br /> <br /> in the server console. This will ask you a series of questions for creating a user (such as first name, last name and password).<br /> <br /> &lt;li&gt; To connect to your new sim with your user, start up a Second Life viewer with the following command line switches: &lt;/li&gt;<br /> <br /> '''Client on same machine as OpenSim:''' -loginuri http://127.0.0.1:9000/ -loginpage http://127.0.0.1:9000/?method=login <br /> <br /> '''Client on same LAN as OpenSim:''' -loginuri http://lan_ip:9000/ -loginpage http://lan_ip:9000/?method=login <br /> <br /> Client on different machine or internet:''' -loginuri http://external_ip:9000/ -loginpage http://external_ip:9000/?method=login'''<br /> <br /> Then enter the user name and password you set up in the previous step and your new user should hopefully login.<br /> <br /> &lt;/ol&gt;<br /> <br /> = Running OpenSim in Grid mode =<br /> <br /> Running OpenSim in grid mode is considerably more complicated. Grid services need to be set up and the region simulator configuration needs to be changed to use these instead of the built-in standalone mode ones.<br /> <br /> ==Configuring the grid services==<br /> [[Image:Exclamation.png|left]]<br /> NOTE: The grid servers are in the process of being redesigned. <br /> Some services are now run in a common 'ROBUST' (Basic Universal Server Technology) server shell <br /> while others are still run as separate legacy servers.<br /> &lt;u&gt;'''More Details on ROBUST are Here --&amp;gt;'''&lt;/u&gt;[[ROBUST|&lt;u&gt;'''ROBUST'''&lt;/u&gt;]]&lt;u&gt;'''&amp;nbsp;&amp;lt;--&amp;nbsp; including Conversion From UGAIM To UGRM (0.6.6 -&gt; 0.6.7) and UGRM to URM (0.6.7 -&gt; 0.6.8)'''&lt;/u&gt;<br /> <br /> As of OpenSim 0.6.8, R.O.B.U.S.T. has connectors for the asset (A), grid (G) and inventory (I) functionality. The legacy servers are still required for user (U) and messaging (M) functionality. The steps below will get you up and running. We'll assume that your current directory is bin/ within the OpenSim distribution.<br /> <br /> &lt;ol&gt;<br /> &lt;li&gt;'''Configure the user server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.UserServer.exe&lt;/li&gt;<br /> &lt;li&gt;You will be asked a number of configuration questions. If the grid servers are all on one machine, most defaults are safe to use. The configuration is stored in the UserServer_Config.xml file which can be changed afterwards if necessary.&lt;/li&gt;<br /> &lt;li&gt;The user server will then load and display it's prompt:&lt;/li&gt;<br /> User#<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure R.O.B.U.S.T.'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Copy OpenSim.Server.ini.example to OpenSim.Server.ini. Don't forget to change ConnectionString for your database settings. (on version 0.6.6 copy OpenSim.Services.ini.example to OpenSim.Services.ini - then use OpenSim.Services instead OpenSim.Server)<br /> &lt;/li&gt;<br /> Linux<br /> bin$ cp OpenSim.Server.ini.example OpenSim.Server.ini<br /> Windows<br /> C:\OpenSim\bin&gt; copy OpenSim.Server.ini.example OpenSim.Server.ini<br /> &lt;li&gt;Start OpenSim.Server.exe&lt;/li&gt;<br /> &lt;li&gt;The server will start up it's asset, inventory and grid components and display the R.O.B.U.S.T prompt:&lt;/li&gt;<br /> R.O.B.U.S.T.#<br /> &lt;li&gt;For more information on the R.O.B.U.S.T. configuration file and more information if you are migrating from an earlier release of OpenSim, refer to [[R.O.B.U.S.T.]]&lt;/li&gt;<br /> &lt;/ul&gt;<br /> <br /> &lt;li&gt;'''Configure the messaging server'''&lt;/li&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Start OpenSim.Grid.MessagingServer.exe&lt;/li&gt;<br /> &lt;li&gt;Answer the configuration questions. Again, if all servers are run on the same machine, it's safe to press enter for all questions. The configuration is stored in MessagingServer_Config.xml.&lt;/li&gt;<br /> &lt;li&gt;The server will start and present you with it's prompt:&lt;/li&gt;<br /> Messaging#<br /> &lt;/ul&gt;<br /> <br /> &lt;/ol&gt; <br /> <br /> For information on running the legacy servers, particularly if you're using an older version of before 0.6.7 that doesn't contain the ROBUST framework, see [[LegacyServers]]<br /> <br /> === Summary of commands for running grid service executables ===<br /> <br /> '''&lt;u&gt;Windows&lt;/u&gt;'''<br /> cd bin<br /> OpenSim.Grid.UserServer.exe<br /> OpenSim.Server.exe<br /> OpenSim.Grid.MessagingServer.exe<br /> <br /> '''&lt;u&gt;Linux / Mac OS X&lt;/u&gt;'''<br /> cd bin<br /> mono OpenSim.Grid.UserServer.exe<br /> mono OpenSim.Server.exe<br /> mono OpenSim.Grid.MessagingServer.exe<br /> <br /> ==Configuring regions==<br /> <br /> When first run, a new OpenSim installation will ask you a series of questions to set up one region. If you want to change these settings or set up multiple regions, please see [[Configuring_Regions]]<br /> <br /> ==Configuring and Starting the region simulator==<br /> &lt;ol&gt;<br /> &lt;li&gt;Find the [Architecture] section, comment out the line that says&lt;/li&gt;<br /> Include-Standalone = &quot;config-include/Standalone.ini&quot;<br /> and uncomment the line saying <br /> Include-Grid = &quot;config-include/Grid.ini<br /> <br /> &lt;li&gt;save OpenSim.ini, and go into the config-include directory.&lt;/li&gt;<br /> &lt;li&gt;copy the following files&lt;/li&gt;<br /> GridCommon.ini.example to GridCommon.ini<br /> CenomeCache.ini.example to CenomeCache.ini<br /> FlotsamCache.ini.example to FlotsamCache.ini<br /> <br /> &lt;li&gt;Open all these files (Grid.ini, GridCommon.ini, CenomeCache.ini and FlotsamCache.ini) and edit to suit your needs&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be ready to start up your sim. The mode that OpenSim.exe starts in is normally controlled by a setting in your OpenSim.ini. It defaults to standalone mode if that setting is not specified or the file is not found. If you wish, you can force opensim to start in gridmode on the command line as follows:&lt;/li&gt;<br /> OpenSim.exe -gridmode=true<br /> or if using the ODE physics plugin under 64 bit Windows<br /> OpenSim.32BitLaunch.exe<br /> or:<br /> mono OpenSim.exe -gridmode=true<br /> if you're using Mono under Linux or Mac OSX. <br /> <br /> With any luck, everything will come up without fatal errors.<br /> <br /> If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br /> &lt;tt&gt;ulimit -s 262144&lt;/tt&gt; Or, run the opensim-ode.sh to start up OpenSimulator.<br /> <br /> &lt;li&gt;Go to the UserServer console, and type 'create user' to create a new avatar. It will prompt you for the name and password, and the X and Y of the sim that should be his home location. Use 1000 and 1000, or wherever you told your sim to live when you brought it up in standalone mode. At the console of any of these servers, you should be able to type 'help' to get a list of commands.&lt;/li&gt;<br /> <br /> &lt;li&gt;You should now be able to connect to your new grid with your secondlife client. You need to tell your client to point at the UserServer rather than directly at the sim, though:&lt;/li&gt;<br /> secondlife -loginuri http://127.0.0.1:8002/<br /> 8002 is the default port for the UserServer, and that IP address should be changed to the server you are running the UserServer on, if they are not all on the same box. Happy OpenSimming!&lt;br&gt;<br /> ''Note: if you are using Windows Vista, remember to start servers as Admin. If not it will prompt you an error in console like &quot;Error - Access denied&quot;''<br /> &lt;/ol&gt;<br /> <br /> ==Attaching your sim to someone else's grid==<br /> To set up the region server (i.e., &lt;tt&gt;OpenSim.exe&lt;/tt&gt;) to connect to an external grid, you should edit the &lt;tt&gt;OpenSim.ini&lt;/tt&gt; file in the &lt;tt&gt;bin&lt;/tt&gt; directory. In that file, there is a &lt;tt&gt;[Network]&lt;/tt&gt; section with URLs for the grid, user, and asset servers, as well as send and receive keys (for a basic level of security). The addresses and send/receive keys will vary depending on the grid you are connecting to, and the grid operator should tell you what values to use.<br /> <br /> The other file you may have to change is in your &lt;tt&gt;bin/Regions&lt;/tt&gt; directory. This is where your individual region config files are. If you only have one region, it will by default be called &lt;tt&gt;Regions.ini&lt;/tt&gt; in OpenSim 0.6.7 and later and &lt;tt&gt;regions.xml&lt;/tt&gt; in OpenSim 0.6.6 and earlier.<br /> <br /> This can be edited with any text editor. The grid owner may tell you what X and Y location you can place your sim at (you can't have multiple sims at the same location on the grid). If so, the fields you will need to change in this file are &lt;tt&gt;sim_location_x&lt;/tt&gt; and &lt;tt&gt;sim_location_y&lt;/tt&gt;. And the &lt;tt&gt;external_host_name&lt;/tt&gt; should be set to the hostname or IP address of your simulation server (i.e., the machine that is running &lt;tt&gt;OpenSim.exe&lt;/tt&gt;).<br /> A list of public grids that you can attach your sim to is at [[OpenSim: Grids]]<br /> <br /> =Further notes=<br /> <br /> ==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br /> [[Image:Exclamation.png|left]]<br /> As of OpenSim 0.6.7, the default physics engine for OpenSim was changed to the ODE engine. This is because ODE is by far the most advanced physics engine plugin currently in OpenSim. Unfortunately, it has the drawback in that it's library is not compilable under 64bit in Windows. Therefore, 64 bit Windows users may need to run <br /> <br /> OpenSim.32BitLaunch.exe<br /> <br /> instead of <br /> <br /> OpenSim.exe<br /> <br /> To launch their region simulator.<br /> <br /> 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.<br /> <br /> ==Note About Mono==<br /> 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. <br /> <br /> 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.<br /> <br /> For example: $ export MONO_THREADS_PER_CPU=125<br /> <br /> == Legacy Configuration Information ==<br /> These are some pages containing some legacy configuration information of unknown accuracy.<br /> <br /> [[OpenSim 0.6.6 legacy configuration information]]<br /> <br /> <br /> == Additional Configuration Tasks (for advanced users) ==<br /> <br /> ===OpenSim.exe command line options===<br /> OpenSim.exe has command line options which allow you to perform actions such as reading configuratio nfiles from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br /> <br /> ===Script engine===<br /> OpenSim supports multiple script engines. See [[ScriptEngines]] for details. If you don't know what this means then the default script engine will be fine.<br /> <br /> ===Permissions Configuration===<br /> OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br /> <br /> === Logging ===<br /> By default, OpenSim logs information to a file called OpenSim.log in the bin directory. See [[Logging]] for details on how to further configure this if required.<br /> <br /> === Configuration of region modules ===<br /> * [[IRCBridgeModule]]<br /> * [[Freeswitch_Module]]<br /> * [[Offline Messaging]]<br /> <br /> === Configuration of Metaverse Exchange Protocol (MXP) ===<br /> * [[Metaverse Exchange Protocol]]<br /> <br /> === Configuration of Web Server and Pages===<br /> OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br /> * [[External Files]]<br /> * [[Internally Generated]]<br /> <br /> [[Category:Configuration]]</div>

Dale Mahalko