This is happening before the syncthing logging facility is running as there is nothing in the logs from the GUI.
If I add the line: ExecStartPre=/bin/sleep 9 under the Service heading it wait long enough for whatever it needs and it starts up the fist time.
So how can I see what syncthing does not have if it starts up too early. I.E. what is causing these failures? Latest Raspberry pi OS.
Yes, in your log entries, Syncthing tries to bind to eth0…
… before eth0 has been assigned an IP address 8 seconds later:
One option is to replace the symlink – e.g. ~/.config/systemd/user/syncthing.service (if running as a user service) – with a copy of the service unit file that’s been customized like so:
That fixed it. Is there a way to tell the powers that be to change their default syncthing unit file or has that already been done after I installed syncthing?
Some Linux repos package the upstream unit file if it’s available while others roll their own.
Given the order in which services often start, it’s normally not necessary to delay starting. Based on the snippet of log entries you shared earlier, it almost looks like the DHCP lease request is taking longer than is typical.
If you’d rather not maintain a custom unit file, another option is to create a drop-in that overrides settings in the default unit file.