Database to upgrade to v1.4.0-rc.7

AudriusButkevicius · February 26, 2020, 9:33am

It seems you are tripping over the fact you have two packages. I suggest you get rid of one.

Andy · February 26, 2020, 9:46am

If needed, I deinstall the Kastelo installation, because is only for testing. Is the above feedback not plausible so that this becomes necessary?

Andy · February 26, 2020, 10:21am

Additionally I deinstall the Kastelo version. I try now

root@Synology:/var/packages/syncthing/target/bin# STTRACE=db /var/packages/syncthing/target/bin/syncthing -reset-database 2>&1 | tee /volume1/PublicSharings/SyncthingExchange/Syncthing_log_Synology_DS1815.log

root@Synology:/var/packages/syncthing/target/bin#

and needs 3-4 seconds. The folder

/var/packages/syncthing/target/var/index-v0.14.0.db/

was not empty and the log file

/volume1/PublicSharings/SyncthingExchange/Syncthing_log_Synology_DS1815.log

is empty, 0kb

Andy · February 26, 2020, 10:25am

If I try

root@Synology:/var/packages/syncthing/target/bin# STTRACE=db syncthing -reset-database 2>&1 | tee /volume1/PublicSharings/SyncthingExchange/Syncthing_log_Synology_DS1815.log

-ash: syncthing: command not found

root@Synology:/var/packages/syncthing/target/bin# STTRACE=db ./syncthing -reset-database 2>&1 | tee /volume1/PublicSharings/SyncthingExchange/Syncthing_log_Synology_DS1815.log

root@Synology:/var/packages/syncthing/target/bin#

Second line is coming in max. 1 second. Same as yesterday

Andy · February 26, 2020, 10:28am

If I use

root@Synology:/var/packages/syncthing/target/bin# STTRACE=db ./syncthing 2>&1 | tee /volume1/PublicSharings/SyncthingExchange/Syncthing_log_Synology_DS1815.log

it means without “-reset-database” the result is as above

imsodin · February 26, 2020, 10:39am

Ideally you go back and read the various postings that explain to you several times why command not found happens so you understand it. Otherwise just stop experimenting and follow advice ad verbatim (aka copy and paste commands).

That’s expected.

Above you have several commands with different outcomes. What does happen - does it exit quickly without any output?

Andy · February 26, 2020, 10:43am

It was related to post 40, it means, also after deinstallation of the second Kastelo package, the result was the same like only stop it.

Moisie · February 26, 2020, 10:57am

Hello:

I’m writing this in the spirit of trying to be constructive - please take it as such.

Andy - it would be helpful if you could format your posts to make it easier for the rest of us to read. Whilst I appreciate English isn’t necessarily your first language, some basic formatting would help a lot:

Use the Preformatted Text button to make commands and file paths easier to read;
If you’re referring to a previous outcome, be explicit about which one you’re referring to. There’s a lot of tests and results in this thread!

Simon is trying his best to help you - but I can’t help but feel his life could be made a lot easier by making your posts easier to read.

Secondly: the original point of this thread was that there was a double count of files and folders. Seeing that there were two Syncthing instances running (somehow…), would that not explain it?

imsodin · February 26, 2020, 11:16am

For reference: This kind of problem

Run ps -e | grep syncthing please.

Andy · February 26, 2020, 11:26am

I understood your message and is also understandable. I also found the Preformatted Text button.

Regarding the first post regarding the doubled number of files and folders, I don’t have the impression that it has to do with the second Syncthing installation (Kastelo), since it was already installed with v1.3.3 and I also updated to v1.3.4.

This duplication occurred immediately with the update of the SynoComm. Installation of v1.3.4 to v1.4.0-rc.1 and the related database conversion.

The databases of both packages also are in separate locations:

/var/packages/syncthing/target/var/index-v0.14.0.db/

/volume1/syncthing-data/index-v0.14.0.db/

Andy · February 26, 2020, 11:33am

14555 ?        00:00:00 syncthing
17902 ?        00:00:00 syncthing
24899 ?        00:00:05 syncthing
31904 ?        00:51:23 syncthing

imsodin · February 26, 2020, 11:45am

So you already have two Syncthing instances running. Please shut down all of them before going back to

Andy · February 26, 2020, 12:36pm

Is done with post 43, also server was rebooted. I use now your second sequence with the follow result:

[start] 2020/02/26 13:24:43.199019 main.go:548: INFO: syncthing v1.4.0-rc.7 "Fermium Flea" (go1.13.8 linux-amd64) teamcity@build.syncthing.net 2020-02-22 16:49:23 UTC

[start] 2020/02/26 13:24:43.848871 main.go:621: INFO: Automatic upgrade is always enabled for candidate releases.

[FBDWL] 2020/02/26 13:24:43.849311 syncthing.go:151: INFO: My ID: FBDWLHxxx

[FBDWL] 2020/02/26 13:24:44.900121 sha256.go:87: INFO: Single thread SHA256 performance is 89 MB/s using minio/sha256-simd (66 MB/s using crypto/sha256).

[FBDWL] 2020/02/26 13:24:46.074051 syncthing.go:183: INFO: Hashing performance is 64.65 MB/s

[FBDWL] 2020/02/26 13:24:46.074587 model.go:273: INFO: Starting deadlock detector with 20m0s timeout

[FBDWL] 2020/02/26 13:24:46.074979 limiter.go:165: INFO: Overall send rate is unlimited, receive rate is unlimited

[FBDWL] 2020/02/26 13:24:46.075510 syncthing.go:271: INFO: Using discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCxxx

[FBDWL] 2020/02/26 13:24:46.076052 syncthing.go:271: INFO: Using discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCxxx

[FBDWL] 2020/02/26 13:24:46.076493 relay_listen.go:62: INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting

[FBDWL] 2020/02/26 13:24:46.076573 syncthing.go:271: INFO: Using discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCxxx

[FBDWL] 2020/02/26 13:24:46.076922 syncthing.go:305: INFO: Anonymous usage reporting is always enabled for candidate releases.

[FBDWL] 2020/02/26 13:24:46.079437 tcp_listen.go:55: INFO: Listen (BEP/tcp): listen tcp 0.0.0.0:22000: bind: address already in use

[FBDWL] 2020/02/26 13:24:46.079580 service.go:139: INFO: c.S.listenerSupervisor: Failed service 'tcp://0.0.0.0:22000' (1.000000 failures of 2.000000), restarting: true, error: "{tcp://0.0.0.0:22000 tcp://0.0.0.0:22000} returned unexpectedly", stacktrace: [unknown stack trace]

[FBDWL] 2020/02/26 13:24:46.079710 tcp_listen.go:55: INFO: Listen (BEP/tcp): listen tcp 0.0.0.0:22000: bind: address already in use

[FBDWL] 2020/02/26 13:24:46.079764 service.go:139: INFO: c.S.listenerSupervisor: Failed service 'tcp://0.0.0.0:22000' (1.999996 failures of 2.000000), restarting: true, error: "{tcp://0.0.0.0:22000 tcp://0.0.0.0:22000} returned unexpectedly", stacktrace: [unknown stack trace]

[FBDWL] 2020/02/26 13:24:46.079842 tcp_listen.go:55: INFO: Listen (BEP/tcp): listen tcp 0.0.0.0:22000: bind: address already in use

[FBDWL] 2020/02/26 13:24:46.079870 service.go:165: INFO: Entering the backoff state.

[FBDWL] 2020/02/26 13:24:46.079923 service.go:139: INFO: c.S.listenerSupervisor: Failed service 'tcp://0.0.0.0:22000' (2.999990 failures of 2.000000), restarting: false, error: "{tcp://0.0.0.0:22000 tcp://0.0.0.0:22000} returned unexpectedly", stacktrace: [unknown stack trace]

[FBDWL] 2020/02/26 13:24:46.084502 quic_listen.go:86: INFO: Listen (BEP/quic): listen udp 0.0.0.0:22000: bind: address already in use

[FBDWL] 2020/02/26 13:24:46.084615 service.go:165: INFO: Entering the backoff state.

[FBDWL] 2020/02/26 13:24:46.084660 service.go:139: INFO: c.S.listenerSupervisor: Failed service 'quic://0.0.0.0:22000' (3.999661 failures of 2.000000), restarting: false, error: "{quic://0.0.0.0:22000 quic://0.0.0.0:22000} returned unexpectedly", stacktrace: [unknown stack trace]

[FBDWL] 2020/02/26 13:24:46.186777 model.go:371: INFO: Ready to synchronize "Default Folder" (default) (sendreceive)

[FBDWL] 2020/02/26 13:24:46.188836 set.go:303: DEBUG: default WithPrefixedHaveTruncated(7777777-777777N-7777777-777777N-7777777-777777N-7777777-77777Q4, "")

[FBDWL] 2020/02/26 13:24:46.189099 folder.go:593: INFO: Completed initial scan of sendreceive folder "Default Folder" (default)

[FBDWL] 2020/02/26 13:24:46.189166 set.go:266: DEBUG: default WithNeed(7777777-777777N-7777777-777777N-7777777-777777N-7777777-77777Q4)

[FBDWL] 2020/02/26 13:24:46.278083 api.go:360: INFO: GUI and API listening on 127.0.0.1:54347

[FBDWL] 2020/02/26 13:24:46.278172 api.go:361: INFO: Access the GUI via the following URL: http://127.0.0.1:54347/

[FBDWL] 2020/02/26 13:24:46.278294 syncthing.go:332: INFO: My name is "Synology"

[FBDWL] 2020/02/26 13:24:46.278328 syncthing.go:340: WARNING: Syncthing should not run as a privileged or system user. Please consider using a normal user account.

[FBDWL] 2020/02/26 13:25:15.188400 static.go:68: INFO: Joined relay relay://212.25.15.128:22067

imsodin · February 26, 2020, 12:40pm

That shows that two Syncthing instances are running, regardless of what you uninstalled or how often you restarted. Please do:

Andy · February 26, 2020, 12:43pm

After uninstall of the Kastelo package and rebooting of server, I get now

10758 ?        00:32:19 syncthing
18403 ?        00:00:00 syncthing

So with the test was running one Syncthing instance.

imsodin · February 26, 2020, 12:51pm

I am switching to German in case language is a problem here, this conversation is anyway not helpful to a broader audience:

Alle laufenden Syncthing Instanzen müssen beendet werden, before du die neue Instanz mit STTRACE=db startest.

Andy · February 26, 2020, 1:05pm

Das ist sehr freundlich von Dir. Ich hoffe, Du kannst gut deutsch, sodass es Dir keine grosse Mühe macht.

Ich habe nun auch die noch vorhandene Instanz über den Synology DSM gestoppt. ps -e | grep syncthing ergibt

10799 pts/19 00:00:03 syncthing

Muss dieser Prozess auch gestoppt werden? Das wüsste ich allerdings nicht wie.

imsodin · February 26, 2020, 1:09pm

Bin Muttersprachler, keine Sorge.

Ja auch der. Klappt es mit killall syncthing oder wenn nicht, mit kill 10799?

Andy · February 26, 2020, 2:36pm

Jetzt sind keine Syncthing-Prozesse mehr am laufen. Ich führe das Kommando nun wieder aus und jetzt läuft es und die Logdatei wächst nun kontinuierlich.

In der Dokumentation steht allerdings nichts darüber, dass alle Syncthing-Prozesse beendet sein müssen.

Ich melde mich wieder, wenn die Sequenz komplett abgeschlossen ist. Hier einmal, was bislang gelaufen ist:

[start] 2020/02/26 15:21:59.215597 main.go:548: INFO: syncthing v1.4.0-rc.7 "Fermium Flea" (go1.13.8 linux-amd64) teamcity@build.syncthing.net 2020-02-22 16:49:23 UTC

[start] 2020/02/26 15:21:59.494050 main.go:621: INFO: Automatic upgrade is always enabled for candidate releases.

[FBDWL] 2020/02/26 15:21:59.495506 syncthing.go:151: INFO: My ID: FBDWLxxxxxxxxxxx

[FBDWL] 2020/02/26 15:22:00.514546 sha256.go:87: INFO: Single thread SHA256 performance is 91 MB/s using minio/sha256-simd (67 MB/s using crypto/sha256).

[FBDWL] 2020/02/26 15:22:01.573193 syncthing.go:183: INFO: Hashing performance is 77.26 MB/s

[FBDWL] 2020/02/26 15:22:01.574290 model.go:273: INFO: Starting deadlock detector with 20m0s timeout

[FBDWL] 2020/02/26 15:22:01.574546 limiter.go:165: INFO: Overall send rate is unlimited, receive rate is unlimited

[FBDWL] 2020/02/26 15:22:01.574826 model.go:371: INFO: Ready to synchronize "Default Folder" (default) (sendreceive)

[FBDWL] 2020/02/26 15:22:01.575302 tcp_listen.go:60: INFO: TCP listener ([::]:22000) starting

[FBDWL] 2020/02/26 15:22:01.575371 relay_listen.go:62: INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting

[FBDWL] 2020/02/26 15:22:01.576425 quic_listen.go:107: INFO: QUIC listener ([::]:22000) starting

[FBDWL] 2020/02/26 15:22:01.577340 set.go:303: DEBUG: default WithPrefixedHaveTruncated(7777777-777777N-7777777-777777N-7777777-777777N-7777777-77777Q4, "")

[FBDWL] 2020/02/26 15:22:01.577590 folder.go:593: INFO: Completed initial scan of sendreceive folder "Default Folder" (default)

[FBDWL] 2020/02/26 15:22:01.577660 set.go:266: DEBUG: default WithNeed(7777777-777777N-7777777-777777N-7777777-777777N-7777777-77777Q4)

[FBDWL] 2020/02/26 15:22:01.577881 syncthing.go:271: INFO: Using discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCxxxxxxxxxxxx

[FBDWL] 2020/02/26 15:22:01.578880 syncthing.go:271: INFO: Using discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCxxxxxxxxxx

[FBDWL] 2020/02/26 15:22:01.579031 syncthing.go:271: INFO: Using discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCxxxxxxxxxx

[FBDWL] 2020/02/26 15:22:01.585571 syncthing.go:305: INFO: Anonymous usage reporting is always enabled for candidate releases.

[FBDWL] 2020/02/26 15:22:01.626197 api.go:360: INFO: GUI and API listening on 127.0.0.1:54347

[FBDWL] 2020/02/26 15:22:01.626262 api.go:361: INFO: Access the GUI via the following URL: http://127.0.0.1:54347/

[FBDWL] 2020/02/26 15:22:01.628082 syncthing.go:332: INFO: My name is "Synology"

[FBDWL] 2020/02/26 15:22:01.628138 syncthing.go:340: WARNING: Syncthing should not run as a privileged or system user. Please consider using a normal user account.

[FBDWL] 2020/02/26 15:22:09.301162 service.go:261: INFO: Failed to exchange Hello messages with O6CDVWB-XSBPEYY-XHDD7HK-4SHCMK6-6SRXXNG-XLABHMR-KN5J5IK-MTWCFQC at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:505d:6416:c832:f0e4]:38096/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:505d:6416:c832:f0e4]:38096: write: connection reset by peer

[FBDWL] 2020/02/26 15:22:12.710075 structs.go:32: INFO: New NAT port mapping: external TCP address 84.182.184.176:39935 to local address 0.0.0.0:22000.

[FBDWL] 2020/02/26 15:22:12.833173 service.go:67: INFO: Detected 3 NAT services

[FBDWL] 2020/02/26 15:22:18.579372 service.go:261: INFO: Failed to exchange Hello messages with CIX3GDP-ZDS2VAF-P6XRBWZ-TV3PBV2-6V6UPH5-YYZU72N-6VVZIVJ-T26FAQA at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:211:32ff:fe43:8d55]:58762/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:211:32ff:fe43:8d55]:58762: write: connection reset by peer

[FBDWL] 2020/02/26 15:22:20.637234 quic_listen.go:55: INFO: quic://0.0.0.0:22000 detected NAT type: Port restricted NAT

[FBDWL] 2020/02/26 15:22:20.637290 quic_listen.go:74: INFO: quic://0.0.0.0:22000 resolved external address quic://84.182.184.176:62391 (via stun.syncthing.net:3478)

[FBDWL] 2020/02/26 15:22:28.800064 static.go:68: INFO: Joined relay relay://213.196.179.198:43396

[FBDWL] 2020/02/26 15:23:21.419209 service.go:261: INFO: Failed to exchange Hello messages with O6CDVWB-XSBPEYY-XHDD7HK-4SHCMK6-6SRXXNG-XLABHMR-KN5J5IK-MTWCFQC at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:505d:6416:c832:f0e4]:38146/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:505d:6416:c832:f0e4]:38146: write: connection reset by peer

[FBDWL] 2020/02/26 15:23:29.834840 service.go:261: INFO: Failed to exchange Hello messages with CIX3GDP-ZDS2VAF-P6XRBWZ-TV3PBV2-6V6UPH5-YYZU72N-6VVZIVJ-T26FAQA at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:211:32ff:fe43:8d55]:58780/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:211:32ff:fe43:8d55]:58780: write: connection reset by peer

[FBDWL] 2020/02/26 15:24:35.168064 service.go:261: INFO: Failed to exchange Hello messages with O6CDVWB-XSBPEYY-XHDD7HK-4SHCMK6-6SRXXNG-XLABHMR-KN5J5IK-MTWCFQC at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:505d:6416:c832:f0e4]:38176/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:505d:6416:c832:f0e4]:38176: write: connection reset by peer

[FBDWL] 2020/02/26 15:24:39.993877 service.go:261: INFO: Failed to exchange Hello messages with CIX3GDP-ZDS2VAF-P6XRBWZ-TV3PBV2-6V6UPH5-YYZU72N-6VVZIVJ-T26FAQA at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:211:32ff:fe43:8d55]:58788/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:211:32ff:fe43:8d55]:58788: write: connection reset by peer

[FBDWL] 2020/02/26 15:25:17.903507 service.go:261: INFO: Failed to exchange Hello messages with XT5D54B-OCNS4I5-IBI6YIF-6FNEXTC-3EEHH6E-YP3WAOI-3VNWRSU-HANRQA4 at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:9d4b:bca4:fd40:756]:40567/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:9d4b:bca4:fd40:756]:40567: write: connection reset by peer

[FBDWL] 2020/02/26 15:25:50.183289 service.go:261: INFO: Failed to exchange Hello messages with CIX3GDP-ZDS2VAF-P6XRBWZ-TV3PBV2-6V6UPH5-YYZU72N-6VVZIVJ-T26FAQA at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:211:32ff:fe43:8d55]:58811/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:211:32ff:fe43:8d55]:58811: write: connection reset by peer

[FBDWL] 2020/02/26 15:26:30.315641 service.go:261: INFO: Failed to exchange Hello messages with O6CDVWB-XSBPEYY-XHDD7HK-4SHCMK6-6SRXXNG-XLABHMR-KN5J5IK-MTWCFQC at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:505d:6416:c832:f0e4]:38212/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:505d:6416:c832:f0e4]:38212: write: connection reset by peer

[FBDWL] 2020/02/26 15:26:30.463753 service.go:261: INFO: Failed to exchange Hello messages with O6CDVWB-XSBPEYY-XHDD7HK-4SHCMK6-6SRXXNG-XLABHMR-KN5J5IK-MTWCFQC at [::]:22000-[2003:c7:df15:2700:505d:6416:c832:f0e4]:47290/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR

[FBDWL] 2020/02/26 15:27:00.310835 service.go:261: INFO: Failed to exchange Hello messages with CIX3GDP-ZDS2VAF-P6XRBWZ-TV3PBV2-6V6UPH5-YYZU72N-6VVZIVJ-T26FAQA at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:211:32ff:fe43:8d55]:58821/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:211:32ff:fe43:8d55]:58821: write: connection reset by peer

[FBDWL] 2020/02/26 15:27:00.450132 service.go:261: INFO: Failed to exchange Hello messages with CIX3GDP-ZDS2VAF-P6XRBWZ-TV3PBV2-6V6UPH5-YYZU72N-6VVZIVJ-T26FAQA at [::]:22000-[2003:c7:df15:2700:211:32ff:fe43:8d55]:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR

[FBDWL] 2020/02/26 15:28:11.366378 service.go:261: INFO: Failed to exchange Hello messages with CIX3GDP-ZDS2VAF-P6XRBWZ-TV3PBV2-6V6UPH5-YYZU72N-6VVZIVJ-T26FAQA at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:211:32ff:fe43:8d55]:58836/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:211:32ff:fe43:8d55]:58836: write: connection reset by peer

[FBDWL] 2020/02/26 15:28:12.472576 service.go:261: INFO: Failed to exchange Hello messages with CIX3GDP-ZDS2VAF-P6XRBWZ-TV3PBV2-6V6UPH5-YYZU72N-6VVZIVJ-T26FAQA at [::]:22000-[2003:c7:df15:2700:211:32ff:fe43:8d55]:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR

[FBDWL] 2020/02/26 15:29:22.617519 service.go:261: INFO: Failed to exchange Hello messages with CIX3GDP-ZDS2VAF-P6XRBWZ-TV3PBV2-6V6UPH5-YYZU72N-6VVZIVJ-T26FAQA at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:211:32ff:fe43:8d55]:58849/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:211:32ff:fe43:8d55]:58849: write: connection reset by peer

[FBDWL] 2020/02/26 15:29:33.681235 service.go:261: INFO: Failed to exchange Hello messages with O6CDVWB-XSBPEYY-XHDD7HK-4SHCMK6-6SRXXNG-XLABHMR-KN5J5IK-MTWCFQC at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:505d:6416:c832:f0e4]:38260/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:505d:6416:c832:f0e4]:38260: write: connection reset by peer

[FBDWL] 2020/02/26 15:29:34.816060 service.go:261: INFO: Failed to exchange Hello messages with O6CDVWB-XSBPEYY-XHDD7HK-4SHCMK6-6SRXXNG-XLABHMR-KN5J5IK-MTWCFQC at [::]:22000-[2003:c7:df15:2700:505d:6416:c832:f0e4]:48625/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256: NO_ERROR

[FBDWL] 2020/02/26 15:30:32.804610 service.go:261: INFO: Failed to exchange Hello messages with CIX3GDP-ZDS2VAF-P6XRBWZ-TV3PBV2-6V6UPH5-YYZU72N-6VVZIVJ-T26FAQA at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:211:32ff:fe43:8d55]:58868/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:211:32ff:fe43:8d55]:58868: write: connection reset by peer

[FBDWL] 2020/02/26 15:31:33.007375 service.go:261: INFO: Failed to exchange Hello messages with CIX3GDP-ZDS2VAF-P6XRBWZ-TV3PBV2-6V6UPH5-YYZU72N-6VVZIVJ-T26FAQA at [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000-[2003:c7:df15:2700:211:32ff:fe43:8d55]:58875/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: write tcp [2003:c7:df15:2700:211:32ff:fe63:7bbf]:22000->[2003:c7:df15:2700:211:32ff:fe43:8d55]:58875: write: connection reset by peer

Andy · February 26, 2020, 3:58pm

Ws läuft wohl noch immer. Wie lange geht so ein Prozess ganz grob?