tucansam Posted April 28, 2020 Share Posted April 28, 2020 (edited) Docker and Plug-ins take about 5 mins to "check for updates" and then cannot establish comms with any host to grab software. Second time this has happened (first time resolved on its own, no idea). While troubleshooting I see this: -- root@ffs2:~# traceroute google.com traceroute to google.com (172.217.3.46), 30 hops max, 60 byte packets 1 192.168.0.1 (192.168.0.1) 0.397 ms 0.382 ms 0.373 ms 2 10.81.10.1 (10.81.10.1) 46.047 ms 43.021 ms 43.093 ms 3 104.200.151.1 (104.200.151.1) 43.355 ms 53.200 ms 43.501 ms 4 107.152.99.93 (107.152.99.93) 42.933 ms 43.095 ms 38.097 ms 5 ae1-205.cr0-phx1.ip4.gtt.net (216.221.157.145) 46.129 ms 52.688 ms 43.414 ms 6 ae11.cr4-lax2.ip4.gtt.net (89.149.140.77) 52.568 ms 54.918 ms 50.865 ms 7 as15169.cr4-lax2.ip4.gtt.net (216.221.156.186) 83.724 ms 87.279 ms 72.14.194.163 (72.14.194.163) 85.408 ms 8 108.170.247.243 (108.170.247.243) 83.773 ms 87.483 ms 88.058 ms 9 108.170.234.124 (108.170.234.124) 87.096 ms 108.170.230.135 (108.170.230.135) 82.408 ms 108.170.234.124 (108.170.234.124) 86.866 ms 10 172.253.71.26 (172.253.71.26) 75.172 ms 74.978 ms^C root@ffs2:~# nslookup google.com nslookup: error while loading shared libraries: libcrypto.so.1: cannot open shared object file: No such file or directory root@ffs2:~# nslookup nslookup: error while loading shared libraries: libcrypto.so.1: cannot open shared object file: No such file or directory root@ffs2:~# -- What the heck? Checking for updates to the OS doesn't work anymore either. But all of my dockers can do whatever they need to do, as far as dns and what-not goes. Edited April 28, 2020 by tucansam Quote Link to comment
tucansam Posted April 29, 2020 Author Share Posted April 29, 2020 Still a problem. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.