DXSpider Tracing Debug Entries

From DXSpider Documentation Wiki
Revision as of 17:11, 5 April 2025 by WI3W (talk | contribs) (Change debug link to something better suited to sysops who have a running node.)
Jump to navigation Jump to search

General Information

DXspider has the ability to log information at various levels, and those levels are set using the debug tool in conjunction with the debug levels. Whilst this information is capture in data files in ../spider/local_data/debug/ it can also be seen in realtime from the command line prompt. Once the debug level is set the watchdbg tool can be used from ../spider/perl/ to watch the cluster's full data stream. This can be a very busy stream but it can be filtered for easier scrutiny.

Filtering traces

To trace incoming messages the I is used, and for outbound the D is used:

'<- I' or ' I '
'<- D' or ' D '

Trace examples

To watch all outbound spots from this node.

./watchdbg ' D ' 'PC[16]1'

or just

./watchdbg '\-> D'

Saving to a file

The debug files will save these traces, and those files can then be searched. But it is possible to save the traces to a specific file by using pipe | to push them to a file.

./watchdbg ' D ' 'PC[16]1' | grep <thing to search for> | trace.txt