1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

[line 108 of /usr/local/cpanel/base/horde/lib/Prefs/sql.php]

Discussion in 'Database Discussions' started by Christleo, Apr 24, 2004.

  1. Christleo

    Christleo Member

    Joined:
    Mar 13, 2003
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    A fatal error has occurred:

    DB Error: connect failed

    [line 108 of /usr/local/cpanel/base/horde/lib/Prefs/sql.php]

    Details have been logged for the administrator.


    I got this error when i logged into my Horde, webmail... please advice..
     
  2. 97cobracpe

    97cobracpe New Member

    Joined:
    Sep 28, 2003
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    I'm getting the exact same error. Mine started after I moved to a new server.

    Both old and new servers were running WHM 9.2.0 cPanel 9.2.0-R24

    Horde still works on the old server, but not on the new server. I made sure to move the datavase for horde over as well.

    Any other with the problem? Is there a fix?
     
  3. 97cobracpe

    97cobracpe New Member

    Joined:
    Sep 28, 2003
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
  4. Christleo

    Christleo Member

    Joined:
    Mar 13, 2003
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    same error pla.. can't work!
     
  5. jalons

    jalons New Member

    Joined:
    Feb 17, 2004
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    At my wits end

    Ok, I'm really sick of Horde, but anyway.

    I'm getting that infamous error:
    A fatal error has occurred:
    DB Error: connect failed
    [line 108 of /usr/local/cpanel/base/horde/lib/Prefs/sql.php]
    Details have been logged for the administrator.

    I've done the following in attempt to resolve this issue:
    1. Checked the ownership of the files in /usr/local/cpanel/base/horde
    1.A For good measure, I chown -R cpanel.cpanel horde

    2. I've done "Reset Local MySQL Root Password" as well as "Set MySQL Root Password" via WHM

    3. I've done /scripts/resethorde and /scripts/fullhordereset and edited the mysql database to insert the password.

    4. I have relinked the mysql.sock in /tmp to /var/lib/mysql/mysql.sock

    5. I have a feeling this is MySQL related, so here is the contents of /etc/my.cnf

    [mysqld]
    set-variable = max_connections=500
    safe-show-database

    This server is running 9.2.0-RELEASE_20

    Any help would be greatly appreciated.
     
  6. jalons

    jalons New Member

    Joined:
    Feb 17, 2004
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Resolved

    I had to call in the big guns to get this resolved. Thanks cPanel support :)

    The horde database was deleted from mysql. The fix for this was to run mysqladmin create horde and then run /scripts/fullhordereset.
     
  7. Christleo

    Christleo Member

    Joined:
    Mar 13, 2003
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    The horde database was deleted from mysql. The fix for this was to run mysqladmin create horde and then run /scripts/fullhordereset.

    how? able to post the thread?
     
  8. jalons

    jalons New Member

    Joined:
    Feb 17, 2004
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Readding horde db

    I'm unable to post the exact fix, as the cPanel support took care of this.

    You'll want to ensure that the Horde db is in face missing in action.

    mysqlshow |grep horde

    If this comes up blank, try the following:

    mysql_setpermission

    mysqladmin create horde

    /scripts/fullhordereset

    HTH, HAND
     
  9. Amjad

    Amjad New Member

    Joined:
    Nov 9, 2002
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Re: Readding horde db

    Thanks Jalons. Nice HTH.
     
  10. othellotech

    othellotech New Member

    Joined:
    Apr 25, 2004
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    thanks, that fixed the first problem of not finding the DB
    now we get
    Notice: Undefined index: direct_access in /usr/local/cpanel/base/horde/imp/templates/menu/menu.inc

    anyone else seeing this ? know a fix ?
     
  11. jeroman8

    jeroman8 Member

    Joined:
    Mar 14, 2003
    Messages:
    427
    Likes Received:
    0
    Trophy Points:
    16
    Hi, same problem here !!

    horde databas was missing from Mysql (??!!???!!!)

    Anyway, I exported the structire from another
    server for Horde.

    Created the databse "horde" using phpmyadmin from
    the link in WHM.

    Then I run the following sql query: (structure)


    # phpMyAdmin SQL Dump
    # version 2.5.6-rc1
    # http://www.phpmyadmin.net
    #
    # Värd: localhost
    # Skapad: 07 maj 2004 kl 13:10
    # Serverversion: 4.0.18
    # PHP-version: 4.2.3
    #
    # Databas : `horde`
    #

    # --------------------------------------------------------

    #
    # Struktur för tabell `horde_categories`
    #

    CREATE TABLE `horde_categories` (
    `category_id` int(11) NOT NULL default '0',
    `group_uid` varchar(255) NOT NULL default '',
    `user_uid` varchar(255) default NULL,
    `category_name` varchar(255) NOT NULL default '',
    `category_data` text,
    `category_serialized` smallint(6) NOT NULL default '0',
    `category_updated` timestamp(14) NOT NULL,
    PRIMARY KEY (`category_id`),
    KEY `category_category_name_idx` (`category_name`),
    KEY `category_group_idx` (`group_uid`),
    KEY `category_user_idx` (`user_uid`),
    KEY `category_serialized_idx` (`category_serialized`)
    ) TYPE=MyISAM;

    # --------------------------------------------------------

    #
    # Struktur för tabell `horde_categories_categories`
    #

    CREATE TABLE `horde_categories_categories` (
    `category_id_parent` int(11) NOT NULL default '0',
    `category_id_child` int(11) NOT NULL default '0',
    PRIMARY KEY (`category_id_parent`,`category_id_child`)
    ) TYPE=MyISAM;

    # --------------------------------------------------------

    #
    # Struktur för tabell `horde_prefs`
    #

    CREATE TABLE `horde_prefs` (
    `pref_uid` varchar(255) NOT NULL default '',
    `pref_scope` varchar(16) NOT NULL default '',
    `pref_name` varchar(32) NOT NULL default '',
    `pref_value` text,
    PRIMARY KEY (`pref_uid`,`pref_scope`,`pref_name`)
    ) TYPE=MyISAM;

    # --------------------------------------------------------

    #
    # Struktur för tabell `horde_users`
    #

    CREATE TABLE `horde_users` (
    `user_uid` varchar(255) NOT NULL default '',
    `user_pass` varchar(32) NOT NULL default '',
    PRIMARY KEY (`user_uid`)
    ) TYPE=MyISAM;

    # --------------------------------------------------------

    #
    # Struktur för tabell `kronolith_events`
    #

    CREATE TABLE `kronolith_events` (
    `event_id` bigint(20) NOT NULL default '0',
    `calendar_id` varchar(255) NOT NULL default '',
    `event_description` text,
    `event_location` text,
    `event_keywords` text,
    `event_exceptions` text,
    `event_title` varchar(80) default NULL,
    `event_category` varchar(80) default NULL,
    `event_recurtype` varchar(11) default '0',
    `event_recurinterval` varchar(11) default NULL,
    `event_recurdays` varchar(11) default NULL,
    `event_recurenddate` datetime default NULL,
    `event_start` datetime default NULL,
    `event_end` datetime default NULL,
    `event_alarm` int(11) default '0',
    `event_modified` int(11) NOT NULL default '0',
    PRIMARY KEY (`event_id`),
    KEY `kronolith_calendar_idx` (`calendar_id`)
    ) TYPE=MyISAM;

    # --------------------------------------------------------

    #
    # Struktur för tabell `kronolith_events_seq`
    #

    CREATE TABLE `kronolith_events_seq` (
    `id` int(10) unsigned NOT NULL auto_increment,
    PRIMARY KEY (`id`)
    ) TYPE=MyISAM AUTO_INCREMENT=2 ;

    # --------------------------------------------------------

    #
    # Struktur för tabell `mnemo_memos`
    #

    CREATE TABLE `mnemo_memos` (
    `memo_owner` varchar(255) NOT NULL default '',
    `memo_id` int(11) NOT NULL default '0',
    `memo_desc` varchar(64) NOT NULL default '',
    `memo_body` text,
    `memo_category` int(11) NOT NULL default '0',
    `memo_private` smallint(6) NOT NULL default '1',
    `memo_modified` int(11) NOT NULL default '0',
    PRIMARY KEY (`memo_owner`,`memo_id`)
    ) TYPE=MyISAM;

    # --------------------------------------------------------

    #
    # Struktur för tabell `nag_tasks`
    #

    CREATE TABLE `nag_tasks` (
    `task_owner` varchar(255) NOT NULL default '',
    `task_id` int(11) NOT NULL default '0',
    `task_name` varchar(64) NOT NULL default '',
    `task_desc` text,
    `task_modified` int(11) NOT NULL default '0',
    `task_due` int(11) default NULL,
    `task_priority` int(11) NOT NULL default '0',
    `task_category` int(11) NOT NULL default '0',
    `task_completed` smallint(6) NOT NULL default '0',
    `task_private` smallint(6) NOT NULL default '1',
    PRIMARY KEY (`task_owner`,`task_id`)
    ) TYPE=MyISAM;

    # --------------------------------------------------------

    #
    # Struktur för tabell `turba_objects`
    #

    CREATE TABLE `turba_objects` (
    `object_id` varchar(32) NOT NULL default '',
    `owner_id` varchar(255) default NULL,
    `object_name` varchar(255) default NULL,
    `object_alias` varchar(32) default NULL,
    `object_email` varchar(255) default NULL,
    `object_homeaddress` varchar(255) default NULL,
    `object_workaddress` varchar(255) default NULL,
    `object_homephone` varchar(25) default NULL,
    `object_workphone` varchar(25) default NULL,
    `object_cellphone` varchar(25) default NULL,
    `object_fax` varchar(25) default NULL,
    `object_title` varchar(255) default NULL,
    `object_company` varchar(255) default NULL,
    `object_notes` text,
    `object_type` varchar(255) NOT NULL default 'Object',
    `object_members` blob,
    PRIMARY KEY (`object_id`),
    KEY `turba_owner_idx` (`owner_id`)
    ) TYPE=MyISAM;

    ------------------

    Then I run /scripts/fullhordereset

    and it works :)
     
  12. HollyRidge

    HollyRidge Member

    Joined:
    Feb 25, 2003
    Messages:
    131
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Garner NC USA
    Seeing this too on one system. Anyone found a fix for it yet?
     
  13. Arvand

    Arvand Member

    Joined:
    Jul 26, 2003
    Messages:
    130
    Likes Received:
    1
    Trophy Points:
    18
    Same here
     
  14. Arvand

    Arvand Member

    Joined:
    Jul 26, 2003
    Messages:
    130
    Likes Received:
    1
    Trophy Points:
    18
    Here is a fix but it will probably be overwritten next time cPanel updates. I don't know why it is doing this... It shouldn't do NOTICE errors. Anyway, go to that file (/usr/local/cpanel/base/horde/imp/templates/menu/menu.inc), open it up and after <?php put

    error_reporting(E_ALL ^ E_NOTICE);
     
  15. frosti

    frosti New Member

    Joined:
    May 5, 2004
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Iceland
    Re: Readding horde db

    I had this error but using your fix, the Horde IMP is now up and running! - Thanks!
     
  16. syserror

    syserror New Member

    Joined:
    Jun 1, 2004
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Wiltshire, UK
    yeh same, had both problems and all fixed, thanks everyone :)
     
  17. onestar

    onestar New Member

    Joined:
    Jul 7, 2003
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Fixes above worked a treat (the fullhordereset scripts and the menu.inc fix)

    Thanks
     
  18. HendrikM

    HendrikM Member

    Joined:
    Jun 26, 2004
    Messages:
    40
    Likes Received:
    0
    Trophy Points:
    6

Share This Page