similar to: Semaphore Time Expired

I have had samba running on my freebsd box for about 2 years now, and my / partition is 50MB (it is just a fileserver with ssh and nothing more). However, recently (about a month or two ago) it disconnects itself from my LAN with warnings like: semaphore timeout has expired. I go to the console on the box and it says that the disk is full (its not, but the root directory is at 101%) I cannot

UPDATE: We found out that there was still an entry in /etc/rc.local to start up the old SAMBA after upgrading and setting up to run from inetd.conf. Once the /etc/rc.local entry was removed, we no longer receive the "semaphore timeout period has expired" messages and we are able to connect to the shares. Ben Burruel Sr. Systems Manager Metrics & Mainframe Capacity Planning San

Hello Hamish. I found your message just googling for Suse and sk98lin. Did you solve your problem? I had the same case and only way to restore was to change NIS driver speed settings from AUTO to 10Mb. And it was not related to OS as the same problem is in WXP ( I have dual boot, ASUS P4P800, integrated GB NIS ). Oleg.

Hello everyone I have samba 3.0.3pre2-SuSE running on SuSE 9.0 i386, this is from SuSE rpms not source. The box is joined to a 2k3 domain, wbinfo works fine, acls work and users are authenticated properly. I had a problem yesterday and cannot seem to find a solution: I have been copying data across from the old SBS server, this seems to work fine for about 5 minutes, then completely crashes

hi, I hv recently installed and configured samba-3.0.10-1 with Ldap and smb tools. Everything looks good, i mean Samba, LDAP and smbldaptools everything. But now when i am trying to access the shares as well as trying to join w2k prof desktop to the domain its giving the error "The semaphore timeout period has expired" Can any one let me know what could be the problem? Thanks &

Hi all I have a samba pdc (3.0.21c) with openldap (2.3.19) on a Redhat Enterprise Linux 4 (2.6.9-5EL-SMP) kernel i have Domain Member servers (samba server), i redirect my users to share declared to in my domain member servers. using logon script which gets executed when users logon . my clients use windows 2k professional and windows xp. my logon script is @ echo off net time \\mypdc /set /yes

Hi. We are running Solaris 2.6, Samba 2.0.0. NT workstations can connect to all samba shares, but W2K workstations can't. Some users get "Semaphore Timeout Period has expired", some get "Network name not found". The NT and W2K users login to the same NT domain. There is a WINS entry matching the Unix server hostname. Any ideas? Thank you. -Anoosh Here is smb.conf

[.. most data for the archives ..] I've got several windows 2000 machines and a samba 2.2.12 on solaris 7. for years only one of the windows machines has ever needed to connect to the samba server. just a couple of days ago, it was necessary for a second machine to connect to the samba server. Whenever the second machine tried to load the network share, windows came back with its "The

Hello all, I have a very annoying situation (at least at my end). I set up Samba 2.0.5 on a Digital UNIX 4.0F system sitting on a Compaq DS20 server with great success.... until recently. I set up three directory file shares with no problems, when I tried to set up a forth, quite a while after setting up the inital three, I tried to access it from a NT box, I got the message server not found,

The following changes since commit 6438fbcb6cb7e0cd40e4bb3681ada047fe77ffdd: Gene Cumm (1): Allow for UNDIIF_ID_DEBUG in 1 mk line are available in the git repository at: git://github.com/geneC/syslinux.git elflink-undi-thread-for-mfleming Gene Cumm (3): core/lwip/undi: Improve UNDIIF_ID_DEBUG messages core: mbox/semaphore NULL checks core: make

We have newly installed ADSL/speedTouch 510 modem. After the installation, we are getting problems with out Win2K machines. On out NT workstation everything is OK, but on the Win2K we are getting following error, "The semaphore timeout period has expired" whne trying to connect to the domain (GARAGET), My Network Places Entire network MS Windows Network Garaget (our

Hi I'm getting a "semaphore timeout period has expired" error trying to connect a WinXP desktop to out linuxbox. (Redhat 7.1 / samba-2.0.7-36) I can't seem to find help about this in the documentation. Has anyone had any experience with this? Thanks Stuart -------------- next part -------------- HTML attachment scrubbed and removed

I am running Samba 2.0 and occasionally get a "semaphore timeout period has expired" message when accessing Samba shares on a Digital UNIX 4.0e server. Does anyone know what kernel semaphore settings should be. Or could a upgrade to 2.0.7 help. I new to Samba and am very green with this product. Thanks David

I ran some local testing on my Fedora 29 system via: $ ./nbdkit memory 1m $ for i in `seq 10`; do ./nbdkit -U - --filter=stats nbd \ statsappend=true statsfile=$file hostname=localhost port=10809 \ --run '~/libnbd/examples/threaded-reads-and-writes $unixsocket' done Pre-patch, the runs averaged 1.266s, 1.30E+08 bits/s Post-patch, the runs averaged 1.154s, 1.42E+08

When I try to connect to smbd on a SUN Solaris 2.6 with a running oracle database, I get the folloing error: [1999/03/25 10:25:30, 1] smbd/files.c:file_init(219) file_init: Information only: requested 10000 open files, 1014 are available. [1999/03/25 10:26:07, 0] locking/shmem_sysv.c:sysv_shm_open(563) Can't create or use semaphore [1]. Error was No space left on device [1999/03/25

Tom, Did you resolve your problem: Question: is this a Samba configuration error or a Win2K configuration error. The 98 and ME connect just fine to SAMBA. If so, what was the answer? Thank you, Jim Majczek

Hi Jeremy, Thanks for your prompt response. I implemented your suggestion and added those lines to includes.h, recompiled and reinstalled the samba on the test machine. Unfortunately it made no difference. :-(. I added some debugging code and looked what happened : -------------------------------------------------------------------- DEBUG(4,("Trying sysv shmem open of size

Hi I have a newly installed FreeBSD 6.0 release machine on which I am getting the following error on the console: "ad4: req=0xc23bc258 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !!" This is generally associated with heightened disk activity, but it happens inevitably after a while (minutes or hours) if the machine is running. The atacontrol list shows:

I've just installed Samba on Solaris-8. When i start 'smbd' the following errors appear in the 'log.smb' log file: # tail ../var/log.smb [2000/07/13 13:53:19, 0] locking/shmem_sysv.c:sysv_shm_open(597) ERROR: root did not create the semaphore [2000/07/13 13:53:19, 0] locking/locking.c:locking_init(174) ERROR: Failed to initialise share modes

I start Samba process smbd and nmbd correctly But smbstatus did not run, it return : # ./smbstatus Samba version 2.0.5a Service uid gid pid machine ---------------------------------------------- ERROR: root did not create the semaphore ERROR: Failed to initialise share modes Can't initialise shared memory - exiting Here is an extract of log.smb : [2001/12/20