proxy seconds behind! (Time not synchronized or server down?) spamming console

[TheMagBum]

i have this error since some times: 13:23:35 [SEVERE] [RedisBungee] proxy-1_ZPu1cV is 15971 seconds behind! (Time not synchronized or server down?) the server is offline and i will that it is offline

[ghost]

what do you mean by "the server is offline and i will that it is offline"?

[TheMagBum]

i have turn off the server, but the error come too

[ghost]

have you turned off the server nicely, with "end" command?

[TheMagBum]

No, I think the server was frozen and I terminated it

[ghost]

in that case it is normal, you need to stop it nicely in order to not have these warnings

[TheMagBum]

The problem is that I am using Redis with a cloud and I can't recreate the serverid

[ghost]

I see, let's see what @ham1255 thinks about this

[ham1255]

Never seen this error before, make sure your system time is right + and shutdown every bungee cord nicely

[ham1255]

and also you could ignore this since this isn't harmful i think btw will check code if there some changes needed.

[mattmalec]

I've seen this before with my Kubernetes infrastructure. It occurs when RedisBungee doesn't have the chance to remove itself from the "heartbeats" key in the Redis server (i.e. not safely shutting down the server, a SIGKILL, etc.)

A heartbeat object is JSON formatted and looks like: { "server-id-1": "last-heartbeat-time", "server-id-2": "last-heartbeat-time", "server-id-3": "last-heartbeat-time" } and etc.

You could fix this by either removing the key of the offending server from that object or by completely deleting the heartbeats key from Redis. You should restart all your proxies for data consistency if you remove the heartbeat key entirely, but it's not necessary if you remove the offending server from the object.

As a more permanent fix, a config option that removes any server that have missed the heartbeat after X amount of seconds would be nice to see. Let me know if you'd like me to PR that addition.

Hope this helps. Thanks!

[ham1255]

Thanks for info!

[ham1255]

I've seen this before with my Kubernetes infrastructure. It occurs when RedisBungee doesn't have the chance to remove itself from the "heartbeats" key in the Redis server (i.e. not safely shutting down the server, a SIGKILL, etc.)

A heartbeat object is JSON formatted and looks like:

`{

"server-id-1": "last-heartbeat-time",

"server-id-2": "last-heartbeat-time",

"server-id-3": "last-heartbeat-time"

}`

and etc.

You could fix this by either removing the key of the offending server from that object or by completely deleting the heartbeats key from Redis. You should restart all your proxies for data consistency if you remove the heartbeat key entirely, but it's not necessary if you remove the offending server from the object.

As a more permanent fix, a config option that removes any server that have missed the heartbeat after X amount of seconds would be nice to see. Let me know if you'd like me to PR that addition.

Hope this helps. Thanks!

But this kind of thing is harmless but if it causing issues please tell me!

[ham1255]

And also when that error happens what i can do is delete the server

[mattmalec]

RedisBungee updates its heartbeat every 3 seconds to ensure the Redis server hasn't just randomly died. If its unable to update the heartbeat, it could be that a server has lost its connection to Redis, or simply that the server wasn't shutdown safely.

[ham1255]

i made pull request try it

2