Sriram Natarajan wrote:
> Neal
> Can you try create the below symbolic link and see if  it helps
> ln -sf /usr/mysql/5.0/lib/mysql/libmysqlclient.so.15  
> /usr/mysql/5.0/lib/mysql/libmysqlclient.so.12

Did the above command as root.  No change.
Do I need to restart anything?
Is there anything I can check or method to diagnose?
I could provide a login to the system, or do a quick phone call to debug?

Neal
x46423

>
> If this does address your issue, then this issue is because of CR: 
> 6625381 and I will be addressing this issue with build 83
>
> thanks
> sriram
>
> Neal Pollack wrote:
>> Hi:
>>
>> I've been playing with webstack to learn how it's configured on 
>> Solaris builds now.
>> Previously, I used to either install blastwave packages, or build 
>> from source in /usr/local.
>>
>> I can't see that php5 is loading the mysql.so connector?
>> The gnome gui for webstack shows mysql and apache2 running.
>> When I put a phpinfo.php page in the document root, I am not
>> seeing the mysql status block that my older servers show.
>>
>> php.in does indeed show mysql.so and it is not commented out.
>> If I manually run /usr/mysql/5.0/bin/mysql I can get status;
>>
>> ./mysql  Ver 14.12 Distrib 5.0.45, for pc-solaris2.11 (i386) using 
>> readline 5.0
>>
>> Connection id:        5
>> Current database:   Current user:        root at localhost
>> SSL:            Not in use
>> Current pager:        stdout
>> Using outfile:        ''
>> Using delimiter:    ;
>> Server version:        5.0.45-log Source distribution
>> Protocol version:    10
>> Connection:        Localhost via UNIX socket
>> Server characterset:    latin1
>> Db     characterset:    latin1
>> Client characterset:    latin1
>> Conn.  characterset:    latin1
>> UNIX socket:        /tmp/mysql.sock
>> Uptime:            1 day 4 hours 39 min 36 sec
>>
>> Threads: 1  Questions: 4  Slow queries: 0  Opens: 12  Flush tables: 
>> 1  Open tables: 6  Queries per second avg: 0.000
>> --------------
>>
>> mysql>
>>
>>
>> One of my older servers built from source shows the following mysql 
>> block in phpinfo.php
>> that seems missing from the build 81 Nevada webstack;
>>
>>
>>     mysql
>>
>> MySQL Support     enabled
>> Active Persistent Links     0
>> Active Links     0
>> Client API version     5.0.24
>> MYSQL_MODULE_TYPE     external
>> MYSQL_SOCKET     /tmp/mysql.sock
>> MYSQL_INCLUDE     -I/opt/csw/mysql5/include/mysql
>> MYSQL_LIBS     -L/opt/csw/mysql5/lib/mysql -lmysqlclient
>>
>>
>> Directive     Local Value     Master Value
>> mysql.allow_persistent     On     On
>> mysql.connect_timeout     60     60
>> mysql.default_host     /no value/     /no value/
>> mysql.default_password     /no value/     /no value/
>> mysql.default_port     /no value/     /no value/
>> mysql.default_socket     /no value/     /no value/
>> mysql.default_user     /no value/     /no value/
>> mysql.max_links     Unlimited     Unlimited
>> mysql.max_persistent     Unlimited     Unlimited
>> mysql.trace_mode     Off     Off
>>
>>
>>
>>
>> THe above displays right under the libxml portion of phpinfo output.
>>
>> So on Nevada build 81, the symptom is that I  can't get php apps to 
>> connect
>> to mysql.   For example, Jyri's phpmyadmin build simply complains that
>>
>>
>>   phpMyAdmin - Error
>>
>> Cannot load /mysql/ <http://php.net/mysql> extension. Please check 
>> your PHP configuration.
>>
>>
>>
>> Is there anyone that simply installed build 81 and started using a 
>> php app with mysql
>> that can tell me what they needed to configure or fix?   Others on 
>> this alias state that
>> it is working right out of the box.   I can only say that for the 
>> individual pieces, and also
>> for php/apache2 integration.   I can't see that   apache->php5-> 
>> mysql5 is connecting.
>>
>>
>> Thanks,
>>
>> Neal
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>>
>>
>> webstack-discuss mailing list
>> webstack-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/webstack-discuss
>>   


Reply via email to