Cases

net.cgoLookupIP Causes Segmentation Violation

Phenomenon

When using unix sock source, Loggie crashes after startup, and there are the following logs:

  1. fatal error: unexpected signal during runtime execution
  2. [signal SIGSEGV: segmentation violation code=0x1 addr=0x47 pc=0x7f59b4528360]
  4. runtime stack:
  5. runtime.throw({0x213b1a1, 0x7f59b423b640})
  6.     /usr/local/go/src/runtime/panic.go:1198 +0x71
  7. runtime.sigpanic()
  8.     /usr/local/go/src/runtime/signal_unix.go:719 +0x396
  10. goroutine 86 [syscall]:
  11. runtime.cgocall(0x1a39d30, 0xc000510d90)
  12.     /usr/local/go/src/runtime/cgocall.go:156 +0x5c fp=0xc000510d68 sp=0xc000510d30 pc=0x40565c
  13. net._C2func_getaddrinfo(0xc00030bc40, 0x0, 0xc000724fc0, 0xc0005bd990)
  14.     _cgo_gotypes.go:91 +0x56 fp=0xc000510d90 sp=0xc000510d68 pc=0x5c7bb6
  15. net.cgoLookupIPCNAME.func1({0xc00030bc40, 0xc0004d29c0, 0x4}, 0xc00030bb80, 0xc000510e50)
  16.     /usr/local/go/src/net/cgo_unix.go:163 +0x9f fp=0xc000510de8 sp=0xc000510d90 pc=0x5c98ff
  17. net.cgoLookupIPCNAME({0x20f751c, 0x3}, {0xc00030bb80, 0xc00022b5e0})
  18.     /usr/local/go/src/net/cgo_unix.go:163 +0x16d fp=0xc000510f38 sp=0xc000510de8 pc=0x5c914d
  19. net.cgoIPLookup(0x358aed0, {0x20f751c, 0xc00030bbc0}, {0xc00030bb80, 0xc000510fb8})
  20.     /usr/local/go/src/net/cgo_unix.go:220 +0x3b fp=0xc000510fa8 sp=0xc000510f38 pc=0x5c99bb
  21. net.cgoLookupIP·dwrap·25()
  22.     /usr/local/go/src/net/cgo_unix.go:230 +0x36 fp=0xc000510fe0 sp=0xc000510fa8 pc=0x5c9e36
  23. runtime.goexit()
  24.     /usr/local/go/src/runtime/asm_amd64.s:1581 +0x1 fp=0xc000510fe8 sp=0xc000510fe0 pc=0x46ae81
  25. created by net.cgoLookupIP
  26.     /usr/local/go/src/net/cgo_unix.go:230 +0x125

Reason

For specific reasons, please refer to: go net。

  1. Name Resolution
  3. The method for resolving domain names, whether indirectly with functions like Dial
  4. or directly with functions like LookupHost and LookupAddr, varies by operating system.
  6. On Unix systems, the resolver has two options for resolving names.
  7. It can use a pure Go resolver that sends DNS requests directly to the servers
  8. listed in /etc/resolv.conf, or it can use a cgo-based resolver that calls C
  9. library routines such as getaddrinfo and getnameinfo.
  11. By default the pure Go resolver is used, because a blocked DNS request consumes
  12. only a goroutine, while a blocked C call consumes an operating system thread.
  13. When cgo is available, the cgo-based resolver is used instead under a variety of
  14. conditions: on systems that do not let programs make direct DNS requests (OS X),
  15. when the LOCALDOMAIN environment variable is present (even if empty),
  16. when the RES_OPTIONS or HOSTALIASES environment variable is non-empty,
  17. when the ASR_CONFIG environment variable is non-empty (OpenBSD only),
  18. when /etc/resolv.conf or /etc/nsswitch.conf specify the use of features that the
  19. Go resolver does not implement, and when the name being looked up ends in .local
  20. or is an mDNS name.
  22. The resolver decision can be overridden by setting the netdns value of the
  23. GODEBUG environment variable (see package runtime) to go or cgo, as in:
  25.     export GODEBUG=netdns=go    # force pure Go resolver
  26.     export GODEBUG=netdns=cgo   # force cgo resolver
  28. The decision can also be forced while building the Go source tree
  29. by setting the netgo or netcgo build tag.

Solution

Add environment variables to the Loggie deployment script:

  1.   env:
  2.     - name: GODEBUG
  3.       value: netdns=go