Whirly Fizzle commented at 2015-11-05T17:05:36Z

Maybe another case of BUG-10598?

Redness, did this problem start for you when your viewer updated to Second Life 3.8.7 (306796) Oct 27 2015 16:01:25 (Second Life Release) ?
Do you have the same problem on the default release viewer from https://secondlife.com/support/downloads/ ?

Other have reported frequesnt disconnects on teleport on the viewer version you are using, which is the HTTP update RC viewer from http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers.

Kyle Linden commented at 2015-11-05T20:07:07Z

Hello RednessV,

Please reproduce this problem and attach the SecondLife.log data from your viewer to this issue; see https://wiki.secondlife.com/wiki/Finding_Log_Files

Or if you prefer you may download the default release viewer to see if it resolves your problem entirely.

Thank you

RednessV commented at 2015-11-06T07:45:33Z

Yes this happen when i update the new version for the sl Viewer that day .....not sure SL viewer side already fix this issue???

Whirly Fizzle commented at 2015-11-06T13:58:48Z

If you look under Help -> About Second Life in the top menu bar of the viewer, if it still shows viewer version "Second Life 3.8.7 (306796) Oct 27 2015 16:01:25 (Second Life Release)", then this is the viewer version which several people have reported having teleport problems with.

If you are still having teleport problems on this viewer version, please can you reproduce getting disconnected after a teleport and then before relunching the viewer, zip up the logs folder & attach it to this issue using More Actions -> Attach files.
You will find the Logs folder here: C:\Users\ [USERNAME] \AppData\Roaming\SecondLife\logs.
This page gives more detailed instrctions for finding the logs folder: http://community.secondlife.com/t5/English-Knowledge-Base/How-to-report-a-bug/ta-p/733545#Section_.3

RednessV commented at 2015-11-07T03:37:51Z

Pls refer to the crash report log for this one...
Kindly revert asap.Thanks

RednessV commented at 2015-11-07T03:40:33Z

I have attach another Log report for your reference incase for wrongly attached just now.. both file Crash report log and Secondlife Log

Whirly Fizzle commented at 2015-11-08T11:58:47Z

Great! Thanks.

Secondlife.log
Session on Second Life Release 3.8.7.306796

• The crash reporter failed to connect at the start of the session.
  Attached crashreport.log also shows crash reports failed to send in - consistent "failed after 8 retries. Reason: Timeout was reached (Easy_28)"

• Login location: CATWA Store, Catwa Clip REGION_ID: e71f6467-b485-4c8d-92cf-079b6844f21b, pos: { 157343, 340624, 21.7915 }

• Login completed at T00:48:41.

• Note the excessive log spam for voice is because the login location has voice disabled - I filed this as a seperate issue at BUG-10645 (I can reproduce this at any voice disabled location & it's specific to CoreHTTP).

• Scratching my head at the end of the log - I'm not seeing a teleport start even logged. (?)
  Redness is still on Catwa Clip at line 31665, ~ 1 hr 20 mins after login there.
  Line 31953 is maybe when TP starts? (World map floater is closed here).
  There is no "LLAgent::teleportRequest: TeleportLocationRequest" logged though. Shouldn't this be logged for all kinds of teleports, even a double click TP?
  Voice spam logging changes right after that from:

  2015-11-07T02:09:13Z INFO:#Voice LLVivoxVoiceClient::parcelVoiceInfoRequestCoro: Voice URI is 
  2015-11-07T02:09:13Z INFO:#LLCoros LLCoros::cleanup: LLCoros: cleaning up coroutine LLVivoxVoiceClient::parcelVoiceInfoRequestCoro
  2015-11-07T02:09:13Z INFO:#LLCoros LLCoros::generateDistinctName: LLCoros: launching coroutine LLVivoxVoiceClient::parcelVoiceInfoRequestCoro

  to actually say "No voice on parcel"
  {code}
  2015-11-07T02:09:14Z INFO:#LLCoros LLCoros::generateDistinctName: LLCoros: launching coroutine LLVivoxVoiceClient::parcelVoiceInfoRequestCoro
  2015-11-07T02:09:14Z WARNING:#CoreHttp LLCore::HttpPolicy::stageAfterCompletion: HTTP request 58DA0DA8 failed after 0 retries. Reason: Not Found (Http_404)
  2015-11-07T02:09:14Z WARNING: LLCoreHttpUtil::HttpCoroHandler::onCompleted:

Error<Http_404> cannot access url 'https://sim10583.agni.lindenlab.com:12043/cap/7ffc97e0-c9d6-fc5c-1467-48ad1372cc94' because Not Found

2015-11-07T02:09:14Z INFO: LLSDXMLParser::Impl::parse: LLSDXMLParser::Impl::parse: XML_STATUS_ERROR parsing:Not Found
2015-11-07T02:09:14Z WARNING: LLCoreHttpUtil::HttpCoroHandler::onCompleted: Returned body=
Not Found
2015-11-07T02:09:14Z WARNING:#Voice LLVivoxVoiceClient::parcelVoiceInfoRequestCoro: No voice on parcel

* "No voice on parcel" logging repeats for 14 seconds & then...
Line 32097

2015-11-07T02:09:28Z INFO:#Mesh LLMeshRepository::metricsUpdate: EventMarker {'fetches':i0,'reason':'Mesh Download Quiescent','scope':'Teleport','start':r4901.282287,'stop':r4901.282287,'sys_cpu':r0.000000,'teleports':i2,'user_cpu':r0.000000}

Must have been a teleport now - "teleports':i2" ?
Double click TP's do count as a teleport in that counter (just checked that).

* Viewer disconnects ~ 30 seconds later while Redness is still on Catwa Clip region.

2015-11-07T02:10:04Z WARNING: LLWorld::removeRegion: Disabling region Catwa Clip that agent is in!
2015-11-07T02:10:04Z WARNING: LLToastAlertPanel::LLToastAlertPanel: Alert: Darn. You have been logged out of Second Life
You have been disconnected from the region you were in.
{code}

Whirly Fizzle commented at 2015-11-08T12:02:05Z

Redness, if you install the default release viewer from https://secondlife.com/support/downloads/, does this fix the teleport problem?

Saeros Linden commented at 2017-07-07T00:35:37Z

Our apologies, it appears this jira has been a victim of a spammer. We're cleaning up the offending comments, sorry for the mess!