Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors after restart from region #245

Open
BogusCurry opened this issue Feb 20, 2017 · 7 comments
Open

Errors after restart from region #245

BogusCurry opened this issue Feb 20, 2017 · 7 comments
Labels
Projects
Milestone

Comments

@BogusCurry
Copy link

BogusCurry commented Feb 20, 2017

Hi there ;D
I would restart a region, but not change in the root path. I becomes this erros messages and crash the region server.
https://paste.md-5.net/doyenobotu.avrasm

Maybe is not a bug, but I think the user must become a message, thats he must change in the root path or ?

Data:
Ubuntu 16.04 64bit.
Last repo from git
Server, not local

Greetings

Bogus
Founder from GridTalk.de

@fly-man- fly-man- added the bug label Mar 20, 2017
@fly-man- fly-man- added this to the 0.9.5 milestone Mar 20, 2017
@fly-man-
Copy link
Member

This is most likely a bug that is basically not a bug

The restart function has been failing for some time now, not sure if it's even worth using.

A full shutdown and restart would always be better then a restart

@greythane
Copy link
Member

Part of the processing is to change back to the 'root' before the restart.
This error appears to be associated with serialising the user data.

Where you the only user logged in?
Where there other users in the sandbox region during the restart?
Where there other users on another region during the restart?

@emperorstarfinder
Copy link
Contributor

You wouldn't necessarily need to change back to root to restart a single region being run by the instance. The Region Restart will in fact work if you have the region set to Sandbox via the change region command. If you were wanting to restart all the regions in the instance then you would change to root.

Also keep in mind that if an avatar was in the region at the time of the restart of the region then it is likely to throw an error but shouldn't cause the region to crash (or the console for that matter) as we had added in the ability to restart regions even with avatars in the region.

I have stumbled on instances before where inputting the command incorrectly or a command which isn't recognized could cause the console to crash.

That being said "Reference not set to an instance of an object" messages usually means that it cannot find the specific item it is looking for. I am sure that the following suggestions for debugging are probably in place but because stranger things do happen (even with old hands), here are a couple things to check to help verify there is an actual bug and not a strange occurrence:

  1. Verify that the .sim file for your region is in the Data/Regions folder (it should be there but just in case a strange occurrence put it elsewhere)
  2. Verify the command you input (and if possible provide the command you used for further testing). In this way. It is possible the command used is not being recognized and is causing the console to crash (Not as likely but it is possible).

I will attempt to test this further as well in order to verify the commands and the restart process.

@BogusCurry
Copy link
Author

BogusCurry commented Mar 21, 2017

Oh my, that is so long, sorry I can't remmember what I have do.

Hmm .. the regionname is sandbox, I have not set the region to a sandbox. And one user was logged in on the region. So I have make the restart as I was on the region ;D

Have a nice Day ;D

Bogus | Founder of GridTalk.de | WhiteCoreSim.de

@emperorstarfinder
Copy link
Contributor

When an avatar is in the region during a region restart the viewer will go grey for 10 to 20 seconds while the region restarts and then will recover all functionality. This lets users stay in the region and logged in during a region restart. After the region restarts and functionality is recovered by the viewer the user can continue on with what they were doing without any negative impact.

@BogusCurry
Copy link
Author

@emperorstarfinder What will you me say ?

@emperorstarfinder
Copy link
Contributor

Guess I am not sure what your asking here with your last comment. However my internal testing shows the region restart is working as it is supposed to be.

@fly-man- fly-man- added this to Issues in 0.9.5 Mar 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
0.9.5
Issues
Development

No branches or pull requests

4 participants