It's not a mysql v5 issue per se, but the new versions of the mysql RPMs for, at the very least, RHEL4, place the client libs in a spot that the SER stuff simply never sees for one reason or another.
If it's in /usr/lib, it just ignores its existence.
N.
On Thu, 08 Feb 2007 13:29:22 -0500, Steve Blair wrote
I'm starting to think this is a mysql v5 issue but I have not yet identified why.
-Steve
Josef.Bajada@go.com.mt wrote:
Hi,
I am having this problem with the mysql module on ser.
0(31212) ERROR: load_module: could not open module </opt/ser/modules/mysql/mysql.so>: /opt/ser/modules/mysql/mysql.so: undefined symbol: log 0(31212) parse error (30,13-14): failed to load module ERROR: bad config file (1 errors)
I can confirm that mysql.so exists in that directory. I have mysql 5.0.27 installed.
I have already tried to clean and make all from scratch but the problem remained.
Any ideas how to solve this?
Thanks a lot,
Josef
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers