secondlife / jira-archive

2 stars 0 forks source link

[BUG-8483] 10+ second delay logging in - authentication step #16085

Open sl-service-account opened 9 years ago

sl-service-account commented 9 years ago

Steps to Reproduce

When logging in there is a 10+ second delay in the authentication step. See portion of my secondlife.log file below.

Other information


2015-02-13T18:46:41Z INFO: LLProcess::kill: destructor killing SLPlugin.exe (2408)
2015-02-13T18:46:41Z INFO: LLCoros::generateDistinctName: LLCoros: launching coroutine LLLogin::Impl::login_
2015-02-13T18:46:41Z INFO: LLStartUp::setStartupState: Startup state changing from STATE_LOGIN_AUTH_INIT to STATE_LOGIN_CURL_UNSTUCK
2015-02-13T18:46:41Z INFO: LLStartUp::setStartupState: Startup state changing from STATE_LOGIN_CURL_UNSTUCK to STATE_LOGIN_PROCESS_RESPONSE
2015-02-13T18:46:51Z INFO: Poller::Poller: login_to_simulator request sent to https://login.agni.lindenlab.com/cgi-bin/login.cgi
2015-02-13T18:46:53Z INFO: LLReqID::stamp: stamp(!) leaving non-map response unmodified: ['https://login.agni.lindenlab.com/cgi-bin/login.cgi']
2015-02-13T18:46:54Z INFO: LLXMLRPCTransaction::transferRate: Buffer size:   158664 B
2015-02-13T18:46:54Z INFO: LLXMLRPCTransaction::transferRate: Transfer rate: 38.024 Kb/s
2015-02-13T18:46:54Z INFO: Poller::poll: login_to_simulator result from https://login.agni.lindenlab.com/cgi-bin/login.cgi: status Complete, errorcode OK ((done))
2015-02-13T18:46:54Z INFO: LLLoginInstance::handleLoginSuccess: LLLoginInstance::handleLoginSuccess
2015-02-13T18:46:54Z INFO: LLCoros::cleanup: LLCoros: cleaning up coroutine LLLogin::Impl::login_
Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-8483 | | Summary | 10+ second delay logging in - authentication step | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Calcite Serendipity (calcite.serendipity) | | Created at | 2015-02-13T18:52:08Z | | Updated at | 2015-02-17T18:19:20Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2015-02-13T17:49:15.352-0600', "Is there anything you'd like to add?": "{code}\r\n2015-02-13T18:46:41Z INFO: LLProcess::kill: destructor killing SLPlugin.exe (2408)\r\n2015-02-13T18:46:41Z INFO: LLCoros::generateDistinctName: LLCoros: launching coroutine LLLogin::Impl::login_\r\n2015-02-13T18:46:41Z INFO: LLStartUp::setStartupState: Startup state changing from STATE_LOGIN_AUTH_INIT to STATE_LOGIN_CURL_UNSTUCK\r\n2015-02-13T18:46:41Z INFO: LLStartUp::setStartupState: Startup state changing from STATE_LOGIN_CURL_UNSTUCK to STATE_LOGIN_PROCESS_RESPONSE\r\n2015-02-13T18:46:51Z INFO: Poller::Poller: login_to_simulator request sent to https://login.agni.lindenlab.com/cgi-bin/login.cgi\r\n2015-02-13T18:46:53Z INFO: LLReqID::stamp: stamp(!) leaving non-map response unmodified: ['https://login.agni.lindenlab.com/cgi-bin/login.cgi']\r\n2015-02-13T18:46:54Z INFO: LLXMLRPCTransaction::transferRate: Buffer size: 158664 B\r\n2015-02-13T18:46:54Z INFO: LLXMLRPCTransaction::transferRate: Transfer rate: 38.024 Kb/s\r\n2015-02-13T18:46:54Z INFO: Poller::poll: login_to_simulator result from https://login.agni.lindenlab.com/cgi-bin/login.cgi: status Complete, errorcode OK ((done))\r\n2015-02-13T18:46:54Z INFO: LLLoginInstance::handleLoginSuccess: LLLoginInstance::handleLoginSuccess\r\n2015-02-13T18:46:54Z INFO: LLCoros::cleanup: LLCoros: cleaning up coroutine LLLogin::Impl::login_\r\n{code}", 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': ' ', 'What were you doing when it happened?': 'When logging in there is a 10+ second delay in the authentication step. See portion of my secondlife.log file below.', 'What were you expecting to happen instead?': ' ', } ```
sl-service-account commented 9 years ago

Calcite Serendipity commented at 2015-02-13T23:41:43Z

Just for fun I logged in from my old XP system with almost no delay, so I guess something wonky is happening on my Windows 7 system:

STATE_LOGIN_AUTH_INIT to STATE_LOGIN_CURL_UNSTUCK
2015-02-13T23:36:25Z INFO: LLStartUp::setStartupState: Startup state changing from STATE_LOGIN_CURL_UNSTUCK to STATE_LOGIN_PROCESS_RESPONSE
2015-02-13T23:36:25Z INFO: LLReqID::stamp: stamp(!) leaving non-map response unmodified: ['https://login.agni.lindenlab.com/cgi-bin/login.cgi']
2015-02-13T23:36:25Z INFO: Poller::Poller: login_to_simulator request sent to https://login.agni.lindenlab.com/cgi-bin/login.cgi
2015-02-13T23:36:26Z INFO: LLProcess::kill:  killing SLPlugin.exe (3668)
2015-02-13T23:36:26Z INFO: LLProcess::kill: destructor killing SLPlugin.exe (3668)
2015-02-13T23:36:29Z INFO: LLXMLRPCTransaction::transferRate: Buffer size:   158623 B
2015-02-13T23:36:29Z INFO: LLXMLRPCTransaction::transferRate: Transfer rate: 34.24 Kb/s
2015-02-13T23:36:29Z INFO: Poller::poll: login_to_simulator result from https://login.agni.lindenlab.com/cgi-bin/login.cgi: status Complete, errorcode OK ((done))
2015-02-13T23:36:29Z INFO: LLLoginInstance::handleLoginSuccess: LLLoginInstance::handleLoginSuccess
2015-02-13T23:36:29Z INFO: LLCoros::cleanup: LLCoros: cleaning up coroutine LLLogin::Impl::login_
2015-02-13T23:36:29Z INFO: LLMessageTemplate::banUdp: Setting EnableSimulator to UDPBlackListed was UDPDeprecated
sl-service-account commented 9 years ago

Kyle Linden commented at 2015-02-13T23:49:15Z

Hello Calcite,

We need more information about your report. Do you believe this is unexpected behavior based on another viewers performance? Or, do you just believe 10 seconds is too long?

When filing a Jira please provide more details of your problem. Without this information your jira will be closed as Needs More information and will not be triaged. Please include: (!) Which version of the client(s) are you using? (This can be found in Help, About Second Life) (!) Your computer specs (from Help, About Second Life) (!) A description of the problem, explaining what you do / see / don't see, including any error messages displayed (!) Step by step Directions on how to reproduce your experience. (!) A screenshot of what you are seeing. Please press the Information Provided button when you have added the additional information.

Thanks!