search for: inhibited

samba 4.4..x version no problem. samba 4.5.rc1 4.5.rc2 4.5.-test all versions problem. winbind max clients = 2000 line. server crashes in 1 day.. :((( my smb file here. winbindd:use external pipes = true winbind cache time = 300 winbind reconnect delay = 30 winbind request timeout = 60 winbind max clients = 2000 # winbind max clients = 200 winbind max domain

We do this by sending an Inhibit() message to logind and receiving a file descriptor back, which we hold open until the conversion completes (or fails). This is described here: https://www.freedesktop.org/wiki/Software/systemd/inhibit/ This adds an additional optional dependency on DBus since we use DBus to call the Inhibit() method. Reported-by: Chris Cowley. --- docs/guestfs-building.pod

Am 12.07.2016 um 23:21 schrieb Reindl Harald: > > > Am 12.07.2016 um 22:55 schrieb Achim Gottinger: >> Funny current debian service files use a wrong PIDFile path (should be >> /var/run/amba/samba.pid). >> >> If I use Type=forking and an wrong PIDFile systemctl start samba must be >> CTRL-C'ed. >> >> Type=notify works with or without an proper

Hi, We are using samba 4.4.5, and we detected two issue, and we are not sure if both errors are related... 1) memory leak I have detected that It seems that samba 4.4.5 (AD mode) has a memory leak, because after some time memory usage is very high, for example with an environment with 150 users and Samba server with 2GB RAM after 222 days up, is using swap, and memory is increasing

Hello! I have a setup - Samba 4 for AD functionality and Zimbra 8 for e-mail and collaboration. Configured in Zimbra that for authentication Samba 4 has to be used.?Basically it works, but now randomly one time in two or three days authentication just stops working.?Nobody?is able to log in to Zimbra e-mail. Had to restart samba and everything goes as nothing ever happened! :( Last entry in

Hi I believe I am having DNS upgrade issues, as noticed below: /etc/init.d/samba-ad-dc status ? samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-08-02 10:04:24 -03; 5h 20min ago Docs: man:samba(8) man:samba(7) man:smb.conf(5) Main PID: 9284

Hi! I need some help. We use samba4 as AD, and now when clients connect to server, samba process stuck at 100% cpu. samba Version: 4.3.4 Release: 13.el6 top: 3777 root 20 0 131m 46m 28m R 99.7 0.3 219:20.53 /usr/local/samba4//sbin/samba -D 24541 csertam 20 0 49260 11m 9048 S 25.1 0.1 0:01.56 smbd -D 7080 squid 20 0 926m 908m 6428 S 9.9 6.2 11:43.50

Hi, I have a File Server as Domain Member and it was working properly. Recently I changed my DCs and after I am not getting authenticate users with winbind. I'm using Samba 4.6.3 as DC and Samba 4.1.17 as File Server. When I restart Samba Service, this message appears: root at dc1:/root# /etc/init.d/samba4 status ● samba4.service - LSB: start Samba4 daemons Loaded: loaded

Funny current debian service files use a wrong PIDFile path (should be /var/run/amba/samba.pid). If I use Type=forking and an wrong PIDFile systemctl start samba must be CTRL-C'ed. Type=notify works with or without an proper PIDFile. Am 12.07.2016 um 22:47 schrieb Sonic: > On Tue, Jul 12, 2016 at 4:29 PM, Achim Gottinger <achim at ag-web.biz> wrote: >> Does your PIDFile

Hello, I may have a problem with winbind setup. -with wbinfo -g and wbinfo -u I get all group/user from AD/DC. -with getent group "Domain Users" and getent passwd "remote_user" I can see the info about the specific group and specific user. -with getent group and getent passwd I only see my local group/users. -I believe that using "getent group" and "getent

Hello. We're running Samba 4.3.9 AD on two Ubuntu 16.04 LTS machines. I'm managing AD users and DNS from Windows 10 joined to the domain, by using ADUC. Last week I noticed the following error when starting ADUC as Administrator of the AD domain: ---- Naming information cannot be located because: The RPC server is unavailable. Contact your system administrator to verify that your domain

Did you install it from binary packages ? compiled from source ? Post your smb.conf here. ----- Original Message ----- From: "samba" <samba at lists.samba.org> To: "samba" <samba at lists.samba.org> Sent: Tuesday, May 9, 2017 1:01:10 PM Subject: Re: [Samba] samba process use 100% cpu Anybody? 2017. 05. 02. 10:48 keltezéssel, Papp Bence via samba írta: > Hi!

Hi there I have migrated from an older version of Samba DC to Samba 4.9.4 AD. Running Centos 7. One server with everything on...  (AD and file server) Bind 9.9.4 Built from source. Followed directions in the wiki. All seems to go fine, but when I startup samba-ad-dc it shows a few errors.    ([kdc failed to setup interfaces]) The initial tests (in the directions in wiki) go fine until I get to 

Hi, I have a Samba AD domain running 2 self compiled 4.7.3 DC's running on Centos 7. Every morning if I run wbinfo -u on DC1 I do not get any info back. I have tried reloading samba but that does not get it working. Restarting samba seems to be the only way to get it working again. DC2 continues to work normally. DC1 holds the FSMO roles and also runs bind DLZ and ISC dhcp configured per

I added a 2nd DC (ADC2) to a samba-ADS today. debian-9.3, samba-4.6.11 from Louis followed https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory replication works afai see - We wanted to test services after turning off the first DC, and running ADC2 and a DM file-server only. DC1/backup: 10.0.0.224 ADC2: 10.0.0.230 We then get NT_STATUS_NO_LOGON_SERVERS On the

I found in my firewall logs something that looked somewhat like a port scan originating from my AD DC. So I started to check the machine and already found something strange using ps aux: root at samba:/# samba -V Version 4.1.11-Debian root at samba:/# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND [...] root 10675 0.0 2.8 457368 29620 ? S Nov04

Am 13.07.2016 um 12:09 schrieb Reindl Harald: > > > Am 12.07.2016 um 23:58 schrieb Achim Gottinger: >> With >> >> Type=notify >> NotifyAccess=all >> >> systemctl status samba-ad-dc >> ● samba-ad-dc.service - Samba AD Daemon >> Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled) >> Active: active (running) since Tue

Anybody? 2017. 05. 02. 10:48 keltezéssel, Papp Bence via samba írta: > Hi! > > > I need some help. > > We use samba4 as AD, and now when clients connect to server, samba > process stuck at 100% cpu. > > samba Version: 4.3.4 Release: 13.el6 > > > top: > > 3777 root 20 0 131m 46m 28m R 99.7 0.3 219:20.53 > /usr/local/samba4//sbin/samba -D

On Monday, 24 October 2016 18:23:26 CEST Richard W.M. Jones wrote: > We do this by sending an Inhibit() message to logind and receiving a > file descriptor back, which we hold open until the conversion > completes (or fails). This is described here: > https://www.freedesktop.org/wiki/Software/systemd/inhibit/ > > This adds an additional optional dependency on DBus since we use

On 2019/02/14 21:12, Rowland Penny via samba wrote: > On Thu, 14 Feb 2019 19:14:19 +0200 > Ashley via samba <samba at lists.samba.org> wrote: > >> Hi there >> >> I have migrated from an older version of Samba DC to Samba 4.9.4 AD. >> Running Centos 7. One server with everything on...  (AD and file >> server) Bind 9.9.4 >> >> Built from