ISPConfig 2.2.1 released

Discussion in 'General' started by till, Apr 11, 2006.

  1. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig 2.2.1 is available for download.

    This release adds support for Fedora Core 5 and CentOS 4.3,
    clamassassin was added (replaces trashscan) and many bugs
    were fixed.

    Detailed Changelog

    - New: Added support for Fedora Core 5.
    - New: Added support for CentOS 4.3.
    - Update: Update of the Italian translation.
    - Update: Replaced trashscan with clamassassin.
    - Update: Updated ClamAV to version 0.88.1.
    - Bugfix: Server hostname is now recognized correctly in ISPConfig interface.
    - Bugfix: Added some patches for more secure passwords.
    - Bugfix: Create backup of existing ISPConfig installation in case of an update.
    - Bugfix: When a client deletes a user from the recycle bin, the user is now
    removed from /etc/passwd and /etc/shadow correctly.
    - Bugfix: Default MX records now use the full hostname of the system.
    - Bugfix: ISPConfig userdb passwords do not show up in logfile anymore.
    - Bugfix: Missing newline at end of named.conf.
    - Bugfix: Partitions are now shown correctly even with LVM partitions.
    - Bugfix: Web space statistics: Usages of more than 1 GB are now shown as GB, not KB.
    - Bugfix: Logsplit does not fail for "localhost" records anymore.
    - Bugfix: Firewall and monitoring rules do not disappear anymore after an update.
    - Bugfix: Removal of web groups is now working.
    - Bugfix: The email addresses were shown with the full hostname. Example
    [email protected] instead of [email protected]. This has been fixed.
    - Bugfix: The monitoring summary (Management -> Server -> Services -> Monitoring)
    now displays the port numbers that are monitored.
    - Bugfix: /root/ispconfig/uninstall does now delete the ISPConfig entries from the
    Apache configuration.



    Installation Instructions

    Download the ISPConfig-2.2.1.tar.gz from

    Installation on the shell as root User:

    tar xvfz ISPConfig-2.2.1.tar.gz
    cd install_ispconfig

    The installer automatically detects the installed ISPConfig version and performs an update.
  2. Cirox

    Cirox New Member


    great work, guys :)

    greetings cirox
  3. danf.1979

    danf.1979 Member

    I got problems here:
    ISPConfig db has now cero tables. I thought It was a problem with my character collation in ispconfig db. I had utf8 and this lines in the mysql class constructor:
    mysql_query("SET character_set_client = 'latin1'");
    mysql_query("SET character_set_results = latin1");
    mysql_query("SET character_set_connection = utf8"); 
    As with the update my db got dead, I decided to take out those lines and define ispconfig db as latin1. I did that and then uploaded a sql backup and began updating again. Same result. The database is there, but there are no tables. Also, the db dump found on /tmp did nothing for me. i had to use my own backup.

    Here are the errors, but they say nothing really important
    All prerequisites are fulfilled.
    Here we go...

    Connected successfully to db isp_config

    mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/dan/src/install_ispconfig/install.php on line 776

    mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/dan/src/install_ispconfig/install.php on line 781

    mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/dan/src/install_ispconfig/install.php on line 791

    mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/dan/src/install_ispconfig/install.php on line 808

    mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/dan/src/install_ispconfig/install.php on line 1114
    Restarting some services
    usr/sbin/apachectl restarthttpd restarted
    Stopping Postfix Mail Transport Agent...                                                                                          [ ok ]
    Starting Postfix Mail Transport Agent...                                                                                          [ ok ]
    Restarting ProFTPD ftp daemon.proftpd.
    .. - 
    mod_tls/2.0.7using OpenSSL 0.9.7g 11 Apr 2005
    parsing '/etc/proftpd.conf' configuration
    parsing '/etc/proftpd_ispconfig.conf' configuration
    Shutting down ISPConfig system...
    root/ispconfig/httpd/bin/apachectl stophttpd (no pid filenot running
    ISPConfig system stopped
    Starting ISPConfig system...
    root/ispconfig/httpd/bin/apachectl startsslhttpd started

    mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /root/ispconfig/scripts/lib/ on line 47
    No results found
    !ISPConfig system is now up and running!
    CongratulationsYour ISPConfig system is now installed. If you had to install quotaplease take the steps described in the installation manualOtherwise your system is now available without reboot.
    Anything to check?
  4. danf.1979

    danf.1979 Member

    Ok. So, this file is in /tmp/:
    So the following line works:
    caselog("cp -f existing_db.sql /tmp/existing_db_".date("m_d_Y__H_i_s", $current_date).".sql", $FILE, __LINE__,"copied existing_db.sql to /tmp/existing_db_".date("m_d_Y__H_i_s", $current_date).".sql"
    Could it be the -f option?
    I read in man cp:
    -f, --force
    if an existing destination file cannot be opened, remove it and
    try again
    Could that be why I can't find anywhere the existing_db.sql file?
  5. adamluz

    adamluz New Member

    Error - Mysql keeps shutting down

    Everytime I try to install the upgrade mysql dies...

    [root@fc4 install_ispconfig]# service mysqld restart
    Stopping MySQL: [FAILED]
    Starting MySQL: [ OK ]
    [root@fc4 install_ispconfig]# service mysqld status
    mysqld (pid 28397) is running...

    Mysql will run all night until

    [root@fc4 install_ispconfig]# ./setup
    Fedora 4.0

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

    ERROR: MySQL is not running! Please start your MySQL database and run the ISPConfig setup again.
    [root@fc4 install_ispconfig]# service mysqld status
    mysqld dead but subsys locked
    [root@fc4 install_ispconfig]# service mysqld restart
    Stopping MySQL: [FAILED]
    Starting MySQL: [ OK ]
    [root@fc4 install_ispconfig]# ./setup
  6. danf.1979

    danf.1979 Member

    Buh, I think it was because I decompressed the files as my user and not root. I'm running the update again... :eek:
  7. danf.1979

    danf.1979 Member

    Buh, I think it was because I decompressed the files as my user and not root. I'm running the update again... :eek:
  8. lyndros

    lyndros New Member

    great work u all guys,
    with people like u is a pleasure :p

    thks to all the ispconfig team
  9. falko

    falko Super Moderator Howtoforge Staff

    I experienced something like this on CentOS 4.3, and the solution was to change MySQL's init script as outlined here:
    Given that Fedora and CentOS are very similar, you might have to do the same.
  10. adamluz

    adamluz New Member


    In /etc/init.d/mysqld

    I changed:


    sleep 3

    and that fixed everything. Thought I would post it here for quicker results when searching.
  11. fobicodam

    fobicodam New Member

    Mx Big Error !!!

    I found a big mistake when you create the domain zone !!! you create this:

    A record

    MX record www

    This is wrong !!! if you do that:

    1.- No email will be served to this server !! if you send a mail to [email protected] its rejected couse there are no MX for !! you must send emails to [email protected] !!! :eek:
    2.- No client want to see their provider hostname on their MX record :mad:

    How can i fix it?!?!?!!!
  12. till

    till Super Moderator Staff Member ISPConfig Developer

    There is no error or bug at all. Go to the ISPConfig DNS-Manager and have a look at the SOA for your domain, I'am pretty sure that there is "www" in the hostname field of the MX record. Remove it and hit save :)

    Does your website in DNS-Manager has a co-domain with empty host and you checked the create MX option in the settings of the co-domain?

    2) I know some providers that needs hostanmes in MX records.

Share This Page