After a mass of hardware troubles the centos is laid down and the ispconfig3 install is proceeding. I have the old servers dbispconfig database on backup. I'm hoping to save a little time and restore that file once the install is done. i will back up the original. Any possible issues with that since the old dbispconfig db was from a 5.6 centos system running mysqld 5.077?
The previous question is moot. I've restored the database and the app still works. I'm still in the dark how to make DNS work from inside the app, but need to review the configuration files before crying "help" Pretty robust if I do say so myself.
Seems i have a bit of a bug problem with the centos 6.0 process /usr/local/ispconfig/server/server.sh Its in cron but its not on the system. I'm also running into trouble migrating the configuration from the 5.6 server to the 6.0 server. I don't know if I should restore the soft links or not. The database was easy to migrate Script is found in second try install inspired by CentOS becoming unbootable. Strange. Looking for guidance on how to migrate my database. Soft links appear to be a problem. I'm thinking maybe the database structure or records are little different and I have to manually key in my data. Inquiring minds want to know.
The smoke has cleared and everything is working but squirrelmail. Error message is: ERROR: Connection dropped by IMAP server. when I use info@localhost as username I've looked at a few threads. http://www.howtoforge.com/forums/showthread.php?t=41068 These make me wonder about: [root@mercury oldvar]# cat /etc/postfix/mysql-virtual_domains.cf user = ispconfig password = 777aa60c2d727a4e41b8b526f744979b dbname = dbispconfig table = mail_domain select_field = domain where_field = domain additional_conditions = and active = 'y' and server_id = 1 Maybe there is something that needs to be done with the password. mysql> select domain from mail_domain; +-------------------------+ | domain | +-------------------------+ ....snip..... | tehillimsongs.com | | woordridgeapartment.com | +-------------------------+ 16 rows in set (0.00 sec) mysql> desc mail_domain; +----------------+------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +----------------+------------------+------+-----+---------+----------------+ | domain_id | int(11) unsigned | NO | PRI | NULL | auto_increment | | sys_userid | int(11) unsigned | NO | | 0 | | | sys_groupid | int(11) unsigned | NO | | 0 | | | sys_perm_user | varchar(5) | NO | | | | | sys_perm_group | varchar(5) | NO | | | | | sys_perm_other | varchar(5) | NO | | | | | server_id | int(11) unsigned | NO | MUL | 0 | | | domain | varchar(255) | NO | MUL | | | | active | enum('n','y') | NO | | NULL | | +----------------+------------------+------+-----+---------+----------------+ 9 rows in set (0.00 sec) mysql> select domain_id,domain,server_id,active from mail_domain; +-----------+-------------------------+-----------+--------+ | domain_id | domain | server_id | active | +-----------+-------------------------+-----------+--------+ ...snip.... | 19 | linuxauthority.com | 1 | y | | 20 | newdatacloud.com | 1 | y | +-----------+-------------------------+-----------+--------+ 16 rows in set (0.00 sec) I did not migrate that file from the old setup, but it looks like its reading a particular table. My migration method was as follows for the record. I did a clean install. I rebuilt the soft links in /etc/httpd/conf/sites-enabled Copied across the content in /etc/httpd/conf/sites-available Restored the dbispconfig database from backup with mysql down. I've got all the data and I'm seeing new mail piling up in /var/vmail Looking for a little help with what is ailing squirrelmail. /var/log/maillog right after a login attempt. Sep 4 17:40:01 mercury postfix/smtpd[321]: disconnect from localhost[::1] Sep 4 17:42:29 mercury imapd: Connection, ip=[::1] Sep 4 17:45:01 mercury imapd: Connection, ip=[::1] Sep 4 17:45:01 mercury imapd: Disconnected, ip=[::1], time=0 Sep 4 17:45:01 mercury pop3d: Connection, ip=[::1] Sep 4 17:45:01 mercury pop3d: Disconnected, ip=[::1] Sep 4 17:45:01 mercury postfix/smtpd[479]: connect from localhost[::1] Sep 4 17:45:01 mercury postfix/smtpd[479]: lost connection after CONNECT from localhost[::1] Sep 4 17:45:01 mercury postfix/smtpd[479]: disconnect from localhost[::1] [root@mercury oldvar]# netstat -nap | grep ":143 " tcp 0 0 :::143 :::* LISTEN 32451/couriertcpd All services seem to be running fine. Realizing it is a weekend I'm going over the install document again to see if I missed anything. http://www.howtoforge.com/perfect-server-centos-6.0-x86_64-ispconfig-3-p6 Other variances that could be important. # SSL Configuration #SSLEngine On #SSLCertificateFile /usr/local/ispconfig/interface/ssl/ispserver.crt #SSLCertificateKeyFile /usr/local/ispconfig/interface/ssl/ispserver.key Was changed in 000-ispconfig.vhost When the following error occurred: Starting httpd: Syntax error on line 48 of /etc/httpd/conf/sites-enabled/000-ispconfig.vhost: SSLCertificateFile: file '/usr/local/ispconfig/interface/ssl/ispserver.crt' does not exist or is empty The file is indeed empty. hoping this helps. I will try mail reader other than squirrelmail when some more time presents itself. Also having some issues running Joomla 1.7 sites. White screen occurs, probably due to incorrect settings. Regards, Update: Joomla issues are resolved. Merely had to pick the right default php to make it work. I am documenting as I go. If I fix squirrelmail, I'm in good shape. I guess I would be better off if I found those crt files. I don't know if that is wreckage from my migration methodology or what.
I managed to fix this on my own. Here is the scoop. I ran update.php and generated a new ssl certificate to allow the SSL code to go back into production. The squirrelmail issue was a little more complex. Remember my migration methodology. Well the passwords on all the users stopped working. The users were created in ISCPCONFIG 3.0 on a Centos 5.6 system. My migration methodology involved restoring the dbispconfig mysql database from a back up after the install. Reset the password on the user and the IMAP drop problem goes away. I am guessing the password encryption/decryption technology was updated or perhaps it was the fact I was running squirrelmail in insecure mode. I was running it that way because the SSL certification messages from the browsers confused my wife and 12 year old, both of whom use accounts on the server. I'd like to provide any information that can shed further light on this subject. Ubuntu provides a stable major version upgrade process. RH does not, they recommend cold install and that is what I did. I'd like to help develop migration methodology. I don't pay for this product and I don't expect fast support, but I think its a good product and would like to help as time permits.
ispconfig3 and centos6 (64bits) troubles After following the instructions on: http://www.howtoforge.com/perfect-server-centos-6.0-x86_64-ispconfig-3 I have succesfully have a working system. >> During the installation I got some errors and warnings, not sure if that was all very importent yet. FTP, http and ssh all works nice, no other tests made so far yet. The thing is, when I do “yum update” via SSH, I get this warning: “1015 packages excluded due to repository priority protections” (That’s a lot !) I have a server with proxmox, and I made a VM with Centos6 64bits and your nice software. The thing is now: I want a stable VM (64bits with ispconfig3), I prefere centos. The above error (and errors during the installation) make me insure to decide if this VM-server will be stable, and ofcourse updates must always be possible. So, can somebody advise: 1) Why I am getting these errors, and how can I solve them ? 2) Or must I reinstall a server using another kind of Linux version ? Debian is preferred according the ipconfig3 site ? (lastest with courier or dovecot, which one would be the best ?) THanks in advance !
This happens because of the yum-priorities package (see http://wiki.centos.org/PackageManagement/Yum/Priorities ). In the tutorial, we have given the EPEL repository a higher priority than the CentOS ones, that's why the respective CentOS packages are excluded, and the ones from EPEL are used instead.
