Topic: PHPMYADMIN - just gives me a blank screen

[Robert Harlow]

Sirs

Newly rebuilt SME5.6u4 server/gateway.
Have run the PHPmyAdmin addon .
Trying to access with https://mydomain/phpmyadmin/ just gets me a blank stare:~|
Is there another trick I have to pull to get this back up and running?

best wishes, Robert

[Robert Harlow]

(information follow up)

Rebooted (old M$ habit...). Have now amended PHP.INI to show errors and this pair of errors arrives onscreen after attempting to use PHPmyAdmin...
Warning: main(./libraries/grab_globals.lib.php): failed to open stream: No such file or directory in /opt/phpMyAdmin/index.php on line 9
Fatal error: main(): Failed opening required './libraries/grab_globals.lib.php' (include_path='.:/usr/share/pear') in /opt/phpMyAdmin/index.php on line 9

Right near the end of the bootup log I see...
Sep 14 20:39:36 nas600 mysql: ERROR 1046 at line 3: No Database Selected
Sep 14 20:39:36 nas600 mysql.init: Loading 40mysql.create.turba.sql into mysql failed

Not sure what this turba thing is but there does seem to be something amiss with PHP, perhaps Perl and particularly with MySQL. Using PuTTY and Midnight Commander I can see a bunch of stuff for PHP, PHPmyAdmin and so forth, it's just a pity it's not doing anything useful. Any clues anyone;~)

best wishes, Robert

[Peter Side]

Hi Robert,

I have the same problem I will keep an eye on this post.

Peter Side

[Craig Jensen]

Did you recently upgrade imp, horde, turba? 40mysql.create.turba.sql is a symlink to the turba.sql left in your init dir to be executed at re-boot after your upgrade.

Locate the file and make sure it has the following as the first line in the script:

USE horde;


The srcipt does not indicate it's database target which is why the error 'No Database Selected'.


Craig Jensen

[Robert Harlow]

Craig

I rebuilt the server over the weekend.
To obtain PHP4.3.2 (specifically gd2) I also ran the PHP/IMP/HORDE upgrade located at:
http://www.leiinc.com/repository/Linux/Mitel_SME_Server/Contribs/imp_php_horde/sme56_php-horde-imp.tar

Have found and its contents are now:
-- $Horde: turba/scripts/drivers/turba.sql,v 1.4.2.4 2002/09/11 11:32:35 jan Exp $

USE horde;

CREATE TABLE turba_objects (
   object_id VARCHAR(32) NOT NULL,
   owner_id VARCHAR(255) NOT NULL,
   object_type VARCHAR(255) NOT NULL DEFAULT 'Object',
   object_members BLOB,
   object_name VARCHAR(255),
   object_alias VARCHAR(32),
   object_email VARCHAR(255),
   object_homeaddress VARCHAR(255),
   object_workaddress VARCHAR(255),
   object_homephone VARCHAR(25),
   object_workphone VARCHAR(25),
   object_cellphone VARCHAR(25),
   object_fax VARCHAR(25),
   object_title VARCHAR(255),
   object_company VARCHAR(255),
   object_notes TEXT,

   PRIMARY KEY(object_id)
);

CREATE INDEX turba_owner_idx ON turba_objects (owner_id);

GRANT SELECT, INSERT, UPDATE, DELETE ON turba_objects TO horde;



I presumed a reboot was required.
There seems to be no improvement to my current difficulties.

Afterwards the boot.log shows the following (at the very end):
Sep 15 09:46:09 nas600 guardian.pl: Loaded 0 addresses from /etc/guardian.ignore
Sep 15 09:46:09 nas600 guardian.pl: Becoming a daemon..
Sep 15 09:46:09 nas600 guardiand: guardian.pl startup succeeded
Sep 15 09:46:11 nas600 mysql: ERROR
Sep 15 09:46:11 nas600 mysql:  1050 at line 5: Table 'turba_objects' already exists
Sep 15 09:46:11 nas600 mysql.init: Loading 40mysql.create.turba.sql into mysql failed
Sep 15 09:46:35 nas600 atalk: atalkd startup succeeded
Sep 15 09:46:47 nas600 atalk: papd startup succeeded
Sep 15 09:46:47 nas600 atalk: afpd startup succeeded


Down in root I see a file called of some 75kB. The file starts off with...

<86>Sep 13 10:13:08 groupadd[272]: new group: name=ntp, gid=38

<86>Sep 13 10:13:08 useradd[273]: new user: name=ntp, uid=38, gid=38, home=/etc/ntp, shell=/sbin/nologin

<86>Sep 13 10:13:10 groupadd[280]: new group: name=slocate, gid=21

<86>Sep 13 10:13:13 groupadd[302]: new group: name=floppy, gid=19

...and this file continues similarly in a scratchpad type manner. Worryingly, the end of the file seems truncated. The end of the file reads...

<142>/etc/e-smith/events/post-install/S75conf-masq[1263]: /home/e-smith/configuration: OLD masq=service|Logging|none|status|enabled

<142>/etc/e-smith/events/post-install/S75conf-masq[1263]: /home/e-smith/configuration: NEW masq=service|Logging|none|Stealth|no|status|enabled

<13>Sep 13 15:20:18 e-smith[1168]: S75conf-masq=action|Event|post-install|Action|S75conf-masq|Start|1063462817 864024|End|1063462818 649861|Elapsed|0.785837
<13>Sep 13 15:20:18 e-smith[1168]: Running event handler: /etc/e-smith/events/post-install/S75conf-mysql-startup
<142>/etc/e-smith/events/post-install/S75conf-mysql-startup[1264]: /home/e-smith/configuration: OLD mysqld=(undefined)

<142>/etc/e-smith/events/post-install/S75conf-mysql-startup[1264]: /home/e-smith/configu

...and the file's content just ends precisely as shown above:-|
Perhaps this is an indicator that something went radically wrong with the functionality of the (PHP/IMP/HORDE) updating process?

best wishes, Robert

[Craig Jensen]

I assume you ran the install as per the how-to here:
http://www.leiinc.com/repository/Linux/Mitel_SME_Server/HowToGuides/sme56_imp-horde-php_upgrade.htm

Specifically,
[root@testbed rpms]# /sbin/e-smith/signal-event horde-update

and the php.ini template creation...

The above command expands all templates for the imp, turba, etc upgrade config files....

The mysql script you altered may need to be 'manually' injected into the database...
mysqladmin > turba.sql  
from the directory contaiing it.

...that is if you still get the error concerning the sql failed in your logs.
 

Craig Jensen

[Robert Harlow]

That HOWTO ran perfectly and there were no (obvious) deviations. I did everything as instructed and everything promised came about just as it described. I was quite impressed at the time. Now I am somewhat disappointed;~/

I have just PuTTY'd into Midnight Commander using root and navigated to the ...horde/turba/scripts/drivers/ directory, then F10'd out of MC, and finally invoked your *manual injection* command. There was no feedback or error reported. Assumed yet another reboot was required. The resulting boot.log shows this at the very end:

Sep 15 15:42:34 nas600 mysql: ERROR
Sep 15 15:42:34 nas600 mysql:  1064 at line 1: You have an error in your SQL syntax near 'mysqladmin  Ver 8.23 Distrib 3.23.49, for redhat-linux-gnu on i386
Sep 15 15:42:34 nas600 mysql: Copyright (C)' at line 1
Sep 15 15:42:34 nas600 mysql.init: Loading 40mysql.create.turba.sql into mysql failed
Sep 15 15:42:58 nas600 atalk: atalkd startup succeeded
Sep 15 15:43:10 nas600 atalk: papd startup succeeded
Sep 15 15:43:10 nas600 atalk: afpd startup succeeded

I changed the script drivers area's turba.sql to include that one line. Was I supposed to do something with a 40mysql file or something?

I don't seem any further forward with this bunch of PHP MySQL trouble. Can I look for some other signs of damage or inclusion or anything?

best wishes, Robert

[Craig Jensen]

Take a look at the file 40mysql.create.turba.sql in MC or ls -l to make sure which file it is linked to and that that file has the corrections pointing to the horde database.

What I did to resolve the error is manually inject the .sql script, ensure that the tables were altered as per the script contents, then remove the 40mysql.create.turba.sql file from init so it quit loading on re-boot.

You may indeed have the sql correct, but the 40mysql.create.turba.sql file is poining to a different srtipt from the one you editted and so 'it' is missing the USE horde; line.

Craig Jensen

[Robert Harlow]

(BTW I have eyeballed the bash_history file and what it shows confirms I did what was required originally)

I am not able to find a file called 40mysql.create.turba.sql here using MC. Where is it normally located?

Alternatively is there a command line you can specify that might find it more accurately globally?

best wishes, Robert

[Robert Harlow]

Found it - standby:-)

[Robert Harlow]

Found it in...    /etc/e-smith/sql/init/40mysql.create.turba.sql

MC's EditSymlink says... that the file above points to: /home/httpd/html/horde/turba/scripts/drivers/turba.sql

Which is the file you suggested I amended with... USE horde;

best wishes, Robert

[Robert Harlow]

I can't just sit on this issue. This afternoon I wiped the server, a brand new rebuild just days old, and rebuilt it from scratch. When I then reloaded PHYmyAdmin I got a proper screen and not this thread's title:-) The server is as is off the ISO. Neither the u2 nor the u4 updaters have yet been installed, the server is still with its original flavour of PHP.

Haven't yet decided whether to run the u2 and u4 updaters before or after the aggregated PHP/IMP/Horde HOWTO (to obtain PHP4.3.2 and with it the gd2 library).

A long while ago I ran the stock PHP4.3.2, straight from their source site, over SME5.6u2 but noticed there were some install issues but these might have been as a result of other debris and extensive previous fallout;~/  Hence my goal of getting this rebuild going with the minimum of install and running errors!

This posting is specifically for Peter (fellow sufferer) - as I'm rebuilding out of this mess - and for interested forum searchers.

best wishes, Robert