Redisbungee displaying wrong playercounts

[Tibet-dev]

Hi, I've noticed, that Redisbungee starts to display wrong playercounts after a certain amount of time. And this wrong playercount won't change at all until i reboot my Waterfall (Bungeecord fork) server.

I've already read the FAQ and i can say that:

• My configuration should be correct.
• The Redis server is running. It currently has no password for testing purpuses but i don't think it causes the error.
• All my Bungeecords are running.
• The Time in all my Bungeecord machines should be alright as they currently are all on the same machine.
• Every Bungeecord has the same version of Redisbungee.
• I'm running the latest version of Redisbungee

There are no logs

I've attached my Config (I changed the IP adress in this example for some obvious reasons). I always use the IPV4 adress of my Redis server

It's named "config.txt". Don't worry I named it config.yml on the Bungeecord

Sorry for my bad english if any of this grammar dosen't makes sence ;)

config.txt

[ham1255]

I seen people sending me dms about this i am not sure what is going wrong.

[ham1255]

Do you have any screenshots?

[ham1255]

RedisBungee has integrity check task which handle incase of desync happens.

[Tibet-dev]

Do you have any screenshots?

It's a german server

[ham1255]

Just to make sure, is all redisbungees uses same redis instance?

[Tibet-dev]

Just made sure. They do. When I restart the weird proxy everything works until in a few hours a proxy (can be the same or a different one) decides to bug out.

What's interesting is that even if a proxy does not know the propper playercont it can display all online players with /glist showall

Is it possible that Multipaper or Playerbalancer can be the reason. I've already turned "redisbungee" on in playerbalancer though

[ham1255]

So glist displays right stuff... hmmm i might need to lookup the motd code ( also check calculating count code too)

[ham1255]

MultiPaper cant cause these problems as redisbungee is proxy plugin

[ham1255]

could you try setting password to your redis instance? then apply it to your redisbungee config

[Tibet-dev]

I'll try

[ham1255]

Any updates?

[Tibet-dev]

I've been running it for a few days now. Since then it never did happen again. Thanks! I'll keep you informed if anything odd happens.

[ham1255]

I've been running it for a few days now. Since then it never did happen again. Thanks! I'll keep you informed if anything odd happens.

Thanks for letting me know everything is solved will be closing the issue now, But whats weird to me that people did actually run to problems with redisbungee with other strange issues without a password is set and the fix was setting the password, is it me or there is weird pattern going on here? like redis itself is misbehaving with no password i set