ISPConfig 2.2.16 released

Solved: some premissions were bad

Thanks for the info, but it happens on every mailbox, no matter the quota.

I managed to find the error, there were some missplaced permissions in daily.inc (files daily.info, daily.ndb and daily.ndu):

Code:

root@bombo:/home/admispconfig/ispconfig/tools/clamav/share/clamav ;)$ ls -l daily.inc/
total 1376
-rwxr-xr-x 1 admispconfig admispconfig  17992 2007-08-30 02:30 COPYING
-rwxr-xr-x 1 admispconfig admispconfig     58 2007-08-30 02:30 daily.cfg
-rwxr-xr-x 1 admispconfig admispconfig  25207 2007-08-30 02:30 daily.db
-rwxr-xr-x 1 admispconfig admispconfig   3440 2007-09-03 09:33 daily.fp
-rwxr-xr-x 1 admispconfig admispconfig   3349 2007-09-02 05:55 daily.hdb
-rwxr-xr-x 1 admispconfig admispconfig    234 2007-08-30 02:30 daily.hdu
-rw------- 1 admispconfig admispconfig    586 2007-09-08 07:06 daily.info
-rwxr-xr-x 1 admispconfig admispconfig 905329 2007-09-08 07:06 daily.mdb
-rwxr-xr-x 1 admispconfig admispconfig   9111 2007-09-04 11:58 daily.mdu
-rw------- 1 admispconfig admispconfig 391130 2007-09-08 07:06 daily.ndb
-rw------- 1 admispconfig admispconfig    623 2007-09-04 14:22 daily.ndu
-rwxr-xr-x 1 admispconfig admispconfig   2517 2007-08-31 19:40 daily.pdb
-rwxr-xr-x 1 admispconfig admispconfig    755 2007-08-30 02:30 daily.wdb
-rwxr-xr-x 1 admispconfig admispconfig   2922 2007-09-03 21:34 daily.zmd

by changing the permissions to 755 in daily.inc/* it has started working again.

I know that freshclam is the updater of these files, but what changed the permissions? was not the update to 2.2.16? I'm a bit confused with this error.

 

Upgrade freeze under Ubuntu feisty fawn 7.04

When upgrading from 2.2.14 to 2.2.16, it says that all is OK :

########## INSTALLATION ##########

Preparation des fichiers. Merci de patienter quelques instants...

But it stops here ... and nothing else ! (i've waited 15 minutes and nothing...)
CTRL + C and it goes as it was before. No update is made.
I run the ./setup as root.

any idea ?

 

OK, I inadvertently DID start the upgrade process more than once when I lost my connection... What should I do, now?

Everything (apart from ISPconfig itself) is still working, at the moment.

 

Error updating

Hi,

I updated mi red-hat 4.0 system after changing the /etc/red-hat-release to centos 5.0 and after lots of messages the process aborted.

I include the file /var/log/ispconfig_install.log

View attachment ispconfig_install.txt

Any ideas what went wrong?

I tried to find the backup copy done by the install process and could not find it in the system. can you tell me where is it done?

 

Well, I left it after selecting the language - or was there another step? - anyway, the main compilation phase. When I came back, my remote connection had dropped. Can I recover it from there?

Alternatively, if I have to reinstall will I lose all the settings, etc?

 

thios is the output of the df -h

[root@activa8 ~]# df -h
S.ficheros Tamaño Usado Disp Uso% Montado en
/dev/mapper/VolGroup00-LogVol00
132G 11G 115G 9% /
/dev/cciss/c0d0p1 99M 13M 82M 14% /boot
none 1,5G 0 1,5G 0% /dev/shm
[root@activa8 ~]#

There are 115 Gb. free.

 

Thank you very much ! It worked !

 

I've got a question. I've got some manually edited info in my vhosts file (SSL info that didn't want to work with ISPConfig, so I edited manually). I know that some things will get messed up when I update ISPConfig. If I make a backup of the vhosts file, then restore that file after the upgrade to ISPConfig, will that be the only thing I need to do to keep what I currently have? Do I need to backup and restore any DB files?

Thanks.

 

You never should edit manually your vhost file, because this file is managed by the ISPConfig system.
Everything you edit there manually will be overwritten/deleted when you:

- add a website within ISPConfig
- change a setting within ISPConfig for a website
- upgrade ISPConfig

So, editing your vhost file is not a solution and must be avoided.
If you tell us why you had to edit the vhost file for your SSL certificate, we can try to find a different solution.

 

The ssl part of the file (port 443 info) wasn't being added.

Here's the thread in question:

http://www.howtoforge.com/forums/showthread.php?t=12955


Brian

 

Did you enable SSL for that website already before you have installed your SSL-certificate?

I ask you this because, also without a SSL-certicate the :443 entries must appear within the vhost file and you are able to visit your SSL-site with https:// instead of http.

So, i like to suggest to do the following:
- Copy the content of the SSL-request AND SSL-certicate fields within a texteditor.
- Remove the CSR/SSL certicate within ISPConfig
- Disable SSL for that website and press save on the basis tab.
- Enable SSL for that website and press save on the basis tab.
- Check your vhost file, to see if the :443 entries are added.
- If so and after that, copy and paste your CSR and SSL certicate from your texteditor within the SSL-request & SSL certificate field again.
- Install the SSL-certicate and press save when you return on the basis tab.

 

After enabling the SSL again for the site, I get 3 vhost_ISPConfig.conf files. One named Vhost_ISPConfing.conf, 1 named Vhosts_ispconfig.conf_24-09-07_21-53-44 and 1 named Vhosts_ispconfig.conf_24-09-07_21-53-46.


The files with the dates and times do have the SSL (port 443) directives in them...the Vhosts_ispconfig.conf file does not.

 

This means that you have a syntax error within ISPConfigs' vhost file.
The result is that ISPConfig can not update the vhost file.
For this reason ISPConfig creates extra vhost files with a date/time stamp within the filename.

Have a look here as well:
http://www.howtoforge.com/forums/showthread.php?t=15712&highlight=syntax+error

 

Thanks...that did the trick. The ssl file was named domain.com when the vhosts file was looking for www.domain.com.

Now, i just need to re-install clamv. I thought I'd have to do without updates since I changed manually my vhost file, so I replaced clamv with clamd back a few versions of ISPConfig ago (when clamv was using up cpu power). Of course, I had forgotten that I had done that until I go errors on the ISPConfig update that it couldn't find clamv!

Oops!

Thanks again.