mikaku / Monitorix

Monitorix is a free, open source, lightweight system monitoring tool.
https://www.monitorix.org
GNU General Public License v2.0
1.12k stars 167 forks source link

BIND stop working #9

Closed supernrm closed 9 years ago

supernrm commented 11 years ago

After 15 min. of working stats from BIND, monitorix stop make graphs.

Fri Mar 29 17:59:00 2013 - main::ALRM_handler: bind_update(): Can't use string ("ANY") as a HASH ref while "strict refs" in use at /usr/lib/monitorix/bind.pm line 273.

Fri Mar 29 18:00:01 2013 - main::ALRM_handler: bind_update(): Can't use string ("ANY") as a HASH ref while "strict refs" in use at /usr/lib/monitorix/bind.pm line 273.

mikaku commented 11 years ago

Does this happened right after restarting BIND or something? Also, can you please pastebin the output of:

curl http://localhost:8053/
supernrm commented 11 years ago

No, BIND was working for maybe 15-20 min. Yesterday after you reply I restart BIND/Monitorix and everything was back to normal. Today suddenly this happen once again.

Mon Apr 1 18:45:54 2013 - Built-in HTTP server pid is '809870'. HTTPServer: You can connect to your server at http://localhost:8080/ Tue Apr 2 14:35:00 2013 - main::ALRM_handler: bind_update(): Can't use string ("ANY") as a HASH ref while "strict refs" in use at /usr/lib/monitorix/bind.pm line 273.

named -V BIND 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.4

Yes, CURL on localhost:8053 give full XML output with data. If you want I can send you this by mail (provate data, can't pastebin to public).

supernrm commented 11 years ago

And again ;) After 3h once again stop working.

Tue Apr 2 15:51:00 2013 - main::ALRM_handler: bind_update(): Can't use string ("ANY") as a HASH ref while "strict refs" in use at /usr/lib/monitorix/bind.pm line 273.

named restart / monitorix restart

working

and again 3h later... ;)

Tue Apr 2 18:11:00 2013 - main::ALRM_handler: bind_update(): Can't use string ("ANY") as a HASH ref while "strict refs" in use at /usr/lib/monitorix/bind.pm line 273.

mikaku commented 11 years ago

I have exactly the same version as yours (CentOS 6.4 here), and I haven't experienced any problem.

You could try one thing. Restart named and right after capture its stats with curl http://localhost:8053/ then wait until it stops working and capture again its stats. Finally make a diffto see which values changed or disappeared from the first output.

Perhaps this can give us some clue of what is happening there.

mikaku commented 11 years ago

FYI, I've experienced recently a similar error message in one of my servers, but in my case the bind graph continue working without any problems.

I'm still investigating the cause.

mikaku commented 9 years ago

I've not seen problems anymore and I'm unable to reproduce it, therefore I'll close this issue. Please, re-open it if the problems continue.