@gubbins wrote:
Summary
Since upgrading to 3.9.0 we're seeing a lot of "Invalid or expired session" errors which are filling the logs.
Steps to reproduce
Server 3.9.0, Chrome clients - otherwise conditions not very clear.
Expected behavior
Clean logs! I wouldn't expect an error in the log under normal conditions.
Observed behavior
Example log excerpt, repeating approximately once every second:
[2017/05/23 19:54:47 AEST] [EROR] /api/v4/users/me: code=401 rid=i74txnzwgibpijajos13z9upwh uid= ip=10.130.64.120 Invalid or expired session, please login again. [details: UserRequired] [2017/05/23 19:54:47 AEST] [EROR] /api/v4/users/me/preferences: code=401 rid=w358uj96oj8ajgwa78skbdg3ir uid= ip=10.130.64.120 Invalid or expired session, please login again. [details: UserRequired] [2017/05/23 19:54:47 AEST] [EROR] /api/v4/users/me/teams: code=401 rid=17bizdxaifyqpkb964uwbe75zc uid= ip=10.130.64.120 Invalid or expired session, please login again. [details: UserRequired] [2017/05/23 19:54:47 AEST] [EROR] /api/v4/users/me/teams/members: code=401 rid=8qauua4kstrh9qgjke8zja6f1e uid= ip=10.130.64.120 Invalid or expired session, please login again. [details: UserRequired] [2017/05/23 19:54:48 AEST] [EROR] /api/v4/channels/members/me/view: code=401 rid=k611ma686fnmuyhbceg5traajw uid= ip=10.130.64.120 Invalid or expired session, please login again. [details: UserRequired]We are seeing this from various source IPs. It looks as if the browser client is in a refresh loop of some sort. Needless to say our logs are getting pretty large.
Posts: 1
Participants: 1