name=syncthingĭEBU 13:03:27 INFO: QUIC listener (:22000) starting name=syncthingĭEBU 13:03:27 INFO: GUI and API listening on 127.0.0.1:8384 name=syncthingĭEBU 13:03:27 INFO: Access the GUI via the following URL: name=syncthingĭEBU 13:03:27 INFO: My name is "" name=syncthing name=syncthingĭEBU 13:03:27 INFO: Overall send rate is unlimited, receive rate is unlimited name=syncthingĭEBU 13:03:27 INFO: Loading HTTPS certificate: open /Users/tc/.ksync/syncthing/https-cert.pem: no such file or directory name=syncthingĭEBU 13:03:27 INFO: Creating new HTTPS certificate name=syncthingĭEBU 13:03:27 INFO: TCP listener (:22000) starting name=syncthingĭEBU 4 13:03:27 connection doesn't allow setting of receive buffer size. name=syncthingĭEBU 13:03:26 INFO: Compacting database after migration. name=syncthingĭEBU 13:03:26 INFO: Running database migration 15. name=syncthingĭEBU 13:03:26 INFO: Running database migration 14. name=syncthingĭEBU 13:03:26 INFO: Running database migration 13. name=syncthingĭEBU 13:03:26 INFO: Running database migration 11. name=syncthingĭEBU 13:03:26 INFO: Running database migration 10. name=syncthingĭEBU 13:03:26 INFO: Running database migration 9. name=syncthingĭEBU 13:03:26 INFO: Running database migration 7. name=syncthingĭEBU 13:03:26 INFO: Running database migration 6. name=syncthingĭEBU 13:03:26 INFO: Running database migration 5. name=syncthingĭEBU 13:03:26 INFO: Running database migration 3. name=syncthingĭEBU 13:03:26 INFO: Running database migration 2. name=syncthingĭEBU 13:03:26 INFO: Hashing performance is 357.71 MB/s name=syncthingĭEBU 13:03:26 INFO: Running database migration 1. name=syncthingĭEBU 13:03:25 INFO: Archiving a copy of old config file format at: /Users/tc/.ksync/syncthing/26 name=syncthingĭEBU 13:03:25 INFO: My ID: name=syncthingĭEBU RESTY 4 13:03:25 ERROR Get " dial tcp :8384: connect: connection refused, Attempt 2ĭEBU tunnel running LocalPort=64393 Namespace=kube-system Out="Forwarding from 127.0.0.1:64393 -> 40321\nForwarding from :64393 -> 40321\n" PodName=ksync-9bdlz RemotePort=40321ĭEBU 13:03:26 INFO: Single thread SHA256 performance is 428 MB/s using minio/sha256-simd (380 MB/s using crypto/sha256). INFO listening bind=127.0.0.1 port=40322ĭEBU RESTY 4 13:03:24 ERROR Get " dial tcp :8384: connect: connection refused, Attempt 1ĭEBU found pod name Namespace=kube-system RadarPort=40321 SyncthingAPI=8384 SyncthingListener=22000 nodeName= podName=ksync-9bdlzĭEBU found pod nodeName= podName=ksync-9bdlz status=RunningĭEBU starting tunnel LocalPort=64393 Namespace=kube-system Out= PodName=ksync-9bdlz RemotePort=40321 url=" DEBU 13:03:25 INFO: syncthing v1.13.1 "Fermium Flea" (go1.15.7 darwin-amd64) 14:15:21 UTC name=syncthingĭEBU 13:03:25 INFO: Generating ECDSA key and certificate for syncthing. INFO new pod detected pod=archt-345-poc-kafka-distributed-cache-user-5d69f76c6d-lm2hv spec=archt-345-poc-kafka-distributed-cache-cache-userĭEBU added service ID=4fc34fc34491d34f41c64e1a1d9f95778057b027f8551f18029155f27b115981 Name=archt-345-poc-kafka-distributed-cache-user NodeName= PodName=archt-345-poc-kafka-distributed-cache-user-5d69f76c6d-lm2hvĭEBU checking to see if radar is ready nodeName=ĭEBU starting syncthing args="" cmd=/Users/tc/.ksync/bin/syncthing Here's the debug log of the watch process: DEBU initializing kubernetes client context=ĭEBU kubernetes client created host=" DEBU watching for updates ContainerName= LocalPath=/Users/tc/code/redox-services/services/archt-345-poc-kafka-distributed-cache LocalReadOnly=true Name=archt-345-poc-kafka-distributed-cache-app Namespace=tc Pod= Reload=true RemotePath=/opt/nodejs RemoteReadOnly=false Selector=""ĭEBU watching for updates ContainerName= LocalPath=/Users/tc/code/redox-services/services/archt-345-poc-kafka-distributed-cache LocalReadOnly=true Name=archt-345-poc-kafka-distributed-cache-cache-user Namespace=tc Pod= Reload=true RemotePath=/opt/nodejs RemoteReadOnly=false Selector=""ĭEBU new event deleted=false name=archt-345-poc-kafka-distributed-cache-user-5d69f76c6d-lm2hv status=Running type=ADDED TLDR the ksync watch process is stuck logging updating due to connection resets and the pod never syncs. However, I have one engineer (so far) facing this. It's a shared cluster and most of my colleagues are using ksync with no problems. We are running an EKS cluster initialized by ksync. We've had quite a bit of success with ksync, but this one is stymieing us.
0 Comments
Leave a Reply. |