I have been running libnss-mysql for quite some time now. Almost two years without any hickups at all.
Recently we upgraded our mysql server to version 5.0.33 (before we used 4.1.21) and libnss-mysql to 1.5. After this upgrade we are unable to start mysql without it crashing.
Removing the mysql entry from group: (and shadow:) in nsswitch.conf fixes it temporarily and we can start mysqld. Enabling group: (and shadow:) in nsswitch.conf after mysql is started works fine. Restarting mysql from here causes a crash obviously.
I need help to resolv this issue. Please advise.
Here is some additional information about our mysql server.
* Debian GNU/Linux 3.0 (sarge)
* Linux server1 2.6.20 #2 SMP Thu Feb 8 09:56:41 CET 2007 i686 GNU/Linux
* mysql Ver 14.12 Distrib 5.0.33, for pc-linux-gnu (i686) using EditLine wrapper
nsswitch.conf looks like this:
passwd: compat mysql
group: compat mysql
shadow: compat mysql
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
Thanks in advance.
Nicklas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i have the same Problem as Nicklas.
Is there a new version of libnss-mysql or a fix on that problem?
Is libnss-mysql uptodate???
Do the developers work on libnss-mysql or will there be no more updates??
thx for your answers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To work arround the problem I wrote a small shell script that takes care of starting up mysql. The trick is not to have mysql enabled in nsswitch.conf while mysql is starting up.
I thought I'd chime in and say that I'm still here, I still get notifications of posts and read them ...
I'll fix serious bugs (especially anything security related), possibly merge submitted code for new features, etc .. but at this time, I'm not making use of the software personally or professionally anymore so naturally I don't focus on it.
The challenge especially with a bug like this is that it's so specific to a distribution or a version of 1 of 100 dependencies that I'd either need far more detail about the crash (e.g. an strace plus libnss-mysql debug logs) or I'd need to install the OS, get it patched and versioned the same as you have it, try to reproduce it (which often is very hard to do), and then finally fix it. That's a huge amount of work for a relatively small problem that has a workaround.
Another option is to give me a login to a machine experiencing the problem so I can diagnose it.. but I understand that's usually not possible.
Regards,
-=| Ben
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm actually adminning Windows systems now (how often do you see a guy go from Linux to Windows?!?) -- and even if that weren't the case, I don't actually admin the base OS -- I'm more of an app admin now.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi!
First of all thanks for this great software!
I have been running libnss-mysql for quite some time now. Almost two years without any hickups at all.
Recently we upgraded our mysql server to version 5.0.33 (before we used 4.1.21) and libnss-mysql to 1.5. After this upgrade we are unable to start mysql without it crashing.
Removing the mysql entry from group: (and shadow:) in nsswitch.conf fixes it temporarily and we can start mysqld. Enabling group: (and shadow:) in nsswitch.conf after mysql is started works fine. Restarting mysql from here causes a crash obviously.
I need help to resolv this issue. Please advise.
Here is some additional information about our mysql server.
* Debian GNU/Linux 3.0 (sarge)
* Linux server1 2.6.20 #2 SMP Thu Feb 8 09:56:41 CET 2007 i686 GNU/Linux
* mysql Ver 14.12 Distrib 5.0.33, for pc-linux-gnu (i686) using EditLine wrapper
nsswitch.conf looks like this:
passwd: compat mysql
group: compat mysql
shadow: compat mysql
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
Thanks in advance.
Nicklas
Hi All,
i have the same Problem as Nicklas.
Is there a new version of libnss-mysql or a fix on that problem?
Is libnss-mysql uptodate???
Do the developers work on libnss-mysql or will there be no more updates??
thx for your answers
Markus,
To work arround the problem I wrote a small shell script that takes care of starting up mysql. The trick is not to have mysql enabled in nsswitch.conf while mysql is starting up.
Script:
#!/bin/bash
case "$1" in
start)
cp /etc/nsswitch.conf.tpl /etc/nsswitch.conf
/etc/init.d/mysql.server "$1"
cp /etc/nsswitch.conf-mysql.tpl /etc/nsswitch.conf
;;
stop)
/etc/init.d/mysql.server "$1"
cp /etc/nsswitch.conf.tpl /etc/nsswitch.conf
;;
*)
echo "Unknown option. Try start or stop."
;;
esac
exit 0
nsswitch.conf-mysql.tpl:
passwd: compat mysql
group: compat mysql
shadow: compat mysql
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
nsswitch.conf-mysql.tpl:
passwd: compat
group: compat
shadow: compat
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
Hope this helps.
Nicklas
I thought I'd chime in and say that I'm still here, I still get notifications of posts and read them ...
I'll fix serious bugs (especially anything security related), possibly merge submitted code for new features, etc .. but at this time, I'm not making use of the software personally or professionally anymore so naturally I don't focus on it.
The challenge especially with a bug like this is that it's so specific to a distribution or a version of 1 of 100 dependencies that I'd either need far more detail about the crash (e.g. an strace plus libnss-mysql debug logs) or I'd need to install the OS, get it patched and versioned the same as you have it, try to reproduce it (which often is very hard to do), and then finally fix it. That's a huge amount of work for a relatively small problem that has a workaround.
Another option is to give me a login to a machine experiencing the problem so I can diagnose it.. but I understand that's usually not possible.
Regards,
-=| Ben
Ben wrote:
> I'm not making use of the software
How are you currently storing passwords? Hopefully, you are free from the shackles of sysadmin work an that is why you don't make use of libnss. :)
- Rudy
I'm actually adminning Windows systems now (how often do you see a guy go from Linux to Windows?!?) -- and even if that weren't the case, I don't actually admin the base OS -- I'm more of an app admin now.