similar to: 400 Server Error - chdir failed - the server is not configured correctly

I compiled the 3.0.21a samba software with the following configure options: configure --prefix=/opt/samba --exec-prefix=/opt/samba --with-krb=/usr/krb5 --with-smbwrapper --with-syslog --with-mandir=/usr/man --with-winbind Everything compiled fine; however, I am unable to see the server on the microsoft network. My smb.conf file looks like the this: [global] workgroup = CAREMARKRX

Hi All, I am running squid as reverse proxy on FreeBSD 7.0-R amd64. After running for a while (~ 8 hours), the throughput degrades to very very low rate. I found the squid is in "zoneli" state and is already a bug report on http://www.freebsd.org/cgi/query-pr.cgi?pr=106317 But after more investigation, I found there are lots of TCP Connections in FIN_WAIT_1 and never close. # netstat

Greetings, I have installed Dovecot under FreeBSD 5_3 It is pretty impressive. I got SSL working with no problem for both imap and pop3. Besides that I do still want to chroot Dovecot. I noticed that there are some options in the dovecot.conf that are intended for this. Unfortunately online resources on how to do that can't be found on google. Although I'm running the server as user

Heya.. By reading my /usr/local/etc/apache2/httpd.conf, I can find out that my Apache is running as the user "www" and the group "www" .. Yet, when I run sockstat, it tells me one of the forks are runned as root and listening on port 80 as well as the other forks are runned by www:www.. If I got a lot of users connecting to my server on port 80, will thier requests ever be

* cross posted to the mongrel mailing list* Hi, I''m running into a strange issue where one mongrel will sometimes develop hundreds of CLOSE_WAIT TCP connections, mostly to apache (I think -- see sample lsof output below). I haven''t had a chance to get the mongrel with this behavior into USR1 debug mode yet. I wrote a little loop below that will catch it next time. This

Hi, I''m running into a strange issue where one mongrel will sometimes develop hundreds of CLOSE_WAIT TCP connections, mostly to apache (I think -- see sample lsof output below). I haven''t had a chance to get the mongrel with this behavior into USR1 debug mode yet. I didn''t catch it in time. This happens a couple times a day on average at seemingly random times.

Hello, I have been using FreeBSD-7.0STABLE with BIND-9.4.2 ( i guess, forget to check before upgrade) up to 2008-01-26 (yesterday). But after upgrade FreeBSD-7.0STABLE-->FreeBSD-7.1STABLE everything goes wrong. 1.BIND can't start anymore and giving me following message at /var/log/messages: . . . Jan 27 12:30:20 ns kernel: ad4: 152587MB <WDC WD1600AAJS-75PSA0 05.06H05> at

>Date: Sun, 23 Dec 2007 06:04:02 -0800 (PST) >From: Nash Nipples <trashy_bumper@yahoo.com> >To: freebsd-security@freebsd.org >Subject: Re: IPFW: Blocking me out. How to debug? > >Dear W.D. > >oh come on. i have the same problem. Which problem are we talking about? cut and paste problem. >cut and paste logic: > >#!/bin/sh >#1. count packets >#2.

Hello samba people. I am having a odd problem related to winbindd. When I leave it running overnight on a quiet (not silent however) server I find that it generates a large number of CLOSE_WAIT state connections. 84 on a fairly quiet system in the last 18 hours. I can't seem to find any command that directly affects the number of CLOSE_WAITS. Below is my netstat listing. Any ideas would

On 11/07/15 04:06, Lee Brown wrote: > Hi Everyone, my first foray into Samba and AD both. > > Not sure if this is an OS or configuration problem. I've found similar > issues, but nothing either recent enough (is related to samba 3) or close > enough. > > FreeBSD-10.1-RELENG, Samba 4.2.2. > > I have the domain provisioned as rfc2307 > I have joined a Win7-virtual

On 11/07/15 10:16, Rowland Penny wrote: > On 11/07/15 04:06, Lee Brown wrote: >> Hi Everyone, my first foray into Samba and AD both. >> >> Not sure if this is an OS or configuration problem. I've found similar >> issues, but nothing either recent enough (is related to samba 3) or >> close >> enough. >> >> FreeBSD-10.1-RELENG, Samba 4.2.2.

On 23/07/2020 18:12, James B. Byrne via samba wrote: > > On Thu, July 23, 2020 16:16:30, Mani Wieser wrote: > >>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >>>> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED >> check where has port 137 occupied > There is nothing listening on 137 > > [root at smb4-2 ~

Hi Everyone, my first foray into Samba and AD both. Not sure if this is an OS or configuration problem. I've found similar issues, but nothing either recent enough (is related to samba 3) or close enough. FreeBSD-10.1-RELENG, Samba 4.2.2. I have the domain provisioned as rfc2307 I have joined a Win7-virtual machine to the domain I have created a new user with ADUC I have assigned 10000 to

On 23/07/2020 18:36, Jeremy Allison wrote: > On Thu, Jul 23, 2020 at 06:31:09PM +0100, Rowland penny via samba wrote: >> On 23/07/2020 18:12, James B. Byrne via samba wrote: >>> On Thu, July 23, 2020 16:16:30, Mani Wieser wrote: >>> >>>>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >>>>>> Failed to bind to

Hello. Im running tinc from long time, but recently I noticed that tinc TCP connections are not closed correctly (timeout). They seem to linger around like this: Proto Recv-Q Send-Q Local Address Foreign Address State tcp 80 0 xxx.x.x.xx:58801 xx.xxx.xxx.xx:*** ESTABLISHED tcp 515 0 xxx.x.x.xx:45422 xx.xxx.xxx.xxx:*** ESTABLISHED

I've attached a patch to OpenSSH 3.0.2p1 that will allow the client side of local port forwarding to be bound to a single address. For my purposes, binding to 127.0.0.1 or (via GatewayPorts) all addresses would not work. I overloaded the "-b local_host" option so that it's address will be used when "-L port:remote_host:remote_port" is also specified. Today is the first

hi everyone, congratulations on the release of icecast 2.1.0 I presume this is the right place to post about iceS. please correct if wrong. I have a two instance setup, and have been finding that after a network error occurs, the instance does not reconnect. The source server is behind a linux NAT box. I have simulated the problem by using iptables REJECT with tcp-reset and here is the

Hi folks, When I enabled stored configs on my puppet master, it began keeping lots of open connections to the MySQL server (as far as I understand it opened one connection for each client run and never closed them). I set up the server to close idle connections after 5 minutes. Now the database server does close the connections but the puppet master keeps them in CLOSE_WAIT state and eventually

Hi, i've got this problem with my jail and i'm abolutly lost as in the why of it. I previously posted this on comp.unix.bsd.freebsd.misc but i was advised to send here I was unable to find help on google :( To resume quick, when i'm in a jail, netstat doesn't work properly. Hopefully i have provided sufficient information for anyone willing to help me :p First of all, my system :

Hi all! I've bumped into an issue which Dovecot which has me a bit stumped; All of a sudden (ie. no obvious changes made to the config as far as I know) Dovecot seems to never stop 'imap-login' processes. This continues to the point where it will hit the 'process_limit'. For a 50-ish user install the limit was set to 100 but I increased it to 512. The only thing this changes