• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Horde Webmail error after Upgrade 7.5.4 to 8.0

igraf

Regular Pleskian
hello,
i have a small error after ugrade plesk 7.5.4 to 8.0 (linux)

error comes in email transmission > confirmation dispatch

Warning: _mkpath(): Maximum recursion depth (25) exceeded in /usr/share/psa-horde/pear/Log/file.php on line 160

Warning: fopen(/var/log/psa-horde/psa-horde.log): failed to open stream: Datei oder Verzeichnis nicht gefunden in /usr/share/psa-horde/pear/Log/file.php on line 202

config.php found:
PHP:
$conf['log']['name'] = '/var/log/psa-horde/psa-horde.log';

file.php (201-207)
PHP:
/* Obtain a handle to the log file. */
            $this->_fp = fopen($this->_filename, ($this->_append) ? 'a' : 'w');

            $this->_opened = ($this->_fp !== false);

            /* Attempt to set the log file's mode. */
            @chmod($this->_filename, $this->_mode);

i go to directory /var/log > psa-horde this does not exist.

i found the file in /var/log/psa_horde.log

email dispatch would go however the error message comes

who is the bug??

thanks for helps
ivan
 
You could either create /var/log/psa-horde/psa-horde.log or reinstall psa-horde:

rpm -e psa-horde psa-ingo psa-kronolith psa-mnemo psa-passwd psa-turba

rpm -Uvh base/psa-horde*rpm opt/horde/psa*rpm
 
hello, thanks for the fast replay

i install the folder psa-horde and create psa-horde.log

can i delete the file in another directory??
/var/log/psa-horde.log

the following message after directory install....

Apr 03 14:51:37 HORDE [error] [imp] Could not log message details to Horde_History. Error returned: DB Error: no such table [on line 67 of "/usr/share/psa-horde/imp/lib/Maillog.php"]
 
I am also getting this error in psa-horde.log file:
Apr 20 03:27:46 HORDE [error] [imp] Could not log message details to Horde_History. Error returned: DB Error: no such table [on line 67 of "/usr/share/psa-horde/imp/lib/Maillog.php"]
Apr 20 03:59:30 HORDE [error] [imp] Could not log message details to Horde_History. Error returned: DB Error: no such table [on line 67 of "/usr/share/psa-horde/imp/lib/Maillog.php"]
Apr 20 04:10:21 HORDE [emergency] [horde] DB Error: connect failed: [nativecode=Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)] ** Array [on line 1615 of "/usr/share/psa-horde/lib/Horde/DataTree/sql.php"]
Apr 20 04:22:46 HORDE [error] [imp] Unknown IMAP response from the server. Server Responded: [on line 609 of "/usr/share/psa-horde/imp/lib/IMAP/Client.php"]
Apr 20 06:03:36 HORDE [error] [imp] Could not log message details to Horde_History. Error returned: DB Error: no such table [on line 67 of "/usr/share/psa-horde/imp/lib/Maillog.php"]

Any one have any idea any advice ?
 
About horde_history problem

I had the same problem after applying the latest patch on PLESK 7.5.4 (FC2).

I run a part of the script that is used to update horde from 3.0 to 3.1: /usr/share/psa-horde/scripts/upgrades/3.0_to_3.1.mysql.sql

Code:
-- $Horde: horde/scripts/upgrades/3.0_to_3.1.mysql.sql,v 1.1.2.1 2006/01/06 10:41:13 jan Exp $
--
-- You can simply execute this file in your database.
--
-- Run as:
--
-- $ mysql --user=root --password=<MySQL-root-password> <db name> < 3.0_to_3.1.mysql.sql

ALTER TABLE horde_users ADD COLUMN user_soft_expiration_date INT;
ALTER TABLE horde_users ADD COLUMN user_hard_expiration_date INT;

CREATE TABLE horde_histories (
    history_id       BIGINT NOT NULL,
    object_uid       VARCHAR(255) NOT NULL,
    history_action   VARCHAR(32) NOT NULL,
    history_ts       BIGINT NOT NULL,
    history_desc     TEXT,
    history_who      VARCHAR(255),
    history_extra    TEXT,
--
    PRIMARY KEY (history_id)
);

CREATE INDEX history_action_idx ON horde_histories (history_action);
CREATE INDEX history_ts_idx ON horde_histories (history_ts);
CREATE INDEX history_uid_idx ON horde_histories (object_uid);

GRANT SELECT, INSERT, UPDATE, DELETE ON horde_histories TO horde@localhost;

/Fredrik
 
Back
Top