Do you see that when you start the region? If so, it *could be* corrupt region data rather than bad assets. I really don't know what could have caused something like that in your case but I'd suspect a corrupt region database. I hope you have a recent oar or other backup of your region. I'd suspect that killing your region process with ctrl-C or some other abnormal termination might cause this. Even if not, it's a good practice to stop a region with the "quit" console command.
On Mon, Apr 20, 2015 at 10:41 AM, Thomas Ringate <[email protected]> wrote: > I found one of the bad assets on one region so far. It's problem was it > had a texture of a null UUID. > It was invisible because of this. I had to delete it in the regions MySQL > database to get rid of it on the region. > > Oddly enough I was both the owner and creator of this object that was > floating in the air and could not be seen as if it did not exist at all. > Even turning on transparency did not show the abject. > > I suspect this was not caused by the asset server crash, other than I did > not see the error in the old logs I have. > > I have IAR's and log files going back to 2011 for all my regions. When I > said I would use an OAR to reload the region, > I was thinking of using an OAR from a time when the logs showed no errors > of any assets. > > My real issue is with the strange new errors which there are dozens of. I > never saw those kinds of errors before, > and I have no idea what the error is even telling me. > > How do I fix an asset that gives this kind of error? > > 2015-04-20 04:09:10,251 DEBUG - > OpenSim.Region.Framework.Scenes.Serialization.SceneObjectSerializer > [SceneObjectSerializer]: Parsing PrimitiveBaseShape for object part > Primitive 7bcf0eba-c86d-4cf9-8f09-77eb0bc371d0 encountered errors in > properties FlexiDrag, FlexiGravity. > 2015-04-20 04:09:10,252 DEBUG - > OpenSim.Region.Framework.Scenes.Serialization.SceneObjectSerializer > [SceneObjectSerializer]: Parsing PrimitiveBaseShape for object part > Primitive 1bc76a3d-c8aa-4d24-88eb-e311335588e0 encountered errors in > properties FlexiDrag, FlexiGravity. > > I see over 65 of those errors on startup on one region. Other regions > have none, and some only have a few. > > I never saw those errors prior to the grid crash. > > But then opensim has 7 months of development work on it since the crash so > opensim isn't the same program either that it was last August. > > Tom > > -----Original Message----- From: Eric Riebling > Sent: Monday, April 20, 2015 9:35 AM > To: [email protected] > Subject: Re: [Opensim-users] Recent request from OSgrid about reloading > badassets > > > Wouldn't reloading from OAR just bring in the same bad asset, by UUID? > > For what it's worth: > > I came across only one bad asset after the big asset server restore, which > traced to some component of an AO. I never did find the exact asset that > went bad, but was able to get rid of the viewer error about bad asset by > re-creating the AO from it's pieces. > > Come to think of it, might have been a texture. I remember the AO rezzing > with a funny texture where a HUD image should have been. > > On 04/20/2015 08:00 AM, [email protected] wrote: > >> Recent request from OSgrid about reloading bad assets >> > > -- > > Eric Riebling Interactive Systems Lab > [email protected] 407 South Craig St. > > _______________________________________________ > Opensim-users mailing list > [email protected] > http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users > _______________________________________________ > Opensim-users mailing list > [email protected] > http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users >
_______________________________________________ Opensim-users mailing list [email protected] http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
