Vbox

Vbox

[Peter]

Hi,

on trying to set-up vbox I get the following messages:

on booting:
INIT: Id "I5" respawning too fast: disabled for 5 minutes

My entry in inittab is:
I5:2345:respawn:/usr/sbin/vboxgetty -d /dev/ttyI5

with command 
telnet localhost vboxd
I get:
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused

and command vbox gives:
Connecting to 'localhost:20012'...
vbox: can't connect to 'localhost:20012

that number 20012 comes from the file /etc/services
vboxd           20012/tcp                       # voice box system
vboxd           20012/udp

What could be wrong?

Thanks & regards




-- 
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Vbox

[Ray Olszewski]

Tough one, Peter, with so little info to work with.

The usual source of respawn problems is an attempt to access a device that 
is not accessable in some way (for example, a serial port that does not 
have handshaking set up properly). Since ttyI5 is not a standard device, 
you might do well to tell us (or check for yourself) both its actual entry 
in /dev and whatever it is supposed to be connected to (some isdn device, I 
imagine) to look for configuration problems. You might also see if the 
"respawn" message is preceded in the logs by any more specific message 
about the process ... such messages usually are.

If neither telnet nor vbox can connect to port 20012, the fist thing to 
check is whether anything is listening on that port. Does vboxd run 
directly as a daemon or through inetd? If the first, is it actually 
running? If the second, is inetd.conf configured proprely? Does either 
vboxd or inetd log anything in connection with these failed attempts?

Beyond those specific thoughts ... the Debian package notes for vbox3 
(which I assume is the same app) mention that it is no longer being 
maintained by its creator, and that opens the door to the possibility of an 
uncorrected bug. So it you post again, you might want to include some 
details about what version (distro) of Linux you are running, what version 
of vbox, and how you got vbox (your distro's packaging system? comipled it 
yourself from source?). Oh, and what your hardware (idsn) setup is.

This URL -- http://www.linuxnetmag.com/en/issue2/m2vbox1.html -- (found in 
2 minutes using Google) has some troubleshooting advice for vboxgetty  and 
vboxd.

At 04:30 PM 10/25/02 +0800, Peter wrote:
>Hi,
>
>on trying to set-up vbox I get the following messages:
>
>on booting:
>INIT: Id "I5" respawning too fast: disabled for 5 minutes
>
>My entry in inittab is:
>I5:2345:respawn:/usr/sbin/vboxgetty -d /dev/ttyI5
>
>with command
>telnet localhost vboxd
>I get:
>Trying 127.0.0.1...
>telnet: connect to address 127.0.0.1: Connection refused
>
>and command vbox gives:
>Connecting to 'localhost:20012'...
>vbox: can't connect to 'localhost:20012
>
>that number 20012 comes from the file /etc/services
>vboxd           20012/tcp                       # voice box system
>vboxd           20012/udp
>
>What could be wrong?
>
>Thanks & regards




--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: VBox

[Peter]

Thnaks Ray!

ray@comarre.com said:
>  You might also see if the  "respawn" message is preceded in the logs
> by any more specific message  about the process ... such messages
> usually are.

In /var/log/messages I get the following

Oct 25 14:39:29 philonline modprobe: modprobe: Can't locate module 
char-major-43
Oct 25 14:44:30 philonline last message repeated 10 times
Oct 25 14:49:31 philonline last message repeated 10 times
Oct 25 14:54:32 philonline last message repeated 10 times
Oct 25 14:59:33 philonline last message repeated 10 times

when I5:2345:respawn:/usr/sbin/vboxgetty -d /dev/ttyI5
is enabled in inittab.

ray@comarre.com said:
> Does vboxd run  directly as a daemon or through inetd? If the first,
> is it actually  running? If the second, is inetd.conf configured
> proprely? Does either  vboxd or inetd log anything in connection with
> these failed attempts?

The instructions say that vboxd can only be used with inetd for which reason I 
put the following in /etc/inetd.conf:
vboxd  stream  tcp  nowait  root  /usr/sbin/tcpd  /usr/sbin/vboxd
as per instructions.

I have
vbox version 2.0.0BETA5 (17-NOV-98)
and run RH7.2

ray@comarre.com said:
> This URL -- http://www.linuxnetmag.com/en/issue2/m2vbox1.html --
> (found in  2 minutes using Google) has some troubleshooting advice for
> vboxgetty  and  vboxd


I checked this out and tail vboxgetty-ttyI5.log gives

26-Oct 16:04:46 <D> Opening modem port "/dev/ttyI5"...
26-Oct 16:04:46 <F> Can't open modem port "/dev/ttyI5"

after /usr/sbin/vboxgetty -d /dev/ttyI5.

So that what it is. The modem port can't be opened. Then where do we go from 
here?

Regards


-- 
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs