
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Describe the bug
用的是socks5 在idea里面启动服务可以,podIp是通的,但是在用openfeign调用其他服务是就无法识别host了:
ERROR UnknownHostException: user-service.default.svc.cluster.local: nodename nor servname provided, or not known (5658ms)
如果用vpn的话是没问题的(kt 0.0.12没问题, kt0.0.13-rc11 vpn的话exchange到本地超时不通,podIp等能访问)。但是windows只能用socks5. 这是属于不能使用dns么?有没有其他解决方案?
9月24更新:
上面那个错误是因为我在bootstrap.yml中设置了spring.cloud.kubernetes.ribbon.mode=service导致的,如果设置mode为pod就不会. 用了 0.0.13-rc11版本后,vpn和socks5都很慢,还有经常不通的情况,换回0.0.12稳定版后就好了
Log
sudo ktctl -d -n default connect --method=socks5 --cidr 10.100.0.0/16 10.96.0.0/16
Password:
3:48PM INF Connect Start At 13384
3:48PM INF private Key generated
3:48PM INF public key generated
3:48PM INF successful create ssh config map kt-connect-public-key-umfci
3:48PM INF Client address 192.168.1.37
3:48PM DBG create shadow with debug mode
3:48PM INF shadow template is prepare ready.
3:48PM INF deploy shadow deployment kt-connect-daemon-umfci in namespace default
3:48PM INF pod label: kt=kt-connect-daemon-umfci
3:48PM INF pod: kt-connect-daemon-umfci-846c578bd4-pmxph is running,but not ready
3:48PM INF pod: kt-connect-daemon-umfci-846c578bd4-pmxph is running,but not ready
3:48PM INF pod: kt-connect-daemon-umfci-846c578bd4-pmxph is running,but not ready
3:48PM INF pod: kt-connect-daemon-umfci-846c578bd4-pmxph is running,but not ready
3:48PM INF Shadow pod: kt-connect-daemon-umfci-846c578bd4-pmxph is ready.
3:48PM DBG Child, os.Args = [ktctl -d -n default connect --method=socks5 --cidr 10.100.0.0/16 10.96.0.0/16]
3:48PM DBG Child, name = port-forward, cmd.Args = [kubectl --kubeconfig=/Users/zhangamin/.kube/config -n default port-forward kt-connect-daemon-umfci-846c578bd4-pmxph 2222:22]
Forwarding from 127.0.0.1:2222 -> 22
Forwarding from [::1]:2222 -> 22
3:48PM INF port-forward start at pid: 13387
3:48PM INF wait(5s) port-forward successful
3:48PM INF ==============================================================
3:48PM INF Start SOCKS5 Proxy Successful: export http_proxy=socks5://127.0.0.1:2223
3:48PM INF ==============================================================
Handling connection for 2222
2020/09/23 15:48:32 [ERR] socks: Unsupported SOCKS version: [67]
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: