GRAFANA log me out

1

Hello,
for 2 days, grafana disconnects from time to time my session and puts me on the login page. Grafana 6.0.0-1 (upgrade from 5.4.3 - 2 weeks ago) runs on a VM linux redhat 7 with 4GB of RAM and 2 cpu, we are 2 developers, our dashboards are quite loaded, 50 panels per screen, refreshed every 30 seconds. Authentification standard grafana :
;cookie_secure = false
Here is an extract of the logs:

t=2019-03-13T01:13:34+0100 lvl=info msg=“Request Completed” logger=context userId=1 orgId=1 uname=admin method=POST path=/api/tsdb/query status=400 remote_addr=172.21.2.171 time_ms=5062 size=623 referer=“http://susis-d-01:3000/d/8rNQjXjik/lab_app_critique?orgId=1&refresh=30s&kiosk”
t=2019-03-13T01:13:34+0100 lvl=info msg=“Request Completed” logger=context userId=1 orgId=1 uname=admin method=POST path=/api/tsdb/query status=400 remote_addr=172.21.2.171 time_ms=5062 size=641 referer=“http://susis-d-01:3000/d/8rNQjXjik/lab_app_critique?orgId=1&refresh=30s&kiosk”
t=2019-03-13T02:48:27+0100 lvl=info msg=“cleanup of expired auth tokens done” logger=auth count=1
t=2019-03-13T07:28:43+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=GET path=/ status=302 remote_addr=172.21.2.171 time_ms=0 size=29 referer=
t=2019-03-13T09:14:00+0100 lvl=info msg=“Request Completed” logger=context userId=1 orgId=1 uname=admin method=GET path=/login status=302 remote_addr=172.21.2.24 time_ms=14 size=24 referer=
t=2019-03-13T11:18:45+0100 lvl=info msg=“Request Completed” logger=context userId=1 orgId=1 uname=admin method=POST path=/api/dashboards/db/ status=412 remote_addr=172.21.2.171 time_ms=37 size=88 referer=“http://susis-d-01:3000/d/8rNQjXjik/lab_app_critique?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”
t=2019-03-13T11:33:47+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=POST path=/api/tsdb/query status=401 remote_addr=172.21.2.171 time_ms=7 size=26 referer=“http://susis-d-01:3000/d/2_YWXXjiz/applications-critiques?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”
t=2019-03-13T11:33:47+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=POST path=/api/tsdb/query status=401 remote_addr=172.21.2.171 time_ms=0 size=26 referer=“http://susis-d-01:3000/d/2_YWXXjiz/applications-critiques?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”
t=2019-03-13T11:33:47+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=POST path=/api/tsdb/query status=401 remote_addr=172.21.2.171 time_ms=0 size=26 referer=“http://susis-d-01:3000/d/2_YWXXjiz/applications-critiques?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”
t=2019-03-13T11:33:47+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=POST path=/api/tsdb/query status=401 remote_addr=172.21.2.171 time_ms=0 size=26 referer=“http://susis-d-01:3000/d/2_YWXXjiz/applications-critiques?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”
t=2019-03-13T11:33:47+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=POST path=/api/tsdb/query status=401 remote_addr=172.21.2.171 time_ms=0 size=26 referer=“http://susis-d-01:3000/d/2_YWXXjiz/applications-critiques?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”
t=2019-03-13T11:33:47+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=POST path=/api/tsdb/query status=401 remote_addr=172.21.2.171 time_ms=0 size=26 referer=“http://susis-d-01:3000/d/2_YWXXjiz/applications-critiques?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”
t=2019-03-13T11:33:47+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=POST path=/api/tsdb/query status=401 remote_addr=172.21.2.171 time_ms=0 size=26 referer=“http://susis-d-01:3000/d/2_YWXXjiz/applications-critiques?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”
t=2019-03-13T11:33:47+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=POST path=/api/tsdb/query status=401 remote_addr=172.21.2.171 time_ms=0 size=26 referer=“http://susis-d-01:3000/d/2_YWXXjiz/applications-critiques?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”
t=2019-03-13T11:33:47+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=POST path=/api/tsdb/query status=401 remote_addr=172.21.2.171 time_ms=0 size=26 referer=“http://susis-d-01:3000/d/2_YWXXjiz/applications-critiques?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”
t=2019-03-13T11:33:47+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=POST path=/api/tsdb/query status=401 remote_addr=172.21.2.171 time_ms=0 size=26 referer=“http://susis-d-01:3000/d/2_YWXXjiz/applications-critiques?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”
t=2019-03-13T11:33:47+0100 lvl=info msg=“Request Completed” logger=context userId=0 orgId=0 uname= method=POST path=/api/tsdb/query status=401 remote_addr=172.21.2.171 time_ms=0 size=26 referer=“http://susis-d-01:3000/d/2_YWXXjiz/applications-critiques?orgId=1”
t=2019-03-13T11:33:47+0100 lvl=eror msg=“failed to look up user based on cookie” logger=context error=“user token not found”

2

Do you have a persistent session store?
http://docs.grafana.org/installation/configuration/#session

The default is local filesystem, but if you run Docker in a container, then the data/sessions directory is probably volatile and sessions are flushed when the instance is restarted.

3

Hello,

graphana.ini :
;provider_config = sessions

Grafana has been installed with the following command:

wget https://…rpm
sudo yum localinstall grafana-x.x.x.x86_64.rpm

No docker.