[Dxspider-support] Auto start second cluster
Peter
pc2a at pi4cc.nl
Thu Nov 24 18:25:16 GMT 2011
Hi Jim
Thanks for the surgestion.
cluster2.pl is running fine when manually started up
#dx1:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl"
sysop >/dev/null
dx2:235:respawn:/bin/su -c "DXSPIDER_ROOT=/home/sysop2 /usr/bin/perl -w
/home/sysop2/spider/perl/cluster2.pl" sysop2 >/dev/tty5
Change all so the out and # the first line
But still get
Nov 24 18:21:23 pi4cc init: Id "dx2" respawning too fast: disabled for 5
minutes
Peter
Jim Bayer schreef:
> Here is an odd thought....
>
> Try renaming cluster.pl in /home/sysop2 to cluster2.pl and change inittab to
> the same. Maybe the init process is trying to respawn the same named
> process and doesn't like it.
>
> This is really a hack but I'm curious if it will work.
>
> Jim
>
> -----Original Message-----
> From: dxspider-support-bounces at dxcluster.org
> [mailto:dxspider-support-bounces at dxcluster.org] On Behalf Of Peter
> Sent: Thursday, November 24, 2011 3:22 AM
> To: The DXSpider Support list
> Subject: Re: [Dxspider-support] Auto start second cluster
>
> Hi All
>
> I still can't managed to autostart 2 dx-spiders on my Debian setup
> dx1 is auto starting after a reboot, but dx2 refuse I got the warning in
> syslog :
> dx2" respawning too fast: disabled for 5 minutes
>
> A manual startup for DX2 works fine
>
> Perhaps its has tot do something paths (?)
> dx2 is in /home/sysop2 and when start-up I go manualy to spider/perl and
> call./cluster.pl
>
> An output of ps | aux clusters.pl:
> pi4cc:~# ps aux | grep cluster.pl
> sysop 1027 0.0 0.2 31244 1120 ? Ss 01:02 0:00 /bin/su
> -c /usr/bin/perl -w /spider/perl/cluster.pl sysop
> sysop 1040 1.1 7.6 86228 38492 ? S 01:02 5:25
> /usr/bin/perl -w /spider/perl/cluster.pl
> sysop2 23664 0.5 5.5 80376 28256 pts/0 S 08:50 0:02
> /usr/bin/perl -w ./cluster.pl
> root 24092 0.0 0.1 3932 540 pts/1 S+ 08:57 0:00 grep
> cluster.pl
>
> There is only 1 line for sysop2.
> Is this a clue?
>
> Peter
> PC2A/PI4CC
>
>
>
> Bob Tenty schreef:
>
>> You see that if it tries to restart it too much because it doesn't run.
>>
>> can you hash out/ disable cluster 1 and see or it only runs with dx 2
>> Line of dx2 looks OK but try the above.
>>
>> Here I run it in a virtual tty not in use, so instead of /dev/null
>> /dev/tty7 for instance. So you can run dx1 and dx2 in two different
>> tty's who are not in use.
>>
>> 73,
>>
>> Bob VE3TOK
>>
>> On 11-11-03 04:33 PM, Peter wrote:
>>
>>> Bob
>>>
>>> In the log file I found:
>>> Nov 3 20:02:33 pi4cc init: Id "dx2" respawning too fast: disabled for
>>> 5 minutes
>>>
>>> ???
>>>
>>> Peter
>>>
>>> NBob Tenty schreef:
>>>
>>>> The system logs are in /var/log look in syslog, messages
>>>>
>>>> dmesg can also give a clue.
>>>>
>>>> 73,
>>>>
>>>> Bob VE3TOK
>>>>
>>>> On 11-11-03 04:03 PM, Peter wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> Sorry that I come back with the same question of " How to auto
>>>>> start a second cluster"
>>>>> April 2010 I had the same question and I got I working.
>>>>> But now the second cluster refuse to start.
>>>>>
>>>>> Cluster 1 is running as sys op (home/sysop) and the second as
>>>>> sysop2
>>>>> (home/sysop2)
>>>>> Manual starting the second cluster via
>>>>> /home/sysop2/spider/perl/cluster.pl will bring up the cluster.
>>>>>
>>>>> DXSPIDER_ROOT is correct:
>>>>> sysop2 at pi4cc:~$ echo $DXSPIDER_ROOT /home/sysop2/spider
>>>>> sysop2 at pi4cc:~$
>>>>>
>>>>> In /etc/inittab I have the 2 lines:
>>>>> dx1:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl"
>>>>> sysop >/dev/null
>>>>> dx2:235:respawn:/bin/su -c "DXSPIDER_ROOT=/home/sysop2
>>>>> /usr/bin/perl -w /home/sysop2/spider/perl/cluster.pl" sysop2
>>>>>
>>>>>> /dev/null
>>>>>>
>>>>> Yes I do telinit q after changes
>>>>> DX1 is autostarting and DX2 refuses.
>>>>> Is there somewhere a log file of inittab with an output to see if
>>>>> there is any error?
>>>>>
>>>>> What do I wrong?
>>>>> Running the system on a debian linux OS
>>>>>
>>>>> Peter
>>>>> PC2A/PI4CC
>>>>>
More information about the Dxspider-support
mailing list