[lsst-dm-stack-users] Can't access https://lsst-web.ncsa.illinois.edu/mydb/

[Mike Freemon]

Hi Michael,

There are some anomalous authentication-related messages in the logs, 
but I don't have enough context to draw any conclusions.

Possibly related: The first challenge should be the browser popup 
window, for which the account is "lsst" and the well-known password. 
There are indications that on at least one occasion your first 
authentication attempt was with account "wmwv".  This attempt failed, 
which could be causing at least some of the symptoms you're describing, 
especially since many browsers provide the option of caching this 
userid/password and using it without a visual indication to the user.

If you see this happen again, please note the exact time and sequence of 
events.  If we can recreate it...

- Mike


On 1/9/2013 1:09 PM, Michael Wood-Vasey wrote:
> Hi Mike,
>
> Thank you for the quick response.
>
> On Jan 9, 2013, at 09:09 , Mike Freemon <mfreemon at illinois.edu> wrote:
>>
>> The system monitoring is not reporting any problems.  I just checked myself, and it seems to be working normally.
>>
>> What are the specific error messages/behaviors?
>
> I had been successfully using PHPAdmin last night to run queries through Firefox.  This morning I used the same active Firefox to try to connect to
>
> https://lsst-web.ncsa.illinois.edu/mydb/
>
> from new windows and never received a response.  This persisted through the hours of this morning.  I then tried with Safari and got the page
>
> https://lsst-web.ncsa.illinois.edu/mydb/
>
> to load.  I logged in and received an error.  I then restarted Firefox and went to
>
> https://lsst-web.ncsa.illinois.edu/mydb/
>
> I logged in by filling out my username and password and clicking "Go" and waited as the page asid it was contact the server and go the same login page back.  I then tried clicking "Go" again and it succeeded.  I believe this first-time fails, second-time works happened a few times yesterday, although I didn't take clear enough notes.
>
> It did not occur to me that there was some session information that would have been preserved in this connection (visiting other web pages with that same Firefox worked perfectly fine) and was perhaps waiting for my previous query to complete or something like that.
>
> Perhaps I'll go back to my standard non-web-based SQL clients that I understand better.
>
> Thanks,
> Michael
>