Hey guys! Running into a huge issue that has me pulling my hair out! Ubuntu 12.04 x64 Ubuntu 12.04.5 LTS (Precise Pangolin)) ISPConfig 3.0.5.4p3 Okay so I have 3 vps's One with perfect server 12.04 Ubuntu- Works fine no issues- installed almost 5 months ago, Perfect server centos 6.5 -works fine New vps Perfect server 12.04 installs and breaks The guide I am following is http://www.howtoforge.com/perfect-server-ubuntu-12.04-lts-apache2-bind-dovecot-ispconfig-3 What is happening The install works fine, No errors I restart the vps and nothing works I have to manually use a serial console from my vps and enable services 1 at a time service ssh restart service mysql restart service apache2 restart Once I do this I am now able to access the server from webpage and ssh I have done the install 5 times and the same thing happens What can cause this? How can I troubleshoot this? Am I missing something? Code: cat htf_report.txt | more ##### SERVER ##### IP-address (as per hostname): ***.***.***.*** [WARN] could not determine server's ip address by ifconfig [INFO] ISPConfig is installed. ##### ISPCONFIG ##### ISPConfig version is 3.0.5.4p3 ##### VERSION CHECK ##### [INFO] php (cli) version is 5.3.10-1ubuntu3.13 ##### PORT CHECK ##### [WARN] Port 143 (IMAP server) seems NOT to be listening [WARN] Port 993 (IMAP server SSL) seems NOT to be listening [WARN] Port 110 (POP3 server) seems NOT to be listening [WARN] Port 995 (POP3 server SSL) seems NOT to be listening [WARN] Port 25 (SMTP server) seems NOT to be listening [WARN] Port 465 (SMTP server SSL) seems NOT to be listening [WARN] Port 21 (FTP server) seems NOT to be listening [WARN] Port 25 (SMTP server) seems NOT to be listening ##### MAIL SERVER CHECK ##### ##### RUNNING SERVER PROCESSES ##### [INFO] I found the following web server(s): Apache 2 (PID 1195) [WARN] I could not determine which mail server is running. [WARN] I could not determine which pop3 server is running. [WARN] I could not determine which imap server is running. [WARN] I could not determine which ftp server is running. ##### LISTENING PORTS ##### (only () Local (Address) [anywhere]:443 (1195/apache2) [anywhere]:3306 (845/mysqld) [anywhere]:8080 (1195/apache2) [anywhere]:80 (1195/apache2) [anywhere]:8081 (1195/apache2) [anywhere]:22 (797/sshd) *:*:*:*::*:22 (797/sshd) ##### IPTABLES ##### Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination
Thank you for the reply Something seems to be causing these not to start I tried that command again and it appears to be working but I restart and still have to manually go through my vps control panel and restart ssh I installed rcconf apt-get install rcconf And it appears everything was already set to start I restarted and everything was working again! I restarted again and everything was broken again.... So it appears something is stalling these from starting or causing them not to start at all I want to say the issue starts as soon as I add the first page on the sites tab of isp config.... Still doing more testing/research Any help would be greatly appreciated oh ya also wanted to add this also happens on the debian wheezy install
Then there migh be a issue with your vps or they have not enough ram. We maintain so many ubuntu and wheezy servers fou or clients and not a single one has a tart issue on any service.
Thank you for your reply Yes my main server works just fine but I installed that in april Using ubuntu 12.04 apache2 guide I have confirmed this issue happens as soon as I add the first website I have also had my friend try with his vps using the debian wheezy and his also breaks right after adding the first site I understand you have this install working on several for several clients, My one install works just fine Any new debian/ubuntu install with the newest ispconfig install is breaking for me. Have you had a successful install within the last few weeks? Last couple days? Also on a new install, if this helps update-rc.d: warning: ssh stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (none) Adding system startup for /etc/init.d/ssh ... /etc/rc0.d/K20ssh -> ../init.d/ssh /etc/rc1.d/K20ssh -> ../init.d/ssh /etc/rc6.d/K20ssh -> ../init.d/ssh /etc/rc2.d/S20ssh -> ../init.d/ssh /etc/rc3.d/S20ssh -> ../init.d/ssh /etc/rc4.d/S20ssh -> ../init.d/ssh /etc/rc5.d/S20ssh -> ../init.d/ssh
Code: Setting up sysv-rc-conf (0.99-6) ... root@vps:~# sysv-rc-conf apache2 on root@vps:~# sysv-rc-conf ssh on root@vps:~# sysv-rc-conf --list ssh ssh 0:off 1:off 2:on 3:on 4:on 5:on 6:off root@vps:~# reboot root@vps:~# initctl list mountall-net stop/waiting nmbd stop/waiting passwd stop/waiting rc stop/waiting screen-cleanup stop/waiting tty4 stop/waiting udev start/running, process 142 upstart-udev-bridge start/running, process 139 hwclock-save stop/waiting plymouth-log stop/waiting rpcbind-boot stop/waiting smbd stop/waiting tty5 stop/waiting failsafe stop/waiting dbus start/running, process 143 mounted-var stop/waiting plymouth stop/waiting portmap stop/waiting ssh start/running, process 1027 udev-fallback-graphics stop/waiting control-alt-delete stop/waiting hwclock stop/waiting mounted-proc stop/waiting module-init-tools stop/waiting shutdown stop/waiting cron stop/waiting mountall stop/waiting mounted-debugfs stop/waiting xinetd stop/waiting console stop/waiting mounted-run stop/waiting bluetooth stop/waiting plymouth-stop stop/waiting rcS stop/waiting wait-for-state stop/waiting flush-early-job-log stop/waiting rc-sysinit stop/waiting upstart-socket-bridge start/running, process 233 tty2 stop/waiting udevtrigger stop/waiting container-detect start/running mounted-dev stop/waiting tty3 stop/waiting udev-finish stop/waiting dovecot stop/waiting hostname stop/waiting mountall-reboot stop/waiting mysql stop/waiting mountall-shell stop/waiting mounted-tmp stop/waiting network-interface (venet0) start/running network-interface (lo) start/running plymouth-ready stop/waiting plymouth-splash stop/waiting plymouth-upstart-bridge stop/waiting portmap-wait stop/waiting tty1 stop/waiting udevmonitor stop/waiting network-interface-security (network-interface/venet0) start/running network-interface-security (network-interface/lo) start/running network-interface-security (networking) start/running networking stop/waiting procps stop/waiting tty6 stop/waiting network-interface-container stop/waiting I have already spoke with my vps provider a little while ago, They said to make sure everything was set to start and referred me back to ispconfig documentation
Its a issue with your vps. The start of services is not even alterd nor managed by ispconfig. If a service starts or not si solely handled by your vps and the operating system start scripts. ispconfg does nothing at all boot time. Like I mentind above, I install such servers daily so I had several successfull installs this week for customers and they are all working, so its not a problem related to ispconfig. To be more exact, there had been more then 10 thousand successfull installs of the latest version. If there would be such an issue, then you could fin here a few hundred posts on that issue for the past week, which is not the case.
What you can do is to ask your host if their vps have problems with bind mounts in /etc/fstab. A bind mount is a mountpoint were you poit directory a to directory b at mount level in fstab. This works normally fine but maybe your vps provider managed to block this somehow.
Thank you Till! Okay update So it appears my fstab file was causing an issue Original Code: proc /proc proc defaults 0 0 none /dev/pts devpts rw,gid=5,mode=620 0 0 none /run/shm tmpfs defaults 0 0 /var/log/ispconfig/httpd/example.com /var/www/clients/client1/web2/log none bind,nobootwait,netdev_ 0 0 Changed to Now everything is working. So it appears _netdev is causing the issue. My understanding is This means that the filesystem resides on a device that requires network access, and it is used to prevent the system from attempting to mount these filesystems until the network has been enabled on the system. Is it to much of a problem to remove this? Is this something Im doing wrong? Or is this an issue with my vps?
