Ad Widget

Collapse

Why does zabbix gui randomly time out. Should I file a bug report? Is this a known?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • vic
    Member
    • Jul 2013
    • 58

    #1

    Why does zabbix gui randomly time out. Should I file a bug report? Is this a known?

    I scoured the log files and there is nothing. I triple checked my install. I looked through bug reports and this forum. I have 2 separate installs doing exactly the same thing.

    Randomly the gui will time out requiring a browser refresh at which point the screen usually comes up right away. Sometimes it refuses and I need to go back to the root page and follow the links again. Something seems wrong but I cannot find any evidence of anything. I enabled all the caching which seems to have reduced the occurrence.

    It's not a capacity/speed/bandwidth issue. Sometimes the pages load right away. It's usually when I hit reload on my browser and somewhat random. Sometimes it's ok for a long time and sometimes it constantly times out on me. Very frustrating. I tried a bunch of things including optimizing MySQL and installing APC cache but nothing helps. I am almost 100% sure it's not due to any limitations being hit such as disk I/O, internet bandwidth, CPU, MySQL query speed, neither read nor write. There is plenty of memory. It's something else going on and it's driving me nuts because other than that Zabbix is working very well for me. Ive tried this on different browsers (Latest Chrome, IE10, latest firefox) and it's the same on all 3.

    Zabbix v2.0.6 installed using the RPM's on CentOS 6 32bit.
    Last edited by vic; 23-07-2013, 22:27.
  • vic
    Member
    • Jul 2013
    • 58

    #2
    As you can see the zabbix-server is basically idling so it's not a server load issue.
    Attached Files

    Comment

    • Alexei
      Founder, CEO
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Sep 2004
      • 5654

      #3
      You should tune Apache configuration parameters. Try to set "KeepAlive Off", I hope it will make a huge difference if you use default Apache settings currently.
      Alexei Vladishev
      Creator of Zabbix, Product manager
      New York | Tokyo | Riga
      My Twitter

      Comment

      • vic
        Member
        • Jul 2013
        • 58

        #4
        Code:
        KeepAlive Off
        is Apache default. At least for CentOS 6.

        I tried changing it to:
        Code:
        KeepAlive On
        and so far it has been working well. Not conclusive yet. The problem is very random and comes and goes but so far seems to be major improvement since I changed it.

        I have a new theory. I have MaxClient limited to 10 which is typically what I set it to for VPS to keep memory usage down and also protects from DDoS. I see that there are 9 opened with the server just idling. So maybe Zabbix creates a bunch of separate connections and I need to increase this?

        I've turned KeepAlive Off again and set MaxClient to 20. Will see what that does.
        Last edited by vic; 26-07-2013, 03:42.

        Comment

        • tchjts1
          Senior Member
          • May 2008
          • 1605

          #5
          So what is your experience with this now? Did setting KeepAlive to On seem to solve your issue?

          Comment

          • vic
            Member
            • Jul 2013
            • 58

            #6
            I still get time outs. It's a bit better but there are still long delays that sometimes result in time outs. There are no bottlenecks I can find anywhere.

            Comment

            • vic
              Member
              • Jul 2013
              • 58

              #7
              Just fyi for anyone else having this issue.

              Setting "KeepAlive On" in the apache configuration basically solved this for me. It defaults to Off (at least in CentOS) but most of the time it's better to set it to On. Especially if you have SSL enabled. I have seen this same thing in other web control panels and setting KeepAlive On always solves it.

              Comment

              • Palmertree
                Senior Member
                • Sep 2005
                • 746

                #8
                Most likely it is a memory limit or timeout in php. You can tell by looking at the appache logs.

                Usually it is memory. Increase php memory setting to something like this in /etc/php.ini:

                memory_limit = 1G

                Comment

                • vic
                  Member
                  • Jul 2013
                  • 58

                  #9
                  I will keep that suggestion in mind. However, I no longer have the problem because of KeepAlive On. So I don't think it was a memory problem in this case.

                  I don't see anything like that in the logs either. Memory_limit is set to 128MB which should be plenty.
                  Last edited by vic; 27-10-2014, 18:59.

                  Comment

                  Working...