Seen in the log during startup, shortly before syncthing connects to another device on the local network, using local discovery. Failed to parse connection url: tcp://[fe80::21e:6ff:fea4:fdfd%{107D0076-9FB9-4334-BA63-C73D06E42D83}]:22000...
FWIW. Windows 10 just updated and got the null bytes in config.xml again. And the end of syncthing.log also has null bytes. This was on 1.1.22, so as expected. Deleting the config.xml indeed fixed it. Looking forward to the next version, keep up the good work! Loving Syncthing/Sync...
Your post allowed me to quickly solve a problem. I ran into this same 'namespacing permission denied' issue that was noted in my systemctl logs while creating a CT for a Syncthing server. Simply checking Options>Features>Nesting:ON took care of the problem! Reactions: willybong and ...
RuntimeDirectoryMode=755 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGROOT}/data ExecStart=/usr/bin/postgres -D ${PGROOT}/data ExecReload=/bin/kill -HUP ${MAINPID} KillMode=mixed KillSignal=SIGINT # Due to PostgreSQL's use of shared memory, OOM killer is often overzealous in # ...
zpool get ashift syncthing-pool NAME PROPERTY VALUE SOURCE syncthing-pool ashift 0 default Running zdb gives the true ashift value: MOS Configuration: version: 5000 name: 'syncthing-pool' state: 0 txg: 94840 pool_guid: 11492548645590784878 errata: 0 hostid: 2360010168 hostname: 'pve' com.delp...