search

coroot / coroot-node-agent

A Prometheus exporter based on eBPF that gathers comprehensive container metrics
https://coroot.com/docs/metrics/node-agent
Apache License 2.0
324 stars 59 forks source link

Rsync error after `vagrant up` #123

Open StLeoX opened 1 month ago

StLeoX commented 1 month ago

Version: coroot-node-agent-v1.21.4

Vagrant's error info:

Host path: /root/Source/obser/coroot-node-agent-v1.21.4/
Guest path: /tmp/src
Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 22 -o LogLevel=FATAL   -o ControlMaster=auto -o ControlPath=/tmp/vagrant-rsync-20240910-2986741-fuu8t5 -o ControlPersist=10m  -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i '/root/Source/obser/coroot-node-agent-v1.21.4/ebpftracer/.vagrant/machines/ubuntu2004/libvirt/private_key'" "--exclude" ".vagrant/" "/root/Source/obser/coroot-node-agent-v1.21.4/" "vagrant@192.168.121.122:/tmp/src"
Error: symlink has no referent: "/root/Source/obser/coroot-node-agent-v1.21.4/proc/fixtures/123/fd/5"
symlink has no referent: "/root/Source/obser/coroot-node-agent-v1.21.4/proc/fixtures/123/fd/4"
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1333) [sender=3.2.3]
StLeoX commented 1 month ago

I solved this by manually removing symlink: rm -r ./proc/fixtures/123/fd/.

StLeoX commented 1 month ago

Maybe we can tell Vagrant to skip those symlinks