Hi River, With regards to getting Apache working on the host, try this...
open up /etc/httpd/conf/httpd.conf comment out any "BindAddress" or "Port" directives and put in... Listen 11.22.33.44:80 Listen 11.22.33.44:443 Where 11.22.33.44 is the IP address of your host server For more see... http://httpd.apache.org/docs/mod/core.html#listen I think that Apache does not load for you at the moment as it cannot "lock" all the IP addresses returned by ifconfig and so just refuses to start up! With regards to proftpd and wu-ftp, ive heard that pro is a faster and more secure. Hope this helps. Ben Kennish [EMAIL PROTECTED] ----- Original Message ----- From: "River Hume" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 18, 2002 5:47 PM Subject: RE: the continuing saga... Thanx Tim :) this is making more and more sense to me now... This does mean that the same binarys must exist on the hosting server as in >the skels. The default skels use ProFTPd whereas a default RedHat >installation uses wu-ftp. This has the effect of 'breaking' ftp services for >the hosting server unless ProFTP has been installed (or you could create a >softlink which points to the wu-ftp binary). The same can happen for other >services depending on how your hosting server is configured. that explains why ftp services are broken, but apache isn't even responding on the master host address or ip anymore... Also, I think I like the idea of setting up a softlink to wu-ftp (unless there's any particular advantage to proftp) but I have no idea how. A little help, or at least a pointer to relevant documentation would be greatly appreciated. >The listening address of services (being run in daemon mode) on the hosting >server can also cause a problem. Typically a Linux server is given multiple >IP aliases on a network and would be expected to service requests on all the >addresses. This is reflected by the default configuration of most services >on the hosting server (ssh for example) to bind to all available IP >addresses. This conflicts with the way VSD needs to work where each service >should only bind to its specific IP address - otherwise the service on the >hosting server will handle requests intended for a different instance of the >service within the virtual private servers. wouldn't that break the virtual servers though? my virtual servers work, it's my master server that's broken... could this still somehow be an issue for me? are the master server services just broken at this point because their default configuration has been overridden by vsd? > > 2. bevs is not working. I can't even get in to set the admin pass... > > > > [root@eatseek ganjuror]# bevs binaryaxiom > > -- cannot read server map file: No such file or directory > > any thoughts on this one? this is key... Thanx again -River ------------------------- 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 -----------------------------------------------------------------------------
