ISPConfig 2.2.21 released

Discussion in 'General' started by till, Feb 12, 2008.

  1. mccharlet

    mccharlet Member HowtoForge Supporter

    update 2.19 to 2.21 on debian etch

    OK
     
  2. tensor

    tensor New Member

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

    Rockdrala New Member

    --- 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.
     
  4. swieep

    swieep New Member

    Spamassassin CPU usage. server not responding. mysql connections killed.

    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
     
    Last edited: Feb 28, 2008
  5. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    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.
     
  6. swieep

    swieep New Member

    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..
     
  7. rafael-ec

    rafael-ec New Member

    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
     
  8. LumpyOne

    LumpyOne New Member

    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?
     

    Attached Files:

  9. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    Can you log in using SSH? What's the output of
    Code:
    netstat -tap
    ?
     
  10. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    You mean because of ClamAV? These problems have been fixed. :)
     
  11. LumpyOne

    LumpyOne New Member

    Nope. The connection just hangs and never connects. The server is pinging, just not responding to anything else. It will require a hard-reboot at this point.
     
  12. t-mug

    t-mug New Member

    Update OK

    Wanted to say to Till and Falko: thank you for good work. Updating from 2.2.13 to 2.2.21 has worked fine.

    Before running the setup script I've executed this as fallback:
    Code:
    #!/bin/sh
    #
    # Backup script for ISPConfig-2.x.x installations
    # It should be executed before updating inside the 2.x.x branch
    # from one version to a higher one.
    #
    # After executing you get a minimum data collection to be able to revert
    # the update process by hand in case an update to a higher 2.x.x version 
    # of ISPConfig fails.
    #
    # This script is !! NOT !! backing up any www-data or other configuration 
    # files, that are necessary to run an ISPConfig Server!!
    #
    BKPDIR=bkp-ispconfig_$(date +%F--%H-%M)
    [ -d $BKPDIR ] || mkdir $BKPDIR
    echo '1.) Backing up /home/admispconfig to file home_admispconfig.tar ...'
    tar cpf  $BKPDIR/home_admispconfig.tar --exclude='*/temp/*' /home/admispconfig && echo '   home_admispconfig.tar ==> OK'
    echo '2.) Backing up /root/ispconfig to file root_ispconfig.tar ...'
    tar cpf  $BKPDIR/root_ispconfig.tar /root/ispconfig && echo '   root_ispconfig.tar ==> OK'
    echo '3.) Backing up ISPConfig database 'db_ispconfig' to file db_ispconfig.sql'
    echo 'Password for mysql root is required'
    mysqldump -p -u root db_ispconfig >  $BKPDIR/db_ispconfig.sql && echo '   db_ispconfig.sql ==> OK'
    echo
    echo 'IF YOU CAN SEE 3 TIMES THE "==> OK" MESSAGE THEN YOU SHOULD BE SAFE.'
    echo 'ANYWAY: CHECK NOW THE 3 FILES BY HAND - AND THEN PERFORM YOUR UPDATE.'
    echo
    echo Backup directory is: $BKPDIR
    ls -lh $BKPDIR
    Well, this is surely not perfect but executing something like this before the official setup script makes me feel better while updating.
     
    Last edited: Mar 16, 2008

Share This Page