MantisBT - opensim
View Issue Details
0008269opensim[REGION] OpenSim Corepublic2017-11-22 12:352019-02-06 11:29
closednot fixable 
master (dev code) 
Standalone (1 Region)
Mono / Linux64
0008269: SIGQUIT is not interpreted by "mono OpenSim.exe"
using mono or mono

when sending a SIGQUIT to the "mono OpenSim.exe" process, the console is displaying a lot an errors like :

Full thread dump :

"STP:PoolService:0" at <unknown> <0xffffffff>
"<unnamed thread>" at <unknown> <0xffffffff>
"PollServiceWatcherThread:10100" at <unknown> <0xffffffff>
"Timer-Scheduler" at <unknown> <0xffffffff>

but the simulator is still functionning
get the simulator pid like using :

PIDFile = ""

and then use (if the process has the pid 1234):
kill -3 1234

and watch the console (the sim is not stopped and is filled with errors)
No tags attached.
related to 0008090closed melanie UnixSignals setup should be more graceful 
Issue History
2017-11-22 12:35ssm2017New Issue
2017-11-22 12:44ssm2017Note Added: 0032459
2017-11-22 14:47ssm2017Note Added: 0032460
2017-11-23 00:51ssm2017Relationship addedrelated to 0008090
2017-11-23 00:53ssm2017Note Added: 0032461
2017-11-23 00:53ssm2017Statusnew => resolved
2017-11-23 00:53ssm2017Resolutionopen => not fixable
2017-11-23 00:53ssm2017Assigned To => ssm2017
2019-02-06 11:29BillBlightNote Added: 0034406
2019-02-06 11:29BillBlightStatusresolved => closed

2017-11-22 12:44   
after beeing informed by JeffKelley, the wiki is saying this : [^]

wouldn't it be better for OpenSim.exe to begin the "shutdown" process instead of returning a dump when receiving a SIGQUIT ?
2017-11-22 14:47   
i can see in the code that SIGTERM should be interpreted.
depending on versions of mono it is either kill the process either do nothing.
i will try to investigate mono versions about that on tomorrow
2017-11-23 00:53   
ok, it looks like a "mono" issue.
when sending a SIGTERM, the console suddenly stops without triggering the "shutdown" and displays "Terminated". (depending on OpenSimulator version and mono version...).
closing this issue
2019-02-06 11:29   
Marked as Resolved but never closed, can be reopened if needed.