X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2FspiderFAQ.txt;h=315f73cbe57812fed9b6f7712d75aba95f16c91c;hb=ab10b5e76b152d41273281b30b019e4c82ed22d8;hp=20cfae60ad15f06a9cc69e6a20b5e947179ffba5;hpb=b922eb1d8811f06f593a921dcb748a1ba19aaac9;p=spider.git diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt index 20cfae60..315f73cb 100644 --- a/txt/spiderFAQ.txt +++ b/txt/spiderFAQ.txt @@ -1,6 +1,6 @@ The DXSpider FAQ - Ian Maude, G0VGS, (ianmaude@btinternet.com) - Version 0.2 July 2000 + Ian Maude, G0VGS, (g0vgs@gb7mbc.net) + December 2001 Revision: 1.8 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -9,18 +9,20 @@ 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? ______________________________________________________________________ @@ -47,8 +49,6 @@ - - assuming the patch version you are using is 1.40 and resides in /tmp! @@ -64,6 +64,7 @@ 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. + 11..44.. II aamm rruunnnniinngg RReeddHHaatt 55..22 aanndd II aamm ggeettttiinngg ssttrraannggee eerrrroorrss,, wwhhaatt iiss wwrroonngg?? @@ -85,7 +86,6 @@ - Run _t_e_l_i_n_i_t _q 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. @@ -102,7 +102,6 @@ - or in later versions of Spider, there is a command called _w_a_t_c_h_d_b_g in which case you simply type .. @@ -112,8 +111,6 @@ - - 22..33.. MMyy nneeiigghhbboouurriinngg nnooddee ccaannnnoott uussee tthhee RRCCMMDD ccoommmmaanndd ttoo mmee,, hhee jjuusstt kkeeeeppss ggeettttiinngg tthhee ""ttuutt ttuutt"" mmeessssaaggee.. @@ -127,72 +124,69 @@ - Assuming that the node_call you are changing is gb7adx. + 22..44.. II ddoo nnoott sseeeemm ttoo bbee sseennddiinngg aannyy bbuulllleettiinn mmaaiill ttoo mmyy lliinnkk ppaarrtt-- nneerrss,, wwhhaatt iiss wwrroonngg?? 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 - restart Spider for the changes to take effect. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + issue the command _l_o_a_d_/_f_o_r_w_a_r_d or restart Spider for the changes to + take effect. + 22..55.. HHooww ccaann II aauuttoommaattiiccaallllyy lliimmiitt tthhee aammoouunntt ooff ddeebbuugg llooggffiilleess tthhaatt + aarree ssttoorreedd?? + 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 + 22..66.. II uuppddaatteedd mmyy LLiinnuuxx ddiissttrriibbuuttiioonn aanndd nnooww SSppiiddeerr ccaannnnoott rreeaadd tthhee + uusseerrss ffiillee oorr tthhee dduuppeeffiillee,, wwhhaatt iiss tthhee pprroobblleemm?? + Almost certainly this is a change in the db format of perl. Follow + these few steps to correct the problem. + +o stop the cluster (disable any autostart in inittab) + +o cd /spider/data + +o issue the command perl user_asc + +o restart the cluster + That should solve the problem. + 22..77.. SSiinnccee II llaasstt uuppddaatteedd II sseeeemm ttoo bbee ggeettttiinngg dduupplliiccaattee ssppoottss + aappppeeaarriinngg.. + 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. + 22..88.. II hhaavvee ddeelleetteedd aa mmeessssaaggee bbuutt iitt iiss ssttiillll tthheerree,, wwhhyy?? + 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 + _d_e_l_e_t_e_/_e_x_p_u_n_g_e to delete it immediately.