Ad Widget

Collapse

1.8 web interface

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • terry.hull
    Junior Member
    • Dec 2009
    • 7

    #1

    1.8 web interface

    I installed 1.8 from source last night on a CentOS 5.4 machine. I have found some strange things with the web interface. I don't know if what I'm seeing is wrong, or if I have a configuration problem.

    I have a single Linux server defined in addition to the Zabbix server. When I navigate to the server, I can see the host name, applications, items, triggers, and graphs link. When I click on the applications, triggers and graphs, I see the list. When I click on Items, the detail pane goes blank. There are over 100 items listed in parentheses, but the list area is blank. It seems the interface has a problem displaying large numbers of items. I can see the triggers, with about 60 entries, but not the items. Incidentally, when I look at the Windows servers, I can see the items, but it has only 23 items. Any clues? TIA.
  • terry.hull
    Junior Member
    • Dec 2009
    • 7

    #2
    [solved] 1.8 web interface

    Sorry for the stupid question. I solved it by increasing the php memory limit. I apologize for the form noise.

    Comment

    • Robert Wagnon
      Member
      • Jan 2008
      • 47

      #3
      Good question

      I don't think this was a stupid question. I assumed that the database upgrade script had silently failed and that I had a permanently damaged zabbix system.

      Some error indication would be nice.

      Thanks for your post, I would have been in bad shape!

      Comment

      • dotelpenguin
        Junior Member
        • Feb 2009
        • 14

        #4
        I agree, had similar problem which I tracked down quickly, but I can see how this could have easily caused other people a plethora of grief.

        Comment

        • gpmidi
          Member
          • Aug 2009
          • 62

          #5
          Same

          I had this problem too. I was able to fix it quickly as Apache logs the error in it's error_log file (by default).

          Comment

          Working...