Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 436291

Summary:

Inconsistent last login stamps

Product:

[ECD] Orion

Reporter:

John Arthorne <john.arthorne>

Component:

Server

Assignee:

Project Inbox <orion.server-inbox>

Status:

RESOLVED INVALID

QA Contact:

Severity:

normal

Priority:

CC:

ahunter.eclipse

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
Last login times on orionhub	none

Description John Arthorne

2014-05-31 11:30:25 EDT

I have been looking at the "last login" times for users on OrionHub. Most of the date stamps are ok, but there are  a large number that are in some strange/different format. It would be good to understand how this happened. If they are very old accounts that haven't logged in for years, then we can just consider removing them.

Comment 1 John Arthorne

2014-05-31 11:34:14 EDT

Created attachment 243752 [details]
Last login times on orionhub

Comment 2 John Arthorne

2014-05-31 11:41:44 EDT

The "good" times are in this range:

Sun Oct 21 03:03:05 EDT 2012  1350802985600
Fri May 30 19:33:09 EDT 2014  1401492789151

There are a bunch of times that are either above or below this range. If all those accounts indeed haven't logged in since October 2012 then they are candidates to prune out (maybe after a warning email if we have valid emails).

Comment 3 Anthony Hunter

2014-06-02 15:54:16 EDT

I have a copy of the legacy metadata from orionhub from January 29 and I sent it through both migrations. I only see users with either no lastlogintimestamp or a lastlogintimestamp starting with "13". 

I am not seeing how these lastlogintimestamp values were introduced.

I am going to continue working on Bug 429576 so we cleanup these accounts.

Comment 4 John Arthorne

2014-06-03 15:01:31 EDT

Sorry Anthony this was a bug in my script. I was extracting timestamp using this:

grep "lastlogin" | sed "s/[^0-9]//g"

However the grep output also includes the username, so if for example we had:

/jo/john999/user.json: "lastlogintimestamp" : "1353610111051"

My script extracted 9991353610111051

So this was just user error on my part.