ISPConfig remoting plugin Beta 2 released

Well done ISPconfig team.

It's late now, but I will be playing with it 1st thing tomorrow.. That is.. If my server is up :-/

 

awesome, lookin forward to 2.3.0

 

I installed the latest ispconfig-dev and ISPConfig remoting plugin and it´s working very, very goooood!!! I am soooo haaaapppy! Thank you Till and Falko so much!!
I have one question. After I have added a user and a web remotely the apache (the server apache, not ispconfig apache port 81) is not restarted. Is this a known issue or how can I make it restart, so the changes takes affect?

 

Any errors in the Apache log? Any errors when you restart Apache?

 

I have 3 machines with Debian 3.1 and Ispconfig 2.3.0-dev. In one of them, I have Apache 2 and there is no problem with that one. In the two other machines I have apache 1.3, and apache is never restarted by ispconfig on them, but it is not working with ispconfig 2.2.0 either. Even if I try to stop and restart apache in services in ispconfig the apache is not restared. Only if i make a apachectl restart in cmd manually, apache is restarted without errors

Can It be that ispconfig i trying a apache2ctl restart on the machines, like the one working?

 

One record and it puts apache2 which is wrong. I changed to apache and now it's working! Do you think there is a bug in the installation that apache1.3 is recognized as apache2?

 

Do you have two Apache versions installed on the system, and was Apache2 running at the time you installed ISPConfig?

 

No, only one apache installed, apache2 has never been installated either in the machine but in debian by default, has the /etc/init.d/apache2 file installed. Perhaps the installation is locking for that file?

 

What's the output of

Code:

httpd -V

?

 

Code:

Server version: Apache/1.3.33 (Debian GNU/Linux)
Server built:   Sep  6 2005 13:10:30
Server's Module Magic Number: 19990320:16
Server compiled with....
 -D EAPI
 -D HAVE_MMAP
 -D HAVE_SHMGET
 -D USE_SHMGET_SCOREBOARD
 -D USE_MMAP_FILES
 -D HAVE_FCNTL_SERIALIZED_ACCEPT
 -D HAVE_SYSVSEM_SERIALIZED_ACCEPT
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D DYNAMIC_MODULE_LIMIT=64
 -D HARD_SERVER_LIMIT=4096
 -D HTTPD_ROOT="/usr"
 -D SUEXEC_BIN="/usr/lib/apache/suexec"
 -D DEFAULT_PIDLOG="/var/run/apache.pid"
 -D DEFAULT_SCOREBOARD="/var/run/apache.scoreboard"
 -D DEFAULT_LOCKFILE="/var/run/apache.lock"
 -D DEFAULT_ERRORLOG="/var/log/apache/error.log"
 -D TYPES_CONFIG_FILE="/etc/mime.types"
 -D SERVER_CONFIG_FILE="/etc/apache/httpd.conf"
 -D ACCESS_CONFIG_FILE="/etc/apache/access.conf"
 -D RESOURCE_CONFIG_FILE="/etc/apache/srm.conf"

 

The version is ok. Then it must be because we have Apache2 in dist.txt. not Apache 1.3, because on most distributions Apache 2 is the default now.

 

I would like to run apache2, but I heard that frontpage extension will not work?

 

We've tested Frontpage only with Apache 1.3. I don't know if it works on Apache2 because hardly anybody is using Frontpage nowadays. But you can have a look here: http://www.google.com/search?q=apac...ient=firefox-a&rls=org.mozilla:en-US:official