Log in issue - UPDATE

Just wanted to give a brief post mortem of the issue that caused login issues for some members. As I've previously mentioned, we're in the process of a major code update. As part of this we're changing data centers (we don't have a choice here, FWIW - the DC we're in is being decommissioned). Moving before the code update will make that process much smoother. During this move, as small change in configuration caused authentication failures for a number of members. We've identified a fixed, rolled it out, and validated that it works. If you're still not able to log, please let us know. Once again, we apologize for the inconvenience. The main LQ site will be moved soon, which will necessitate a brief outage. We'll give notice before that happens.

--jeremy

Thank You Jeremy! I missed my daily LQ.

All the best with the work you're doing on this at the moment. Much appreciated.

An additional update. The site is now being served out of the new datacenter. If any members notice any issues or differences, please let me know ASAP. Thanks for the patience. With the move now out of the way, we'll move our focus to the pending code update. More on the soon.

--jeremy

Yeah, I'm having some login issues; basically what happens is that, I login and then I'm kicked off and am no longer logged in anymore. I've had to login a few times just to be able to login, if you know what I mean. I'm on a desktop machine, but I can't say that it isn't with Android either.

Also, I got the "You must have atleast 1 posts before being able to rate posts." message while trying to give rep through the "Did you find this helpful"'s "Yes" link to another member's post. But, the second time I tried, it worked. I clearly have a lot more than just 1 post to my name here.

I'm not able to reproduce this behavior. Are any other members seeing similar issues?

--jeremy

It just happened again (what I described before), I had to put in my username and password 3 times before I was actually logged in, I still got the "Thank you for logging in jsbjsb001" message and then the first and second times I tried to login, the page went straight back to it is when you ain't logged in - if that makes sense.

EDIT: I forgot to mention a few things; I'm not having the same trouble with any other sites as far as I know. And this time I logged in I didn't have the same issue, but did get the error in the attached screenshot the first time I tried editing this post. I'm using Firefox 60.3.0esr on CentOS 7.5 if it makes any difference.

Have you tried manually deleting all LQ-related cookies? It's possible one is corrupt and causing an issue.

--jeremy

I just tried logging in with Google Chrome that I have installed as a fallback, and I had no issues. I'd made sure I'd cleared the cookies in Chrome first before I loaded the site up. I didn't clear Firefox's cookies to see if I could recreate the issue - I couldn't. So far Firefox isn't giving me the same issues as before.

So I guess you were probably right. Although I always disable the browser history and what not as one of the first things I do after installing a distro that I'm going to use as my main system.

I'll post back if I see any more issues.

Thanks for your time and attention in the matter Jeremy. You do a good job.

In early December, I noticed that the time to load the opening page after logging in increased substantially, taking perhaps a minute or more. After the opening page has loaded, further response time is good. Could this be related to the new software or data center? Or should I be looking at my own installation? I normally use Chromium 71 but I get the same problem with Firefox 60esr, both under Ubuntu 18.04 and Debian 9.6. I didn't find other posts on this issue.

Originally Posted by flshope In early December, I noticed that the time to load the opening page after logging in increased substantially, taking perhaps a minute or more. After the opening page has loaded, further response time is good. Could this be related to the new software or data center? Or should I be looking at my own installation? I normally use Chromium 71 but I get the same problem with Firefox 60esr, both under Ubuntu 18.04 and Debian 9.6. I didn't find other posts on this issue.

I'm not able to reproduce this issue (and have not gotten any other similar reports). Is it happening to any other members?

--jeremy

I have just observed that after logging in, it is the home page that is taking a long time to load. If I click on any other LQ tab (e.g., Forums) across the top of the screen, it loads immediately. If I switch away from Home after it finishes loading, say to Forums, and then come back to Home, it again takes minutes for Home to load.

I just started Chromium under Debian 9.6 from the command line and got the following error message:

/usr/bin/chromium
Gtk-Message: Failed to load module "canberra-gtk-module"
[5028:5028:1221/190110.709024:ERROR:x11_input_method_context_impl_gtk.cc(149)] Not implemented reached in virtual void libgtkui::X11InputMethodContextImplGtk::SetSurroundingText(const string16&, const gfx::Range&)
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[5028:5059:1221/190111.674241:ERROR:nss_util.cc(748)] After loading Root Certs, loaded==false: NSS error code: -8018

If I run the command 'apt list --all-versions|grep canberra-gtk-module', I get

libcanberra-gtk-module/stable 0.30-3 amd64

which means there is a related lib file available but not installed. Could this be relevant here?

Starting firefox from the command line does not generate any error messages, but Home still loads slowly.

I have just observed that after logging in, it is the home page that is taking a long time to load. If I click on any other LQ tab (e.g., Forums) across the top of the screen, it loads immediately. If I switch away from Home after it finishes loading, say to Forums, and then come back to Home, it again takes minutes for Home to load.

Today (12/23/18, ~1530 CST), I am not observing the LQ Home page slow-load problem with any browser under any OS, or on any of the machines that I have routine access to. I will monitor and report back any change.