Installation error: Administrator content object does not have 'first_name' and 'last_name' fields

Sunday 13 February 2005 4:59:02 pm

The setup wizard was not able to complete the creation of your selected sites.

The following errors were detected:

* EZSW-023Administrator content object does not have a 'first_name' field
* EZSW-024Administrator content object does not have a 'last_name' field
* EZSW-040Failed to initialize site package shop

I have been trying all day to install EZPublish 3.5.0 on a 1and1.com dedicated Linux server (Fedora Core 2). I managed to set open_basedir to none using the Apache conf file, and also used mysql to make sure that the db user has all privileges on the db in case the script uses some alter table command or something. I'm thinking of putting it into debug mode now (gotta find out how) so that I can see what might be going wrong. I have tried to setup a plain install, as well as a shop with the same results. I have sufficient versions of Apache, MySQL and PHP.

It looks to me like there is an error in some SQL somewhere, trying to insert the pre-populated 'first_name' and 'last_name' values that are in the form/wizard. It doesn't matter whether I change the values, or blank them out, the install still refuses to finish.

I have tried the manual setup, but without luck there either since the documentation on a manual installation is actually lacking some concrete examples on what at a minimum should be put into the site.ini.append.php file (actually the docs say to edit site.ini which is incorrect)

Any help would be appreciated.

Thanks,

nothing to sig here, move along

Monday 14 February 2005 10:55:45 am

With help from agentbob on IRC, I solved my problem. It turns out that error 28 means that the disk is out of space. There is plenty of disk space in my server account, however a little investigation shows that the MySQL temporary directory

mysql> show variables like "tmpdir";
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| tmpdir        | /tmp/ |
+---------------+-------+
1 row in set (0.00 sec)

checking the disk partitions

[root@u15178040 ezpublish]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda1             510M  510M     0 100% /
none                  122M     0  122M   0% /dev/shm
/dev/hda7              27G  196M   26G   1% /home
/dev/hda5             4.9G  1.3G  3.7G  26% /usr
/dev/hda6             4.9G  302M  4.6G   7% /var

showed that the root partition was indeed full. /tmp doesn't show it's own partition above, so therefore it is part of '/'. I deleted some junk in /tmp, and reloaded my MySQL database using a prior data dump from a known good installation on my local development box.

mysql -u ez_admin ez_db -pSomePassword <MyDefaultData.sql

I wish I had though on my own to search for the error code on mysql.com. I just figured it was an internal ezPublish error code, but now it is obvious to me that the smart folks at ezPublish would trap and report any native error codes.

Thanks again agentbob!

nothing to sig here, move along