Hello, I agree with Ben, it looks like its a hostname problem. vmail1.pacspro.com is resolving to the host box, but when vsd tries to figure out what vmail1.pacspro.com is, it can't find anything, so is telling you that the vs doesn't exist (it treats the host as a vs as well).
There is a soft link in the /home/vsd/vs directory with the same name as the host, if you use this name in the vsdadm command it should work. HTH, Damion. John Oliver wrote: > [root@vmail1 root]# vsdadm vs_create vmail1.pacspro.com vsone > 192.168.20.132 test1.pacspro.com 50 0 default > error: -ERR Virtual server does not exist > > [root@vmail1 root]# ping -U vmail1.pacspro.com > PING vmail1.pacspro.com (192.168.20.131) from 192.168.20.131 : 56(84) > bytes of data. > > [root@vmail1 root]# ping -U test1.pacspro.com > PING test1.pacspro.com (192.168.20.132) from 192.168.20.132 : 56(84) > bytes of data. > > Both hostnames resolve locally. So why is it telling me that the > virtual server doesn't exist when this is a no duh... of course it > doesn't exist, I'm trying to create it??? > ------------------------- 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 -----------------------------------------------------------------------------
