Debian4, New Install, Web Server won't start

Discussion in 'Installation/Configuration' started by BorderAmigos, Jun 14, 2008.

  1. BorderAmigos

    BorderAmigos New Member

    After messing up my Fedora install beyond repair I decided to start fresh with a different distro. Per recommendations here I installed Debian 4.0 (etch) from scratch according to "The Perfect Setup" instructions.

    Additionally I installed NVIDIA video drivers and Webmin.

    After installing ISPConfig DNS and Web-Server both show offline. Adjusting name server domains got DNS going. But I can't get Apache2 going still. Searching here for solutions, many of the directories mentioned don't seem to exist on my system. I re-installed ISPConfig with no change.

    I can access the IPConfig administration on 81 and the Webmin on 10000 without any problems.

    SuExec is disabled. Firewall is off for now.

    Here are some outputs...

    unable to start piped log program ' /usr/sbin/vlogger -s access.log /var/log/ispconfig/httpd': No such file or directory
    Unable to open logs

    (I created a new text file /var/log/ispconfig/httpd/access.log but it didn't help).

    > netstat -tap

    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
    tcp 0 0 *:50368 *:* LISTEN 3198/rpc.statd
    tcp 0 0 localhost:10025 *:* LISTEN 3446/master
    tcp 0 0 *:mysql *:* LISTEN 2730/mysqld
    tcp 0 0 *:sunrpc *:* LISTEN 2397/portmap
    tcp 0 0 *:webmin *:* LISTEN 3524/perl
    tcp 0 0 *:81 *:* LISTEN 3337/ispconfig_http
    tcp 0 0 *:auth *:* LISTEN 3031/inetd
    tcp 0 0 *:ftp *:* LISTEN 3504/proftpd: (acce
    tcp 0 0 host.servidora.n:domain *:* LISTEN 3483/named
    tcp 0 0 localhost:domain *:* LISTEN 3483/named
    tcp 0 0 localhost:ipp *:* LISTEN 2922/cupsd
    tcp 0 0 localhost:953 *:* LISTEN 3483/named
    tcp 0 0 *:smtp *:* LISTEN 3446/master
    tcp 1 0 localhost:smtp localhost:42251 CLOSE_WAIT -
    tcp 1 0 localhost:smtp localhost:42256 CLOSE_WAIT -
    tcp 0 1492 host.servidora.n:webmin cpe-72-130-158-54.:1359 ESTABLISHED4687/index.cgi
    tcp 1 0 localhost:smtp localhost:36669 CLOSE_WAIT -
    tcp6 0 0 *:imaps *:* LISTEN 2877/couriertcpd
    tcp6 0 0 *:pop3s *:* LISTEN 2896/couriertcpd
    tcp6 0 0 *:pop3 *:* LISTEN 2882/couriertcpd
    tcp6 0 0 *:imap2 *:* LISTEN 2865/couriertcpd
    tcp6 0 0 *:ssh *:* LISTEN 3123/sshd
    tcp6 0 0 ip6-localhost:953 *:* LISTEN 3483/named
    tcp6 0 0 *:smtp *:* LISTEN 3446/master

    > /etc/init.d/apache2 start

    Starting web server (apache2)...[Sat Jun 14 10:39:22 2008] [warn] NameVirtualHost has no VirtualHosts
    [Sat Jun 14 10:39:22 2008] [warn] NameVirtualHost has no VirtualHosts
    Last edited: Jun 14, 2008
  2. BorderAmigos

    BorderAmigos New Member

    I found the following in another thread and it seems to solve the issue...

    ... comment out the line Include /etc/apache2/sites-enabled/ in /etc/apache2/apache2.conf:

    # Include the virtual host configurations:
    #Include /etc/apache2/sites-enabled/
  3. mihai331

    mihai331 New Member


    I found in the sites-enabled directory a link, called ispconfig.conf (or something with isp in it's name)

    delete the link and apache2 will start working again.
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    You posted here in the ispconfig 2 forum but the file you deleted belongs to ISPConfig 3. So the question is, which ispconfig version did you install? ISPConfig 2 qnd 3 are completely different sotware packages which use different configurations.
  5. mihai331

    mihai331 New Member

    My mistake. I didn't notice that this thread was for ispconfig 2, but I had the same behavior of the webserver, and the solution was working fine.
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    No wonder that it dont workes. You can not install ispconfig 2 on a server that had ispconfig 3 installed or vice versa. You have to format the server and then reinstall it eaxctly as described in the perfect setup guide for the ispconfig version you use. If you did not follow the guides exactly, then your install will not work as not all system requiremenst are installed.

Share This Page