Argo Tunnel Requires GLIBC 2.14

bug

#1

Hi there,
One of my sites went down today and it appears that CloudflareD is not coming back up. It was running previously on this exact system, but now it is complaining of a missing dependency: glibc 2.14

[[email protected] log]# tail /var/log/cloudflared.err
panic: close of closed channel

goroutine 13516395 [running]:
code.cfops.it/tun/cftunnel/origin.ServeTunnelLoop.func1(0xc420c4a420, 0xc420426180)
        /cfsetup_build/.GOPATH/src/code.cfops.it/tun/cftunnel/origin/tunnel.go:153 +0x4c
created by code.cfops.it/tun/cftunnel/origin.ServeTunnelLoop
        /cfsetup_build/.GOPATH/src/code.cfops.it/tun/cftunnel/origin/tunnel.go:151 +0x1ce
/usr/local/bin/cloudflared: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /usr/local/bin/cloudflared)
/usr/local/bin/cloudflared: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /usr/local/bin/cloudflared)
/usr/local/bin/cloudflared: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /usr/local/bin/cloudflared)

The tunnel failed after several “connection reset by peer” errors

ESC[31mERROESC[0m[1630075] Unable to dial edge                           ESC[31merrorESC[0m="DialContext error: dial tcp 198.41.192.227:7844: i/o timeout"
ESC[36mINFOESC[0m[1630075] Retrying in 16s seconds
ESC[31mERROESC[0m[1630080] Unable to dial edge                           ESC[31merrorESC[0m="DialContext error: dial tcp 198.41.192.167:7844: i/o timeout"
ESC[36mINFOESC[0m[1630080] Retrying in 16s seconds
ESC[31mERROESC[0m[1630106] Unable to dial edge                           ESC[31merrorESC[0m="DialContext error: dial tcp 198.41.192.227:7844: i/o timeout"
ESC[33mWARNESC[0m[1630106] Tunnel disconnected due to error              ESC[33merrorESC[0m="DialContext error: dial tcp 198.41.192.227:7844: i/o timeout"
ESC[31mERROESC[0m[1630111] Unable to dial edge                           ESC[31merrorESC[0m="DialContext error: dial tcp 198.41.192.167:7844: i/o timeout"

Then it gave up and refuses to start without a dependency it’s never asked for before. Any thoughts that don’t include a wipe and move to CentOS 7?

CentOS 6.9 x64 min

Thanks,
Mike


EDIT:
I’ve downloaded glibc from the gnu ftp, built and installed it. Still can’t launch it. Cloudflared commands work, but starting it as a service fails with the glibc error.


#2

I’ve updated the $PATH to include the compiled glibc 2.14 install. Now I’m seeing this:

[[email protected] bin]# service cloudflared start
INFO[0000] Applied configuration from /etc/cloudflared/config.yml
INFO[0000] Build info: {GoOS:linux GoVersion:go1.9.3 GoArch:amd64}
INFO[0000] Version 2018.7.3
INFO[0000] Flags map[origincert:/etc/cloudflared/cert.pem url:https://access.chaplain.co:443 hostname:access.chaplain.co]
INFO[0000] cloudflared will not automatically update when run from the shell. To enable auto-updates, run cloudflared as a service: https://developers.cloudflare.com/argo-tunnel/reference/service/
INFO[0000] Starting metrics server                       addr="127.0.0.1:33031"
ERRO[0000] Error validating url                          error="Specified origin urls using both --url and argument. Decide which one you want, I can only support one."

#3

Here’s what I’ve figured out. If I run it as a service, it will not run. If I run it as a command and then disown the process, it’s fine. I wouldn’t consider this “fixed” as it will require repeated manual intervention, but it seems to be working until CF comes up with a solution.


#4

Is there any feedback on this issue? I’d like to continue using this product, but it appears that maybe my OS is no longer supported despite CF not noting that it’s no longer supported.