ISPConfig 2.2.21 released

[mccharlet]

update 2.19 to 2.21 on debian etch

OK

[tensor]

Running .21 for some time now. No new problems.

[Rockdrala]

--- INFO ---

Ok i can create a new Remoting User again after i reinstall the remoting plugin after the update to 2.21.
This raises some concerns becuase it seems that it wiped out my old Remoting Users and they may be leaving dead remote user fields in the iscponfig DB.

[swieep]

Hi,

I upgraded 2 day's ago to 2.2.21 on 2 servers. It looked everything went ok.

Then I got into trouble with clamav and spamassassin.

I installed the clamavd (thank you Morons) and the problems where less severe.

Now today the customers where calling, roundcube was not working and all websites where down.

When I finally was logged in with ssh, the server was only helping spamassassin. average load was 164.xx!!

Trying to fix it I used the mysql query found in one thread:

update isp_isp_user set user_spamfilter = 0, status = 'u' WHERE 1

But when I start postfix, spamassassin is still used and within no time the server becomes unresponsive.

setup: ubuntu 7.04 server, up2date with apt-get before the upgrade to ispconfig 2.2.21, 1 CPU Celeron D, 3,33Ghz on a dell poweredge 860, kernel: 2.6.20-15-server

[till]

To disable spamassassin, you will have to edit one user in the ispconfig interface and click on save after you chnaged the ispconfig database. Otherwise the changes were not written to the config files.

[swieep]

Originally Posted by till

To disable spamassassin, you will have to edit one user in the ispconfig interface and click on save after you chnaged the ispconfig database. Otherwise the changes were not written to the config files.

Thank you, I will update/save a user..

Ofcourse I want to use spamassassin.. is there a solution so I can enable it again, it worked up to 2.2.1x..

[rafael-ec]

I have version 2.2.18 in CentOS 4.6 up to date. I saw there where problemas updating to version 2.2.19, would I have this problems if I update to 2.21?

Regards,

Rafael

[LumpyOne]

Just upgraded from 2.2.1 --> 2.2.21 and now my server is not responding at all. Here was the last message I had. Any clues as to what my next step should be?

[falko]

Originally Posted by LumpyOne

Just upgraded from 2.2.1 --> 2.2.21 and now my server is not responding at all. Here was the last message I had. Any clues as to what my next step should be?

Can you log in using SSH? What's the output of

netstat -tap

?

[falko]

Originally Posted by rafael-ec

I have version 2.2.18 in CentOS 4.6 up to date. I saw there where problemas updating to version 2.2.19, would I have this problems if I update to 2.21?

You mean because of ClamAV? These problems have been fixed.