Our website is made possible by displaying online advertisements to our visitors.
Please consider supporting us by disabling your ad blocker.
Please consider supporting us by disabling your ad blocker.
OpenSimWorld is the directory of 3D Virtual Worlds based on OpenSimulator and connected through the HyperGrid. Learn More
At the present time, Amoa Nude Beach is experiencing technical difficulties. I cannot say how long this will take to repair, but I apologize for this asset issue happening a second time in 2 weeks.
It is apparently being caused by Dreamgrid software that I, nor the grid owners have control over, which causes a failure of assets.
So we have missing textures, failing scripts, body in-completions among the most notable. I will have to redo alot of it again. Sorry for the inconvenience.
It is apparently being caused by Dreamgrid software that I, nor the grid owners have control over, which causes a failure of assets.
So we have missing textures, failing scripts, body in-completions among the most notable. I will have to redo alot of it again. Sorry for the inconvenience.
Liked by: 
Comments
Thanks everyone. It is not a FS issue or Barefoot Dreamers. It is based on the Dreamgrid Robust Asset Server disconnecting.
It happened 2 weeks ago. All the new additions and changes, were completly disconnected. SO things that were scripted, suddenly the script doesn't exist anymore and the object fails. Anything uploaded in recent period, suddenly had no UUid or existed. So Our bodies disintegrated, Stats counter or something like that failed to work because the scripts in them were gone. The ocean looked like an Iceburg floated into the tropics because the texture for the ocean, disappeared.
The previous failure, the entire TROPICAL area looked like a Blizzard hit it because of all the failed textures leaving everything default white.
Poor Huga is almost bald from pulling her hair out. The reason was caused by Fred installing PHP8 which is a completely useless failure like PHP 6 was. But of course Fred just loves fixing what isn't broken, must be the vax. So it took alot of work to restore, than adding new things, and then when everything runs top speed and looking good, BOOM another Ice Storm of the Tropics, pissed off first time visitors and you are left with half rezzed residents of that grid who's huds dont function because scripts YOU WROTE, are now gone.
like(1)
It happened 2 weeks ago. All the new additions and changes, were completly disconnected. SO things that were scripted, suddenly the script doesn't exist anymore and the object fails. Anything uploaded in recent period, suddenly had no UUid or existed. So Our bodies disintegrated, Stats counter or something like that failed to work because the scripts in them were gone. The ocean looked like an Iceburg floated into the tropics because the texture for the ocean, disappeared.
The previous failure, the entire TROPICAL area looked like a Blizzard hit it because of all the failed textures leaving everything default white.
Poor Huga is almost bald from pulling her hair out. The reason was caused by Fred installing PHP8 which is a completely useless failure like PHP 6 was. But of course Fred just loves fixing what isn't broken, must be the vax. So it took alot of work to restore, than adding new things, and then when everything runs top speed and looking good, BOOM another Ice Storm of the Tropics, pissed off first time visitors and you are left with half rezzed residents of that grid who's huds dont function because scripts YOU WROTE, are now gone.
Not sure its Dreamgrid (Fred) I'm thinking its something else completely no reason to start pointing fingers without full knowledge at what is wrong or how it happened.
like(2)
Last time was due to PHP 8 installation by him. So at this point, with nothing else done by either grid or region, leaves this as a likely culprit.
like(2)
I use a older version in my 2 grids, Reason is because if it works why change to the latest. I always go by if it ain't broke why fix it reasoning. I don't know just saying. But good luck over there.
like(3)
Thanks and I agree with that. Most times you rarely have to upgrade anything unless of course it would affect things on a major scale. I am not the type that needs the latest and greatest. I prefer performance and reliability over being cooler.
like(1)
I know you are frustrated but let's look at this shall we? Databases can get corrupted easily and here is how.
A Robust Asset Server disconnect can be caused by a variety of issues, including:
Network Connectivity Problems:
Internet Outages: Fluctuations or interruptions in the internet connection.
Network Congestion: High traffic can overwhelm the network, causing timeouts or disconnects.
Firewall/Router Issues: Misconfigured firewall settings or router problems can block or limit the connection to the asset server.
Server-Side Issues:
Hardware Failures: Issues such as failing hard drives, insufficient memory, or overheating components.
Server Overload: Excessive demand on the server resources, leading to crashes or slowdowns.
Power Failures: Unstable power supply or outages causing the server to go offline.
Database Issues:
Corruption: Corruption of the database that the asset server relies on.
Connection Problems: Issues with connecting to the database, including authentication failures or network issues.
Performance Bottlenecks: Slow database queries or excessive database load causing delays and timeouts.
External Dependencies:
Third-Party Services: Dependencies on external services or APIs that are experiencing outages or issues.
Cloud Services: If hosted on cloud infrastructure, issues with the cloud provider can impact server connectivity and performance.
Security and Access Control:
Unauthorized Access: Security breaches or hacking attempts disrupting normal operations.
DDoS Attacks: Distributed Denial of Service attacks overwhelming the server with traffic.
Misconfigured Permissions: Incorrectly set permissions causing access issues or conflicts.
Environmental Factors:
Physical Damage: Damage to server infrastructure due to environmental factors like fire, flooding, or earthquakes
.
Maintenance Issues: Scheduled or unscheduled maintenance disrupting server availability.
Dreamgrid Software has been working flawlessly for me for over four years. Yes bugs do occur, and get cleaned up quickly, and there is new security patches that need to be released- that is why there may be ongoing updates. Maintenance of the grid is Key, all these variables affect the grid. Because someone is vaccinated or not has nothing to do with how your grid is maintained.
like(1)
A Robust Asset Server disconnect can be caused by a variety of issues, including:
Network Connectivity Problems:
Internet Outages: Fluctuations or interruptions in the internet connection.
Network Congestion: High traffic can overwhelm the network, causing timeouts or disconnects.
Firewall/Router Issues: Misconfigured firewall settings or router problems can block or limit the connection to the asset server.
Server-Side Issues:
Hardware Failures: Issues such as failing hard drives, insufficient memory, or overheating components.
Server Overload: Excessive demand on the server resources, leading to crashes or slowdowns.
Power Failures: Unstable power supply or outages causing the server to go offline.
Database Issues:
Corruption: Corruption of the database that the asset server relies on.
Connection Problems: Issues with connecting to the database, including authentication failures or network issues.
Performance Bottlenecks: Slow database queries or excessive database load causing delays and timeouts.
External Dependencies:
Third-Party Services: Dependencies on external services or APIs that are experiencing outages or issues.
Cloud Services: If hosted on cloud infrastructure, issues with the cloud provider can impact server connectivity and performance.
Security and Access Control:
Unauthorized Access: Security breaches or hacking attempts disrupting normal operations.
DDoS Attacks: Distributed Denial of Service attacks overwhelming the server with traffic.
Misconfigured Permissions: Incorrectly set permissions causing access issues or conflicts.
Environmental Factors:
Physical Damage: Damage to server infrastructure due to environmental factors like fire, flooding, or earthquakes
.
Maintenance Issues: Scheduled or unscheduled maintenance disrupting server availability.
Dreamgrid Software has been working flawlessly for me for over four years. Yes bugs do occur, and get cleaned up quickly, and there is new security patches that need to be released- that is why there may be ongoing updates. Maintenance of the grid is Key, all these variables affect the grid. Because someone is vaccinated or not has nothing to do with how your grid is maintained.
Great list and advice Marianna, however all of those had been checked from my side. Based on grid owner feedback, all of these had been checked. The only one that MAY be a possibility is "cloud" services were are crap and leaving you vunerable to their failures. Based on my experience, I wouldn't doubt that Fred put his on "cloud" crap. I personally never put anything of my own on anything cloud. If you ever read the fine print, anything and everything created on cloud, becomes the property of the cloud owner such as Amazon. Good luck taking their legal team on in an intellectual property battle in court. This website I know uses it.
So that is is a great list, and I am experienced enough to check all of it immediately from my end. However, I cannot check the asset server on Fred's end.
like(1)
So that is is a great list, and I am experienced enough to check all of it immediately from my end. However, I cannot check the asset server on Fred's end.
There's no "cloud crap" involved. This is 100% stock, released Opensim 0.9.2.2 with a few lines comments out that spam the console and addition of one function for Smart Boot. There is no asset server on "Fred's end". It's entirely on the grid owners system. There are only two relevant things that make up an opensim server: Opensim\bin\fsassets, and mysql\data. Everything else is a cache or code. A few settings in a file here and an image there. That's it. I have worked with Fred now for over four years, I know for a fact he wants to see everyone up and running including Barefoot Dreamer's Grid.
like(0)
I do see the OS Version but as for it's hosting, being on a server farm like Contabo, that could be the cloud crap. Someone did check and saw that asset server corruption is the most likely culprit. However, for it to be sudden, and affecting things that had been in place for years, means it goes beyond that. The 2 week prior incident, proved that upon an .oar reset, once complete, all textures and scripts were restored. For 2 weeks following, not a problem, speed increased and then, it started with missing eyeballs and avalanched into many issues.
The record indicated from the first time, it was Fred's implementation of PHP 8 that was piped through his "updates" that caused it.
If Fred didn't go proactively block me a year ago when Barefoot had issues and I was trying to help, I could have had more information to assist. But he chose that path, so I am left to assume all of the information based on knowledge from MY end only.
The situation affects the whole grid, not just Amoa. It affects Dreamgrid. It also affects Huga personally who has had to deal with irate customers and has been pulling her hair out. To put this poor lady through this because of Fred's assinine blocking of people, (who never even spoke before) trying to help her, is on Fred as well. So to solve this issue, would be a paramount concern for any and all Dreamgrid owners. It might be safe to presume that this is something that will happen not IF but WHEN to all Dreamgrid owners.
like(1)
The record indicated from the first time, it was Fred's implementation of PHP 8 that was piped through his "updates" that caused it.
If Fred didn't go proactively block me a year ago when Barefoot had issues and I was trying to help, I could have had more information to assist. But he chose that path, so I am left to assume all of the information based on knowledge from MY end only.
The situation affects the whole grid, not just Amoa. It affects Dreamgrid. It also affects Huga personally who has had to deal with irate customers and has been pulling her hair out. To put this poor lady through this because of Fred's assinine blocking of people, (who never even spoke before) trying to help her, is on Fred as well. So to solve this issue, would be a paramount concern for any and all Dreamgrid owners. It might be safe to presume that this is something that will happen not IF but WHEN to all Dreamgrid owners.
Many things continue to work despite everything, (even my translator ;-) so the region is still visitable!
In the meantime (I'm still thinking... ;-) the next week's resurrection coming!
like(2)
In the meantime (I'm still thinking... ;-) the next week's resurrection coming!
Yes Ankh is correct. You are able to visit. But I would recommend not expecting all furniture, vehicles or features to work because of missing scripts now. Also, I swear it is not an iceburg in the water along all shores. It is due to the textures missing. Same with trees and other aesthetics.
like(2)
Sorry this is happening to you. Crashes or improper shutdowns of the server can lead to asset data not being saved correctly. Which causes asset issues. Also, Network interruptions or latency can cause problems with asset retrieval and storage, leading to incomplete or missing assets. Many reasons as to why this occurs. Error logs help to identify the cause. Assets need time to load and save. Sometimes just cleaning your cache and grid caches clears things up.
like(2)
That sounds bad ... We have dreamgrid too ... was this the latest update? Or another version?
I am very sorry to hear this happened to you :(
Kinda scary ..
like(3)
I am very sorry to hear this happened to you :(
Kinda scary ..
I honestly do not know since it is not my grid. I appreciate it, but there isn't much I can do as I built Amoa for Barefoot Dreamers and simply built it, run it and maintain it as a volunteer)). It is safe to assume it is Fred's fault as the cause. Last time was caused by him trying to implement garbage PHP 8 which is worse than epic failure PHP 6. I am confident in saying that he did it again and it gets passed through any update. When things run smoothe and perfect, let that be a warning that Fred will a way to fix what isn't broken and cause you to experience this. If I am wrong, I would love to know, but I cannot think of any other reason that this.
like(2)