We have a datacentre instance of JIRA with Crowd as the credential service. In the past 2 weeks we have started having a problem where the last login information is not being updated.
Checking the database shows that the db is being updated (e.g. updated_date is showing today for most users) but login.lastLoginMillis is not updating since the 17th Jan. The date here is the same for all users so it looks like something happened on the 17th that is impacting the update of this field.
Has anyone seen anything like this before and have any suggestions where to look?
I'm answering my own question here but I thought I should put it out there in case anyone else ever sees something similar.
As we had been having trouble with configuring users in JIRA we decided we should reboot crowd (has been running for 2 years without reboot). When we did this everything went to hell in a handbasket. Many could not log in to JIRA but those who still had a valid login token were ok.
After much head scratching and not a little panic I discovered that the user directory configuration in JIRA for connection to crowd was all blank so JIRA could not connect to crowd. This had been set up by a third party when our environment was built and we did not have the password so these are the steps I followed to fix it:
Suddenly everything was working again including the last login dates in JIRA.
I have no idea what caused this information to disappear from JIRA but it has clearly been missing for a while and JIRA was hobbling along despite this, including adding and removing users via crowd and syncing passwords. Not sure how it could be doing that but it all stopped working when we rebooted crowd.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event