TPing from Thera to Mohrr is one example.. On windlight I get it every time i try to tp today, while yesterday (before the 2000 region restarts) it was tping ok.

On the RC i think i did manage to TP successfully from mohrr to thera so its not every time there

After i try to teleport wither using map or lm, the bar moves slowly at first, and after a bit i get the log out message:
You have been logged out of Seconde Life:
You have been disconnected from the region you werre in.
Click continue blablabla (the casual [continue] and [quit] buttons)

Happened yesterday 4 times in a row for me with different TP targets.

Repro: TP from "Isle of Ecstasy" to "ETD Isle (212, 216, 26)" via Landmark
Isle is up and running (11 ppl on it (reported by "Map"))
Date/Time: 17.11.2007, 3:26

After logging back in my AV is stuck (unable to move).
A log out and new login results in a "System is logging you out right now". Which means a real working login after such a failed TP takes me often 2-5 minutes.

For me this seems to be linked with 'missing groups' where I have no groups in my group editor, presumably because some lame server somewhere can't be bothered to download them .. which I notice fairly quickly because I don't have rights to any of my stuff and can't manage my land. Anyway .. I''ve started watching this now .. I haven't yet seen a case where I get this sort of teleport failure without groups also being borked. It also seems predictive .. if my groups are borked I know the tp will crash me. Anyone else noticing that link?

i get the message of being logged out only when my groups list hasn't loaded.
that resolved the randomicity confusion from before.

When groups list is complete, TP's happen normaly

I thought it might be more prone to occur after being in-world for a long time (e.g. due to memory leaks accumulating) but it just this morning occurred again (11/19/07 Monday) after being in-world for only an hour or less.

PS.This problem might not be VWR problem but something else?

I've had this problem too, but not yet have a repro.

Have been home bound for over a week now, have given up trying to tp

Am running a G5 Mac, running OSX 10.4.11, can anyone help

This morning's incident occurred with my Group List fully populated and intact – I happened to have looked at that shortly before TP'ing to my doom.

.. I first noticed it when the server patch to add teleport debugging was added .. October sometime? But since then it has gone from an occasional nuisance (1 time in 10) to a major headache (whole days without a single successful tp). It seems load related ... much less likely to happen when SL is quiet (looking forward to TG weekend), but one has to mistrust that sort of anecdotal evidence.

.. my hardware, router, and router config have been stable for 9+ months now. Since I am running a microsoft OS I can hardly use the word stable .. but you get the idea.

i) I can agree that the tp failure/logout is not invariantly associated with unpopulated group list. But in my case at least, the correlation is 98%+ so I can't rid myself of the notion that they are connected.

ii) It also afflicts intra-region teleports via the map. So a region -change is also not necessary to produce this crash mode .. although I don't know how intra-region tps are coded .. possibly they use exactly the same mechanism in which case this might not be a very interesting observation.

If I stay in one place for a long time and then teleport, the teleport fails.
If I log back on and teleport right away and TP regularly from one place to another, the teleports work.

Symptom of failure:

• the viewer image goes monochrome / grayscale
• a message box appears saying:

"You have been logged out of Second Life:

You have been disconnected from the region you were in.

Click Continue to look at existing IM and Chat.
You will not be able to perform any other operations.
Click Quit to exit Second Life immediately."

with buttons Continue and Quit

It's unfortunate that this does not trigger a crash report. So, for the record this is a 1 year old iMac with Core 2 Duo, nVidia 7600, OS X 10.4.10 and running SL1.18.4(3).

You are at 271702.7, 259462.3, 28.3 in Avaron located at sim4899.agni.lindenlab.com (64.129.47.153:13003)
Second Life Server 1.18.5.73200

CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+
Memory: 3033 MB
OS Version: Linux 2.6.22.9-61.fc6 #1 SMP Thu Sep 27 18:48:03 EDT 2007 i686
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 7300 GT/PCI/SSE2/3DNOW!
OpenGL Version: 2.1.1 NVIDIA 100.14.19
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 5285/140277 (3.8%)
Viewer Digest: de123326-c0a8-4b7f-daa1-afb79e8c2d45
----------------

2007-11-26 12:53 PST (SL Time) Teleport Warbluster -> Isles of Intrigue2
2007-11-26 14:04 PST (SL Time) Teleport Isles of Intrigue2 -> Avaron

Logging in after failed TPs most commonly returns me to my set Home position, rather than either the TP source or destination.

Symptom of failure:

• the viewer image goes monochrome / grayscale
• a message box appears saying:

"You have been logged out of Second Life:

You have been disconnected from the region you were in.

Click Continue to look at existing IM and Chat.
You will not be able to perform any other operations.
Click Quit to exit Second Life immediately."

with buttons Continue and Quit

Just for the sake of it I'm on a Toshiba laptop with an Intel 945GM, ! GB RAM

So, unfortunately not a lot of rhyme or reason to it, not reproducible on demand, but quite annoying just the same.

Symptom of failure:

• the viewer image goes monochrome / grayscale
• a message box appears saying:

"You have been logged out of Second Life:

You have been disconnected from the region you were in.

Click Continue to look at existing IM and Chat.
You will not be able to perform any other operations.
Click Quit to exit Second Life immediately."

with buttons Continue and Quit

If you notice, this issue occur when you change between regions... not in the same region. If you walk, fly or tp into another region... crash!!!!
This is happen to me since 1.18.4(3)

Sometimes TP works as somebody above said... if you do it very quick... but this success not happen very often and sometimes can not be replicable. My computer is an iMAC power PC.
I have an adsl modem with 2Mbps of bw.... If the TCP or UDP ports are the problem, you need to tell us how can we configure our firewall options...
pls help!

However, I do hope the mindset is not, "it doesn't affect that many people, let's ignore it".

For those who are affected it can be critical in its impact. In my own case it affects me about 90% of the time .. making it essentially impossible to use SL.

This inconsistency is one of the more puzzling features.

90% of Residents seem unaffected.

9% are affected infrequently.

<1% see this behaviour almost all the time.

No one (that I am aware of) sees this bug all the time.

Oh .. and if any Linden browsing here maintains the illusion that the support ticket system works .. I invite them to look at the file.
My ticket has been open for two-and-a-half weeks. I've yet to receive a response from anyone who manages to convince me that they have even read the ticket.
That sort of support actually has negative impact.

I don't think your estimate is accurate, it seems to happen to a lot of people. More likely those people just don't bother to find this entry on the JIRA, or even mention it at all. Flaky teleport's have become something of a standard SL undocumented feature over time. Either leaving you where you started frozen or able to try again, or crashing you out, or sometimes teleporting you and then crashing just for variety.

The recent upsurge in the frequency of this particular flavour of crash happening is a worry, but I honestly think a lot of SL users have become desensitised to bugs. "Yeah, I've had about X crashes already tonight" is a fairly common comment if you complain about your last crash in an area with more than about 5 people present.

Ahh btw I forgot to mention that this bug is still happening, maybe not so frequent like before (maybe also related to the cache that i have to clear now daily), but i still suffer from it :/

I am not really sure, if I alone would easily produce an excess of ten crash reports per day, since weeks, and all the other people who are suffering the same fate would duly and automatically flood the crash reports in at the same rate, if it still would have been downgraded. Or if it might have even been resolved by now.

Well, one might still dream, might one not...

It's so bad for me that I just can't go anywhere... almost any time I try to teleport I simply get logged out and rolled back. I'm pulling my hair out. I will provide two useful bits of information I've learned from this for others suffering from the issue:
1: if you do try to teleport and don't see any status text by the time the bar is about a quarter of the way filled, you can hit cancel and send your friends IMs telling them you're about to be disconnected so they don't wonder why you logged off. But by this time most people just assume you got TP-booted.
2: A better idea is to forget teleports completely and simply log off, set your starting region to wherever you want to go, and log back in. Right now it's the only way some of us can get around.

I'll have a few tests but it's likely I'll be removing my vote if my problems appear to remain random and not sim specific.

Please don't jump to conclusion based on your isolated experiences and please don't jerk other people's bug reportage around.

If you have really hard, non-subjective evidence of region specificity then you need a new strand or a new bug report, but please don't try and invalidate everything we have collected here.

This not region specifi, it happens everywhere, the only thing i noticed (someone else already reported it), is that it happens always if i stay in a region for "some" time (approx more than 20 minutes), then the TP's stops to work... but if i try multiple teleports just after have logged in, they works correctly.

I've limited knownledge about programming, so i may only guess why the time factor is gonna affect the TP, it's something like a buffer (because of a memory leak or any other similar problem) is going to get full after a certain period... so the tp's stops to work.

Some people get logged out every time, no matter where they are. Some others get logged out consistently when leaving specific sims.

All I know is that if you hang out in the Plio region for a few minutes, and then try teleport/map off... you will get logged off most times, though not every time. I do not have a reliable repro, but I run a business there that relies on a large number people coming and going, and have heard this from several people. Its consistent.

And if there is a specific, reproducible issue TPing to a certain region(s), as Fluf Fredricksson mentioned, please file it as a separate issue (and you can link it to this as related). It's important we be able to focus on this issue without diluting it.

I (and several other Lindens) have noticed this on occasion but it doesn't happen frequently to me. But because of the votes and newfound reports (which give us a better idea of how many are affected), I'd agree this is a Critical issue, so I'm moving that back up.

The summary is now vaguer and not as useful as my earlier edit, so I'm going to revert it.

Those of you saying getting logged out happens "every time" you teleport, please be sure to attach a log file so we have further info to go on – info on how to do that is here:

» http://wiki.secondlife.com/wiki/Debug_Help

We'll continue to investigate, thanks for your patience.

More observations:
The incidence of this for me has been dramatically reduced since the last rolling restart on the 28th/29th? of November. It was pretty much a permanent thing with occasional spells of normal operation up until then. Since then I have had only one or two bad days.
For me it is still strongly linked (99%+) with unpopulated groups.
If I attempt to abort the failing teleport early I sometimes get the "Teleport is currently blocked" error THEN get logged out.
For me definitely not location sensitive ..while in this mode all teleports from/to anywhere by any method will fail and log me out.

Log files attached after having been lightly edited to remove personal data.

***Folks .. before you post your log files to a public place .. be aware .. they contain your user name on your workstation. *** (bad Lindens, bad)
***and the name you logged in under .. which may not be the name you logged into JIRA under .. so if you are sensitive about having your alts linked ..... *** (really bad Lindens)

And having said all that: I also noticed a relevant drop in the amount of failures to teleport properly since the latest update outage.
Nevertheless it still happened...

Background:
Until (and including) 1.18.3, everything worked fine. I missed 1.18.4, but with the WL-clients, and all the ones since 1.18.5 (FL and official) I got logged out on TP/sim-crossing.

Changes:
Between 1.18.3 and 1.18.5, library c-ares was introduced for doing DNS lookups.

Problem:

• Network trace revealed that a faulty configured (local) DNS-cache delayed the answer for a DNS request for about 5s (it first asks the wrong
  DNS server for the name, and after a 5s timeout the correct DNS-server, so every DNS-request took just over 5s).
• c-ares default configuration uses a timeout of 5s.

So, what happened was:

• DNS request for the address of the sim I want to TP to is posted via c-ares
• DNS-cache asks wrong server first
• after 5s, c-ares timout hits and c-ares asks again, causing the DNS-cache to drop the old request (from the same IP, for the same name)
  and restart the process, asking again the wrong DNS server.
• after several retries, c-ares tells SL-client: Can't find address of sim
• client logs off.

Solution:

• For me, correcting the faulty DNS-cache configuration solved my problem. DNS requests are now answered within <0.2s, and I can TP with the current 1.18.6 (and
  the 1.18.5 I compained about above) without fail.
• In general: This will happen whenever the answer for a DNS-request is delayed for more than 5s (neatly explaining the "I'm sometimes logged out" problems, too).
  I suggest to configure c-ares with a higher DNS-timeout (at least 15s, via ares_init_options). Will add a patch later (have to switch to the 1.18.6 sources first).

Nevertheless, I just tried it again to make sure: Fixing the DNS setup fixed the problem for me. I can get the old non-TPable condition again by using the old config for my DNS-cacne.

So, to summarize Slow:DNS responses were the reason for the problem for me, but the introduction of c-ares into the viewer at the same time the problem occurred for me seems to be a coincidence.

However, I'm fairly convinced it's some kind of configuration issue, since the code itself hasn't changed significantly in a while.

The client is being logged off because the sim you are teleporting from is telling the client "we are done". However, the sim you are teleporting to has not told the client "Yeah, you are here now".

Basically the existing region information within the client is being removed, but there is no new region information, and as such the client immediately thinks you are logged off, hence seeing the Logged Off screen.

Now the interesting part here is that if this were a configuration issue within sim to sim communication, then teleporting wouldn't work at all. And yet it does. Add to that accounts where this happen, I then hijack them and it all works fine for me, and we arrive at a sim->client configuration issue that may well be related to local conditions at the client. Something is not getting forwarded correctly - potentially the new sim saying the client "hey, I have you". And it's very intermittent.

I'm still looking into this. Just thought I'd update you guys on what I am seeing.

Umm .. can I just reemphasize that 'intermittent' is only the word to use if you are averaging across the totality of Resident experiences. For certain individual Residents it is certainly not intermittent. The ability to tp at all without a crash is the intermittent bit ;-(

Having said which .. and for what little it's worth .. some further observations.

• The incidence has changed since the last grid-wide rolling restart of about ten days ago. It's dropped from perhaps 95% of all tp attempts (bursty - ie that 95% means one hour a day when things work properly not 1 out of 20 attempts) to perhaps 70% of the time when it's broken.

• The (for me) very strong co-incidence with unpopulated group lists has weakened slightly .. dropping from 99%+ to 95%+. I still never see a tp succeed with unpopulated groups .. but I do now see the occasional one fail even with populated groups.

• Watching myself in a failed tp using an alt I am often seen to 'arrive' briefly at my destination before vanishing again as I am logged out. From my perspective I never see my destination. That tends to support Jake's analysis I imagine. The new region 'receives' you but the viewer doesn't get the news.

• Cancelling a 'failing' tp is usually fatal in the sense that you end up being logged out anyway. However you sometimes see strange things in the second or two before you are logged out. The one that intrigues me is a curious 'mixture' of origin and destination. Once or twice this has even extended to the view with things like objects from the origin against the landscape of the destination. The commonest though are things like a scrambled title bar .. name of destination region with description from the source region is quite a common one. Anyway .. the viewer is getting some information from the destination.

Dunno if any of that helps ... but omg I hope something does and soon.

Gil, if you are in world, I'll give you a ping.

More Information:
Internally, Linden Lab is in the process of bringing up a new internal second life grid, and funnily enough any teleport from one location to another fails, with almost exactly the same symptoms. I am hoping that whatever is the issue there is the same one that is being seen in the main second life grid.

So fingers crossed I find that and the solution is applicable.

Pls let us know as soon as your team finds something!

Enable TCP port 12043 through your router.

I was able to repro/resolve this issue consistently by opening/closing this port. This also solves the missing group issue here -> http://jira.secondlife.com/browse/VWR-2633.

I'm fairly sure I have the area where this is happening narrowed down. I fixed our internal problem and it suggested the area where this happens externally.

I also suspect this is potentially a router / firewall issue, but I need some extra data to add evidence to my hypothesis.

With that in mind, could I ask for some more data when you guys run into this? Namely -

a) Can you region cross when the Teleport goes RART**? IE can you walk / fly from one region to another?

b) Does voice still work when you are in this state?

c) Is this a state that persists across multiple logging in?

d) does it happen instantly on logging in, or is this something that starts occurring over time?

e) What router do you use?

f) What firewall do you use?

g) Does it go away if you power cycle your router

and finally

g) What deoderant do you use? Cos I get a rash from mine...

If this is what I think it is I'm gonna have a hard time proving it and an even harder time figuring out what to do about....

• • RART = Rapidly Assuming Room Temperature. Emergency room code for Dead.

b) Does voice still work when you are in this state? NO IDEA. THERE'S VOICE NOW?

c) Is this a state that persists across multiple logging in? YES

d) does it happen instantly on logging in, or is this something that starts occurring over time? EITHER. BUT IT DOESN'T "START OCCURRING" .. IT'S ON/OFF WITH A TIMESCALE OF HOURS.

e) What router do you use? USR SURECONNECT

f) What firewall do you use? The USR SURECONNECT INTERNAL ONE. WINDOWS SO-CALLED FIREWALL COMPLETELY DISABLED

g) Does it go away if you power cycle your router HAVEN'T TRIED. THAT WOULD TAKE A LONG TIME TO ESTABLISH WITH ANY CONFIDENCE.

and finally

g) What deoderant do you use? Cos I get a rash from mine...

I am on a Zoom ADSL X6 modem router, connecting via wireless to the router. I have Vista Firewall on but no other firewall. I think there is also a hardware one in the router. I cannot answer most of your other questions because the tp failure caught me unawares so I was not testing, but I tend with that alt to be tping everywhere (mostly on private land so region walking is not really on most of the time). Never got voice to work (I think my headphone set is broken rather than SL).

If you are worried about deodorant, ask for a transfer to the Brighton office, its never warm enough in England to need deodorant.

a)NO
b)i dont use voice
c)YES
d)both
e)2WIRE
f)above....
g)no

If i can give you more data, pls dont hesitate in ask for it.... This situation is unsustainable

And can you share your theory with us? I'm having trouble buying the router theory because of way the fault comes and goes, it has to - at least - be much more elaborate than just router configuration. And that wouldn't answer the question of why it just suddenly started occurring .. at the very least something at your end must have happened to expose it.

I could buy a routing connection .. which would explain why the problem seems to occur with all accounts from a specific machine but not with those accounts used on a different machine. The route used between here and there could well change .. over a timescale of hours .,, and produce the pattern seen.

I'd be fascinated to know, for instance, whether a specific route to LL's datacentre makes me more or less likely to be connected to a particular server/rack/interconnect ...

Or a variation of Homer's theory .. a problem only exposed by high latency .. which could also vary on those long timescales ...

b) Does voice still work when you are in this state?
R: Not sure.

c) Is this a state that persists across multiple logging in?
R: Nope, immediatly after login the TP's works correctly. The problem appear after a certain amount of time.

d) does it happen instantly on logging in, or is this something that starts occurring over time?
R: as c) ...it happens only after a certain amount of time sitting in a sim.

e) What router do you use?
R: netgear... but it's the same router as i had before the problems stard (about a month ago?)

f) What firewall do you use?
R: router firewall.. but as e) the configuration didn't changed.

g) Does it go away if you power cycle your router
R: it's not necessary, since at the next login TP's works again.

Anyway the effect (exposed by jake) seems right: the avatar reaches the destination, but the client doesn't receive the information so it assumes it is a failing TP and try to recover the originating simulator, but it has been "cleared" (since the TP, in fact, worked) and then you're forced to logoff.

Im not quiet sure what i have now... but let me tell you about it....
Yesterday i was trying to teleport myself (always try to "check" the issue....) so... when i saw the progress bar had that delay i sent SL app to background and i pull up the SAFARI app to the foreground and stared to navigate in the internet.... and after a couple of seconds i heard the "bell" yes that bell that all of you heard when the teleporting action is completed.....
My surprise was i did a sucesfull teleporting!!!! yeah after a couple of weeks!!!!
I realized that the only diference was that i was surfing the internet at the same time when i was teleporting myself.... so I replicate the scene and i teleport 4 times before SL takes me out of the game.... with the same error window....
That was yesterday.... today i did just 2 succesful teleports..... same scenario...

SL in the background
Internet browser in the foreground.... changing pages....

Peharps did means nothing for an unexpert user as myself.... i hope JAKE or else more expert in these stuff can figure out was happened....

Guys.... pls think hard... seems you are close enough to make a workaround or some....

Happy New Year!!!!

So here's what I think this is.

Normal communication between the Sim and the Client is via a UDP connection that is hand managed by our code.

However, recently we've built a better way of dealing with some of these communications - since they don't need to be UDP (the difference between UDP and TCP/IP - which I'm sure you've all heard of - is that TCP/IP guarantees packets delivered in order, and actually delivered. UDP does not. It's like sending a letter and just throwing it out into the world and hoping it gets there, and having registered mail. So why don't we use TCP/Ip purely? Because if a packet gets lost or is delivered out of order then TCP/IP can take on the order of seconds to sort it out and get the right packets where they are supposed to go. Something you can't afford to rely on for things like positional updates and so on).

Some communications can afford to be TCP/IP since it isn't so critical that we update instantly - stuff like inventory handling, IM's and so on.

Anyway, the new structure we have in place is also an indirection system. What that means is that instead of the client assuming that it's always talking with a Sim, on log on the sim tells the client "this is the web address you talk to to handle IM's. This is the web address you talk to to handle Inventory. This is the web address you talk to to handle Asset downloading" etc. The idea being that eventually we can move the actual processing of inventory, or IM's or whatever off the sim itself, and onto a dedicated system instead. This frees up processing time on the sim to handle physics and scripts, and allows us to scale the way we handle IM's or some database intensive task.

So inside of the teleport (and region crossing) there is One Message that goes via this new communications method (called Capabilities). All the rest are UDP, however one goes via TCP/IP and is sent via a web connection rather than anything else. If that one message is dropped then the teleport (or region crossing) fails, and you get logged out. But you only get logged on on that one specific message being dropped. If any other message is dropped you get the teleport failed message.

So, ergo, this means that one message is, in these cases, not getting through.

Now it should be further pointed out that this new communications method (capabilities) operates via HTTPS not just the standard HTTP protocol. HTTPS is 'secure', and we need that because we'll probably be passing some sensitive data across. However this does require the correct certificates in place (you've all seen websites that require you to accept a certificate right? That's HTTPS in action) and it's all a lot more complicated that traditional HTTP web communication.

What does this mean? I have a suspicion that in some cases some routers get messed up with HTTPS communication, over time. Some internal buffer gets overloaded, or some certificate gets messed up or whatever, with the net result of this one message not being communicated from the Sim to the Client and teleports suddenly failing.

Now in the short term the answer is obvious - switch the teleport / region cross message across back to UDP and all should be good again. But since we've built this new communications system, and a lot of our intended new sim configuration design for 2008 and beyond is dependent on this working, we need to understand why we are seeing this hiccup, and what we can do about it.

Thats why I am asking about routers and rebooting to see if the problem goes away, because if it does then it's obviously router related. The fact that only a very small subset of you are hitting this makes me suspect a local configuration problem rather than our code per-se because if it was our code, everyone would be seeing this problem (as they did on our internal grid I was helping to bring up).

I hope this gives you an idea of what I am looking at and why.

Jake

This is now very plausible .. but don't lose sight of other possibilities. Once you pin the blame on HTTPS glitches (for which you adduce strong circumstantial evidence) you also have to think about the local machine. I'd be just as inclined to suspect a bug in the TCP stack in the local machine or even idiocy by some other HTTPS client doing something horrible (I, for one, almost always have a browser running at the same time as SL). Against that .. rebooting the local machine doesn't seem to help. So still puzzling however you look at it.

I wouldn't be ready to rule out timeouts as a culprit either. We do sometimes see horrific levels of both latency and packet loss on SL. Remember that TCP doesn't guarantee delivery - it just guarantees to keep trying. Presumably something somewhere in the server will eventually decide that this is just not happening.

But .. you still need code changes, Jake. Your code needs to attempt to recover from this sort of hiccup .. not just give up and boot the viewer. At the most minimal end of barely acceptable .. take the viewer back to the login* page with the SLURL of the failed TP target already entered.

[* Which is also a puzzle. Presumably the same sort of HTTPS transaction occurs during a login. Yet they work. I speculate because the login logic doesn't give up straightaway if the HTTPS transaction fails .. it goes round again and has another go.]

If the problem is related to the caps event queue during the teleport, then perhaps some sort of error recovery needs to be implemented as Gil suggest.

thank you for the information you provided. I am anyway not sure that it is really related to a router problem.

When the idea with the router related problem came up I tried several things to have a workaround:
(the diconnect effect after/during TP happens to me occasionally)

a) I have this problem occassionally with 2 different local routers
b) I have this problem also without a local router (direct DSL connection)
c) Usually when it happens I have had several (1-4) successful TPs and am inworld for at usually at least 30 minutes before it happens the first time.
d) When it happens and I get disconnected and log back in, I am stalled until I relog again: I can not TP anymore and can not move or fly anymore, but I can do everything else (transactions, IM, ...).
After your info I reset my router before I logged back in: No difference ... stalled again until the next relog.

> The fact that only a very small subset of you are hitting this [...]
e) A lot more people told me they have the same problem - they just don't believe adding their comment/note to jira will help fixing it. They just live with it, sigh and wait for it to be fixed - they are simply frustrated.

But back to "on topic" about the only thing I might have changed concerning this is upgrading my SSL related libraries in Debian Linux. I didn't think SL used those though, so remain somewhat unconvinced. But for the record am now on:
libcurl3 7.17.1-1
libssl 0.9.8g-3
openssl 0.9.8g-3
And teleports have been good for a while. [Shrugs]
I'm also using a heavily patched version of 1.18.5.3 which may have more to do with it.

Edit: Just jumped in world. Asked first online friend I could IM if they get logged out on teleports. Answer? "About once every three times"....

I've taken some time to experiment. Here's a little info I have which I can confirm:

1: Though I get seemingly random disconnects as well, if I remain in one sim for too long, particularly overnight, I am guaranteed to have a disconnect when I try to move to another sim in the morning. This is 100% reproducible so far. It's possible that this particular reproducible case of TP disconnect is caused by being logged in for too long, or being in one sim for too long... I haven't tried to figure out which of the two causes this.

2: I live on an island, and WALKING to the adjoining island will fail as well. I have no idea if this happens on the mainland, but remaining on my home island overnight and trying to walk to the adjoining one in the morning is a 100% reproducible failure (a hang on sim crossing) just like an attempt to teleport under the same conditions will cause me to disconnect. Could it be the same bug? It seems likely, and there have always been people in the destination sim who aren't experiencing any lag or other issues there.

3: This doesn't mean it ONLY happens when I've been in one sim for a long time. I have, in one circumstance, logged in after being TP disconnected only to find I'd been rolled back to a different sim. I immediately tried to teleport and got disconnected. This happened three times in a row before I decided to simply log in at the sim I was attempting to teleport to. However, this is now rare.

4: Like others, I also often find I'm "stuck" upon login after a TP disconnect. My avatar is stuck in a ruthy crouch pose, I can not move, and can not teleport or take other actions. Another relog generally fixes this. However, this also doesn't happen 100% of the time.

5: I've sometimes played with logging in two avatars at once on the same system. (using the -multiple parameter.) When one avatar is TP disconnected, the other is entirely unaffected, and no other downloads or connections are interrupted.

6: I've removed my router entirely and dialed in directly with my DSL, and the results are the same. This is absolutely not the only cause of these disconnects. Whether it makes the problem worse or not, I can't say, but I can still reproduce disconnects without the router. However if it helps the process at all, my router is simply a linux box.

7: The failure in TP disconnects seems to happen in a consistent way. I know when I'm about to be TP disconnected because "Requesting teleport" briefly flashes and then disappears. The progress bar continues to move, but "contacting new region" never appears. Once the progress bar reaches the halfway point, I then get disconnected.

8: If I want, I can press the "cancel" button at any time during a failed teleport. I will then find myself at seemingly no location in the (origin) sim... the location vector does not appear at all at the top of the screen, but the sim name does. I am **NOT** truly disconnected at the time, though... I can send and receive IMs. Some time after this, at the same time I assume that the TP progress bar would reach the halfway point with no REAL teleport progress, I am then disconnected, just like I would be if I hadn't hit the "cancel" button. (EDIT: Just to clarify, the sim I'm stuck in is my origin sim, not the destination. As far as I can tell, SL never contacts the destination sim.)

I realize that it's difficult to track the real source of this problem, but I assure you it's not simply something that goes away when a router is reset or removed. Hopefully this information will help.

What makes me wonder is why a sim restart gets rid off this problem and not a router reset. Maybe it is burried again in some code lines for the server.
I had 6 tps of death from my sim to others, after a restart it was working again, so i would suspect also a different combination of the upper mentioned ideas.
And believe me, if a router messes up https communications, then throw it away. Otherwise you wouldn't be able to do other important secured web things.

b) Does voice still work when you are in this state?
R: Yes and the voice i hear is from the starting location (not the destination).

I've seen this behavior with the following clients:

• FirstLook 1.18.6 (76453) under Linux (nvidia 7600 GT, 2Gb Ram, Suse 10.3)
• Standard client 1.18.5.3 under Windows (Intel 945M, 1Gb Ram, Windows XP)

The Windows client crashes as often as the Linux client. (Which is only at TP-ing, other functions are very stable).

Dump of the log at the time of crashing (Linux-client):
-----------------------
2008-01-02T16:29:46Z INFO: removeRegion: Removing region 256768:259840
2008-01-02T16:29:46Z INFO: LLEventPollResponder::stop <9> https://sim4171.agni.lindenlab.com:12043/cap/23236922-505d-f6f4-450b-7f4b8cc1903a
2008-01-02T16:29:46Z INFO: LLMessageSystem::disableCircuit for 63.210.157.75:12035
2008-01-02T16:29:46Z WARNING: disableCircuit: Couldn't find circuit code for 63.210.157.75:12035
2008-01-02T16:29:46Z INFO: removeRegion: Removing region 257280:259840
2008-01-02T16:29:46Z INFO: LLEventPollResponder::stop <10> https://sim47.agni.lindenlab.com:12043/cap/b8460c8d-e679-67fa-5088-0092e34d6bef
2008-01-02T16:29:46Z INFO: LLMessageSystem::disableCircuit for 64.154.220.14:12035
2008-01-02T16:29:46Z WARNING: disableCircuit: Couldn't find circuit code for 64.154.220.14:12035
2008-01-02T16:29:46Z INFO: removeRegion: Removing region 256768:260096
2008-01-02T16:29:46Z INFO: LLMessageSystem::disableCircuit for 8.2.32.201:12035
2008-01-02T16:29:46Z WARNING: disableCircuit: Couldn't find circuit code for 8.2.32.201:12035
2008-01-02T16:29:47Z WARNING: removeRegion: RegionDump: Agapema 63.210.156.193:13005 { 257024, 259840, 0 }
2008-01-02T16:29:47Z WARNING: removeRegion: RegionDump: Neumoegen 63.210.156.135:13005 { 257280, 260096, 0 }
2008-01-02T16:29:47Z WARNING: removeRegion: RegionDump: Calleta 63.210.157.197:13006 { 257280, 259584, 0 }
2008-01-02T16:29:47Z WARNING: removeRegion: Agent position global { 257154, 260004, 502.846 } agent { 129.87, 164.313, 502.846 }
2008-01-02T16:29:47Z WARNING: removeRegion: Regions visited 2
2008-01-02T16:29:47Z WARNING: removeRegion: gFrameTimeSeconds 29826.7
2008-01-02T16:29:47Z WARNING: removeRegion: Disabling region Agapema that agent is in!
2008-01-02T16:29:47Z WARNING: createXml: Alert: [YouHaveBeenLoggedOut]
----------------------

Regards,
Marcoh Larsen

I'm pretty convinced that this is the message dropping, the question really is how is this happening.

The router issue - the reason I ask is that I was using a guy who commented in this thread as a control - he was having it happen every time he logged on, however when I hijacked his account it never happened for me. I give him his account back again and viola, it starts happening again - therefore the issue had to be down the chain from the Sim itself, and more likely a local issue. He then went out a purchased a new router and suddenly all his issues just went away. So you can imagine why I ask the router questions.

Now it appears obvious that his was a rolling red herring, although it is still some pretty strong evidence.

ISP issues is an interesting idea. Not entirely sure how I test that though.

This is the most interesting comment though
"What makes me wonder is why a sim restart gets rid off this problem and not a router reset."

Now that does make it interesting, since it sounds like the HTTPS message is being dropped from the sim to the HTTPS forwarding service which sends it on to the client.

a) Sometimes. I have successfully hit Teleport Home and pulled myself out of a dead TP after hitting cancel. But not always. It may depend on how quickly I reacted.
b) I don't recall. But IMs still work.
c) Not for me. I'm always safe in the destination sim after login.
d) there was one occasion where attempting to TP to the same sim caused the TP of death 3 times in a row, directly after logging in. But that was a frustrating exception, not the rule.
e) cheapie US Robotics Cable Modem Router. Model # 8004
f) I have no firewall, the Router is set to DMZ (yes I'm crazy like that)
g) It's not consistent enough for me to determine that.
h) sorry can't help you with your rash.

CPU: AMD (Unknown model) (3013 MHz)
Memory: 2046 MB
OS Version: Microsoft Windows Vista (Build 6000)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8500 GT/PCI/SSE2/3DNOW!
OpenGL Version: 2.1.1
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 931/244394 (0.4%)
Viewer Digest: ffac34f4-0452-2fcc-16b7-c2868f0923ef

http://forums.secondlife.com/showthread.php?threadid=232812

And one tech note to add that may or may not be relevant. As I've said, I've not had these crashes roughly since I started running the "CoolViewer" http://sldev.free.fr/ for a list of patches applied. But I also tried turning RIP1+2 on in the router around the same time. I've no idea how much of an impact that's having except in theory I'm getting more direct routes to the servers. TBH though, I think it's either more to do with running the patched client software, or I'm just lucky all of a sudden!

What I've noticed is that, during login, when the progress indicator pauses for a minute or so (sometimes up to 3 minutes) on 'Initializing World...', I am guaranteed that I won't be able to teleport and that my group list will be empty.

Now, I've also had the failed TP when the group list is populated, so I reckon it's a co-symptom, for want of a better phrase, rather than directly related.

MacBook Pro (series 1)
Any client.

I put the Mac into my DMZ when using SL.

2008-01-09T06:59:51Z info src=24.64.230.3 dst=86.155.143.105 ipprot=17 sport=16029 dport=1027 Unknown inbound session stopped
2008-01-09T06:59:51Z low src=24.64.230.3 dst=86.155.143.105 ipprot=17 sport=16029 dport=1028 UDP Port Scan Detected
2008-01-09T06:59:51Z info src=24.64.230.3 dst=86.155.143.105 ipprot=17 sport=16029 dport=1028 Unknown inbound session stopped
2008-01-09T07:00:00Z info src=64.129.43.2 dst=192.168.1.7 ipprot=17 (layer 4 info unknown) Unknown inbound session stopped
2008-01-09T07:00:00Z info src=64.129.40.204 dst=192.168.1.7 ipprot=17 (layer 4 info unknown) Unknown inbound session stopped
2008-01-09T07:00:13Z info src=70.42.62.21 dst=86.155.143.105 ipprot=17 sport=5062 dport=22891 Unknown inbound session stopped
2008-01-09T07:02:56Z info src=24.64.137.222 dst=86.155.143.105 ipprot=17 sport=9175 dport=1026 Unknown inbound session stopped
2008-01-09T07:02:56Z info src=24.64.137.222 dst=86.155.143.105 ipprot=17 sport=9175 dport=1027 Unknown inbound session stopped
2008-01-09T07:02:56Z low src=24.64.137.222 dst=86.155.143.105 ipprot=17 sport=9175 dport=1028 UDP Port Scan Detected
2008-01-09T07:02:56Z info src=24.64.137.222 dst=86.155.143.105 ipprot=17 sport=9175 dport=1028 Unknown inbound session stopped
2008-01-09T07:05:26Z info src=24.64.185.181 dst=86.155.143.105 ipprot=17 sport=16428 dport=1026 Unknown inbound session stopped
2008-01-09T07:05:26Z low src=24.64.185.181 dst=86.155.143.105 ipprot=17 sport=16428 dport=1027 UDP Port Scan Detected
2008-01-09T07:05:26Z info src=24.64.185.181 dst=86.155.143.105 ipprot=17 sport=16428 dport=1027 Unknown inbound session stopped
2008-01-09T07:05:26Z info src=24.64.185.181 dst=86.155.143.105 ipprot=17 sport=16428 dport=1028 Unknown inbound session stopped

Time gaps are re-logging after being kicked out, and there is a significant time waiting to log on when bar reached "initialising" after a tp has failed. The first log on of the day doesnt have this wait.

I'm no techie but hope this helps.

Meri

Incidence of this wretched problem had been declining steadily (for me) since the start of Dec, from about 95% of ALL teleports at Dec1 down to fewer than 10% by the New Year.

Woohoo, I thought. I can sort of live with that.

Since yesterday's asset server upgrade .. 90%+ of all teleport attempts cause an involuntary log-out, again. Strong correlation with groups not loading is still there (for me .. I know some people don't see that).

I've got to stress (if needed), that NOTHING has changed at my end. Same hardware, same OS, same router, same firewall configuration as this time last year. For me this problem comes and goes as the servers are messed with. Come on guys, think! What did you change yesterday that might be messing with teleports?

Simple lack of availability of asset server service? (I've given up trying to script for today as well .. scripts are neither loading nor saving reliably enough or quickly enough).

GD

Gil - Just a thought, but maybe the windows DNS cache couldn't cope with the change of server layout after the downtime? I could be way wrong here, but again, perhaps worth a try ... http://vlaurie.com/computers2/Articles/dnscache.htm for details.

I'd be interested to know if the tip at the end of that article on not storing bad DNS lookups helps anyone out.

Have a new revelation to this problem
If i log in at home, cannot tp at all...100% failure...but if i type a region in the login and start there I am able to get one tp but only one, next tp attempt freezes my screen.

Jakes explaination of the issue seems to ring true, it would explain the firewall problems I am having, and sometimes the random pattern of failures.
SL has changed something since the 18.4.3 upgrade which is when all my probs started. Which seems a long time ago now.

Heh. Sorry watchers to edit. But just to make that crystal clear.
Viewer software A and Router A .. ran fine for several weeks.
Now... With no changes to router, viewer etc...
Viewer software A and Router A .. teleport logging me out again.
During the whole period, router reset every 3 to 5 days (sometimes less).

However, I notice that it also happens on Sim crossing if the sim I'm traveling too has a lot of objects/avatars and is still rezzing on my screen. If I stop before I enter a sim and let things rez a bit and go slow before I cross then crossing is ok. If I am going fast, my av often ends up flying forever (soon outside of any sim) and then the error message occurs.

Is rezzing the environment taking a higher priority than the sim crossover or is it just that my connection has lost a packet related to the crossover?

This problem only seems to happen when my camera is fixed on my avatar rather than a stationary position somewhere. Also, sitting on a prim to make the sim crossing, prevents this problem almost entirely.

My experience of the problem is slightly different from the bug description in that the teleport screen doesn't hang. The bar slowly creeps along, but no status update messages appear at all. No "Requesting teleport...". Nothing. The bar just creeps along to about 1/3 to 1/2 the way and then DING. Disconnect. (And also viewer hang for me with Windlight. See VWR-4087). An imminent disconnect is usually apparent with in 1-4 seconds because of not seeing any status messages indicating the new region is being contacted.

I have also noticed that in general it happens mostly after I've been connected for a few hours. Up to 9 hours at a go before I teleport sometimes, and then I can usually expect the disconnect to occur. It does happen sooner in some cases, too though. Sometimes, even after just logging back in, it has been almost a 50/50 whether the teleports would work.

To Jake's questions:

a) Not sure I understand this question, especially with the RART acronym. If I understand correctly, if the teleport fails, the viewer is disconnected completely and it's not possible to resume without relogging. If you however mean that can you simply cross regions before trying to teleport, I'm yet to confirm this one.

b) No. But the viewer crashes for me. See VWR-4087

c) It generally happens each time I log in – But I stay logged in most of the time. Eventually it will happen, sooner or later.

d) Mostly over time, but I don't teleport very often when I stay logged in.

e) Linksys WRT54GL running a Linux firmware from the OpenWRT project. Usual uptime is months on end.

f) The default firewall rules policy/NAT config in the router. Some minor port forwarding for other applications. Nothing in SL's usage range.

g) Will verify this next time it happens!

h) You probably want to try something else

No one knows what happened with Jake?

He used to answer or update this "blog" every 4 or 5 days... now I didnt hear any about him long time ago...

For all... im having sucesfull teleporting every time i access (in other window) internet at the same time with teleport process... 4 or 6 times... then suddenly the next time just crash in the way ALL of you know.

If someone much more "expert" wants to try.... feedback is very welcome.... not for me... but Jake and Co.

This situation is taking a lot of time....

Land from (my land): Beerbaum
TP to: Avalon Isle (where i got banned.. don't ask me why... hihhiihih)

...i receive the message "you got baned... ablabal" so the TP failed.

2nd TP to: Parioli

...and da da! Stuck on teleport... "always".

3 in 10 teleports result in "You have been disconnected from the simluator you were in..." and a blank terrain and no other avies or scenery. Up until the failed teleport, I would be doing things normally, IMing, rezzing objects etc. I would be logged into the support portal and jira and the sl wiki (all https). Granted- https communications with secondlife.com is excruciatingly slow compared to other servers in the Internet. (hint hint)

The funny thing Jake, the simulator I was IN still thinks I am logged in. Residents around me testify I never left, except very briefly (like seconds) while my first attempt to log back in triggers the simulator to log me out, and I log back in. Not the couple of minutes it takes for me to shutdown SL and restart. (as a side note, logins to Second Life have slowed down greatly with the last rolling restart – I spend a great deal of time on the PRECACHING screen that I never really have previously).

Often times Second Life viewer doesn't know it's been logged off or disconnected from Second Life and remains normally active (until I try to move or teleport). I check my SLEEK and they are logged off - they know. (this condition is easy to reproduce). But in this teleport case, Second Life doesn't know it's still logged in... Being intermittent, I can't explain when or why it happens.

Sometimes it happens at the very first teleport after I log on

Sometimes it happens after I've been logged on an entire day.

Sometimes it happens in between. All I can say is that a one-a-day occurrence has become a several times an evening occurence in the past two weeks. My on-line habits have not changed hardly, in the past 6 months.

Kind of blows the router theory out of the window?

Also another odd thing, if I wait until I get the "you have been logged out message" and log back in, my av is in a bit a "squat" position and I can't move. I can turn but not move otherwise. The only fix in this case is to relog AGAIN. Also I have notice that if I cancel the teleport before this then close the viewer, at least I only have to relog once, rather than twice.

-DB

1) Log into SL.
2( (Disable Away when idle). Let avatar stand idle for more than a couple of hours.
3) Attempt to teleport to...Cyclops
4) Receive disconnected message
5) Open a second copy of SL (before shutting down the first, but after receiving message) -
6) Log in as an alt and teleport correctly

If it were routing tables, then the 2nd instance of the browser wouldn't have experienced proper teleportation either? Something like that would require an OS restart / not an SL restart...

=====================

Not so reliably
1) log into SL
2) teleport immediately
3) fail immediately

No rhyme or reason to the immediate failures. Also, when it happens, some of the mentor and help channels have announced that a rash of it is going on - although there are many residents who are still able to transport freely at that precise moment.

Has seemed to me for a long time now that we have one failure mode but several triggers .. so possibly several bugs. These include (at least)

i) The time-in-sim related version documented by lum & Fluf and others

ii) The server incompetency version that afflicts me (correlated with other failures such as no groups loaded etc)

iii) Particular region related versions?

iv) heavily loaded SL versions?

.....

So in a sense the real bug is that the viewer doesn't handle a failure to tp correctly .. the bug is in the error handler .. or possibly it's the sim-to-sim protocol for handing off an agent that needs a really critical eye cast over it .. it seems to be broken almost by definition since it has an 'indeterminate' state where the two ends can't agree on what happened.

1) Don't log in to "Home" or "Last Place", type a region name to log in, this I find will give me at least 3 successful tp's before logging me out. (Oh yeh forgot to say, dont stay in region too long or it won't work)

2) To get more successful tp's I find that clicking constantly on my emails "send and receive button" while tp bar is moving, helps too! ( Mad Hey?)

3) Havn't tried standing on my head whilst drinking coffee yet, but if anyone has, please let me know if it works

What a sad life we lead!

Pick two sims that are not close together.
One will be your starting sim and the other will be your destination.
Log in and go to your starting sim.
Add a packet filter blocking all ip traffic between you and the destination sim.
Teleport to the destination sim.

Expected result: the teleport times out and you are left where you were in the starting sim.

Actual result: the teleport times out and you are logged out of secondlife.

Firstly, anecdotal evidence in SL tells me this is happening to a lot of people. They just fail a TP, sigh and relog after they have been at a club or gig for a while and say "ah well, it's SL, what do you expect?" (or words to that effect).

Second, there may be something of a presence clue. Now I've witnessed a few people fail to teleport away from me, if they get as far as vanishing from my view, reasonably often I don't get a "x has logged out" message, and IM lets me chat to them is if they are on-line. It's only when they re-log I briefly get the IM "will be saved" message usually for one line before SL then tells me they are on-line again almost immediately. Don't know if that helps you track down the point at which they get dumped out, but thought it might.

Using the AT&T routers causes above described TP failures every single time.

Using the Valley Internet router allows me to play Second Life like in the old days.... sigh reminiscing....

Anyway, I have been playing SL from home using the same AT&T DSL router since Oct 2006. So there is something that has changed in the latest releases that seems to be incompatible with the AT&T DSL router/firewall setup.

Again, this is something I have noticed in my case, and may not be true for everyone. I have checked this on several different days over the past couple months, and the same results appear each and every time.

I can only play SL now when I am at my friend's house who uses Valley Internet.

Besides, it has uses in a covert sort of way. If I know someone has been on-line for ages without a break, I can now pretty much assume that they have only been in the one sim the whole time.

Suffering heavily from it, over the last couple of days I noticed a 100% success rate when teleporting, irrespectively of time spent in a region ( from nearly none to up to several hours).
IF I teleported from the map after it had loaded completely...

Inconclusive test with an alt to teleport as simultaneously as humanely possible from the same PC via the same router show that it can happen, but only to a very small percentage, that both teleports fail so spectacularly. Normally at least one of my mes gets through...

I've come to hate that bug from the depth of my little heart...

a) assert server is under load (many users online (> 50.000))
b) when I stay more than 1 hour in a place

The TP attempt takes a long time and when I click 'cancel' during the process I find myself in nowhere with no prims around me and also the "continue/quit" dialog.

Fatal effect which was also reported here several times: After logging back in I am unable to walk, fly and teleport.
I have to log out and log back in a second time for everything to work 'normal' again.

About 15% of my teleport attempts are affected by it and it happens only with viewers after 1.18.4 (windows version)
RC 1.19 is also affected. No changes in my network config or router for about 3/4 year

athlon62 X2 4400+, 2 GB, geforce 6800 GT
windows XP pro

I'm a builder, the last time I used TP while I was building, I lost all last modifications I did before TP...
Regularly, when I relog, I'm freezed and can't do anything else than chating ... (telling friends I re-relog, cause I can't move)

This problem has been reported FOUR MONTHS ago, so PLEASE ask your developpers to check this out SOON for real, this time....

Enjoy SL, be patient...

Click Continue to look at existing IM and chat.
You will not be able to perform any other operations.
Click Quit to exit Second Life immediately.
2008-02-11T21:41:44Z INFO: LLMessageSystem::disableCircuit for 64.129.41.86:13006
2008-02-11T21:41:44Z WARNING: disableCircuit: Couldn't find circuit code for 64.129.41.86:13006

I have to say that I have mixed emotions now... I was having problems with TPing my avatar in my iMac PowerPC since a couple of months ago... i posted several comments trying to give more information regarding this issue. Well, i have to say now, that i got a new laptop not a MAC but a PC with nVidia Quadro Video Card, etc. and i downloaded the 1.18.5(3) version of SL and start to doing some tests.... well as far as today (one week later) all my TP's were been sucesfull. An interesting point here... my router is the same... nothing change, no config., no new firmware, not even a reboot... I just changed the Computer....
I will keep doing test and trying to post feedback to this forum in order to find out where is the problem.... because I rather play with the iMAC than the PC... I saw some comments regarding that in some cases people change the computer and the issue is still there... well i dont know where's the catch... but this wasnt my case...

...unbelivable...

Jake:If you need more info about the config of my laptop, let me know

I've moved positions with Linden Lab and this is the last thing on my list of 'old' tasks I have to clear, so I'm back on it this week.

Again, apologies.

I do have something to look at in terms of internal code - I need some time with the originator of the code to see what's going on.

I've done some debugging that may help with this. removeRegion that is called causing the client to quit is called from the code path that has the commented out llinfos:

Disabling simulator with message from 64.129.41.86:13006

It can be called from one of two code paths, so this may help you narrow it down.

Yes, you were right... i had experiencied in my new laptop the same behavior... but to be honest, the frequency is one every week or more.... nothing in comparison with the frequency in my iMAC where is every single teleporting.
So im playing more time in my new laptop than the iMAC but it is mandatory that someone fixed this problem asap. Im talking with a lot of people inside SL and the common answer is.... yes "i have the problem" or yes "i know someone that has the problem".... the difference is the frequency when the problem appears...

WindLight 1.19.0 (80044) on a 24 inch imac Intel Core Duo 2.4 GHz running with an ATI Radeon HD2600 256 VRAM and 2GB of ram.

Can't teleport at all now, hangs then crashes EVERY time. reinstalled windLight makes no difference, no settings have changed, no dropping of connection speed, no changes whatsoever.

At the same time i have also got an older iMAC intel core duo 2 GHz running a Radeon X1600 128 Mb VRAM 1GB ram - no problems at all - sharing the same wireless router both machines setups are the same i have tried lower settings in preferences but it doesn't make any difference.

And it only started happening yesterday (Saturday night after 9PM GMT)

I now know exactly what is going wrong - still a little fuzzy on the why, but I'm zeroing in.

Here's what the problem is.

There's a particular message that gets sent from the originating sim to the client when either a teleport / region crossing has been completed successfully (ie the originating sim has contacted the destination sim, the agent has been passed across and then deleted from the originating sim).

This message contains information for the client to talk to the new sim.

This message is getting dropped.

What happens is that the client already knows a teleport is in transit and dumps out the old region information internally after the teleport times out, but doesn't have replacement region information, in which case it considers you logged out and, well, logs you out.

Thats what is happening.

Now, why is this message getting dropped?
Well, it's going via a new system - an HTTPS driven TCP/IP system that encrypts the information since some of the new server information we send to the client we want to keep encrypted.

This system is dropped the message in one of three possible places.

Either in the Simulator sending the message out to the client, in transport on it's way to the client (which is why when you guys turn off TCP/IP on your routers you get the same error) or in the code on the client that takes the incoming TCP/IP message and then fakes a UDP call so the same code that used to talk to the UDP stream is called. We know the actual code that runs when the message is received is not being called because it dumps out text to the logs and all the logs you guys have posted is missing this text - ergo that function is not being called.

I have a suspicion it's in the simulator side - what I need is one of you guys that is seeing this to ping me online if you see me, since I need to watch the logs of the sim you are teleporting from where the failure occurs and look for a specific message. If I see that message, then I know my hunch is correct. If I don't, then we need to look further down the pipe.

I'm going to be online tomorrow (the 26th of Feb) looking for people who are having the teleport fail there and then with this error.

Just wanted you to know that progress is being made.

Needless to say the one bit of suspect code that would have explained it all was not being tripped as I had fondly imagined it was. I've tracked down two actual teleport failures and neither reported anything unusual in the simulator logs.

Well, at least I know it's not what I had hoped it would be - that would have been too simple!

I think I'm going to start looking at the client next..

Today I stuck some extra logging into the simulators to tell me if messages are getting dropped on the simulator.

I managed to miss the roll out by a day so I'll have to wait till we do a patch or another roll out before this code hits the grid.

I'm exploring client side logging (seeing whats already there) and I may well ask some of you guys to turn on more verbose debugging within the client so I can look at those logs to see whats happening, assuming I can figure out what is possibly being logged now, and assuming its the info I need.

Jake

Help us Jake! You're our only hope!!

haha.

So two people connecting through the same router, one has no problem and the other dies on every tp. change the router and it fixes it. I hope you can make some sense out of that Jake.

Another thing I have noticed that hasn't been mentioned here that might or might not be useful information. When I send a TP invite to someone and they don't show up, it never tells me they are offline. A minute or two later I get the message they just came online. but the offline message never comes.

Second Life 1.19.0 (5) Feb 28 2008 17:18:12 (Second Life Release)

You are at 280540.6, 270611.1, 22.4 in CandyCleo located at sim5935.agni.lindenlab.com (8.2.35.237:13004)
Second Life Server 1.19.1.81132

CPU: Intel Core 2 Series Processor (2127 MHz)
Memory: 2046 MB
OS Version: Microsoft Windows Vista (Build 6000)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8600 GT/PCI/SSE2
OpenGL Version: 2.1.1
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 22/7024 (0.3%)
Viewer Digest: 6b1bac12-2a86-e1f2-aa5e-3108db5c8eeb

Repro: TP from "CandyCleo (211,18,21)" to " Southlands (53, 157, 22)" via Landmark
Isle is up and running (1 person on it, reported by "Map")
Date/Time: 04.03.08, 02:02
Result: Could not teleport, received msg "System unable to complete tp in timely fashion, please try again in a few minutes", returned to "CandyCleo (211,18,21)".

Repro: Log off system, log on directly to "Southlands (68, 87, 21)"
Isle is up and running (1 person on it, reported by "Map")
Date/Time: 04.03.08, 02:06
Result: Location not currently available, transported to nearby location "Orientation Island Public (99,169,32).

**SHOCK! Able to TP Home "CandyCleo (212,19,21)" **

Doesn't usually happen though. Last two attempts to get to Southlands (my place of work) resulted in me being transported to nearby locations Hanson (161,103,100) and Ross (34,221,57). I couldn't TP home from either place and had to re-log.

As of 2:21 I'm suddenly able to teleport again. I still want to report this though, as it's been the most frustrating week in my SL life so far. Hopefully this info will help other people in the same predicament!

a) Can you region cross when the Teleport goes RART**? IE can you walk / fly from one region to another?
Nope.

b) Does voice still work when you are in this state?
Didn't try before it 'repaired' itself, sorry.

c) Is this a state that persists across multiple logging in?
Yes.

d) does it happen instantly on logging in, or is this something that starts occurring over time?
Instantly and completely.

e) What router do you use?
Netgear Wireless router for Sky Broadband (UK).

f) What firewall do you use?
I disabled my firewall ages ago but I use and Sunbelt Counterspy.

g) Does it go away if you power cycle your router
No.

Well, that's it. My deodorant is a jasmine variety. ) Thanks for looking after us.

I'm on Debian Linux, and have been experiencing this since i started using SL with the 1.18.5 client. I upgraded to 1.19.0.5 hoping it would have a fix, but it still happens.

I usually get about 4 successful teleports then a failed one. If a teleport fails then the mini-map still says i haven't moved at all, and the title bar still says the previous location. The scenery looks like i'm stuck in nowhere-land, and there is usually a red arrow encouraging me to walk about 3000 miles to reach my destination. It won't even entertain the option of another teleport attempt - the teleport button does nothing.

I log off and then try to log on again, but it tells me something like, "Agent not in region, agent probably in a neighbouring region. Please try again". It takes about 3-5 attempts to be able to log in again.

My workaround has been to log off before attempting teleport because i am more likely to succeed if i have only just logged on.

Oh, one other thing i noticed, on failed teleports there are hundreds of log error messages about unable to set UTF8 settings. Something like that. I don't have the logs to hand right now.

Please let me know if there is a proper solution to this problem. I have skim-read the above but didn't find anything conclusive that would help.

Thanks.

Notice: i'm talking about this precise bug, the one that make you logout if you stay in a region more than X minutes (approx 1 hour), the one that never happens just after a login, etc... not those other tp bugs (that are individual) mentioned in some other comments,

Either that or this is a heisenbug; now that people are looking for it, it's not gonna happen.

I have not had one failed teleport and it started to be this way right after changing my DNS setting to use these. Same with other computers at home using SL.

A number of non Second life things have also improved.

I'm not sure how client side DNS comes into the picture if it even does, but I thought I'd toss this info into the picture in case it helped.

Please don't confuse the two.

If you are getting a gray screen disconnect after TP completes (not crash), then that might be related to this.

Here was my issue: I wasn't able to teleport to some islands at all. It would always log me out. Other islands I could usually teleport to, then sometimes I couldn't.

In one of the logs someone snipped into here, it showed both ports 13004 and 13006 in two separate lines for a single teleport failure. I use a software firewall that I have to specifically open ports for SL to be able to work, and I only had the ports open that SL was using to login to my usually login locations - I didn't realize that teleporting changes udp ports SL is using. For me, the solution was to go into my log, find which ports SL was using to teleport to the islands I couldn't get to (which the logs showed my firewall blocking that destination port), and make a rule to open them. There seems to be a huge range of ports, right now I have udp ports from 12035 to 13006. I don't know if it's documented anywhere what ports ppl need to open for SL to work, but I thought mentioning it in this thread might help someone else too, as there seems to be multiple reasons ppl are not getting the information from the sim they are porting to.

When I am using a NON-AT&T, NON-2Wire router, I do not have any TP issues whatsoever.

Is there a certain port number we can use for pinholes/port forwarding to test out Second Life usability on the 2Wire routers?

Mac OS firewall is disabled. Firewall ports on the router are configured for 443/TCP, 12035/UDP, 12036/UDP, 12043/TCP, and 13000-13050/UDP as per this KB article: https://support.secondlife.com/ics/support/default.asp?deptID=4417

and this one specifically regarding Teleporting and region crossing: https://support.secondlife.com/ics/support/KBAnswer.asp?questionID=3942

I have not tried a different router or network to see if the problem persists. If I use the SAME ROUTER and SAME COMPUTER (the MBP) but running SL under Windows Vista I do NOT experience teleport failures/log outs. Ever. I've been using Vista BootCamped on the MBP since August 2007 because of this showstopping problem: https://jira.secondlife.com/browse/VWR-1749

well that bug is finally fixed and SL looks great on Mac OS X. 20-30 fps is pretty good compared to what we had before, 15 mins of bad graphics and a system freeze. yummy. But now this teleport failure problem makes it a showstopper under Mac OS X for me.

I read magnolia´s comment about running SL on a AT&T DSL router 2wire 2701HG-B..... Well I have the same router but 2701HG-T.... Here is the thing

On My iMac G5 maybe 4 or 5 months ago just the TP process stop working... not even one succesfull TP. Testing different scenarios i realized that when i was running SAFARI in background makein a search or so and I TP my avatar... then i get a succesfull Teleport!!!! almost 100% of the times when i was surfing the net.... TP works...

I bought this thinkpad laptop few weeks ago running Win XP and I downloaded SL.... guest what!?!Unable to render embedded object: File (? 100% of my TP are succesfull..... same router) not found.!!! same config!!!! i try to use on MAC the newest clients and then on the thinkpad....

My laptop runs SL fine on other routers by the way....

my 0.02cents

other issues i've seen with this router in the past are connection failures/ drop outs when loading inventory after clearing cache and zooming in or out on the main map. excessive packet flooding maybe? I get 2.5mbps dowload and 420kb upload speeds and set the network speed in SL prefs to 500kbps to avoid flooding and increased ping time. but again all these functions work fine and do not cause the same problems for the router using Vista Home Basic on the same MBP hardware and AT&T router with no configuration changes.

Thank you Soft Linden for taking on this problem. I have faith in you!

Edward

At the end of March, I installed 1.18.3.5 and was able to transport quickly and flawlessly multiple times for the first time since Nov 07' when I started following this thread! PROBLEM SOLVED!

Nope......

Since April 4, and the release of 1.19.1.4, as warned in the blog, I'm forced to quit or download the new client and then I can't teleport anymore.

So Soft, I'm thinking there is something that every viewer did after 1.18.3.5 that messes up Mac users on the 2701HG-D 2wire router.

http://www.apple.com/support/downloads/airportextremeupdate2007002.html

I'm seeing the 2WiRE as a common thread, and I've found a few people suggesting that the above has helped them with packet loss using other network software.

I've used the 1.18,1.19, and the new 1.20 with this same issue. prior to all this I had to manually enter the ip's and domains into my system's hosts.txt file (i.e. simXXX.agni.lindenlab.com, lindenlab.com, secondlife.com). I still can't teleport. IMHO this isn't an issue with router's or on the user's setup its an issue with the client, with your servers and host, or even both. Each sim I visit has to either be a slurl or manually entered before login with out an option of leaving that sim. I'm not even going into my hardware and OS setup as seeing from the tracker it doesn't matter you still get this bug.

This stuff doesn't help sl's credibility within the MMO world and it devalues it intirely as anything more than a pipe dream or hobbist ware. Now don't get me wrong I love SL and think it has a lot of protential, machinima being a big one for me.

Now I hope that in between my rant there is something that helps point out a major flaw that hasn't been addressed in a while and with all that said, this looks like its an issue with the timeouts on the networking protocol. meaning as the client goes to switch to the new sim the dns timesout and then the client's connection to the old sim dies. thus, forcing a logout.

I have been in SL for almost a year now, but his problem about three weeks ago. Since having the problem start, I have done a complete format and reinstall of everything (long overdue anyway), but the symptoms stayed the same.

The symptoms: when I TP the blue bar moves very slowly, and I know then it will be a failed TP, until some time later I return back in the sim I was in before, but it is just empty landscape, and moments later I am logged out. I know I appear at the destination sim, my friend sees me, but I am fly hovering and quickly disappear.

When the problem started, the first week it was worse: I not only could not TP, but I could not hear streaming music, although environment sounds were fine, and my groups were empty. Since then, music has come back, and groups too, but I have noticed I cannot now edit anything about the group I am the owner of.

One more thing, I agree with previous posters who say this problem is much more widespread than it seems, the attitude seems to be to brush it away with comments like "That's SL". I myself am only posting because my friend persuaded me to, I too brushed it aside and fouind a workaround - at the log in screen type in the name of the region I want, which means to change sims I need to log off and on again.

Here are the tech specs I have:

Second Life 1.19.1 (4) Apr 2 2008 11:59:37 (Second Life Release)

You are at 272470.7, 256339.1, 27.0 in Romero located at sim213.agni.lindenlab.com (8.4.128.89:13001)
Second Life Server 1.21.0.85745

CPU: AMD (Unknown model) (2210 MHz)
Memory: 2048 MB
OS Version: Microsoft Windows XP Dodatek Service Pack 2 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 6800 XT/AGP/SSE2/3DNOW!
OpenGL Version: 2.1.2
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.14680 (Mozilla GRE version 1.8.1.13_0000000000)
Packets Lost: 0/2386 (0.0%)
Viewer Digest: bb2966f6-cf81-a0de-1e21-dcd21f05428a

http://slurl.com/secondlife/Ihruree/25/233/28

Please do attend if you're one of the people having regular problems. It's amazing how often live discussions turn up new information even when a topic's been written about extensively. I'll follow up afterward with notes about what we discussed, what we've learned so far, and what we're working on.

I have 3 Mac
I was open all ports & firewall but nothing to change.

1) MacPro 8core 3.2Ghz , 10G memory, Nvidia8800GT 512MB, OS Leopard
2) Mac G5 Dual 2.0Ghz, 3G memory, Radeon9800pro 256MB, OS Tiger
3) I MAC G5 2.1Ghz, 2.5Gmemory, Radeon X600XT 128MB, OS Tiger
Router : AT&T 2wire gateway 2701HG-B Ethernet connection.

For Mac and Linux, Dan and I have traced this down to exactly where the problem was introduced between the 1.18.3 and 1.18.4 viewer series - love to Dan for testing a billion builds for me while narrowing this down. The problem was an upgrade to a newer version of libcurl, the library that does much of our reliable communications work. Walking the relevant change out fixes this problem, but introduces others. I'm diving into the details of this presently, and plan a fix soon.

I still haven't found a reproducible case of this with Windows, however. Each Windows user I've looked at has had other problems, either an unsupported graphics chipset causing general system issues, or an ISP that's dropping packets between their system and our network. Once the known issue is resolved with Mac and Linux, I'll create a separate issue for drilling down into Windows issues to see what we can do on our end.

In the near future, I'm also adding some changes that ease the load on the teleport system incurred by overly aggressive bots and combat cheating hacks. This will increase teleport reliability overall.

I'm a Windows user, and I've had the same problem ever since I joined SL a month ago. I've actually only experienced three 3 successful teleports between regions wthout getting logged out, in those four weeks. (Those left me quite confused, because they ruined the log-out statistics.) I've tried running SL both at my stationary computer at home and on the laptop both at home and on campus, and teleporting just won't work. So if you need a volunteer/dummy for Windows crash-testing (or perhaps more technically correct; getting-logged-out-while-teleporting-testing) I'd be more than happy to help. Obviously, I have no experience with the older viewers and whether those work on either system or internet connection, so I cannot actually confirm that "other problem, graphics chipsets or general system issues" are not to blame. As it is now, it is not only making exploring SL quite the hazzle for me, I am also unable to use it for educational purposes until I can teleport myself or my students around.

Also, I don't think anyone mentioned it above: People waiting at the destination of the teleport say that I arrive, hover in the air for a while and then get logged out. I get the grayscale emptyness though, and never see them.

The two systems:
1:
Second Life 1.19.1 (4) Apr 2 2008 11:59:37 (Second Life Release) AND ALSO: Second Life 1.20.6 (86925) May 6 2008 20:43:54 (Second Life Release Candidate)

You are at 249292.2, 245664.8, 27.1 in ISTE Island 2 located at sim7100.agni.lindenlab.com (8.10.144.102:13000)
Second Life Server 1.21.1.86182

CPU: AMD (Unknown model) (2805 MHz)
Memory: 2046 MB
OS Version: Microsoft Windows Vista (Build 6000)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 7300 LE/PCI/SSE2/3DNOW!
OpenGL Version: 2.1.0
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.15136 (Mozilla GRE version 1.8.1.13_0000000000)
Packets Lost: 0/1002 (0.0%)
Viewer Digest: bb2966f6-cf81-a0de-1e21-dcd21f05428a

2:
Second Life 1.19.1 (4) Apr 2 2008 11:59:37 (Second Life Release)

You are at 249292.2, 245664.8, 27.1 in ISTE Island 2 located at sim7100.agni.lindenlab.com (8.10.144.102:13000)
Second Life Server 1.21.1.86182

CPU: Intel Core 2 Series Processor (2193 MHz)
Memory: 2046 MB
OS Version: Microsoft Windows XP Service Pack 2 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: Quadro NVS 135M/PCI/SSE2
OpenGL Version: 2.1.1
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.15135 (Mozilla GRE version 1.8.1.13_0000000000)
Packets Lost: 0/530 (0.0%)
Viewer Digest: bb2966f6-cf81-a0de-1e21-dcd21f05428a

My friend and I were going to contribute to SVC-2345 (kind of about not seeing past a sim boundary) which is one of my problems, so we decided to try adjacent sims which were well-known. We went to Grasmere (Hello Torley) and I found I COULD see past the sim border, into Borrowdale, and even cross into it. We also tried at sLiterary, home of the Globe theatre (spread over 4 sims) and the same was true, I could see the whole theatre.

I examined my other issues, not being able to edit my own group - now I could (and still can); teleporting, I found I could!!! ... but only for about 2 hours after that, then whatever was causing the problem seemed to come back and since then TPing has been logging me out.

This happened on the 15th May, about 12pm SLT, until 2pm SLT.

im on a MBP 15" OS 10.4.11
2.33 GHz Intel Core 2 Duo
2GB 667 Mhz DDR2 SDRAM
ATI Radeon X1600

Im running the last SL viewer....Is it possible to get an old viewer while you fix all this issues? pleaseeeeeeee?

About-land doesnt work, and logs out on any teleport. Been like this for days.

I'm kind of a solitary fellow, but after a time I do wish to take a stroll around, away from home!

If I use SLURL to try to log in elsewhere, it says: Unable to log in to Second Life, DNS Could Not Resolve the Host Name.

Hmm...

Does teleporting need DNS by chance? My home (Caledon Moors) might just already be in my DNS Cache or what not. Hmm.

Sure, you can use an older viewer until we have a proper fix. Keep in mind however, that this is not eligible for support, and some features may not work. Please comment here to let me know whether this does or does not fix issues for you.

For Mac:
http://download-secondlife-com.s3.amazonaws.com/SecondLife_1_18_3_5.dmg

To avoid being forced to update, you will need to create a file in the Second Life package called:
Second Life.app/Contents/Resources/arguments.txt

In this file, you'll need to add "--channel teleporthack" (without the quotes)

For Linux:
http://download-secondlife-com.s3.amazonaws.com/SecondLife_i686_1_18_3_5.tar.bz2

To avoid being forced to update, in the install directory, create a file called:
gridargs.dat

In this file, add "--channel teleporthack" (without the quotes)

With both versions, note that many of your preferences will be reset, and the first run will take a while to appear, as your entire cache will be cleared.

@Soft Linden

Reinstalled :1.19.0 (5) does not help.
--------------
Second Life 1.19.0 (5) Feb 28 2008 17:18:12 (Second Life Release)

You are at 260530.0, 289852.7, 21.6 in Fuchs located at sim3682.agni.lindenlab.com (216.82.22.163:13002)
Second Life Server 1.21.1.87495

CPU: Intel Core 2 Series Processor (2666 MHz)
Memory: 3325 MB
OS Version: Microsoft Windows Vista Service Pack 1 (Build 6001)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8600 GT/PCI/SSE2
OpenGL Version: 2.1.1
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 0/2030 (0.0%)
--------------

Useing Second Life Release Candidate 1.20.6 (86925) same thing:
Second Life 1.20.6 (86925) May 6 2008 20:43:54 (Second Life Release Candidate)

You are at 260530.0, 289852.7, 21.6 in Fuchs located at sim3682.agni.lindenlab.com (216.82.22.163:13002)
Second Life Server 1.21.1.87495

CPU: Intel Core 2 Series Processor (2666 MHz)
Memory: 3325 MB
OS Version: Microsoft Windows Vista Service Pack 1 (Build 6001)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8600 GT/PCI/SSE2
OpenGL Version: 2.1.1
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.15308 (Mozilla GRE version 1.8.1.13_0000000000)
Packets Lost: 0/811 (0.0%)
----------------------

NO TP and NO Groups

Its impossible to use SL that way.

Thaaaaank You for the Temporary Fix for Mac, It works!:

-------------------------------------------
For Mac:
http://download-secondlife-com.s3.amazonaws.com/SecondLife_1_18_3_5.dmg

To avoid being forced to update, you will need to create a file in the Second Life package called:
Second Life.app/Contents/Resources/arguments.txt

In this file, you'll need to add "--channel teleporthack" (without the quotes)
-------------------------------------------

*Note: control-click Second Life in the applications folder after you've installed 1.18.3.5 and choose "Show Package Contents" to find Contents/Resources/arguments.txt

2-wire 2701 HG-B (seeing a pattern here).

Connect is slower than Windows box, but I'm stuck in entry sim - Generally fantastic performance, but only in the sim I enter. Walking across sim boundaries=loss of control, crash. TP attempts= 5 second lag, crash.

Have tried every possible config on the 2Wire router, port settings, DMZ - no effect.

Winbox exhibits similar behavior, but only crossing many sims, or many TP's...(but without any special configs to the router, it just works)

The iMac tho - dead in the SL waters no matter what ... (just SL so far, other apps seem to work fine, but one day does not a shakedown cruise make).

• Since the release of 1.18.4, crash on almost every TP. 99.99% of TPs fail with a forced quit. this happens for every viewer since 1.18.3.5.
  It looks like TPs time out because crashes don't happen immediately. Progress bar goes about two thirds of the way, and then quit dialog.
• This does not affect 1.18.3.5 in any way, in my experience. Other problems with that version, but not this bug.
• Crashes are not specific to any sim. I crash just as well from my home sim, a class 5 server that is only 9 months old.
• Groups sometime don't appear until Search is executed, sometime not even the. I don't know the frequency or correlation, but more often than not.
• This is a very real bug that affects a great many users that I have talked to in world, who didn't know about JIRA.

My configuration works for the 1.18.3.5 viewer.
Mine is not a router issue. Regular use of 1.18.3.5 without issue rules that out. I have a relatively new 2wire unit.
This is not a firewall or SELinux issue, as turning off SELinux and firewall temporarily had no effect.
Brand new machine as of November 1, 2007.
64 bit Linux with compatibility libs installed. All updates and security patches installed.
My DSL connection has a ~1300 kbps download speed with no packet loss.

My config:
==========================================================================================
Second Life 1.18.3 (5) Sep 20 2007 11:42:15 (Second Life default)

You are at 247257.5, 241955.5, 21.7 in Kalani Cove located at sim4302.agni.lindenlab.com (63.210.157.206:13002)
Second Life Server 1.21.1.87495

CPU: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
Memory: 2013 MB
OS Version: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 16:52:18 EST 2008 x86_64
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 7600 GT/PCI/SSE2
OpenGL Version: 2.1.1 NVIDIA 100.14.19
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 0/3550 (0.0%)
==========================================================================================

Torley et al, can someone at LL please take a careful look at the known good viewer, 1.18.3.5, and diff it to 1.18.4, and find out what code changes made this bug happen? The change happened after 1.18.3.5. Please take this issue seriously. For those of us that experience it, it is a show stopper once 1.18.3.5 is deprecated (which must eventually happen). I will also attach my SecondLife.log as the file Stephani_Honi_SL_TP_crash.log to this bug, assuming I can.

2008-05-23T20:00:22Z INFO: ViewerStatsResponder::error 499 STATUS_EXPIRED
2008-05-23T20:00:22Z WARNING: setSeedCapability: Ignoring duplicate seed capability
2008-05-23T20:00:35Z INFO: removeRegion: Removing region 247296:241920
2008-05-23T20:00:35Z INFO: LLMessageSystem::disableCircuit for 8.2.35.238:13001
2008-05-23T20:00:35Z WARNING: disableCircuit: Couldn't find circuit code for 8.2.35.238:13001
2008-05-23T20:00:35Z INFO: removeRegion: Removing region 247040:241664
2008-05-23T20:00:36Z INFO: LLMessageSystem::disableCircuit for 63.210.159.30:13001
2008-05-23T20:00:36Z WARNING: disableCircuit: Couldn't find circuit code for 63.210.159.30:13001
2008-05-23T20:00:36Z INFO: removeRegion: Removing region 247040:241920
2008-05-23T20:00:36Z INFO: LLMessageSystem::disableCircuit for 63.210.157.206:13002
2008-05-23T20:00:36Z WARNING: disableCircuit: Couldn't find circuit code for 63.210.157.206:13002
2008-05-23T20:00:36Z INFO: removeRegion: Removing region 247296:241664
2008-05-23T20:00:36Z INFO: LLMessageSystem::disableCircuit for 216.82.17.92:12035
2008-05-23T20:00:36Z WARNING: disableCircuit: Couldn't find circuit code for 216.82.17.92:12035
2008-05-23T20:00:53Z WARNING: LLEventPollResponder::error: <5> got 404: Not Found
2008-05-23T20:00:53Z INFO: LLEventPollResponder::stop <5> https://sim2341.agni.lindenlab.com:12043/cap/fa41ee97-3a9e-50e6-e1e7-5578af487751
2008-05-23T20:00:53Z INFO: LLEventPollResponder::stop <5> https://sim2341.agni.lindenlab.com:12043/cap/fa41ee97-3a9e-50e6-e1e7-5578af487751
2008-05-23T20:00:58Z WARNING: LLEventPollResponder::error: <3> got 404: Not Found
2008-05-23T20:00:58Z INFO: LLEventPollResponder::stop <3> https://sim5936.agni.lindenlab.com:12043/cap/e7193e08-cb13-c141-3251-3046a2c043f9
2008-05-23T20:00:58Z INFO: LLEventPollResponder::stop <3> https://sim5936.agni.lindenlab.com:12043/cap/e7193e08-cb13-c141-3251-3046a2c043f9
2008-05-23T20:01:20Z WARNING: createXml: Alert: [TeleportFromLandmark]
2008-05-23T20:01:20Z WARNING: createDialog: Alert: Are you sure you want to teleport?
2008-05-23T20:01:22Z WARNING: updateMeshTextures: invalid host for object: 790634dd-e8f5-4769-b1c3-acd764f556ec
2008-05-23T20:01:23Z INFO: idle: Kills on unknown objects: 9
2008-05-23T20:02:12Z WARNING: removeRegion: RegionDump: Coco Beach South 216.82.18.221:13002 { 226560, 239360, 0 }
2008-05-23T20:02:12Z WARNING: removeRegion: Agent position global { 226793, 239518, 22.8706 } agent { 232.637, 158.027, 22.8706 }
2008-05-23T20:02:12Z WARNING: removeRegion: Regions visited 2
2008-05-23T20:02:12Z WARNING: removeRegion: gFrameTimeSeconds 200.066
2008-05-23T20:02:12Z WARNING: removeRegion: Disabling region Coco Beach South that agent is in!
2008-05-23T20:02:12Z WARNING: createXml: Alert: [YouHaveBeenLoggedOut]
2008-05-23T20:02:12Z WARNING: createDialog: Alert: You have been logged out of Second Life:
You have been disconnected from the region you were in.

Click Continue to look at existing IM and chat.
You will not be able to perform any other operations.
Click Quit to exit Second Life immediately.
2008-05-23T20:02:12Z INFO: LLMessageSystem::disableCircuit for 216.82.18.221:13002
2008-05-23T20:02:12Z WARNING: disableCircuit: Couldn't find circuit code for 216.82.18.221:13002
...

http://download-secondlife-com.s3.amazonaws.com/SecondLife_1_18_3_5.dmg

To avoid being forced to update, you will need to create a file in the Second Life package called:
Second Life.app/Contents/Resources/arguments.txt

In this file, you'll need to add "--channel teleporthack" (without the quotes)
----------------

It worked on the iMac 3.06/8800gs - although it is a step back in time, viewer wise, everything functioned correctly, although the Graphics and CPU were not recognized, and thus dog slow (15-20 FPS. 2-3 at times)...

still not the solution tho - and as stated, not supported, but it did let me get around ok...

Getting 40-45 FPS, at 256m draw range with little to no lag was awesome, as was the graphics quality by comparison, but such as it is, with the temporary hack, at least I am able to visit my neighbors sim 20 m away.

Viewer 1.18.3.5 doesnt work for me at all! Won't log in, says "DNS Could Not Resolve The Host Name". At least 1.19 lets me connect (but no teleport, or moving between sims.)

Spring 2008 iMac, 3.06/8800/4 gigs, Leopard 10.5.2...

I was able to resolve these issues by manually setting DNS in OSX networking - and believe it's connected to the 2Wire 2701 router (AT&T) - I am able to log and move about freely, and TP with both RC and 1.19.1.4 now that DNS is set manually in both the router and Networking.

Other issues still remain... but for the large part, manually setting DNS seems to have solved the TP/crossing sim problem. I tried both AT&T DNS and OpenDNS - no major differences (other than having to track DNS down for AT&T).

RC is flaky, 1.19.1.4 worked fairly well - temporary timeouts aside. Looked great tho, and let that new GPU really work!

Soft Lindens workaround with the older client (-teleporthack) was also very stable.

The problem I'm zeroing in on is indeed related to a change in how the viewer does name resolution, which was introduced with 1.18.4. It seems there's something about how the 2WiRE router responds to DNS queries that c-ares, the name resolution library we use with libcurl, really hates.

I just logged in and everything works again...

Earlier today, unrelated to SL, I rejiggered my whole wireless network. I couldn't say what in particular changed (router wise) but I'm now mostly using an airport express instead of a linksys. For what it's worth.

1. This is something that started with 1.18.4? I didn't notice issues until I started using the RC for 1.20. I can no longer leave the region I log into. I'm stuck in one 256x256 region unless I re-log. Also, while moving about the region, the parcel info always reports the information on the land I logged into. Weird.

2. Something is horribly wrong with the link that cobb supplied. That client crashes OpenGL on my Leopard iMac something awful. I had to restart the whole system to fix it.

3. I filed a support ticket this past week with Shaun, but he suggested that it is either my router/firewall/antivirus or my ISP. Now, I'm certain that it must be the router since I'm not alone!

4. I don't know if this helps, but whenever I try a traceroute to data.agni.lindenlab.com, it times out at:
LINDEN-RESE.car2.SanFrancisco1.Level3.net (4.78.242.50) 92.574 ms 91.716 ms 90.699 ms

5. On A side note, the 2Wire router sucks all around. I hate that it sends incorrect DNS information when it can't connect to the internet. Without running dscacheutil -flushcache, I'm stuck looking at the "Resolution Successful" page. Yuck.

I pray this gets some attention soon!

I have a Sprint 3g card and it works fabulous...can do anything in SL with no problems...same computer, same SL config, etc.

So, today...i called ATT and got a return auth for the modem. I am going to buy my own and see if the problems exist. Prior to this 2wire adventure, i was using a rural telecom and a noname modem with a netgear router for the wireless...again had few problems with SL. I am pretty sure the is a Mac/2wire incompatibility issue. I also found that folks in WoW are having the same issue...here is a link to an article that may help solve the issue.

http://forums.worldofwarcraft.com/thread.html?topicId=3120974294&sid=1&pageNo=12

I run 64bit Fedora Core Linux with 32bit compatibility, so whatever this is, it is not strictly a MacOS issue.
It may very well be that WoW had some problem that is identical in nature. Maybe Soft Linden can tell us if there is shared code.
The only thing that is a common (and not absolute) thread that I see is the use of 2WIRE DSL.
I have the 2WIRE 2701HG-B unit.

Model Number: 2701HG-B Gateway
Hardware Version: 2700-100594-004
Software Version: 5.29.47

I don't use wireless at all, never have. It works well for everything else, including streaming audio and video. I have patched and prevented any possible URL exploits, not that my system was ever compromised, as I have a admin password set on my router-gateway (as everyone well should). Find the workaround for any possible DNS redirect exploit here:
http://www.dslreports.com/forum/r19987755-2Wire-Cross-Site-Request-Forgery-Vulnerability

As already noted, the previous version, 1.18.3.5 continues to function well for me with teleporting.
The problem lies somewhere in the changes to SL code (possibly server side) between version 1.18.3.5 and later versions, as reported by Soft Linden.
I have noticed some marginal improvements since last week's rollout of server code version 1.22, and can sometimes TP successfully using 1.20.8.
My success rate at TP is somewhere around 20% success rate using 1.20.8 since the rollout, 0% prior to that.

June 20th, 2008
Why has there been no movement on this bug?
It's not a configuration glitch. My older client works fine.
Any hints on when this might get a serious look see?

Seems this bug gets picked up by a Linden and they are really focused on finding a solution, but then find that this issue is more difficult than anticipated so interest wanes and the problem sits dormant. Rinse. Repeat.

I cancelled my paid membership months ago as this has been a lingering problem. Too bad. I miss playing SL.... but doesn't seem there is going to be a resolution any time in the near future, unless I move and am no longer forced to use ATT as my ISP.

Sidenote to rocksand jewell: You were able to keep ATT as your ISP even though you are using a modem purchased at Best Buy? Can you go into that a little further?

This is most certainly a Mac/2Wire Gateway router problem.

All you have to do is login to the new modems firmware with your web browser (usually going to 192.168.11, 192.168.1.254, 10.0.0.1, etc) and fill in your username (should be your primary email address) and password. There's often a wizard to run through. If at all possible also fill in the dns numbers as DHCP is often unreliable or slow to obtain them.

As for at&t having issues, it's become a bi-yearly event for me to put out a service call, there's a defect in the junction box boards they use that causes them to burn out over time, so I don't know if that's aggravating your problem or not.

In the interim, you can replace the router, or you can call your ISP's support and ask for help in configuring your computer to use their DNS directly. Others have solved this by avoiding use of the 2WiRE built-in DNS forwarding, which seems to be the failure point. If you or others try this, it would be helpful to hear back whether it helped.

This exact same problem started for me on June 18th. Same symptoms, same issue, same frustration. Except I am not using AT&T, or even a DSL line. I have a cable modem through Cablevision here in NYC and am working with a Linksys router. Prior to June 18 I'd had no problems with the same exact setup. Nothing about my modem or router has changed, even a little.

So this is more widespread than just a DSL/ATT issue. It's affecting cable modem folks also.

FWIW, I'm running WinXP64, but I don't think it matters.

If someone wants to hand me a router/DNS fix, I'll try it, short of having to buy a new router when the old one worked perfectly all this time (and still works perfectly, save for this issue.)

It seems there is some sort of code segment related to teleporting is not functioning the same way in the unix platforms as it does in the windows client... This might be a clue?

Can you share with me the steps on how to do this?

Soft Linden, you said: "you can call your ISP's support and ask for help in configuring your computer to use their DNS directly. Others have solved this by avoiding use of the 2WiRE built-in DNS forwarding, which seems to be the failure point. If you or others try this, it would be helpful to hear back whether it helped."

Can you give specific steps on how to bypass 2WiRE built-in DNS forwarding? I would like to try it and see if it helps.

I would like to try configuration changes before replacing a perfectly good router that only has issues with SL and not with other programs.

I have a Macbook Pro and haven't been able to successfully use all the viewer functions for SL since the release of 1.18.4.

A chance comment made on the recent RC release blog drew my attention to the possible 2Wire connection - my 2Wire modem is model 2071-A

I now have this problem with every single TP I try and do ( am in the USA now on wireless ... in the UK on wireless 6 weeks ago i didn't have the issue). The TP starts, takes too long and then I get the continue/quit message. I am on a brand new high end sony vaio using windows vista. I haven't had a single successful TP in 4 days. I have to stay logged out 1 minute or so log back in and i am at my desired destination.

I also have no voice chat now.

Pretty much unplayable as it is. Happy to give whatever feedback is needed to get it sorted.

Slapnuts

I tested removal of attack detection within the 2WIRE firmware, with no change.
Removed attack detection for:

Excessive Session Detection
TCP/UDP Port Scan
Invalid Source/Destination IP address
Packet Flood (SYN/UDP/ICMP/Other)
Invalid TCP Flag Attacks (NULL/XMAS/Other)
Invalid ICMP Detection
Miscellaneous

I am still not sure what "avoiding use of the 2WiRE built-in DNS forwarding" means, but I can resolve DNS just fine, either using hard coded IP addresses or using DHCP. Any suggestions?
Hopefully you will clarify this, or provide steps on how we might change DNS settings to suit this one application that requires us to hack our routers so that we might use your service. Without this information, we are unable to test configuration changes as a workaround to this bug.

• TP anywhere I like! OMG!
• Take snapshots
• Edit "About Land" properties
• Groups update without error
• Upload files

This may help the folks with related bugs as well, not sure. Seems related to VWR-5521
http://jira.secondlife.com/browse/VWR-5521

I stumbled on it while looking at the OpenDNS web pages for proper configuration for using OpenDNS's DNS servers:
https://www.opendns.com/start?device=ubuntu

"To avoid having your settings get revoked after reboots, or after periods of inactivity, do this:

$ sudo cp /etc/resolv.conf /etc/resolv.conf.auto
$ sudo gedit /etc/dhcp3/dhclient.conf

1. append the following line to the document
   prepend domain-name-servers 208.67.222.222,208.67.220.220;
2. save and exit
   $ sudo ifdown eth0 && sudo ifup eth0

You may be required to change eth0 to your own network device's name if it uses a non-standard name."

I use Fedora Core Linux 7, not Unbuntu, but this may work for other Linux distros as well.

I edited the file called dhclient-eth0.conf (your system may have a different file to edit. My system's interface is eth0)

Added the line:
prepend domain-name-servers 208.67.222.222,208.67.220.220;

This points your system at the OpenDNS servers so that your client can find them.
I have no idea why this works, but it does for me. I tried everything else.
OpenDNS has information on how to point your system at their DNS servers for other systems including other flavors of Linux, Windows Macintosh, etc.
https://www.opendns.com/start

I hope that this helps.

P.S.-
I also tried added these DNS server IP addresses to my 2WIRE configuration:
https://www.opendns.com/start?device=2wire
But this alone didn't do the trick, so I also edited my dhclient file.
I'm using hardcoded IPs for DNS as well as the fix described above.

Mac users, see below.

is this a fix for a PC?????

sorry, it's all gobbledegook to me - tech savvy, but not THAT tech savvy

... and I have a Mac - which I miss being able to use SL in properly - bootcamp is great - and the windows version of SL works amazingly well in that - same modem btw.

... for some reason it's only on the Mac side of my puter that I have the problems.

/me is still scratching head

Wish someone would fix this properly in the base code - or provide a patch for those of us it effects.

In the meantime - a step-by-step easy to understand procedure for the non-tech literati would be good

... and one for a Mac would be even better.
Shai

Hadn't used SL in months until yesterday. I downloaded it again and the first time I attempted to teleport it did not work so I did a search for recent and similar bug reports.
Before I found this particular issue I found another that gave me the idea of deleting everything and re-downloading. When I did so I could teleport, temporarily anyways. I made it to one different sim but after about 3 minutes the game froze and crashed, when I re-opened it I could no longer use the TP function.

Since deleting and re-downloading had worked before I tried it, though my attempt was not successful.
I also tried downloading the SL Release Candidate just in case but it did not work either.

"In the meantime - a step-by-step easy to understand procedure for the non-tech literati would be good"
I'll second that. I'm using a Mac also.

MacOS has a similar issue with DNS resolution (changing IP addresses like 192.168.1.1 to domain names like yahoo.com).
Changing the resolv.conf file should fix it as well, because under the covers of MacOS lies a Linux/Unix like operating system.

To attempt to fix this on the Macintosh:

Find the app called "Terminal" and open it. This is the command line client.
At the prompt, type "ls -l /etc/resolv.conf" (without the quotes - notice that there is no "e") and see if it is a symbolic link or a plain file.

You should see output like this for a linked file, meaning that this file is actually the other file pointed to (AKA a symbolic link):
$ ls -l /etc/resolv.conf
lrwxrwxrwx 2 root root 139 2008-07-08 19:13 /etc/resolv.conf -> /var/run/resolv.conf

(The lower case L at the beginning of this means that it's a link to another file, in this case the resolv.conf that lives in /var/run/, which is good)

If your file looks more like this...

$ ls -l /etc/resolv.conf
rw-rr- 2 root root 139 2008-07-08 19:13 /etc/resolv.conf

... which is likely, then you will want to fix it by typing at the prompt:

"sudo rm /etc/resolv.conf; sudo ln -s /var/run/resolv.conf /etc/resolv.conf"

This will remove the useless /etc/resolv.conf and point to the good and working one in /var/run

reboot your Mac

If this does not fix the problem, you can edit /var/run/resolv.conf directly and add your preferred DNS servers to the file.
Open the file /var/run/resolv.conf in an editor (sorry, I don't have a Mac so I don't know how to tell you to do this) and add this line:

prepend domain-name-servers 208.67.222.222,208.67.220.220;

save and exit
reboot your Mac

You can find a more detailed description of the problem here:
http://relentlessinquiry.wordpress.com/2007/11/08/mac-os-dns-fix-for-second-life/
" Under Mac OS X, system applications, like Firefox, Safari, etc, use the built in resolver libraries. The Second Life client, like the nslookup utility, apparently is using classical DNS rather than the system libraries and using only /etc/resolv.conf to get information. The problem was that my /etc/resolv.conf file was no longer a link to /var/run/resolv.conf, and thsu was not supplying the correct information. This can happen for various reasons, including system updates, or booting without a network cable.

The symptom to identify this is if the person CAN get to www.secondlife.com from a browser, do ssh from a terminal/shell window, etc, but the Second Life client claims that there is a DNS error. This shows that the operating system is correctly doing name lookups via the built-in libraries, but that DNS is not correctly configured.

Diagnosis: Have the customer open up a terminal window and do "ls -l /etc/resolv.conf" and see if it is a symbolic link or a plain file. It should be a link to /var/run/resolv.conf.

Correction: If not, they should fix it: "sudo rm /etc/resolv.conf; sudo ln -s /var/run/resolv.conf /etc/resolv.conf"

If this does not resolve the problem, inspect the contents of /var/run/resolv.conf. If there is a problem with the network DHCP, there will not be any correct nameserver lines in the resolv.conf, and then that's a client network problem not subject to quick fixes. "

best regards,
Strata aka Maybear "

Details: When I have logged in (regardless of where I log in at) I am unable to teleport to another location. I get logged out of second life when I try to teleport. This has been happening repeatedly! I've tried even using an ethernet connection, rather than wireless, and cleared my cache, and restarted my computer, still no luck. 1 teleport at the most, then logged out. I'm on a mac, running on OS 10.4.11

/////
Greetings katrine fredriksson,

Thank you for contacting us about this issue you are experiencing. In order to better diagnose the problem we need to know some information regarding your computers hardware and software configuration. Could you please tell us:

• Your graphics card information, on Macintosh, your graphics card can be identified with the utility application System Profiler, under "PCI/AGP Cards".
  1. Click on the Apple symbol in the top left of the screen.
  2. Click the More info... button.
  3. From the Hardware dropdown, select PCI/AGP Cards.
• Your Current OS Version
• Type of internet connection (Wired, Wireless, connection speed etc)

Could you please also attach a copy of your Secondlife.log file directly after the viewer has crashed and closed. Your Secondlife.log file can be typically found in:
[username]/Library/Application support/SecondLife/logs

Regards,
Mark
Linden Lab Support

/////

Mark,
Thank you for the request for information. I have provided the necessary information below.

Graphics Card and Display Information:
ATI Radeon X1600:

Chipset Model: ATY,RadeonX1600
Type: Display
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x71c5
Revision ID: 0x0000
ROM Revision: 113-xxxxxx-158
EFI Driver Version: 01.00.158
Displays:
Color LCD:
Display Type: LCD
Resolution: 1440 x 900
Depth: 32-bit Color
Built-In: Yes
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported

------

Mac OS 10.4.11
Processor: 2.33 Ghz Intel Core 2 Dui
Memory: 2 GB 667 Mhz DDR2 SDRAM

Connecting to Internet via DSL connection over wireless (and wired conenection, I've tried both)

Wireless Speeds:
Download Speed: 5931 kb/s
Upload Speed: 670 kb/s

(all current logs were attached)

//////////////

Hello katrine fredriksson,

Thank you for contacting Linden Lab Support regarding the issue that you have mentioned.

I Would like you to do the following and then inform me of the results.

• Go into your Mac Hard Drive
• Click on applications
• Click on utilities
• Click on Network Utilities
• Then ping your IP and trace route your connection to
  "data.agni.lindenlab.com"

Best regards,

Mark,

Linden Lab Support,

///////////////

Ping has started ...

PING 192.168.0.65 (192.168.0.65): 56 data bytes
64 bytes from 192.168.0.65: icmp_seq=0 ttl=64 time=0.043 ms
64 bytes from 192.168.0.65: icmp_seq=1 ttl=64 time=0.053 ms
64 bytes from 192.168.0.65: icmp_seq=2 ttl=64 time=0.070 ms
64 bytes from 192.168.0.65: icmp_seq=3 ttl=64 time=0.072 ms
64 bytes from 192.168.0.65: icmp_seq=4 ttl=64 time=0.051 ms
64 bytes from 192.168.0.65: icmp_seq=5 ttl=64 time=0.086 ms
64 bytes from 192.168.0.65: icmp_seq=6 ttl=64 time=0.091 ms
64 bytes from 192.168.0.65: icmp_seq=7 ttl=64 time=0.117 ms
64 bytes from 192.168.0.65: icmp_seq=8 ttl=64 time=0.112 ms
64 bytes from 192.168.0.65: icmp_seq=9 ttl=64 time=0.070 ms

— 192.168.0.65 ping statistics —
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.043/0.076/0.117/0.024 ms

Traceroute has started ...

traceroute to data.agni.lindenlab.com (64.154.223.192), 64 hops max, 40 byte packets
1 home (192.168.0.1) 2.914 ms 1.890 ms 2.798 ms
2 hlrn-dsl-gw32-224.hlrn.qwest.net (207.225.112.224) 42.326 ms 44.404 ms 45.533 ms
3 hlrn-agw1.inet.qwest.net (71.217.188.249) 43.491 ms 46.210 ms 43.038 ms
4 67.14.2.85 (67.14.2.85) 65.022 ms 63.937 ms 65.171 ms
5 xe-8-2-0.edge2.dallas3.level3.net (4.68.63.53) 65.055 ms 65.094 ms 64.969 ms
6 * * vlan79.csw2.dallas1.level3.net (4.68.19.126) 70.307 ms
7 ae-73-73.ebr3.dallas1.level3.net (4.69.136.157) 75.049 ms ae-63-63.ebr3.dallas1.level3.net (4.69.136.153) 66.980 ms ae-83-83.ebr3.dallas1.level3.net (4.69.136.161) 71.891 ms
8 ae-3.ebr2.losangeles1.level3.net (4.69.132.77) 84.447 ms 83.995 ms 88.721 ms
9 ae-92-92.csw4.losangeles1.level3.net (4.69.137.30) 90.333 ms ae-62-62.csw1.losangeles1.level3.net (4.69.137.18) 93.753 ms 86.575 ms
10 ae-63-63.ebr3.losangeles1.level3.net (4.69.137.33) 92.643 ms 86.712 ms 89.831 ms
11 ae-2.ebr3.sanjose1.level3.net (4.69.132.9) 98.493 ms 87.967 ms 90.554 ms
12 ae-73-73.csw2.sanjose1.level3.net (4.69.134.230) 86.450 ms 98.589 ms 90.584 ms
13 ae-72-72.ebr2.sanjose1.level3.net (4.69.134.213) 91.232 ms 87.937 ms 86.614 ms
14 ae-1-6.bar2.sanfrancisco1.level3.net (4.69.140.153) 90.245 ms 87.902 ms 88.754 ms
15 ae-4-4.car2.sanfrancisco1.level3.net (4.69.133.157) 88.607 ms 88.995 ms 90.557 ms
16 linden-rese.car2.sanfrancisco1.level3.net (4.78.242.50) 88.722 ms 89.873 ms 88.160 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 *

///////////////

Hello katrine fredriksson,

Thank you for contacting Linden Lab Support regarding the issue that you have mentioned.

I would like to direct you to the developers forum, where you can post all the information about your Mac and the problem. It appears as though the developers are currently trying to resolve a very similar problem to the one you are having. The link is below and I would like you to post your information in there so the developers can look into the issue further.

The reason I am directing you to this link is because I do not see any problems with your system or why the problem you are having is happening.

https://jira.secondlife.com/browse/SVC-972

Regards,
Mark,
Linden Lab Support.

//////////

And so the result is that I am here. I hope there is a solution provided so I can determine whether or not I am going to continue in second life. Please feel free to contact me, I guess...somehow, since I can't do anything in SL.

[9:30] Stephani Honi: You are most welcome!
[9:33] Stephani Honi: If you would be so kind as to add your comments to the bug report to let other Mac users know the steps that you took to make this happen, I would be grateful, and other Mac users will be, just as you are.

Here's what I did to fix my problem.

First of all, my hardware is as follows:

2Wire router model 2700HGV-B plugged in via cable to the computer
iMac Core2Duo running Tiger

After reading Stephani Honi's post, I checked the Broadband Link Details on my router, and noted that the Primary and Secondary Domain name Servers were not the same as the one listed in the file /var/run/resolv.conf

So under System Preferences -> Network -> Show -> Built-In Ethernet, in the textbox beside DNS servers
I placed the 2 DNS servers in there that the router listed.

I downloaded the latest client and I can tp anywhere now. Previously I was getting around using the 1.18.3 Teleport hack one as listed above by cobb compton.

I am the furthest thing from a network guru, so I really can't comment on any long lasting effects this may have, but I know that I can now teleport with a high success rate.

Also, I contacted a fellow SL iMac user (macbook pro) using a wireless network with a 2Wire router and the same problem as me, except she uses Leopard. I walked her through the same steps I did, and now she can teleport with a very high success rate too.

The fix should be available as part of the upcoming 1.21 viewer series or soon thereafter.

Thanks for your patience and helpful additional information while we were tracking this down.

But cmonnnnnn ...... tell us what the fix is

A Heisenberg Uncertainty Principle of debugging maybe?

Not very happy.