[VoxBo] error for vbsrvd in xinetd

[Julia Bender]

HiDan, hi Dongbo,

I'm not sure if this is what you suggested I should do, but I restarted
xinetd, restarted the scheduler, waited a few seconds, then retried my
sequence. Here's what I get:

kli-lab at Herkules:/mrt/Visac/14Visac/models> voxq -a

Server      Load Pri Job                            Pct Elapsed
Herkules    0.54  0  <idle>

------------------------------------------------------------------------
Sequence Name        Num  Pri Owner    Wait  Run   Bad   Done Total
------------------------------------------------------------------------
test                 4     1  kli-lab   33    0     0     0    33
------------------------------------------------------------------------

So, it's still not running, although the scheduler and server seem to be on.
Do you have any ideas what could be wrong, still?

Thanks,
 Julia


> Hi Julia.  I think there are a few things possibly going on here.  It
looks like you first saw this:
>
>> No servers currently available.
>
> and later this:
>
>> "voxq -l":
>> Server         Load  CPU Usage Resources
>> Herkules       0.08   0 of 1   cpu,bigtape,littletape(0) mailagent(0)
>
> The former means that your machine was not visible, but the latter means
that it was.  Since these bits of information come from the same place
in
> the code, I'm going to assume this means that your server was installed
and running correctly, but you just ran the first command too soon after
starting the scheduler (it takes a few seconds to check in with the
server).
>
>> "voxq -b Herkules" (localhost) gives me:
>> host Herkules not currently reserved in your name
>
> I'm not sure what you were trying to do here -- voxq -b is for releasing
a
> machine that you've previously reserved with voxq -g.  You should never
need to use it when you're the only VoxBo user on the machine.
>
>> So the scheduler cannot access my machine. I've checked the defaults
file, serverlist, servers/ and the xinetd configuration and everything
looks right. However when I do "xinetd -d" i get
>
> xinetd -d is the command to start the xinetd server manually in debug
mode.  This isn't the normal way to start and stop xinetd.  In
> Redhat/Fedora, you can restart xinetd with this:
>   /etc/init.d/xinetd restart
> You have to do that as root or using sudo.  It might be the same command
or something similar on your distribution.  But from the output of voxq
-l
> above, it looks like xinetd is already running just fine, and the
scheduler is having no problem connecting to the server.
>
> Incidentally, if you need to grab the old version of vbview, I put a
separate copy up here:
>
> http://voxbo.org/download/alacarte/linux/oldvbview
>
> dan
>


Dipl. Psych. Julia Bender
Humboldt Universität zu Berlin
Mathematisch - Naturwissenschaftliche Fakultät II
Institut für Psychologie, Abt. Klinische Psychologie
Unter den Linden 6
D-10099 Berlin