Page MenuHomePhabricator

Some users get unwantedly logged out on it.wikivoyage
Closed, DeclinedPublic

Description

Several users are experiencing this issue but I wasn't able to identify a specific pattern for this problem.

To give you an idea of the issue I'll paste some user logs:

1

  • (diff | cron) . . Romprezzagno‎; 22:38 . . (+3)‎ . . ‎LINO CORRADI (Discussione | contributi | blocca)‎
  • (diff | cron) . . Romprezzagno‎; 22:25 . . (-78)‎ . . ‎87.14.145.188 (Discussione | blocca)‎
  • (diff | cron) . . Romprezzagno‎; 22:14 . . (+3)‎ . . ‎LINO CORRADI (Discussione | contributi | blocca)‎ (→‎Come arrivare)

2

  • (diff | cron) . . ! Vicenza‎; 15:25 . . (+180)‎ . . ‎Marcok (Discussione | contributi | blocca)‎ (→‎Punti di informazione: aggiunat link documento)
  • (diff | cron) . . ! Vicenza‎; 15:21 . . (+175)‎ . . ‎188.152.34.81 (Discussione | blocca)‎ (→‎Ville palladiane: formattaz.)
  • (diff | cron) . . ! Vicenza‎; 14:47 . . (+149)‎ . . ‎Marcok (Discussione | contributi | blocca)‎ (→‎Quando andare)

One thing that I can say (talking with those users) is that the browser it's not relevant because the problem occurs both with Chrome, Safari, Firefox...

The issue can be replicated although it may take minutes/hours.

Please let me know because it's quite annoying.


Version: wmf-deployment
Severity: major
URL: http://it.wikivoyage.org/
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=49708
https://bugzilla.wikimedia.org/show_bug.cgi?id=47843

Details

Reference
bz48646

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:19 AM
bzimport set Reference to bz48646.
bzimport added a subscriber: Unknown Object (MLST).

I've forgetten to add that this issue happens for sure in it:voy.
I can't state anything about the other wikis.

swalling wrote:

This is unlikely to be related to userlogin and signup components, if they successfully logged in and then were logged out mysteriously. Are these users getting a session expiration error? Do they accept cookies?

Hi Steven,
I can speak for myself because I'm logged out as well.
I don't get any session error, that's why like the users above it happens that I save my edits as an anonymous ID.

Through the chrome console I've looked and compared the it.wikivoyage.org cookie (that is correctly enabled) and I haven't noticed any particular differences.

If you think that can help I can copy and paste its content.

Andyrom75: When this happens, are you logged in automatically on the next edit? or instead when it logs you out, you have to manually log in again (going to Special:Userlogin)?

Jesús,
Normally I have open 1 instance of Chrome with multiple tabs. Most of them in it:voy, some of them in en/de:voy and it/en:w.

One tab is in editing while the others just browsing.
I know if I have been logged out during the saving of the page.

When it happens I just log in again manually, otherwise I just keep the browser open for several days.

Usually it log me out no more than once per day, but I remember one occasion (when I was trying IE & Chrome together) that it logged me out from Chrome 3/4 times within 10 minutes.

Have I completely answer to your question?

I don't know if it's of any help, but I'll put on the table.
I've just changed the wireless network and, although everything is still normally works, in the cookie I've found 4 new keys:
3 from from "toolserver.org" Domain:

  1. PHPSESSID
  2. _pk_id.1.8248
  3. _pk_ref.1.8248

and the last one from ".toolserver.org" Domain ....note the starting "."

  1. xssc-sso-id

The value specified in xssc-sso-id is the same of .wikivoyage.org and .wikimedia.org. This is fine because is a Single Sign On session.

Let me know if I can provide you more info.

The 4 keys above explained has disappeared from the cookie after sveral minutes.

Which browser(s) and version(s) is this about?

Personally I use Chorme last version (frequently updated by the embedded feature). But, as stated in my first post, I've ask to other user about their browser, and they use different ones, so I've assumed that the browser it's not relevant.

I've just made a quick comparison of the cookies in three different moments:

  1. after the forced logout from [http://it.wikivoyage.org/wiki/Speciale:UltimeModifiche page]
  2. just after authentication in [http://it.wikivoyage.org/w/index.php?title=Speciale:Entra&action=submitlogin&type=login&returnto=Speciale:UltimeModifiche page]
  3. after login in the same [http://it.wikivoyage.org/wiki/Speciale:UltimeModifiche page]

In step 2, due to the SUL, I see cookies coming from many different wikis.
All the cookies in step 3 coming from it.wikivoyage.org plus 1 from .wikimedia.org.
The last one is xssc-sso-id. There's another xssc-sso-id that cames from .wikivoyage.org with an identical value (the session id).
Obviously all the cookies present in step 3 are the same of the ones in step 2.

A part from 4 toolserve cookies (mentioned few post ago), all the cookies in step 1 are the same of step 3. The differences consist the values of some of them. The list of those cookies are the followings:

  • centralauth_Session
  • itwikivoyage_session

Let me know if I can help you on debugging because this problem is a real pain in the "neck". Thanks.

Still can't reproduce. Is this still a problem recently?

I have to admit that recently this hasn't happen with the same frequency. It happens but it's quite rare.

PS
How can I see the list of the opened bug of mine?

Re "PS": There should be "Saved Searches > My Bugs" in the sidebar on the left.

In "Saved Searches > My Bugs" I can only see the pending bugs, but not the closed ones. How can I see them all?

(In reply to comment #14)

In "Saved Searches > My Bugs" I can only see the pending bugs, but not the
closed ones. How can I see them all?

Create a saved search - wait two more days and I'll have blogged about this:
http://blogs.gnome.org/aklapper/2013/07/12/bugzillatips-saved-searches/

Logout has not happened anymore. I think you can close the bug.

Thanks for the update, and sorry that we never found out the underlying issue. :-/

No problem... at least it works :-)
However, although I've read your link, I'm not still able to see my previous open bug :-(