Princessrose Faerye asked:

got this message,,,

[23:01] WW of Meeroos HUD V1.2: 503 - Error reaching Meeroo DB
[23:01] WW of Meeroos HUD V1.2: 503 - Error reaching Meeroo DB
[23:01] p-x : 503 - Error reaching Meeroo DB

should i be worried??

ANSWER: As far as I know, everything is okay. No more baby ready nests! Please! :D

The error reaching database can happen during a hiccup in the relay of information between Second Life and our database. More often than not, this is due to Lag within Second Life - not passing the buck on this, it is one potential factor in any given scenario. It can also be because at that moment the server is bottlenecked, but typically the error-reporting Meeroo is fine once he catches up.

Once in awhile you will see this error out of nowhere, even when you aren't interacting with your Meeroos! This is because the Meeroos occasionally call in to let the database know they are there, functioning and eating. They will try again, despite the error to update their status. The reason they call home is so that we can help troubleshoot and debug specifically anomalous regarding a Meeroo that is suffering issues. Also, so we can validate the Meeroo as authentic when we have to call one back that has been gobbled up by the asset server or ran to the wild thinking it was a duplicate (That bug is the bane of my existence! The bug that shall not be named!)