similar to: Error: Can't create or use IPC area. Error was File exists.

Displaying 20 results from an estimated 12000 matches similar to: "Error: Can't create or use IPC area. Error was File exists."

1998 Oct 26
0
SAMBA digest 1853
samba@samba.anu.edu.au wrote: > > SAMBA Digest 1853 > > For information on unsubscribing see http://samba.anu.edu.au/listproc > Topics covered in this issue include: > > 1) Re: long winded printing LARGE files soloution > by Heiko Nardmann <h.nardmann@secunet.de> > 2) Samba replacing NFS > by Jonathan Peterson
2020 Apr 30
0
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
Hi, I restored the last backup with the 4.11.6 setup. This is working fine and i can confirm that my AD is set up with a single forwarding zone, there is no _msdsc zone. On this 4.11.6 setup also the Windows DNS Tool does not complain. When upgrading to 4.12.2 DNS administration fails again with WERR_DNS_ERROR_DS_UNAVAILABLE. I will try the steps described in the MS document? and come back
2020 Apr 29
2
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
G'Day Olaf, If this was working before, then it would be this bug: https://bugzilla.samba.org/show_bug.cgi?id=14310 I'm a bit swamped right now, per Microsoft the correct fix is for our DNS Management server to ignore these values. Can you see if your error looks like this in the server logs? Andrew Bartlett On Wed, 2020-04-29 at 18:53 +0200, Olaf Dreyer via samba wrote: > Well,
2020 Apr 30
2
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
On 30/04/2020 11:44, Olaf Dreyer wrote: > Hi, > > I restored the last backup with the 4.11.6 setup. This is working fine > and i can confirm that my AD is set up with a single forwarding zone, > there is no _msdsc zone. On this 4.11.6 setup also the Windows DNS > Tool does not complain. When upgrading to 4.12.2 DNS administration > fails again with
2020 Apr 30
0
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
Am 30.04.2020 um 12:57 schrieb Rowland penny via samba: > On 30/04/2020 11:44, Olaf Dreyer wrote: >> Hi, >> >> I restored the last backup with the 4.11.6 setup. This is working >> fine and i can confirm that my AD is set up with a single forwarding >> zone, there is no _msdsc zone. On this 4.11.6 setup also the Windows >> DNS Tool does not complain. When
2020 Apr 29
0
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
Well, sometimes I? feel really old..... The last dynamic changes in DNS where made earlier this month, probably before I upgraded from 4.11.5 to newer version. With samba 4.11.5 DNS administration using samba-tool was working fine. Do you think this old setup is the reason for the problems?Any way to fix it? Best regards, Olaf Am 29.04.2020 um 18:35 schrieb Rowland penny via samba: > On
2020 Apr 29
0
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
Hi Rowland, this is a good question. Does this listing help or answer? root at OMTNDC3:/usr/local/samba/private/sam.ldb.d# ls -al total 93220 Node,CN=Schema,CN=Configuration,DC=omtn,DC=de drwxr-x--- 2 root bind????? 4096 Apr 28 16:03 . drwx------ 7 root root????? 4096 Apr 29 11:25 .. -rw------- 1 root staff 30384128 Apr 29 12:46 'CN=CONFIGURATION,DC=OMTN,DC=DE.ldb' -rw------- 1 root
2020 Apr 29
3
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
On 29/04/2020 17:29, Olaf Dreyer wrote: > Hi Rowland, > > this is a good question. Does this listing help or answer? > > root at OMTNDC3:/usr/local/samba/private/sam.ldb.d# ls -al > total 93220 Node,CN=Schema,CN=Configuration,DC=omtn,DC=de > drwxr-x--- 2 root bind????? 4096 Apr 28 16:03 . > drwx------ 7 root root????? 4096 Apr 29 11:25 .. > -rw------- 1 root staff
2020 Apr 29
3
samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS
On 29/04/2020 10:58, Olaf Dreyer via samba-technical wrote: > > I run a setup with two Samba DC (currently samba 4.12.2 on debian 10 > VMs). I started with a Windows 2003 DC but the last Windows DC has > been removed a few years ago from this setup. this is really the wrong list for this, so i have CC'ed the samba mailing list, please reply there. You say you started with Win
2001 May 01
0
ERROR: Can't create or use IPC area. Error was Cannot allocate memory
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
2000 Mar 10
0
Can't create or use IPC area - PLEASE HELP
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
2000 Mar 08
0
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
1999 Jan 29
0
MAX_OPEN_FILES - message & changeing
Nguyen Cao Dat asked about this: ERROR! Out of file structures - perhaps increase MAX_OPEN_FILES? As it happens I have started getting them too - on a PC Application server - the cause seems to be lots of files needed to be open to run applications - Lotus apps seems to be a particular culprit, but experiments indicate that even opening help on Microsoft Word opens 13 files! MAX_OPEN_FILES
2018 Jan 02
0
ext4 support
On Sat, Dec 30, 2017 at 9:37 AM, Bernd Dreyer <dreyerbernd at hotmail.de> wrote: > Hi Gene, > > thank very much you for the answer. > I have trouble with EasyBCD 2.3 on a X64 Intel non UEFI system and dual boot Windows 10 and Lubuntu. So a boot selector with fairly simple OSs. > Both systems on logical drives. You mean logical partitions within the drive. In MBR
2013 Jun 04
2
[PATCH] Set DISTRO to SUSE if /etc/SuSE-release exists
Signed-off-by: Olaf Hering <olaf@aepfle.de> --- not compile-tested. configure.ac | 3 +++ 1 file changed, 3 insertions(+) diff --git a/configure.ac b/configure.ac index 71f7b06..2db9593 100644 --- a/configure.ac +++ b/configure.ac @@ -519,6 +519,9 @@ fi if test -f /etc/arch-release; then DISTRO=ARCHLINUX fi +if test -f /etc/SuSE-release; then + DISTRO=SUSE +fi
2013 Jun 04
0
Re: [PATCH] Set DISTRO to SUSE if /etc/SuSE-release exists
On Tue, Jun 04, 2013 at 04:39:12PM +0200, Olaf Hering wrote: > Signed-off-by: Olaf Hering <olaf@aepfle.de> > --- > > not compile-tested. > > configure.ac | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/configure.ac b/configure.ac > index 71f7b06..2db9593 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -519,6 +519,9 @@ fi > if
1998 Jun 23
0
samba and clearcase (PR#7829)
Hi Jeremy, thanks for the tip but ...(there's always a but) if I do this (increase MAX_OPEN_FILES to 1024), I get an error in log.smb: Can't create or use IPC area. Error was File exists I'm using FAST_SHARE_MODES to compile samba. Does this take up too much space or is there something else wrong? Bye, Jeremy Allison wrote: > > franky.vanliedekerke@mcd.alcatel.be wrote:
2010 Oct 30
2
Samba 3.4.9 net rpc shutdown and XP Domain client
Hi @all, this is an very old problem, posted the first time 2005 to samba-testers at samba.org: If I have a Domain client with WinXP, which is part of a domain and using this client, if the PDC is not available and want to remote shut down this client with the net tool from other servers, then this is not possible, because net tries to authenticate against the PDC: testeis # net -d3 -S
2014 May 14
2
Intermittent failure
Hello. I'm in need of some help to shed some light on a strange problem. The box is running Samba 4.1.7 on FreeBSD 9.2/amd64 and I suspect (though I'm not sure) all troubles started after the upgrade from 4.1.6. The setup is quite simple: no AD, no LDAP, only one server. A command as simple as "smbclient -U user //SERVER/SHARE", if fired up several times in a row on the
2018 Nov 30
2
editing CentOS Storage SIG wiki
Sure, I've renamed it to https://wiki.centos.org/KenDreyer Would you please consider dropping this policy? It's not very welcoming to new contributors, and I don't think it'll integrate well with https://accounts.centos.org/ if the MoinMoin instance can use that for authentication. - Ken On Fri, Nov 30, 2018 at 10:39 AM Akemi Yagi <amyagi at gmail.com> wrote: > > On