Meta tags:
Headings (most frequently used words):
debugging, syncthing, file, isn, syncing, the, folder, counts, seem, incorrect, debug, logs, environment, variables, stepping, with, breakpoints, navigation, related, topics, quick, search, donate, support,
Text of the page (most frequently used words):
the (64), syncthing (21), and (21), file (16), for (11), api (8), #debugging (7), debug (7), with (7), set (7), run (6), you (6), use (6), folder (6), side (6), gui (5), this (5), logs (5), can (5), name (5), discovery (5), database (5), folderid (5), sync (5), receiving (5), usage (4), version (4), mapping (4), command (4), need (4), reporting (3), event (3), github (3), steps (3), build (3), binary (3), these (3), running (3), logging (3), which (3), cpu (3), number (3), information (3), used (3), under (3), port (3), main (3), facility (3), nat (3), model (3), beacon (3), sttrace (3), environment (3), counts (3), out (3), post (3), both (3), sending (3), filename (3), question (3), automatic (2), crash (2), developers (2), building (2), development (2), documentation (2), rest (2), release (2), device (2), introduction (2), remote (2), configuration (2), follow (2), vscode (2), https (2), com (2), delve (2), program (2), any (2), cores (2), string (2), line (2), only (2), filesystem (2), upnp (2), stun (2), relay (2), client (2), protocol (2), pmp (2), root (2), package (2), connections (2), sqlite (2), are (2), listed (2), facilities (2), generally (2), log (2), level (2), given (2), variables (2), including (2), variable (2), about (2), placeholder (2), represents (2), abcd (2), 1234 (2), etc (2), seem (2), incorrect (2), output (2), cli (2), taked (2), why (2), begin (2), will (2), check (2), failed (2), donate, support, quick, search, next, previous, overview, related, topics, specifications, http, utility, services, signing, creating, issue, management, infrastructure, understanding, ids, working, web, navigation, written, gf020590, edit, page, goland, jetbrains, create, two, displayed, microsoft, golang, blob, master, docs, installing, using, itself, see, stnodefaultfolder, stnoupgrade, stnorestart, dlv, listen, 2345, headless, true, exec, home, _test_config, browser, like, step, through, non, optimized, derekparker, stepping, breakpoints, hack, completely, disable, example, when, benchmarks, nonempty, value, logger_discard, percentage, heap, growth, trigger, default, 100, lower, numbers, keep, peak, memory, down, price, performance, gogc, maximum, defaults, all, available, gomaxprocs, add, extra, wrapper, tool, controlling, communicate, end, user, stversionextra, internal, deadlocks, sets, sensitivity, direction, developer, stlockthreshold, watcher, watchaggregator, versioning, versioner, upgrades, upgrade, functionality, change, detection, hashing, scanner, bep, hub, access, generation, events, discover, dialing, dialer, connection, handling, loading, saving, config, multicast, broadcast, valid, strings, below, additionally, always, outputs, most, date, list, help, serve, increase, verbosity, specific, enter, comma, separated, trace, optionally, per, specify, something, other, than, potentially, overriding, global, adjustment, warn, error, windows, needs, prior, unix, mac, easiest, way, prepend, there, lot, that, happens, behind, covers, quite, silent, verbose, various, parts, enable, profiling, files, total, inspect, raw, following, sides, from, verbatim, indicating, same, above, second, details, directories, relative, make, sure, quotes, around, includes, spaces, first, extract, metadata, nothing, relevant, showed, far, considered, receive, setup, look, closer, what, knows, may, items, cause, failure, secondly, has, mentioned, even, not, currently, visible, together, someone, forum, screenshots, wonder, suspect, caused, bug, collect, some, isn, syncing,
Text of the page (random words):
debugging syncthing syncthing documentation debugging syncthing a file isn t syncing if you wonder why a given file is out of sync or you suspect it s caused by a bug we need to collect some information you ll need the name of the file and the folder id it s in to begin with check the gui on the receiving side it may be listed under failed items with a cause for the failure secondly check the logs on the receiving side if the file has failed to sync this will be mentioned in the logs even if it is not currently visible in the gui if you are debugging this together with someone on the forum post screenshots of the gui and the logs in question if nothing relevant showed up so far or the question is why the file is considered out of sync to begin with in a receive only setup etc we can look closer at what syncthing knows about the file you ll need to do these steps on both the receiving side and sending side we will need to use the syncthing cli for this first an extract of database metadata for the file taked by the command syncthing debug database file folderid filename the folderid placeholder represents the folder id e g abcd 1234 and filename is the name of the file including any directories relative to the folder root make sure to use quotes around the file name if it includes spaces second details of the file information for the file in question taked by the command syncthing cli debug file folderid filename use the same folder id and file name as above post the output from both of these verbatim indicating which is the receiving side and which is the sending side the folder counts seem incorrect if the number of files in sync out of sync in total etc seem to be incorrect we can inspect the raw counts in the database run the following command on both the sending and receiving sides and post the output syncthing debug database counts folderid the folderid placeholder represents the folder id e g abcd 1234 debug logs there s a lot that happens behind the covers and syncthing is generally quite silent about it a number of environment variables can be used to set the logging to verbose for various parts of the program and to enable profiling under unix including mac the easiest way to run syncthing with an environment variable set is to prepend the variable to the command line i e sttrace model syncthing on windows it needs to be set prior to running syncthing c set sttrace model c syncthing environment variables sttrace used to increase the debugging verbosity in specific facilities generally mapping to a go package enter a comma separated string of facilities to trace api beacon optionally a log level can be given per facility to specify something other than debug api warn beacon error potentially overriding a global log level adjustment the valid facility strings are listed below additionally syncthing serve help always outputs the most up to date list api rest api beacon multicast and broadcast discovery config configuration loading and saving connections connection handling db sqlite sqlite database dialer dialing connections discover remote device discovery events event generation and logging fs filesystem access main main package model the root hub nat nat discovery and port mapping pmp nat pmp discovery and port mapping protocol the bep protocol relay client relay client scanner file change detection and hashing stun stun functionality syncthing main run facility upgrade binary upgrades upnp upnp discovery and port mapping ur usage reporting versioner file versioning watchaggregator filesystem event watcher stlockthreshold used for debugging internal deadlocks sets debug sensitivity use only under direction of a developer stversionextra add extra information to the version string in logs and the version line in the gui can be set to the name of a wrapper or tool controlling syncthing to communicate this to the end user gomaxprocs set the maximum number of cpu cores to use defaults to all available cpu cores gogc percentage of heap growth at which to trigger gc default is 100 lower numbers keep peak memory usage down at the price of cpu usage i e performance logger_discard hack to completely disable logging for example when running benchmarks set to any nonempty value to use it stepping with breakpoints if you like to step through the running program build a non optimized binary and run with https github com derekparker delve follow these steps go run build go debug binary build stnodefaultfolder 1 stnoupgrade 1 stnorestart 1 dlv listen 2345 headless true api version 2 exec syncthing home _test_config no browser for installing and using delve itself see vscode microsoft https github com golang vscode go blob master docs debugging md goland jetbrains create remote run configuration and follow the two steps displayed edit this page on github version v2 1 0 26 gf020590 written for v2 1 0 navigation introduction usage development introduction working on the web gui building syncthing debugging syncthing automatic crash reporting for developers understanding device ids syncthing infrastructure issue management creating a release release signing rest api event api http utility services api specifications related topics documentation overview development previous building syncthing next automatic crash reporting for developers quick search donate support
|