+++ /dev/null
- The DXSpider FAQ
- Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
- December 2001 Revision: 1.8
-
- A reference for SysOps of the DXSpider DXCluster program.
- ______________________________________________________________________
-
- Table of Contents
-
-
- 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?
-
-
- ______________________________________________________________________
-
- Please mail any FAQs to the maintainer at the address above.
-
-
-
- 1\b1.\b. I\bIn\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn
-
- 1\b1.\b.1\b1.\b. W\bWh\bhe\ber\bre\be d\bdo\bo I\bI g\bge\bet\bt D\bDX\bXS\bSp\bpi\bid\bde\ber\br?\b?
-
- All things Spider can be found at www.dxcluster.org and the actual
- program and patches can be found in the download area.
-
-
- 1\b1.\b.2\b2.\b. H\bHo\bow\bw d\bdo\bo I\bI u\bus\bse\be t\bth\bhe\be p\bpa\bat\btc\bch\bhe\bes\bs?\b?
-
- Patching is done in the standard linux way ...
-
-
-
- zcat /tmp/patch-1.40 | patch -p0
-
-
-
- assuming the patch version you are using is 1.40 and resides in /tmp!
-
-
- Be aware that each patch assumes the previous patch has been applied.
- That is to say if you are patching from version 1.38 to 1.40 you would
- first need to apply patch-1.39 and then patch-1.40.
-
-
- 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?
-
- The version of Perl that comes with 5.2 seems to be some kind of pre-
- release and is broken. You can get a new version of perl from
- www.dxcluster.org or ftp://updates.redhat.com. Don't forget to patch
- it with the CPAN modules.
-
-
- 2\b2.\b. A\bAd\bdm\bmi\bin\bni\bis\bst\btr\bra\bat\bti\bio\bon\bn
-
- 2\b2.\b.1\b1.\b. H\bHo\bow\bw c\bca\ban\bn I\bI g\bge\bet\bt S\bSp\bpi\bid\bde\ber\br t\bto\bo r\bre\bes\bst\bta\bar\brt\bt a\bau\but\bto\bom\bma\bat\bti\bic\bca\bal\bll\bly\by i\bif\bf i\bit\bt c\bcr\bra\bas\bsh\bhe\bes\bs?\b?
-
- Put this line into /etc/inittab ..
-
-
-
- DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop > /dev/tty7
-
-
-
- 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.
-
-
- 2\b2.\b.2\b2.\b. H\bHo\bow\bw c\bca\ban\bn I\bI m\bmo\bon\bni\bit\bto\bor\br t\btr\bra\baf\bff\bfi\bic\bc t\bto\bo a\ban\bnd\bd f\bfr\bro\bom\bm a\ba n\bno\bod\bde\be o\bor\br u\bus\bse\ber\br?\b?
-
- There are 2 ways to achieve this. You can use the _\bt_\ba_\bi_\bl command like
- this ..
-
-
-
- tail -f /spider/data/debug/167.dat |grep G0VGS
-
-
-
- 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 ..
-
-
-
- watchdbg G0VGS
-
-
-
- 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 permissions are set correctly (perm level 5
- required), it could be that the home_node is set incorrectly. You can
- reset the home_node using the _\bs_\bp_\bo_\bo_\bf command like this ..
-
-
-
- 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?
-
- There is a file in /spider/msg called forward.pl.issue. Rename this
- to forward.pl and edit it to meet your requirements. You will need to
- issue the command _\bl_\bo_\ba_\bd_\b/_\bf_\bo_\br_\bw_\ba_\br_\bd or restart Spider for the changes to
- 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.
-
-
- 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