[LOG - Info] Invalid tokens older than DATE

Server
,
1

Hello, I get allways following info-log. Can you tell me what this is?

Actual behaviour

{"reqId":"XX","remoteAddr":"","app":"no app in context","message":"Invalidating tokens older than 2016-07-28T02:45:01+00:00","level":1,"time":"2016-07-28T09:45:01+02:00","method":"--","url":"--","user":"--"}

Server configuration
Operating system: CentOS 7
Web server: Apache 2.4.6
Database: MariaDB 10.1.16
PHP version: 5.5.21
ownCloud version (see ownCloud admin page): 9.1.0
Updated from an older ownCloud or fresh install: -
ownCloud log (data/owncloud.log, see How to find webserver or OC logfile / enable php logfile):

{"reqId":"XX","remoteAddr":"","app":"no app in context","message":"Invalidating tokens older than 2016-07-28T01:45:02+00:00","level":1,"time":"2016-07-28T08:45:02+02:00","method":"--","url":"--","user":"--"}
{"reqId":"XX","remoteAddr":"","app":"no app in context","message":"Invalidating tokens older than 2016-07-28T02:00:01+00:00","level":1,"time":"2016-07-28T09:00:01+02:00","method":"--","url":"--","user":"--"}
{"reqId":"XX","remoteAddr":"","app":"no app in context","message":"Invalidating tokens older than 2016-07-28T02:15:01+00:00","level":1,"time":"2016-07-28T09:15:01+02:00","method":"--","url":"--","user":"--"}
{"reqId":"XX","remoteAddr":"","app":"no app in context","message":"Invalidating tokens older than 2016-07-28T02:30:02+00:00","level":1,"time":"2016-07-28T09:30:02+02:00","method":"--","url":"--","user":"--"}
{"reqId":"XX","remoteAddr":"","app":"no app in context","message":"Invalidating tokens older than 2016-07-28T02:45:01+00:00","level":1,"time":"2016-07-28T09:45:01+02:00","method":"--","url":"--","user":"--"}

Special configuration (external storage, external authentication, reverse proxy, server-side-encryption):

  • SELinux enforced

Integrity status for oC9+

No errors have been found.
2

Hi,

have a look at the documentation available here:

A log level of 1 means:

1: INFO: Activity such as user logins and file activities, plus warnings, errors, and fatal errors.

where the default loglevel is 2:

By default the log level is set to 2 (WARN).
2: WARN: Operations succeed, but with warnings of potential problems, plus errors and fatal errors.

Set it back to the default loglevel as described in the documentation above and the log entries are gone.

3

Okay, thanks - works fine!