Stale results in webui until uchiwa process restarted

[madeddie]

Looks to be the same problem described in #438

OS: Ubuntu 16.04
Sensu: 0.26.3
Uchiwa: 0.20.1

In the events and clients overview pages the results are stale, directly visible from their ages (e.g. Issued times). When clicking through to the client and check details, the data is up-to-date.
This problem comes up after a while and at undetermined intervals.

Refreshing the browser doesn't work, only restarting the Uchiwa process fixes this.

The uchiwa.log shows the last "Updating the datacenter sensu" the stale time ago, i.e., the datacenter data isn't being updated.

Let me know if you want specific information.

[palourde]

Hi @madeddie

Thanks for reporting this issue. I'm unfortunately unable to reproduce it so I'll need some help. Could you modify the logvalue attribute to debug and restart Uchiwa?

Then, the next time you face this issue, simply provide us the last few lines from the Uchiwa log files. It should help us understand the current behavior you are facing.

Thanks!

[madeddie]

Hey, thanks for the quick reply. A coworker decided to rollback Uchiwa to an older version because of other problems (handlers not compatible with current silencing method), I'll set up a concurrent test setup and will get back to you.

[drichelson]

@madeddie What version did you roll back to? I'm also seeing this problem

[madeddie]

We're currently on 0.17.1. I'm still seeing "slow" results at times, harder to debug. Slow meaning it's usually not an hour or more behind, but more like 2 to 10 minutes or so.

Also setting up a shadow env with newer version uchiwa is proving difficult.

[jwatroba]

I ran into this issue and it turned out that my "refresh" setting had an insane 10000 because I had copied old config over where this had been the default. This default had since been changed to 10. Once I updated to 10, it worked fine.

[madeddie]

I'm afraid I don't have a production sensu setup under my control anymore, so this ticket can be closed AFAIAC.
I will close this issue myself in 3 weeks if it's not closed or requested to stay open beforehand.

[palourde]

I'll go ahead and close this issue. Do not hesitate to open a new issue if anyone face this problem again!