search for: 00.01

Dear "someone who can help", I am having a problem with SAMBA and SWAT (although I'm not sure SWAT is part of the problem...) I get two instances of "smbd" when ever it is started on this system. From SWAT I can only stop it ONE time. After that, each time I attempt to stop the SMBD daemon from SWAT it simply starts TWO more instances of the daemon (or something

I have a FreeBSD 4.8-Release machine that I upgraded from a 4.5 or 4.4 machine. It works just great for about 9 days, then processes will not die. It starts to become a problem when I can't kill processes, restart services, connections hang, and I can't reboot or shutdown, I have to do a hard reset. I can't really find anything in the logs to indicate what is giving me

On Thu, 26 Feb 2015 22:45:02 +0000 Rowland Penny <rowlandpenny at googlemail.com> wrote: > > Just what do you mean by 'allow no connections' ?? where from ? how? ivory:~ wynkoop$ smbclient -L prd2 Receiving SMB: Server stopped responding protocol negotiation failed ivory:~ wynkoop$ and on the server with the samba-tool built config I have these samba related processes:

Hello - I just noticed, that there seems to be a change in the way "process titles" are being set between 2.0.6 and 2.0.7: Behavior of 2.0.6: (ps aux | fgrep dovecot) ------------------ root 30803 0.0 0.0 601540 708 ?? S 1:08AM 0:00.00 dovecot/log _dovecot 30802 0.0 0.0 601544 624 ?? S 1:08AM 0:00.00 dovecot/anvil root 30801 0.0 0.0

I have Samba 3.0.4 joined to a Windows 2000 Active Directory domain with about 16,000 users and 1,000 groups. I run FreeBSD 5.2.1 on a Dell PowerEdge 1750, dual proc P4 Xeon with HTT and 1 gig of RAM. Storage is RAID-5, three drives, 36G each. I use winbind to auth users when accessing shares on the server. This is going to be our new fileserver. Check this: # time ps auxwww | grep http root

Hi There, I have an odd issue with my samba4 infrastructure, I have two servers both replicating fine. DC1 passes all tests documented here: https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Controller Except the following test: # kinit administrator # kinit: krb5_get_init_creds: Client (administrator at DOMAIN.NAME.COM.AU) unknown And in the logs I have found the

Hi, I have an issues that involves KDC, it is quite complex so I'll try to be really specific. I was running Samba42 with a secondary server replicating all was working fine. After we upgrade to Samba43 we start with the issues: 1. Replication wasn't working anymore error (WERR_LOGON_FAILURE) 2. Kerberos is also broken. On the Primary DC wouldn't allow me to to a kinit

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz.sig Quite a lot of changes, so here's a release candidate first. If no problems are reported I'll make v2.2.17 release early next week. Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. * Dovecot no

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz.sig Quite a lot of changes, so here's a release candidate first. If no problems are reported I'll make v2.2.17 release early next week. Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. * Dovecot no

Hi There, I have an odd issue with my samba4 infrastructure, I have two servers both replicating fine. DC1 passes all tests documented here: https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Controller Except the following test: # kinit administrator # kinit: krb5_get_init_creds: Client (administrator at DOMAIN.NAME.COM.AU) unknown And in the logs I have found the

I'm running a few servers sitting on top of a NetAPP file server ? everything runs great, but periodically I'm getting: nfs_getpages: error 13 vm_fault: pager read error, pid 11355 (https) errors on my screen ? not always same pid ? the annoying part is that it seems to always affect the same jail that is running .. if I shutdown all jails on that physical server, everything shuts down

On Wed, 25 Feb 2015 19:48:07 +0000 Rowland Penny <rowlandpenny at googlemail.com> wrote: > OK, you would appear to be running samba4 in AD mode, i.e. you > provisioned it. > > You have now tried to add things to your smb.conf to make it work > like samba3, this will not work! Put your smb.conf back to what it > was like just after the provision and then go and read the

Version: dovecot --version: 1.0.0 OS: OS X - 10.4.9 Architecture: G5 Dual/1.8Ghz Had a fairly normal time correction last night: May 9 20:56:56 G518X2 ntpd[219]: time set -1.212733 s Which dovecot duly noted: May 9 20:56:56 G518X2 dovecot: auth(default): Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. This morning all of the dovecot processes are

I think there is a very similar situation with the PowerPC/Mac OS X nightly tests. Over each of the past few nights, something has been filling up the process table, causing me to be unable to log in. The nightly tester wrote out regression test and feature test logs featuring hundreds of "Resource temporarily unavailable" errors from fork(), so I assume it's the qmtest

I decided to restart the provisioning process. I stopped the samba_server, deleted /usr/local/etc/smb4.conf and /var/db/samba4. I then decided to do an interactive provisioning and this is the result: [root at smb4-1 ~ (master)]# ll /var/samba4 ; ll /usr/local/etc/smb4.conf ls: /var/samba4: No such file or directory ls: /usr/local/etc/smb4.conf: No such file or directory [root at smb4-1 ~

>> I'm not sure that I follow. The qmtest stuff isn't working on Zion >> because (I believe) of an upgrade that happened on the machine (the >> qmtest >> binary doesn't work anymore?). Are you seeing a problem on freebsd where >> the feature tests go into a loop? If so, can you provide us with more >> information? >> make, ~ > ps -xu

Hello, I see that incase of command execution: :fork()" is called twice, in sshd. Once to spin off child sshd from parenat and second from child sshd, to execute command. Due to this I see 3 processes being created for each connection viz: 16398 0.0 0.3 1284 892 ?? S 4:33PM 0:00.05 sshd:child 16399 0.0 0.1 320 232 p4 Is+ 4:33PM 0:00.06 -sh -c foo_command 16401 0.0

reflum, On Mon, 2014-12-08 at 16:54 +0000, Dean Sauer wrote: > On Mon, 01 Dec 2014 23:52:35 +0000, Philipp Schafft wrote: > > > Have you set top to display threads instead of processes? > > I rebooted, one process started, after a while... back to the insane > numbers of them, and even more threads.... > > below is: > > top -H (all threads) > 1509

I am running centos 4.2 on a P4 3 GIG with 2 GIG ram. This machine has been fine for months. my laptop is fine. X is taking 99 percent of the cpu after some time. All I was doing was editing code. If I killall -9 X it comes back for a while then maxes out again. Any ideas on something to tweek??? THanks, jerry ------------ Tasks: 120 total, 2 running, 118 sleeping, 0 stopped, 0 zombie

>> > I assume you're talking about the FreeBSD run. I'm not sure what is >> > going >> > on >> >> No. You can see problem with Feature tests at >> http://llvm.cs.uiuc.edu/testresults/X86/ also (see Feature Test Results >> section ) > > I'm not sure that I follow. The qmtest stuff isn't working on Zion > because (I