scriptworx phpbb

SiteWorx General Discussion
1

PHP Fatal error: Cannot instantiate non-existent class: sql_db in /chroot/home/domain/domain.com/html/forum/includes/db.php on line 60

This is after a fresh scriptworx install of phpbb.

What did I do wrong!? Other phpbb databases on this machine work.

2

Edit: I’ve just done a phpBB install via scriptworx on another domain and I get the same error as above.

3

Hi thegoat,

A google search for this error shows lots of possibilities as to the cause - possibly php or mysql version issue, or some problem connecting to the MySQL database. I tested installing phpBB with one of our test servers and couldn’t reproduce this issue so it doesn’t appear to a global scriptworx problem. It may take some more investigation to figure out what the actual problem is.

Paul

4

Well I haven’t done anything outside upgrades or installs of anything outside of the yum upgrades that InterWorx does automatically.

So the possibility of it being a php/mysql version error seems interesting.

Maybe i’ve inadvertantly done something without remembering. I’ll continue looking for a solution as well.

5

Run

rpm -qa | grep mysql

Make sure all of the RPM’s are the same version. I had a similar issue once where the main mysql was one version and the mysql-client and mysql-server were different for some reason.

6

mysql-3.23.58-4
mysql-server-3.23.58-4
php-mysql-4.3.11-100.fdr10.iworx
mysql-devel-3.23.58-4
mysql-iworx-4.0.21-3.fdr10.iworx

no dice :frowning:

Other siteworx stuff works fine with databases. only phpbb is messing up.

7

If you look at config.php in the phpbb installation, what does it have for the $dbms variable?

–Dustin

8

Actually you are running RPM’s for both MySQL 3.23 and 4.0 Ideally they should all be the same. Yes they wull work with mixed versions, I’ve dome that too.

I had an issue like this before and upgrading all of them to the new RPM’s fixed it for me. I don’t remember if it was phpBB or not.

In any event it can’t hurt. Of course I was on CentOS 3.x and you are on FC1, so I’m not sure if the RPM’s are available.

I did some poking ariund and didn’t find them on

http://updates.interworx.info/fedora/core/1/i386/os/Fedora/RPMS/

But on

httip://updates.interworx.info/iworx/

I did some poking around and found THIS rpm which I have but you don’t. Not sure what it is



http://updates.interworx.info/iworx/RPMS/fdr10/i386/mysql-shared-compat-4.0.21-100.iworx.i386.rpm

you are also running both mysql and mysql-iworx

The second appears to replace the first at least on my boxex.

Anyway, it’s up to you what you want to try but here’s some other things to look at.

For the record this is what I have on My current CentOS box:



[root@iworx root]# rpm -qa | grep mysql
mysql-iworx-4.0.21-3.cos3x.iworx
mysql-shared-compat-4.0.21-100.iworx
mysql-server-4.0.21-104.iworx
mysql-client-4.0.21-104.iworx
php-mysql-4.3.11-100.cos3x.iworx
mysql-devel-4.0.21-104.iworx
[root@iworx root]#
9

After checking the $dbms value was set to “”

Changed to “mysql” and it works fine.

Any idea why the scriptworx would leave the $dbms value as “” instead of “mysql” ?

works :slight_smile:

Thanks for the help again

10

If you can reproduce this case consistently, I’d be glad to take a look and see why ScriptWorx couldn’t determine the MySQL version properly. If you could open a support ticket I will take a look and hopefully we can prevent other folks from having the same problem. :slight_smile: Glad it’s fixed.

–Dustin