View Single Post
  #4  
Old 21st February 2013, 09:51
till till is online now
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,811
Thanks: 821
Thanked 5,339 Times in 4,188 Posts
Default

The quota setup is the same for apache and nginx, so there is no difference in this regard.

Quote:
Should i skip step 15:
No. You just skip the editing of the /etc/fstab file.

Quote:
One more thing. When i try to do this in step 21: insserv -r apache2
I get this error: insserv: warning: script is corrupt or invalid: /etc/init.d/../rc6.d/S00vzreboot
Thats ok and can be ignored.

Quote:
And then when i try to restart nginx, i get this:
Restarting nginx: nginxnginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()
There is already a software running on post 80. Run:

netstat -tap

to see which software runs there and stop it before you start nginx.

Quote:
Should i try more with nginx or should i go for apache2?
Nginx is fast but its not as easy to use then apache, especially .htaccess files do not work with nginx, so if any of your sites use .htaccess, you will have to write new rules for nginx and insert them in the nginx directives field of the website.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote