similar to: Can't create or use IPC area

Hi there, I got SAMBA 2.0.6 on a Mandrake7 machine, and when I run SMBSTATUS, I get the following: Can't create or use IPC area. Error was File not Found ERROR: Failed to initialise share modes Samba version 2.0.6 Service uid gid pid machine ---------------------------------------------- Can't initialise shared memory - exiting Does anybody knows why is this

Hello. I just installed Samba 2.0.8 onto a shiuny new FreeBSD 4.3-STABLE machine, and all seems well from the client side of things - I can smbclient to other servers and access files and the whole nine yards. I even have Sharity-Light running and am able to mount shares that way. However, whenever someone tries to connect to my machine, they get denied, and I get this in the samba.log

I'm running the latest samba release (2.2.8a), and everything seems to be running fine. Except for something that does not look quite right. Connections to the IPC$ share are being left behind by samba once the user has logged off. And what's even more troubling is that the pid associated with the lingering IPC$ connection is picked up by the next smbd process, and then you have one pid

Greetings, Is there any way to get Samba to interact with MS-DOS? I am attempting to turn a Linux box into a VPN router for DOS clients. What I need to know is, can I get a CIFS protocol stack for MS-DOS, is a TCP/IP stack sufficient, are there any other solutions anyone knows about? Thank You. Tyrell Kumlin, Help Desk Cipher Systems Ltd. - Providing quality software solutions & services

Hi, I am running Samba version 2.2.5 with utmp turned on. I have a problem with utmp and not displaying who is currently logged in. The basic idea is that even though a user has logged off the computer (win2k pro) a connection to IPC$ remains. It gives this. [root@lifesaver root]# smbstatus -u scott Samba version 2.2.5 Service uid gid pid machine

Back to this problem Here a proof of it: 1. smbd version 3.0.11 started yaberge2@sda6 ==> p smbd root 13820 20662 0 08:05:39 - 0:00 /usr/local/samba/sbin/smbd -D -s/usr/local/samba/lib/smb.conf root 20662 1 0 08:05:39 - 0:00 /usr/local/samba/sbin/smbd -D -s/usr/local/samba/lib/smb.conf yaberge2@sda6 ==> /usr/local/samba/bin/smbstatus Samba version 3.0.11

We use samba purely as for file serving from Solaris 7 or 8 servers. THE PDC and BDCs are NT machines. We have been using Samba 2.0.7, but used 2.2.5 for a new server. One noticeable difference is that smbstatus lists a number of entries "IPC$ nobody nobody" which we did not see in 2.0.7. Is this normal in 2.2.5 or something I should be ivestigating? Eg trout# smbstatus

I had to increase the MAX_OPEN_FILES Parameter in "local.h". Since then i get the error in the logfile: Can't create or use IPC area. Error was File exists. Are there any solutions for this problem? I found similar questions but no answers in the digests. Olaf Dreyer

Hi all, I have a question about memory usage and IPC$ share. I'am auditing the swap usage of my server because I already have a problem with a full swap. I see that the smbd process take < 200Mo on swap : Example : PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 24429 lge 15 0 197m 39m 14m S 0.3 1.0 0:15.17 smbd but some process use more than 200Mo

After upgrading to 3.0.26a and moving to linux my member server gets hundreds of IPC$ connections when I run smbstatus. I also see in my logs the following... [2007/10/01 10:01:15, 0] lib/util_tdb.c:tdb_chainlock_with_timeout_internal(84) tdb_chainlock_with_timeout_internal: alarm (10) timed out for key VALDEZ in tdb /usr/local/samba/private/secrets.tdb I did a dump of secrets on my old

What can i do about this... ~~ # smbstatus Can't create or use IPC area. Error was File exists ERROR: Failed to initialise share modes Can't initialise shared memory - exiting In log-uri: Jan 24 07:22:41 lapd smbd[19406]: [2001/01/24 07:22:41, 0] locking/shmem_sysv.c:sysv_shm_open(667) Jan 24 07:22:41 lapd smbd[19406]: Can't create or use IPC area. Error was File exists Jan 24

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,

hi i am working in the right direction this are the message in the log.smbd [2001/04/12 11:11:48, 0] locking/shmem_sysv.c:sysv_shm_open(667) Can't create or use IPC area. Error was El fichero existe [2001/04/12 11:11:48, 0] locking/locking.c:locking_init(174) ERROR: Failed to initialise share modes I don't know what to do i am only traying to print from win clients to mandrake linux

I am running Linux Kernel 2.2.18 which is upgraded from from RedHat 6.2 kernel 2.2.14 using standard kernel patches from kernel.org. I am running Samba 2.0.7 from RedHAT 6.2 upgrade/addendums. When I get more then one connection smbd will die and log.smb will read this - [2001/03/23 06:12:19, 0] locking/shmem_sysv.c:sysv_shm_open(667) - Can't create or use IPC area. Error was File exists

I am running Samba version 2.0.6 on Solaris 2.6. When I run smbstatus, it coredumps. Here is some detailed information that may help in killing this bug. This is a run of smbstatus where it coredumps, and afterwards, a gdb session. root@grads:/depot/samba-2.0.6/bin 174# ./smbstatus Samba version 2.0.6 Service uid gid pid machine ----------------------------------------------

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

MM = M Maki (1 Oct 2002) AB = Andrew Bartlett (2 Oct 2002) MM > I have a couple of Samba (2.0.7 & 2.2.0) servers I scanned with > Nessus and they reported a security hole of "Possible to login > to the remote host using a NULL session" I have a couple of NT > servers I disabled with a registry edit. Is there a way to > prevent this on the Samba

Freebsd 5.4 smbstatus output #smbstatus Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise locking module - exiting ??????? ----- Original Message ----- From: "Jeremy Allison" <jra@samba.org> To: "Konstantin Getman" <getman@junik.lv> Sent: Tuesday, August 16, 2005 8:06 PM Subject: Re: your mail

At 03:33 AM 11/01/1999 +1100, you wrote: > >From: Hai Nguyen <hhn1@yahoo.com> >To: samba-technical@samba.org, samba@samba.org >Subject: root did not create the semaphore >Message-ID: <19991030210628.3575.rocketmail@web705.mail.yahoo.com> >MIME-Version: 1.0 >Content-Type: text/plain; charset=us-ascii > >Hello, >I am new to samba and need assistance

Hi, Can you help me.....I have downloaded the latest version of samba 3.0.0. After having followed the instructions to configure & compile etc I am getting the following error message when I run the command smbstatus. smbstatus Error trying to resolve symbol 'init_module' in /usr/local/samba/lib/charset/CP850.so: ld.so.1: smbstatus: fatal: /usr/local/samba/lib/charset/