Page MenuHomeMiraheze

Loss of session data
Closed, InvalidPublic

Description

Getting loss of session data error on Meta. I've seen this reported by multiple users in the past days

Event Timeline

MacFan4000 raised the priority of this task from High to Unbreak Now!.Nov 21 2016, 16:51

Affects the site so raising priority

John lowered the priority of this task from Unbreak Now! to High.Nov 21 2016, 16:53
John added a project: Upstream.

Upstream, we can't have this an UBN unfortunately as we have zero control over the issue or the fix and it's wholly reliant upon upstream's priority which will presumably be low.

Got the first logs:

[session] SessionBackend "[ID]" metadata dirty due to provider metadata change (Array([CentralAuthSource] => Local) => Array([CentralAuthSource] => CentralAuth)): call_user_func_array/MediaWiki\Session\SessionBackend->MediaWiki\Session\{closure}/MediaWiki\Session\SessionBackend->save/CentralAuthSessionProvider->persistSession/MediaWiki\Session\SessionBackend->setProviderMetadata
[session] SessionBackend "[ID]" metadata dirty due to provider metadata change ( => Array([CentralAuthSource] => Local)): MediaWiki\Session\SessionBackend->persist/MediaWiki\Session\SessionBackend->autosave/MediaWiki\Session\SessionBackend->save/CentralAuthSessionProvider->persistSession/MediaWiki\Session\SessionBackend->setProviderMetadata
[session] SessionBackend "[ID]" metadata dirty due to provider metadata change (Array([CentralAuthSource] => Local) => Array([CentralAuthSource] => CentralAuth)): call_user_func_array/MediaWiki\Session\SessionBackend->MediaWiki\Session\{closure}/MediaWiki\Session\SessionBackend->save/CentralAuthSessionProvider->persistSession/MediaWiki\Session\SessionBackend->setProviderMetadata
John lowered the priority of this task from High to Normal.Dec 11 2016, 18:53

Blocked upstream, going to lower priority so we can see what our priorities are clearly.

I've not experienced this lately.

Can anyone say otherwise?

@John I still get errors with "hijacking" and 504s and "Central login" stuff

@Reception123 but that's not what this task is about!

@John Well apparently on the WMF Phabricator they said it could be related to that so that's why I mentioned it. I've indeed not been getting the exact error recently though

That's good enough for me.

Hijacking is a different upstream issue. 504s and Central Login stuff is db2 read-write-speed related.