Tried to down BOARDBUSY on custom listener startup
Hi
I've written a custom perl listener for the client channel.
It seems to work quite fine when it starts properly, but most of the time it just sits there receiving no data and there's the message "Tried to down BOARDBUSY" in the listener logs.
I suspect this is related to the channel registration :)
Henrik, any clue how to debug this? May it be something wrong in my client?
Cheers, Gildas
On Tue, Mar 06, 2007 at 11:19:21AM +0000, Gildas Le Nadan wrote:
I've written a custom perl listener for the client channel.
It seems to work quite fine when it starts properly, but most of the time it just sits there receiving no data and there's the message "Tried to down BOARDBUSY" in the listener logs.
I suspect this is related to the channel registration :)
How are you running your perl program ?
You must run it from hobbitlaunch.cfg through a new section like
[myclienttool] ENVFILE /usr/lib/hobbit/server/etc/hobbitserver.cfg CMD hobbitd_channel --channel=client /usr/local/bin/myclient.pl LOGFILE $BBSERVERLOGS/myclient.log
myclient.pl then receives the client data on <STDIN>
For debugging you can run it by hand. You MUST be logged in as the hobbit user, then run bbcmd hobbitd_channel --channel=client /usr/local/bin/myclient.pl
Henrik
Henrik Stoerner wrote:
On Tue, Mar 06, 2007 at 11:19:21AM +0000, Gildas Le Nadan wrote:
I've written a custom perl listener for the client channel.
It seems to work quite fine when it starts properly, but most of the time it just sits there receiving no data and there's the message "Tried to down BOARDBUSY" in the listener logs.
I suspect this is related to the channel registration :)
How are you running your perl program ?
You must run it from hobbitlaunch.cfg through a new section like
[myclienttool] ENVFILE /usr/lib/hobbit/server/etc/hobbitserver.cfg CMD hobbitd_channel --channel=client /usr/local/bin/myclient.pl LOGFILE $BBSERVERLOGS/myclient.log
myclient.pl then receives the client data on <STDIN>
For debugging you can run it by hand. You MUST be logged in as the hobbit user, then run bbcmd hobbitd_channel --channel=client /usr/local/bin/myclient.pl
Henrik
Ok, my mistake. The message is sent when hobbit is stopped, not started, so it is a known issue.
I guess I was just too impatient, as I receive messages after a while.
It seems that there is some kind of buffering on the logs produced by the listener when launched through hobbitlaunch.cfg so it delayed the messages even more.
Thanks for your help, Gildas
Gildas, Maybe it has something to do with buffering. Did you unbuffer the stdin/out in your perl script? You can do it by select or using sysread/syswrite system calls. -werner
On 3/6/07, Gildas Le Nadan <gn1 at sanger.ac.uk> wrote:
Henrik Stoerner wrote:
On Tue, Mar 06, 2007 at 11:19:21AM +0000, Gildas Le Nadan wrote:
I've written a custom perl listener for the client channel.
It seems to work quite fine when it starts properly, but most of the time it just sits there receiving no data and there's the message "Tried to down BOARDBUSY" in the listener logs.
I suspect this is related to the channel registration :)
How are you running your perl program ?
You must run it from hobbitlaunch.cfg through a new section like
[myclienttool] ENVFILE /usr/lib/hobbit/server/etc/hobbitserver.cfg CMD hobbitd_channel --channel=client /usr/local/bin/myclient.pl LOGFILE $BBSERVERLOGS/myclient.log
myclient.pl then receives the client data on <STDIN>
For debugging you can run it by hand. You MUST be logged in as the hobbit user, then run bbcmd hobbitd_channel --channel=client /usr/local/bin/myclient.pl
Henrik
Ok, my mistake. The message is sent when hobbit is stopped, not started, so it is a known issue.
I guess I was just too impatient, as I receive messages after a while.
It seems that there is some kind of buffering on the logs produced by the listener when launched through hobbitlaunch.cfg so it delayed the messages even more.
Thanks for your help, Gildas
participants (3)
-
gn1＠sanger.ac.uk
-
henrik＠hswn.dk
-
wxxx333＠gmail.com