Installation errors

[everity]

I have been trying to get this to work for 3 weeks, but to no avail. It is a Virtuozzo VE running
CENTOS Enterprise 4.6 i686
cPanel 11
PHP 5.2.5
MySQL 5.0.45

Based on the options available, I assumed the file for CentOS 4.3 i386 was the best match, so I downloaded
http://download1.parallels.com/SiteBuilder/4.2.0/sitebuilder-4.2.0-centos4.build08030317.tar.gz

The only dependency I'm aware of that isn't working is libmysqlclient.so.14, because MySQL 5 doesn't use it. My first question: I'd rather not have to downgrade to an ancient version of MySQL. Is that the only way to use SiteBuilder?

In any case, I ran all the RPM's, and they appear to have installed, but of course there are problems.

ERROR 1
[2008 Apr 22 12:27:15] [FATAL] No suitable PHP found
Fatal error encountered at /usr/local/sitebuilder/utils/SB/Logging.pm line 121
SB::Logging::Log('SB::Logging=HASH(0x840bab4)', 5, 'No suitable PHP found') called at /usr/local/sitebuilder/utils/S$
SB::Utils::checkParameters() called at configure line 303
main::main() called at configure line 377

Check.php looks like this
OK : supported version of PHP found (5.1.X or newer - 5.2.5)
ERROR : extension sitebuilder3 must be on
OK : extension pdo in state on found
OK : extension pdo_mysql in state on found
OK : extension sqlite in state on found
OK : extension dom in state on found
OK : extension libxml in state on found
OK : extension xml in state on found
OK : extension xsl in state on found
OK : extension spl in state on found
OK : extension pcre in state on found
OK : extension session in state on found
OK : extension simplexml in state on found
OK : extension ftp in state on found
OK : extension openssl in state on found
OK : extension mbstring in state on found
OK : extension soap in state on found
OK : extension gd in state on found
OK : extension ctype in state on found
OK : extension zlib in state on found
OK : extension iconv in state on found
OK : extension curl in state on found
OK : extension posix in state on found
OK : extension mysql in state on found
OK : supported SQLite version 2.x found
WARNING : SQLite UTF-8 encoding not found (current is iso8859)
OK : GD library PNG support found
OK : GD library GIF support found
OK : GD library JPG support found
OK : GD library WBMP support found
OK : supported GD library version 2.0.1 (or newer) found
OK : setting magic_quotes_gpc in state off found
OK : setting magic_quotes_runtime in state off found
OK : setting open_basedir in state off found
OK : setting safe_mode in state off found
OK : setting zend.ze1_compatibility_mode in state off found
OK : setting mbstring.internal_encoding in state UTF-8 found
OK : config file was successfully parsed
ERROR : unable to connect to MySQL database (SQLSTATE[28000] [1045] Access denied for user 'sitebuilder_db'@'localhost' (using password: YES))

More Info

# sb_config --help|grep php
--phpcli_path PHP CLI executable
--phpcgi_path PHP CGI executable

# cat /opt/php52/etc/php.d/sitebuilder3.ini
extension=sitebuilder3.so

# rpm -qa|grep -i sitebuilder-core
sitebuilder-core-4.2.0-centos4.build08030317

# rpm -ql sitebuilder-core
/opt/php52/etc/php.d/sitebuilder3.ini
/opt/php52/lib/php/modules/sitebuilder3.so

# cat /opt/php52/etc/php5/conf.d/sitebuilder3.ini
cat: /opt/php52/etc/php5/conf.d/sitebuilder3.ini: No such file or directory

# /opt/php52/bin/php5 -m|grep sitebuilder
/opt/php52/bin/php5: error while loading shared libraries: libmysqlclient.so.14: cannot open shared object file: No such file or directory

I am at a dead end. I have a lot of customers on another server that are anxious to try this out because they are not happy with a competing product, but I need some help getting this to work.

 

[Dmitry Frantsev]

In this case I can see at least 3 issues:

1. "ERROR : unable to connect to MySQL database (SQLSTATE[28000] [1045] Access denied for user 'sitebuilder_db'@'localhost' (using password: YES))"
It means that Sitebuilder could not connect to MySQL database and most probably Sitebuilder user and database were not created in MySQL. Most probably this happens because there is password defined somewhere in /etc/my.cnf or /root/my.cnf file. Try to check it. If there is password defined you can try to run following command:

# sb_config --db_admin_name root --db_admin_passwd "MySQL administrator password"

If this command goes well after that better install Sitebuilder RPMs one more time with '--force' option.

2. "No suitable PHP found" - this means that for current Sitebuilder installation not appropriate PHP is used. As I understand right now default PHP installation from Cpanel is used which does not observe all requirements. So it is better to use PHP which goes with Sitebuilder installation.
Command "sb_config --help|grep php" should output something like this:

# sb_config --help|grep php
--phpcli_path PHP CLI executable [/opt/php52/bin/php5]
--phpcgi_path PHP CGI executable [/opt/php52/cgi-bin/php5]

Try to redefine this in /usr/local/sitebuilder/conf file or by running following command:

# sb_config --phpcli_path /opt/php52/bin/php5 --phpcgi_path /opt/php52/cgi-bin/php5

3. "libmysqlclient.so.14: cannot open shared object file: No such file or directory"

As a workaround you can try to create symlink from libmysqlclient.so.15 to libmysqlclient.so.14 or get only this library libmysqlclient.so.14 (from RPM package for example) and put it into appropriate place.

Hope it helps. Check it up and let me know about the results.

 

[everity]

Thank you for your quick and thorough reply. Unfortunately, the problems have yet to be solved.

1. Correct, databases were not created. Password shows correctly in /root/my.cnf

# sb_config --db_admin_name root
[FATAL] No suitable PHP found
There were some configuration errors, check logs
Logs saved to /usr/local/sitebuilder/tmp/sb_config-0804231418.log
(No change...)

I tried re-installing all sitebuilder rpm's anyway with --force and --nodeps, but all the same problems are still there.

2. There is nothing in usr/local/sitebuilder/conf at all relating to the PHP path, so I added these lines...
phpcli_path = /opt/php52/bin/php5
phpcgi_path = /opt/php52/cgi-bin/php5

then I also tried

phpcli_path = /opt/php52/bin/php5
phpcgi_path = /opt/php52/cgi-bin/php5

[B]# sb_config --phpcli_path /opt/php52/bin/php5[/B]
[FATAL] No suitable PHP found
There were some configuration errors, check logs
Logs saved to /usr/local/sitebuilder/tmp/sb_config-0804231431.log

Nothing I did worked:  
[B]# sb_config --help|grep php[/B]
 --phpcli_path        PHP CLI executable
 --phpcgi_path        PHP CGI executable

I went into Utils.pm and redefined the above variables just above line 109 where the "No suitable PHP found" error was coming from, just to see what would happen.  This resulted in different errors, but at least it made a difference.  In any case, I changed it back.  

3. Symlinks made no difference either.  Hopefully I entered them correctly... (I tried twice.)
[B]# ln -s /usr/lib/libmysqlclient.so.15 /usr/lib/libmysqlclient.so.14[/B]
(it said "File Exists")

This broke MySQL completely.   I had to reinstall all the MySQL-related rpm's.  To be sure, I also tried
[B]# ln -s /usr/lib/libmysqlclient.so.14 /usr/lib/libmysqlclient.so.14[/B]
(File Exists)

Still, the same problem continues...

[B]# /opt/php52/bin/php5 -m|grep sitebuilder[/B]
/opt/php52/bin/php5: error while loading shared libraries: libmysqlclient.so.14: cannot open shared object file: No such file or directory

If this ever works, will we have to go through this every time something changes on the server?  Will customer web sites go down constantly?  Why is this software so difficult?  

Nothing personal, I appreciate the hard work you've put into this forum, and I know the end result is a quality product, but from a hosting provider's perspective, you guys would be getting at least ten times as much business if this weren't so hard to set up and maintain.  I actually tried a couple years ago, and neither myself nor the techs were able to get it to work.  So, we installed a competing builder instead, on a production server no less (I won't mention the name unless asked).  The entire process took 15 minutes from download to the first sale, and it has worked almost flawlessly ever since, even through major upgrades. Why can't SB be a little more like that?  [B]:)[/B]

Seriously, this is a brand new VE that has never been used for anything else. It has no accounts on it yet.  Nothing is 'broken' or outdated on our end.  Why can't SB just work?

Sorry to be so blunt, but this is undeniably the MOST difficult software I have ever encountered.  You really should find a way to make it run more easily, as that would result in a lot more sales!!

 

[Dmitry Frantsev]

Try to use following command:

sb_config --db_admin_name root --db_admin_passwd <password from my.cnf>

If this does not help you can try to set appropriate root password for connecting to MySQL database here /usr/local/sitebuilder/utils/SB/Defaults.pm:

'host' => 'localhost',
'username' => 'root',
'password' => '',
'dbname' => 'sitebuilder3',

Instead of empty one, try to put correct one and re-run RPM installation procedure.

Actually, Sitebuilder installation goes well in most cases. This situation related to specific CPanel configuration on server which could affect installation. I set up Sitebuilder into Cpanel many times and can say that it can be installed and work without any issues.
Such issues with installation on Cpanel was already passed to developers and quality assurance teams. In future versions, this should be improved and some general recommendations done before starting installation process on Cpanel server.

Hope it helps. Please let me know about the results.

 

[everity]

Sorry, still no change, even after manually updating utils.pm and re-installing the rpm's. I'm giving up for now. In any case, I appreciate your support, and may try again in another year or two.

 

[Dmitry Frantsev]

If there is still a chance you would like to try you can create a ticket here for support
http://www.parallels.com/en/support/sitebuilder/ and give me ticket ID, so I could process it for you.

 

[mdiberi]

I have also been having this same error:

[FATAL] No suitable PHP found
There were some configuration errors, check logs
Logs saved to /usr/local/sitebuilder/tmp/sb_config-0804231431.log

In my case ioncube loader was the problem and I had to do a force rpm install in order to eliminate the error.