MantisBT - opensim
View Issue Details
0006612opensim[REGION] Specific OpenSim Modulepublic2013-04-28 07:532013-10-17 13:36
Michelle Argus 
master (dev code) 
all current
Standalone (1 Region) , Standalone (Multiple Regions) , Grid (1 Region per Sim) , Grid (Multiple Regions per Sim)
Unknown, Mono / Linux32, Mono / Linux64, Mono / Windows, Mono / OSX
0006612: [Remote Admin] Create Region fails.
Creating a new region with using the Remote Admin module fails, if the specified Estate does not already exists and the there is no Scene loaded yet. I have added the Warning as Additional Info.

 In all other cases creating a region works fine.

 I have located the problem. When a new Estate needs to be created, RemoteAdmin checks if the estateowner exists. As there is no scene loaded, the sim cannot verify the estateowner via GetUserAccount() which requires SceneManager.CurrentOrFirstScene to be available.

 Havn't got time to find a soulution, but will fix it once there is time...
- Set allow_regionless = true in OpenSim.ini
- Remove all region.ini files
- start the regionless sim
- Create a new region with the RemotAdmin command "admin_create_region" with a new estatename which is not already in the estate tables
[RADMIN]: CreateRegion: new request
16:32:00 - [RADMIN]: Method admin_create_region failed. Exception Object reference not set to an instance of an object at OpenSim.ApplicationPlugins.RemoteController.RemoteAdminPlugin.XmlRpcCreateRegionMethod (Nwc.XmlRpc.XmlRpcRequest request, Nwc.XmlRpc.XmlRpcResponse response, System.Net.IPEndPoint remoteClient) [0x00000] in <filename unknown>:0
  at OpenSim.ApplicationPlugins.RemoteController.RemoteAdminPlugin.InvokeXmlRpcMethod (Nwc.XmlRpc.XmlRpcRequest request, System.Net.IPEndPoint remoteClient, System.Action`3 method) [0x00000] in <filename unknown>:0
No tags attached.
Issue History
2013-04-28 07:53Michelle ArgusNew Issue
2013-10-17 03:21hack13Note Added: 0024496
2013-10-17 12:43justinccNote Added: 0024506
2013-10-17 13:36Michelle ArgusNote Added: 0024512

2013-10-17 03:21   
Confirmed! This is still an issue even in current master!
2013-10-17 12:43   
Yes, this is architecturally difficult to fix. It shouldn't be necessary to have a scene to perform UserAccount operations but unfortunately that's how it is structured.

It might be possible to separately initialize a UserAccount connector but this is may not be very straightforward.
Michelle Argus   
2013-10-17 13:36   
right, Justin.

 For now I have a workaround on my OS by skipping GetUserAccount() if there is no Scene available. In this case I simply asume the agent uuid passt on to RA is correct. That workaround is however not something I would want to see implemented in core as it also may mess up things when not used correctly...