Well, this may or may not fix your problem. But, it is a chance to improve things.
The problem some are seeing is texture and mesh fetching errors, which means regions and/or avatars are failing to render. When that happens things may be odd shaped or never appear and they stay gray. If you look in your Second Life™ log files you’ll find errors like these:
LOG Error Examples
newview/lltexturefetch.cpp(1575) : 2015-03-31T03:12:25Z INFO: LLTextureFetchWorker::doWork: HTTP GET failed for: http://bake-texture.agni.lindenlab.com/texture/4c4ab9a6-0d19-4428-957e-bd283729474c/lower/dbb84db1-e… Status: Easy_28 Reason: ‘Timeout was reached’
2015-03-13T02:01:48Z INFO: LLTextureFetchWorker::doWork: HTTP GET failed for: http://asset-cdn.agni.lindenlab.com/?texture_id=65e28e31-9700-7784-4181-796869041279 Status: Easy_28 Reason: ‘Timeout was reached’
Oz explains that above error messages indicates either a texture or mesh download failed.
Oz and Monty Linden have been responding to a forum thread: Rez Failures & CDN Issues during Peak SL times? 5:30pm SLT – 9pm ish? Nightly?
The URL with asset-cdn indicates the attempt that failed was from a request to a CDN server. The above URL referencing bake-texture is an avatar baked texture, which also uses the same CDN service. The name difference according to Oz is just a legacy thing that evolved as the system grew.
If your having problems and are fairly certain it is CDN, Monty suggests you try these troubleshooting steps: (I’ve added my spin)
- In the viewer change these Debug Settings:
- Mesh2MaxConcurrentRequests (set to 3)
- TextureFetchConcurrency (set to 3)
- Shut down the viewer.
- Examine your log for texture failures. You are interested in the number of them. If you search on ‘HTTP GET failed’ using find all your editor often gives you a count.
- Clear the viewer cache – while this is normally a last resort step, it is needed here to create a better viewer log for troubleshooting.
- Restart the viewer.
- Go to a region you are having problems with.
- Give it 10 or 15 minutes then close the viewer.
- Examine to log again looking for failures. 404 Not Found errors are unrelated to CDN issues. Well, may be… I have thousands of those.
- If that has NOT helped, repeat this process and add on more setting.
- HttpPipelining (set to false) – Monty says, “Combined with the previous two, it may be a very slow load but I’m interested in error-free first.”
Your log file is in:
Win 7 & 8: C:\Users\[Win_Login_ID]\AppData\Roaming\SecondLife\logs\
If this change gives you have way less errors, you have a work around. Otherwise, you have information to give to your ISP.
About this work around Monty says:
In no way is this intended to dismiss the problems people are seeing. They are real and work is progressing behind the firewall on getting the experience up to expectations. I’m just offering an expedient treat-the-symptom approach. Something to alleviate some pain now and get sufferers closer to where they want to be. It may also give some insight into where we might go with service monitoring or adaptive behavior in the client.
The CDN failures are geographically and time-of-day sensitive. As one of the people said, …lots of textures and avatars are now failing to load. An hour ago all was working fine.
Not all of us are seeing these problems. But, in SoCal there are days when regions load really slow. It very much looks to me like cold CDN caches. But, my home is repeatedly slow to load, which I just don’t understand, unless the CDN in my area is clearing cache every 20 or 30 minutes.
I think it is going to take some time for the Lab to figure this out. From their side it is impossible to see. They are dependent on users to find and report the problems. Knowing what to look for in the logs, gives us some idea what to report and a way to decide if our problem is CDN related.