OpenNMS
  1. OpenNMS
  2. NMS-1061

Status on HP Web Jetadmin/2.0.43 Server port 8000 problem

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Trivial Trivial
    • Resolution: Incomplete
    • Affects Version/s: 1.1.4
    • Fix Version/s: Unknown Release
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Environment:
      Operating System: Linux
      Platform: PC
    • Bugzilla Id:
      977

      Description

      I am seeing a node service be declared down that is up. Service is http-8000,
      which is an HP Web Jetadmin/2.0.43 Server. Telnet to the node:port 8000 and wget
      to the node:port work, as well as connecting with Firefox also is ok. Port 8000
      redirects you to 8443 but don't see why that should matter. This in the only
      device with mgmt port I have running on port 8000.

      poll: response= HTTP/1.0 401 Unauthorized
      is what is seen in pollers.log.

        Activity

        Hide
        Ted Kaczmarek added a comment -

        Seeing a failure on one machine with https as well. Service is fine, yet OpenNMS
        declaring it down. Below is last few lines of telnet to port 443 output.

        <br />
        <small>Apache/2.0.40 (Red Hat Linux)</small>
        </address>
        </dd>
        </dl>
        </body>
        </html>

        Connection closed by foreign host.

        This is snippet from pollers.log, all else looks ok.
        HttpsMonitor: IOException while polling address.

        I enabled snmp on the node and did a rescan and it had no affect on the https
        service.

        Show
        Ted Kaczmarek added a comment - Seeing a failure on one machine with https as well. Service is fine, yet OpenNMS declaring it down. Below is last few lines of telnet to port 443 output. <br /> <small>Apache/2.0.40 (Red Hat Linux)</small> </address> </dd> </dl> </body> </html> Connection closed by foreign host. This is snippet from pollers.log, all else looks ok. HttpsMonitor: IOException while polling address. I enabled snmp on the node and did a rescan and it had no affect on the https service.
        Hide
        Ted Kaczmarek added a comment -

        In testing cvs from early today(12/04/04) I killed an http daemon, OpenNMS
        declared https down, and stopped polling http.

        Show
        Ted Kaczmarek added a comment - In testing cvs from early today(12/04/04) I killed an http daemon, OpenNMS declared https down, and stopped polling http.
        Hide
        matt@opennms.org added a comment -

        The redirect causes the protocol to switch to HTTPS so this is not really a valid
        HTTP. If you like open an enhancement causing not to dicover http redirected in
        this was as HTTP service.

        Matt

        Show
        matt@opennms.org added a comment - The redirect causes the protocol to switch to HTTPS so this is not really a valid HTTP. If you like open an enhancement causing not to dicover http redirected in this was as HTTP service. Matt

          People

          • Assignee:
            OpenNMS Bug Mailing List
            Reporter:
            Ted Kaczmarek
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development