From: g0vgs Date: Mon, 26 Mar 2001 20:22:04 +0000 (+0000) Subject: Add FAQ on restarting user file X-Git-Tag: R_1_47~92 X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=commitdiff_plain;h=204a594bd86adeba2cbb1ddefd3ddd6c288b702a;p=spider.git Add FAQ on restarting user file --- diff --git a/html/spiderFAQ-2.html b/html/spiderFAQ-2.html index 125b9d33..c707610d 100644 --- a/html/spiderFAQ-2.html +++ b/html/spiderFAQ-2.html @@ -81,6 +81,20 @@ take effect.

Remember to make it executable!

This will limit your debug data down to the last 10 days

+

2.6 I updated my Linux distribution and now Spider cannot read the users +file or the dupefile, what is the problem?

+ +

Almost certainly this is a change in the db format of perl. Follow these +few steps to correct the problem. +

+

+

That should solve the problem. +


Next Previous diff --git a/html/spiderFAQ.html b/html/spiderFAQ.html index d44fe38e..8656f59e 100644 --- a/html/spiderFAQ.html +++ b/html/spiderFAQ.html @@ -15,7 +15,7 @@ Contents

The DXSpider FAQ

-

Ian Maude, G0VGS, (ianmaude@btinternet.com)

Version 0.4 March 2001 +

Ian Maude, G0VGS, (ianmaude@btinternet.com)

Version 0.5 March 2001


A reference for SysOps of the DXSpider DXCluster program.
@@ -40,6 +40,7 @@ Contents
  • 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
    Next diff --git a/sgml/spiderFAQ.sgml b/sgml/spiderFAQ.sgml index 7a3d9e70..e2962e5c 100644 --- a/sgml/spiderFAQ.sgml +++ b/sgml/spiderFAQ.sgml @@ -6,7 +6,7 @@ The DXSpider FAQ <author>Ian Maude, G0VGS, (ianmaude@btinternet.com) -<date>Version 0.4 March 2001 +<date>Version 0.5 March 2001 <abstract> A reference for SysOps of the DXSpider DXCluster program. </abstract> @@ -124,4 +124,20 @@ Remember to make it executable! This will limit your debug data down to the last 10 days +<sect1>I updated my Linux distribution and now Spider cannot read the users +file or the dupefile, what is the problem? + +<P> +Almost certainly this is a change in the db format of perl. Follow these +few steps to correct the problem. + +<itemize> +<item>stop the cluster (disable any autostart in inittab) +<item>cd /spider/data +<item>issue the command perl user_asc +<item>restart the cluster +</itemize> + +That should solve the problem. + </article> diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt index ecd96265..142293b2 100644 --- a/txt/spiderFAQ.txt +++ b/txt/spiderFAQ.txt @@ -1,6 +1,6 @@ The DXSpider FAQ Ian Maude, G0VGS, (ianmaude@btinternet.com) - Version 0.4 March 2001 + Version 0.5 March 2001 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -22,6 +22,7 @@ 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? ______________________________________________________________________ @@ -64,6 +65,8 @@ 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. + + 11..44.. II aamm rruunnnniinngg RReeddHHaatt 55..22 aanndd II aamm ggeettttiinngg ssttrraannggee eerrrroorrss,, wwhhaatt iiss wwrroonngg?? @@ -127,9 +130,9 @@ - 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?? @@ -157,25 +160,22 @@ This will limit your debug data down to the last 10 days + 22..66.. ffiillee oorr tthhee dduuppeeffiillee,, wwhhaatt iiss tthhee pprroobblleemm?? II uuppddaatteedd mmyy LLiinnuuxx + ddiissttrriibbuuttiioonn aanndd nnooww SSppiiddeerr ccaannnnoott rreeaadd tthhee uusseerrss + 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.