Koozali.org: home of the SME Server

Snafu'd my IMP

Ruusvuu

Snafu'd my IMP
« on: April 03, 2002, 08:08:17 PM »
I don't know what happened.
I opened https://***.***.**.**/webmail
and got access denied for user hordemgr@localhost using password YES

So I installed IMP 3.1
Now I get:

Some of IMP's configuration files are missing:
conf.php This is the main IMP configuration file. It contains paths and options for the IMP scripts.
html.php This file controls the stylesheet that is used to set colors and fonts in addition to or overriding Horde defaults.
mime_drivers.php This file controls local MIME drivers for IMP, specifically what kinds of attachments are viewable and/or downloadable.
prefs.php This file controls the default preferences for IMP, and also controls which preferences users can alter.
servers.php This file controls the default settings for IMP, and also defines the list of available servers if you are using the server list.

What have I done? %(

Thanks

Ruusvuu

Re: Snafu'd my IMP
« Reply #1 on: April 03, 2002, 08:14:44 PM »
OK, I'm an idiot!

all the files in the horde folder are named .php3
The new IMP is obviously looking for .php files.

Simple question:   How do I rename the files from SSH?

Thank you!

Dan G.

Re: Snafu'd my IMP
« Reply #2 on: April 03, 2002, 08:36:18 PM »
_HOW_ did you upgrade?  Were you following Dan Brown's very nice How-to to the letter?   ...and I mean, to the letter?

If you did, something else would have to be majorly unhinged to come up with what you are seeing...

Dan G.

Dan Brown

Re: Snafu'd my IMP
« Reply #3 on: April 03, 2002, 08:51:16 PM »
If he upgraded to IMP 3.1, he couldn't have done so following my HOWTO, as it's for IMP 3.0 only.  I'll update it after IMP 3.1 is released (not in RC stage).

Ruusvuu

Re: Snafu'd my IMP
« Reply #4 on: April 03, 2002, 09:35:50 PM »
Hi Dan!

Maybe I can upgrade to 3.0 using --force?
I really hope I didn't totally mess things up.

Dan Brown

Re: Snafu'd my IMP
« Reply #5 on: April 03, 2002, 10:23:46 PM »
Depends how you installed 3.1.  If you used tarballs, you shouldn't need --force; just follow my howto.

Ruusvuu

Re: Snafu'd my IMP
« Reply #6 on: April 03, 2002, 11:30:05 PM »
Thanks for your help Dan.
What is the default password for hordemgr?
I don't know what happened to it.
The horde DB was gone and the user hordemgr was gone, too.
Once I get this fixed, I think I'm ready to roll.

Richard

Ruusvuu

Re: Snafu'd my IMP
« Reply #7 on: April 05, 2002, 01:41:23 AM »
Hello Gentlemen!

PHP works
MySQL works
They don't work together
In attempting to finally follow DB's How-To, I get the following:

[root@xend php412]# ls
php-4.1.2-2es.i386.rpm       php-mysql-4.1.2-2es.i386.rpm
php-imap-4.1.2-2es.i386.rpm  php-pgsql-4.1.2-2es.i386.rpm
php-ldap-4.1.2-2es.i386.rpm
[root@xend php412]# rpm -Fvh *
[root@xend php412]# rpm -Uvh *
error: failed dependencies:
        postgresql is needed by php-pgsql-4.1.2-2es
        libpq.so   is needed by php-pgsql-4.1.2-2es
[root@xend php412]#

Any and all help appreciated.

"A good teacher makes him/herself progressively unnecessary."
                                                                    Author Unknown

robert

Re: Snafu'd my IMP
« Reply #8 on: April 05, 2002, 01:58:30 AM »
Do you get any errors in IMP? Because the rpm error is easily explained and nothing to worry about. The -F switch tells rpm to only 'freshen' those packages for which there's an older version on your system. The -U switch will update a package if there's an older version on your system _or_ install a new package if there's no older version on your system. That's why -Fvh does not return any errors, while -Uvh does. Rpm -Uvh tries to install php-pgsql, but fails because you don't have postgresql installed on your system, but you don't need it anyway. Looks like the install went ok. Did you encounter any other problems?

Ruusvuu

Re: Snafu'd my IMP
« Reply #9 on: April 05, 2002, 02:08:42 AM »
cannot load MySQL extension,
please check PHP Configuration.

This is what phpMyAdmin returns

I edited php.ini thus:

extension_dir = ./ --> extension_dir = /usr/lib/php4

The problem might lie in the fact that I incorrectly upgraded php from 4.0.6 to 4.1.2
and, therefore, may have hph installed in the wrong place, which means I may have edited the wrong php.ini file.

I'm not giving up on this!

The primary domain on this server is www.xend.net and is colo'd at Deru Internet in Arizona.

Ruusvuu

Re: Snafu'd my IMP
« Reply #10 on: April 05, 2002, 03:26:31 AM »
Fatal error: Call to undefined function: mysql_connect() in /home/e-smith/files/primary/html/advt/common.php on line 7

Does this look like my PHP 4.1.2 doesn't even know what mysql is?!

Dan Brown

Re: Snafu'd my IMP
« Reply #11 on: April 05, 2002, 04:35:54 AM »
Yes, that's what it looks like.  Make sure php-mysql is installed (with rpm -q php-mysql).  If it is, take a look in /etc/php.ini.  The extension_dir setting you mentioned above is one thing that needs to be correct (and /usr/lib/php4 is the correct value); also make sure that you have a line that says "extension=mysql.so", and that that line isn't commented out.

Ruusvuu

Re: Snafu'd my IMP
« Reply #12 on: April 05, 2002, 05:00:00 AM »
[root@xend php412]# rpm -ivh php-mysql-4.1.2-2es.i386.rpm
Preparing...                ########################################### [100%]
package php-mysql-4.1.2-2es is already installed
[root@xend php412]# rpm -e php-mysql-4.1.2-2es.i386.rpm
error: package php-mysql-4.1.2-2es.i386.rpm is not installed
[root@xend php412]#

Wow!  First it's already installed and two seconds later it's not!
Maybe I just understand the rpm syntaqx well enough - and I admin I don't know as much as I'd like.

Thanks for all help.
We'll get this thing!

Terry Brummell

Re: Snafu'd my IMP
« Reply #13 on: April 05, 2002, 05:06:28 AM »
When uninstalling a rpm you don't specify the version number.

rpm -e php-mysql

(or something like that)

Ruusvuu

Re: Snafu'd my IMP
« Reply #14 on: April 05, 2002, 05:12:56 AM »
OK!

I didn't need to reinstall or uninstall anything.
Thanks to Dan Brown, simply typing in the directive:

extension-mysql.so

did the trick

What puzzles me is that php.ini says the mysql is included by default or something like that and doesn't need the extension...

Oh, well

Thanks for everyone's input.
I'm so stoked!