[kronolith] unserialize() problem in a clean installation

Guy Morton guy at alchemy.com.au
Thu Jul 21 19:14:12 PDT 2005


Hi there

I have read a number of previous posts where people have reported 
similar issues and the answer has been "Use the new prefs file". That 
does not solve the problem for me. (I have used the prefs file from the 
dist - if someone wants to send me copies of prefs files that work for 
them please feel free!)

Operating system is Debian (Sarge). All details from test.php printed below.

I have done a brand new install of Horde 3, and IMP 4 - these both work 
perfectly (and nice work, by the way!). Both were installed from the 
tarballs.

However, Kronolith 2 (again a clean install from tarball) gives me the 
following output when i try to access index.php:
*
Notice*: unserialize(): Argument is not a string in 
*/var/www/horde/kronolith/lib/base.php* on line *66*

*Notice*: unserialize(): Argument is not a string in 
*/var/www/horde/kronolith/lib/base.php* on line *67*

*Warning*: array_values(): The argument should be an array in 
*/var/www/horde/kronolith/lib/base.php* on line *89*

*Notice*: unserialize(): Argument is not a string in 
*/var/www/horde/kronolith/lib/base.php* on line *99*

*Warning*: main(/var/www/horde/kronolith/.php): failed to open stream: 
No such file or directory in */var/www/horde/kronolith/index.php* on 
line *22*

*Fatal error*: main(): Failed opening required 
'/var/www/horde/kronolith/.php' 
(include_path='/var/www/horde/lib:.:/usr/share/php:/usr/share/pear') in 
*/var/www/horde/kronolith/index.php* on line *22

*Interestingly, if I go to the weekly, daily etc view, I get errors but 
also I get the interface coming up underneath the errors. The errors on 
those pages look like this:

*Notice*: unserialize(): Argument is not a string in 
*/var/www/horde/kronolith/lib/base.php* on line *66*

*Notice*: unserialize(): Argument is not a string in 
*/var/www/horde/kronolith/lib/base.php* on line *67*

*Warning*: array_values(): The argument should be an array in 
*/var/www/horde/kronolith/lib/base.php* on line *89*

*Notice*: unserialize(): Argument is not a string in 
*/var/www/horde/kronolith/lib/base.php* on line *99*

*Notice*: unserialize(): Argument is not a string in 
*/var/www/horde/kronolith/templates/menu.inc* on line *2

*I have beaten my head against this for several hours and am at a loss 
to understand why it isn't working. The prefs files as straight out of 
the distribution, I've even tried setting the permissions on the 
kronolith config directory to 777 thinking maybe it was just having a 
problem reading the configs but that didn't work either. I've totally 
removed the original database used by horde and recreated it using the 
script supplied in the dist package...ditto with the kronolith tables.

Please help!

Other info that might be useful::


  Horde Version

    * Horde: 3.0.5-RC1


  Horde Applications

    * Horde: 3.0.5-RC1
    * Imp: H3 (4.0.3) (run Imp tests
      <http://webmail.virtuit.com.au/horde/imp/test.php>)
    * Kronolith: H3 (2.0.3)


  PHP Version

    * View phpinfo() screen
      <http://webmail.virtuit.com.au/horde/test.php?mode=phpinfo&url=%2Fhorde%2Ftest.php>
    * View loaded extensions
      <http://webmail.virtuit.com.au/horde/test.php?mode=extensions&url=%2Fhorde%2Ftest.php>
    * PHP Version: 4.3.10-15
    * PHP Major Version: 4.3
    * PHP Minor Version: 10
    * PHP Subminor Version: 15
    * PHP Version Classification: release
    * *You are running a supported version of PHP.*


  PHP Module Capabilities

    * Ctype Support: *Yes*
    * DOM XML Support: *Yes*
    * FTP Support: *Yes*
    * GD Support: *Yes*
    * Gettext Support: *Yes*
    * Iconv Support: *Yes*
    * IMAP Support: *Yes*
    * LDAP Support: *Yes*
    * Mbstring Support: *Yes*
    * Mcrypt Support: *No*
    * MIME Magic Support (fileinfo): *No*
      *The fileinfo PECL module or the mime_magic PHP extension (see
      below) will most likely provide faster MIME Magic lookups than the
      built-in Horde PHP magic code. See horde/docs/INSTALL for
      information on how to install PECL/PHP extensions.*
    * MIME Magic Support (mime_magic): *Yes*
    * MySQL Support: *Yes*
    * OpenSSL Support: *Yes*
    * PostgreSQL Support: *No*
    * Session Support: *Yes*
    * XML Support: *Yes*
    * Zlib Support: *Yes*


  Miscellaneous PHP Settings

    * magic_quotes_runtime disabled: *Yes*
    * memory_limit disabled: *No*
      *If PHP's internal memory limit is turned on and if not set high
      enough Horde will not be able to handle large data items (e.g.
      large mail attachments in IMP). If possible, you should disable
      the PHP memory limit by recompiling PHP /without/ the
      "--enable-memory-limit" flag. If this is not possible, then you
      should set the value of memory_limit in php.ini to a sufficiently
      high value (Current value of memory_limit: 36M).*
    * safe_mode disabled: *Yes*
    * session.use_trans_sid disabled: *Yes*
    * session.auto_start disabled: *Yes*


  File Uploads

    * file_uploads enabled: *Yes*
    * upload_max_filesize: 2M
    * post_max_size: 8M


  Required Horde Configuration Files

    * config/conf.php: *Yes*
    * config/mime_drivers.php: *Yes*
    * config/nls.php: *Yes*
    * config/prefs.php: *Yes*
    * config/registry.php: *Yes*


  PHP Sessions

    * Session counter: 7
    * To unregister the session: click here
      <http://webmail.virtuit.com.au/horde/test.php?mode=unregister>


  PEAR

    * *PEAR Search Path (PHP's include_path)*:
       /var/www/horde/lib:.:/usr/share/php:/usr/share/pear
    * PEAR: *Yes*
    * Recent PEAR: *Yes*
    * Mail: *Yes*
    * Mail_Mime: *Yes*
    * Log: *Yes*
    * DB: *Yes*
    * Net_Socket: *Yes*
    * Date: *Yes*
    * Auth_SASL: *Yes*
    * HTTP_Request: *Yes*
    * File: *Yes*
    * Net_SMTP: *Yes*
    * Services_Weather: *Yes*

Valid XHTML 1.0! <http://validator.w3.org/check/referer>



-- phpMyAdmin SQL Dump
-- version 2.6.2
-- http://www.phpmyadmin.net
-- 
-- Host: localhost
-- Generation Time: Jul 22, 2005 at 12:05 PM
-- Server version: 4.0.24
-- PHP Version: 4.3.10-15
-- 
-- Database: `horde`
-- 

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

-- 
-- Table structure for table `horde_datatree`
-- 

CREATE TABLE `horde_datatree` (
  `datatree_id` int(11) NOT NULL default '0',
  `group_uid` varchar(255) NOT NULL default '',
  `user_uid` varchar(255) NOT NULL default '',
  `datatree_name` varchar(255) NOT NULL default '',
  `datatree_parents` varchar(255) NOT NULL default '',
  `datatree_order` int(11) default NULL,
  `datatree_data` text,
  `datatree_serialized` smallint(6) NOT NULL default '0',
  `datatree_updated` timestamp(14) NOT NULL,
  PRIMARY KEY  (`datatree_id`),
  KEY `datatree_datatree_name_idx` (`datatree_name`),
  KEY `datatree_group_idx` (`group_uid`),
  KEY `datatree_user_idx` (`user_uid`),
  KEY `datatree_serialized_idx` (`datatree_serialized`)
) TYPE=MyISAM;

-- 
-- Dumping data for table `horde_datatree`
-- 

INSERT INTO `horde_datatree` VALUES (1, 'horde.shares.kronolith', 
'guy at alchemy.com.au', 'guy at alchemy.com.au', '', NULL, NULL, 0, 
'20050722120053');

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

-- 
-- Table structure for table `horde_datatree_attributes`
-- 

CREATE TABLE `horde_datatree_attributes` (
  `datatree_id` int(11) NOT NULL default '0',
  `attribute_name` varchar(255) NOT NULL default '',
  `attribute_key` varchar(255) NOT NULL default '',
  `attribute_value` text,
  KEY `datatree_attribute_idx` (`datatree_id`),
  KEY `datatree_attribute_name_idx` (`attribute_name`),
  KEY `datatree_attribute_key_idx` (`attribute_key`)
) TYPE=MyISAM;

-- 
-- Dumping data for table `horde_datatree_attributes`
-- 

INSERT INTO `horde_datatree_attributes` VALUES (1, 'owner', '', 
'guy at alchemy.com.au');
INSERT INTO `horde_datatree_attributes` VALUES (1, 'name', '', 'Guy 
Morton''s Calendar');
INSERT INTO `horde_datatree_attributes` VALUES (1, 'perm_users', 
'guy at alchemy.com.au', '30');

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

-- 
-- Table structure for table `horde_datatree_seq`
-- 

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

-- 
-- Dumping data for table `horde_datatree_seq`
-- 

INSERT INTO `horde_datatree_seq` VALUES (1);

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

-- 
-- Table structure for table `horde_log`
-- 

CREATE TABLE `horde_log` (
  `id` int(11) NOT NULL default '0',
  `logtime` timestamp(14) NOT NULL,
  `ident` varchar(16) NOT NULL default '',
  `priority` int(11) NOT NULL default '0',
  `message` text,
  PRIMARY KEY  (`id`)
) TYPE=MyISAM;

-- 
-- Dumping data for table `horde_log`
-- 


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

-- 
-- Table structure for table `horde_prefs`
-- 

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

-- 
-- Dumping data for table `horde_prefs`
-- 


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

-- 
-- Table structure for table `horde_tokens`
-- 

CREATE TABLE `horde_tokens` (
  `token_address` varchar(100) NOT NULL default '',
  `token_id` varchar(32) NOT NULL default '',
  `token_timestamp` bigint(20) NOT NULL default '0',
  PRIMARY KEY  (`token_address`,`token_id`)
) TYPE=MyISAM;

-- 
-- Dumping data for table `horde_tokens`
-- 


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

-- 
-- Table structure for table `horde_users`
-- 

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

-- 
-- Dumping data for table `horde_users`
-- 


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

-- 
-- Table structure for table `horde_vfs`
-- 

CREATE TABLE `horde_vfs` (
  `vfs_id` bigint(20) NOT NULL default '0',
  `vfs_type` smallint(6) NOT NULL default '0',
  `vfs_path` varchar(255) NOT NULL default '',
  `vfs_name` varchar(255) NOT NULL default '',
  `vfs_modified` bigint(20) NOT NULL default '0',
  `vfs_owner` varchar(255) NOT NULL default '',
  `vfs_data` longblob,
  PRIMARY KEY  (`vfs_id`),
  KEY `vfs_path_idx` (`vfs_path`),
  KEY `vfs_name_idx` (`vfs_name`)
) TYPE=MyISAM;

-- 
-- Dumping data for table `horde_vfs`
-- 


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

-- 
-- Table structure for table `kronolith_events`
-- 

CREATE TABLE `kronolith_events` (
  `event_id` varchar(32) NOT NULL default '',
  `event_uid` varchar(255) NOT NULL default '',
  `calendar_id` varchar(255) NOT NULL default '',
  `event_creator_id` varchar(255) NOT NULL default '',
  `event_description` text,
  `event_location` text,
  `event_status` int(11) default '0',
  `event_attendees` text,
  `event_keywords` text,
  `event_exceptions` text,
  `event_title` varchar(255) 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`),
  KEY `kronolith_uid_idx` (`event_uid`)
) TYPE=MyISAM;

-- 
-- Dumping data for table `kronolith_events`
-- 


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

-- 
-- Table structure for table `kronolith_storage`
-- 

CREATE TABLE `kronolith_storage` (
  `vfb_owner` varchar(255) default NULL,
  `vfb_email` varchar(255) NOT NULL default '',
  `vfb_serialized` text NOT NULL,
  KEY `kronolith_vfb_owner_idx` (`vfb_owner`),
  KEY `kronolith_vfb_email_idx` (`vfb_email`)
) TYPE=MyISAM;

-- 
-- Dumping data for table `kronolith_storage`
-- 




More information about the kronolith mailing list