Amisync blocks/hangs the computer

[FerryA1]

I've been able to synchronize small files, maybe up to 1,5MB or so, but syncing bigger files blocks the Amiga, and eventually hangs it, causing it to reboot.

My Syncthing setup is:

MacBook Pro 2015 with macOS 10.14.6 Mojave and Syncthing v1.26.1 (latest available for Mojave). I've set up a "send&receive" shared folder based on a static-size RAM disk in the Mac called "MacRAM", pointing to a folder/assign in RAM on the Amiga (better to test with RAM disks instead of risking filesystem integrity in hard disks because a hang, a bad write, whatever).

In the Amiga (Miami TPC/IP stack, AmiSync v0.9.5), I did set the config file up in order for it to write the log file in the shared folder (loglevel set to debug), so I'd have an automatic copy on the Mac. Then I copied a 1,4MB ZIP file to the shared folder in the Amiga (for your reference in the log, one containing versions 1.4 and 2.0 of Aegis Sonix). The syncing made the Amiga to get blocked for 9 minutes, couldn't move the mouse (neither USB nor DB9), clock in NewMeter stopped updating…:

https://i.imgur.com/JFQfUev.jpeg

Once synced, then I unpacked the ZIP file received in the Mac where I received it, the Mac shared folder itself, that created a folder with 4 ADF files inyo the shared folder, so Syncthing started to sync it too. According the AmiSync log (below) it was syncing the third file when the Amiga got hanged, I had to reboot (three-fingers salute):

2026-09-08 22:50:53 INF AmiSync 0.9.5 (68020 build, 07.09.2026) starting (background)
2026-09-08 22:50:53 INF daemon up; ARexx port 'AMISYNC' open
2026-09-08 22:50:53 INF daemon: clock is local time, UTC+01:00 (from locale.library)
2026-09-08 22:50:53 DBG mem: fast RAM free at startup: 1920076152
2026-09-08 22:50:54 DBG mem: ssl_open               +3870392 bytes, 1916205760 free
2026-09-08 22:50:54 INF daemon: loaded index for 'ux5wy-muxyt' (18 file(s), seq 59)
2026-09-08 22:50:54 DBG mem: folder indexes          +35776 bytes, 1916169984 free
2026-09-08 22:50:54 INF peer: starting worker for 192.168.0.10:22000
2026-09-08 22:50:54 INF daemon: 1 peer(s) configured
2026-09-08 22:50:54 INF worker: dialing 192.168.0.10:22000
2026-09-08 22:50:54 INF daemon: listening on port 22000
2026-09-08 22:50:54 INF listener: accepting BEP on port 22000
2026-09-08 22:50:54 DBG mem: peers + listener       +276504 bytes, 1915893480 free
2026-09-08 22:50:54 INF daemon: local discovery enabled
2026-09-08 22:50:54 DBG mem: discovery              +135648 bytes, 1915757832 free
2026-09-08 22:50:54 INF daemon: scanner started over 1 folder(s)
2026-09-08 22:50:54 INF scanner: started (1 folder(s), every 60s)
2026-09-08 22:50:54 DBG mem: scanner                +298528 bytes, 1915459304 free
2026-09-08 22:50:54 INF disco: announcing CG223HP-6FJIWH3-7C7Z2L7-OFUPQZJ-JYTYVNK-Z5KRYQT-OTK4PFY-CA44VQD on UDP 21027 every 30s (and listening)
2026-09-08 22:50:54 INF scanner: change notification active for 'ux5wy-muxyt' (1 watch(es) total)
2026-09-08 22:50:54 INF status: Offline
2026-09-08 22:50:54 INF scanner: tombstoned 1 vanished file(s) in folder 'ux5wy-muxyt'
2026-09-08 22:50:54 INF appicon: using icon file PROGDIR:amisync.info
2026-09-08 22:50:54 INF appicon: placed on the Workbench backdrop
2026-09-08 22:50:54 DBG mem: statuswin               +68928 bytes, 1915390376 free
2026-09-08 22:50:54 INF daemon: our device ID is CG223HP-6FJIWH3-7C7Z2L7-OFUPQZJ-JYTYVNK-Z5KRYQT-OTK4PFY-CA44VQD
2026-09-08 22:50:54 INF worker: TLS cipher TLS_CHACHA20_POLY1305_SHA256
2026-09-08 22:50:54 INF worker: peer authenticated as RTC3B3F-QXFVS6Y-I4NQSHS-DC3CYJE-ZQJNFSE-OV3YMMR-36464KG-OK3GUAN
2026-09-08 22:50:54 INF worker: connected; peer is "MacFerry.local" (syncthing v1.26.1), 1 folder(s) shared
2026-09-08 22:50:55 INF worker: peer ClusterConfig, 1 folder(s)
2026-09-08 22:50:57 INF status: Up to Date
2026-09-08 22:50:57 WRN worker: bep_read_message r=-1 (read/framing error)
2026-09-08 22:50:57 INF peer: worker for 192.168.0.10 ended (connected=1, rc=1)
2026-09-08 22:50:57 INF status: Offline
2026-09-08 22:50:59 INF worker: dialing 192.168.0.10:22000
2026-09-08 22:50:59 INF worker: TLS cipher TLS_CHACHA20_POLY1305_SHA256
2026-09-08 22:50:59 INF worker: peer authenticated as RTC3B3F-QXFVS6Y-I4NQSHS-DC3CYJE-ZQJNFSE-OV3YMMR-36464KG-OK3GUAN
2026-09-08 22:50:59 INF worker: connected; peer is "MacFerry.local" (syncthing v1.26.1), 1 folder(s) shared
2026-09-08 22:51:00 INF worker: peer ClusterConfig, 1 folder(s)
2026-09-08 22:51:02 INF status: Up to Date
2026-09-08 22:51:02 WRN worker: bep_read_message r=-1 (read/framing error)
2026-09-08 22:51:02 INF peer: worker for 192.168.0.10 ended (connected=1, rc=1)
2026-09-08 22:51:02 INF status: Offline
2026-09-08 22:51:04 INF worker: dialing 192.168.0.10:22000
2026-09-08 22:51:06 INF worker: TLS cipher TLS_CHACHA20_POLY1305_SHA256
2026-09-08 22:51:06 INF worker: peer authenticated as RTC3B3F-QXFVS6Y-I4NQSHS-DC3CYJE-ZQJNFSE-OV3YMMR-36464KG-OK3GUAN
2026-09-08 22:51:06 INF worker: connected; peer is "MacFerry.local" (syncthing v1.26.1), 1 folder(s) shared
2026-09-08 22:51:06 INF status: Up to Date
2026-09-08 22:51:07 INF worker: peer ClusterConfig, 1 folder(s)
2026-09-08 22:51:07 WRN worker: bep_read_message r=-1 (read/framing error)
2026-09-08 22:51:07 INF peer: worker for 192.168.0.10 ended (connected=1, rc=1)
2026-09-08 22:51:07 INF status: Offline
2026-09-08 22:51:09 INF worker: dialing 192.168.0.10:22000
2026-09-08 22:51:09 INF worker: TLS cipher TLS_CHACHA20_POLY1305_SHA256
2026-09-08 22:51:09 INF worker: peer authenticated as RTC3B3F-QXFVS6Y-I4NQSHS-DC3CYJE-ZQJNFSE-OV3YMMR-36464KG-OK3GUAN
2026-09-08 22:51:09 INF worker: connected; peer is "MacFerry.local" (syncthing v1.26.1), 1 folder(s) shared
2026-09-08 22:51:10 INF status: Up to Date
2026-09-08 22:51:10 INF worker: peer ClusterConfig, 1 folder(s)
2026-09-08 22:51:10 WRN worker: bep_read_message r=-1 (read/framing error)
2026-09-08 22:51:10 INF peer: worker for 192.168.0.10 ended (connected=1, rc=1)
2026-09-08 22:51:10 INF status: Offline
2026-09-08 22:51:12 INF worker: dialing 192.168.0.10:22000
2026-09-08 22:51:12 INF worker: TLS cipher TLS_CHACHA20_POLY1305_SHA256
2026-09-08 22:51:12 INF worker: peer authenticated as RTC3B3F-QXFVS6Y-I4NQSHS-DC3CYJE-ZQJNFSE-OV3YMMR-36464KG-OK3GUAN
2026-09-08 22:51:12 INF worker: connected; peer is "MacFerry.local" (syncthing v1.26.1), 1 folder(s) shared
2026-09-08 22:51:14 INF worker: peer ClusterConfig, 1 folder(s)
2026-09-08 22:51:16 INF status: Up to Date
2026-09-08 23:25:15 INF worker: 4 file(s) to fetch from 'ux5wy-muxyt'
2026-09-08 23:25:15 INF worker: fetching 'Aegis_Sonix -1.4 y 2.0-/Cobra-ImpSonix13.adf' (7 block(s))
2026-09-08 23:25:15 INF status: Syncing (4 files)
2026-09-08 23:25:16 DBG worker: block 2 of 'Aegis_Sonix -1.4 y 2.0-/Cobra-ImpSonix13.adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:16 DBG worker: block 3 of 'Aegis_Sonix -1.4 y 2.0-/Cobra-ImpSonix13.adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:16 DBG worker: block 4 of 'Aegis_Sonix -1.4 y 2.0-/Cobra-ImpSonix13.adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:17 DBG worker: block 5 of 'Aegis_Sonix -1.4 y 2.0-/Cobra-ImpSonix13.adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:17 DBG worker: block 6 of 'Aegis_Sonix -1.4 y 2.0-/Cobra-ImpSonix13.adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:17 INF worker: completed 'Aegis_Sonix -1.4 y 2.0-/Cobra-ImpSonix13.adf'
2026-09-08 23:25:17 INF worker: fetching 'Aegis_Sonix -1.4 y 2.0-/Aegis_Sonix_v2.0_1987_Aegis.adf' (7 block(s))
2026-09-08 23:25:17 DBG worker: block 2 of 'Aegis_Sonix -1.4 y 2.0-/Aegis_Sonix_v2.0_1987_Aegis.adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:18 INF status: Syncing (3 files)
2026-09-08 23:25:18 DBG worker: block 3 of 'Aegis_Sonix -1.4 y 2.0-/Aegis_Sonix_v2.0_1987_Aegis.adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:19 DBG worker: block 4 of 'Aegis_Sonix -1.4 y 2.0-/Aegis_Sonix_v2.0_1987_Aegis.adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:19 DBG worker: block 5 of 'Aegis_Sonix -1.4 y 2.0-/Aegis_Sonix_v2.0_1987_Aegis.adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:20 DBG worker: block 6 of 'Aegis_Sonix -1.4 y 2.0-/Aegis_Sonix_v2.0_1987_Aegis.adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:21 INF worker: completed 'Aegis_Sonix -1.4 y 2.0-/Aegis_Sonix_v2.0_1987_Aegis.adf'
2026-09-08 23:25:21 INF worker: fetching 'Aegis_Sonix -1.4 y 2.0-/Aegis Sonix - Scores 5 (19xx)(-).adf' (7 block(s))
2026-09-08 23:25:21 DBG worker: block 1 of 'Aegis_Sonix -1.4 y 2.0-/Aegis Sonix - Scores 5 (19xx)(-).adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:21 DBG worker: block 3 of 'Aegis_Sonix -1.4 y 2.0-/Aegis Sonix - Scores 5 (19xx)(-).adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:22 DBG worker: block 2 of 'Aegis_Sonix -1.4 y 2.0-/Aegis Sonix - Scores 5 (19xx)(-).adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:22 INF status: Syncing (2 files)
2026-09-08 23:25:22 DBG worker: block 4 of 'Aegis_Sonix -1.4 y 2.0-/Aegis Sonix - Scores 5 (19xx)(-).adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:23 DBG worker: block 3 of 'Aegis_Sonix -1.4 y 2.0-/Aegis Sonix - Scores 5 (19xx)(-).adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:23 DBG worker: block 5 of 'Aegis_Sonix -1.4 y 2.0-/Aegis Sonix - Scores 5 (19xx)(-).adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:23 DBG worker: block 4 of 'Aegis_Sonix -1.4 y 2.0-/Aegis Sonix - Scores 5 (19xx)(-).adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:24 DBG worker: block 6 of 'Aegis_Sonix -1.4 y 2.0-/Aegis Sonix - Scores 5 (19xx)(-).adf' arrived ahead of its turn; re-requesting
2026-09-08 23:25:24 DBG worker: block 5 of 'Aegis_Sonix -1.4 y 2.0-/Aegis Sonix - Scores 5 (19xx)(-).adf' arrived ahead of its turn; re-requesting

Also, when syncing even small files, I noticed a certain "stutter" in the mouse, like the syncing interfering with the mouse.

Other times, the Amiga got blocked as soon as I started amisync, so no log could be captured, but I've been not able to reproduce in solid way, looks pretty random…

That's all I can remember.

Right now, I'd say amisync is too unstable for a regular use, but it has an enormous potential.

And if you need me to do any test, just ask.

Saluditos,

Ferrán.

[thomasseverinsen]

Ferrán,

Thanks again for the detailed report - the log and the context around it were exactly what I needed.

I've been digging into it today, and I have a couple of possible solutions that I'm working on. I've been testing against a real A4000 as well as a couple of WinUAE configurations, all with Roadshow and SyncThing 2.x. So my setup is a bit different from yours, but I am making progress and getting some interesting results.

Thanks for the patience!

imSaluditos,
Thomas

[thomasseverinsen]

Hi Ferrán

0.9.6 is out: https://github.com/thomasseverinsen/amisync/releases/tag/v0.9.6

Fixes:

1. The "arrived ahead of its turn" issue was every block being fetched twice.
2. A block the peer never answered could hang a transfer forever.
3. A log file inside a synced folder was announcing itself with the wrong size on every scan.

The freeze itself I couldn't reproduce. I'm not sure, but it could be an issue with Emu68. This report is an A1200 on the 1.1 alpha 1 freezing under load: michalsc/Emu68#323

Three small things if you get a chance to try the new version:

1. Move logfile to a hard-disk partition outside the shared folder and send me the whole file after a freeze.
2. If it still freezes tell me which network driver you're using (PCMCIA card, or the Pi's own port).

Thanks again, this was a very useful report.

[FerryA1]

Hi, Thomas.

Well, I'm using Emu68 v1.1 beta1, not alpha1, I can run it for hours without a single hiccup with net running (web, ftp, samba, synergy client…). Same with alpha2, the version I was running before beta1.

Regarding the net driver, I'm using wifipi.device, RPi own wifi connection.

For example, I'm betatesting a FTP program from a friend, I'm using it now to transfer files downloaded from Aminet with my Mac to a Synology server, and from there to the Amiga with this FTP prog. Previously I used SMB2, directly mounting the server on the Amiga in order to transfer files: not a single problem either ways with both progs, even with files in the GB size range.

On the other hand, mine is a 8GB CM4, limited in config.txt to 2GB, so this should be not a problem. In the Emu68 issue thread you linked to, I suspect the user is limiting Amiga mem to 1024MB in a 1GB RPi, so he's telling Emu68 the Amiga can use ALL the RPi mem, and Emu68 (not only the emulator itself, but the overlay files, ELF files, etc.) uses some RPi mem, so if that user tells the Amiga to use it all, he could be overwriting mem already being used by the emulator, hanging the Amiga. But, hey, just a guess…

I'll try the new version and report back.

Saluditos,

Ferrán.

[FerryA1]

Oh, I forgot:

regarding putting the log file in a hard drive, hmmmm… That's exactly what I was trying to prevent: an unfinished write during a freeze could lead to problems with the file system. I discovered a while ago that RAD drives do survive a reboot in Emu68, let's see if it can survive a freeze too ;)

Saluditos,

Ferrán.

[thomasseverinsen]

Hi Ferrán,

RAD: for the log is a good idea, no need to risk any file system issues :)

You're right, it doesn't sound like Emu68. It could be the SSL encryption, that's the one thing AmiSync does that FTP and SMB don't.
If you get a chance, the attached file might narrow it down. It runs a benchmark of AmiSSL's crypto.

Unzip it, copy to T:, Protect ssl_bench_020 +e.

If the machine stutters or freezes while it runs, we'll know that's it.
ssl_bench_020.zip

Thanks for helping test all this!

[FerryA1]

Hi, Thomas.

First, the ssl_bench output:

ssl_bench: 4 MB per primitive, 64 KiB chunks

  AES-128-GCM            4096 KB in 340 ms = 12047 KB/s
  AES-256-GCM            4096 KB in 340 ms = 12047 KB/s
  ChaCha20-Poly1305      4096 KB in 200 ms = 20480 KB/s
  SHA-256                4096 KB in 100 ms = 40960 KB/s

For scale: amisync's per-block SHA-256 verify was measured in
situ on the A4000 at about 930 KB/s. A cipher line far above the
observed transfer rate means the cipher is not what you are
waiting on.

Then, the debug log from amisync:

2026-09-11 01:59:24 INF AmiSync 0.9.6 (68020 build, 09.09.2026) starting (background)
2026-09-11 01:59:24 INF daemon up; ARexx port 'AMISYNC' open
2026-09-11 01:59:24 INF daemon: clock is local time, UTC+01:00 (from locale.library)
2026-09-11 01:59:24 INF daemon: platform: 68040+FPU under Emu68, Kickstart 47.13, TCP/IP: bsdsocket.library 4.1 (15.12.96), 1.8 MB chip / 1830.6 MB fast free
2026-09-11 01:59:24 DBG mem: fast RAM free at startup: 1919570688
2026-09-11 01:59:24 DBG mem: ssl_open               +3870392 bytes, 1915700296 free
2026-09-11 01:59:24 INF daemon: loaded index for 'ux5wy-muxyt' (42 file(s), seq 96)
2026-09-11 01:59:24 DBG mem: folder indexes          +37120 bytes, 1915663176 free
2026-09-11 01:59:24 INF peer: starting worker for 192.168.0.10:22000
2026-09-11 01:59:24 INF daemon: 1 peer(s) configured
2026-09-11 01:59:24 INF worker: dialing 192.168.0.10:22000
2026-09-11 01:59:24 INF daemon: listening on port 22000
2026-09-11 01:59:24 INF listener: accepting BEP on port 22000
2026-09-11 01:59:24 DBG mem: peers + listener       +276504 bytes, 1915386672 free
2026-09-11 01:59:24 INF daemon: local discovery enabled
2026-09-11 01:59:24 DBG mem: discovery              +135648 bytes, 1915251024 free
2026-09-11 01:59:24 INF daemon: scanner started over 1 folder(s)
2026-09-11 01:59:24 DBG mem: scanner                +297472 bytes, 1914953552 free
2026-09-11 01:59:24 INF scanner: started (1 folder(s), every 60s)
2026-09-11 01:59:24 INF disco: announcing CG223HP-6FJIWH3-7C7Z2L7-OFUPQZJ-JYTYVNK-Z5KRYQT-OTK4PFY-CA44VQD on UDP 21027 every 30s (and listening)
2026-09-11 01:59:24 INF scanner: change notification active for 'ux5wy-muxyt' (1 watch(es) total)
2026-09-11 01:59:24 INF scanner: tombstoned 18 vanished file(s) in folder 'ux5wy-muxyt'
2026-09-11 01:59:24 INF status: Offline
2026-09-11 01:59:24 INF appicon: using icon file PROGDIR:amisync.info
2026-09-11 01:59:24 INF appicon: placed on the Workbench backdrop
2026-09-11 01:59:24 DBG mem: statuswin               +45512 bytes, 1914908040 free
2026-09-11 01:59:24 INF daemon: our device ID is CG223HP-6FJIWH3-7C7Z2L7-OFUPQZJ-JYTYVNK-Z5KRYQT-OTK4PFY-CA44VQD
2026-09-11 01:59:25 INF worker: TLS cipher TLS_CHACHA20_POLY1305_SHA256
2026-09-11 01:59:25 INF worker: peer authenticated as RTC3B3F-QXFVS6Y-I4NQSHS-DC3CYJE-ZQJNFSE-OV3YMMR-36464KG-OK3GUAN
2026-09-11 01:59:25 INF worker: connected; peer is "MacFerry.local" (syncthing v1.26.1), 1 folder(s) shared
2026-09-11 01:59:26 INF worker: peer ClusterConfig, 1 folder(s)
2026-09-11 01:59:28 INF status: Up to Date
2026-09-11 01:59:29 INF worker: 9 file(s) to fetch from 'ux5wy-muxyt'
2026-09-11 01:59:29 INF worker: fetching 'zenPrismWifi.readme' (1 block(s))
2026-09-11 01:59:29 INF worker: completed 'zenPrismWifi.readme'
2026-09-11 01:59:29 INF worker: fetching 'zenPrismWifi.lha' (1 block(s))
2026-09-11 01:59:29 INF worker: completed 'zenPrismWifi.lha'
2026-09-11 01:59:29 INF worker: fetching 'statram31.readme' (1 block(s))
2026-09-11 01:59:29 INF worker: completed 'statram31.readme'
2026-09-11 01:59:29 INF worker: fetching 'statram31.lha' (1 block(s))
2026-09-11 01:59:29 INF worker: completed 'statram31.lha'
2026-09-11 01:59:29 INF worker: fetching 'rsGUI.readme' (1 block(s))
2026-09-11 01:59:29 INF worker: completed 'rsGUI.readme'
2026-09-11 01:59:29 INF worker: fetching 'rsGUI.lha' (1 block(s))
2026-09-11 01:59:29 INF worker: completed 'rsGUI.lha'
2026-09-11 01:59:29 INF worker: fetching 'BackupVault.readme' (1 block(s))
2026-09-11 01:59:29 INF worker: completed 'BackupVault.readme'
2026-09-11 01:59:29 INF worker: fetching 'BackupVault.lha' (2 block(s))
2026-09-11 01:59:29 DBG worker: block 1 of 'BackupVault.lha' arrived ahead of its turn; holding it
2026-09-11 01:59:29 INF worker: completed 'BackupVault.lha'
2026-09-11 01:59:29 INF worker: fetching 'amisync-0.9.6.lha' (4 block(s))
2026-09-11 01:59:29 DBG worker: block 3 of 'amisync-0.9.6.lha' arrived ahead of its turn; holding it
2026-09-11 01:59:29 DBG worker: block 2 of 'amisync-0.9.6.lha' arrived ahead of its turn; holding it
2026-09-11 01:59:29 INF worker: completed 'amisync-0.9.6.lha'

and, last, the output from the Syncthing app in my Mac (from the moment it connects to Amisyc):

2026-09-11 01:59:25 Established secure connection to CG223HP at 192.168.0.10:22000-192.168.0.240:1024/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/LAN-P10-33A1M7BAL7K3GOFN17AOFCN49E
2026-09-11 01:59:25 Device CG223HP client is "AmiSync 0.9.6" named "CaOS1200" at 192.168.0.10:22000-192.168.0.240:1024/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/LAN-P10-33A1M7BAL7K3GOFN17AOFCN49E
2026-09-11 01:59:26 Device CG223HP folder "MacRAM" (ux5wy-muxyt) has a new index ID (0x106B3EC9D0BA04DB)
2026-09-11 02:00:44 Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
2026-09-11 02:00:44 Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
2026-09-11 02:00:44 listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: Get "https://relays.syncthing.net/endpoint": dial tcp 49.12.16.80:443: connect: host is down

The last lines, those related to "Relay listener", do keep repeating on and on.

Now, what happened:

As in previous tests, I have a shared folder defined in the Mac side, containing your amisync-0.9.6.lha and 8 more files downloaded from Aminet, totalling like 800KB:

https://i.imgur.com/RjKJRGk.jpeg

I start with the Syncthing app already started in the Mac, then I start the Amiga side after a fresh boot. As soon as the synchronization starts -aprox. at 01:59:26-, the Amiga freezes but not hangs, and after 4mins and 35secs of freezing, syncing was done and Amiga unfrozen. While the Amiga was frozen, the Syncthing web page said the status of the Amiga was "Synchronizing (0%)".

Then I did a second attempt, but trying to know what was exactly the delay between I press "Intro" to the amisync command and the freeze. I prepared everything, including a fresh boot in the Amiga, net on, wrote "amisync" in a shell and pressed "intro" at 2:58:00. Mouse and clock got frozen at 2:58:03, but this time it did not return after syncing was done: I resetted the Amiga after 10 minutes waiting.

Find below the Amisync log for this last attempt and, after it, the log of the Mac app:

2026-09-11 02:58:00 INF AmiSync 0.9.6 (68020 build, 09.09.2026) starting (background)
2026-09-11 02:58:00 INF daemon up; ARexx port 'AMISYNC' open
2026-09-11 02:58:00 INF daemon: clock is local time, UTC+01:00 (from locale.library)
2026-09-11 02:58:00 INF daemon: platform: 68040+FPU under Emu68, Kickstart 47.13, TCP/IP: bsdsocket.library 4.1 (15.12.96), 1.9 MB chip / 1831.3 MB fast free
2026-09-11 02:58:00 DBG mem: fast RAM free at startup: 1920318840
2026-09-11 02:58:00 DBG mem: ssl_open               +3868016 bytes, 1916450824 free
2026-09-11 02:58:00 INF daemon: loaded index for 'ux5wy-muxyt' (52 file(s), seq 127)
2026-09-11 02:58:00 DBG mem: folder indexes          +37000 bytes, 1916413824 free
2026-09-11 02:58:00 INF peer: starting worker for 192.168.0.10:22000
2026-09-11 02:58:00 INF daemon: 1 peer(s) configured
2026-09-11 02:58:00 INF worker: dialing 192.168.0.10:22000
2026-09-11 02:58:00 INF daemon: listening on port 22000
2026-09-11 02:58:00 INF listener: accepting BEP on port 22000
2026-09-11 02:58:00 DBG mem: peers + listener       +276504 bytes, 1916137320 free
2026-09-11 02:58:00 INF daemon: local discovery enabled
2026-09-11 02:58:00 DBG mem: discovery              +135648 bytes, 1916001672 free
2026-09-11 02:58:00 INF daemon: scanner started over 1 folder(s)
2026-09-11 02:58:00 INF scanner: started (1 folder(s), every 60s)
2026-09-11 02:58:00 DBG mem: scanner                +297472 bytes, 1915704200 free
2026-09-11 02:58:00 INF disco: announcing CG223HP-6FJIWH3-7C7Z2L7-OFUPQZJ-JYTYVNK-Z5KRYQT-OTK4PFY-CA44VQD on UDP 21027 every 30s (and listening)
2026-09-11 02:58:00 INF scanner: change notification active for 'ux5wy-muxyt' (1 watch(es) total)
2026-09-11 02:58:00 INF scanner: tombstoned 11 vanished file(s) in folder 'ux5wy-muxyt'
2026-09-11 02:58:00 INF status: Offline
2026-09-11 02:58:00 INF appicon: using icon file PROGDIR:amisync.info
2026-09-11 02:58:00 INF appicon: placed on the Workbench backdrop
2026-09-11 02:58:00 DBG mem: statuswin               +50480 bytes, 1915653720 free
2026-09-11 02:58:00 INF daemon: our device ID is CG223HP-6FJIWH3-7C7Z2L7-OFUPQZJ-JYTYVNK-Z5KRYQT-OTK4PFY-CA44VQD
2026-09-11 02:58:02 INF worker: TLS cipher TLS_CHACHA20_POLY1305_SHA256
2026-09-11 02:58:02 INF worker: peer authenticated as RTC3B3F-QXFVS6Y-I4NQSHS-DC3CYJE-ZQJNFSE-OV3YMMR-36464KG-OK3GUAN
2026-09-11 02:58:02 INF worker: connected; peer is "MacFerry.local" (syncthing v1.26.1), 1 folder(s) shared
2026-09-11 02:58:02 INF status: Up to Date
2026-09-11 02:58:03 INF worker: peer ClusterConfig, 1 folder(s)

Mac app log (from the moment it establishes connection with Amisync):

2026-09-11 02:58:02 Established secure connection to CG223HP at 192.168.0.10:22000-192.168.0.240:1024/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/LAN-P10-33A1SK3LUSH8GLFCQ8HR55M924
2026-09-11 02:58:02 Device CG223HP client is "AmiSync 0.9.6" named "CaOS1200" at 192.168.0.10:22000-192.168.0.240:1024/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/LAN-P10-33A1SK3LUSH8GLFCQ8HR55M924
2026-09-11 02:58:04 Device CG223HP folder "MacRAM" (ux5wy-muxyt) has a new index ID (0x46F32D57414A52FB)
2026-09-11 02:59:00 Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
2026-09-11 02:59:00 Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
2026-09-11 02:59:00 listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: Get "https://relays.syncthing.net/endpoint": dial tcp 49.12.16.80:443: connect: host is down
2026-09-11 02:59:00 Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
2026-09-11 02:59:00 Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
2026-09-11 02:59:00 listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: Get "https://relays.syncthing.net/endpoint": dial tcp 49.12.16.80:443: connect: host is down
2026-09-11 02:59:00 Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
2026-09-11 02:59:00 Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
2026-09-11 02:59:00 listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: Get "https://relays.syncthing.net/endpoint": dial tcp 49.12.16.80:443: connect: host is down
2026-09-11 02:59:52 Lost primary connection to CG223HP at 192.168.0.10:22000-192.168.0.240:1024/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/LAN-P10-33A1SK3LUSH8GLFCQ8HR55M924: reading length: read tcp 192.168.0.10:22000->192.168.0.240:1024: read: operation timed out (0 remain)
2026-09-11 02:59:52 Connection to CG223HP at 192.168.0.10:22000-192.168.0.240:1024/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/LAN-P10-33A1SK3LUSH8GLFCQ8HR55M924 closed: reading length: read tcp 192.168.0.10:22000->192.168.0.240:1024: read: operation timed out
2026-09-11 03:00:04 Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
2026-09-11 03:00:04 Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
2026-09-11 03:00:04 listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: Get "https://relays.syncthing.net/endpoint": dial tcp 49.12.16.80:443: connect: host is down

BTW, finally RAD did show it was not a proper solution: it resists a soft reboot, but not a hard one, and the kind of freeze Amisync does need a hard reboot. But then I remembered of an "old friend": StatRAM. It is able to resist almost any reboot (not a power cycle, of course), so you can remount the unit and it will be there, containing the info, again and again, until you switch the Amiga off.

Hope all this info helps.

Saluditos,

Ferrán.

[FerryA1]

Hi again.

I forgot: ssl_bench took like 1-2 seconds or so to give results and finish its task, so no time to see if there was any stutter or freeze.

Saluditos,

Ferrán.

[thomasseverinsen]

Hi Ferrán,

Thanks again for the detailed info!

I've released 0.9.7 with some fixes based on what I see from your logs:
A send that stops draining now gives up after 120 s and reconnects instead of holding the daemon forever.
Sends over 5 s are logged, and the Workbench icon is relabeled far less often during a sync.

None of that explains why it freezes though.

For this run use the attached amisync_020 rather than the 0.9.7 release. It is 0.9.7 plus two experimental changes: no compression on
sent messages, and the TCP stack's default socket buffers. taskmon is a tiny monitor that runs at high priority and logs once a second which
task was running.

1. Put both binaries in C: and Protect them +e.

2. In amisync.conf add these two lines, and point the log file at a disk rather than RAM: so it survives a reset:
   appicon = no
   discovery = no
   This removes updating the desktop appicon and sending UDP discovery broadcasts from the equation.

3. Fresh boot, network up, then:
   Run >NIL: taskmon LOG=SYS:taskmon.log
   amisync

4. Let it sync the same files as before. If it freezes and doesn't come
   back, reset after a few minutes as you did.

Then please attach amisync.log and taskmon.log. Together they should hopefully show whats going on.

I have an A1200 sitting around and may pick up a PiStorm32 so I can chase this on the same hardware if this run doesn't settle it :)

Thanks for your patience with this.

amisync_020_experimental.zip
taskmon.zip

Saluditos,
Thomas