[horde] Horde 4.0-ALPHA1: table already exists

[Jan Schneider]

Zitat von Hiromi Kimura <hiromi at tac.tsukuba.ac.jp>:

> Quoting Jan Schneider <jan at horde.org>
>
>> Zitat von Hiromi Kimura <hiromi at tac.tsukuba.ac.jp>:
>>
>>> Quoting Jan Schneider <jan at horde.org>?
>>>
>>>> Zitat von Hiromi Kimura <hiromi at tac.tsukuba.ac.jp>:
>>>>
>>>>> Quote: Jan Schneider <jan at horde.org>?
>>>>>> The installation method for Horde 4 has been changed to use the PEAR
>>>>>> installer. To prepare your local PEAR installation to install  
>>>>>> software from
>>>>>> Horde's PEAR server, run the following commands from the command line:
>>>>>>
>>>>>> pear channel-discover pear.horde.org
>>>>>> pear install horde/horde_role-alpha
>>>>>> pear run-scripts horde/horde_role
>>>>>>
>>>>>> The last command will ask you for the filessystem location for  
>>>>>> your Horde
>>>>>> installation. This should be some path in your web server's  
>>>>>> document root,
>>>>>> e.g. /var/www/horde. These commands only need to be run once.  
>>>>>> You are now
>>>>>> prepared to install, upgrade and uninstall Horde packages. To  
>>>>>> install the alpha
>>>>>> release of Horde, run the following commands:
>>>>>>
>>>>>> pear install horde/horde-alpha
>>>>>>
>>>>>> Just go to the config/ directory of your Horde installation and copy
>>>>>> conf.php.dist to conf.php:
>>>>>>
>>>>>> cd /var/www/horde/config/
>>>>>> cp conf.php.dist conf.php
>>>>>>
>>>>>> Then point your browser to the installation location, go to the
>>>>>> Administration/Configuration screen and start configuring. You  
>>>>>> probably want
>>>>>> to:
>>>>>>
>>>>>> 1. Configure a real authentication backend!
>>>>>> 2. Configure a database backend (Horde configuration, Database tab)
>>>>>> 3. Install the database tables ("Update all DB schemas" button)
>>>>>
>>>>> After these steps, I get some sql errors at each login.
>>>>>
>>>>> 2011-03-09T12:18:18+09:00 ERR: HORDE4 [horde] SQL QUERY FAILED:  
>>>>> SQLSTATE[42S01]: Base table or view already exists: 1050 Table  
>>>>> 'horde_activesync_schema_info' already exists
>>>>>     CREATE TABLE `horde_activesync_schema_info` ( `version` int(11) )
>>>>>       ENGINE=InnoDB DEFAULT CHARSET=utf8 [pid 14865 on line 782  
>>>>> of "/usr/local/share/pear/Horde/Db/Adapter/Base.php"]
>>>>> 2011-03-09T12:18:18+09:00 ERR: HORDE4 [horde] SQL QUERY FAILED:  
>>>>> SQLSTATE[42S01]: Base table or view already exists: 1050 Table  
>>>>> 'horde_alarm_schema_info' already exists
>>>>>     CREATE TABLE `horde_alarm_schema_info` ( `version` int(11) )
>>>>>       ENGINE=InnoDB DEFAULT CHARSET=utf8 [pid 14865 on line 782  
>>>>> of "/usr/local/share/pear/Horde/Db/Adapter/Base.php"]
>>>>> 2011-03-09T12:18:18+09:00 ERR: HORDE4 [horde] SQL QUERY FAILED:  
>>>>> SQLSTATE[42S01]: Base table or view already exists: 1050 Table  
>>>>> 'horde_auth_schema_info' already exists
>>>>>     CREATE TABLE `horde_auth_schema_info` ( `version` int(11) )
>>>>>       ENGINE=InnoDB DEFAULT CHARSET=utf8 [pid 14865 on line 782  
>>>>> of "/usr/local/share/pear/Horde/Db/Adapter/Base.php"]
>>>>
>>>> Please read the release notes. Upgrades are *not* supported at  
>>>> the moment. Keep following Git if this is what you used in the  
>>>> past.
>>>
>>> This is my another test machine and tried clean installation without Git.
>>>
>>>> With that being said, it still shouldn't happen. I can only  
>>>> imagine insufficient DB permissions between your mixed up Horde  
>>>> installations.
>>>
>>> Humm, I made the DB account as 'grant all privileges' for this horde-alpha.
>>
>> Well, for some reason it's trying to create the schema tables, even  
>> though it should only *update* them if they exist. I can only think  
>> of permission problems causing this behavior.
>>
>> Oh, I only read now that you get this after login not when running  
>> the schemas? Where do you get the messages? In some log file, in a  
>> fatal error, in a notification bubble?
>> Are all schemas green in the configuration screen?
>
> Yes, I only see this message once per login.
> The messages were logged into the log file specified in horde's config.
> It is not fatal error, it seems working. All schemas are green.

So, these message are still logged, even though the schemas are all  
installed and green? Or are these old message from the first log in?  
That would be perfectly find and the expected behavior.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/