The DXSpider FAQ
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 0.3 January 2001
+ $Date$ $Revision$
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
2.2 How can I monitor traffic to and from a node or user?
2.3 My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message.
2.4 I do not seem to be sending any bulletin mail to my link partners, what is wrong?
+ 2.5 How can I automatically limit the amount of debug logfiles that are stored?
+ 2.6 I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?
+ 2.7 Since I last updated I seem to be getting duplicate spots appearing.
______________________________________________________________________
1\b1.\b.3\b3.\b. I\bIf\bf I\bI u\bus\bse\be a\ba t\bta\bar\brb\bba\bal\bll\bl t\bto\bo o\bov\bve\ber\brw\bwr\bri\bit\bte\be m\bmy\by i\bin\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn,\b, w\bwh\bha\bat\bt h\bha\bap\bpp\bpe\ben\bns\bs t\bto\bo
m\bmy\by c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn?\b?
+
The tarballs are designed to not overwrite your existing configuration
and can be used at any time to update your Spider software. All the
key files have the suffix .issue (eg. DXVars.pm.issue) at default.
+
1\b1.\b.4\b4.\b. I\bI a\bam\bm r\bru\bun\bnn\bni\bin\bng\bg R\bRe\bed\bdH\bHa\bat\bt 5\b5.\b.2\b2 a\ban\bnd\bd I\bI a\bam\bm g\bge\bet\btt\bti\bin\bng\bg s\bst\btr\bra\ban\bng\bge\be e\ber\brr\bro\bor\brs\bs,\b, w\bwh\bha\bat\bt i\bis\bs
w\bwr\bro\bon\bng\bg?\b?
spoof gb7adx set/home gb7adx
-
-
-
Assuming that the node_call you are changing is gb7adx.
+
2\b2.\b.4\b4.\b. I\bI d\bdo\bo n\bno\bot\bt s\bse\bee\bem\bm t\bto\bo b\bbe\be s\bse\ben\bnd\bdi\bin\bng\bg a\ban\bny\by b\bbu\bul\bll\ble\bet\bti\bin\bn m\bma\bai\bil\bl t\bto\bo m\bmy\by l\bli\bin\bnk\bk p\bpa\bar\brt\bt-\b-
n\bne\ber\brs\bs,\b, w\bwh\bha\bat\bt i\bis\bs w\bwr\bro\bon\bng\bg?\b?
take effect.
+ 2\b2.\b.5\b5.\b. H\bHo\bow\bw c\bca\ban\bn I\bI a\bau\but\bto\bom\bma\bat\bti\bic\bca\bal\bll\bly\by l\bli\bim\bmi\bit\bt t\bth\bhe\be a\bam\bmo\bou\bun\bnt\bt o\bof\bf d\bde\beb\bbu\bug\bg l\blo\bog\bgf\bfi\bil\ble\bes\bs t\bth\bha\bat\bt
+ a\bar\bre\be s\bst\bto\bor\bre\bed\bd?\b?
+ Use the tmpwatch command. Create a file in /etc/cron.daily/
+ containing the line ...
+ /usr/sbin/tmpwatch -f 240 /spider/data/debug
+ Remember to make it executable!
+ This will limit your debug data down to the last 10 days
+ 2\b2.\b.6\b6.\b. I\bI u\bup\bpd\bda\bat\bte\bed\bd m\bmy\by L\bLi\bin\bnu\bux\bx d\bdi\bis\bst\btr\bri\bib\bbu\but\bti\bio\bon\bn a\ban\bnd\bd n\bno\bow\bw S\bSp\bpi\bid\bde\ber\br c\bca\ban\bnn\bno\bot\bt r\bre\bea\bad\bd t\bth\bhe\be
+ u\bus\bse\ber\brs\bs f\bfi\bil\ble\be o\bor\br t\bth\bhe\be d\bdu\bup\bpe\bef\bfi\bil\ble\be,\b, w\bwh\bha\bat\bt i\bis\bs t\bth\bhe\be p\bpr\bro\bob\bbl\ble\bem\bm?\b?
+ Almost certainly this is a change in the db format of perl. Follow
+ these few steps to correct the problem.
+ +\bo stop the cluster (disable any autostart in inittab)
+ +\bo cd /spider/data
+ +\bo issue the command perl user_asc
+ +\bo restart the cluster
+ That should solve the problem.
+ 2\b2.\b.7\b7.\b. S\bSi\bin\bnc\bce\be I\bI l\bla\bas\bst\bt u\bup\bpd\bda\bat\bte\bed\bd I\bI s\bse\bee\bem\bm t\bto\bo b\bbe\be g\bge\bet\btt\bti\bin\bng\bg d\bdu\bup\bpl\bli\bic\bca\bat\bte\be s\bsp\bpo\bot\bts\bs
+ a\bap\bpp\bpe\bea\bar\bri\bin\bng\bg.\b.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+ What has probably happened is that the dupefile has got corrupted in
+ some way. Simply delete the /spider/data/dupefile and restart the
+ cluster. It may take a little time to become fully functional but
+ should solve your problem.
projects / spider.git / blobdiff