Uploaded image for project: 'Couchbase Go SDK'
  1. Couchbase Go SDK
  2. GOCBC-323

Some log messages log the local address instead of remote address.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 1.4.0
    • 1.4.0
    • library
    • None
    • 1

    Description

      Some log messages are logging the local address instead of remote address of the server they are talking to.  I suspect a tracing change caused this (and maybe we should log both), but it makes it difficult to figure out whats going on from the logs.

      Example (note that the remote address is not 192.168.3.57):

      GOCB 15:04:28.929211 memdclient.go:77: Writing request. 192.168.3.57:65398 OP=0x1f. Opaque=1
      		 
      GOCB 15:04:28.929237 agentrouting.go:51: Fetching cluster client data
      		 
      GOCB 15:04:28.929301 memdclient.go:77: Writing request. 192.168.3.57:65397 OP=0x1f. Opaque=1
      		 
      GOCB 15:04:28.929822 agentrouting.go:51: Fetching cluster client data
      		 
      GOCB 15:04:28.929861 memdclient.go:77: Writing request. 192.168.3.57:65399 OP=0x1f. Opaque=1
      		 
      GOCB 15:04:28.929907 agentrouting.go:51: Fetching cluster client data
      		 
      GOCB 15:04:28.929935 memdclient.go:77: Writing request. 192.168.3.57:65400 OP=0x1f. Opaque=1
      		 
      GOCB 15:04:28.955459 memdclient.go:193: Resolving response OP=0x1f. Opaque=1

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            charles.dixon Charles Dixon
            brett19 Brett Lawson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty