Red Hat Bugzilla – Bug 88716
"Failed to setup RT_SIGNAL_LEASE handler" error in /var/log/samba/smbd.log
Last modified: 2014-08-31 19:24:49 EDT
Description of problem:
When samba starts i get a "Failed to setup RT_SIGNAL_LEASE handler" error
Version-Release number of selected component (if applicable):
All the time.
Steps to Reproduce:
1. Restart samba.
I get this error not only at startup, but about every 30 minutes. System is
RH9 full install with all updates applied. More details available on request.
Ok, after opening the bug report, and with more time, i found that i also get the error
messages frequently. I have disabled kernel oplocks in the samba configuration file for
Please attach your /etc/samba/smb.conf file to this bug report so I'll have at
least some chance of replicating this problem.
Created attachment 91258 [details]
This smb.conf file triggers the error
The smb.conf file has been migrated from Redhat 8.
This is the one of the errors it now produces:
[2003/04/23 21:11:47, 0] smbd/oplock_linux.c:linux_init_kernel_oplocks(287)
Failed to setup RT_SIGNAL_LEASE handler
Created attachment 91270 [details]
This is my smb.conf
Created attachment 91915 [details]
Another conf that produces the error msg.
Here's another one. This is on RH9 w/all current updates (samba-2.2.7a-8.9.0).
Possibly helpful info from linux.samba:
I have the exact same problem. It makes my samba server VERY slow.
Created attachment 92599 [details]
A patch to fix samba
Samba uses signal 33 and 34, which may be used by threads.
This patch seems to fix it.
I started seeing this problem recently, when I installed the kernel-2.4.20-20.9
and samba-2.2.7a-8.9.0 updates. I don't know which of the two updates
caused/unmasked the problem.
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still
running Red Hat Linux, you are strongly advised to upgrade to a
current Fedora Core release or Red Hat Enterprise Linux or comparable.
Some information on which option may be right for you is available at
Red Hat apologizes that these issues have not been resolved yet. We do
want to make sure that no important bugs slip through the cracks.
If this issue is still present in a current Fedora Core release, please
open a new bug with the relevant information.
Closing as CANTFIX.