Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Calling all brilliant minds in SL. And anyone else who cares to input their ideas.

Sean Martin
Yesnomaybe.
Join date: 13 Sep 2005
Posts: 584
10-08-2008 19:20
:edit: That title sounds insulting doesn't it. Sorry.. lol. I'm one of the not so brilliant when it comes to this stuff. :rolleyes:

First of all, thanks to Matthew Linden and all others who are working on this issue. But I figured it couldn't hurt to tap the brilliant minds of the SL residents. ;)

THE PROBLEM:
I have owned land in Ambat for a long time now. And a few months after i got it, some years ago, I found I could no longer permanently change my land description, my land title, and now i believe it also effects the land pic.
So to clarify, I can change the data in the input box on my land description, title, and i can change the pic. BUT it does not stay after the sim resets. It's not permanent so i have to redo this just about every time i log in.

TESTS & OTHER INFO:
I have attemted to "kick" the server into seeing the new info. I have tried joining, splitting, buying more land and even dedicating part of my land to a public sandbox that i host. (Which now has the same problems) I also had to rebuild parts of my shop after things returned from changing the group to see if that worked.
But nothing yet.
The server simply reverts all info back after it is either forced to reset from some type of lag or a manual reset for ghost prims in the sandbox. Which is another big issue going on in this sim.

The sim resets often because of the Ambat info hub i believe. So I'm forced to change my info nearly every time i log in.
That said.. Lindens, please don't delete the Ambat info hub as a "fix". I like the info hub and helping new people there. I dedicated half my land to a sandbox for them. (I heard that a few other info hubs have disappeared over the years.)
Oh by the way, it also happens to the sandbox land now. When i first made the sandbox durring all of this mess it worked fine. Apparently when a person gets new land from someone else then it kicks their description and other info in. But after that it doesn't allow any changes. I'm guessing everyone in this Ambat sim is having the issue. If they haven't sent a ticket in about it then i guess they don't need to update their description that often.

Ok anyway now here is a few more interesting bits of info.
After i changed the info for my land for about the 1634th time.. I noticed that my listing in the search sometimes shows the old info.. and at other times shows the new. If you keep clicking the Vetox listing, in the places search tab, say about 30 or so times.. you'll see the listing info flip back and forth between the old info and new.

THEORIES:
It's almost as if the server is holding the new info in RAM and not storing it to the hard disk, or asset server? Thats the only thing i can think of. I'm really not sure how they work officially.
Thats why I thought some of the residents may have ideas as to why this is happening.
_____________________
Sindy Tsure
Will script for shoes
Join date: 18 Sep 2006
Posts: 4,103
10-08-2008 20:20
Wow.. That's pretty weird.

Each region has a "simstate" file that's got a list of all the stuff rezzed in the region and, I think, all the info on how the land is split up along with parcel owner/names/pics and all that. Basically, it's what it sounds like - the "simstate" is the state of the sim.

Every once-in-a-while, every 10 minutes?, the sim dumps all its info into this file and that file gets saved off somewhere. When LL does a rollback on a region, all they're really doing is shutting down the sim and restoring one of these backup simstate files.

It sounds like something in this process has gone all funky and it's not saving the correct parcel info. Has Michael said anything about the simstate file? Like, "I poked around in the simstate and the correct info's there." sorta thing?

Sadly, I don't think any non-Linden is going to know more about this than Michael. I guess you could add a JIRA for this and try to lure a dev into looking at it. That or maybe hit up somebody like Andrew or Zero at their office hour, though they're not support people and probably won't be able to look at the problem.
Sean Martin
Yesnomaybe.
Join date: 13 Sep 2005
Posts: 584
10-10-2008 00:48
Yeah the lindens have looked at it. And they tell me the data looks normal.
Yet I keep getting all of it reverted.

Matthew Linden still has the support ticket as 'Work in Progress'. Though the color changed to black instead of blue.. Dunno what that means. lol

I noticed the day after posting this.. I can no longer get the info to flip around in the search listing. hmm.
_____________________
Qie Niangao
Coin-operated
Join date: 24 May 2006
Posts: 7,138
10-10-2008 04:27
If I had this problem, I'd try deeding the whole parcel to a group for maybe a day, trying some new parcel info while it's owned by that group, then buying it back and trying again to get new parcel info to "stick".

That very well may not work at all, because I'm pretty sure the parcel retains its UUID through change of ownership, and it's a fair bet that whatever is wacky, is wacky by UUID. The split-and-join thing probably also retained the UUID because the larger side of the split retains the UUID, and determines the UUID when re-joined, so whatever is corrupted there would just come back in force after the operations were complete.

So the only hope of the above suggestion working is that the corruption is a function of both the owner and the parcel ID.

Failing that, and still on the premise that it's really a parcel ID corruption, one could try a two-step splitting:

- first cutting the parcel almost in half, creating subparcels A (larger--retaining the original UUID) and B (smaller),

- then cutting A almost in half, creating A' (larger, again retaining the original UUID), and C (smaller);

- then joining B and C, creating a parcel D that's larger than A';

- and finally joining D and A', the result of which should get D's UUID, and the assumed-corrupted original UUID should be gone for good.

Naturally, this will totally hose any existing Search for the parcel, and probably Landmarks and Picks and... God only knows what all else.

And of course, whatever causes the flakiness will happen again, because it already happened to the separate sandbox parcel. So may want to coordinate any radical fix attempts with LL's efforts, in case they can get to the root cause.