This is a message generated by libnss-mysql - nothing to do with postfix per-se. If it's not breaking anything, I wouldn't worry *too* much about it, but I would like to track down what's causing it. Can you give me some details on what O/S you're running, version of postfix, and what you're doing with postfix that causes those messages to come up? If I can reproduce it, I'll be able to track it down. libnss-mysql 1.0?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-08-31
Redhat 7.3, Postfix 2.0.13, libnss-mysql-1.0-1
I am doing domain, alias, and mailbox lookups through a mysql database, and using saslauthd to authenticate SMTP users through courier-imap which authenticates with the same database (yeah, it's kind of convoluded :) ). It's a pretty basic Postfix,courier-imap,mysql setup with saslauthd thown in.
It's not breaking anything, it's just making my log files bigger :)
Thanks for your help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-09-12
Just noticed that it's throwing the same error with apache in /var/log/messages. Looks like it happens everytime a page is requested.
from /var/log/messages:
Sep 11 20:12:09 localhost httpd: libnss-mysql: Unable to save socket info
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This appears to be related to using the RPM. My guess is that it's due to the statically-compiled-in mysql libs conflicting with the mysql libs your httpd is loading.. Do you have php with mysql on your apache server?
Not sure why it would affect postfix unless it's also using mysql...
Could you remove the RPM and install from source for me? Meanwhile I"ll keep digging.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I take that back. It looks like this happens when using the MySQL 4.x client libs (which the RPM contains). If you're using Mysql 3.x you can compile from source to make the message go away (which *is* breaking the ability for apache and postfix to look up nss-mysql users). And I'll find out why this is breaking with 4.x
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here's the problem. libnss-mysql is compiled against a different-enough version of the mysql libraries than httpd/php & postfix is that it's causing problems. When I made sure my php and my libnss-mysql were compiled against the same version, the problem went away. Now, since you're using the RPM, you'd have to use MySQL 4.0.13 and recompile. If you're using RedHat RPMs for php and whatnot, .. you'll have to compile libnss-mysql from source.
I'll investigate dynamically loading the mysql libs instead of compiling against them in the next version.. that may prove a little difficult, however. That would be the only real solution I can think of.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-09-21
Thanks for looking into it. I'll compile it from source.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you wouldn't mine, can you check out thew new RPM I just uploaded (1.0-2)? It should fix this problem (It did with my test apache environment). Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure why Postfix cares that I started using nss-mysql, but I am getting lines like this in my logs:
Aug 28 21:38:14 localhost postfix/flush[30054]: libnss-mysql: Unable to save socket info
I asked the Postfix mailing list, but I got no response.
Anyone have any experience with this?
This is a message generated by libnss-mysql - nothing to do with postfix per-se. If it's not breaking anything, I wouldn't worry *too* much about it, but I would like to track down what's causing it. Can you give me some details on what O/S you're running, version of postfix, and what you're doing with postfix that causes those messages to come up? If I can reproduce it, I'll be able to track it down. libnss-mysql 1.0?
Redhat 7.3, Postfix 2.0.13, libnss-mysql-1.0-1
I am doing domain, alias, and mailbox lookups through a mysql database, and using saslauthd to authenticate SMTP users through courier-imap which authenticates with the same database (yeah, it's kind of convoluded :) ). It's a pretty basic Postfix,courier-imap,mysql setup with saslauthd thown in.
It's not breaking anything, it's just making my log files bigger :)
Thanks for your help.
Just noticed that it's throwing the same error with apache in /var/log/messages. Looks like it happens everytime a page is requested.
from /var/log/messages:
Sep 11 20:12:09 localhost httpd: libnss-mysql: Unable to save socket info
roger that. I'll take a look into it and let you know.
This appears to be related to using the RPM. My guess is that it's due to the statically-compiled-in mysql libs conflicting with the mysql libs your httpd is loading.. Do you have php with mysql on your apache server?
Not sure why it would affect postfix unless it's also using mysql...
Could you remove the RPM and install from source for me? Meanwhile I"ll keep digging.
I take that back. It looks like this happens when using the MySQL 4.x client libs (which the RPM contains). If you're using Mysql 3.x you can compile from source to make the message go away (which *is* breaking the ability for apache and postfix to look up nss-mysql users). And I'll find out why this is breaking with 4.x
Here's the problem. libnss-mysql is compiled against a different-enough version of the mysql libraries than httpd/php & postfix is that it's causing problems. When I made sure my php and my libnss-mysql were compiled against the same version, the problem went away. Now, since you're using the RPM, you'd have to use MySQL 4.0.13 and recompile. If you're using RedHat RPMs for php and whatnot, .. you'll have to compile libnss-mysql from source.
I'll investigate dynamically loading the mysql libs instead of compiling against them in the next version.. that may prove a little difficult, however. That would be the only real solution I can think of.
Thanks for looking into it. I'll compile it from source.
If you wouldn't mine, can you check out thew new RPM I just uploaded (1.0-2)? It should fix this problem (It did with my test apache environment). Thanks!