MantisBT - opensim
View Issue Details
0008090opensim[REGION] OpenSim Corepublic2016-12-12 00:442019-02-06 11:29
Mono 4.2.2Linux x863.2.0
master (dev code) 
Standalone (1 Region)
Mono / Linux32
0008090: UnixSignals setup should be more graceful
On this configuration, the OpenSim.exe barely gets off the ground, when it tries to instantiate new UnixSignals. The stack trace below is what is returned when I wrapped the new code in a try/catch block.

Regardless of if this is an issue with the Mono configuration or system libraries, we should probably be a little more graceful.
1. Try to start OpenSim.exe

(Underlying issue may be too old of a Mono version, or missing configuration option in Mono.)
03:39:20 - [CONFIG]: Loading environment variables for Config
03:39:20 - [OPENSIM MAIN]: Using async_call_method SmartThreadPool
03:39:20 - [STARTUP]: Beginning startup processing
03:39:20 - [STARTUP]: version: OpenSim Dev 1aaf1e2
03:39:20 - [STARTUP]: Operating system version: Unix, .NET platform Unix, 32-bit
03:39:20 - ====================================================================
03:39:20 - ========================= STARTING OPENSIM =========================
03:39:20 - ====================================================================
03:39:20 - Failed to set up POSIX signals: System.TypeInitializationException: The type initializer for 'Mono.Unix.UnixSignal' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Mono.Unix.Native.Stdlib' threw an exception. ---> System.EntryPointNotFoundException: Mono_Unix_VersionString
  at (wrapper managed-to-native) Mono.Unix.Native.Stdlib:VersionStringPtr ()
  at Mono.Unix.Native.Stdlib.VersionCheck () <0xb47a1950 + 0x00027> in <filename unknown>:0
  at Mono.Unix.Native.Stdlib..cctor () <0xb47a1b28 + 0x0024f> in <filename unknown>:0
  --- End of inner exception stack trace ---
  at Mono.Unix.UnixSignal..cctor () <0xb47a1248 + 0x00063> in <filename unknown>:0
  --- End of inner exception stack trace ---
  at OpenSim.OpenSim.StartupSpecific () <0xb47a0390 + 0x000b7> in <filename unknown>:0
03:39:20 - [LOCAL CONSOLE]: Persistent command line history is Enabled, up to 100 lines from file /opt/erfgrid/sim/opensim/bin/OpenSimConsoleHistory.txt
03:39:20 - [LOCAL CONSOLE]: Read 100 lines of command line history from file /opt/erfgrid/sim/opensim/bin/OpenSimConsoleHistory.txt
03:39:20 - [SERVER BASE]: Starting in /opt/erfgrid/sim/opensim/bin
03:39:20 - [SERVER BASE]: OpenSimulator version: OpenSim Dev 1aaf1e2
03:39:20 - [SERVER BASE]: Operating system version: Unix, .NET platform Unix, 32-bit
Console log level is ALL
03:39:20 - [SERVER BASE]: Logging started to file /opt/erfgrid/sim/opensim/bin/OpenSim.log
03:39:20 - [MIGRATIONS]: RegionStore data tables already up to date at revision 43
03:39:20 - [WATCHDOG]: Started tracking thread Non-blocking non-critical job engine, ID 11
No tags attached.
has duplicate 0008091closed melanie Crash on region initialize 
related to 0008269closed ssm2017 SIGQUIT is not interpreted by "mono OpenSim.exe" 
patch 0001-Let-s-be-a-little-more-graceful-with-the-Unix-specif.patch (1,633) 2016-12-12 00:49
Issue History
2016-12-12 00:44TomTheDragonNew Issue
2016-12-12 00:48TomTheDragonNote Added: 0031426
2016-12-12 00:49TomTheDragonFile Added: 0001-Let-s-be-a-little-more-graceful-with-the-Unix-specif.patch
2016-12-12 00:50TomTheDragonStatusnew => patch included
2016-12-12 01:02TomTheDragonRelationship addedhas duplicate 0008091
2016-12-12 01:22BillBlightNote Added: 0031427
2016-12-12 01:31melanieStatuspatch included => resolved
2016-12-12 01:31melanieResolutionopen => fixed
2016-12-12 01:31melanieAssigned To => melanie
2017-11-23 00:51ssm2017Relationship addedrelated to 0008269
2019-02-06 11:29BillBlightNote Added: 0034407
2019-02-06 11:29BillBlightStatusresolved => closed

2016-12-12 00:48   
This is a quick and dirty fix, since the Unix signals are a nice feature to have but should not totally block starting a region at all.
2016-12-12 01:22   
Did not see this one before I posted mine, must have been almost at the same time ..

I have applied this patch to my builds ...

Now back up and running ...
2019-02-06 11:29   
Marked as Resolved but never closed, can be reopened if needed.