HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   General (http://www.howtoforge.com/forums/forumdisplay.php?f=15)
-   -   ISPConfig 2.2.1 released (http://www.howtoforge.com/forums/showthread.php?t=3640)

till 11th April 2006 21:59

ISPConfig 2.2.1 released
 
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
name@www.domain.com instead of name@domain.com. 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.


Download
--------

http://www.ispconfig.org/downloads.htm

Forums
------

http://www.howtoforge.com/forums


Installation Instructions
-------------------------

Download the ISPConfig-2.2.1.tar.gz from sourceforge.net

http://prdownloads.sourceforge.net/i...ar.gz?download


Installation on the shell as root User:

tar xvfz ISPConfig-2.2.1.tar.gz
cd install_ispconfig
./setup

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

Cirox 12th April 2006 00:05

Hi,

great work, guys :)

greetings cirox

danf.1979 12th April 2006 00:59

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:
PHP Code:

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
PHP Code:

All prerequisites are fulfilled.
Here we go...

Connected successfully to db isp_config

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

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

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

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

Warning
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
proftpd
.
 
done.
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

Warning
mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /root/ispconfig/scripts/lib/config.inc.php 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?

danf.1979 12th April 2006 01:34

Ok. So, this file is in /tmp/:
existing_db_04_11_2006__17_43_18.sql
So the following line works:
Code:

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?

adamluz 12th April 2006 01:41

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 ##########
[EDITED LICENCE CONTENT OUT OF POST]

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
Repeat.....

danf.1979 12th April 2006 01:55

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

danf.1979 12th April 2006 02:04

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

lyndros 12th April 2006 02:52

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

thks to all the ispconfig team

falko 12th April 2006 11:14

Quote:

Originally Posted by adamluz
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 ##########
[EDITED LICENCE CONTENT OUT OF POST]

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
Repeat.....

I experienced something like this on CentOS 4.3, and the solution was to change MySQL's init script as outlined here: http://www.howtoforge.com/perfect_setup_centos_4.3_p4
Given that Fedora and CentOS are very similar, you might have to do the same.

adamluz 13th April 2006 01:09

Quote:

Originally Posted by falko
I experienced something like this on CentOS 4.3, and the solution was to change MySQL's init script as outlined here: http://www.howtoforge.com/perfect_setup_centos_4.3_p4
Given that Fedora and CentOS are very similar, you might have to do the same.

Thanks

In /etc/init.d/mysqld

I changed:
restart(){
stop
start
}

to

restart(){
stop
sleep 3
start
}

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


All times are GMT +2. The time now is 10:01.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.