Postmap Issue

2011-09-21 Thread Van Der Meulen, Mark
Hi All,

Has anyone seen this error when running postmap on FreeBSD 8.X?

mail# postmap /usr/local/etc/postfix/transport

/libexec/ld-elf.so.1: Shared object libmysqlclient.so.18 not found,
required by postmap

If not, does anyone have some advice on better places to look? Google
search has been fruitless.

 

P.S. mySQL is installed, and postfix was installed with mySQL support.

 

Thanks!

 

Mark

***
Travelex - www.travelex.com

Travelex Outsourcing Pty Limited [Currency Select businesss] is a limited 
company registered in Australia with company number: 127 747 586.

Information in this email including any attachment ('email') is confidential, 
may be privileged and is intended solely for the addressee. Unauthorised 
recipients are requested to preserve the confidentiality of this email, advise 
the sender immediately of any error in transmission, and then delete the email
from the recipient's mailbox without making copies. Any disclosure, copying, 
distribution or action taken, or omitted to be taken, in reliance upon the 
contents of this email by unauthorised recipients is prohibited and may be
unlawful.

Please note that no contracts or commitments may be concluded on behalf of 
Travelex Outsourcing Pty Limited [Currency Select businesss] or its groups of 
companies ('Travelex') by means of email, and no statement or representation 
made in this email is binding on 
behalf of Travelex.

DISCLAIMER: Whilst this message has been scanned for viruses, Travelex 
disclaims any responsibility or liability for viruses contained therein. It is 
therefore recommended that all emails should be scanned for viruses.
***
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Postmap Issue

2011-09-21 Thread Robert Bonomi

First things first.

_PLEASE_ !!!  Do not post from an account that includes these _stupid_ and
*LEGALLY*WORTHLESS* quote disclaimers unquote.  They are not worth the
electrons they're printed on.

They _do_ accomplish ONE thing -- they make the sender look like an idiot,
and =discourage= some people (those who _know_ what garbage those disclaimers
are) from offering helpful information.  People too uninformed to recognize
that such nonsense is being attached to their messages, or too incompetent
as to seek out an email service that does _not_ perform msuch sutpidities,
are _unlikely_ to be mentally alert enough to profit from advice offered.

/rant


 Date: Wed, 21 Sep 2011 16:17:03 +1000
 From: Van Der Meulen, Mark mark.vandermeu...@travelex.com.au
 Subject: Postmap Issue

 **
 * Travelex - www.travelex.com

 Travelex Outsourcing Pty Limited [Currency Select businesss] is a limited 
 company registered in Australia with company number: 127 747 586.

 Information in this email including any attachment ('email') is 
 confidential, may be privileged and is intended solely for the addressee. 
 Unauthorised recipients are requested to preserve the confidentiality of 
 this email, advise the sender immediately of any error in transmission, 
 and then delete the email from the recipient's mailbox without making 
 copies. Any disclosure, copying, distribution or action taken, or omitted 
 to be taken, in reliance upon the contents of this email by unauthorised 
 recipients is prohibited and may be unlawful.

 Please note that no contracts or commitments may be concluded on behalf 
 of Travelex Outsourcing Pty Limited [Currency Select businesss] or its 
 groups of companies ('Travelex') by means of email, and no statement or 
 representation made in this email is binding on behalf of Travelex.

 DISCLAIMER: Whilst this message has been scanned for viruses, Travelex 
 disclaims any responsibility or liability for viruses contained therein. 
 It is therefore recommended that all emails should be scanned for 
 viruses. 
 **
 *

 Hi All,

 Has anyone seen this error when running postmap on FreeBSD 8.X?

 mail# postmap /usr/local/etc/postfix/transport

 /libexec/ld-elf.so.1: Shared object libmysqlclient.so.18 not found, 
 required by postmap

 If not, does anyone have some advice on better places to look? Google 
 search has been fruitless.



 P.S. mySQL is installed, and postfix was installed with mySQL support.

This may be a 'version mismatch' between an existing 'libmysqlclient.so'
and what postmap expects  run a find(1) for libmysqlclient.so**' and
see what it reports, an in what directories. use option '-ls' so you can
see permissions as well as mere file existeance.

See also 'man ldconfig'.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Postmap Issue

2011-09-21 Thread Matthew Seaman
On 21/09/2011 07:17, Van Der Meulen, Mark wrote:
 mail# postmap /usr/local/etc/postfix/transport
 
 /libexec/ld-elf.so.1: Shared object libmysqlclient.so.18 not found,
 required by postmap

What version of mysql client do you have installed?

libmysqlclient.so.18 comes from databases/mysql55-client which became
the default MySQL version about 6 months ago.

There are two ways you can get this problem:

1) Incompatible version of MySQL client installed:

If you use binary packages from the FreeBSD ftp servers, they will be
compiled against mysql55 shared libs nowadays.  If you instal from
ports, it will automatically link against whatever version of MySQL
client you have installed.

However, if you had installed an older version of MySQL it wouldn't
automatically get upgraded to MySQL 5.5.x -- that you'ld have to do
manually.  So updating via pkgs could lead to the situation you see --
except you should have run into it about 6 months ago...

As I recall, the MySQL 5.1 to 5.5 upgrade is not particularly onerous,
but if you're upgrading MySQL server at the same time, you need to take
the DB down while you're doing the updates, and you need to run the
'mysql-after-upgrade' stuff to applie various changes to the standard DB
schema.

2) Correct version of mysql-client installed, but ld.so can't find the
  libmysqlclient shlib

So, assuming you've got mysql-client-5.5.x installed --

The MySQL ports install their shlibs into /usr/local/lib/mysql/ and add
that to the default list of paths for ld.so to search.  That should be
automatic, but maybe something went wrong.

What does:

   ldconfig -r | grep 'search directories'

return?  How about

   ldconfig -r | grep 'mysql'

?

If /usr/local/lib/mysql/libmysqlclient.so.18 is missing from the above,
then you can fix things up by:

  ldconfig -m /usr/local/lib/mysql

Cheers

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature