Re: [Nss-mysql-users] nss-mysql and NSCD

[Guillaume Morin]

On 05 Oct  1:05, Markus Valtin wrote:
> I recently see logmessages like:
>       Oct  5 00:35:34 rs_ewam nss-mysql[4765]: client 211.53.35.250#62208: 
> query (cache) 'foobar/A/IN' denied
>       Oct  4 13:33:14 rs_ewam nss-mysql[4765]: lame server 
> resolving 'e-burg.su' (in 'e-burg.su'?): 195.58.27.158#53
>       Oct  4 13:33:15 rs_ewam nss-mysql[4765]: unexpected RCODE (SERVFAIL) 
> resolving 'ns.e-burg.su/AAAA/IN': 194.226.235.22#53
> 
> 
> My research indicates that this comes somehow from NSCD or named because on a 
> other server I get a similar message from named (libnss-mysql or nscd are not 
> installed).
> So my Question is now:
> What happened??? Is it a serious problem? Why happened? 

nss-mysql logged a message before these messages and initialized the
syslog name to nss-mysql before the program did.
These messages are from bind9, I believe.  
Go back up in the log and look for the first nss-mysql message and fix
whatever is reported.  This will avoid this problem in the future.

> And what means the line: (except the obvious)
> "YOU SHOULD NOT USE NSCD with this version." I did not find any information 
> WHY not use nscd.

nss-mysql used to have problems with nscd, I believe they are fixed though.

Guillaume.

-- 
Guillaume Morin <address@hidden>

 I am Ubik. Before the universe was, I am. I made the suns. I made the worlds.
                                (Philip K. Dick)