similar to: inotify trouble

I have setup a basic samba configuration without winbind, using security=user. I have a usermap file that maps everyone to the user ftp. I can see the username being changed to ftp and the user being allowed access. Yesterday I had everything working, no errors in the log. NOTHING has changed from yesterday to today, I know this because I'm the only one who works on samba right now. Today

I have Samba 2.2.4 installed on Redhat 7.3. I was trying to set up printers through it and everything works great on from a Windows 2000 Professional Client, but a Windows XP Client dies a miserable death when trying to view the properties of a printer. On the Windows XP Client side, I get: Properties clould not be displayed, procedure could not be finished On the Redhat 7.3 side, I'm seeing:

Ello -- I'm having an issue using Samba 3.0.25b on Linux 2.6.22.7 (Also had it occur, though more frequently with 3.0.25) where the log file will be filled to disk capacity with : [2008/02/20 11:30:58, 0] smbd/notify_inotify.c:inotify_handler(234) No data on inotify fd?! [2008/02/20 11:30:58, 0] smbd/notify_inotify.c:inotify_handler(234) No data on inotify fd?! [2008/02/20 11:30:58,

Dear Group members! Since I have set up a Samba PDC-Server (openSUSE 11.2-64bit with default package Samba 3.4.3) approx. 8 months ago, I have encountered 3 or 4 times a severe crash of Samba. What happens is that all over a sudden Samba floods /var/log/messages and /var/log/warn with the following message (cropped out date/time/servername, etc.): smbd[19724]:

Hello there This morning our main Samba server was pretty unresponsive running at a 30+ load average. After digging a bit what I found in the logs was the following. No data on inotify fd?! [2008/01/21 07:02:59, 0] smbd/notify_inotify.c:inotify_handler(234) That entry appears a billion zillion times in the log file until the file system is filled up leaving no space on the device and sending

A few months ago we bought a GIS software. It is running under Windows XP Pro. This software has stored its databases in dbf files, located on one samba share. Executables reside on each WinXP Pro client. The software simply uses dbf databases located on samba share. Each session of the gis opens about 500 files. I have four workstations that are allowed to run this software. [kirchner]

I've got a samba server that's occasionally spewing inotify errors. The classic, "smbd/notify_inotify.c:inotify_handler No data on inotify fd?" type errors solved by kernel change notify = false Now, everything is working perfectly on this box unless one or two users leave files open from specific machines (this is as far as I can tell, it's hard to get good info from the

Hello, One of the server I maintain has Ubuntu 8.04 LTS server with samba 3.0.28a. Kernel version is 2.6.24-16-server. The samba setup for this server is a workgroup environment, with user level security. At least once a week, sometimes more often, the server becomes unavailable because the system disk is full. It appears that the samba logs are the problem. Although the samba configuration

Hello, We have a RHEL4 x64 running for 3 years, which is a samba member server integrated with a AD domain without any problems (we was using samba-3.0.10-1.4E.6). Last Saturday we performed an entire server update, applying all RHN available patches. Everything is running fine, except for winbind service which has a strange behavior: often we are receiving some errors at logs, and the

I service a small office with 6 XP computers. I just installed a server running CentOS 5.4 and Samba 3.0.33. They use a program called "On-screen Takeoff". This program accesses a couple database files that live on the shared drive. "Projects.ldb" and "Projects.mdb" On-screen takeoff stays open all day, and maintains access to it's database files all day.

Had a server fill up completely with a samba workstation log file. The log file repeatedly had this information [2010/04/29 04:00:01, 0] smbd/notify_inotify.c:inotify_handler(240) No data on inotify fd?! about a billion times. In my smb.conf Ihave max log size = 50 set, so I was hoping the log file wouldn't get that big.

Hi, I'm going through my messages log and I've noticed a large amount of the following error going on. What affect would this have on the smb client that is connected to those pid's? Mar 11 11:35:24 process1 smbd[25349]: [2010/03/11 11:35:24, 0] smbd/notify_inotify.c:293(inotify_setup) Mar 11 11:35:24 process1 smbd[25349]: Failed to init inotify - Too many open files

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, all. Last night, access to our samba server was interrupted, and the only thing I can find is these repeated over and over again in the messages file: Jul 8 07:44:15 knorr winbindd[24628]: cli_pipe: return critical error. Error was NT_STATUS_PIPE_DISCONNECTED Jul 8 07:44:15 knorr winbindd[24628]: [2005/07/08 07:44:15, 0]

We recently upgraded our PDC from Debian 4 to Debian 5. That entailed an upgrade of Samba from 3.0.24 to 3.2.5. Since the upgrade we've had a very specific problem connecting to shares on a commercial NAS running Samba 3.0.34. The problem happens when users try to connect to shares from standalone servers--e.g., Windows XP Pro boxes that we use for testing. From those boxes users should be

Hi, When I try to connect to samba server from windows XP machines, I get an err "No process is on the other end of the pipe" .But some of the users running windows vista said they are not having any issues on that. The log.wb log says: [2010/01/20 16:43:41.368049, 0, pid=23202, effective(0, 1), real(0, 1)] rpc_client/cli_pipe.c:rpc_api_pipe(790) rpc_api_pipe: Remote machine

Hello, Hope you can help us out with a problem with samba / winbind; We have samba 3.0.21c with winbind running on an RHEL 4 server. This runs quite stable for more than a year now. But since the lasts weeks it appears that sometimes our users can't connect to the samba shares. I suspect that this problem has something to do with the integration of samba (winbind) with the Microsoft

Hello! I see where this came up on the list a few months and never really ws resolved. Someone resolved it by linking libnss_winbind ... But that's not my problem... I'm getting " Failed to join domain: failed to set machine spn: Operations error" when I do a net ads join. I've used this user account (me) to join many Samba 3.5.6 servers to the domain. Config file and

Installed Samba 3.0.10 via 'pkgadd' on Solaris 2.6 workstation s080 (137.223.31.80) - previously running Samba 2.2.8 which has worked for a long time. Samba 3.0.10 smb.conf file - changed to security =DOMAIN from SERVER at 2.2.8 version password server = 137.223.33.45, 137.223.33.72 - these are DCs # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date:

Hello, I've a problem on my system with inotify. In the smbd logfile are shown a lot messages like this: [2015/06/10 11:15:21.644453, 0, pid=57030, effective(12700, 100), real(0, 0)] smbd/notify_inotify.c:297(inotify_setup) Failed to init inotify - Too many open files [2015/06/10 11:15:23.968497, 0, pid=57030, effective(12700, 100), real(0, 0)] smbd/notify_inotify.c:297(inotify_setup)

Hello, I'm having some trouble with the winbind process I'm getting a lot of error: [2005/07/04 14:14:48, 0] libsmb/clientgen.c:cli_send_smb(155) Error writing 494 bytes to client. -1 (Broken pipe) [2005/07/04 14:14:48, 0] rpc_client/cli_pipe.c:rpc_api_pipe(435) cli_pipe: return critical error. Error was Write error: Broken pipe [2005/07/04 14:14:49, 0]