similar to: Samba 3.0.5 error

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

Gurus, I have downloaded and compiled 3.0.2a. I can map from 2000 to my share fine. If I try a smbstatus I get errors, see below. Can someone please point me in the right direction? smbstatus -s /usr/local/etc/meltwk-tst02.conf -d 10 edited to keep it short but this error about not having this charset repeats about 10 times. Locale charset 'ISO8859-15' unsupported, using ASCII

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

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

> "Moving tdb files in /var/lock/samba/*.tdb to /var/cache/samba/*.tdb", Nothing to worry about > Now, the smbstatus command produces the message: > > "/var/cache/samba/connections.tdb not initialised > This is normal if an SMB client has never connected to your server. > Failed to open byte range locking database > ERROR: Failed to initialise locking

Hi, I have been trying to get Samba 2.2.2 to run on HP-UX 11.00 64 bit, but seem to be running into problems with the locking databases. (Note : this is running the smb.conf file from the examples directory in SAMBA 2.2.2). I have tried to two different servers and both of them generate the same result described below. The problem I have hit is after compiling samba and starting up the system

Afternoon, I'm running OpenBSD 3.1, and since being informed that since 2.2.3a contains a bug I should upgrade to 2.3.4 - which I've done. I've installed this from source, and havn't seen any reason to believe the build process didn't work properly (Other than having duplicated binaries in /usr/local/samba/bin/ and in /usr/source_distributions/samba-2.2.4/source/bin/smbd

I am getting this error message when I type smbstatus.The message does not offer a lot of assistance. Is there any one with a good reason for this message?? Thx in advance Glenn Samba version 2.2.0a Service uid gid pid machine ---------------------------------------------- Failed to open byte range locking database ERROR: Failed to initialise

Greetings! After successfully setting up the printer using my RedHat Linux 7.2 (using command-line interface), and after installing my ethernet card (again, using command-line interface), I've tried to setup my linux server to share the printer with Windows-based machines. I thought I pretty much did everything right, but when I type a "smbstatus", I get the following: >Samba

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

Hi! I've been fighting with Samba for over a week now and I can't seem to work it out. It all started when I installed the standard samba (2.2.1a-4) which came with RH7.2. I ran "smbstatus" and got the following error: Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise locking module - exiting. I've tried the

I have just upgraded a RedHat 6.2 box from Samba 2.0.10 to Samba 2.2.5 in one of our elementary school buildings because we now have some w2k boxes that must log to the domain. I'm now getting an error on initializing the locking modules when I run smbstatus. I did the upgrade remotely so I don't know yet whether workstations work properly with the upgrade. [root@fvserver samba]#

Hi all, i am trying to run Samba 2.2.3a under a RedHat 7.2 i386 machine. After i compiled and installed the packages, i made a smb.conf up. Just some standard stuff nothing special. Now, when i start smbd and then check it with smbstatus it gives me this error : Samba version 2.2.3a Service uid gid pid machine ---------------------------------------------- tdb((null)):

I have successfully implemented Samba in the past but I am now perplexed by a new installation which fails smbstatus with the message: "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/brlock.tdb: No such file or directory Failed to open byte range locking database "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/locking.tdb: No such file or directory ERROR:

I have installed Samba 2.2.2 on Solaris 8 Sun Blade. Samba starts but I can not see any workgroup and when "smbstatus" is started I get the following error: Samba version 2.2.2 Service uid gid pid machine ---------------------------------------------- Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise

I am running RH8 with Samba 2.2.6. I am attempting to connect a Win2k box to my Linux box. I "see" Linux in Network Neighborhood, I can ping the Win2k BIOS name, and I can ping the Linux box BIOS name. However When I click on accessing linux I get resource not available. And when I run smbstatus I get the following: Samba version 2.2.6 Service uid gid pid machine

Odd, I just noticed that smbstatus does not work, either: >[root@xxxxx /root]# smbstatus > >Samba version 2.2.2 >Service uid gid pid machine >---------------------------------------------- > >Failed to open byte range locking database >ERROR: Failed to initialise locking database >Can't initialise locking module - exiting Is it possible that

Hello All, I am facing some problems with the samba 3.0.14a + Cups 1.1.12 and Solaris 10 combination. I am using the printing services on Samba. Whenever I give a smbstatus command I get the following error. The clients are able to connect and access the printers, but still this error occurs, which is really weird. Error: sessionid.tdb not initialised

Hello All, I am having a problem configuring Samba on IRIX ver. 6.5. Any help or RTFM pointers would be sincerely appreciated. I am getting the following error with test 3 in DIAGNOSIS.txt (smbclient -L hostname): read_socket_with_timeout: timeout read. read error = Connection reset by peer. session request to *SMBSERVER failed. With log level set to 10 I get the following error in

Hi, I have updated my old 2.4.7 kernel to 2.4.19 using the full download from kernel.org and installed samba-2.2.6 Using my old kernel i can access every share and everything works fine. Using my new kernel also everything works but samba,. i can telnet the system, ftp also works ok, but windows 2k tells me server not found if i try to acces the shares. i think, i forgot something to compile to