Koozali.org: home of the SME Server

Upgrade problem

Tim Hogan

Upgrade problem
« on: July 08, 2002, 07:58:17 PM »
I have upgraded to Version 5.5 and received the following error messages during bootup (they appear to be different from the migrate-imp-to-turba problem listed on the bug page):

Jul  8 08:38:52 e-smith-server migrate-imp-to-turba: Migrating IMP 2.x address book to IMP 3.x (Turba)
Jul  8 08:38:52 e-smith-server migrate-imp-to-turba: Migrating database
Jul  8 08:38:57 e-smith-server migrate-imp-to-turba: loading /etc/e-smith/sql/init/30mysql.create.horde.sql into mysql
Jul  8 08:38:57 e-smith-server migrate-imp-to-turba: /etc/rc.d/init.d/mysql.init: /etc/e-smith/sql/init/30mysql.create.horde.sql: No such file or directory
Jul  8 08:38:58 e-smith-server migrate-imp-to-turba: Loading data into mysql
Jul  8 08:39:02 e-smith-server mysql.init: Loading data into mysql failed
Jul  8 08:39:02 e-smith-server migrate-imp-to-turba: ^[[60G
Jul  8 08:39:02 e-smith-server migrate-imp-to-turba: [
Jul  8 08:39:02 e-smith-server migrate-imp-to-turba: ^[[1;31m
Jul  8 08:39:02 e-smith-server migrate-imp-to-turba: FAILED
Jul  8 08:39:02 e-smith-server migrate-imp-to-turba:
Jul  8 08:39:02 e-smith-server migrate-imp-to-turba: Creating Turba objects table
Jul  8 08:39:05 e-smith-server migrate-imp-to-turba: DBI->connect(horde:localhost:3306) failed: Access denied for user: 'horde@localhost' (Using password: YES) at /etc/rc.d/init.d/migrate-imp-to-turba line 120
Jul  8 08:39:05 e-smith-server migrate-imp-to-turba: Converting book entries
Jul  8 08:39:05 e-smith-server rc: Starting migrate-imp-to-turba:  failed
Jul  8 08:39:14 e-smith-server atalk: atalkd startup succeeded
Jul  8 08:39:25 e-smith-server mysql.init: loading /etc/e-smith/sql/init/30mysql.create.horde.sql into mysql
Jul  8 08:39:25 e-smith-server mysql.init: /etc/rc.d/init.d/mysql.init: /etc/e-smith/sql/init/30mysql.create.horde.sql: No such file or directory
Jul  8 08:39:25 e-smith-server mysql.init: Loading data into mysql
Jul  8 08:39:26 e-smith-server mysql.init: Loading data into mysql failed
Jul  8 08:39:26 e-smith-server mysql.init: ^[[60G
Jul  8 08:39:26 e-smith-server mysql.init:
Jul  8 08:39:26 e-smith-server rc: Starting mysql.init:  succeeded

I ran the imp-folders-0.0.1 from myezserver.com several weeks ago so that Procmail and Outlook Express would get along.  Could this be part of the problem?

Mail seems to be working through Outlook Express (I use IMAP) - at least I am receiving mail.  If I try to use Webmail (setting the default folder to /) I receive the following message:

IMP Maintenance Operations - Confirmation  
 
Warning! IMP is ready to perform the maintenance operations checked below.
Check the box for any operation(s) you want to perform at this time.  
 
A fatal error has occurred
object(db_error)(7) {
  ["error_message_prefix"]=>
  string(0) ""
  ["mode"]=>
  int(1)
  ["level"]=>
  int(1024)
  ["code"]=>
  int(-24)
  ["message"]=>
  string(24) "DB Error: connect failed"
  ["userinfo"]=>
  string(86) " [nativecode=Access denied for user: 'horde@localhost' (Using password: YES)] ** Array"
  ["callback"]=>
  NULL
}
[/home/httpd/html/horde/lib/Prefs/sql.php : 102]


So far all else seems to be working OK.

Tim Hogan

Bill Talcott

Re: Upgrade problem
« Reply #1 on: July 08, 2002, 09:38:03 PM »

Tim Hogan

Re: Upgrade problem
« Reply #2 on: July 09, 2002, 01:44:22 AM »
I'm not sure if you are telling me to report a bug or read the bug report for migrate-imp-to-turba.  I did disable migrate-imp-to-turba as suggested and it stops the error messages when I reboot the server.  However, I cannot get into my email via Webmail.  I have tried to log in with the folder-prefix set to "Mail/" (the default), blank and "/".  None work, I receive the error message detailed in my first message.  Also, with migrate-imp-to-turba enabled, the error message at bootup is not the same as that shown in the bug report.

Tim

Re: Upgrade problem
« Reply #3 on: July 23, 2002, 10:34:57 PM »
Hi have this same exact problem and the "fix" did not fix the problem.

Tom Veitch

Re: Upgrade problem
« Reply #4 on: July 23, 2002, 10:46:06 PM »
You login with the root password the type fsck /dev/hda5 or 6
it then should start the repair

Tim Hogan

Re: Upgrade problem
« Reply #5 on: July 24, 2002, 12:07:41 AM »