"Auth Error: login token expired" every 5 seconds

I see this message every 5 seconds in one.log.
Any idea how to prevent this ?

`Fri Feb 26 12:03:21 2016 [Z0][AuM][E]: Auth Error: login token expired
Fri Feb 26 12:03:21 2016 [Z0][ReM][D]: Req:6112 UID:-1 ImageInfo invoked , 667
Fri Feb 26 12:03:21 2016 [Z0][ReM][E]: Req:6112 UID:- ImageInfo result FAILURE [ImageInfo] User couldn’t be authenticated, aborting call.
Fri Feb 26 12:03:26 2016 [Z0][AuM][D]: Message received: LOG I 134281 Command execution fail: /var/lib/one/remotes/auth/server_cipher/authenticate serveradmin f2ac4017d7cd1723820022b8a26a6752f686f332 ****

Fri Feb 26 12:03:26 2016 [Z0][AuM][I]: Command execution fail: /var/lib/one/remotes/auth/server_cipher/authenticate serveradmin f2ac4017d7cd1723820022b8a26a6752f686f332 ****
Fri Feb 26 12:03:26 2016 [Z0][AuM][D]: Message received: LOG E 134281 login token expired

Fri Feb 26 12:03:26 2016 [Z0][AuM][I]: login token expired
Fri Feb 26 12:03:26 2016 [Z0][AuM][D]: Message received: LOG I 134281 ExitCode: 255

Fri Feb 26 12:03:26 2016 [Z0][AuM][I]: ExitCode: 255
Fri Feb 26 12:03:26 2016 [Z0][AuM][D]: Message received: AUTHENTICATE FAILURE 134281 login token expired

Fri Feb 26 12:03:26 2016 [Z0][AuM][E]: Auth Error: login token expired
Fri Feb 26 12:03:26 2016 [Z0][ReM][D]: Req:144 UID:-1 ImageInfo invoked , 667
Fri Feb 26 12:03:26 2016 [Z0][ReM][E]: Req:144 UID:- ImageInfo result FAILURE [ImageInfo] User couldn’t be authenticated, aborting call.`

Could you check if the system clock is synced in the machine that are running oned and sunstone-server?

Tokens are generated using the EXPIRE_DELTA and EXPIRE_MARGIN defined in the CloudAuth.rb file, did you modify this values?

Hello Daniel,
I haven’t modified those values.
The machine that runs oned and sunstone-server is same, and its system clock is ok.
What should I check ?

The error message I’m getting seems to originate from:

How can I force the creation of a new login token ?
Is there a file and/or a database entry that I can delete so that it is recreated automatically ?

The token is generated every time you do a request through Sunstone, the only thing that changes over time is the expiration time that is injected and changed if necessary in this part of the code:

I don’t know what could be the problem, if I were you I would add some kind of logging in the following 2 parts of the code and check the values of the expire variables: