The DXSpider FAQ
- Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 0.4 March 2001
+ Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
+ December 2001 Revision: 1.8
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
1. Installation
-
1.1 Where do I get DXSpider?
1.2 How do I use the patches?
1.3 If I use a tarball to overwrite my installation, what happens to my configuration?
1.4 I am running RedHat 5.2 and I am getting strange errors, what is wrong?
2. Administration
-
2.1 How can I get Spider to restart automatically if it crashes?
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.
+ 2.8 I have deleted a message but it is still there, why?
______________________________________________________________________
-
-
assuming the patch version you are using is 1.40 and resides in /tmp!
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?
-
Run _\bt_\be_\bl_\bi_\bn_\bi_\bt _\bq as root. Spider will restart so be aware. However, any
time you reboot, cluster.pl will start in tty7 and if it crashes, it
should restart ok.
-
or in later versions of Spider, there is a command called _\bw_\ba_\bt_\bc_\bh_\bd_\bb_\bg in
which case you simply type ..
-
-
2\b2.\b.3\b3.\b. M\bMy\by n\bne\bei\big\bgh\bhb\bbo\bou\bur\bri\bin\bng\bg n\bno\bod\bde\be c\bca\ban\bnn\bno\bot\bt u\bus\bse\be t\bth\bhe\be R\bRC\bCM\bMD\bD c\bco\bom\bmm\bma\ban\bnd\bd t\bto\bo m\bme\be,\b, h\bhe\be j\bju\bus\bst\bt
k\bke\bee\bep\bps\bs g\bge\bet\btt\bti\bin\bng\bg t\bth\bhe\be "\b"t\btu\but\bt t\btu\but\bt"\b" m\bme\bes\bss\bsa\bag\bge\be.\b.
-
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?
-
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.
+ 2\b2.\b.8\b8.\b. I\bI h\bha\bav\bve\be d\bde\bel\ble\bet\bte\bed\bd a\ba m\bme\bes\bss\bsa\bag\bge\be b\bbu\but\bt i\bit\bt i\bis\bs s\bst\bti\bil\bll\bl t\bth\bhe\ber\bre\be,\b, w\bwh\bhy\by?\b?
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+ This is now the way messages are handled for deletion in Spider. If
+ you look closely you will see a 'D' following the message number.
+ This message is marked for deletion and will be deleted in 2 days if
+ nothing further is done. Optionally you can use the command
+ _\bd_\be_\bl_\be_\bt_\be_\b/_\be_\bx_\bp_\bu_\bn_\bg_\be to delete it immediately.
projects / spider.git / blobdiff