Uchiwa consistently dies if refresh param is less than 5 seconds

[Savemech]

error log:
==> /var/log/uchiwa.err <==
net/http.HandlerFunc.ServeHTTP(0xc8200c7ba0, 0x7f0c99db8a68, 0xc82011c410, 0xc8200e2e00)
/usr/local/go/src/net/http/server.go:1618 +0x3a
net/http.(_ServeMux).ServeHTTP(0xc820066ae0, 0x7f0c99db8a68, 0xc82011c410, 0xc8200e2e00)
/usr/local/go/src/net/http/server.go:1910 +0x17d
net/http.serverHandler.ServeHTTP(0xc82008e280, 0x7f0c99db8a68, 0xc82011c410, 0xc8200e2e00)
/usr/local/go/src/net/http/server.go:2081 +0x19e
net/http.(_conn).serve(0xc82014cb00)
/usr/local/go/src/net/http/server.go:1472 +0xf2e
created by net/http.(*Server).Serve
/usr/local/go/src/net/http/server.go:2137 +0x44e

[Savemech]

my bad,
Debian GNU/Linux 8
3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux
using this package: uchiwa_0.17.1-1_amd64.deb

[josephholsten]

@Savemech did you get this resolved?

[Savemech]

@josephholsten sort of, i just did
crontab:

*  *    * * *   root    systemctl restart uchiwa.service

and this is barely helps, uchiwa still goes unstable some time
i'm thinking of implementation some of keepalived + vip to keep my uchiwa instances up and dont show broken info.
I'm also noticed, when uchiwa about to broke, its some symbols appear in random places like

action create&12

idk maybe its chrome bug to render that in way like this, maybe it's uchiwa itself but few minutes later uchiwa just stop responding and dies completely

[palourde]

Hi,

I believe this issue could be related and fixed with the 0.18 release: #543

Could you let us know if you still face this problem with the newer versions?

Thanks

[Savemech]

Yes of course, i will update my uchiwa installations soon and post some results.
Thank you guys, you're awesome!

[Savemech]

Bug seems fixed, with refresh ratio in 1 sec works stable for 2 days in row with 16MB memory footprint with 24 clients and ~50 checks

[palourde]

\o/