> Sorry to keep bugging...
No problem.
>
> I am now trying to add a virtual server. I do the following:
>
> [root@localhost /root]# vsdadm vs_create homex.xxxx.com vsone 66.XX.XX.XX
> vsone.xxxx.com 200 0
If the prompt just returns, then there is no problem, if it returns with
a -ERR or a read timeout then there is a problem. Which version of the
source are you using? The freevsd-1.4.9-1.tar.gz or have you fetched the
latest CVS?
vsdadm logs all of its commands to syslog, but if you want some verbose
output, add the following args to the vsd entry in inetd.conf:
-p local6 -l 4
but I wouldn't advise doing this for anything else than debugging vsd,
as it sends all the protocol sent to syslog (not a good thing to have
going on).
If the prompt does just return then you are ready to physically create
your virtual server which vsd-vsbatch.pl (you woun't get any output from
this unless there are errors).
All of these steps are covered in the freevsd-1.4.9/INSTALL document,
which is a damn fine read :).
Damion.
>
> Thing is that it just hangs. Doesn't do anything at all.
>
> Is there somewhere a log to look at? I can't go further without knowing
> what to look for. Or, of course, do you know what the problem might be?
>
> Thank you for your help!!
>
> pablo
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of FreeVSD
> Sent: Thursday, August 02, 2001 11:27 AM
> To: [EMAIL PROTECTED]
> Subject: Re: System.map problem
>
> I see now. That explains it!
>
> I have been able to access it via telnet. So it seems to all be good.
>
> Thank you,
>
> Pablo
>
> On 02 Aug 2001 16:09:20 +0100, Damion Parry wrote:
> > Hello,
> >
> > vsd runs as a process through inetd, you don't need to manually start
> > it. To set up all of the necessary configuration you just need to run
> > vsd-install.pl. Once thats done you should be able to execute any vsd
> > commands (either through vsdadm or through the protocol) and it will all
> > work.
> >
> > If you want to see that the daemon is there listening try:
> >
> > telnet localhost 1725
> >
> > and you should get the prompt (this will work for NON-SSL only):
> >
> > +OK FreeVSD Virtual Server Administrator localhost.localdomain v1.4.9
> > ready
> >
> > and typing 'EOF' will get you out of it.
> >
> > The error reading map problem, is the vsd map (etc/vsd/vsd.conf), not a
> > system file.
> >
> > HTH.
> > Damion.
> >
> >
> >
> >
> >
> > FreeVSD wrote:
> > >
> > > Hi,
> > >
> > > I am installing freevsd on a redhat 6.2 system that has been patched
> > > with a new kernel. It comes this way from my system vendor. The patch
> > > upgrades the kernel to 2.2.19 and other goodies.
> > >
> > > The problem I have is that after installing freevsd, I try to start the
> > > daemon and get an error:
> > >
> > > [root@localhost]# /etc/rc.d/init.d/vsd start
> > > couldn't read server map file: No such file or directory
> > >
> > > I think it's referring to the System.map file. I checked in my /boot
> > > directory and here is what I have:
> > >
> > > [root@localhost freevsd-1.4.9]# ls -l /boot
> > > total 40
> > > lrwxrwxrwx 1 root root 11 Jul 26 14:54 System.map ->
> > > /System.map
> > > -rw-r--r-- 1 root root 512 Apr 10 2000 boot.0300
> > > -rw-r--r-- 1 root root 512 Jul 26 14:58 boot.0800
> > > -rw-r--r-- 1 root root 4568 Feb 2 2000 boot.b
> > > -rw-r--r-- 1 root root 612 Feb 2 2000 chain.b
> > > -rw-r--r-- 1 root root 237 Apr 11 2000 kernel.h
> > > -rw------- 1 root root 12288 Jul 26 15:29 map
> > > -rw-r--r-- 1 root root 620 Feb 2 2000 os2_d.b
> > >
> > > The actually System.map file is sitting in the / directory as specified
> > > by the symbolic link. Why would this cause an error? Is there a
> > > specific string it's looking for? How do I find the place in the code
> > > where this is occuring? Or simply: How do I fix it so I can start the
> > > vsd daemon?
> > >
> > > Thank you!
> > >
> > > Pablo
> > >
> > > ------------------------- The freeVSD Support
> List --------------------------
> > > Subscribe:
> mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
> > > Unsubscribe:
> mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
> > > Archives: http://freevsd.org/support/mail-archives/freevsd-support
> >
> > --------------------------------------------------------------------------
> ---
> > ------------------------- The freeVSD Support
> List --------------------------
> > Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
> > Unsubscribe:
> mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
> > Archives: http://freevsd.org/support/mail-archives/freevsd-support
> > --------------------------------------------------------------------------
> ---
> >
> >
>
> ------------------------- The freeVSD Support
> List --------------------------
> Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
> Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
> Archives: http://freevsd.org/support/mail-archives/freevsd-support
> ----------------------------------------------------------------------------
> -
>
> ------------------------- The freeVSD Support List --------------------------
> Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
> Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
> Archives: http://freevsd.org/support/mail-archives/freevsd-support
> -----------------------------------------------------------------------------
------------------------- The freeVSD Support List --------------------------
Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
Archives: http://freevsd.org/support/mail-archives/freevsd-support
-----------------------------------------------------------------------------
