Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-17637

Artifactory is filling the log with useless messages when Xray is down

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: High
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Xray
    • Labels:
      None

      Description

      When Xray is down, pings to /api/v1/system/ping are answered with

      <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
       <html><head>
       <title>503 Service Unavailable</title>
       </head><body>
       <h1>Service Unavailable</h1>
       <p>The server is temporarily unable to service your
       request due to maintenance downtime or capacity
       problems. Please try again later.</p>
       </body></html>
      

      and Artifactory fills the logs with

      2018-10-15 10:27:40,270 [pool-31-thread-1] [WARN ] (o.j.x.c.h.XrayHeartbeatImpl:173) - Cannot retrieve xray server status due to: Failed to parse Xray Error message: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at [Source: (org.apache.http.conn.EofSensorInputStream); line: 1, column: 2]

      which can lead to DOS when logging to disk. Artifactory should be better at interpreting the state Xray is in and perhaps log only when ping stops working and starts working again? Alternatively, repetitive messages could be accumulated a la syslog?

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            gintas Gintas Grigelionis
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated: