OpenNMS
  1. OpenNMS
  2. NMS-3736

Resource Graphs and custom time period error while refreshing

    Details

    • Type: Bug Bug
    • Status: Reopened
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.8.3, 1.12.5
    • Fix Version/s: Backlog
    • Component/s: Web UI - General
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Environment:
      Operating System: All
      Platform: PC
    • Bugzilla Id:
      3695

      Description

      Description of the issue :

      • On OpenNMS web page
      • I click on "Node List"
      • I click on a server with several monitored resources
      • I click on select all to get a page with all graphes
      • I click on submit
      • On time period I select custom
      • I click on Apply Custom Time Period
      • If I click again on Apply Custom Time Period or if I wait for auto-refreshing period then I got an "page not found" error like :

      ================================================================================
      Page Web inaccessible

      La page Web à l'adresse http://iint-opennms-test.itron.com:8980/opennms/graph/results.htm?resourceId=node%5B14%5D.nodeSnmp%5B%5D&resourceId=node%5B14%5D.interfaceSnmp%5BVMware_Accelerated_AMD_PCNet_Adapter_-005056a57815%5D&resourceId=node%5B14%5D.responseTime%5B192.168.49.77%5D&resourceId=node%5B14%5D.hrStorageIndex%5B1%5D&resourceId=node%5B14%5D.hrStorageIndex%5B2%5D&resourceId=node%5B14%5D.hrStorageIndex%5B3%5D&resourceId=node%5B14%5D.hrStorageIndex%5B4%5D&resourceId=node%5B14%5D.hrStorageIndex%5B8%5D&resourceId=node%5B14%5D.hrStorageIndex%5B9%5D&resourceId=node%5B14%5D.hrStorageIndex%5B5%5D&resourceId=node%5B14%5D.hrStorageIndex%5B7%5D&resourceId=node%5B14%5D.hrStorageIndex%5B6%5D&resourceId=node%5B14%5D.sinfNetInstance%5B25.77.83.32.84.67.80.32.76.111.111.112.98.97.99.107.32.105.110.116.101.114.102.97.99.101%5D&resourceId=node%5B14%5D.sinfNetInstance%5B36.86.77.119.97.114.101.32.65.99.99.101.108.101.114.97.116.101.100.32.65.77.68.32.80.67.78.101.116.32.65.100.97.112.116.101.114%5D&resourceId=node%5B14%5D.sinfCpuInstance%5B1.48%5D&resourceId=node%5B14%5D.sinfCpuInstance%5B1.49%5D&resourceId=node%5B14%5D.sinfCpuInstance%5B1.50%5D&resourceId=node%5B14%5D.sinfCpuInstance%5B1.51%5D&resourceId=node%5B14%5D.sinfCpuInstance%5B6.95.84.111.116.97.108%5D&resourceId=node%5B14%5D.sinfLDskInstance%5B2.67.58%5D&resourceId=node%5B14%5D.sinfLDskInstance%5B2.68.58%5D&resourceId=node%5B14%5D.sinfLDskInstance%5B2.69.58%5D&resourceId=node%5B14%5D.sinfLDskInstance%5B2.83.58%5D&resourceId=node%5B14%5D.sinfLDskInstance%5B2.90.58%5D&resourceId=node%5B14%5D.sinfLDskInstance%5B6.95.84.111.116.97.108%5D&reports=all&relativetime=custom&zoom=&startMonth=3&startDate=15&startYear=2010&startHour=4&endMonth=3&endDate=15&endYear=2010&endHour=6 est peut-être temporairement inaccessible ou a peut-être été redirigée de façon permanente vers une nouvelle adresse Web.

      Plus d'informations sur cette erreur
      Message d'erreur original ci-dessous

      Erreur 324 (net::ERR_EMPTY_RESPONSE) : Erreur inconnue

      ================================================================================

      If I select only one or two resource to graph there is no error.

      Should parameters be transmit using a POST method instead of a GET method in URL ?

        Activity

        Hide
        mannu added a comment -

        On 1.8.9 release this bug seems to be resolved.
        I have tested with different servers and resource graph reports without any issues.

        So I think you can successfully close this ticket.

        Show
        mannu added a comment - On 1.8.9 release this bug seems to be resolved. I have tested with different servers and resource graph reports without any issues. So I think you can successfully close this ticket.
        Hide
        David Hustace added a comment -

        Resolved per reporter.

        Show
        David Hustace added a comment - Resolved per reporter.
        Hide
        David Hustace added a comment -

        Closing per reporter.

        Show
        David Hustace added a comment - Closing per reporter.
        Hide
        mannu added a comment -

        On 1.8.12-1 release the bug is here. Select a lot of graph to display. Wait for autorefresh and I get a blank page without any log.

        The only things I catch within jetty.log are some lines when I display the page :

        2011-06-09 11:36:23,561 WARN [24605656@qtp-13386596-580] JRobinRrdStrategy: JRobin: Unrecognized graph argument:

        Maybe it is related to autorefresh blank page ?

        Show
        mannu added a comment - On 1.8.12-1 release the bug is here. Select a lot of graph to display. Wait for autorefresh and I get a blank page without any log. The only things I catch within jetty.log are some lines when I display the page : 2011-06-09 11:36:23,561 WARN [24605656@qtp-13386596-580] JRobinRrdStrategy: JRobin: Unrecognized graph argument: Maybe it is related to autorefresh blank page ?
        Hide
        Ron Roskens added a comment -

        The problem is the URL being requested ends up being larger than the header buffer size.

        I had this happen under 1.12.5:

        2014-08-13 17:03:53,156 WARN [qtp1619549734-76965415] HttpParser: HttpParser Full for /172.16.3.24:443 <--> /172.16.31.51:59919

        Show
        Ron Roskens added a comment - The problem is the URL being requested ends up being larger than the header buffer size. I had this happen under 1.12.5: 2014-08-13 17:03:53,156 WARN [qtp1619549734-76965415] HttpParser: HttpParser Full for /172.16.3.24:443 <--> /172.16.31.51:59919

          People

          • Assignee:
            Seth Leger
            Reporter:
            Emmanuel Thouraud
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:

              Development