syncthing errors and warning in htop.

i just came across this fails and warning due to syncthing. any body care to tell me what are these means ? and what can i do to stop all these error and warning from popping up ? does these thing slow my system ? i am using manjaro xfce.

lately my system is very slow, it is a lot slower than window 7 os that i used to run on this laptop. it takes a few seconds to run an app. even my tor browser stopped working… (this is the main reason why i looked into htop but found syncthing errors. )

This doesn’t look like htop, but systemd logs.

It seems there are no logs for syncthing so it’s hard to say what it’s doing.

Perhaps it’s scanning hence using up all the cpu, but you should be able to see that in the web ui.

I suggest you also check syncthings logs.

yes, not htop. my mistake.

i looked thru syncthing log:

it keeps failing with one device, it is my j6+ hp. but nothing wrong with my hp… everything works… is there anything i should be worry about ?

2020-08-15 12:49:16 Failed to exchange Hello messages with CEIVOCO-RZLEQTZ-GYHG2VF-PQPNMUH-RQOXRTS-FKE3K4A-GAU3OAS-MKCTDAQ at 192.168.0.2:54776-192.168.0.5:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256: read tcp 192.168.0.2:54776->192.168.0.5:22000: i/o timeout
2020-08-15 12:50:17 Failed to exchange Hello messages with CEIVOCO-RZLEQTZ-GYHG2VF-PQPNMUH-RQOXRTS-FKE3K4A-GAU3OAS-MKCTDAQ at 192.168.0.2:54980-192.168.0.5:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256: read tcp 192.168.0.2:54980->192.168.0.5:22000: i/o timeout
2020-08-15 12:51:17 Failed to exchange Hello messages with CEIVOCO-RZLEQTZ-GYHG2VF-PQPNMUH-RQOXRTS-FKE3K4A-GAU3OAS-MKCTDAQ at 192.168.0.2:55112-192.168.0.5:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256: read tcp 192.168.0.2:55112->192.168.0.5:22000: i/o timeout
2020-08-15 12:52:18 Failed to exchange Hello messages with CEIVOCO-RZLEQTZ-GYHG2VF-PQPNMUH-RQOXRTS-FKE3K4A-GAU3OAS-MKCTDAQ at 192.168.0.2:55188-192.168.0.5:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256: read tcp 192.168.0.2:55188->192.168.0.5:22000: i/o timeout
2020-08-15 12:53:18 Failed to exchange Hello messages with CEIVOCO-RZLEQTZ-GYHG2VF-PQPNMUH-RQOXRTS-FKE3K4A-GAU3OAS-MKCTDAQ at 192.168.0.2:55246-192.168.0.5:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256: read tcp 192.168.0.2:55246->192.168.0.5:22000: i/o timeout
2020-08-15 12:54:19 Failed to exchange Hello messages with CEIVOCO-RZLEQTZ-GYHG2VF-PQPNMUH-RQOXRTS-FKE3K4A-GAU3OAS-MKCTDAQ at 192.168.0.2:55338-192.168.0.5:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256: read tcp 192.168.0.2:55338->192.168.0.5:22000: i/o timeout
2020-08-15 12:55:19 Failed to exchange Hello messages with CEIVOCO-RZLEQTZ-GYHG2VF-PQPNMUH-RQOXRTS-FKE3K4A-GAU3OAS-MKCTDAQ at 192.168.0.2:55490-192.168.0.5:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256: read tcp 192.168.0.2:55490->192.168.0.5:22000: i/o timeout
2020-08-15 12:56:20 Failed to exchange Hello messages with CEIVOCO-RZLEQTZ-GYHG2VF-PQPNMUH-RQOXRTS-FKE3K4A-GAU3OAS-MKCTDAQ at 192.168.0.2:55616-192.168.0.5:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256: read tcp 192.168.0.2:55616->192.168.0.5:22000: i/o timeout
2020-08-15 12:57:01 Established secure connection to CEIVOCO-RZLEQTZ-GYHG2VF-PQPNMUH-RQOXRTS-FKE3K4A-GAU3OAS-MKCTDAQ at

this kind of constant sync seeking … isn’t it resource consuming ? i wish syncthing can have manual sync button so that when i need it to sync, it sync only that one time…

That’s called rsync. Perhaps you are using the wrong tool.

Anyways, from the logs it seems firewalls (or devices just being super slow) are getting in the way of these two devices connecting, because it fails to exchange a basic message in 10 seconds.

it is never a good idea to have multiple devices installed just for doing a type of job. i want auto sync as of syncthing capable of , especially from other subnet. but with a bit of manual control is always not bad. :slight_smile:

You can always manually pause one of your folders or one of the remotes. When you unpause it was automatically start syncing again.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.