[VoxBo] single user mode error!

[Daniel Kimberg]

> Thank you very much. According to your opinions, I install it for a
> cluster on my single computer. However, the error emerges again. I
> test my 6004 port. It is OK! What is the problem? I have missed any
> configuration step?

I think you're pretty close.  From the log you sent, it looks like you started the scheduler, suspended it with ctrl-z, and then started again as a second process.  The first time, it looks like it succeeded, but the second time it couldn't open the port (because the first process still had it open).  You can only run the scheduler once at a time, and it's okay to ctrl-c it if you want to restart it (or you can do "voxq --die").  If you ctrl-z it, it's still running (suspended) and keeps the port open.  But I think that's the only reason it couldn't open the port.

The other issue is that it doesn't seem to be finding any servers.  The scheduler will check the list of servers in VoxBo/etc/serverlist, and it gets a little sensitive about machine names.  If your machine's domain name is mymachine.foo.bar.edu, it's best to name the server mymachine.  Which means that you should have a line for mymachine in VoxBo/etc/serverlist and a file in VoxBo/etc/servers called mymachine.  I think there's a sample file in that directory, you can just rename it and edit it so that the hostname is mymachine.  For single-user mode you'll probably want to set it up so that it always lets processes use all your CPUs.

dan